MediaWiki mediawikiwiki https://www.mediawiki.org/wiki/MediaWiki MediaWiki 1.39.0-wmf.22 first-letter Media Special Talk User User talk Project Project talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Thread Thread talk Summary Summary talk Manual Manual talk Extension Extension talk API API talk Skin Skin talk Data Data talk TimedText TimedText talk Module Module talk Translations Translations talk Gadget Gadget talk Gadget definition Gadget definition talk Topic Newsletter Newsletter talk Project:Sandbox 4 1428 5386445 5380412 2022-07-28T14:06:44Z 2.47.54.12 ok wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} Ciao, this is a test 45chkzogwz2pkpu6xhh2ll8ijegnxg6 5386479 5386445 2022-07-28T14:33:28Z Hazard-Bot 560685 Bot: Automatically cleaned wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} ni8p3ypkq39hxrmit1g3300saroa1mk 5386597 5386479 2022-07-28T16:12:48Z 188.192.120.217 wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} gggg gg pvv6thvn1bwawytt350hce90z7oislo 5386600 5386597 2022-07-28T16:14:02Z 188.192.120.217 wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} gggg gg fff ife87f6itm9ram5csbiidco8reb2ymc 5386611 5386600 2022-07-28T16:33:28Z Hazard-Bot 560685 Bot: Automatically cleaned wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} ni8p3ypkq39hxrmit1g3300saroa1mk 5386691 5386611 2022-07-28T17:25:59Z 75.159.110.156 123 wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} hello! 123 kogda2v95mcz298ptrwkkejasmbk03x 5386719 5386691 2022-07-28T18:33:28Z Hazard-Bot 560685 Bot: Automatically cleaned wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} ni8p3ypkq39hxrmit1g3300saroa1mk 5386805 5386719 2022-07-28T19:11:45Z 37.138.216.218 wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} Dies ist ein Test des Wikis<syntaxhighlight lang="java"> private int lolEy = "nice" </syntaxhighlight> orlgphkvxfw08vk1p564hw7mf263hi7 5386874 5386805 2022-07-28T19:33:13Z Hazard-Bot 560685 Bot: Automatically cleaned wikitext text/x-wiki {{Please leave this line alone and write below (this is the coloured heading)}} ni8p3ypkq39hxrmit1g3300saroa1mk Sites using MediaWiki/zh 0 3476 5386385 5340533 2022-07-28T13:36:55Z Honoka55 7760646 /* Y */ // Edit via Wikiplus wikitext text/x-wiki {{MediaWiki Sites/zh}} ''This is a list of sites that are using MediaWiki, and that are written or provided in '''Chinese language'''.'' ---- 這是一個'''使用 MediaWiki 軟件的站點'''列表。以下是我們收集的'''中文'''Wiki站點。<br /> 这是一个'''使用 MediaWiki 软件的站点'''列表。以下是我们收集的'''中文'''Wiki站点。 __FORCETOC__ {| || * 請自行在列表中添加你的站點,但注意按照以下添加格式: <pre> ;網站名稱 - [http://www.example.org/ example.org] :簡短介紹 </pre> * 請使用簡短的描述並且不使用廣告用語。 * 新添加的條目會被定期檢查,不可存取或沒有使用 MediaWiki 軟體的站點會被移除。 * 請注意對於各維基媒體站點的[[:zh:网站镜像|鏡像網站]]不應加到此處。而若為中文維基百科的鏡像網站請考慮改放到[[:zh:WP:MIRROR]]。 * 索引的開頭字母應依照站點的網址中代表站點名字的欄位而不是站點標題的拉丁表記。 || * 请自行在列表中添加你的站点,但注意按照以下添加格式: <pre> ;网站名称 - [http://www.example.org/ example.org] :简短介绍 </pre> * 请使用简短的描述并且不使用广告用语。 * 新添加的条目会被定期检查,不可访问或没有使用 MediaWiki 软件的站点会被移除。 * 请注意对于各维基媒体站点的[[:zh:网站镜像|镜像网站]]不应加到此处。而若为中文维基百科的镜像网站请考虑改放到[[:zh:WP:MIRROR]]。 * 索引的开头字母应依照站点的网址中代表站点名字的字段而不是站点标题的拉丁表记。 |} * <span class="sfrac nowrap"><span style="display:inline-block; vertical-align:-0.5em; line-height:1em;"><span style="display:block;">最後檢查時間</span><span style="display:block;">最后检查时间</span></span></span>:2021-10-01 == 维基媒体基金会 == 考虑到数量问题,维基媒体基金会运营的中文维基媒体计划网站不在此列表中。项目列表可参见[[Sites using MediaWiki/Wikimedia/zh]],所有语言版本参见[[Special:Sitematrix|此页面]]。 ==中文 MediaWiki 站点== {{CompactTOC}} ===#=== ;神奇宝贝百科 - [http://wiki.52poke.com wiki.52poke.com] :关于神奇宝贝的中文百科 ;百问网Linux嵌入式维基 - [http://wiki.100ask.org wiki.100ask.org] :一个高质量的Linux嵌入式资料网站 === A === ;A+医学百科 - [http://www.a-hospital.com www.a-hospital.com] :收录医学基础概念,疾病参考,药品说明,诊断治疗方案,医院概况,医生介绍等各类医学相关内容。 ;Advent of Ascension Wiki - [http://adventofascension-zh.gamepedia.com adventofascension-zh.gamepedia.com]: 收录一切可能与Minecraft大型Mod《虚无世界》相关的百科。 ;Arcaea中文维基 - [http://wiki.arcaea.cn wiki.arcaea.cn] :Arcaea游戏相关的百科。 ;冰与火之歌中文维基 - [http://asoiaf.huijiwiki.com asoiaf.huijiwiki.com] :华语最全面的《冰与火之歌》小说维基百科,同时也收录HBO电视剧《权力的游戏》相关内容 === B === ;大西洋帝国中文维基 - [http://boardwalkempire.huijiwiki.com boardwalkempire.huijiwiki.com] :关于HBO出品美剧《大西洋帝国(Boardwalk Empire)》的中文资料站。 ;巴哈伊百科 - [http://zh.bahaikipedia.org/ zh.bahaikipedia.org] :有关巴哈伊信仰的百科全书 ;哔哩哔哩游戏百科 - [https://wiki.biligame.com/wiki/index.php?&title=%E7%89%B9%E6%AE%8A%3A%E7%89%88%E6%9C%AC wiki.biligame.com] :哔哩哔哩游戏百科是哔哩哔哩游戏旗下以玩家兴趣为导向、玩家共建为基础的免费维基平台 === C === ;红铜智库 - [http://coppermind.huijiwiki.com/ coppermind.huijiwiki.com] :美国奇幻作家布兰登·桑德森(Brandon Sanderson)中文相关维基百科,意在收录布兰登·桑德森的所有作品和世界观设定资料。 === D === ;唐顿庄园中文维基 - [http://downtonabbey.huijiwiki.com/ downtonabbey.huijiwiki.com]:英剧唐顿庄园(Downton Abbey)的中文维基页面。 ;多维百科 - [http://www.docswiki.cn www.docswiki.cn]:偏向财经、证券、投资及法律的中文百科全书。 === E === ;EVE百科- [https://www.evebk.com www.evebk.com] :EVE online(中文名:星战前夜;简称:EVE)中文维基百科。 ;EVE中文wiki - [https://eve.huijiwiki.com/ eve.huijiwiki.com] :最全面的中文EVE online维基百科,同步国服和欧服的数据更新。 ;EHWiki - [https://ehwiki.org/wiki/Main_Page ehwiki.org] :EHWiki is the official wiki for E-Hentai; information regarding all of the site's features and functions can be found here. Popular topics include:。 ;主页 - ElWiki - [http://elwiki.net/w/Main_Page/zh-hans elwiki.net] :一个含有来自不同服务器的信息的多语种艾尔之光数据库。 ;儒释道书籍在线阅读 - [https://www.ed29.com/ ed29.com] :中国传统儒释道经典书籍在线阅读及南怀瑾先生讲学视频音频下载。 ;中国分布式计算总站 - [http://www.equn.com/wiki/首页 www.equn.com] :一个科普性质的非盈利站点,由一群乐于奉献、热心于网络公益性分布式计算项目的爱好者共同创立。 ;欧陆风云4百科 - [http://www.eu4cn.com/wiki/首页 www.eu4cn.com] :人人可以编辑的欧陆风云4中文百科 === F === === G === === H === ;H萌娘 - [http://www.hmoegirl.com http://www.hmoegirl.com] :萌娘百科里站,收录ACG色情和政治条目。 ;华佗百科 - [http://www.huatuo.org/ http://www.huatuo.org] :医学中文百科。 ;开放百科 - 灰狐 - [http://wiki.huihoo.com wiki.huihoo.com] ;灰机wiki - [http://www.huijiwiki.com huijiwiki.com] :一个国内免费的wiki平台,基于最新版MediaWiki搭建,允许用户申请并创建自己的站点。 ;虎扑足球百科 - [http://soccer.hupu.com/wiki/%E9%A6%96%E9%A1%B5 http://soccer.hupu.com/wiki/%E9%A6%96%E9%A1%B5]: 关于足球方面的资料站点。 ;火器百科 - [https://huoqibaike.club https://huoqibaike.club]: 关于武器方面的资料站点,意在收入所有有关轻武器的内容。 ;逍遥法外中文维基 - [http://htgawm.huijiwiki.com http://htgawm.huijiwiki.com] :美剧逍遥法外(How to Get Away with Murder)的中文维基网站。 === I === ;Infinitipedia - [http://www.infinity-game.com/wiki 无限大典] :太空游戏无限星辰资料库 === J === ;简·奥斯汀中文维基 - [http://janeausten.huijiwiki.com janeausten.huijiwiki.com] :关于英国作家简·奥斯汀(Jane Austen)的作品及其改编影视作品的资料站点。 === K === ;Kerbal Space Program Wiki - [http://wiki.kerbalspaceprogram.com/wiki/Main_Page/zh-cn wiki.kerbalspaceprogram.com] :Kerbal Space rogram Wiki The official community-driven guide to the game. ;舰娘百科 - 专业性的舰队Collection百科全书 - [http://zh.kcwiki.moe/wiki/舰娘百科 zh.kcwiki.moe] :在百度舰队collection吧发布的舰娘各种游戏资料的相关的wiki。 === L === ;魔戒中文维基 - [http://lotr.huijiwiki.com lotr.huijiwiki.com] :致力于收集整理有关J.R.R.托尔金创作的《魔戒》及相关内容的维基站点,是华语圈最全面的魔戒资料站。 ;语言维基 - [https://langwiki.org/w/Home langwiki.org] : 人人可编辑的语言百科和教程。 === M === ;萌娘百科 - [http://zh.moegirl.org.cn zh.moegirl.org.cn] :收录女性角色,拟人萌化作品,以及(华语区作者的)原创作品的ACG向网络百科全书 ;萌娘文库 - [http://library.moegirl.org.cn/Mainpage library.moegirl.org.cn] :萌娘百科的一个子项目。 ;MLP中文维基 - [https://mlp.huijiwiki.com mlp.huijiwiki.com] :收集一切有关《[[wikipedia:zh:小马宝莉|小马宝莉]]》的信息站。 ;中文Minecraft Wiki - [http://minecraft-zh.gamepedia.com/Minecraft_Wiki http://minecraft-zh.gamepedia.com/] :收集与Minecraft相关的内容。 ;漫威电影宇宙中文资料站 - [http://mcu.huijiwiki.com mcu.huijiwiki.com] :收录漫威电影宇宙(MCU)相关资料的专题站点。 ;漫威电影宇宙资料站 - [http://mcu.huijiwiki.com/wiki/%E7%A5%9E%E7%9B%BE%E6%8E%A2%E5%91%98 mcu.huijiwiki.com] :漫威电影宇宙资料站。 === N === === O === === P === ;ProgWiki - [http://www.player.idv.tw/prog/ www.player.idv.tw] : :口袋百科向所有口袋爱好者绽放着最丰富多彩的信息。 ;台灣百科全書 - [http://zh.pedia.wikia.com zh.pedia.wikia.com] :「真正」屬於台灣鄉民的百科全書 === Q === === R === ;台灣無線電掃頻維基(台掃)(Taiwan Radio Scanning Wiki (Táisǎo)) - [http://radioscanningtw.miraheze.org/ radioscanningtw.miraheze.org] === S === ;索尼克百科 - [https://sonic.wiki/ https://sonic.wiki] :刺猬索尼克中文百科全书 === T === ;首页 - translatewiki.net - [https://translatewiki.net translatewiki.net] :Translatewiki.net是一个翻译社区、语言社区以及自由和开源项目的平台。它始于MediaWiki软件的本地化,后来增加了对MediaWiki扩展、FreeCol和其他自由和开源项目的支持。 :收录中西医医学基础概念,中药,方剂,穴位,疾病参考,药品说明,诊断治疗方案,等各类医学相关内容。 ;台灣棒球維基館 (WikiBaseball) - [http://twbsball.dils.tku.edu.tw/ twbsball.dils.tku.edu.tw] :自由的百科全书專以棒球為主題。 ;东方维基 - 包含一切关于东方Project的维基大典 - [http://zh.touhouwiki.net/wiki/东方维基 zh.touhouwiki.net] :此维基为东方系列游戏相关的维基,其中大部分游戏为ZUN氏所制作的弹幕射击游戏。 ;THBWiki · 专业性的东方Project中文维基百科 - TBSGroup - [http://www.thwiki.cc/首页 www.thwiki.cc] :本站是中文(以简体中文为主)东方Project主题维基百科。 ;主選單 - Portal Wiki - [http://theportalwiki.com/wiki/Main_Page/zh-hant theportalwiki.com] :The Portal 2 Wiki was founded on the 20th April 2011 === U === ; Undertale社区维基 - https://utcwiki.com : Undertale社区维基(utcwiki)是Undertale社区的百科网站,收录AU、音乐、画作、创作者、圈内大事件等内容。 === V === ;主页 - Valve Developer Community - [https://developer.valvesoftware.com/wiki/Main_Page:zh-cn developer.valvesoftware.com] :The Valve Developer Community is a site built by and for all users of the Source engine SDK. === W === ;吾萌百科 - https://wiki.wumoe.cn<nowiki/>:吾萌百科(WuMoe Wiki)是一群有趣又可爱的人记录自己日常所习所知的站点。 ;WikiTeamWork - [http://zh.wikiteamwork.wikia.com zh.wikiteamwork.wikia.com] :示範 MediaWiki 在教學上的應用方式。 ;Wikia中文 - [http://zh.wikia.com zh.wikia.com] :Wikia的中文站。 ;Warcraft中文维基 - [http://warcraft.huijiwiki.com warcraft.huijiwiki.com] :致力于收集魔兽世界相关设定资料的维基站点。 ;猎魔人中文维基 - [http://witcher.huijiwiki.com witcher.huijiwiki.com] :以波兰奇幻作家安杰伊·萨普科夫斯基著《猎魔人(Wiedźmin)》系列奇幻小说及其改编游戏《巫师(The Witcher)》系列为基础的所有猎魔人世界的作品资料和世界观设定。 ;猫武士维基 - [http://warriors.huijiwiki.com warriors.huijiwiki.com] :收集与Erin Hunter的小说《猫武士》/《貓戰士》/Warriors相关的资料。 === X === ;星露谷物语中文维基 - [http://xinglugu.huijiwiki.com/ http://xinglugu.huijiwiki.com/] : Steam平台上的独立游戏星露谷物语(Stardew Valley)的中文维基网站。 :用于普及科学知识的维基。 === Y === ;羊羊百科 - [https://xyy.huijiwiki.com xyy.huijiwiki.com] :收集《喜羊羊与灰太狼》相关信息的百科。 '''有图有真相的百科 - [https://www.ytyzx.org www.ytyzx.org]''' 一搜便知百科 - [https://www.yisoubianzhi.com www.yisoubianzhi.com] ;游戏百科书wiki - [https://gamebaikeshuwiki.miraheze.org gamebaikeshuwiki.miraheze.org]: 争取做网络游戏百科全书的网站。 === Z === ;舰R百科 - [http://www.zjsnrwiki.com/wiki/首页 www.zjsnrwiki.com] :舰R百科为《战舰少女R》游戏爱好者建立的网站,以帮助其他爱好者、传播军舰舰娘文化为目的建立。 ;早鸟科技 - [http://www.zaoniao.it/ zaoniao.it] :早鸟科技是一个区块链百科和数字货币大全的网站。 [[Category:MediaWiki References|zh]] q4dknvw17ht1i05qs83ky4u8ldsd3uc 5386389 5386385 2022-07-28T13:39:10Z Honoka55 7760646 // Edit via Wikiplus wikitext text/x-wiki {{MediaWiki Sites/zh}} ''This is a list of sites that are using MediaWiki, and that are written or provided in '''Chinese language'''.'' ---- 這是一個'''使用 MediaWiki 軟件的站點'''列表。以下是我們收集的'''中文'''Wiki站點。<br /> 这是一个'''使用 MediaWiki 软件的站点'''列表。以下是我们收集的'''中文'''Wiki站点。 __FORCETOC__ {| || * 請自行在列表中添加你的站點,但注意按照以下添加格式: <pre> ;網站名稱 - [http://www.example.org/ example.org] :簡短介紹 </pre> * 請使用簡短的描述並且不使用廣告用語。 * 新添加的條目會被定期檢查,不可存取或沒有使用 MediaWiki 軟體的站點會被移除。 * 請注意對於各維基媒體站點的[[:zh:网站镜像|鏡像網站]]不應加到此處。而若為中文維基百科的鏡像網站請考慮改放到[[:zh:WP:MIRROR]]。 * 索引的開頭字母應依照站點的網址中代表站點名字的欄位而不是站點標題的拉丁表記。 || * 请自行在列表中添加你的站点,但注意按照以下添加格式: <pre> ;网站名称 - [http://www.example.org/ example.org] :简短介绍 </pre> * 请使用简短的描述并且不使用广告用语。 * 新添加的条目会被定期检查,不可访问或没有使用 MediaWiki 软件的站点会被移除。 * 请注意对于各维基媒体站点的[[:zh:网站镜像|镜像网站]]不应加到此处。而若为中文维基百科的镜像网站请考虑改放到[[:zh:WP:MIRROR]]。 * 索引的开头字母应依照站点的网址中代表站点名字的字段而不是站点标题的拉丁表记。 |} * <span class="sfrac nowrap"><span style="display:inline-block; vertical-align:-0.5em; line-height:1em;"><span style="display:block;">最後檢查時間</span><span style="display:block;">最后检查时间</span></span></span>:2021-10-01 == 维基媒体基金会 == 考虑到数量问题,维基媒体基金会运营的中文维基媒体计划网站不在此列表中。项目列表可参见[[Sites using MediaWiki/Wikimedia/zh]],所有语言版本参见[[Special:Sitematrix|此页面]]。 ==中文 MediaWiki 站点== {{CompactTOC}} ===#=== ;神奇宝贝百科 - [http://wiki.52poke.com wiki.52poke.com] :关于神奇宝贝的中文百科 ;百问网Linux嵌入式维基 - [http://wiki.100ask.org wiki.100ask.org] :一个高质量的Linux嵌入式资料网站 === A === ;A+医学百科 - [http://www.a-hospital.com www.a-hospital.com] :收录医学基础概念,疾病参考,药品说明,诊断治疗方案,医院概况,医生介绍等各类医学相关内容。 ;Advent of Ascension Wiki - [http://adventofascension-zh.gamepedia.com adventofascension-zh.gamepedia.com]: 收录一切可能与Minecraft大型Mod《虚无世界》相关的百科。 ;Arcaea中文维基 - [http://wiki.arcaea.cn wiki.arcaea.cn] :Arcaea游戏相关的百科。 ;冰与火之歌中文维基 - [http://asoiaf.huijiwiki.com asoiaf.huijiwiki.com] :华语最全面的《冰与火之歌》小说维基百科,同时也收录HBO电视剧《权力的游戏》相关内容 === B === ;大西洋帝国中文维基 - [http://boardwalkempire.huijiwiki.com boardwalkempire.huijiwiki.com] :关于HBO出品美剧《大西洋帝国(Boardwalk Empire)》的中文资料站。 ;巴哈伊百科 - [http://zh.bahaikipedia.org/ zh.bahaikipedia.org] :有关巴哈伊信仰的百科全书 ;哔哩哔哩游戏百科 - [https://wiki.biligame.com/wiki/index.php?&title=%E7%89%B9%E6%AE%8A%3A%E7%89%88%E6%9C%AC wiki.biligame.com] :哔哩哔哩游戏百科是哔哩哔哩游戏旗下以玩家兴趣为导向、玩家共建为基础的免费维基平台 === C === ;红铜智库 - [http://coppermind.huijiwiki.com/ coppermind.huijiwiki.com] :美国奇幻作家布兰登·桑德森(Brandon Sanderson)中文相关维基百科,意在收录布兰登·桑德森的所有作品和世界观设定资料。 === D === ;唐顿庄园中文维基 - [http://downtonabbey.huijiwiki.com/ downtonabbey.huijiwiki.com]:英剧唐顿庄园(Downton Abbey)的中文维基页面。 ;多维百科 - [http://www.docswiki.cn www.docswiki.cn]:偏向财经、证券、投资及法律的中文百科全书。 === E === ;EVE百科- [https://www.evebk.com www.evebk.com] :EVE online(中文名:星战前夜;简称:EVE)中文维基百科。 ;EVE中文wiki - [https://eve.huijiwiki.com/ eve.huijiwiki.com] :最全面的中文EVE online维基百科,同步国服和欧服的数据更新。 ;EHWiki - [https://ehwiki.org/wiki/Main_Page ehwiki.org] :EHWiki is the official wiki for E-Hentai; information regarding all of the site's features and functions can be found here. Popular topics include:。 ;主页 - ElWiki - [http://elwiki.net/w/Main_Page/zh-hans elwiki.net] :一个含有来自不同服务器的信息的多语种艾尔之光数据库。 ;儒释道书籍在线阅读 - [https://www.ed29.com/ ed29.com] :中国传统儒释道经典书籍在线阅读及南怀瑾先生讲学视频音频下载。 ;中国分布式计算总站 - [http://www.equn.com/wiki/首页 www.equn.com] :一个科普性质的非盈利站点,由一群乐于奉献、热心于网络公益性分布式计算项目的爱好者共同创立。 ;欧陆风云4百科 - [http://www.eu4cn.com/wiki/首页 www.eu4cn.com] :人人可以编辑的欧陆风云4中文百科 === F === === G === === H === ;H萌娘 - [http://www.hmoegirl.com http://www.hmoegirl.com] :萌娘百科里站,收录ACG色情和政治条目。 ;华佗百科 - [http://www.huatuo.org/ http://www.huatuo.org] :医学中文百科。 ;开放百科 - 灰狐 - [http://wiki.huihoo.com wiki.huihoo.com] ;灰机wiki - [http://www.huijiwiki.com huijiwiki.com] :一个国内免费的wiki平台,基于最新版MediaWiki搭建,允许用户申请并创建自己的站点。 ;虎扑足球百科 - [http://soccer.hupu.com/wiki/%E9%A6%96%E9%A1%B5 http://soccer.hupu.com/wiki/%E9%A6%96%E9%A1%B5]: 关于足球方面的资料站点。 ;火器百科 - [https://huoqibaike.club https://huoqibaike.club]: 关于武器方面的资料站点,意在收入所有有关轻武器的内容。 ;逍遥法外中文维基 - [http://htgawm.huijiwiki.com http://htgawm.huijiwiki.com] :美剧逍遥法外(How to Get Away with Murder)的中文维基网站。 === I === ;Infinitipedia - [http://www.infinity-game.com/wiki 无限大典] :太空游戏无限星辰资料库 === J === ;简·奥斯汀中文维基 - [http://janeausten.huijiwiki.com janeausten.huijiwiki.com] :关于英国作家简·奥斯汀(Jane Austen)的作品及其改编影视作品的资料站点。 === K === ;Kerbal Space Program Wiki - [http://wiki.kerbalspaceprogram.com/wiki/Main_Page/zh-cn wiki.kerbalspaceprogram.com] :Kerbal Space rogram Wiki The official community-driven guide to the game. ;舰娘百科 - 专业性的舰队Collection百科全书 - [http://zh.kcwiki.moe/wiki/舰娘百科 zh.kcwiki.moe] :在百度舰队collection吧发布的舰娘各种游戏资料的相关的wiki。 === L === ;魔戒中文维基 - [http://lotr.huijiwiki.com lotr.huijiwiki.com] :致力于收集整理有关J.R.R.托尔金创作的《魔戒》及相关内容的维基站点,是华语圈最全面的魔戒资料站。 ;语言维基 - [https://langwiki.org/w/Home langwiki.org] : 人人可编辑的语言百科和教程。 === M === ;萌娘百科 - [http://zh.moegirl.org.cn zh.moegirl.org.cn] :收录女性角色,拟人萌化作品,以及(华语区作者的)原创作品的ACG向网络百科全书 ;萌娘文库 - [http://library.moegirl.org.cn/Mainpage library.moegirl.org.cn] :萌娘百科的一个子项目。 ;MLP中文维基 - [https://mlp.huijiwiki.com mlp.huijiwiki.com] :收集一切有关《[[wikipedia:zh:小马宝莉|小马宝莉]]》的信息站。 ;中文Minecraft Wiki - [http://minecraft-zh.gamepedia.com/Minecraft_Wiki http://minecraft-zh.gamepedia.com/] :收集与Minecraft相关的内容。 ;漫威电影宇宙中文资料站 - [http://mcu.huijiwiki.com mcu.huijiwiki.com] :收录漫威电影宇宙(MCU)相关资料的专题站点。 ;漫威电影宇宙资料站 - [http://mcu.huijiwiki.com/wiki/%E7%A5%9E%E7%9B%BE%E6%8E%A2%E5%91%98 mcu.huijiwiki.com] :漫威电影宇宙资料站。 === N === === O === === P === ;ProgWiki - [http://www.player.idv.tw/prog/ www.player.idv.tw] : :口袋百科向所有口袋爱好者绽放着最丰富多彩的信息。 ;台灣百科全書 - [http://zh.pedia.wikia.com zh.pedia.wikia.com] :「真正」屬於台灣鄉民的百科全書 === Q === === R === ;台灣無線電掃頻維基(台掃)(Taiwan Radio Scanning Wiki (Táisǎo)) - [http://radioscanningtw.miraheze.org/ radioscanningtw.miraheze.org] === S === ;索尼克百科 - [https://sonic.wiki/ https://sonic.wiki] :刺猬索尼克中文百科全书 === T === ;首页 - translatewiki.net - [https://translatewiki.net translatewiki.net] :Translatewiki.net是一个翻译社区、语言社区以及自由和开源项目的平台。它始于MediaWiki软件的本地化,后来增加了对MediaWiki扩展、FreeCol和其他自由和开源项目的支持。 :收录中西医医学基础概念,中药,方剂,穴位,疾病参考,药品说明,诊断治疗方案,等各类医学相关内容。 ;台灣棒球維基館 (WikiBaseball) - [http://twbsball.dils.tku.edu.tw/ twbsball.dils.tku.edu.tw] :自由的百科全书專以棒球為主題。 ;东方维基 - 包含一切关于东方Project的维基大典 - [http://zh.touhouwiki.net/wiki/东方维基 zh.touhouwiki.net] :此维基为东方系列游戏相关的维基,其中大部分游戏为ZUN氏所制作的弹幕射击游戏。 ;THBWiki · 专业性的东方Project中文维基百科 - TBSGroup - [http://www.thwiki.cc/首页 www.thwiki.cc] :本站是中文(以简体中文为主)东方Project主题维基百科。 ;主選單 - Portal Wiki - [http://theportalwiki.com/wiki/Main_Page/zh-hant theportalwiki.com] :The Portal 2 Wiki was founded on the 20th April 2011 === U === ; Undertale社区维基 - https://utcwiki.com : Undertale社区维基(utcwiki)是Undertale社区的百科网站,收录AU、音乐、画作、创作者、圈内大事件等内容。 === V === ;主页 - Valve Developer Community - [https://developer.valvesoftware.com/wiki/Main_Page:zh-cn developer.valvesoftware.com] :The Valve Developer Community is a site built by and for all users of the Source engine SDK. === W === ;吾萌百科 - https://wiki.wumoe.cn<nowiki/>:吾萌百科(WuMoe Wiki)是一群有趣又可爱的人记录自己日常所习所知的站点。 ;WikiTeamWork - [http://zh.wikiteamwork.wikia.com zh.wikiteamwork.wikia.com] :示範 MediaWiki 在教學上的應用方式。 ;Wikia中文 - [http://zh.wikia.com zh.wikia.com] :Wikia的中文站。 ;Warcraft中文维基 - [http://warcraft.huijiwiki.com warcraft.huijiwiki.com] :致力于收集魔兽世界相关设定资料的维基站点。 ;猎魔人中文维基 - [http://witcher.huijiwiki.com witcher.huijiwiki.com] :以波兰奇幻作家安杰伊·萨普科夫斯基著《猎魔人(Wiedźmin)》系列奇幻小说及其改编游戏《巫师(The Witcher)》系列为基础的所有猎魔人世界的作品资料和世界观设定。 ;猫武士维基 - [http://warriors.huijiwiki.com warriors.huijiwiki.com] :收集与Erin Hunter的小说《猫武士》/《貓戰士》/Warriors相关的资料。 === X === ;星露谷物语中文维基 - [http://xinglugu.huijiwiki.com/ http://xinglugu.huijiwiki.com/] : Steam平台上的独立游戏星露谷物语(Stardew Valley)的中文维基网站。 :用于普及科学知识的维基。 ;羊羊百科 - [https://xyy.huijiwiki.com xyy.huijiwiki.com] :收集《喜羊羊与灰太狼》相关信息的百科。 === Y === '''有图有真相的百科 - [https://www.ytyzx.org www.ytyzx.org]''' 一搜便知百科 - [https://www.yisoubianzhi.com www.yisoubianzhi.com] ;游戏百科书wiki - [https://gamebaikeshuwiki.miraheze.org gamebaikeshuwiki.miraheze.org]: 争取做网络游戏百科全书的网站。 === Z === ;舰R百科 - [http://www.zjsnrwiki.com/wiki/首页 www.zjsnrwiki.com] :舰R百科为《战舰少女R》游戏爱好者建立的网站,以帮助其他爱好者、传播军舰舰娘文化为目的建立。 ;早鸟科技 - [http://www.zaoniao.it/ zaoniao.it] :早鸟科技是一个区块链百科和数字货币大全的网站。 [[Category:MediaWiki References|zh]] r5nuetotaezxnh3bl1cxggz26qk3r1r Installation 0 4377 5387776 495214 2022-07-29T09:21:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Installation/ko 0 4572 5387791 1378805 2022-07-29T09:23:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ko]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ko]] 2mv5oubsjsrbcsagzy12ozik9wg3xf7 Installation/ja 0 4784 5387790 808362 2022-07-29T09:23:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ja]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ja]] py2vi5h7xkgtxh7fx7e96mdawd1gx0m Installation/zh 0 4823 5387804 1396206 2022-07-29T09:26:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/zh]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/zh]] qrimzzgio3038yaymj8xbmi9ea03i0e Installation/fr 0 5894 5387786 599602 2022-07-29T09:23:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/fr]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/fr]] ezkxxg8g5rvukcyd6rc5fyrnipfeb8r Installation/pl 0 6126 5387793 546144 2022-07-29T09:24:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/pl]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pl]] b6zf9uu302z9prb61dalq114ribkgg6 Installation/es 0 6449 5387783 1378806 2022-07-29T09:22:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/es]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/es]] 2gqtb4xa5rfmo3773s65aritcwisa9u Installation/de 0 6804 5387780 1378807 2022-07-29T09:22:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/de]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/de]] d5kmxqmeba5eoob88wqnq12eaf1a6rj Installation/it 0 6818 5387789 1378808 2022-07-29T09:23:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/it]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/it]] tqhmp7ofn2m4czho71m8f239k3y1wuq Installation/hu 0 12620 5387787 1378809 2022-07-29T09:23:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/hu]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/hu]] 4apmsov1n5tohqerhaeov88a77u2wgv Installation/ca 0 12672 5387778 1378810 2022-07-29T09:21:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ca]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ca]] b9f6tlf0wmlb1f9vcbxcxapr7ob2eqy Sites using MediaWiki/ko 0 13750 5386386 5152672 2022-07-28T13:36:59Z 124.50.111.138 /* ㅅ */ wikitext text/x-wiki {{MediaWiki Sites/ko}} ''This is an incomplete listing of sites that are using MediaWiki and that are written or provided in '''Korean language'''.'' ---- 아래 목록은 미디어위키를 사용하고 있으며, '''한국어'''로 쓰여 있거나 제공되는 사이트들의 목록입니다. (한국어를 포함하여) 하나 이상의 여러 언어를 쓰고 있는 위키에 대해서는 [[Sites using MediaWiki/multilingual|다언어 사이트 목록]]을 보십시오. 또한 Andrew Palo의 [http://www.cs.brown.edu/~pavlo/mediawiki/ 오픈 미디어위키 사이트의 목록]과 http://wikiindex.org/Category:MediaWiki<nowiki />에서도 한국어로 쓰여 있는 위키 사이트들의 목록을 볼 수 있습니다. ---- *아래의 목록에 여러분의 사이트를 자유롭게 추가해도 괜찮습니다. 다만 주어진 형식에 맞춰 주기 바랍니다. :<code><nowiki>;제목 - [http://www.example.org/ example.org] :짧은 설명</nowiki></code> *사이트 설명은 간결하게 하는 것이 좋습니다. 아래에 나열된 사이트들은 모두 위키 사이트입니다. 여러분의 사이트를 "...하는 위키"라고 소개할 필요는 없습니다. *새로 추가된 항목은 확인될 것입니다. 만약 연결할 수 없거나 미디어위키를 사용하지 않는 사이트는 제거됩니다. *마지막 검사 완료: (2021년 10월 1일) *:(어떤 경우에서 언급된 부분 특정 검사) ==위키미디어 위키== 위키미디어 재단의 위키 사이트들(위키백과, 위키인용집, 위키낱말사전, 위키배움터 등)은 이 목록에 포함되지 않습니다. 위키미디어 프로젝트의 목록은 [[Sites using MediaWiki/Wikimedia]] 문서를 참고하십시오. 그리고 모든 언어에 대한 완전한 목록은 [[Special:Sitematrix]] 문서를 보십시오. ==한국어로 제공되는 미디어위키 위키== {{CompactTOC}} ===#=== ===ㄱ=== ;가온 위키 - [https://www.gaonwiki.com/w/ www.gaonwiki.com/w/] ;고클래식 위키 - [http://ko.goclassic.co.kr/wiki/ ko.goclassic.co.kr/wiki/] :고전 음악 백과사전 ;國漢大百科 - [https://wiki.韓國語.漢字.net/ wiki.韓國語.漢字.net] :한글과 漢字를 함께 使用하는 위키 ===ㄴ=== ;누리위키 - [http://nuriwiki.net nuriwiki.net] : ===ㄷ=== ;디시위키 - [http://wiki.dcinside.com/ wiki.dcinside.com] :디시인사이드에서 운영하는 위키. ===ㄹ=== ;리브레 위키 - [http://librewiki.net/ librewiki.net] : ;리프위키 - [https://wiki.1if.in wiki.1if.in] ===ㅁ=== ;마비노기 위키아 - [http://ko.mabinogi.wikia.com/ ko.mabinogi.wikia.com] :[[Wikipedia:ko:넥슨|넥슨]]의 게임인 '[[Wikipedia:ko:마비노기|마비노기]]'에 대해 다루는 위키. This wiki deals with '[[Wikipedia:Mabinogi|Mabinogi]]' which is a game [[Wikipedia:Nexon|Nexon]] presents. ===ㅂ=== ;부족전쟁 위키아 - [https://bujok.fandom.com/ko bujok.fandom.com/ko] ===ㅅ=== ;샵위키 - [[https://shopwiki.kr]] ;수학노트 - [http://wiki.mathnt.net/ wiki.mathnt.net] ;선린위키 ===ㅇ=== ===ㅈ=== ;자유인사전 - [http://www.licentium.net/wiki/ www.licentium.net/wiki/] ;전서 - [http://www.ndu.kr/wiki ndu.kr/wiki/] ;제이위키 - https://jwiki.kr ;제타위키 - [http://zetawiki.com/ zetawiki.com] ;진보위키 - [http://Jinbowiki.org jinbowiki.org] : ===ㅊ=== ;창조 위키 - [http://creationwiki.org/ko/ creationwiki.org/ko/] :창조 과학의 백과사전 ===ㅋ=== ===ㅌ=== ===ㅍ=== ;페미위키 - [https://femiwiki.com https://femiwiki.com] :페미니즘 위키 ;풋케위키 - [http://footballk.net/mediawiki/ footballk.net/mediawiki/] :대한민국 축구 위키 ===ㅎ=== ;항공위키 - [https://airtravelinfo.kr/wiki airtravelinfo.kr/wiki]:항공여행, 항공기 운항, 서비스 정보 관련 위키 ===L=== ;L위키 - https://www.lwiki.net :리버럴의 L자를 따서 작명한 잡학 위키 사이트. ===U=== ;UT위키 - [http://utwiki.pe.kr/r/UT:대문 utwiki.pe.kr] :교통계 가상 회사의 활동공간, 가상 철도/버스노선 등의 문서가 있음. (현재 폐쇄적으로 운영되고 있어, 문서를 볼 수는 있지만 회원가입이나 편집은 불가능합니다.) [[Category:MediaWiki References|ko]] ffv8vxjmkvc4odsrttxrs4nng9crfh9 5386387 5386386 2022-07-28T13:37:19Z 124.50.111.138 /* ㅅ */ wikitext text/x-wiki {{MediaWiki Sites/ko}} ''This is an incomplete listing of sites that are using MediaWiki and that are written or provided in '''Korean language'''.'' ---- 아래 목록은 미디어위키를 사용하고 있으며, '''한국어'''로 쓰여 있거나 제공되는 사이트들의 목록입니다. (한국어를 포함하여) 하나 이상의 여러 언어를 쓰고 있는 위키에 대해서는 [[Sites using MediaWiki/multilingual|다언어 사이트 목록]]을 보십시오. 또한 Andrew Palo의 [http://www.cs.brown.edu/~pavlo/mediawiki/ 오픈 미디어위키 사이트의 목록]과 http://wikiindex.org/Category:MediaWiki<nowiki />에서도 한국어로 쓰여 있는 위키 사이트들의 목록을 볼 수 있습니다. ---- *아래의 목록에 여러분의 사이트를 자유롭게 추가해도 괜찮습니다. 다만 주어진 형식에 맞춰 주기 바랍니다. :<code><nowiki>;제목 - [http://www.example.org/ example.org] :짧은 설명</nowiki></code> *사이트 설명은 간결하게 하는 것이 좋습니다. 아래에 나열된 사이트들은 모두 위키 사이트입니다. 여러분의 사이트를 "...하는 위키"라고 소개할 필요는 없습니다. *새로 추가된 항목은 확인될 것입니다. 만약 연결할 수 없거나 미디어위키를 사용하지 않는 사이트는 제거됩니다. *마지막 검사 완료: (2021년 10월 1일) *:(어떤 경우에서 언급된 부분 특정 검사) ==위키미디어 위키== 위키미디어 재단의 위키 사이트들(위키백과, 위키인용집, 위키낱말사전, 위키배움터 등)은 이 목록에 포함되지 않습니다. 위키미디어 프로젝트의 목록은 [[Sites using MediaWiki/Wikimedia]] 문서를 참고하십시오. 그리고 모든 언어에 대한 완전한 목록은 [[Special:Sitematrix]] 문서를 보십시오. ==한국어로 제공되는 미디어위키 위키== {{CompactTOC}} ===#=== ===ㄱ=== ;가온 위키 - [https://www.gaonwiki.com/w/ www.gaonwiki.com/w/] ;고클래식 위키 - [http://ko.goclassic.co.kr/wiki/ ko.goclassic.co.kr/wiki/] :고전 음악 백과사전 ;國漢大百科 - [https://wiki.韓國語.漢字.net/ wiki.韓國語.漢字.net] :한글과 漢字를 함께 使用하는 위키 ===ㄴ=== ;누리위키 - [http://nuriwiki.net nuriwiki.net] : ===ㄷ=== ;디시위키 - [http://wiki.dcinside.com/ wiki.dcinside.com] :디시인사이드에서 운영하는 위키. ===ㄹ=== ;리브레 위키 - [http://librewiki.net/ librewiki.net] : ;리프위키 - [https://wiki.1if.in wiki.1if.in] ===ㅁ=== ;마비노기 위키아 - [http://ko.mabinogi.wikia.com/ ko.mabinogi.wikia.com] :[[Wikipedia:ko:넥슨|넥슨]]의 게임인 '[[Wikipedia:ko:마비노기|마비노기]]'에 대해 다루는 위키. This wiki deals with '[[Wikipedia:Mabinogi|Mabinogi]]' which is a game [[Wikipedia:Nexon|Nexon]] presents. ===ㅂ=== ;부족전쟁 위키아 - [https://bujok.fandom.com/ko bujok.fandom.com/ko] ===ㅅ=== ;샵위키 - [https://shopwiki.kr] ;수학노트 - [http://wiki.mathnt.net/ wiki.mathnt.net] ;선린위키 ===ㅇ=== ===ㅈ=== ;자유인사전 - [http://www.licentium.net/wiki/ www.licentium.net/wiki/] ;전서 - [http://www.ndu.kr/wiki ndu.kr/wiki/] ;제이위키 - https://jwiki.kr ;제타위키 - [http://zetawiki.com/ zetawiki.com] ;진보위키 - [http://Jinbowiki.org jinbowiki.org] : ===ㅊ=== ;창조 위키 - [http://creationwiki.org/ko/ creationwiki.org/ko/] :창조 과학의 백과사전 ===ㅋ=== ===ㅌ=== ===ㅍ=== ;페미위키 - [https://femiwiki.com https://femiwiki.com] :페미니즘 위키 ;풋케위키 - [http://footballk.net/mediawiki/ footballk.net/mediawiki/] :대한민국 축구 위키 ===ㅎ=== ;항공위키 - [https://airtravelinfo.kr/wiki airtravelinfo.kr/wiki]:항공여행, 항공기 운항, 서비스 정보 관련 위키 ===L=== ;L위키 - https://www.lwiki.net :리버럴의 L자를 따서 작명한 잡학 위키 사이트. ===U=== ;UT위키 - [http://utwiki.pe.kr/r/UT:대문 utwiki.pe.kr] :교통계 가상 회사의 활동공간, 가상 철도/버스노선 등의 문서가 있음. (현재 폐쇄적으로 운영되고 있어, 문서를 볼 수는 있지만 회원가입이나 편집은 불가능합니다.) [[Category:MediaWiki References|ko]] 4amau21nu852i10xp7jceg6ew2pd2tm 5386388 5386387 2022-07-28T13:37:42Z 124.50.111.138 /* ㅅ */ wikitext text/x-wiki {{MediaWiki Sites/ko}} ''This is an incomplete listing of sites that are using MediaWiki and that are written or provided in '''Korean language'''.'' ---- 아래 목록은 미디어위키를 사용하고 있으며, '''한국어'''로 쓰여 있거나 제공되는 사이트들의 목록입니다. (한국어를 포함하여) 하나 이상의 여러 언어를 쓰고 있는 위키에 대해서는 [[Sites using MediaWiki/multilingual|다언어 사이트 목록]]을 보십시오. 또한 Andrew Palo의 [http://www.cs.brown.edu/~pavlo/mediawiki/ 오픈 미디어위키 사이트의 목록]과 http://wikiindex.org/Category:MediaWiki<nowiki />에서도 한국어로 쓰여 있는 위키 사이트들의 목록을 볼 수 있습니다. ---- *아래의 목록에 여러분의 사이트를 자유롭게 추가해도 괜찮습니다. 다만 주어진 형식에 맞춰 주기 바랍니다. :<code><nowiki>;제목 - [http://www.example.org/ example.org] :짧은 설명</nowiki></code> *사이트 설명은 간결하게 하는 것이 좋습니다. 아래에 나열된 사이트들은 모두 위키 사이트입니다. 여러분의 사이트를 "...하는 위키"라고 소개할 필요는 없습니다. *새로 추가된 항목은 확인될 것입니다. 만약 연결할 수 없거나 미디어위키를 사용하지 않는 사이트는 제거됩니다. *마지막 검사 완료: (2021년 10월 1일) *:(어떤 경우에서 언급된 부분 특정 검사) ==위키미디어 위키== 위키미디어 재단의 위키 사이트들(위키백과, 위키인용집, 위키낱말사전, 위키배움터 등)은 이 목록에 포함되지 않습니다. 위키미디어 프로젝트의 목록은 [[Sites using MediaWiki/Wikimedia]] 문서를 참고하십시오. 그리고 모든 언어에 대한 완전한 목록은 [[Special:Sitematrix]] 문서를 보십시오. ==한국어로 제공되는 미디어위키 위키== {{CompactTOC}} ===#=== ===ㄱ=== ;가온 위키 - [https://www.gaonwiki.com/w/ www.gaonwiki.com/w/] ;고클래식 위키 - [http://ko.goclassic.co.kr/wiki/ ko.goclassic.co.kr/wiki/] :고전 음악 백과사전 ;國漢大百科 - [https://wiki.韓國語.漢字.net/ wiki.韓國語.漢字.net] :한글과 漢字를 함께 使用하는 위키 ===ㄴ=== ;누리위키 - [http://nuriwiki.net nuriwiki.net] : ===ㄷ=== ;디시위키 - [http://wiki.dcinside.com/ wiki.dcinside.com] :디시인사이드에서 운영하는 위키. ===ㄹ=== ;리브레 위키 - [http://librewiki.net/ librewiki.net] : ;리프위키 - [https://wiki.1if.in wiki.1if.in] ===ㅁ=== ;마비노기 위키아 - [http://ko.mabinogi.wikia.com/ ko.mabinogi.wikia.com] :[[Wikipedia:ko:넥슨|넥슨]]의 게임인 '[[Wikipedia:ko:마비노기|마비노기]]'에 대해 다루는 위키. This wiki deals with '[[Wikipedia:Mabinogi|Mabinogi]]' which is a game [[Wikipedia:Nexon|Nexon]] presents. ===ㅂ=== ;부족전쟁 위키아 - [https://bujok.fandom.com/ko bujok.fandom.com/ko] ===ㅅ=== ;샵위키 - [https://shopwiki.kr https://shopwiki.kr] ;수학노트 - [http://wiki.mathnt.net/ wiki.mathnt.net] ;선린위키 ===ㅇ=== ===ㅈ=== ;자유인사전 - [http://www.licentium.net/wiki/ www.licentium.net/wiki/] ;전서 - [http://www.ndu.kr/wiki ndu.kr/wiki/] ;제이위키 - https://jwiki.kr ;제타위키 - [http://zetawiki.com/ zetawiki.com] ;진보위키 - [http://Jinbowiki.org jinbowiki.org] : ===ㅊ=== ;창조 위키 - [http://creationwiki.org/ko/ creationwiki.org/ko/] :창조 과학의 백과사전 ===ㅋ=== ===ㅌ=== ===ㅍ=== ;페미위키 - [https://femiwiki.com https://femiwiki.com] :페미니즘 위키 ;풋케위키 - [http://footballk.net/mediawiki/ footballk.net/mediawiki/] :대한민국 축구 위키 ===ㅎ=== ;항공위키 - [https://airtravelinfo.kr/wiki airtravelinfo.kr/wiki]:항공여행, 항공기 운항, 서비스 정보 관련 위키 ===L=== ;L위키 - https://www.lwiki.net :리버럴의 L자를 따서 작명한 잡학 위키 사이트. ===U=== ;UT위키 - [http://utwiki.pe.kr/r/UT:대문 utwiki.pe.kr] :교통계 가상 회사의 활동공간, 가상 철도/버스노선 등의 문서가 있음. (현재 폐쇄적으로 운영되고 있어, 문서를 볼 수는 있지만 회원가입이나 편집은 불가능합니다.) [[Category:MediaWiki References|ko]] q0w3m6eodt80k0ktj9xl9pa7g1tbwzy Install 0 13812 5387775 495216 2022-07-29T09:21:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Combating spam 100 13916 5387467 5202550 2022-07-28T22:39:45Z Shirayuki 472859 make untranslatable wikitext text/x-wiki <languages/> {{RightTOC}} <translate><!--T:1--> Like all current dynamic web sites, wikis are a common target for spammers wishing to promote products or websites.</translate> <translate><!--T:2--> MediaWiki offers a number of features designed to [[<tvar name=1>Special:MyLanguage/Manual:Combating vandalism</tvar>|combat vandalism in general]].</translate> <translate><!--T:176--> On this page we deal specifically with [[m:Wiki spam|wiki spam]], which is often automated.</translate> <translate> == Overview == <!--T:3--> <!--T:4--> Common tools used to combat wiki spam typically fall into these categories: <!--T:5--> * Requiring log in and/or a CAPTCHA on certain operations, such as edits, adding external links, or new user creation</translate> <translate> <!--T:6--> * Blocking edits from known blacklisted IP addresses or IPs running open proxies</translate> <translate> <!--T:7--> * Blocking edits which add specific unwanted keywords or external links</translate> <translate> <!--T:8--> * Blocking specific username and page title patterns commonly used by spambots</translate> <translate> <!--T:9--> * Blocking edits by new or anonymous users to specific often-targeted pages</translate> <translate> <!--T:10--> * Whitelisting known-good editors (such as admins, regular contributors) while placing restrictions on new or anonymous users</translate> <translate> <!--T:11--> * Cleanup scripts or bulk deletion (<tvar name=ext>{{ll|Extension:Nuke}}</tvar>) of existing posts from recently-banned spambots <!--T:12--> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </translate> <translate><!--T:13--> Note that many of these features are not activated by default.</translate> <translate><!--T:14--> If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</translate> <translate><!--T:15--> By all means ask your users to help [[<tvar name=1>m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam</tvar>|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</translate> <translate><!--T:16--> It helps to raise the bar a little.</translate> <translate><!--T:17--> You should also note however, that none of these solutions can be considered completely spam-proof.</translate> <translate><!--T:136--> Checking "<tvar name=1>{{int|recentchanges}}</tvar>" (<tvar name=2>[[Special:RecentChanges]]</tvar>) regularly is an effective practice.</translate> <translate> ==Quickest solutions to try first== <!--T:19--> </translate> <translate><!--T:20--> Fighting spam should not be too hard.</translate> <translate><!--T:21--> If you want to quickly and drastically reduce spam, try these few steps first.</translate> <translate> <!--T:135--> * Install the [[<tvar name=1>Special:MyLanguage/Extension:StopForumSpam</tvar>|StopForumSpam]] extension to block known spammer IPs.</translate> <translate> <!--T:23--> * Install and set up the basic antivandalism extensions (already shipped with [[<tvar name=download>Special:MyLanguage/Download</tvar>|last releases]]), in particular <tvar name=ext>{{ll|Extension:ConfirmEdit}}</tvar>.</translate> <translate> <!--T:24--> * [[<tvar name=1>Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha</tvar>|Configure QuestyCaptcha]] and [[<tvar name=2>Special:MyLanguage/Extension:ConfirmEdit#Configuration</tvar>|change default settings]] if needed for your wiki.</translate> <translate> <!--T:146--> * Enable <tvar name=1>{{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}</tvar>, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. <!--T:25--> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. ==Antispam setup basics== <!--T:26--> </translate> {{anchor|CAPTCHA}} <translate> ===CAPTCHA=== <!--T:27--> </translate> <translate><!--T:28--> One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</translate> <translate><!--T:29--> The <tvar name=ConfirmEdit>{{ll|Extension:ConfirmEdit|ConfirmEdit}}</tvar> extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</translate> <translate> <!--T:30--> * all edits</translate> <translate> <!--T:31--> * edits adding new, unrecognized external links</translate> <translate> <!--T:32--> * user registration </translate> <translate><!--T:33--> The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</translate> <translate><!--T:34--> Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</translate> <translate><!--T:35--> The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</translate> <translate><!--T:36--> ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</translate> <translate><!--T:37--> It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</translate> <translate><!--T:38--> One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</translate> <translate><!--T:39--> You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</translate><ref> <translate><!--T:137--> For example, [<tvar name=url>https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards</tvar> Section 508 Standards for Electronic and Information Technology]</translate> </ref> <translate><!--T:40--> Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</translate> <translate><!--T:41--> For this reason it should be combined with other mechanisms.</translate> ===rel="nofollow"=== <translate> <!--T:42--> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. <!--T:142--> You can switch ''off'' this behaviour on a site-wide basis using <tvar name=1>{{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}}</tvar> or on a per-namespace basis using the <tvar name=2>{{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}}</tvar> configuration variable. </translate> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <translate> ==Antispam routine: tailored measures== <!--T:43--> <!--T:44--> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </translate> {{anchor|Individual page protection}} <translate> ===Individual page protection=== <!--T:45--> <!--T:46--> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </translate> <translate><!--T:47--> As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</translate> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. <translate> === Abuse filter === <!--T:48--> <!--T:138--> <tvar name=1>{{ll|Extension:AbuseFilter}}</tvar> allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </translate> <translate><!--T:49--> It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</translate> <translate><!--T:148--> It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</translate> <translate><!--T:149--> The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</translate> <translate> <!--T:50--> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. ===SpamBlacklist=== <!--T:51--> <!--T:139--> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. <!--T:52--> A popular extension for MediaWiki is the <tvar name=1>{{ll|Extension:SpamBlacklist|SpamBlacklist}}</tvar> extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). <!--T:53--> The <tvar name=1>{{ll|Extension:TitleBlacklist|TitleBlacklist}}</tvar> extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. === Open proxies === <!--T:54--> <!--T:55--> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </translate> <translate><!--T:56--> Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</translate> <translate><!--T:150--> Most such blocks are performed manually, when noticing the abuse.</translate> <translate><!--T:151--> It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the <tvar name=1>{{ll|Extension:CheckUser|CheckUser}}</tvar> extension.</translate> <translate> <!--T:110--> Several extensions, particularly the <tvar name=1>{{ll|Extension:Tor block|Tor block}}</tvar> extension, blocks a range of open proxies. <!--T:111--> Since 1.22, <tvar name=1>{{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}}</tvar> is available to make blocks more effective. ==Hardcore measures== <!--T:57--> <!--T:58--> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </translate> === $wgSpamRegex === <translate><!--T:112--> MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <tvar name=1><code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code></tvar> configuration variable.</translate> <translate><!--T:145--> You can use this to block additional snippets of text or markup associated with common spam attacks.</translate> <translate><!--T:60--> Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</translate> <translate><!--T:152--> Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</translate> <translate><!--T:153--> <tvar name=1>{{ll|Extension:SpamRegex}}</tvar> allows editing of this variable on-wiki.</translate> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <translate><!--T:61--> This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</translate> <translate><!--T:154--> The '/i' at the end makes the search case insensitive.</translate> <translate><!--T:155--> It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</translate> <translate> === Apache configuration changes === <!--T:62--> </translate> <translate><!--T:63--> In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</translate> <translate><!--T:156--> These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</translate> <translate> ==== Filtering by user agent ==== <!--T:64--> <!--T:65--> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </translate> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <translate> <!--T:66--> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". <!--T:67--> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </translate> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <translate> ==== Preventing blocked spammers from consuming resources ==== <!--T:68--> <!--T:69--> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources.</translate> <translate><!--T:113--> By adding a [<tvar name=apache>http://httpd.apache.org/docs/2.2/howto/access.html</tvar> deny from] pragma such as the following to your <tvar name=hta><code>.htaccess</code></tvar> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</translate> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <translate> ===IP address blacklists=== <!--T:70--> <!--T:71--> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </translate> <translate><!--T:72--> A relatively simple [[<tvar name=1>#CAPTCHA</tvar>|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[<tvar name=2>#Individual page protection</tvar>|certain often-spammed pages]].</translate> <translate><!--T:144--> These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</translate> <translate> <!--T:73--> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance <tvar name=1>[http://www.stopforumspam.com/downloads stopforumspam.com]</tvar> has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. ==== CPU usage and overload ==== <!--T:74--> <!--T:75--> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. ==== DNSBL ==== <!--T:76--> </translate> <translate><!--T:140--> You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</translate> <translate><!--T:141--> For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</translate> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <translate> ==== Bad Behavior and Project HoneyPot ==== <!--T:77--> <!--T:78--> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see <tvar name=1>{{ll|Extension:Bad Behavior}}</tvar>. <!--T:79--> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </translate> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <translate><!--T:114--> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans.</translate>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <translate> <!--T:115--> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </translate> ==== $wgProxyList ==== {{Warning|1=<translate><!--T:116--> This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</translate>}} <translate> <!--T:117--> You can set the variable <tvar name=1>{{wg|ProxyList}}</tvar> to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </translate> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <translate><!--T:118--> You then set in your <tvar name=ls>LocalSettings.php</tvar>:</translate> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <translate> <!--T:82--> You may want to save these commands in a file called e.g. <tvar name=1><code>updateBannedIPs.sh</code></tvar>, so you can run it periodically. <!--T:83--> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [<tvar name=url>http://www.pschmidt.it/vim_source/updateBanned_php.txt</tvar> here]. <!--T:80--> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. <!--T:84--> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… ==== Honeypots, DNS BLs and HTTP BLs ==== <!--T:85--> <!--T:86--> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? <!--T:87--> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. <!--T:88--> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </translate> <translate><!--T:119--> The <tvar name=1>{{wg|EnableDnsBlacklist}}</tvar> and <tvar name=2>{{wg|DnsBlacklistUrls}}</tvar> options in MediaWiki provide a primitive example of access to a DNS blacklist.</translate> <translate><!--T:147--> Set the following settings in <tvar name=2>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</tvar> and IP addresses listed as HTTP spam are blocked:</translate> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <translate> <!--T:120--> The DNS blacklist operates as follows: <!--T:157--> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89')</translate> <translate> <!--T:158--> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server</translate> <translate> <!--T:159--> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.')</translate> <translate> <!--T:160--> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </translate> <translate><!--T:121--> The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</translate> <translate><!--T:161--> Unlike <tvar name=1>{{wg|ProxyKey}}</tvar> settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</translate> <translate><!--T:162--> This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</translate> <translate> <!--T:122--> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: <!--T:163--> * <tvar name=tornevall>[http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.]</tvar> operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs.</translate> <translate> <!--T:164--> * <tvar name=projecthoneypot>[http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.]</tvar> specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.'</translate> <translate> <!--T:165--> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for <tvar name=botscout>[http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89]</tvar> would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for <tvar name=stopforumspam>[http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89]</tvar> would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </translate> <translate><!--T:123--> With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</translate> <translate><!--T:166--> The inability to specify more than one blacklist server further limits the usefulness of the built-in <tvar name=1>{{wg|EnableDnsBlacklist}}</tvar> and <tvar name=2>{{wg|DnsBlacklistUrls}}</tvar> options.</translate> <translate><!--T:167--> Since <tvar name=rev>[[rev:58061]]</tvar>, MediaWiki has been able to check multiple DNSBLs by defining <tvar name=3><code>$wgDnsBlacklistUrls</code></tvar> as an array.</translate> <translate><!--T:89--> Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</translate> <translate><!--T:168--> As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</translate> <translate><!--T:90--> Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</translate> <translate><!--T:169--> A relatively small number of spambots appear to be behind a large percentage of the overall problem.</translate> <translate><!--T:170--> Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</translate> <translate><!--T:171--> One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</translate> <translate> <!--T:91--> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. ==== But what's this about honeypots? ==== <!--T:92--> <!--T:124--> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </translate> <translate><!--T:93--> Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</translate> <translate><!--T:172--> Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</translate> <translate><!--T:173--> The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</translate> <translate><!--T:174--> Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</translate> <translate><!--T:175--> See [[w:Honeypot_(computing)|Honeypot (computing)]].</translate> <translate> <!--T:94--> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. <!--T:95--> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. ==== More lists of proxy and spambot IPs ==== <!--T:96--> <!--T:125--> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </translate> <translate><!--T:97--> In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</translate> <translate><!--T:99--> It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</translate> <translate><!--T:126--> See also [<tvar name=sdsc>http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html</tvar> Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</translate> <translate><!--T:100--> Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</translate> <translate><!--T:101--> Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</translate> <translate><!--T:127--> To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</translate> # <translate><!--T:128--> Add one line to <tvar name=1>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</tvar> to set:</translate> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <translate><!--T:129--> Add the following text in <tvar name=blockiptext>[[MediaWiki:Blockiptext]]</tvar> to display:</translate> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <translate><!--T:102--> This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</translate> <translate><!--T:130--> Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[<tvar name=ext-SpamBlacklist>Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)</tvar>|specific external links]] being [[<tvar name=ext-SpamRegex>Extension:SpamRegex</tvar>|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[<tvar name=ext-TitleBlacklist>Extension:TitleBlacklist</tvar>|title or username blacklists]] and [[<tvar name=ext-ConfirmEdit>Extension:ConfirmEdit</tvar>|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[<tvar name=ext-AkismetKlik>Extension:AkismetKlik</tvar>|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</translate> <translate> == If spam has won the battle == <!--T:103--> </translate> <translate><!--T:104--> You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</translate> <translate><!--T:131--> See <tvar name=manual>{{ll|Manual:Combating vandalism}}</tvar> and in particular [[<tvar name=cleanup>Manual:Combating vandalism#Cleaning up</tvar>|Cleaning up]], [[<tvar name=restrict>Manual:Combating vandalism#Restrict editing</tvar>|Restrict editing]].</translate> <translate> <!--T:132--> See ''External links'' for other tools without MediaWiki support. == Other ideas == <!--T:133--> <!--T:134--> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. ==See also== <!--T:105--> </translate> *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. <translate> === Extensions === <!--T:106--> </translate> *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <translate> ==== Bundled in the installer ==== <!--T:107--> <!--T:108--> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </translate> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users <translate> === Settings === <!--T:109--> </translate> * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <translate> === External links === <!--T:143--> </translate> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] nxdoa320jd1ehpe4gdg76yz5khi5tbw Manual:Installation 100 14077 5387808 150072 2022-07-29T09:26:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Running MediaWiki 100 14084 5387828 150585 2022-07-29T09:30:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Running MediaWiki 0 14085 5387806 150079 2022-07-29T09:26:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Installation/ru 0 14456 5387796 1378811 2022-07-29T09:24:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ru]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ru]] dszrz7cbezxeak88ngzg6sexsb1tipm Installation/fi 0 14841 5387785 1378812 2022-07-29T09:22:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/fi]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/fi]] gn4d8iwiwl5d41w4mpykqlgioeembqu Extension talk:Page Forms 103 14971 5387443 5385183 2022-07-28T22:29:44Z Jonathan3 9129 /* How do you transclude user input from a form into a page without the section heading? */ wikitext text/x-wiki {{Page Forms navigation}} {{Archive box| * [[Extension talk:Page Forms/Archive 2007|2007]] * [[Extension talk:Page Forms/Archive January to March 2008|January to March 2008]] * [[Extension talk:Page Forms/Archive April to June 2008|April to June 2008]] * [[Extension talk:Page Forms/Archive July to September 2008|July to September 2008]] * [[Extension talk:Page Forms/Archive October to December 2008|October to December 2008]] * [[Extension talk:Page Forms/Archive January to April 2009|January to April 2009]] * [[Extension talk:Page Forms/Archive May to July 2009|May to July 2009]] * [[Extension talk:Page Forms/Archive August to September 2009|August to September 2009]] * [[Extension talk:Page Forms/Archive October to December 2009|October to December 2009]] * [[Extension talk:Page Forms/Archive January to February 2010|January to February 2010]] * [[Extension talk:Page Forms/Archive March to May 2010|March to May 2010]] * [[Extension talk:Page Forms/Archive June 2010|June 2010]] * [[Extension talk:Page Forms/Archive July to August 2010|July to August 2010]] * [[Extension talk:Page Forms/Archive September to October 2010|September to October 2010]] * [[Extension talk:Page Forms/Archive November 2010|November 2010]] * [[Extension talk:Page Forms/Archive December 2010|December 2010]] * [[Extension talk:Page Forms/Archive January 2011|January 2011]] * [[Extension talk:Page Forms/Archive February to March 2011|February to March 2011]] * [[Extension talk:Page Forms/Archive April 2011|April 2011]] * [[Extension talk:Page Forms/Archive May to June 2011|May to June 2011]] * [[Extension talk:Page Forms/Archive July 2011|July 2011]] * [[Extension talk:Page Forms/Archive August to September 2011|August to September 2011]] * [[Extension talk:Page Forms/Archive October to November 2011|October to November 2011]] * [[Extension talk:Page Forms/Archive December 2011|December 2011]] * [[Extension talk:Page Forms/Archive January to February 2012|January to February 2012]] * [[Extension talk:Page Forms/Archive March 2012|March 2012]] * [[Extension talk:Page Forms/Archive April to June 2012|April to June 2012]] * [[Extension talk:Page Forms/Archive July to August 2012|July to August 2012]] * [[Extension talk:Page Forms/Archive September to October 2012|September to October 2012]] * [[Extension talk:Page Forms/Archive November to December 2012|November to December 2012]] * [[Extension talk:Page Forms/Archive January to February 2013|January to February 2013]] * [[Extension talk:Page Forms/Archive March to April 2013|March to April 2013]] * [[Extension talk:Page Forms/Archive May to July 2013|May to July 2013]] * [[Extension talk:Page Forms/Archive August to September 2013|August to September 2013]] * [[Extension talk:Page Forms/Archive October to December 2013|October to December 2013]] * [[Extension talk:Page Forms/Archive January to March 2014|January to March 2014]] * [[Extension talk:Page Forms/Archive April to June 2014|April to June 2014]] * [[Extension talk:Page Forms/Archive July to August 2014|July to August 2014]] * [[Extension talk:Page Forms/Archive September to December 2014|September to December 2014]] * [[Extension talk:Page Forms/Archive January 2015|January 2015]] * [[Extension talk:Page Forms/Archive February to March 2015|February to March 2015]] * [[Extension talk:Page Forms/Archive April to May 2015|April to May 2015]] * [[Extension talk:Page Forms/Archive June to August 2015|June to August 2015]] * [[Extension talk:Page Forms/Archive September 2015|September 2015]] * [[Extension talk:Page Forms/Archive October to December 2015|October to December 2015]] * [[Extension talk:Page Forms/Archive January to March 2016|January to March 2016]] * [[Extension talk:Page Forms/Archive April to July 2016|April to July 2016]] * [[Extension talk:Page Forms/Archive August to October 2016|August to October 2016]] * [[Extension talk:Page Forms/Archive November to December 2016|November to December 2016]] * [[Extension talk:Page Forms/Archive January 2017|January 2017]] * [[Extension talk:Page Forms/Archive February to March 2017|February to March 2017]] * [[Extension talk:Page Forms/Archive April to July 2017|April to July 2017]] * [[Extension talk:Page Forms/Archive August to December 2017|August to December 2017]] * [[Extension talk:Page Forms/Archive January to February 2018|January to February 2018]] * [[Extension talk:Page Forms/Archive March to May 2018|March to May 2018]] * [[Extension talk:Page Forms/Archive June to July 2018|June to July 2018]] * [[Extension talk:Page Forms/Archive August to September 2018|August to September 2018]] * [[Extension talk:Page Forms/Archive October to December 2018|October to December 2018]] * [[Extension talk:Page Forms/Archive January to February 2019|January to February 2019]] * [[Extension talk:Page Forms/Archive March to June 2019|March to June 2019]] * [[Extension talk:Page Forms/Archive July to August 2019|July to August 2019]] * [[Extension talk:Page Forms/Archive September to December 2019|September to December 2019]] * [[Extension talk:Page Forms/Archive January to March 2020|January to March 2020]] * [[Extension talk:Page Forms/Archive April to June 2020|April to June 2020]] * [[Extension talk:Page Forms/Archive July to September 2020|July to September 2020]] * [[Extension talk:Page Forms/Archive October to December 2020|October to December 2020]] * [[Extension talk:Page Forms/Archive January to February 2021|January to February 2021]] * [[Extension talk:Page Forms/Archive March to April 2021|March to April 2021]] * [[Extension talk:Page Forms/Archive May to December 2021|May to December 2021]] * [[Extension talk:Page Forms/Archive January to March 2022|January to March 2022]] }} == [RESOLVED] No display of a jqplotchart query called from a form == MW 1.35.6 / PHP 7.4.27 / MariaDB 10.1.48 / SMW 3.2.3 / PF 5.3.4 My SearchPeople query form calls the SearchPeople template which contains the following query (which I have simplified for testing): <code><nowiki>{{#ask:[[Category:People]]|?unit|mainlabel=-|format=jqplotchart|distribution=1|charttype=pie}}</nowiki></code> The request does not succeed (a spinning logo rotates indefinitely) when I go through the form that I also simplified for testing: <code><nowiki>{{{for template|searchPeople}}}</nowiki><nowiki>{{end template}}</nowiki></code> Yet the template page does display the graphic. In a previous version of my MediaWiki system (MW 1.31, SMW 2.5.8, PF 4.3.1), this works (with exactly the same code and more complex form/template duos). PS1: To see if this changed anything, I switched the type of the form button from GET to POST by changing line 149 in PF_RunQuery.php. Nothing changed. PS2: Since the upgrade to PF 5.3.4, I also get this type of warning: <code>Notice: Uninitialized string offset: 37 in /var/www/mediawiki/extensions/PageForms/includes/PF_FormPrinter.php on line 1009</code> I can add the bug in Phabricator if necessary. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 11:09, 1 April 2022 (UTC) :Do you see any JavaScript errors, if you look in the browser console? To see a clear error message, you may need to add "&debug=true" to the URL. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:12, 1 April 2022 (UTC) ::In the meantime, I'm debugging the upgrade from SMW 3.2.3 to SMW 4.0.1. which messes up my wiki by blocking all javascript. ::I've just noticed that the jqplotchart problem and the problems related to the migration to SMW 4.0.1 are naturally solved when I remove the display errors: ::<syntaxhighlight lang="php"># ini_set( 'display_errors', 1 );</syntaxhighlight> ::Does this little # allow SMW 4.0.1 to work and thus the query form leading to a jqplot ask to succeed? I don't know and I don't care (yet). Thank you in any case Yaron for forcing me to go deeper into the debugging. --[[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 21:58, 1 April 2022 (UTC) == editor=wikieditor in a field crashes the form == MW 1.37.2 / PHP 7.4.27 / SMW 4.0.1 / PF 5.3.4 Specifying editor=wikieditor in a textarea field causes the form to crash when trying to create a new page with that form. This is the error message for a form called MyForm: <code>WikiPage constructed on a Title that cannot exist as a page: Spécial:AddData/MyForm</code> The form does not crash when modifying a previously created instance. The problem was not seen with MW1.35.4 and SMW3.2.3 [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 21:02, 2 April 2022 (UTC) :I'm using the same version of MW and PageForms. But I'm not able to see this error while creating a page. [[User:Techwizzie|Techwizzie]] ([[User talk:Techwizzie|talk]]) 02:55, 17 April 2022 (UTC) == Embedding query forms broken == All of a sudden embedding query forms does not work any longer " <code><nowiki>{{Special:RunQuery/PageQueryKeyword}}</nowiki></code> leads to <nowiki>Special:RunQuery?pfRunQueryFormName=PageQueryKeyword&PageQueryKeyword[keyword][]=foo+bar&PageQueryKeyword[keyword][is_list]=1&wpRunQuery=&pf_free_text=</nowiki> The error I am now getting: "You must specify a form name in the URL; the URL should look like "Special:RunQuery/<form name>". The form looks like this: <pre> <includeonly>{{{info|query title=Query for pages with the given keyword:}}} {{{for template|PageQueryKeyword}}} {{{field|keyword|input type=tokens|values from property=Has keyword|max values=1}}} {{{standard input|run query|label=Start search}}} {{{end template}}}</includeonly> </pre> Last time I used this about 4 weeks ago it was still working. In the meantime nothing was updated for the wiki, i.e. it is on MW 1.31.16 and PF 5.0.1. Now updating to PF 5.2.1 did not help. Any suggestions that may help to find out why it is no longer working. [[Special:Contributions/2003:F1:C725:6300:4094:E81D:9963:3FBA|2003:F1:C725:6300:4094:E81D:9963:3FBA]] 08:34, 12 April 2022 (UTC) :Embedding a query form actually works fine for me. It's strange that your URL has Special:RunQuery as (I assume) the name of the page, and not the actual page that the form is embedded in. Why is that, do you know? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 18:38, 18 April 2022 (UTC) :: Yes the URL is as posted and not containing the name of the originating page. Since the error message claims that Special:RunQuery should be part of the URL it did not realize that this could be the issue. Still, worked before and not sure why this happens all of a sudden. Now using queryformlink to provide the search though not as nice. --[[User:Marbot|Marbot]] ([[User talk:Marbot|talk]]) 07:30, 20 April 2022 (UTC) == Preload field in free text not working with <nowiki>{{#autoedit:...</nowiki> == On '''[https://gerrit.wikimedia.org/g/mediawiki/extensions/PageForms.git/+/d87af0d48d1983ed05b1c440cd500ce911c48dc8 Page Forms master]''' {| class = "wikitable" ! Product ! Version |- | MediaWiki || 1.35.5 |- | PHP || 7.4.22 (cgi-fcgi) |- | MariaDB || 10.4.11-MariaDB |- | ICU || 66.1 |- | Lua || 5.1.4 |} You can preload data for the '''[[Extension:Page_Forms/Defining_forms#The_free_text_input|free text input]]''' which works fine when used with <code><nowiki>{{#formlink:....</nowiki></code> but it does not seem to work with the <code><nowiki>{{#autoedit:...</nowiki></code> parserfunction. I tried to figure out what is going wrong but the below simple '''Form '''works fine when used with the '''formlink '''parserfunction but when used with the '''autoedit '''parserfunction the content of the '''Load autofill''' page is ignored and does not end up on the created page. <pre> <includeonly>{{{info|query form at top|onlyinclude free text}}}{{{for template|Aaaa}}} * {{{field|Equipment}}} {{{end template}}} {{{standard input|free text|input type=textarea|editor=wikieditor|rows=25|preload=Load autofill}}}</includeonly> </pre> I am not sure if this is on purpose or if there is something wrong. We only used preload for template parameters until now but we want to be able to preload the free text on a page. Thanks and regards, [[User:Jongfeli|Felipe]] ([[User talk:Jongfeli|talk]]) 12:40, 12 April 2022 (UTC) :I believe it's on purpose, although maybe it's not ideal; parameters like "preload=" and "default=" only apply when creating a new page, not when editing an existing page, and I think that holds true even when using #autoedit. If that's true, then there may be no way to modify the free text from within #autoedit, although there probably should be. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 18:33, 18 April 2022 (UTC) ::Hello Yaron, the above applies when generating a new page not an existing one with '''formlink '''or '''autoedit'''. I understand and agree (we had that discussion in the past) that it does not apply for editing existing pages. To me it seems that '''autoedit '''is not "aware" or ignores the '''standard input|free text''' field in the form when it automatically generates the new page. It only "looks" in-between the <code><nowiki>{{{for template|....</nowiki></code> and <code><nowiki>{{{end template}}}</nowiki></code> calls. [[User:Jongfeli|Felipe]] ([[User talk:Jongfeli|talk]]) 11:18, 21 April 2022 (UTC) == Table Error in textarea field == <nowiki>"|" is not allowed, except within {{...}}, [[...]], or special tags </nowiki> [[File:Pageforms5.4.3Textarea.png]] I am getting the above error. My fields are set for textarea. Not sure if cargo field matters but it is wikitext. I am using PageForms 5.3.4 and mediawiki 1.35 Thanks, Margaret [[User:Issiegainsley|Issiegainsley]] ([[User talk:Issiegainsley|talk]]) 13:58, 16 April 2022 (UTC) :The pipes are used within the template to separate the parameters with their values. Any table added to the parameter like you describe would "break" the template. You can still add tables to to a parameter but you need to replace all the pipes "|" used in the table with the magic word <code><nowiki>{{!}}</nowiki></code> . See: [[Help:Magic_words#Other]]. <pre>{{{!}} class = "wikitable" width = " 30%" ! Header 1 ! Header 2 ! Header 3 {{!}}- {{!}} Some text {{!}} align = "center {{!}} Some more text {{!}} align = "right {{!}} And even more {{!}}}</pre> Would result in: {{{!}} class = "wikitable" width = " 30%" ! Header 1 ! Header 2 ! Header 3 {{!}}- {{!}} Some text {{!}} align = "center {{!}} Some more text {{!}} align = "right {{!}} And even more {{!}}} :[[User:Jongfeli|Felipe]] ([[User talk:Jongfeli|talk]]) 08:33, 18 April 2022 (UTC) == The combobox fields are not user-friendly == When a value has been previously entered in a combobox field, the list of other possible values is not displayed. [[File:ComboboxProblemSample.jpg]] To change the value, the user must delete the old value with the Delete or Backspace keys. The user may then have the impression that it is impossible to change the value. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 08:35, 17 April 2022 (UTC) == Mandatory parameter does not work in combobox == With the last version of Page Forms 5.3.4, the mandatory condition does not apply if input type=combobox. The warning message does not appear and the user can save the form even if the field is blank. An example [https://fr.wikidebates.org/wiki/Sp%C3%A9cial:AjouterDonn%C3%A9es/Sous-arguments/Il_faut_limiter_la_libert%C3%A9_d'expression_pour_ne_pas_faire_de_tort_aux_personnes here]. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 18:57, 18 April 2022 (UTC) :This was fixed [[phab:T306363|here]]. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:15, 21 April 2022 (UTC) ::Thanks! It works. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 21:54, 21 April 2022 (UTC) == Any suggestion to troubleshoot 'autocomplete on URL'? == Hi - I believe I followed all the steps described [https://www.mediawiki.org/wiki/Extension:Page_Forms/Input_types#Autocompleting_on_outside_values at this page] to set up an external source for autocomplete. I can go to the URL and look up a value manually and the page returns a JSON object that matches what is described in the documentation. Once I am in the form, I am not getting any value using the mapping I defined in LocalSettings. Do you have tips to debug what is going on? I am not seeing any error in the browser console or in the form itself. [[User:Lalquier|Lalquier]] ([[User talk:Lalquier|talk]]) 20:17, 20 April 2022 (UTC) :One thought about it - does Page Form expect a particular Mime Type or header for the JSON content produced by the remote URL? Another possibility is an interference with a single sign on extension we are using. In any case, a way to have some kind of trace or log of what Page Form is doing with autocomplete would be helpful. [[User:Lalquier|Lalquier]] ([[User talk:Lalquier|talk]]) 22:43, 20 April 2022 (UTC) == Property parameter does not work for combobox == With the last version of Page Forms 5.3.4, property (or values from property) parameter does not work if input type=combobox. No autocompletion applies (but it does for values from category). An example [https://fr.wikidebates.org/wiki/Sp%C3%A9cial:AjouterDonn%C3%A9es/Arguments_POUR_(test)/Faut-il_instaurer_un_revenu_de_base_%3F here]. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 21:59, 21 April 2022 (UTC) :Looks like property values ​​don't like property names with an apostrophe. I took the liberty of doing a test on your wiki with a property with a "more suitable" name (Property:TestAttribut) and it worked. I advise you to rename your attributes and retest. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 08:03, 23 April 2022 (UTC) ::Thanks! Now the titles are displaying... but if they are long, the end of the title is of this kind: A la différence des ordres d'exécution pfe27252df55cf9ac6e3d1f5d512ec765. ::So, it's still not working :(. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 17:17, 24 April 2022 (UTC) :::Now it's working. I had to change the property declaration: <nowiki>[[Has type::Text]]</nowiki> to <nowiki>[[Has type::Page]]</nowiki>. :::But why? This property does not refer to pages but to text. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 17:32, 24 April 2022 (UTC) ::::Again, I took the liberty of testing on your wiki by changing the type of the page attribute to text (I reset page after my tests...). Indeed, when the value exceeds 72 characters, cryptic characters are displayed after the 40th character. A quick search of the SMW docs shows that there are indeed differences in the treatment of [https://www.semantic-mediawiki.org/wiki/Help:Type_Text Text] and [https://www.semantic-mediawiki.org/wiki/Help:Type_Page Page] types.<BR/>Can you modify the [https://www.semantic-mediawiki.org/wiki/Help:$smwgFieldTypeFeatures $smwgFieldTypeFeatures] parameter to see if the SMW_FIELDT_CHAR_LONG setting fixes the problem? --[[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 11:27, 27 April 2022 (UTC) == A concrete example of the use of the promising "values dependent on" functionality? == I feel like I'm digging up an old topic but I haven't found a clear answer to this question in the documentation of the Page Forms extension or in the talk archive. Is there an example of the implementation of the "values dependent on" feature somewhere on the web? My tests didn't give me much and despite what the [[Extension:Page Forms/Input types#Dependent autocompletion|documentation]] says, the example given (restaurant, country, city) doesn't shed any light on how this parameter works. My hidden hope is that this will overcome the current malfunction of the [[Extension:Semantic Forms Select|Semantic Forms Select]] extension. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 07:11, 28 April 2022 (UTC) :You can see an example [https://discoursedb.org/w/index.php?title=We_need_more_vaccinations,_but_is_Biden_OSHA_rule_the_way_to_get_it_done%3F&action=formedit here], using [https://discoursedb.org/wiki/Form:Item this form] - the values for "Position" are dependent on the value for "Topic". Thankfully you can modify these values even when logged out. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:58, 28 April 2022 (UTC) ::OK. Thank you for this example. I have the same type of code except that the form is not multiple and I am not using Cargo but SMW. I have a class instance that registers the City and Country properties. However the choice of country in the form does not show the city... <div style="max-height: 200px; overflow:auto; border: 1px solid black;"> '''Template:Restaurant''' <pre>* Country: [[Country::{{{Country|}}}]] * City : [[City::{{{City|}}}]] </pre> '''Form:Restaurant''' <pre>{{{info|page name=Test Values dependent on}}} {{{for template|Restaurant}}} {{{field|Country|property=Country|input type=combobox}}} {{{field|City|property=City|input type=combobox|values dependent on=Restaurant[Country]}}} {{{end template}}}</pre> '''Property:City''' and '''Property:Country''' <pre>[[Has type::Text]]</pre> '''La Tour d'Argent''' <pre>{{Restaurant |Country=France |City=Paris }}</pre> </div> [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 07:17, 29 April 2022 (UTC) :There may be a bug with the handling of "values dependent on" in SMW - it's been a long time since I tested it. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:14, 29 April 2022 (UTC) == _run table display bug == Adding <code>_run</code> onto a query string results in an odd display bug with tables. To reproduce: # Click [http://discoursedb.org/wiki/Special:RunQuery/Item_query?Item_query%5Bauthor%5D=A&Item_query%5Bsource%5D=New&_run this link] # Now click "run query" on the same page, and the table difference will be obvious. [[User:Frybread|Frybread]] ([[User talk:Frybread|talk]]) 04:48, 29 April 2022 (UTC) == Combobox - A non-numeric value encountered == I'm not sure if this is an error with my form or an error with PageForms, any ideas on how to remedy (other than not using Comboboxes)?<br> MediaWiki - 1.35.6<br> PHP - 7.4.25 (cgi-fcgi)<br> MySQL - 8.0.28-0ubuntu0.20.04.3<br> PageForms 5.4<br> ErrorException from line 99 of /home/username/website.com/w/extensions/PageForms/includes/forminputs/PF_ComboBoxInput.php: PHP Warning: A non-numeric value encountered #0 /home/username/website.com/w/extensions/PageForms/includes/forminputs/PF_ComboBoxInput.php(99): MWExceptionHandler::handleError(integer, string, string, integer, array) #1 /home/username/website.com/w/extensions/PageForms/includes/forminputs/PF_ComboBoxInput.php(196): PFComboBoxInput::getHTML(string, string, boolean, boolean, array) #2 /home/username/website.com/w/extensions/PageForms/includes/PF_FormPrinter.php(2042): PFComboBoxInput->getHtmlText() #3 /home/username/website.com/w/extensions/PageForms/includes/PF_FormPrinter.php(1408): PFFormPrinter->formFieldHTML(PFFormField, string) #4 /home/username/website.com/w/includes/StubObject.php(116): PFFormPrinter->formHTML(string, boolean, boolean, integer, string, string, NULL, boolean, boolean, boolean, array, User) #5 /home/username/website.com/w/includes/StubObject.php(142): StubObject->_call(string, array) #6 /home/username/website.com/w/extensions/PageForms/includes/PF_AutoeditAPI.php(978): StubObject->__call(string, array) #7 /home/username/website.com/w/extensions/PageForms/includes/PF_AutoeditAPI.php(129): PFAutoeditAPI->doAction() #8 /home/username/website.com/w/extensions/PageForms/specials/PF_FormEdit.php(103): PFAutoeditAPI->execute() #9 /home/username/website.com/w/extensions/PageForms/specials/PF_FormEdit.php(44): PFFormEdit->printForm(string, string, NULL) #10 /home/username/website.com/w/includes/specialpage/SpecialPage.php(600): PFFormEdit->execute(string) #11 /home/username/website.com/w/includes/specialpage/SpecialPageFactory.php(635): SpecialPage->run(string) #12 /home/username/website.com/w/includes/MediaWiki.php(307): MediaWiki\SpecialPage\SpecialPageFactory->executePath(Title, RequestContext) #13 /home/username/website.com/w/includes/MediaWiki.php(945): MediaWiki->performRequest() #14 /home/username/website.com/w/includes/MediaWiki.php(548): MediaWiki->main() #15 /home/username/website.com/w/index.php(53): MediaWiki->run() #16 /home/username/website.com/w/index.php(46): wfIndexMain() #17 {main}<br> [[User:TiltedCerebellum|TiltedCerebellum]] ([[User talk:TiltedCerebellum|talk]]) 05:10, 12 May 2022 (UTC) :I figured it out, apparently size '''must''' be set to some numeric value, but nowhere is that stated in the docs, nor does it fail gracefully, warn, or have a default. Imo there should be a default to prevent exceptions, or at the very least a warning on save. At some point we had a user change or delete the value, and it kicked this error [[User:TiltedCerebellum|TiltedCerebellum]] ([[User talk:TiltedCerebellum|talk]]) 05:20, 12 May 2022 (UTC) ::"size" doesn't have to be set, although it did lead to a PHP warning if it was set to a non-numeric value (like "50px" instead of "50"). I just checked in a fix for this. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:56, 12 May 2022 (UTC) == Card Suit Symbols in {{#queryformlink:form=|link type=button|link text=&#9824;&#9829;&#9830;&#9827; == I am creating a card game wiki and would like to have the queryformlink button text show card suit symbols (Spades/&#9824;, Hearts/&#9829;, Diamonds/&#9830;, Clubs/&#9827;). I have tried to use Unicode and HTML-codes for these symbols and also a link to an image. None of these seem to work. (PageForms 5.4, MW 1.35.2). Also I do not see any card suit icons in the OOUI set which would be an option I could live with (assuming I can figure out how to change the button icon from '> next'). Pre OOUI usage this was possible (ie. I can do this in PageForms 4.6). Am I missing something fundamental that would allow me to have this more user friendly interface? Thanks in advance, Gregg [[User:GMShimokura|GMShimokura]] ([[User talk:GMShimokura|talk]]) 02:35, 13 May 2022 (UTC) :That's too bad. I haven't tried this personally, but I can think of two potential approaches: (1) having the links be of the default text type, instead of buttons, and using CSS to make them look more like buttons; or (2) adding some JavaScript (in MediaWiki:Common.js) to change the text on the buttons, after they have already been rendered. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 03:06, 13 May 2022 (UTC) == Datetimepicker (and combobox), highly criticized by users == I get very negative feedback from my users about the datetimepicker fields. They say that these fields are not at all ergonomic compared to the old version, especially : * it is impossible to enter a whole date with the keyboard (e.g. 21/02/2022 17:04) * the current date and time is filled in by default when you start filling in the field (including minutes and seconds!), which means that you have to update everything (including minutes and seconds, which the user often has to reset to 00). * the delete button on the right of the field is not explicit. Moreover, on the Linux version of Firefox, its width is reduced to a few pixels (you have to aim right). If we also consider combobox, it is difficult to find advantages to the change to OOUI. Will a white knight fight this dragon? [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 13:59, 22 May 2022 (UTC) :I admit that the datetimepicker input has some problems (I didn't know about Firefox on Linux). I should note that there's also a "datetime" input type - which is not JavaScript-based, but it might appeal more to your users. What are the problems with "combobox"? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:16, 22 May 2022 (UTC) ::Hello Yoren, ::Thank you for your answer. The datetime type is even less ergonomic (no navigation in a calendar + a field for day, month, year, hour, minutes, seconds, PM/AM... phew!). ::In a form, a user should be able to move from field to field with the TAB key and type an entry with the keyboard if he wants. And for the date/time fields, he must be able to fill it in at once. ::For combobox, I noted: ::* [[phab:T306333|Feeds to map does not work with combobox fields]] ::* [[Extension talk:Page Forms#The combobox fields are not user-friendly|When a value has been previously entered in a combobox field, the list of other possible values is not displayed]] ::* [[phab:T305222|No image preview in an "uploadable" field]] ::[[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 16:02, 22 May 2022 (UTC) :::Okay, thanks for putting all of these in one place. Were any/all of these working when combobox was defined with jQuery UI instead of OOUI, do you know? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:48, 22 May 2022 (UTC) ::::I just tested on a jquery version : ::::* The geocoding with leaflet was not working so impossible to know if feeds to map worked with combobox fields ::::* The other possible values are displayed when a value has been previously filled in. ::::* As for OOUI, image preview does not work: at the creation of the page, no preview at all. On modification, the image previously filled in is displayed but the display is not updated if you change the file in the combobox. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 18:09, 22 May 2022 (UTC) == visualeditor in fields not working == Hi,<br /> [https://fr.dicoado.org/dico/special:version MW 1.35.6 | SMW 4.0.1 | Foreground 2.4.0 | PageForms 5.1 | VEForAll 0.4 | VisualEditor 0.1.2] <br /> I have in [https://fr.dicoado.org/dico/Formulaire:Ajouter_un_mot my form] fields that I want to be used with VEForAll to have a VisualEditor bundled in it. I used |editor=visualeditor before, but since the upgrade from 1.35.2 to 1.35.6 it broke and now the field is simply greyed out and disabled. Thus, I've to put it back to a normal text field to make it usable. Could you please help me make the form working again? Here's the configuration I have for PageForms: <syntaxhighlight lang="PHP"> $wgPageFormsLinkAllRedLinksToForms = true; $wgPageFormsHeightForMinimizingInstances = -1; </syntaxhighlight> [[User:Raphoraph|Raphoraph]] ([[User talk:Raphoraph|talk]]) 18:50, 11 June 2022 (UTC) :Okay, so tested with the Vector skin, and suddenly it worked… not only with Vector but with Foreground too. I'm a little confused. Perhaps without noticing, I cleared some cache or data, and it worked. [[User:Raphoraph|Raphoraph]] ([[User talk:Raphoraph|talk]]) 19:13, 11 June 2022 (UTC) == pf_autoedit_fail error == Switching from PF 5.21 to 5.3x, the message "Modifying <a href="pagetitle..."> failed." appears in case of an anonymous edit. It's impossible to edit a page with PF when non-logged. An autoedit error appears. Yet the #autoedit function is not used in the form. An example [https://fr.wikidebates.org/wiki/Sp%C3%A9cial:AjouterDonn%C3%A9es/R%C3%A9sum%C3%A9/Le_revenu_de_base_apporte_de_meilleures_conditions_de_vie here]. (Note the captcha: "Wikipedia" or "debats".) [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 16:03, 21 June 2022 (UTC) == How to display form uploaded image in completed page? == I was able to create a form that requires multiple inputs and allow a file upload. Once done/saved, the new page does not display or reference the uploaded file. I have also tried adjusting the field to the file reference <code><nowiki>[[File:xxxx.png|frameless|1000px]]</nowiki></code> as is the formatting I am planning to use but no images display. [[User:Coreyjohnson75|Coreyjohnson75]] ([[User talk:Coreyjohnson75|talk]]) 17:06, 24 June 2022 (UTC) :Was the file uploaded, and is its name stored in the template call on the page? If so, the problem is somewhere in the template. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:48, 24 June 2022 (UTC) ::It uploads the file but the upload pop-up window goes white/blank after the upload. I can see the file under file list. If I close the pop-up the file name is not visible on the form. [[User:Coreyjohnson75|Coreyjohnson75]] ([[User talk:Coreyjohnson75|talk]]) 18:58, 24 June 2022 (UTC) :::I'm guessing there's some kind of JavaScript error. Can you try it again, this time looking in the browser console (if you know how to do that) to see if an error occurs? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:00, 1 July 2022 (UTC) ::::I tried again and had the same results. Found this in the console from Dev Tools: ::::[[File:Console Error.png|thumb|ReferenceError]] [[User:Coreyjohnson75|Coreyjohnson75]] ([[User talk:Coreyjohnson75|talk]]) 15:14, 1 July 2022 (UTC) == Remote Autocompletion values arriving differently than Local when using values from property=xx when xx Has type::Keyword == Hi. I wanted to list a weird thing that has started happening to me recently (since January 2022) with Keyword properties. When Page Forms pulls the list of items from a keyword property for local autocomplete, they show up as they were entered.. capitalization and everything (even though internally there isn't case sensitivity to them I know)... but when it switches to remote autocompletion, suddenly everything is all lowercase. I have figured the best way to solve this is just never touch the keyword type for now, but if it were possible to keep capitalization for looks purposes and have the smw search be case insensitive (which I think was my original thought of using keyword and how it seemed to work a while ago), it'd be even better. [[User:RinaCY|RinaCY]] ([[User talk:RinaCY|talk]]) 20:09, 30 June 2022 (UTC) :I had never heard of the "Keyword" type before, but I just looked up its [https://www.semantic-mediawiki.org/wiki/Help:Type_Keyword documentation page], and it does say that Keyword values are "normalized (lowercased, removed diacritics)". So it sounds like it's local autocompletion that's doing it "wrong". Though really, maybe you should always be entering these values as all-lowercase? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:05, 1 July 2022 (UTC) ::You're likely right, I guess I just noticed how it worked at one point then once things got too large it completely changed, and now things have to be rewritten. [[User:RinaCY|RinaCY]] ([[User talk:RinaCY|talk]]) 17:42, 6 July 2022 (UTC) == _run doesn't populate default values when using #queryformlink == I have a form with a field called "Author" with "default=current user". If I access this form with #queryformlink, my username is automatically filled in the Author field, as expected. However, I still have to click "Run query" to see the results. When I add "query string=_run", the query is executed without populating the Author field. Is this a bug or is there something else I should be doing? [[User:Wulfda02|Wulfda02]] ([[User talk:Wulfda02|talk]]) 21:08, 19 July 2022 (UTC) :That does sound like a bug, yes. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:51, 22 July 2022 (UTC) == Form properties after upgrading from Semantic Forms to Page Forms. == MediaWiki - 1.35.6 PHP - 7.4.25 (cgi-fcgi) Postgresql - 10+ PageForms 5.4 Upgrading from Mediawiki 1.27; I have a Special Page query which looks for page properties, most importantly, the [[Geometry:]] property; My forms (PF_NS_FORM) are each built off a template. Each page has a relative Template page (NS_TEMPLATE) which contains the [[Has default form::]] which I go through every page with that using a script and adding {{#default_form:}} as outlined in Page Forms (https://www.mediawiki.org/wiki/Extension:Page_Forms/The_%22edit_with_form%22_tab); However, after doing this, my Form no longer displays the CategoryLinks to some of the properties, most noteably [[Geometry]] and [[DTG]] (which is a date time thing). All forms before updating the template (and running runJobs.php) query properly and show Geometry but after the template update, it no longer works. Is there another way I should be doing this? [[User:Rijvirajib|Rijvirajib]] ([[User talk:Rijvirajib|talk]]) 04:06, 22 July 2022 (UTC) :Sorry, what do you mean by "no longer displays the CategoryLinks"? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:50, 22 July 2022 (UTC) ::Thanks for getting back to me so quickly! In my form using [\[Page has default form]\], I have a property at the bottom [\[Geometry:POINT(some numbers)]\]. I want to query Page Forms form for all properties for that form, including Geometry. This works fine BEFORE I update my Page Form Template and append {{#default_form}} to the bottom so that the form itself will show "Edit with form" when viewing it. However, when I update the Form Template, the properties that I once queried to get Geometry and others like [\[Has DTG:]\] no longer display. ::The query to grab all properties for a form/template: ::<code> ::SELECT DISTINCT T1.smw_sortkey AS pname ::FROM mediawiki.smw_object_ids T1, :: mediawiki.smw_object_ids T2, :: mediawiki.smw_di_wikipage page ::WHERE page.s_id IN (SELECT smw_id :: FROM mediawiki.smw_object_ids :: WHERE smw_title IN (SELECT page_title :: FROM mediawiki.page, :: mediawiki.categorylinks :: WHERE cl_from = page_id' :: AND cl_to = 'Bridge_Assessment' :: )) :: AND T1.smw_id = page.p_id :: AND T2.smw_id = page.o_id :: ORDER BY pname; ::</code> [[User:Rijvirajib|Rijvirajib]] ([[User talk:Rijvirajib|talk]]) 15:55, 22 July 2022 (UTC) :::Sorry, I still don't understand. Are you putting properties like "Geometry" in the form, or the template? I'm guessing in the template, but if so - does this issue actually have to do with Page Forms? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 21:57, 22 July 2022 (UTC) ::::Correct, they are stored in the template. We are trying to discover all the properties used in a particular template. For example, if you create a page form based on a template there are properties generated on the newly created form for the user to populate. We need to get these properties. ::::We have been using the above database query but since moving to MW 1.35.5 (SMW 3.2.3) we have noticed the query no longer returns back the correct properties. Some are missing (Geometry, DTG, etc.). ::::Do you know of a way to get these list of page form template properties using an endpoint API (https://www.semantic-mediawiki.org/wiki/Help:API, https://www.mediawiki.org/w/api.php), direct DB query or a using the any of the classes (https://doc.wikimedia.org/mediawiki-core/master/php/annotated.html) ? [[Special:Contributions/2601:191:8400:9E0:30F4:BCF9:8D80:85B4|2601:191:8400:9E0:30F4:BCF9:8D80:85B4]] 15:20, 23 July 2022 (UTC) :::::I don't know, but this does sound like a Semantic MediaWiki, not a Page Forms, question - it seems like this issue would exist even if you were editing pages manually, not with forms. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:35, 24 July 2022 (UTC) ::::::How does PageForms know what properties to use for a category/template(s)? [[User:Ckapop|Ckapop]] ([[User talk:Ckapop|talk]]) 22:00, 27 July 2022 (UTC) :::::::Do you mean, for example, how it knows where to get the autocompletion values for some field? It parses the template page to see what SMW property (if any) is attached to each template field. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 22:47, 27 July 2022 (UTC) == Remote autocompletion when using mapping property == SMW : 4.0.1 // MW : 1.38.1 // PF : 5.4 Hello, It seems that remote autocompletion doesn't work when using mapping property. Is ther a way to active it ? Thanks ! [[User:Paul LEMPERIERE|Paul LEMPERIERE]] ([[User talk:Paul LEMPERIERE|talk]]) 19:33, 23 July 2022 (UTC) == Wrong value displayed using token input type and {{DISPLAYTITLE:...}} magic word == SMW : 4.0.1 // MW : 1.38.1 // PF : 5.4 I use the magicword <nowiki>{{DISPLAYTITLE}}</nowiki> for a page category. When i feed the list of a token input type with this category, here is what happen : - The list displayed is the original name of the page - If i search a word that must be in the alias of the page title, the results filtered are good, like if the alias thas hidden. So the alias is searchable - When i click on a result to display it, the alias appear in the box ! See here the use case : https://gifyu.com/image/SNlJ7 Is it possible to show the display title in the list of the token input ? [[User:Paul LEMPERIERE|Paul LEMPERIERE]] ([[User talk:Paul LEMPERIERE|talk]]) 20:04, 23 July 2022 (UTC) == Prevent resorting of input-type tokens (textarea with autocomplete) == Hej-hej, is it possible for extension Page Forms 5.1 (SMW 3.2.2) to prevent the resorting or rearrangemet of input-types tokens (former textarea with autocomplete)? My goal is to input words in a (semicolon separated) list but keep the order of input values ''as it was entered'' by the user. I found no possibility yet to prevent that reordering when the form is loaded—is it possible and how can it be achieved? Thank you for any help on this. -- [[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 11:48, 24 July 2022 (UTC) :You should definitely upgrade to the latest Page Forms version - I'm not sure this bug has been fixed, but I think it has. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:35, 24 July 2022 (UTC) == How do you create a category (or select an existing one) from a field value on a Page Form in MediaWiki? == I created a form to allow users to input data about scientific topics, references and categories in an organized manner. Problem is, I am unable to automatically categorize the page (by either creating a new category or using an existing one) when a user fills the form with the appropriate category information. Here is the template page from my Mediawiki site:<syntaxhighlight> <noinclude> {{#template_params:Summary (label=Topic Summary (In point form, as a numbered list. Include references between <ref></ref> tags.))|User_Category}} </noinclude><includeonly> {{#template_display:_format=sections}} [[Category:Summary Article]] [[Category:{{#arraymap:|,|@@||}}]] </includeonly> </syntaxhighlight>Here's my form code:<syntaxhighlight> <noinclude> This is the "Summary Article" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Summary Article}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> =Summary= {{{section|Summary|level=1}}} ==Category== {{{field|User_Category|level=2}}} </includeonly> </syntaxhighlight>I attempted to assign the field value to the category variable `User_Category` in order to create a category in the template page, but was unsuccessful. Any assistance would be greatly appreciated. [[Special:Contributions/114.73.149.245|114.73.149.245]] 13:28, 25 July 2022 (UTC) :You should change this line in your template: [[Category:{{#arraymap:|,|@@||}}]] ...to something more like: <pre><nowiki>[[Category:{{{User Category|}}}]]</nowiki></pre> (Assuming the user is only supposed to enter one category, not a list of them.) [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:30, 25 July 2022 (UTC) :Yeah, I made the changes, but it still doesn't work as the category information doesn't turn up on the page that is created (I only entered one category). [[Special:Contributions/114.73.149.245|114.73.149.245]] 23:21, 25 July 2022 (UTC) ::See [[Topic:Wzwhzgwbn1bv73fw]]. [[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 13:28, 26 July 2022 (UTC) == How do you transclude user input from a form into a page without the section heading? == I have a form that takes user input and creates a page. Unfortunately, the page that is created includes the section heading, which I wish to avoid. I only wish to keep the name of the page, user input and nothing else. Here is the template page from my Mediawiki site:<syntaxhighlight> <noinclude> {{#template_params:Summary (label=Topic Summary (In point form, as a numbered list. Include references between <ref></ref> tags.))|User_Category}} </noinclude><includeonly> {{#template_display:_format=sections}} [[Category:Summary Article]] </includeonly> </syntaxhighlight>Here's my form code:<syntaxhighlight> <noinclude> This is the "Summary Article" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Summary Article}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> =Summary= {{{section|Summary|level=1}}} ==Category== {{{field|User_Category|level=2}}} </includeonly> </syntaxhighlight>The page that is created has it's name on top, then the label 'Summary' as the next heading, followed by the user input. I wish to remove the 'Summary' heading altogether. How do I accomplish that? [[Special:Contributions/114.73.149.245|114.73.149.245]] 10:32, 26 July 2022 (UTC) :I think you'd have to replace the <code><nowiki>{{#template_display:_format=sections}}</nowiki></code> line and find another way to display the <code><nowiki>{{{Summary|}}}</nowiki></code> field. Maybe have it as a field rather than a section? [[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 13:33, 26 July 2022 (UTC) ::That doesn't work [[Special:Contributions/114.73.149.245|114.73.149.245]] 14:02, 26 July 2022 (UTC) :::The error I get is "EditPage does not have a context title set" [[Special:Contributions/114.73.149.245|114.73.149.245]] 14:03, 26 July 2022 (UTC) ::::Edit the page to remove the section heading <code>=Summary=</code> and the text below. Then change the form to have a field instead of a section. Then edit the template to show the summary field. (By the way it's confusing to have a PF field called Summary when wiki pages have a Summary field already.) Note that in the following I've made changes from your original code, so you might have other changes to make. ::::Form: ::::<syntaxhighlight> <noinclude> This is the "Summary Article" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Summary Article}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Summary Article}}} ==Summary== {{{field|Summary|input type=textarea}}} ==Category== {{{field|User Category|input type=tokens|list}}} </includeonly> </syntaxhighlight> ::::Template: ::::<syntaxhighlight> <noinclude> {{#template_params:Summary|User Category}} </noinclude><includeonly> {{{Summary|}}} [[Category:Summary Article]] {{#arraymap:{{{User Category|}}}|,|@@|[[Category:@@]]|}} </includeonly> </syntaxhighlight> ::::[[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 22:29, 28 July 2022 (UTC) qaiora5s4nuep91u0p33tvj8whd1jt5 5387444 5387443 2022-07-28T22:30:25Z Jonathan3 9129 /* How do you transclude user input from a form into a page without the section heading? */ wikitext text/x-wiki {{Page Forms navigation}} {{Archive box| * [[Extension talk:Page Forms/Archive 2007|2007]] * [[Extension talk:Page Forms/Archive January to March 2008|January to March 2008]] * [[Extension talk:Page Forms/Archive April to June 2008|April to June 2008]] * [[Extension talk:Page Forms/Archive July to September 2008|July to September 2008]] * [[Extension talk:Page Forms/Archive October to December 2008|October to December 2008]] * [[Extension talk:Page Forms/Archive January to April 2009|January to April 2009]] * [[Extension talk:Page Forms/Archive May to July 2009|May to July 2009]] * [[Extension talk:Page Forms/Archive August to September 2009|August to September 2009]] * [[Extension talk:Page Forms/Archive October to December 2009|October to December 2009]] * [[Extension talk:Page Forms/Archive January to February 2010|January to February 2010]] * [[Extension talk:Page Forms/Archive March to May 2010|March to May 2010]] * [[Extension talk:Page Forms/Archive June 2010|June 2010]] * [[Extension talk:Page Forms/Archive July to August 2010|July to August 2010]] * [[Extension talk:Page Forms/Archive September to October 2010|September to October 2010]] * [[Extension talk:Page Forms/Archive November 2010|November 2010]] * [[Extension talk:Page Forms/Archive December 2010|December 2010]] * [[Extension talk:Page Forms/Archive January 2011|January 2011]] * [[Extension talk:Page Forms/Archive February to March 2011|February to March 2011]] * [[Extension talk:Page Forms/Archive April 2011|April 2011]] * [[Extension talk:Page Forms/Archive May to June 2011|May to June 2011]] * [[Extension talk:Page Forms/Archive July 2011|July 2011]] * [[Extension talk:Page Forms/Archive August to September 2011|August to September 2011]] * [[Extension talk:Page Forms/Archive October to November 2011|October to November 2011]] * [[Extension talk:Page Forms/Archive December 2011|December 2011]] * [[Extension talk:Page Forms/Archive January to February 2012|January to February 2012]] * [[Extension talk:Page Forms/Archive March 2012|March 2012]] * [[Extension talk:Page Forms/Archive April to June 2012|April to June 2012]] * [[Extension talk:Page Forms/Archive July to August 2012|July to August 2012]] * [[Extension talk:Page Forms/Archive September to October 2012|September to October 2012]] * [[Extension talk:Page Forms/Archive November to December 2012|November to December 2012]] * [[Extension talk:Page Forms/Archive January to February 2013|January to February 2013]] * [[Extension talk:Page Forms/Archive March to April 2013|March to April 2013]] * [[Extension talk:Page Forms/Archive May to July 2013|May to July 2013]] * [[Extension talk:Page Forms/Archive August to September 2013|August to September 2013]] * [[Extension talk:Page Forms/Archive October to December 2013|October to December 2013]] * [[Extension talk:Page Forms/Archive January to March 2014|January to March 2014]] * [[Extension talk:Page Forms/Archive April to June 2014|April to June 2014]] * [[Extension talk:Page Forms/Archive July to August 2014|July to August 2014]] * [[Extension talk:Page Forms/Archive September to December 2014|September to December 2014]] * [[Extension talk:Page Forms/Archive January 2015|January 2015]] * [[Extension talk:Page Forms/Archive February to March 2015|February to March 2015]] * [[Extension talk:Page Forms/Archive April to May 2015|April to May 2015]] * [[Extension talk:Page Forms/Archive June to August 2015|June to August 2015]] * [[Extension talk:Page Forms/Archive September 2015|September 2015]] * [[Extension talk:Page Forms/Archive October to December 2015|October to December 2015]] * [[Extension talk:Page Forms/Archive January to March 2016|January to March 2016]] * [[Extension talk:Page Forms/Archive April to July 2016|April to July 2016]] * [[Extension talk:Page Forms/Archive August to October 2016|August to October 2016]] * [[Extension talk:Page Forms/Archive November to December 2016|November to December 2016]] * [[Extension talk:Page Forms/Archive January 2017|January 2017]] * [[Extension talk:Page Forms/Archive February to March 2017|February to March 2017]] * [[Extension talk:Page Forms/Archive April to July 2017|April to July 2017]] * [[Extension talk:Page Forms/Archive August to December 2017|August to December 2017]] * [[Extension talk:Page Forms/Archive January to February 2018|January to February 2018]] * [[Extension talk:Page Forms/Archive March to May 2018|March to May 2018]] * [[Extension talk:Page Forms/Archive June to July 2018|June to July 2018]] * [[Extension talk:Page Forms/Archive August to September 2018|August to September 2018]] * [[Extension talk:Page Forms/Archive October to December 2018|October to December 2018]] * [[Extension talk:Page Forms/Archive January to February 2019|January to February 2019]] * [[Extension talk:Page Forms/Archive March to June 2019|March to June 2019]] * [[Extension talk:Page Forms/Archive July to August 2019|July to August 2019]] * [[Extension talk:Page Forms/Archive September to December 2019|September to December 2019]] * [[Extension talk:Page Forms/Archive January to March 2020|January to March 2020]] * [[Extension talk:Page Forms/Archive April to June 2020|April to June 2020]] * [[Extension talk:Page Forms/Archive July to September 2020|July to September 2020]] * [[Extension talk:Page Forms/Archive October to December 2020|October to December 2020]] * [[Extension talk:Page Forms/Archive January to February 2021|January to February 2021]] * [[Extension talk:Page Forms/Archive March to April 2021|March to April 2021]] * [[Extension talk:Page Forms/Archive May to December 2021|May to December 2021]] * [[Extension talk:Page Forms/Archive January to March 2022|January to March 2022]] }} == [RESOLVED] No display of a jqplotchart query called from a form == MW 1.35.6 / PHP 7.4.27 / MariaDB 10.1.48 / SMW 3.2.3 / PF 5.3.4 My SearchPeople query form calls the SearchPeople template which contains the following query (which I have simplified for testing): <code><nowiki>{{#ask:[[Category:People]]|?unit|mainlabel=-|format=jqplotchart|distribution=1|charttype=pie}}</nowiki></code> The request does not succeed (a spinning logo rotates indefinitely) when I go through the form that I also simplified for testing: <code><nowiki>{{{for template|searchPeople}}}</nowiki><nowiki>{{end template}}</nowiki></code> Yet the template page does display the graphic. In a previous version of my MediaWiki system (MW 1.31, SMW 2.5.8, PF 4.3.1), this works (with exactly the same code and more complex form/template duos). PS1: To see if this changed anything, I switched the type of the form button from GET to POST by changing line 149 in PF_RunQuery.php. Nothing changed. PS2: Since the upgrade to PF 5.3.4, I also get this type of warning: <code>Notice: Uninitialized string offset: 37 in /var/www/mediawiki/extensions/PageForms/includes/PF_FormPrinter.php on line 1009</code> I can add the bug in Phabricator if necessary. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 11:09, 1 April 2022 (UTC) :Do you see any JavaScript errors, if you look in the browser console? To see a clear error message, you may need to add "&debug=true" to the URL. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:12, 1 April 2022 (UTC) ::In the meantime, I'm debugging the upgrade from SMW 3.2.3 to SMW 4.0.1. which messes up my wiki by blocking all javascript. ::I've just noticed that the jqplotchart problem and the problems related to the migration to SMW 4.0.1 are naturally solved when I remove the display errors: ::<syntaxhighlight lang="php"># ini_set( 'display_errors', 1 );</syntaxhighlight> ::Does this little # allow SMW 4.0.1 to work and thus the query form leading to a jqplot ask to succeed? I don't know and I don't care (yet). Thank you in any case Yaron for forcing me to go deeper into the debugging. --[[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 21:58, 1 April 2022 (UTC) == editor=wikieditor in a field crashes the form == MW 1.37.2 / PHP 7.4.27 / SMW 4.0.1 / PF 5.3.4 Specifying editor=wikieditor in a textarea field causes the form to crash when trying to create a new page with that form. This is the error message for a form called MyForm: <code>WikiPage constructed on a Title that cannot exist as a page: Spécial:AddData/MyForm</code> The form does not crash when modifying a previously created instance. The problem was not seen with MW1.35.4 and SMW3.2.3 [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 21:02, 2 April 2022 (UTC) :I'm using the same version of MW and PageForms. But I'm not able to see this error while creating a page. [[User:Techwizzie|Techwizzie]] ([[User talk:Techwizzie|talk]]) 02:55, 17 April 2022 (UTC) == Embedding query forms broken == All of a sudden embedding query forms does not work any longer " <code><nowiki>{{Special:RunQuery/PageQueryKeyword}}</nowiki></code> leads to <nowiki>Special:RunQuery?pfRunQueryFormName=PageQueryKeyword&PageQueryKeyword[keyword][]=foo+bar&PageQueryKeyword[keyword][is_list]=1&wpRunQuery=&pf_free_text=</nowiki> The error I am now getting: "You must specify a form name in the URL; the URL should look like "Special:RunQuery/<form name>". The form looks like this: <pre> <includeonly>{{{info|query title=Query for pages with the given keyword:}}} {{{for template|PageQueryKeyword}}} {{{field|keyword|input type=tokens|values from property=Has keyword|max values=1}}} {{{standard input|run query|label=Start search}}} {{{end template}}}</includeonly> </pre> Last time I used this about 4 weeks ago it was still working. In the meantime nothing was updated for the wiki, i.e. it is on MW 1.31.16 and PF 5.0.1. Now updating to PF 5.2.1 did not help. Any suggestions that may help to find out why it is no longer working. [[Special:Contributions/2003:F1:C725:6300:4094:E81D:9963:3FBA|2003:F1:C725:6300:4094:E81D:9963:3FBA]] 08:34, 12 April 2022 (UTC) :Embedding a query form actually works fine for me. It's strange that your URL has Special:RunQuery as (I assume) the name of the page, and not the actual page that the form is embedded in. Why is that, do you know? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 18:38, 18 April 2022 (UTC) :: Yes the URL is as posted and not containing the name of the originating page. Since the error message claims that Special:RunQuery should be part of the URL it did not realize that this could be the issue. Still, worked before and not sure why this happens all of a sudden. Now using queryformlink to provide the search though not as nice. --[[User:Marbot|Marbot]] ([[User talk:Marbot|talk]]) 07:30, 20 April 2022 (UTC) == Preload field in free text not working with <nowiki>{{#autoedit:...</nowiki> == On '''[https://gerrit.wikimedia.org/g/mediawiki/extensions/PageForms.git/+/d87af0d48d1983ed05b1c440cd500ce911c48dc8 Page Forms master]''' {| class = "wikitable" ! Product ! Version |- | MediaWiki || 1.35.5 |- | PHP || 7.4.22 (cgi-fcgi) |- | MariaDB || 10.4.11-MariaDB |- | ICU || 66.1 |- | Lua || 5.1.4 |} You can preload data for the '''[[Extension:Page_Forms/Defining_forms#The_free_text_input|free text input]]''' which works fine when used with <code><nowiki>{{#formlink:....</nowiki></code> but it does not seem to work with the <code><nowiki>{{#autoedit:...</nowiki></code> parserfunction. I tried to figure out what is going wrong but the below simple '''Form '''works fine when used with the '''formlink '''parserfunction but when used with the '''autoedit '''parserfunction the content of the '''Load autofill''' page is ignored and does not end up on the created page. <pre> <includeonly>{{{info|query form at top|onlyinclude free text}}}{{{for template|Aaaa}}} * {{{field|Equipment}}} {{{end template}}} {{{standard input|free text|input type=textarea|editor=wikieditor|rows=25|preload=Load autofill}}}</includeonly> </pre> I am not sure if this is on purpose or if there is something wrong. We only used preload for template parameters until now but we want to be able to preload the free text on a page. Thanks and regards, [[User:Jongfeli|Felipe]] ([[User talk:Jongfeli|talk]]) 12:40, 12 April 2022 (UTC) :I believe it's on purpose, although maybe it's not ideal; parameters like "preload=" and "default=" only apply when creating a new page, not when editing an existing page, and I think that holds true even when using #autoedit. If that's true, then there may be no way to modify the free text from within #autoedit, although there probably should be. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 18:33, 18 April 2022 (UTC) ::Hello Yaron, the above applies when generating a new page not an existing one with '''formlink '''or '''autoedit'''. I understand and agree (we had that discussion in the past) that it does not apply for editing existing pages. To me it seems that '''autoedit '''is not "aware" or ignores the '''standard input|free text''' field in the form when it automatically generates the new page. It only "looks" in-between the <code><nowiki>{{{for template|....</nowiki></code> and <code><nowiki>{{{end template}}}</nowiki></code> calls. [[User:Jongfeli|Felipe]] ([[User talk:Jongfeli|talk]]) 11:18, 21 April 2022 (UTC) == Table Error in textarea field == <nowiki>"|" is not allowed, except within {{...}}, [[...]], or special tags </nowiki> [[File:Pageforms5.4.3Textarea.png]] I am getting the above error. My fields are set for textarea. Not sure if cargo field matters but it is wikitext. I am using PageForms 5.3.4 and mediawiki 1.35 Thanks, Margaret [[User:Issiegainsley|Issiegainsley]] ([[User talk:Issiegainsley|talk]]) 13:58, 16 April 2022 (UTC) :The pipes are used within the template to separate the parameters with their values. Any table added to the parameter like you describe would "break" the template. You can still add tables to to a parameter but you need to replace all the pipes "|" used in the table with the magic word <code><nowiki>{{!}}</nowiki></code> . See: [[Help:Magic_words#Other]]. <pre>{{{!}} class = "wikitable" width = " 30%" ! Header 1 ! Header 2 ! Header 3 {{!}}- {{!}} Some text {{!}} align = "center {{!}} Some more text {{!}} align = "right {{!}} And even more {{!}}}</pre> Would result in: {{{!}} class = "wikitable" width = " 30%" ! Header 1 ! Header 2 ! Header 3 {{!}}- {{!}} Some text {{!}} align = "center {{!}} Some more text {{!}} align = "right {{!}} And even more {{!}}} :[[User:Jongfeli|Felipe]] ([[User talk:Jongfeli|talk]]) 08:33, 18 April 2022 (UTC) == The combobox fields are not user-friendly == When a value has been previously entered in a combobox field, the list of other possible values is not displayed. [[File:ComboboxProblemSample.jpg]] To change the value, the user must delete the old value with the Delete or Backspace keys. The user may then have the impression that it is impossible to change the value. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 08:35, 17 April 2022 (UTC) == Mandatory parameter does not work in combobox == With the last version of Page Forms 5.3.4, the mandatory condition does not apply if input type=combobox. The warning message does not appear and the user can save the form even if the field is blank. An example [https://fr.wikidebates.org/wiki/Sp%C3%A9cial:AjouterDonn%C3%A9es/Sous-arguments/Il_faut_limiter_la_libert%C3%A9_d'expression_pour_ne_pas_faire_de_tort_aux_personnes here]. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 18:57, 18 April 2022 (UTC) :This was fixed [[phab:T306363|here]]. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:15, 21 April 2022 (UTC) ::Thanks! It works. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 21:54, 21 April 2022 (UTC) == Any suggestion to troubleshoot 'autocomplete on URL'? == Hi - I believe I followed all the steps described [https://www.mediawiki.org/wiki/Extension:Page_Forms/Input_types#Autocompleting_on_outside_values at this page] to set up an external source for autocomplete. I can go to the URL and look up a value manually and the page returns a JSON object that matches what is described in the documentation. Once I am in the form, I am not getting any value using the mapping I defined in LocalSettings. Do you have tips to debug what is going on? I am not seeing any error in the browser console or in the form itself. [[User:Lalquier|Lalquier]] ([[User talk:Lalquier|talk]]) 20:17, 20 April 2022 (UTC) :One thought about it - does Page Form expect a particular Mime Type or header for the JSON content produced by the remote URL? Another possibility is an interference with a single sign on extension we are using. In any case, a way to have some kind of trace or log of what Page Form is doing with autocomplete would be helpful. [[User:Lalquier|Lalquier]] ([[User talk:Lalquier|talk]]) 22:43, 20 April 2022 (UTC) == Property parameter does not work for combobox == With the last version of Page Forms 5.3.4, property (or values from property) parameter does not work if input type=combobox. No autocompletion applies (but it does for values from category). An example [https://fr.wikidebates.org/wiki/Sp%C3%A9cial:AjouterDonn%C3%A9es/Arguments_POUR_(test)/Faut-il_instaurer_un_revenu_de_base_%3F here]. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 21:59, 21 April 2022 (UTC) :Looks like property values ​​don't like property names with an apostrophe. I took the liberty of doing a test on your wiki with a property with a "more suitable" name (Property:TestAttribut) and it worked. I advise you to rename your attributes and retest. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 08:03, 23 April 2022 (UTC) ::Thanks! Now the titles are displaying... but if they are long, the end of the title is of this kind: A la différence des ordres d'exécution pfe27252df55cf9ac6e3d1f5d512ec765. ::So, it's still not working :(. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 17:17, 24 April 2022 (UTC) :::Now it's working. I had to change the property declaration: <nowiki>[[Has type::Text]]</nowiki> to <nowiki>[[Has type::Page]]</nowiki>. :::But why? This property does not refer to pages but to text. [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 17:32, 24 April 2022 (UTC) ::::Again, I took the liberty of testing on your wiki by changing the type of the page attribute to text (I reset page after my tests...). Indeed, when the value exceeds 72 characters, cryptic characters are displayed after the 40th character. A quick search of the SMW docs shows that there are indeed differences in the treatment of [https://www.semantic-mediawiki.org/wiki/Help:Type_Text Text] and [https://www.semantic-mediawiki.org/wiki/Help:Type_Page Page] types.<BR/>Can you modify the [https://www.semantic-mediawiki.org/wiki/Help:$smwgFieldTypeFeatures $smwgFieldTypeFeatures] parameter to see if the SMW_FIELDT_CHAR_LONG setting fixes the problem? --[[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 11:27, 27 April 2022 (UTC) == A concrete example of the use of the promising "values dependent on" functionality? == I feel like I'm digging up an old topic but I haven't found a clear answer to this question in the documentation of the Page Forms extension or in the talk archive. Is there an example of the implementation of the "values dependent on" feature somewhere on the web? My tests didn't give me much and despite what the [[Extension:Page Forms/Input types#Dependent autocompletion|documentation]] says, the example given (restaurant, country, city) doesn't shed any light on how this parameter works. My hidden hope is that this will overcome the current malfunction of the [[Extension:Semantic Forms Select|Semantic Forms Select]] extension. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 07:11, 28 April 2022 (UTC) :You can see an example [https://discoursedb.org/w/index.php?title=We_need_more_vaccinations,_but_is_Biden_OSHA_rule_the_way_to_get_it_done%3F&action=formedit here], using [https://discoursedb.org/wiki/Form:Item this form] - the values for "Position" are dependent on the value for "Topic". Thankfully you can modify these values even when logged out. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:58, 28 April 2022 (UTC) ::OK. Thank you for this example. I have the same type of code except that the form is not multiple and I am not using Cargo but SMW. I have a class instance that registers the City and Country properties. However the choice of country in the form does not show the city... <div style="max-height: 200px; overflow:auto; border: 1px solid black;"> '''Template:Restaurant''' <pre>* Country: [[Country::{{{Country|}}}]] * City : [[City::{{{City|}}}]] </pre> '''Form:Restaurant''' <pre>{{{info|page name=Test Values dependent on}}} {{{for template|Restaurant}}} {{{field|Country|property=Country|input type=combobox}}} {{{field|City|property=City|input type=combobox|values dependent on=Restaurant[Country]}}} {{{end template}}}</pre> '''Property:City''' and '''Property:Country''' <pre>[[Has type::Text]]</pre> '''La Tour d'Argent''' <pre>{{Restaurant |Country=France |City=Paris }}</pre> </div> [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 07:17, 29 April 2022 (UTC) :There may be a bug with the handling of "values dependent on" in SMW - it's been a long time since I tested it. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:14, 29 April 2022 (UTC) == _run table display bug == Adding <code>_run</code> onto a query string results in an odd display bug with tables. To reproduce: # Click [http://discoursedb.org/wiki/Special:RunQuery/Item_query?Item_query%5Bauthor%5D=A&Item_query%5Bsource%5D=New&_run this link] # Now click "run query" on the same page, and the table difference will be obvious. [[User:Frybread|Frybread]] ([[User talk:Frybread|talk]]) 04:48, 29 April 2022 (UTC) == Combobox - A non-numeric value encountered == I'm not sure if this is an error with my form or an error with PageForms, any ideas on how to remedy (other than not using Comboboxes)?<br> MediaWiki - 1.35.6<br> PHP - 7.4.25 (cgi-fcgi)<br> MySQL - 8.0.28-0ubuntu0.20.04.3<br> PageForms 5.4<br> ErrorException from line 99 of /home/username/website.com/w/extensions/PageForms/includes/forminputs/PF_ComboBoxInput.php: PHP Warning: A non-numeric value encountered #0 /home/username/website.com/w/extensions/PageForms/includes/forminputs/PF_ComboBoxInput.php(99): MWExceptionHandler::handleError(integer, string, string, integer, array) #1 /home/username/website.com/w/extensions/PageForms/includes/forminputs/PF_ComboBoxInput.php(196): PFComboBoxInput::getHTML(string, string, boolean, boolean, array) #2 /home/username/website.com/w/extensions/PageForms/includes/PF_FormPrinter.php(2042): PFComboBoxInput->getHtmlText() #3 /home/username/website.com/w/extensions/PageForms/includes/PF_FormPrinter.php(1408): PFFormPrinter->formFieldHTML(PFFormField, string) #4 /home/username/website.com/w/includes/StubObject.php(116): PFFormPrinter->formHTML(string, boolean, boolean, integer, string, string, NULL, boolean, boolean, boolean, array, User) #5 /home/username/website.com/w/includes/StubObject.php(142): StubObject->_call(string, array) #6 /home/username/website.com/w/extensions/PageForms/includes/PF_AutoeditAPI.php(978): StubObject->__call(string, array) #7 /home/username/website.com/w/extensions/PageForms/includes/PF_AutoeditAPI.php(129): PFAutoeditAPI->doAction() #8 /home/username/website.com/w/extensions/PageForms/specials/PF_FormEdit.php(103): PFAutoeditAPI->execute() #9 /home/username/website.com/w/extensions/PageForms/specials/PF_FormEdit.php(44): PFFormEdit->printForm(string, string, NULL) #10 /home/username/website.com/w/includes/specialpage/SpecialPage.php(600): PFFormEdit->execute(string) #11 /home/username/website.com/w/includes/specialpage/SpecialPageFactory.php(635): SpecialPage->run(string) #12 /home/username/website.com/w/includes/MediaWiki.php(307): MediaWiki\SpecialPage\SpecialPageFactory->executePath(Title, RequestContext) #13 /home/username/website.com/w/includes/MediaWiki.php(945): MediaWiki->performRequest() #14 /home/username/website.com/w/includes/MediaWiki.php(548): MediaWiki->main() #15 /home/username/website.com/w/index.php(53): MediaWiki->run() #16 /home/username/website.com/w/index.php(46): wfIndexMain() #17 {main}<br> [[User:TiltedCerebellum|TiltedCerebellum]] ([[User talk:TiltedCerebellum|talk]]) 05:10, 12 May 2022 (UTC) :I figured it out, apparently size '''must''' be set to some numeric value, but nowhere is that stated in the docs, nor does it fail gracefully, warn, or have a default. Imo there should be a default to prevent exceptions, or at the very least a warning on save. At some point we had a user change or delete the value, and it kicked this error [[User:TiltedCerebellum|TiltedCerebellum]] ([[User talk:TiltedCerebellum|talk]]) 05:20, 12 May 2022 (UTC) ::"size" doesn't have to be set, although it did lead to a PHP warning if it was set to a non-numeric value (like "50px" instead of "50"). I just checked in a fix for this. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:56, 12 May 2022 (UTC) == Card Suit Symbols in {{#queryformlink:form=|link type=button|link text=&#9824;&#9829;&#9830;&#9827; == I am creating a card game wiki and would like to have the queryformlink button text show card suit symbols (Spades/&#9824;, Hearts/&#9829;, Diamonds/&#9830;, Clubs/&#9827;). I have tried to use Unicode and HTML-codes for these symbols and also a link to an image. None of these seem to work. (PageForms 5.4, MW 1.35.2). Also I do not see any card suit icons in the OOUI set which would be an option I could live with (assuming I can figure out how to change the button icon from '> next'). Pre OOUI usage this was possible (ie. I can do this in PageForms 4.6). Am I missing something fundamental that would allow me to have this more user friendly interface? Thanks in advance, Gregg [[User:GMShimokura|GMShimokura]] ([[User talk:GMShimokura|talk]]) 02:35, 13 May 2022 (UTC) :That's too bad. I haven't tried this personally, but I can think of two potential approaches: (1) having the links be of the default text type, instead of buttons, and using CSS to make them look more like buttons; or (2) adding some JavaScript (in MediaWiki:Common.js) to change the text on the buttons, after they have already been rendered. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 03:06, 13 May 2022 (UTC) == Datetimepicker (and combobox), highly criticized by users == I get very negative feedback from my users about the datetimepicker fields. They say that these fields are not at all ergonomic compared to the old version, especially : * it is impossible to enter a whole date with the keyboard (e.g. 21/02/2022 17:04) * the current date and time is filled in by default when you start filling in the field (including minutes and seconds!), which means that you have to update everything (including minutes and seconds, which the user often has to reset to 00). * the delete button on the right of the field is not explicit. Moreover, on the Linux version of Firefox, its width is reduced to a few pixels (you have to aim right). If we also consider combobox, it is difficult to find advantages to the change to OOUI. Will a white knight fight this dragon? [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 13:59, 22 May 2022 (UTC) :I admit that the datetimepicker input has some problems (I didn't know about Firefox on Linux). I should note that there's also a "datetime" input type - which is not JavaScript-based, but it might appeal more to your users. What are the problems with "combobox"? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:16, 22 May 2022 (UTC) ::Hello Yoren, ::Thank you for your answer. The datetime type is even less ergonomic (no navigation in a calendar + a field for day, month, year, hour, minutes, seconds, PM/AM... phew!). ::In a form, a user should be able to move from field to field with the TAB key and type an entry with the keyboard if he wants. And for the date/time fields, he must be able to fill it in at once. ::For combobox, I noted: ::* [[phab:T306333|Feeds to map does not work with combobox fields]] ::* [[Extension talk:Page Forms#The combobox fields are not user-friendly|When a value has been previously entered in a combobox field, the list of other possible values is not displayed]] ::* [[phab:T305222|No image preview in an "uploadable" field]] ::[[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 16:02, 22 May 2022 (UTC) :::Okay, thanks for putting all of these in one place. Were any/all of these working when combobox was defined with jQuery UI instead of OOUI, do you know? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:48, 22 May 2022 (UTC) ::::I just tested on a jquery version : ::::* The geocoding with leaflet was not working so impossible to know if feeds to map worked with combobox fields ::::* The other possible values are displayed when a value has been previously filled in. ::::* As for OOUI, image preview does not work: at the creation of the page, no preview at all. On modification, the image previously filled in is displayed but the display is not updated if you change the file in the combobox. [[User:Megajoule|Megajoule]] ([[User talk:Megajoule|talk]]) 18:09, 22 May 2022 (UTC) == visualeditor in fields not working == Hi,<br /> [https://fr.dicoado.org/dico/special:version MW 1.35.6 | SMW 4.0.1 | Foreground 2.4.0 | PageForms 5.1 | VEForAll 0.4 | VisualEditor 0.1.2] <br /> I have in [https://fr.dicoado.org/dico/Formulaire:Ajouter_un_mot my form] fields that I want to be used with VEForAll to have a VisualEditor bundled in it. I used |editor=visualeditor before, but since the upgrade from 1.35.2 to 1.35.6 it broke and now the field is simply greyed out and disabled. Thus, I've to put it back to a normal text field to make it usable. Could you please help me make the form working again? Here's the configuration I have for PageForms: <syntaxhighlight lang="PHP"> $wgPageFormsLinkAllRedLinksToForms = true; $wgPageFormsHeightForMinimizingInstances = -1; </syntaxhighlight> [[User:Raphoraph|Raphoraph]] ([[User talk:Raphoraph|talk]]) 18:50, 11 June 2022 (UTC) :Okay, so tested with the Vector skin, and suddenly it worked… not only with Vector but with Foreground too. I'm a little confused. Perhaps without noticing, I cleared some cache or data, and it worked. [[User:Raphoraph|Raphoraph]] ([[User talk:Raphoraph|talk]]) 19:13, 11 June 2022 (UTC) == pf_autoedit_fail error == Switching from PF 5.21 to 5.3x, the message "Modifying <a href="pagetitle..."> failed." appears in case of an anonymous edit. It's impossible to edit a page with PF when non-logged. An autoedit error appears. Yet the #autoedit function is not used in the form. An example [https://fr.wikidebates.org/wiki/Sp%C3%A9cial:AjouterDonn%C3%A9es/R%C3%A9sum%C3%A9/Le_revenu_de_base_apporte_de_meilleures_conditions_de_vie here]. (Note the captcha: "Wikipedia" or "debats".) [[User:Manu.wikidebats|Manu.wikidebats]] ([[User talk:Manu.wikidebats|talk]]) 16:03, 21 June 2022 (UTC) == How to display form uploaded image in completed page? == I was able to create a form that requires multiple inputs and allow a file upload. Once done/saved, the new page does not display or reference the uploaded file. I have also tried adjusting the field to the file reference <code><nowiki>[[File:xxxx.png|frameless|1000px]]</nowiki></code> as is the formatting I am planning to use but no images display. [[User:Coreyjohnson75|Coreyjohnson75]] ([[User talk:Coreyjohnson75|talk]]) 17:06, 24 June 2022 (UTC) :Was the file uploaded, and is its name stored in the template call on the page? If so, the problem is somewhere in the template. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:48, 24 June 2022 (UTC) ::It uploads the file but the upload pop-up window goes white/blank after the upload. I can see the file under file list. If I close the pop-up the file name is not visible on the form. [[User:Coreyjohnson75|Coreyjohnson75]] ([[User talk:Coreyjohnson75|talk]]) 18:58, 24 June 2022 (UTC) :::I'm guessing there's some kind of JavaScript error. Can you try it again, this time looking in the browser console (if you know how to do that) to see if an error occurs? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:00, 1 July 2022 (UTC) ::::I tried again and had the same results. Found this in the console from Dev Tools: ::::[[File:Console Error.png|thumb|ReferenceError]] [[User:Coreyjohnson75|Coreyjohnson75]] ([[User talk:Coreyjohnson75|talk]]) 15:14, 1 July 2022 (UTC) == Remote Autocompletion values arriving differently than Local when using values from property=xx when xx Has type::Keyword == Hi. I wanted to list a weird thing that has started happening to me recently (since January 2022) with Keyword properties. When Page Forms pulls the list of items from a keyword property for local autocomplete, they show up as they were entered.. capitalization and everything (even though internally there isn't case sensitivity to them I know)... but when it switches to remote autocompletion, suddenly everything is all lowercase. I have figured the best way to solve this is just never touch the keyword type for now, but if it were possible to keep capitalization for looks purposes and have the smw search be case insensitive (which I think was my original thought of using keyword and how it seemed to work a while ago), it'd be even better. [[User:RinaCY|RinaCY]] ([[User talk:RinaCY|talk]]) 20:09, 30 June 2022 (UTC) :I had never heard of the "Keyword" type before, but I just looked up its [https://www.semantic-mediawiki.org/wiki/Help:Type_Keyword documentation page], and it does say that Keyword values are "normalized (lowercased, removed diacritics)". So it sounds like it's local autocompletion that's doing it "wrong". Though really, maybe you should always be entering these values as all-lowercase? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:05, 1 July 2022 (UTC) ::You're likely right, I guess I just noticed how it worked at one point then once things got too large it completely changed, and now things have to be rewritten. [[User:RinaCY|RinaCY]] ([[User talk:RinaCY|talk]]) 17:42, 6 July 2022 (UTC) == _run doesn't populate default values when using #queryformlink == I have a form with a field called "Author" with "default=current user". If I access this form with #queryformlink, my username is automatically filled in the Author field, as expected. However, I still have to click "Run query" to see the results. When I add "query string=_run", the query is executed without populating the Author field. Is this a bug or is there something else I should be doing? [[User:Wulfda02|Wulfda02]] ([[User talk:Wulfda02|talk]]) 21:08, 19 July 2022 (UTC) :That does sound like a bug, yes. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:51, 22 July 2022 (UTC) == Form properties after upgrading from Semantic Forms to Page Forms. == MediaWiki - 1.35.6 PHP - 7.4.25 (cgi-fcgi) Postgresql - 10+ PageForms 5.4 Upgrading from Mediawiki 1.27; I have a Special Page query which looks for page properties, most importantly, the [[Geometry:]] property; My forms (PF_NS_FORM) are each built off a template. Each page has a relative Template page (NS_TEMPLATE) which contains the [[Has default form::]] which I go through every page with that using a script and adding {{#default_form:}} as outlined in Page Forms (https://www.mediawiki.org/wiki/Extension:Page_Forms/The_%22edit_with_form%22_tab); However, after doing this, my Form no longer displays the CategoryLinks to some of the properties, most noteably [[Geometry]] and [[DTG]] (which is a date time thing). All forms before updating the template (and running runJobs.php) query properly and show Geometry but after the template update, it no longer works. Is there another way I should be doing this? [[User:Rijvirajib|Rijvirajib]] ([[User talk:Rijvirajib|talk]]) 04:06, 22 July 2022 (UTC) :Sorry, what do you mean by "no longer displays the CategoryLinks"? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:50, 22 July 2022 (UTC) ::Thanks for getting back to me so quickly! In my form using [\[Page has default form]\], I have a property at the bottom [\[Geometry:POINT(some numbers)]\]. I want to query Page Forms form for all properties for that form, including Geometry. This works fine BEFORE I update my Page Form Template and append {{#default_form}} to the bottom so that the form itself will show "Edit with form" when viewing it. However, when I update the Form Template, the properties that I once queried to get Geometry and others like [\[Has DTG:]\] no longer display. ::The query to grab all properties for a form/template: ::<code> ::SELECT DISTINCT T1.smw_sortkey AS pname ::FROM mediawiki.smw_object_ids T1, :: mediawiki.smw_object_ids T2, :: mediawiki.smw_di_wikipage page ::WHERE page.s_id IN (SELECT smw_id :: FROM mediawiki.smw_object_ids :: WHERE smw_title IN (SELECT page_title :: FROM mediawiki.page, :: mediawiki.categorylinks :: WHERE cl_from = page_id' :: AND cl_to = 'Bridge_Assessment' :: )) :: AND T1.smw_id = page.p_id :: AND T2.smw_id = page.o_id :: ORDER BY pname; ::</code> [[User:Rijvirajib|Rijvirajib]] ([[User talk:Rijvirajib|talk]]) 15:55, 22 July 2022 (UTC) :::Sorry, I still don't understand. Are you putting properties like "Geometry" in the form, or the template? I'm guessing in the template, but if so - does this issue actually have to do with Page Forms? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 21:57, 22 July 2022 (UTC) ::::Correct, they are stored in the template. We are trying to discover all the properties used in a particular template. For example, if you create a page form based on a template there are properties generated on the newly created form for the user to populate. We need to get these properties. ::::We have been using the above database query but since moving to MW 1.35.5 (SMW 3.2.3) we have noticed the query no longer returns back the correct properties. Some are missing (Geometry, DTG, etc.). ::::Do you know of a way to get these list of page form template properties using an endpoint API (https://www.semantic-mediawiki.org/wiki/Help:API, https://www.mediawiki.org/w/api.php), direct DB query or a using the any of the classes (https://doc.wikimedia.org/mediawiki-core/master/php/annotated.html) ? [[Special:Contributions/2601:191:8400:9E0:30F4:BCF9:8D80:85B4|2601:191:8400:9E0:30F4:BCF9:8D80:85B4]] 15:20, 23 July 2022 (UTC) :::::I don't know, but this does sound like a Semantic MediaWiki, not a Page Forms, question - it seems like this issue would exist even if you were editing pages manually, not with forms. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:35, 24 July 2022 (UTC) ::::::How does PageForms know what properties to use for a category/template(s)? [[User:Ckapop|Ckapop]] ([[User talk:Ckapop|talk]]) 22:00, 27 July 2022 (UTC) :::::::Do you mean, for example, how it knows where to get the autocompletion values for some field? It parses the template page to see what SMW property (if any) is attached to each template field. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 22:47, 27 July 2022 (UTC) == Remote autocompletion when using mapping property == SMW : 4.0.1 // MW : 1.38.1 // PF : 5.4 Hello, It seems that remote autocompletion doesn't work when using mapping property. Is ther a way to active it ? Thanks ! [[User:Paul LEMPERIERE|Paul LEMPERIERE]] ([[User talk:Paul LEMPERIERE|talk]]) 19:33, 23 July 2022 (UTC) == Wrong value displayed using token input type and {{DISPLAYTITLE:...}} magic word == SMW : 4.0.1 // MW : 1.38.1 // PF : 5.4 I use the magicword <nowiki>{{DISPLAYTITLE}}</nowiki> for a page category. When i feed the list of a token input type with this category, here is what happen : - The list displayed is the original name of the page - If i search a word that must be in the alias of the page title, the results filtered are good, like if the alias thas hidden. So the alias is searchable - When i click on a result to display it, the alias appear in the box ! See here the use case : https://gifyu.com/image/SNlJ7 Is it possible to show the display title in the list of the token input ? [[User:Paul LEMPERIERE|Paul LEMPERIERE]] ([[User talk:Paul LEMPERIERE|talk]]) 20:04, 23 July 2022 (UTC) == Prevent resorting of input-type tokens (textarea with autocomplete) == Hej-hej, is it possible for extension Page Forms 5.1 (SMW 3.2.2) to prevent the resorting or rearrangemet of input-types tokens (former textarea with autocomplete)? My goal is to input words in a (semicolon separated) list but keep the order of input values ''as it was entered'' by the user. I found no possibility yet to prevent that reordering when the form is loaded—is it possible and how can it be achieved? Thank you for any help on this. -- [[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 11:48, 24 July 2022 (UTC) :You should definitely upgrade to the latest Page Forms version - I'm not sure this bug has been fixed, but I think it has. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:35, 24 July 2022 (UTC) == How do you create a category (or select an existing one) from a field value on a Page Form in MediaWiki? == I created a form to allow users to input data about scientific topics, references and categories in an organized manner. Problem is, I am unable to automatically categorize the page (by either creating a new category or using an existing one) when a user fills the form with the appropriate category information. Here is the template page from my Mediawiki site:<syntaxhighlight> <noinclude> {{#template_params:Summary (label=Topic Summary (In point form, as a numbered list. Include references between <ref></ref> tags.))|User_Category}} </noinclude><includeonly> {{#template_display:_format=sections}} [[Category:Summary Article]] [[Category:{{#arraymap:|,|@@||}}]] </includeonly> </syntaxhighlight>Here's my form code:<syntaxhighlight> <noinclude> This is the "Summary Article" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Summary Article}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> =Summary= {{{section|Summary|level=1}}} ==Category== {{{field|User_Category|level=2}}} </includeonly> </syntaxhighlight>I attempted to assign the field value to the category variable `User_Category` in order to create a category in the template page, but was unsuccessful. Any assistance would be greatly appreciated. [[Special:Contributions/114.73.149.245|114.73.149.245]] 13:28, 25 July 2022 (UTC) :You should change this line in your template: [[Category:{{#arraymap:|,|@@||}}]] ...to something more like: <pre><nowiki>[[Category:{{{User Category|}}}]]</nowiki></pre> (Assuming the user is only supposed to enter one category, not a list of them.) [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:30, 25 July 2022 (UTC) :Yeah, I made the changes, but it still doesn't work as the category information doesn't turn up on the page that is created (I only entered one category). [[Special:Contributions/114.73.149.245|114.73.149.245]] 23:21, 25 July 2022 (UTC) ::See [[Topic:Wzwhzgwbn1bv73fw]]. [[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 13:28, 26 July 2022 (UTC) == How do you transclude user input from a form into a page without the section heading? == I have a form that takes user input and creates a page. Unfortunately, the page that is created includes the section heading, which I wish to avoid. I only wish to keep the name of the page, user input and nothing else. Here is the template page from my Mediawiki site:<syntaxhighlight> <noinclude> {{#template_params:Summary (label=Topic Summary (In point form, as a numbered list. Include references between <ref></ref> tags.))|User_Category}} </noinclude><includeonly> {{#template_display:_format=sections}} [[Category:Summary Article]] </includeonly> </syntaxhighlight>Here's my form code:<syntaxhighlight> <noinclude> This is the "Summary Article" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Summary Article}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> =Summary= {{{section|Summary|level=1}}} ==Category== {{{field|User_Category|level=2}}} </includeonly> </syntaxhighlight>The page that is created has it's name on top, then the label 'Summary' as the next heading, followed by the user input. I wish to remove the 'Summary' heading altogether. How do I accomplish that? [[Special:Contributions/114.73.149.245|114.73.149.245]] 10:32, 26 July 2022 (UTC) :I think you'd have to replace the <code><nowiki>{{#template_display:_format=sections}}</nowiki></code> line and find another way to display the <code><nowiki>{{{Summary|}}}</nowiki></code> field. Maybe have it as a field rather than a section? [[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 13:33, 26 July 2022 (UTC) ::That doesn't work [[Special:Contributions/114.73.149.245|114.73.149.245]] 14:02, 26 July 2022 (UTC) :::The error I get is "EditPage does not have a context title set" [[Special:Contributions/114.73.149.245|114.73.149.245]] 14:03, 26 July 2022 (UTC) ::::Edit the page (by this I mean any content page you have created using the form) to remove the section heading <code>=Summary=</code> and the text below. Then change the form to have a field instead of a section. Then edit the template to show the summary field. (By the way it's confusing to have a PF field called Summary when wiki pages have a Summary field already.) Note that in the following I've made changes from your original code, so you might have other changes to make. ::::Form: ::::<syntaxhighlight> <noinclude> This is the "Summary Article" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Summary Article}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Summary Article}}} ==Summary== {{{field|Summary|input type=textarea}}} ==Category== {{{field|User Category|input type=tokens|list}}} </includeonly> </syntaxhighlight> ::::Template: ::::<syntaxhighlight> <noinclude> {{#template_params:Summary|User Category}} </noinclude><includeonly> {{{Summary|}}} [[Category:Summary Article]] {{#arraymap:{{{User Category|}}}|,|@@|[[Category:@@]]|}} </includeonly> </syntaxhighlight> ::::[[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 22:29, 28 July 2022 (UTC) hu7iaip47ojkt72h9tz1bvy3fpo0eo0 Installation/vi 0 15179 5387802 1147552 2022-07-29T09:25:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Download/zh 0 15319 5386447 5375982 2022-07-28T14:08:13Z 103.173.255.162 wikitext text/x-wiki <languages/> {{InstallationNav}} == 最新版本 == {{DownloadMediaWiki}} === 从命令行下载 === <div lang="en" dir="ltr" class="mw-content-ltr"> To download MediaWiki {{MW stable release number}} in a terminal on a Linux machine using [[w:wget|wget]], use one of the following commands: </div> <code class="mw-code mw-highlight plainlinks" style="display:block"><!-- -->wget https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz </code> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, using [[w:cURL|cURL]]:</span> <code class="mw-code mw-highlight plainlinks" style="display:block"><!-- -->curl -O https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz </code> === 从Git下载(开发者) === 活跃的MediaWiki开发者应该[[Special:MyLanguage/Download from Git|从Git下载]],以获得MediaWiki软件的最新版本。 Git仓库有软件的早期版本,所以您可以切换("check out")到某个特定的版本。 <span lang="en" dir="ltr" class="mw-content-ltr">Developers downloading from Git will also need to manually install dependencies via {{ll|Composer}}.</span> === 签名 === {{void|1= PLEASE DO NOT REMOVE THE FOLLOWING TEXT TO PRESERVE THE CORRESPONDING TRANSLATIONS FOR FUTURE USE. * 旧版 * 长期支持版本 }} {{NoteTA|G1=IT}} * GPG签名(可在[[w:zh:GnuPG|GNU Privacy Guard]]中使用,以验证您的下载): ** [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz.sig|MediaWiki {{MW stable release number}}]] - 稳定版<!-- -->{{void|1= ** [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz.sig|MediaWiki {{MW stable release number}}]] - 稳定版,当前长期支持版本(LTS) }} ** [[download:mediawiki/{{MW lts branch number}}/mediawiki-{{MW lts release number}}.tar.gz.sig|MediaWiki {{MW lts release number}}]] - 当前长期支持版本(LTS)<!-- -->{{void|1= ** [[download:mediawiki/{{MW legacy branch number}}/mediawiki-{{MW legacy release number}}.tar.gz.sig|MediaWiki {{MW legacy release number}}]] - 仍受支持 ** [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz.sig|MediaWiki {{MW legacy lts release number}}]] - 长期支援(LTS) ** [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz.sig|MediaWiki {{MW legacy lts release number}}]] - 仍受支持的长期支持版本(LTS) }} * <span class="plainlinks">[https://www.mediawiki.org/keys/keys.html GPG密钥]</span> {{#if:{{#invoke:String|match|{{MW stable release number}}|^%d+%.%d+%.0$|nomatch=}}||<nowiki/> * [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.patch.gz|MediaWiki {{MW stable release number}}的更改,不包含i18n]] (标准差异)<!-- -->{{void|1= * [[download:mediawiki/{{MW stable branch number}}/mediawiki-i18n-{{MW stable release number}}.patch.gz|MediaWiki {{MW stable release number}} i18n changes]] (unified diff) }}<!--void--> }}<!--#if--> === 非手动安装 === <span class="mw-translate-fuzzy">部份使用者可能偏好跳过手动安装,而使用已预先整合好的MediaWiki[[Software bundles/zh|套装软件]]或[[hosting services|托管服务]]。部份[[w:zh:Linux发行版|Linux发行版]](例如Debian、Ubuntu、Fedora和Gentoo)的-{;zh-hans:仓库;zh-hant:储存库}-提供了MediaWiki软件包,它们的更新频率和扩展支持各有不同。</span> <span lang="en" dir="ltr" class="mw-content-ltr">Repositories of some [[w:Linux distribution|Linux distributions]] also increasingly offer packages for MediaWiki, with different degrees of frequency and extensions coverage (e.g. Debian, Ubuntu, Fedora, Gentoo).</span> == 接下来该做什么? == [[mail:mediawiki-announce|订阅我们的发行公告-{zh-hans:邮件列表;zh-hant:邮递清单}-]] 永不错过新版本,保证您的服务器安全! == 旧版本 == 若您对MediaWiki进行了大量修改,可能会在应用最新的官方变更或更新时遇到困难。为了对这类使用者提供支持,我们会对旧版本提供至少一年的维护,对长期支持版本提供最多三年的维护。 * [[download:mediawiki/{{MW legacy branch number}}/mediawiki-{{MW legacy release number}}.tar.gz|下载旧版MediaWiki ({{MW legacy release number}})]] <!-- * [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz|下载旧的LTS版MediaWiki ({{MW legacy lts release number}})]] --> == 开发版本 == 若您想使用最新的开发版本(例如alpha版),您可以下载{{MW alpha branch link}}或者[[Special:MyLanguage/Download from Git|从Git下载]]。 您也可以通过Git下载''整个-{zh-hans:仓库;zh-hant:储存库}-''(大约528MiB) <syntaxhighlight lang="bash">git clone https://gerrit.wikimedia.org/r/mediawiki/core.git</syntaxhighlight> 或''只下载最新的修订版本''(大约85MiB;此操作通常被称作“浅克隆”(''shallow clone'')——更省时间、下载量更小)。<ref> 使用「git pull」升级您的浅克隆(''shallow clone'')可能会造成引用问题,新修订会引用其他未下载至您系统的旧修订档案。在这种情况下,您只需额外下载一些内容——通过增加深度值——或者下载之后的全部修订版本。重新制作浅克隆也可解决此问题。 </ref> <syntaxhighlight lang="bash"> git clone --depth 1 https://gerrit.wikimedia.org/r/mediawiki/core.git </syntaxhighlight> 您也可以用您的浏览器来查看{{git file|action=tree|project=mediawiki/core|branch=master|text=最新的原始码}}。 == 远古版本 == 您可以在[[download:mediawiki/|MediaWiki下载记录]]中找到所有版本MediaWiki的tarball文件(带有扩展<code>''*''.tar.gz</code>),最早可追溯至2005年3月。 <div class="plainlinks"> 要浏览所有版本(包括远古版本),请查看[[Special:MyLanguage/Gerrit|Git]]-{zh-hans:仓库;zh-hant:储存库}-的[https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+refs 标签]。 </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Footnotes == </div> <references /> [[Category:MediaWiki Introduction{{#translation:}}|{{PAGENAME}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] tkftpuqc6gvb5n3ll4ih6848nyecynf Installation/yue 0 16948 5387803 1378813 2022-07-29T09:25:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/yue]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/yue]] ro85k36xvrojv0ws1m4zevk4n3e78do Manual:Installation guide 100 16959 5386631 5384736 2022-07-28T17:14:09Z Pppery 5901069 Removed redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki{{subst:User:pppery/s}}#translation:}}]]<translate></translate> jmomrv0qywwpucerhdp8j4zopo1ejqo 5386632 5386631 2022-07-28T17:14:19Z Pppery 5901069 Marked this version for translation wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki{{subst:#translation:}}]]<translate></translate> 75dncde1l9jjxpil4fybg5av9eey3lz 5386678 5386632 2022-07-28T17:15:23Z Pppery 5901069 Reverted edits by [[Special:Contribs/Pppery|Pppery]] ([[User talk:Pppery|talk]]) to last version by AKlapper (WMF) wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Combating spam/ja 100 17130 5387478 5330473 2022-07-28T22:40:19Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} 現在のすべての動的Webサイトと同様に、wikiは製品やWebサイトを宣伝したいスパマーの共通のターゲットです。 MediaWikiには、[[Special:MyLanguage/Manual:Combating vandalism|一般的な破壊行為に対抗する]]ために設計された多くの機能があります。 このページでは、[[m:Wiki spam|ウィキスパム]]を具体的に扱います。 == 概要 == ウィキスパムと戦うために使用される一般的なツールは、通常次のカテゴリに分類されます。 * 編集、外部リンクの追加、新規ユーザー作成など、特定の操作でログインやCAPTCHAを要求する * ブラックリストに登録された既知のIPアドレスまたは公開プロキシを実行しているIPからの編集をブロックする * 特定の不要なキーワードや外部リンクを追加する編集をブロックする * スパムロボットが一般的に使用する特定のユーザー名とページのタイトルパターンをブロックする * 新規または匿名利用者による、頻繁にターゲットとされる特定のページへの編集をブロックする * 新規利用者または匿名利用者に制限を課しながら、既知の優れた編集者 (管理者、通常の投稿者など) をホワイトリストに登録する * 最近禁止されたスパムボットからの投稿のクリーンアップスクリプトまたは一括削除({{ll|Extension:Nuke}}) <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> これらの機能の多くはデフォルトでは有効になっていません。 <span lang="en" dir="ltr" class="mw-content-ltr">If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</span> <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It helps to raise the bar a little.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> 定期的に「{{int|recentchanges}}」([[Special:RecentChanges]]) を確認することが効果的です。 ==最初に試すべき最も素早い解決策== スパムとの闘いはそれほど難しくありません。 スパムを迅速かつ大幅に削減したい場合は、まずこれらのいくつかの手順を試してください。 * [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]]拡張機能をインストールして、既知のスパマーIPをブロックします。 * 基本的な破壊行為対策拡張機能、特に{{ll|Extension:ConfirmEdit}}をインストールし設定します(既に[[Special:MyLanguage/Download|最新公開版]]に同梱されています)。 * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|QuestyCaptchaを設定]]し、必要があればウィキの[[Special:MyLanguage/Extension:ConfirmEdit#Configuration|初期設定を変更]]してください。 * {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}を有効化すると、編集やアカウント作成など特定の操作において、プロキシを開いたり、ノードやVPNを終了したりするのを防ぐことができます。 <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> ==スパム対策の基本== {{anchor|CAPTCHA}} ===CAPTCHA=== 自動的な投稿を除外する最も一般的な方法の1つは、機械にとって困難なタスクをユーザに解決するように依頼することにより、人間を自動システムと区別しようとするシステムである[[:ja:CAPTCHA|CAPTCHA]]を使用することです。 MediaWiki の {{ll|Extension:ConfirmEdit|ConfirmEdit}} 拡張機能は、以下を含む多くの操作で引き起こされる拡張可能な[[CAPTCHA]]フレームワークを提供します * すべての編集 * 新しい/カテゴリ分けされていない外部リンクを追加する編集 * 利用者登録 <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> 公開ウィキにConfirmEditをインストールするウィキ管理者は、拡張機能に含まれるCAPTCHAモジュールの1つを使用することが推奨されます(合計5つあります)。 <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Individual page protection=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === Abuse filter === <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> === オープンプロキシ === <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> === Apacheの構成の変更 === <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> ''外部リンク''に MediaWiki がサポートしないその他のツールをまとめました。 ==その他のアイデア== <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> ==関連項目== *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === 拡張機能 === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} ====インストーラにバンドルされているもの==== <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === 設定 === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} === 外部リンク === * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] 1bcwlui8oyq33p08j66t08y24s2tw90 Manual:Installation/pt 100 17703 5387813 297097 2022-07-29T09:27:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/pt]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pt]] hm3bwmhq55v0f70dk8b7yp6vzij4nt5 Download/cs 0 18151 5386449 5375910 2022-07-28T14:09:02Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{InstallationNav}} == Nejnovější verze == {{DownloadMediaWiki}} === Stažení pomocí příkazového řádku === Chcete-li stáhnout MediaWiki {{MW stable release number}} do terminálu na počítači se systémem Linux pomocí [[w:wget|wget]], použijte jeden z následujících příkazů: <code class="mw-code mw-highlight plainlinks" style="display:block"><!-- -->wget https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz </code> Jinak použitím [[w:cURL|cURL]]: <code class="mw-code mw-highlight plainlinks" style="display:block"><!-- -->curl -O https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz </code> === Stažení z Gitu (pro vývojáře) === Aktivní vývojáři MediaWiki by si měli stáhnout nejnovější verzi MediaWiki [[Special:MyLanguage/Download from Git|pomocí Gitu]]. Repozitář obsahuje i starší verze softwaru, takže je možné se přepnout ("vycheckoutovat si") konkrétní verzi. Vývojáři, kteří stahují z Gitu, budou také muset ručně nainstalovat závislosti prostřednictvím {{ll|Composer}}. === Stahování podpisů === {{void|1= PLEASE DO NOT REMOVE THE FOLLOWING TEXT TO PRESERVE THE CORRESPONDING TRANSLATIONS FOR FUTURE USE. * starší * LTS }} * Bezpečnostní podpis, kterým si můžete stažené soubory ověřit pomocí programu [[:cs:GNU Privacy Guard|GNU Privacy Guard]]: ** [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz.sig|MediaWiki {{MW stable release number}}]] - stabilní<!-- -->{{void|1= ** [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz.sig|MediaWiki {{MW stable release number}}]] - stabilní, současná dlouhodobá podpora (LTS) }} ** [[download:mediawiki/{{MW lts branch number}}/mediawiki-{{MW lts release number}}.tar.gz.sig|MediaWiki {{MW lts release number}}]] - aktuální dlouhodobá podpora (LTS)<!-- -->{{void|1= ** [[download:mediawiki/{{MW legacy branch number}}/mediawiki-{{MW legacy release number}}.tar.gz.sig|MediaWiki {{MW legacy release number}}]] - podpora starších verzí ** [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz.sig|MediaWiki {{MW legacy lts release number}}]] - dlouhodobá podpora (LTS) ** [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz.sig|MediaWiki {{MW legacy lts release number}}]] - dlouhodobá podpora starších verzí (LTS) }} * <span class="plainlinks">[https://www.mediawiki.org/keys/keys.html Klíče do GPG]</span> {{#if:{{#invoke:String|match|{{MW stable release number}}|^%d+%.%d+%.0$|nomatch=}}||<nowiki/> * [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.patch.gz|Změny v MediaWiki {{MW stable release number}} kromě překladů]] (unifikovaný diff (jednotný rozdíl))<!-- -->{{void|1= * [[download:mediawiki/{{MW stable branch number}}/mediawiki-i18n-{{MW stable release number}}.patch.gz|MediaWiki {{MW stable release number}} i18n changes]] (unified diff) }}<!--void--> }}<!--#if--> === Alternativy k ruční instalaci === Někteří uživatelé mohou raději přeskočit ruční instalaci pomocí předem integrovaného [[Special:MyLanguage/Software bundles|softwarového zařízení]] nebo [[Special:MyLanguage/Hosting services|hostingových služeb]] MediaWiki. <span lang="en" dir="ltr" class="mw-content-ltr">Repositories of some [[w:Linux distribution|Linux distributions]] also increasingly offer packages for MediaWiki, with different degrees of frequency and extensions coverage (e.g. Debian, Ubuntu, Fedora, Gentoo).</span> == Co dál? == [[mail:mediawiki-announce|Přihlaste se k odběru našich oznámení o nových verzích]] Sledujte nové verze a udržujte svůj server bezpečný! == Starší verze == Pokud jste si instalaci MediaWiki výrazně upravili, může být začlenění nejnovějších oficiálních změn v MediaWiki náročné. Pro takové uživatele vždy zhruba rok udržujeme starší verzi našeho softwaru a až tři roky verze s dlouhodobou podporou (LTS). * [[download:mediawiki/{{MW legacy branch number}}/mediawiki-{{MW legacy release number}}.tar.gz|Stáhnout starou verzi MediaWiki ({{MW legacy release number}})]] <!-- * [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz|Stáhnout starou LTS verzi MediaWiki ({{MW legacy lts release number}})]] --> == Vývojová verze == Pokud chcete provozovat poslední vývojovou (''např.'' alfa) verzi, můžete si ji stáhnout jako balíček {{MW alpha branch link}} nebo přes [[Special:MyLanguage/Download from Git|Git]]. Z Gitu si můžete stáhnout buď ''kompletní repozitář'' (cca 528 MiB) <syntaxhighlight lang="bash">git clone https://gerrit.wikimedia.org/r/mediawiki/core.git</syntaxhighlight> nebo ''jen jeho nejnovější revizi'' (cca 85 MiB; tomu se často říká ''"mělký klon"'': je rychlejší a menší).<ref> To však může způsobit potíže s odkazy, pokud později použijete k aktualizaci ''mělkého klonu'' příkaz "git pull" a novější revize odkazuje na starší revize, které jste si dosud nestáhli. V takovém případě si toho můžete později stáhnout více – zvýšit hloubku – nebo všechno. Nebo vyrobit mělký klon úplně znovu. </ref> <syntaxhighlight lang="bash"> git clone --depth 1 https://gerrit.wikimedia.org/r/mediawiki/core.git </syntaxhighlight> {{git file|action=tree|project=mediawiki/core|branch=master|text=Aktuální zdrojový kód}} si také můžete prohlédnout přímo v prohlížeči. == Staré verze == Balíčky (s příponou <code>''*''.tar.gz</code>) všech verzí MediaWiki od března 2005 (nejstarší je MediaWiki 1.3.11) najdete v [[download:mediawiki/|našem archivu]]. <div class="plainlinks"> Všechny verze (včetně těch ještě starších) si můžete procházet jako [https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+refs tags] v [[Special:MyLanguage/Gerrit|Gitu]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Footnotes == </div> <references /> [[Category:MediaWiki Introduction{{#translation:}}|{{PAGENAME}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] rm2y3prgsbrfvlpykrvbuv7l6u3s026 5386451 5386449 2022-07-28T14:11:12Z ENeRZet 17359278 Created page with "Repozitáře některých [[w:Linux distribution|Linuxových distribucí]] také stále častěji nabízejí balíčky pro MediaWiki s různým stupněm pokrytí frekvence a rozšíření (např. Debian, Ubuntu, Fedora, Gentoo)." wikitext text/x-wiki <languages/> {{InstallationNav}} == Nejnovější verze == {{DownloadMediaWiki}} === Stažení pomocí příkazového řádku === Chcete-li stáhnout MediaWiki {{MW stable release number}} do terminálu na počítači se systémem Linux pomocí [[w:wget|wget]], použijte jeden z následujících příkazů: <code class="mw-code mw-highlight plainlinks" style="display:block"><!-- -->wget https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz </code> Jinak použitím [[w:cURL|cURL]]: <code class="mw-code mw-highlight plainlinks" style="display:block"><!-- -->curl -O https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz </code> === Stažení z Gitu (pro vývojáře) === Aktivní vývojáři MediaWiki by si měli stáhnout nejnovější verzi MediaWiki [[Special:MyLanguage/Download from Git|pomocí Gitu]]. Repozitář obsahuje i starší verze softwaru, takže je možné se přepnout ("vycheckoutovat si") konkrétní verzi. Vývojáři, kteří stahují z Gitu, budou také muset ručně nainstalovat závislosti prostřednictvím {{ll|Composer}}. === Stahování podpisů === {{void|1= PLEASE DO NOT REMOVE THE FOLLOWING TEXT TO PRESERVE THE CORRESPONDING TRANSLATIONS FOR FUTURE USE. * starší * LTS }} * Bezpečnostní podpis, kterým si můžete stažené soubory ověřit pomocí programu [[:cs:GNU Privacy Guard|GNU Privacy Guard]]: ** [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz.sig|MediaWiki {{MW stable release number}}]] - stabilní<!-- -->{{void|1= ** [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz.sig|MediaWiki {{MW stable release number}}]] - stabilní, současná dlouhodobá podpora (LTS) }} ** [[download:mediawiki/{{MW lts branch number}}/mediawiki-{{MW lts release number}}.tar.gz.sig|MediaWiki {{MW lts release number}}]] - aktuální dlouhodobá podpora (LTS)<!-- -->{{void|1= ** [[download:mediawiki/{{MW legacy branch number}}/mediawiki-{{MW legacy release number}}.tar.gz.sig|MediaWiki {{MW legacy release number}}]] - podpora starších verzí ** [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz.sig|MediaWiki {{MW legacy lts release number}}]] - dlouhodobá podpora (LTS) ** [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz.sig|MediaWiki {{MW legacy lts release number}}]] - dlouhodobá podpora starších verzí (LTS) }} * <span class="plainlinks">[https://www.mediawiki.org/keys/keys.html Klíče do GPG]</span> {{#if:{{#invoke:String|match|{{MW stable release number}}|^%d+%.%d+%.0$|nomatch=}}||<nowiki/> * [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.patch.gz|Změny v MediaWiki {{MW stable release number}} kromě překladů]] (unifikovaný diff (jednotný rozdíl))<!-- -->{{void|1= * [[download:mediawiki/{{MW stable branch number}}/mediawiki-i18n-{{MW stable release number}}.patch.gz|MediaWiki {{MW stable release number}} i18n changes]] (unified diff) }}<!--void--> }}<!--#if--> === Alternativy k ruční instalaci === Někteří uživatelé mohou raději přeskočit ruční instalaci pomocí předem integrovaného [[Special:MyLanguage/Software bundles|softwarového zařízení]] nebo [[Special:MyLanguage/Hosting services|hostingových služeb]] MediaWiki. Repozitáře některých [[w:Linux distribution|Linuxových distribucí]] také stále častěji nabízejí balíčky pro MediaWiki s různým stupněm pokrytí frekvence a rozšíření (např. Debian, Ubuntu, Fedora, Gentoo). == Co dál? == [[mail:mediawiki-announce|Přihlaste se k odběru našich oznámení o nových verzích]] Sledujte nové verze a udržujte svůj server bezpečný! == Starší verze == Pokud jste si instalaci MediaWiki výrazně upravili, může být začlenění nejnovějších oficiálních změn v MediaWiki náročné. Pro takové uživatele vždy zhruba rok udržujeme starší verzi našeho softwaru a až tři roky verze s dlouhodobou podporou (LTS). * [[download:mediawiki/{{MW legacy branch number}}/mediawiki-{{MW legacy release number}}.tar.gz|Stáhnout starou verzi MediaWiki ({{MW legacy release number}})]] <!-- * [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz|Stáhnout starou LTS verzi MediaWiki ({{MW legacy lts release number}})]] --> == Vývojová verze == Pokud chcete provozovat poslední vývojovou (''např.'' alfa) verzi, můžete si ji stáhnout jako balíček {{MW alpha branch link}} nebo přes [[Special:MyLanguage/Download from Git|Git]]. Z Gitu si můžete stáhnout buď ''kompletní repozitář'' (cca 528 MiB) <syntaxhighlight lang="bash">git clone https://gerrit.wikimedia.org/r/mediawiki/core.git</syntaxhighlight> nebo ''jen jeho nejnovější revizi'' (cca 85 MiB; tomu se často říká ''"mělký klon"'': je rychlejší a menší).<ref> To však může způsobit potíže s odkazy, pokud později použijete k aktualizaci ''mělkého klonu'' příkaz "git pull" a novější revize odkazuje na starší revize, které jste si dosud nestáhli. V takovém případě si toho můžete později stáhnout více – zvýšit hloubku – nebo všechno. Nebo vyrobit mělký klon úplně znovu. </ref> <syntaxhighlight lang="bash"> git clone --depth 1 https://gerrit.wikimedia.org/r/mediawiki/core.git </syntaxhighlight> {{git file|action=tree|project=mediawiki/core|branch=master|text=Aktuální zdrojový kód}} si také můžete prohlédnout přímo v prohlížeči. == Staré verze == Balíčky (s příponou <code>''*''.tar.gz</code>) všech verzí MediaWiki od března 2005 (nejstarší je MediaWiki 1.3.11) najdete v [[download:mediawiki/|našem archivu]]. <div class="plainlinks"> Všechny verze (včetně těch ještě starších) si můžete procházet jako [https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+refs tags] v [[Special:MyLanguage/Gerrit|Gitu]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Footnotes == </div> <references /> [[Category:MediaWiki Introduction{{#translation:}}|{{PAGENAME}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] 4ycc3sgl3clhtm0kaas1fixmf1e0x3j 5386453 5386451 2022-07-28T14:11:26Z ENeRZet 17359278 Created page with "== Poznámky pod čarou ==" wikitext text/x-wiki <languages/> {{InstallationNav}} == Nejnovější verze == {{DownloadMediaWiki}} === Stažení pomocí příkazového řádku === Chcete-li stáhnout MediaWiki {{MW stable release number}} do terminálu na počítači se systémem Linux pomocí [[w:wget|wget]], použijte jeden z následujících příkazů: <code class="mw-code mw-highlight plainlinks" style="display:block"><!-- -->wget https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz </code> Jinak použitím [[w:cURL|cURL]]: <code class="mw-code mw-highlight plainlinks" style="display:block"><!-- -->curl -O https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz </code> === Stažení z Gitu (pro vývojáře) === Aktivní vývojáři MediaWiki by si měli stáhnout nejnovější verzi MediaWiki [[Special:MyLanguage/Download from Git|pomocí Gitu]]. Repozitář obsahuje i starší verze softwaru, takže je možné se přepnout ("vycheckoutovat si") konkrétní verzi. Vývojáři, kteří stahují z Gitu, budou také muset ručně nainstalovat závislosti prostřednictvím {{ll|Composer}}. === Stahování podpisů === {{void|1= PLEASE DO NOT REMOVE THE FOLLOWING TEXT TO PRESERVE THE CORRESPONDING TRANSLATIONS FOR FUTURE USE. * starší * LTS }} * Bezpečnostní podpis, kterým si můžete stažené soubory ověřit pomocí programu [[:cs:GNU Privacy Guard|GNU Privacy Guard]]: ** [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz.sig|MediaWiki {{MW stable release number}}]] - stabilní<!-- -->{{void|1= ** [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz.sig|MediaWiki {{MW stable release number}}]] - stabilní, současná dlouhodobá podpora (LTS) }} ** [[download:mediawiki/{{MW lts branch number}}/mediawiki-{{MW lts release number}}.tar.gz.sig|MediaWiki {{MW lts release number}}]] - aktuální dlouhodobá podpora (LTS)<!-- -->{{void|1= ** [[download:mediawiki/{{MW legacy branch number}}/mediawiki-{{MW legacy release number}}.tar.gz.sig|MediaWiki {{MW legacy release number}}]] - podpora starších verzí ** [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz.sig|MediaWiki {{MW legacy lts release number}}]] - dlouhodobá podpora (LTS) ** [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz.sig|MediaWiki {{MW legacy lts release number}}]] - dlouhodobá podpora starších verzí (LTS) }} * <span class="plainlinks">[https://www.mediawiki.org/keys/keys.html Klíče do GPG]</span> {{#if:{{#invoke:String|match|{{MW stable release number}}|^%d+%.%d+%.0$|nomatch=}}||<nowiki/> * [[download:mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.patch.gz|Změny v MediaWiki {{MW stable release number}} kromě překladů]] (unifikovaný diff (jednotný rozdíl))<!-- -->{{void|1= * [[download:mediawiki/{{MW stable branch number}}/mediawiki-i18n-{{MW stable release number}}.patch.gz|MediaWiki {{MW stable release number}} i18n changes]] (unified diff) }}<!--void--> }}<!--#if--> === Alternativy k ruční instalaci === Někteří uživatelé mohou raději přeskočit ruční instalaci pomocí předem integrovaného [[Special:MyLanguage/Software bundles|softwarového zařízení]] nebo [[Special:MyLanguage/Hosting services|hostingových služeb]] MediaWiki. Repozitáře některých [[w:Linux distribution|Linuxových distribucí]] také stále častěji nabízejí balíčky pro MediaWiki s různým stupněm pokrytí frekvence a rozšíření (např. Debian, Ubuntu, Fedora, Gentoo). == Co dál? == [[mail:mediawiki-announce|Přihlaste se k odběru našich oznámení o nových verzích]] Sledujte nové verze a udržujte svůj server bezpečný! == Starší verze == Pokud jste si instalaci MediaWiki výrazně upravili, může být začlenění nejnovějších oficiálních změn v MediaWiki náročné. Pro takové uživatele vždy zhruba rok udržujeme starší verzi našeho softwaru a až tři roky verze s dlouhodobou podporou (LTS). * [[download:mediawiki/{{MW legacy branch number}}/mediawiki-{{MW legacy release number}}.tar.gz|Stáhnout starou verzi MediaWiki ({{MW legacy release number}})]] <!-- * [[download:mediawiki/{{MW legacy lts branch number}}/mediawiki-{{MW legacy lts release number}}.tar.gz|Stáhnout starou LTS verzi MediaWiki ({{MW legacy lts release number}})]] --> == Vývojová verze == Pokud chcete provozovat poslední vývojovou (''např.'' alfa) verzi, můžete si ji stáhnout jako balíček {{MW alpha branch link}} nebo přes [[Special:MyLanguage/Download from Git|Git]]. Z Gitu si můžete stáhnout buď ''kompletní repozitář'' (cca 528 MiB) <syntaxhighlight lang="bash">git clone https://gerrit.wikimedia.org/r/mediawiki/core.git</syntaxhighlight> nebo ''jen jeho nejnovější revizi'' (cca 85 MiB; tomu se často říká ''"mělký klon"'': je rychlejší a menší).<ref> To však může způsobit potíže s odkazy, pokud později použijete k aktualizaci ''mělkého klonu'' příkaz "git pull" a novější revize odkazuje na starší revize, které jste si dosud nestáhli. V takovém případě si toho můžete později stáhnout více – zvýšit hloubku – nebo všechno. Nebo vyrobit mělký klon úplně znovu. </ref> <syntaxhighlight lang="bash"> git clone --depth 1 https://gerrit.wikimedia.org/r/mediawiki/core.git </syntaxhighlight> {{git file|action=tree|project=mediawiki/core|branch=master|text=Aktuální zdrojový kód}} si také můžete prohlédnout přímo v prohlížeči. == Staré verze == Balíčky (s příponou <code>''*''.tar.gz</code>) všech verzí MediaWiki od března 2005 (nejstarší je MediaWiki 1.3.11) najdete v [[download:mediawiki/|našem archivu]]. <div class="plainlinks"> Všechny verze (včetně těch ještě starších) si můžete procházet jako [https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+refs tags] v [[Special:MyLanguage/Gerrit|Gitu]]. </div> == Poznámky pod čarou == <references /> [[Category:MediaWiki Introduction{{#translation:}}|{{PAGENAME}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] 8j0iykrg86naluagqdpzdjybnxsgu1l Manual:Installing MediaWiki 100 18173 5387487 5384922 2022-07-28T22:44:55Z Shirayuki 472859 wikitext text/x-wiki <languages/> {{InstallationNav}} <translate> <!--T:146--> This page covers all steps to manually install and configure MediaWiki. </translate> <translate><!--T:3--> MediaWiki can be difficult to install if you do not have any experience with Apache (web server software), PHP and MySQL/MariaDB (database).</translate> <translate><!--T:147--> The [[<tvar name=1>#Appendices</tvar>|Appendices]] section below offers [[<tvar name=2>#Alternatives to manual installation</tvar>|easier alternatives to manual installation]].</translate> <translate> <!--T:148--> The [[<tvar name=1>#Appendices</tvar>|Appendices]] section below also provides installation notes for specific system configurations. </translate> {{Note|<translate><!--T:149--> If you are already running MediaWiki, see the [[<tvar name=1>Special:MyLanguage/Manual:Upgrading</tvar>|Upgrade guide]].</translate>}} <translate> == Check the installation requirements == <!--T:150--> <!--T:151--> Check that your system meets the [[<tvar name=1>Special:MyLanguage/Manual:Installation requirements</tvar>|installation requirements]]. <!--T:152--> Make sure to also check the <tvar name=1>{{ll|Release notes}}</tvar> of the MediaWiki version that you plan to install. == Download the MediaWiki software == <!--T:6--> <!--T:121--> Download the MediaWiki tar file from the [[<tvar name=1>Special:MyLanguage/Download</tvar>|official download page]]. <!--T:122--> Generally, if you're using a production environment, you want to be running the latest stable release, which is <tvar name=1>MediaWiki {{MW stable release number}}</tvar>. == Extract the MediaWiki software == <!--T:136--> </translate> <translate><!--T:10--> The downloaded file is in <tvar name=2><code>.zip</code></tvar> or in <tvar name=1><code>.tar.gz</code></tvar> file format.</translate> <translate><!--T:137--> You need to uncompress this archive file before use.</translate> <translate><!--T:11--> You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</translate> <translate> <!--T:12--> On Windows, uncompressing is usually done with software such as <tvar name=7zip>[https://www.7-zip.org/ 7-Zip]</tvar> (free), <tvar name=winzip>[http://www.winzip.com/ WinZip]</tvar>, <tvar name=winrar>[https://www.rarlab.com/ WinRAR]</tvar> or <tvar name=izarc>[https://www.izarc.org/ IZArc]</tvar> (free). </translate> <translate><!--T:13--> On Linux and Mac OS X, you can uncompress the file using the command:</translate> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<translate><!--T:145--> If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</translate> <translate><!--T:141--> On Linux systems, the command would be using [[w:chown|chown]] as the following:</translate> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <translate> ==Upload files to your web server== <!--T:18--> <!--T:19--> If you have not already uploaded the files to your [[<tvar name=1>Special:MyLanguage/Manual:Installation requirements#Web server</tvar>|web server]] (or copied, if your web server software runs locally on your <tvar name=2><code>localhost</code></tvar>), do so now. <!--T:21--> Upload the files to your web server's web directory either by: <!--T:22--> # directly copying the unzipped folder or</translate> <translate> <!--T:23--> # by using an FTP client such as <tvar name=filezilla>[https://filezilla-project.org/ FileZilla]</tvar> (Windows, OSX and Linux) or <tvar name=cyberduck>[https://cyberduck.io/ Cyberduck]</tvar> (Windows and OSX). </translate> # <translate><!--T:135--> by using software already provided by your [[<tvar name=1>Special:MyLanguage/Hosting services</tvar>|hosting service]], such as the ''cPanel File Manager''</translate> <translate> <!--T:20--> If your upload tool has a "change file names to lowercase" option, then you must disable this. </translate> <translate><!--T:24--> If you use the Apache HTTPD web server, the correct directory is specified in your <tvar name=conf><code>httpd.conf</code></tvar> file in the <tvar name=3>[https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>]</tvar> directive.</translate> <translate><!--T:153--> By default, this is <tvar name=1><code>/var/www/</code></tvar> or {{<tvar name=2>tmpl|0=<code>&lt;$1>/htdocs</code></tvar>|apache-folder}}.</translate> <translate><!--T:142--> The exact location of the Apache server settings and directories file <tvar name=1><code>httpd.conf</code></tvar> depends on your operating system.</translate> <translate><!--T:25--> In Debian and Ubuntu, the file for Apache server settings and directories is <tvar name=conf><code>/etc/apache2/apache2.conf</code></tvar>.</translate> <translate><!--T:143--> In Red Hat and Fedora, the file is <tvar name=1><code>/etc/httpd/conf/httpd.conf</code></tvar>.</translate> <translate><!--T:27--> Rename the uploaded folder to whatever you would like to have in the URL.</translate> <translate><!--T:28--> If your web server is running as <tvar name=1><code>http://localhost</code></tvar> for example, renaming to <tvar name=2><code>/w/</code></tvar> directory would mean you would access your wiki at <tvar name=index><code>http://localhost/w/index.php</code></tvar>.</translate> {{Note|1=<translate><!--T:29--> Do not use <tvar name=wiki><code>/wiki/</code></tvar> if you want to set it up as a [[<tvar name=short-url>Special:MyLanguage/Manual:Short URL</tvar>|Short URL]] after running the [[<tvar name=1>Special:MyLanguage/Manual:Config script</tvar>|installation script]].</translate>}} {{anchor|Create a database}} <translate> == Set up the database == <!--T:33--> <!--T:46--> MediaWiki's [[<tvar name=1>Special:MyLanguage/Manual:Config script</tvar>|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. <!--T:34--> If you already have a database server and know the password for the "root" (admin) user, skip to the [[<tvar name=1>#Run the installation script</tvar>|#Run the installation script]] section below. <!--T:36--> If you don't know the password for the root user, for example if you are on a [[<tvar name=1>Special:MyLanguage/Hosting services</tvar>|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </translate> <translate><!--T:37--> SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</translate> <translate><!--T:115--> If you're unsure which database to choose, use MariaDB.</translate> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <translate> <!--T:144--> No further setup is required for [[<tvar name=1>Special:MyLanguage/Manual:SQLite</tvar>|SQLite]] if the <tvar name=2><code>pdo-sqlite</code></tvar> module for PHP is installed on the system. </translate> <translate><!--T:42--> On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</translate> <translate><!--T:43--> For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</translate> <translate><!--T:44--> If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</translate> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <translate><!--T:48--> See the corresponding documentation of your hosting provider.</translate> <translate><!--T:49--> Alternatively, contact your [[<tvar name=1>Special:MyLanguage/Hosting services</tvar>|hosting provider]] to have them create an account for you.</translate> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <translate> <!--T:72--> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<tvar name=1><code>mediawiki.example.com</code></tvar> in the example below): </translate> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<translate><!--T:105--> MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</translate> <translate><!--T:106--> If this concerns you, delete and disable the <tvar name=history><code>.mysql_history</code></tvar> file after running these queries by following the [<tvar name=url>https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file</tvar> MySQL documentation].</translate>}} ===PostgreSQL=== <translate><!--T:74--> If you are using [[<tvar name=1>Special:MyLanguage/Manual:PostgreSQL</tvar>|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</translate> <translate><!--T:75--> Often, this is the database user named <tvar name=1><code>postgres</code></tvar>.</translate> <translate> <!--T:154--> The following commands on a Linux command-line, as the postgres user, create a database user named <tvar name=1><code>wikiuser</code></tvar>, and a database named <tvar name=2><code>my_wiki</code></tvar> owned by the user named <tvar name=3><code>wikiuser</code></tvar>.</translate> createuser -S -D -R -P -E wikiuser <translate><!--T:80--> (then enter the database password)</translate> createdb -O wikiuser my_wiki <translate> <!--T:81--> or as superuser (default postgres) execute the following commands at the database prompt: </translate> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <translate> <!--T:82--> Beware of the [[<tvar name=phab>phab:tag/postgreSQL</tvar>|list of known issues when running MediaWiki with PostgreSQL]]. </translate> {{anchor|Run the installation script}} <translate> == Run the installation script == <!--T:110--> <!--T:84--> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in <tvar name=man>{{ll|Manual:Config script}}</tvar>. ==Further configuration== <!--T:116--> </translate> * {{ll|Manual:System administration#Configuration}} - <translate><!--T:155--> Additional configuration</translate> * {{ll|Manual:Administrators}} - <translate><!--T:156--> Wiki administration</translate> <translate> == Keep up to date! == <!--T:88--> </translate> <translate> <!--T:90--> Once installed, make sure you stay up to date with releases, and keep your server secure!</translate> {{Clickable button 2|<translate><!--T:89--> Subscribe to the MediaWiki release announcements mailing list.</translate>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <translate> == Appendices == <!--T:157--> </translate> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <translate> === Alternatives to manual installation === <!--T:158--> <!--T:159--> Instead of manually installing MediaWiki, alternative options might be easier:</translate> * <translate><!--T:160--> [[<tvar name=1>Special:MyLanguage/Software bundles#MediaWiki software appliances</tvar>|pre-integrated software appliances]]</translate> * <translate><!--T:161--> [[<tvar name=1>Special:MyLanguage/Hosting services</tvar>|hosting services with 1-click installation, or wiki farms]]</translate> :{{Note|1=<translate><!--T:66--> Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</translate>}} <translate> <!--T:140--> See also the <tvar name=1>{{ll|comparison of distribution options}}</tvar>. === System-specific instructions === <!--T:162--> <!--T:163--> The pages listed on <tvar name=1>{{ll|Manual:OS specific help}}</tvar> give more detailed installation instructions aimed at specific systems. </translate> <translate><!--T:164--> However, by and large these per-system docs are less maintained and might not always be up to date.</translate> <translate><!--T:165--> First consult <tvar name=1>{{ll|Manual:Installing MediaWiki|nsp=0}}</tvar> (this page) before looking at per-system installation documentation.</translate> {{anchor|Wiki families (multiple wikis)}} <translate> === Running multiple wikis === <!--T:166--> <!--T:167--> Refer to [[<tvar name=1>Special:MyLanguage/Manual:FAQ#Installation and configuration</tvar>|Manual:FAQ#Installation and configuration]]. </translate> {{anchor|Installing an existing wiki}} <translate> === Importing an existing wiki database === <!--T:168--> <!--T:169--> Refer to [[<tvar name=1>Special:MyLanguage/Manual:FAQ#Installation and configuration</tvar>|Manual:FAQ#Installation and configuration]]. == See also == <!--T:94--> </translate> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 2lrgvtnmwga4wghd5kyrdkw8ae1gmfu Manual:Installing third-party tools 100 18176 5387818 5377087 2022-07-29T09:28:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Template:InstallationNav 10 18186 5387182 5384760 2022-07-28T21:17:12Z Shirayuki 472859 discard translation units wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<translate><!--T:11--> Install MediaWiki</translate>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<translate><!--T:12--> Requirements</translate>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<translate><!--T:13--> Extract</translate>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<translate><!--T:14--> Upload</translate>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<translate><!--T:15--> Set up database</translate>}} &bull; <!-- -->{{ll|Manual:Config script|2=<translate><!--T:16--> Install</translate>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<translate><!--T:17--> Configure</translate>}} &bull; <!-- -->{{ll|Customization|2=<translate><!--T:10--> Customize</translate>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2=<translate> <!--T:18--> FAQ</translate>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2=<translate> <!--T:19--> Common issues</translate>}} &bull; <!-- -->{{ll|Communication|2=<translate>Get help and support</translate>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] qmo4zd208p08kga75369f5jovo1zver 5387183 5387182 2022-07-28T21:17:23Z Shirayuki 472859 Marked this version for translation wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<translate><!--T:11--> Install MediaWiki</translate>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<translate><!--T:12--> Requirements</translate>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<translate><!--T:13--> Extract</translate>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<translate><!--T:14--> Upload</translate>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<translate><!--T:15--> Set up database</translate>}} &bull; <!-- -->{{ll|Manual:Config script|2=<translate><!--T:16--> Install</translate>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<translate><!--T:17--> Configure</translate>}} &bull; <!-- -->{{ll|Customization|2=<translate><!--T:10--> Customize</translate>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2=<translate> <!--T:18--> FAQ</translate>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2=<translate> <!--T:19--> Common issues</translate>}} &bull; <!-- -->{{ll|Communication|2=<translate><!--T:20--> Get help and support</translate>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] dcsm5ih62g0nielyp6as6vlpuz14tf2 Manual:Installation guide/cs 100 18208 5386462 5381077 2022-07-28T14:24:46Z ENeRZet 17359278 wikitext text/x-wiki <noinclude> <languages/> {{InstallationNav}} Tato příručka obsahuje pokyny k instalaci a konfiguraci MediaWiki, [[#Manual installation|návody]] a jednodušší [[#Alternatives to manual installation|alternativy]]. [[#Appendices|Dodatky]] poskytují odkazy na podrobnější poznámky k instalaci pro specifické konfigurace systému a další méně běžná použití softwaru. == Průvodce aktualizací == Pokud již MediaWiki používáte, podívejte se do [[Special:MyLanguage/Manual:Upgrading|příručky pro aktualizaci]]. {{anchor|Manual installation}} == Návod na instalaci == {{anchor|Summarized_installation_guide}} === Shrnutí === </noinclude> Pro zkušené uživatele je zde rychlá verze instalačních pokynů (například pokud nevíte, jak nainstalovat nebo zkontrolovat nezbytný software v počítači). Většina uživatelů, bude chtít [[#Main-installation-guide|postupovat podle průvodce základní instalací]]. <ol> <li>Zkontrolujte, zda váš systém splňuje následující minimální požadavky. ''(Podrobnosti najdete v [[Special:MyLanguage/Manual:Installation requirements|požadavcích na instalaci]]. Nezapomeňte také zkontrolovat požadavky v [[Special:MyLanguage/Release notes|POZNÁMKÁCH K VYDÁNÍ]] (relase notes) dodaných s MediaWiki.)'' Budete potřebovat: * [[Special:MyLanguage/Download|Stáhněte si]] MediaWiki (aktuální stabilní verze je {{MW stable release number}}) * '''Webový server''' jako [[Special:MyLanguage/Apache_configuration|Apache]] nebo [https://www.iis.net/ IIS] ** Kvůli spouštění údržbových skriptů je vyžadován přístup k příkazové řádce * '''{{ll|PHP_configuration|PHP}}''' {{MW stable php requirement}}+ {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} ** MediaWiki requires some PHP extensions to be installed. These extensions are enabled in PHP by default. The MediaWiki installer will point out missing PHP extensions. See [[Manual:Installation requirements#PHP]] for a full list. * Jeden z následujících '''databázových serverů''': ** {{ll|Manual:MySQL|MySQL}} {{MW stable mysql requirement}}+ ** {{ll|Manual:MariaDB|MariaDB}} {{MW stable MariaDB requirement}}+ ** {{ll|Manual:PostgreSQL|PostgreSQL}} {{MW stable postgresql requirement}}+ ** {{ll|Manual:SQLite|SQLite}} {{MW stable sqlite requirement}}+ Další programy vyžadují [[Special:MyLanguage/Manual:image thumbnailing|miniatury obrázku]]. {{ll|Parsoid}} (vyžaduje [[Special:MyLanguage/VisualEditor|VisualEditor]]) a i jiné služby mají své vlastní požadavky.</li> <li>[[Special:MyLanguage/Download|Stáhněte si MediaWiki]] <small>({{MW stable release link|přímý odkaz na stažení aktuálního stabilního vydání}})</small> a umístěte archiv do složky, která může být přístupná z webu.</li> <li>Nasměrujte váš prohlížeč do adresáře, kam byla MediaWiki umístěna a postupujte podle pokynů na obrazovce. Mělo by to být ve formátu <code>http://''doména''/''adresář''/mw-config/index.php</code> Nahraďte příkaz ''adresář'' (directory) cestou do umístění vaší MediaWiki složky. Pokud instalujete do místního zařízení, nahraďte ''doména'' (domain) tímto textem: <code>localhost</code>. Pokud nainstalujete MediaWiki lokálně a poté chcete přistupovat k vaší wiki z ''domény'', musíte změnit LocalSetting.php z kódu <code>localhost</code> na ''doména''. Pokud je nainstalován na vzdáleném serveru, nahraďte ''doména'' jménem vaší domény (například www.example.com).</li> <li>Pro dokončení procesu [[Special:MyLanguage/Manual:Config script|postupujte podle pokynů na obrazovce]].</li> </ol> Tyto instrukce jsou úmyslně velmi stručné. <span lang="en" dir="ltr" class="mw-content-ltr">If in doubt, read {{ll|Manual:Installing MediaWiki}}.</span> <section end=short /><noinclude> {{clear}} {{anchor|Alternatives to manual installation|Alternative to manual installation}} == Alternativy k ruční instalaci == Ruční instalaci se můžete vyhnout využitím [[Special:MyLanguage/Software bundles#MediaWiki software appliances|automatizovaných instalačních balíčků]], [[Special:MyLanguage/Hosting services|některých hostingů se zjednodušenou instalací nebo wikifarem]]. {{Note|1=<span class="mw-translate-fuzzy">Weby hostingových služeb občas nabízejí také automatickou instalaci různých aplikací, jako je např. MediaWiki. Často při tom nedodrží správný postup. Což má za následek chyby a problémy při instalací MediaWiki! Pokud narazíte na takový problém, pak ''to neznamená'', že MediaWiki nejde nainstalovat! Znamená to, že byste MediaWiki měli raději nainstalovat ručně podle následujících kroků. Má to i své výhody. Kromě toho, že budete mít větší kontrolu nad tím, kam si MediaWiki na serveru nainstalujete a jakou použijete cestu k souborům, můžete také při ruční instalaci použít sdílenou databázi nebo sledovat instalační proces a při tom povolit nové funkce wiki.</span>}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == Přílohy == === Pokročilá konfigurace === <div class="mw-translate-fuzzy"> Následující stránky popisují některé pokročilejší konfigurační možnosti: * [[$1|Pokročilá konfigurace]]. * [[$2|Správa wiki]]. </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> For running several wikis or importing content into a MediaWiki installation, refer to [[Manual:FAQ#Installation and configuration]]. === Pomoc s instalací === * FAQ: [[Special:MyLanguage/FAQ#Installation and configuration|FAQ#Instalace a konfigurace]]. * {{ll|Manual:Common errors and symptoms#Installation Errors|2=MediaWiki installation errors}} * {{ll|Communication}} - Ask questions and receive help about installing MediaWiki === Pokyny pro konkrétní systémy === Stránky uvedené na {{ll|Manual:OS specific help}} poskytují podrobnější pokyny k instalaci zaměřené na konkrétní systémy. Celkově je však {{ll|Manual:Installing MediaWiki}} aktuálnější a lépe napsaná než dokumenty pro jednotlivé systémy a proto se doporučuje, abyste si nejprve prohlédli {{ll|Manual:Installing MediaWiki}}, než se podíváte na instalační dokumenty pro jednotlivé systémy. == Související stránky == * {{ll|Comparison of distribution options|2=Porovnání možností distribuce softwaru MediaWiki}} * {{ll|Manual:Uninstallation|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:MediaWiki Introduction{{#translation:}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] </noinclude> 71p5u4g7f7iz5tb6a2siqrqcu1aj579 5386464 5386462 2022-07-28T14:25:08Z ENeRZet 17359278 Created page with "Pokud máte pochybnosti, přečtěte si $1." wikitext text/x-wiki <noinclude> <languages/> {{InstallationNav}} Tato příručka obsahuje pokyny k instalaci a konfiguraci MediaWiki, [[#Manual installation|návody]] a jednodušší [[#Alternatives to manual installation|alternativy]]. [[#Appendices|Dodatky]] poskytují odkazy na podrobnější poznámky k instalaci pro specifické konfigurace systému a další méně běžná použití softwaru. == Průvodce aktualizací == Pokud již MediaWiki používáte, podívejte se do [[Special:MyLanguage/Manual:Upgrading|příručky pro aktualizaci]]. {{anchor|Manual installation}} == Návod na instalaci == {{anchor|Summarized_installation_guide}} === Shrnutí === </noinclude> Pro zkušené uživatele je zde rychlá verze instalačních pokynů (například pokud nevíte, jak nainstalovat nebo zkontrolovat nezbytný software v počítači). Většina uživatelů, bude chtít [[#Main-installation-guide|postupovat podle průvodce základní instalací]]. <ol> <li>Zkontrolujte, zda váš systém splňuje následující minimální požadavky. ''(Podrobnosti najdete v [[Special:MyLanguage/Manual:Installation requirements|požadavcích na instalaci]]. Nezapomeňte také zkontrolovat požadavky v [[Special:MyLanguage/Release notes|POZNÁMKÁCH K VYDÁNÍ]] (relase notes) dodaných s MediaWiki.)'' Budete potřebovat: * [[Special:MyLanguage/Download|Stáhněte si]] MediaWiki (aktuální stabilní verze je {{MW stable release number}}) * '''Webový server''' jako [[Special:MyLanguage/Apache_configuration|Apache]] nebo [https://www.iis.net/ IIS] ** Kvůli spouštění údržbových skriptů je vyžadován přístup k příkazové řádce * '''{{ll|PHP_configuration|PHP}}''' {{MW stable php requirement}}+ {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} ** MediaWiki requires some PHP extensions to be installed. These extensions are enabled in PHP by default. The MediaWiki installer will point out missing PHP extensions. See [[Manual:Installation requirements#PHP]] for a full list. * Jeden z následujících '''databázových serverů''': ** {{ll|Manual:MySQL|MySQL}} {{MW stable mysql requirement}}+ ** {{ll|Manual:MariaDB|MariaDB}} {{MW stable MariaDB requirement}}+ ** {{ll|Manual:PostgreSQL|PostgreSQL}} {{MW stable postgresql requirement}}+ ** {{ll|Manual:SQLite|SQLite}} {{MW stable sqlite requirement}}+ Další programy vyžadují [[Special:MyLanguage/Manual:image thumbnailing|miniatury obrázku]]. {{ll|Parsoid}} (vyžaduje [[Special:MyLanguage/VisualEditor|VisualEditor]]) a i jiné služby mají své vlastní požadavky.</li> <li>[[Special:MyLanguage/Download|Stáhněte si MediaWiki]] <small>({{MW stable release link|přímý odkaz na stažení aktuálního stabilního vydání}})</small> a umístěte archiv do složky, která může být přístupná z webu.</li> <li>Nasměrujte váš prohlížeč do adresáře, kam byla MediaWiki umístěna a postupujte podle pokynů na obrazovce. Mělo by to být ve formátu <code>http://''doména''/''adresář''/mw-config/index.php</code> Nahraďte příkaz ''adresář'' (directory) cestou do umístění vaší MediaWiki složky. Pokud instalujete do místního zařízení, nahraďte ''doména'' (domain) tímto textem: <code>localhost</code>. Pokud nainstalujete MediaWiki lokálně a poté chcete přistupovat k vaší wiki z ''domény'', musíte změnit LocalSetting.php z kódu <code>localhost</code> na ''doména''. Pokud je nainstalován na vzdáleném serveru, nahraďte ''doména'' jménem vaší domény (například www.example.com).</li> <li>Pro dokončení procesu [[Special:MyLanguage/Manual:Config script|postupujte podle pokynů na obrazovce]].</li> </ol> Tyto instrukce jsou úmyslně velmi stručné. Pokud máte pochybnosti, přečtěte si {{ll|Manual:Installing MediaWiki}}. <section end=short /><noinclude> {{clear}} {{anchor|Alternatives to manual installation|Alternative to manual installation}} == Alternativy k ruční instalaci == Ruční instalaci se můžete vyhnout využitím [[Special:MyLanguage/Software bundles#MediaWiki software appliances|automatizovaných instalačních balíčků]], [[Special:MyLanguage/Hosting services|některých hostingů se zjednodušenou instalací nebo wikifarem]]. {{Note|1=<span class="mw-translate-fuzzy">Weby hostingových služeb občas nabízejí také automatickou instalaci různých aplikací, jako je např. MediaWiki. Často při tom nedodrží správný postup. Což má za následek chyby a problémy při instalací MediaWiki! Pokud narazíte na takový problém, pak ''to neznamená'', že MediaWiki nejde nainstalovat! Znamená to, že byste MediaWiki měli raději nainstalovat ručně podle následujících kroků. Má to i své výhody. Kromě toho, že budete mít větší kontrolu nad tím, kam si MediaWiki na serveru nainstalujete a jakou použijete cestu k souborům, můžete také při ruční instalaci použít sdílenou databázi nebo sledovat instalační proces a při tom povolit nové funkce wiki.</span>}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == Přílohy == === Pokročilá konfigurace === <div class="mw-translate-fuzzy"> Následující stránky popisují některé pokročilejší konfigurační možnosti: * [[$1|Pokročilá konfigurace]]. * [[$2|Správa wiki]]. </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> For running several wikis or importing content into a MediaWiki installation, refer to [[Manual:FAQ#Installation and configuration]]. === Pomoc s instalací === * FAQ: [[Special:MyLanguage/FAQ#Installation and configuration|FAQ#Instalace a konfigurace]]. * {{ll|Manual:Common errors and symptoms#Installation Errors|2=MediaWiki installation errors}} * {{ll|Communication}} - Ask questions and receive help about installing MediaWiki === Pokyny pro konkrétní systémy === Stránky uvedené na {{ll|Manual:OS specific help}} poskytují podrobnější pokyny k instalaci zaměřené na konkrétní systémy. Celkově je však {{ll|Manual:Installing MediaWiki}} aktuálnější a lépe napsaná než dokumenty pro jednotlivé systémy a proto se doporučuje, abyste si nejprve prohlédli {{ll|Manual:Installing MediaWiki}}, než se podíváte na instalační dokumenty pro jednotlivé systémy. == Související stránky == * {{ll|Comparison of distribution options|2=Porovnání možností distribuce softwaru MediaWiki}} * {{ll|Manual:Uninstallation|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:MediaWiki Introduction{{#translation:}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] </noinclude> kvym1d3za71deou1xnh8bav1lorr7p1 5386466 5386464 2022-07-28T14:26:18Z ENeRZet 17359278 wikitext text/x-wiki <noinclude> <languages/> {{InstallationNav}} Tato příručka obsahuje pokyny k instalaci a konfiguraci MediaWiki, [[#Manual installation|návody]] a jednodušší [[#Alternatives to manual installation|alternativy]]. [[#Appendices|Dodatky]] poskytují odkazy na podrobnější poznámky k instalaci pro specifické konfigurace systému a další méně běžná použití softwaru. == Průvodce aktualizací == Pokud již MediaWiki používáte, podívejte se do [[Special:MyLanguage/Manual:Upgrading|příručky pro aktualizaci]]. {{anchor|Manual installation}} == Návod na instalaci == {{anchor|Summarized_installation_guide}} === Shrnutí === </noinclude> Pro zkušené uživatele je zde rychlá verze instalačních pokynů (například pokud nevíte, jak nainstalovat nebo zkontrolovat nezbytný software v počítači). Většina uživatelů, bude chtít [[#Main-installation-guide|postupovat podle průvodce základní instalací]]. <ol> <li>Zkontrolujte, zda váš systém splňuje následující minimální požadavky. ''(Podrobnosti najdete v [[Special:MyLanguage/Manual:Installation requirements|požadavcích na instalaci]]. Nezapomeňte také zkontrolovat požadavky v [[Special:MyLanguage/Release notes|POZNÁMKÁCH K VYDÁNÍ]] (relase notes) dodaných s MediaWiki.)'' Budete potřebovat: * [[Special:MyLanguage/Download|Stáhněte si]] MediaWiki (aktuální stabilní verze je {{MW stable release number}}) * '''Webový server''' jako [[Special:MyLanguage/Apache_configuration|Apache]] nebo [https://www.iis.net/ IIS] ** Kvůli spouštění údržbových skriptů je vyžadován přístup k příkazové řádce * '''{{ll|PHP_configuration|PHP}}''' {{MW stable php requirement}}+ {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} ** MediaWiki requires some PHP extensions to be installed. These extensions are enabled in PHP by default. The MediaWiki installer will point out missing PHP extensions. See [[Manual:Installation requirements#PHP]] for a full list. * Jeden z následujících '''databázových serverů''': ** {{ll|Manual:MySQL|MySQL}} {{MW stable mysql requirement}}+ ** {{ll|Manual:MariaDB|MariaDB}} {{MW stable MariaDB requirement}}+ ** {{ll|Manual:PostgreSQL|PostgreSQL}} {{MW stable postgresql requirement}}+ ** {{ll|Manual:SQLite|SQLite}} {{MW stable sqlite requirement}}+ Další programy vyžadují [[Special:MyLanguage/Manual:image thumbnailing|miniatury obrázku]]. {{ll|Parsoid}} (vyžaduje [[Special:MyLanguage/VisualEditor|VisualEditor]]) a i jiné služby mají své vlastní požadavky.</li> <li>[[Special:MyLanguage/Download|Stáhněte si MediaWiki]] <small>({{MW stable release link|přímý odkaz na stažení aktuálního stabilního vydání}})</small> a umístěte archiv do složky, která může být přístupná z webu.</li> <li>Nasměrujte váš prohlížeč do adresáře, kam byla MediaWiki umístěna a postupujte podle pokynů na obrazovce. Mělo by to být ve formátu <code>http://''doména''/''adresář''/mw-config/index.php</code> Nahraďte příkaz ''adresář'' (directory) cestou do umístění vaší MediaWiki složky. Pokud instalujete do místního zařízení, nahraďte ''doména'' (domain) tímto textem: <code>localhost</code>. Pokud nainstalujete MediaWiki lokálně a poté chcete přistupovat k vaší wiki z ''domény'', musíte změnit LocalSetting.php z kódu <code>localhost</code> na ''doména''. Pokud je nainstalován na vzdáleném serveru, nahraďte ''doména'' jménem vaší domény (například www.example.com).</li> <li>Pro dokončení procesu [[Special:MyLanguage/Manual:Config script|postupujte podle pokynů na obrazovce]].</li> </ol> Tyto instrukce jsou úmyslně velmi stručné. Pokud máte pochybnosti, přečtěte si {{ll|Manual:Installing MediaWiki}}. <section end=short /><noinclude> {{clear}} {{anchor|Alternatives to manual installation|Alternative to manual installation}} == Alternativy k ruční instalaci == Ruční instalaci se můžete vyhnout využitím [[Special:MyLanguage/Software bundles#MediaWiki software appliances|automatizovaných instalačních balíčků]], [[Special:MyLanguage/Hosting services|některých hostingů se zjednodušenou instalací nebo wikifarem]]. {{Note|1=Hostingové služby, které poskytují automatickou instalaci aplikací, jako je MediaWiki, mohou nabízet zastaralé verze nebo mít jiné problémy. Pokud narazíte na problémy, ''neznamená to'', že nemůžete nainstalovat MediaWiki. To znamená, že byste měli nainstalovat MediaWiki ručně.}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == Přílohy == === Pokročilá konfigurace === <div class="mw-translate-fuzzy"> Následující stránky popisují některé pokročilejší konfigurační možnosti: * [[$1|Pokročilá konfigurace]]. * [[$2|Správa wiki]]. </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> For running several wikis or importing content into a MediaWiki installation, refer to [[Manual:FAQ#Installation and configuration]]. === Pomoc s instalací === * FAQ: [[Special:MyLanguage/FAQ#Installation and configuration|FAQ#Instalace a konfigurace]]. * {{ll|Manual:Common errors and symptoms#Installation Errors|2=MediaWiki installation errors}} * {{ll|Communication}} - Ask questions and receive help about installing MediaWiki === Pokyny pro konkrétní systémy === Stránky uvedené na {{ll|Manual:OS specific help}} poskytují podrobnější pokyny k instalaci zaměřené na konkrétní systémy. Celkově je však {{ll|Manual:Installing MediaWiki}} aktuálnější a lépe napsaná než dokumenty pro jednotlivé systémy a proto se doporučuje, abyste si nejprve prohlédli {{ll|Manual:Installing MediaWiki}}, než se podíváte na instalační dokumenty pro jednotlivé systémy. == Související stránky == * {{ll|Comparison of distribution options|2=Porovnání možností distribuce softwaru MediaWiki}} * {{ll|Manual:Uninstallation|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:MediaWiki Introduction{{#translation:}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] </noinclude> sty8g1a5x40lzmafrrcxxeu6wmp3erl 5386468 5386466 2022-07-28T14:26:47Z ENeRZet 17359278 wikitext text/x-wiki <noinclude> <languages/> {{InstallationNav}} Tato příručka obsahuje pokyny k instalaci a konfiguraci MediaWiki, [[#Manual installation|návody]] a jednodušší [[#Alternatives to manual installation|alternativy]]. [[#Appendices|Dodatky]] poskytují odkazy na podrobnější poznámky k instalaci pro specifické konfigurace systému a další méně běžná použití softwaru. == Průvodce aktualizací == Pokud již MediaWiki používáte, podívejte se do [[Special:MyLanguage/Manual:Upgrading|příručky pro aktualizaci]]. {{anchor|Manual installation}} == Návod na instalaci == {{anchor|Summarized_installation_guide}} === Shrnutí === </noinclude> Pro zkušené uživatele je zde rychlá verze instalačních pokynů (například pokud nevíte, jak nainstalovat nebo zkontrolovat nezbytný software v počítači). Většina uživatelů, bude chtít [[#Main-installation-guide|postupovat podle průvodce základní instalací]]. <ol> <li>Zkontrolujte, zda váš systém splňuje následující minimální požadavky. ''(Podrobnosti najdete v [[Special:MyLanguage/Manual:Installation requirements|požadavcích na instalaci]]. Nezapomeňte také zkontrolovat požadavky v [[Special:MyLanguage/Release notes|POZNÁMKÁCH K VYDÁNÍ]] (relase notes) dodaných s MediaWiki.)'' Budete potřebovat: * [[Special:MyLanguage/Download|Stáhněte si]] MediaWiki (aktuální stabilní verze je {{MW stable release number}}) * '''Webový server''' jako [[Special:MyLanguage/Apache_configuration|Apache]] nebo [https://www.iis.net/ IIS] ** Kvůli spouštění údržbových skriptů je vyžadován přístup k příkazové řádce * '''{{ll|PHP_configuration|PHP}}''' {{MW stable php requirement}}+ {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} ** MediaWiki requires some PHP extensions to be installed. These extensions are enabled in PHP by default. The MediaWiki installer will point out missing PHP extensions. See [[Manual:Installation requirements#PHP]] for a full list. * Jeden z následujících '''databázových serverů''': ** {{ll|Manual:MySQL|MySQL}} {{MW stable mysql requirement}}+ ** {{ll|Manual:MariaDB|MariaDB}} {{MW stable MariaDB requirement}}+ ** {{ll|Manual:PostgreSQL|PostgreSQL}} {{MW stable postgresql requirement}}+ ** {{ll|Manual:SQLite|SQLite}} {{MW stable sqlite requirement}}+ Další programy vyžadují [[Special:MyLanguage/Manual:image thumbnailing|miniatury obrázku]]. {{ll|Parsoid}} (vyžaduje [[Special:MyLanguage/VisualEditor|VisualEditor]]) a i jiné služby mají své vlastní požadavky.</li> <li>[[Special:MyLanguage/Download|Stáhněte si MediaWiki]] <small>({{MW stable release link|přímý odkaz na stažení aktuálního stabilního vydání}})</small> a umístěte archiv do složky, která může být přístupná z webu.</li> <li>Nasměrujte váš prohlížeč do adresáře, kam byla MediaWiki umístěna a postupujte podle pokynů na obrazovce. Mělo by to být ve formátu <code>http://''doména''/''adresář''/mw-config/index.php</code> Nahraďte příkaz ''adresář'' (directory) cestou do umístění vaší MediaWiki složky. Pokud instalujete do místního zařízení, nahraďte ''doména'' (domain) tímto textem: <code>localhost</code>. Pokud nainstalujete MediaWiki lokálně a poté chcete přistupovat k vaší wiki z ''domény'', musíte změnit LocalSetting.php z kódu <code>localhost</code> na ''doména''. Pokud je nainstalován na vzdáleném serveru, nahraďte ''doména'' jménem vaší domény (například www.example.com).</li> <li>Pro dokončení procesu [[Special:MyLanguage/Manual:Config script|postupujte podle pokynů na obrazovce]].</li> </ol> Tyto instrukce jsou úmyslně velmi stručné. Pokud máte pochybnosti, přečtěte si {{ll|Manual:Installing MediaWiki}}. <section end=short /><noinclude> {{clear}} {{anchor|Alternatives to manual installation|Alternative to manual installation}} == Alternativy k ruční instalaci == Ruční instalaci se můžete vyhnout využitím [[Special:MyLanguage/Software bundles#MediaWiki software appliances|automatizovaných instalačních balíčků]], [[Special:MyLanguage/Hosting services|některých hostingů se zjednodušenou instalací nebo wikifarem]]. {{Note|1=Hostingové služby, které poskytují automatickou instalaci aplikací, jako je MediaWiki, mohou nabízet zastaralé verze nebo mít jiné problémy. Pokud narazíte na problémy, ''neznamená to'', že nemůžete nainstalovat MediaWiki. To znamená, že byste měli nainstalovat MediaWiki ručně.}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == Přílohy == === Pokročilá konfigurace === Následující stránky popisují některé pokročilejší konfigurační možnosti: * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> For running several wikis or importing content into a MediaWiki installation, refer to [[Manual:FAQ#Installation and configuration]]. === Pomoc s instalací === * FAQ: [[Special:MyLanguage/FAQ#Installation and configuration|FAQ#Instalace a konfigurace]]. * {{ll|Manual:Common errors and symptoms#Installation Errors|2=MediaWiki installation errors}} * {{ll|Communication}} - Ask questions and receive help about installing MediaWiki === Pokyny pro konkrétní systémy === Stránky uvedené na {{ll|Manual:OS specific help}} poskytují podrobnější pokyny k instalaci zaměřené na konkrétní systémy. Celkově je však {{ll|Manual:Installing MediaWiki}} aktuálnější a lépe napsaná než dokumenty pro jednotlivé systémy a proto se doporučuje, abyste si nejprve prohlédli {{ll|Manual:Installing MediaWiki}}, než se podíváte na instalační dokumenty pro jednotlivé systémy. == Související stránky == * {{ll|Comparison of distribution options|2=Porovnání možností distribuce softwaru MediaWiki}} * {{ll|Manual:Uninstallation|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:MediaWiki Introduction{{#translation:}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] </noinclude> 3ilvrqo16us3n0o8bku23xwr9d80ljg 5386470 5386468 2022-07-28T14:27:09Z ENeRZet 17359278 Created page with "Pokročilá konfigurace" wikitext text/x-wiki <noinclude> <languages/> {{InstallationNav}} Tato příručka obsahuje pokyny k instalaci a konfiguraci MediaWiki, [[#Manual installation|návody]] a jednodušší [[#Alternatives to manual installation|alternativy]]. [[#Appendices|Dodatky]] poskytují odkazy na podrobnější poznámky k instalaci pro specifické konfigurace systému a další méně běžná použití softwaru. == Průvodce aktualizací == Pokud již MediaWiki používáte, podívejte se do [[Special:MyLanguage/Manual:Upgrading|příručky pro aktualizaci]]. {{anchor|Manual installation}} == Návod na instalaci == {{anchor|Summarized_installation_guide}} === Shrnutí === </noinclude> Pro zkušené uživatele je zde rychlá verze instalačních pokynů (například pokud nevíte, jak nainstalovat nebo zkontrolovat nezbytný software v počítači). Většina uživatelů, bude chtít [[#Main-installation-guide|postupovat podle průvodce základní instalací]]. <ol> <li>Zkontrolujte, zda váš systém splňuje následující minimální požadavky. ''(Podrobnosti najdete v [[Special:MyLanguage/Manual:Installation requirements|požadavcích na instalaci]]. Nezapomeňte také zkontrolovat požadavky v [[Special:MyLanguage/Release notes|POZNÁMKÁCH K VYDÁNÍ]] (relase notes) dodaných s MediaWiki.)'' Budete potřebovat: * [[Special:MyLanguage/Download|Stáhněte si]] MediaWiki (aktuální stabilní verze je {{MW stable release number}}) * '''Webový server''' jako [[Special:MyLanguage/Apache_configuration|Apache]] nebo [https://www.iis.net/ IIS] ** Kvůli spouštění údržbových skriptů je vyžadován přístup k příkazové řádce * '''{{ll|PHP_configuration|PHP}}''' {{MW stable php requirement}}+ {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} ** MediaWiki requires some PHP extensions to be installed. These extensions are enabled in PHP by default. The MediaWiki installer will point out missing PHP extensions. See [[Manual:Installation requirements#PHP]] for a full list. * Jeden z následujících '''databázových serverů''': ** {{ll|Manual:MySQL|MySQL}} {{MW stable mysql requirement}}+ ** {{ll|Manual:MariaDB|MariaDB}} {{MW stable MariaDB requirement}}+ ** {{ll|Manual:PostgreSQL|PostgreSQL}} {{MW stable postgresql requirement}}+ ** {{ll|Manual:SQLite|SQLite}} {{MW stable sqlite requirement}}+ Další programy vyžadují [[Special:MyLanguage/Manual:image thumbnailing|miniatury obrázku]]. {{ll|Parsoid}} (vyžaduje [[Special:MyLanguage/VisualEditor|VisualEditor]]) a i jiné služby mají své vlastní požadavky.</li> <li>[[Special:MyLanguage/Download|Stáhněte si MediaWiki]] <small>({{MW stable release link|přímý odkaz na stažení aktuálního stabilního vydání}})</small> a umístěte archiv do složky, která může být přístupná z webu.</li> <li>Nasměrujte váš prohlížeč do adresáře, kam byla MediaWiki umístěna a postupujte podle pokynů na obrazovce. Mělo by to být ve formátu <code>http://''doména''/''adresář''/mw-config/index.php</code> Nahraďte příkaz ''adresář'' (directory) cestou do umístění vaší MediaWiki složky. Pokud instalujete do místního zařízení, nahraďte ''doména'' (domain) tímto textem: <code>localhost</code>. Pokud nainstalujete MediaWiki lokálně a poté chcete přistupovat k vaší wiki z ''domény'', musíte změnit LocalSetting.php z kódu <code>localhost</code> na ''doména''. Pokud je nainstalován na vzdáleném serveru, nahraďte ''doména'' jménem vaší domény (například www.example.com).</li> <li>Pro dokončení procesu [[Special:MyLanguage/Manual:Config script|postupujte podle pokynů na obrazovce]].</li> </ol> Tyto instrukce jsou úmyslně velmi stručné. Pokud máte pochybnosti, přečtěte si {{ll|Manual:Installing MediaWiki}}. <section end=short /><noinclude> {{clear}} {{anchor|Alternatives to manual installation|Alternative to manual installation}} == Alternativy k ruční instalaci == Ruční instalaci se můžete vyhnout využitím [[Special:MyLanguage/Software bundles#MediaWiki software appliances|automatizovaných instalačních balíčků]], [[Special:MyLanguage/Hosting services|některých hostingů se zjednodušenou instalací nebo wikifarem]]. {{Note|1=Hostingové služby, které poskytují automatickou instalaci aplikací, jako je MediaWiki, mohou nabízet zastaralé verze nebo mít jiné problémy. Pokud narazíte na problémy, ''neznamená to'', že nemůžete nainstalovat MediaWiki. To znamená, že byste měli nainstalovat MediaWiki ručně.}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == Přílohy == === Pokročilá konfigurace === Následující stránky popisují některé pokročilejší konfigurační možnosti: * {{ll|Manual:System administration#Configuration}} - Pokročilá konfigurace * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> For running several wikis or importing content into a MediaWiki installation, refer to [[Manual:FAQ#Installation and configuration]]. === Pomoc s instalací === * FAQ: [[Special:MyLanguage/FAQ#Installation and configuration|FAQ#Instalace a konfigurace]]. * {{ll|Manual:Common errors and symptoms#Installation Errors|2=MediaWiki installation errors}} * {{ll|Communication}} - Ask questions and receive help about installing MediaWiki === Pokyny pro konkrétní systémy === Stránky uvedené na {{ll|Manual:OS specific help}} poskytují podrobnější pokyny k instalaci zaměřené na konkrétní systémy. Celkově je však {{ll|Manual:Installing MediaWiki}} aktuálnější a lépe napsaná než dokumenty pro jednotlivé systémy a proto se doporučuje, abyste si nejprve prohlédli {{ll|Manual:Installing MediaWiki}}, než se podíváte na instalační dokumenty pro jednotlivé systémy. == Související stránky == * {{ll|Comparison of distribution options|2=Porovnání možností distribuce softwaru MediaWiki}} * {{ll|Manual:Uninstallation|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:MediaWiki Introduction{{#translation:}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] </noinclude> j6m4w7hjiclmhb1w0maz9emue0abgy4 5386472 5386470 2022-07-28T14:27:27Z ENeRZet 17359278 Created page with "Správa wiki" wikitext text/x-wiki <noinclude> <languages/> {{InstallationNav}} Tato příručka obsahuje pokyny k instalaci a konfiguraci MediaWiki, [[#Manual installation|návody]] a jednodušší [[#Alternatives to manual installation|alternativy]]. [[#Appendices|Dodatky]] poskytují odkazy na podrobnější poznámky k instalaci pro specifické konfigurace systému a další méně běžná použití softwaru. == Průvodce aktualizací == Pokud již MediaWiki používáte, podívejte se do [[Special:MyLanguage/Manual:Upgrading|příručky pro aktualizaci]]. {{anchor|Manual installation}} == Návod na instalaci == {{anchor|Summarized_installation_guide}} === Shrnutí === </noinclude> Pro zkušené uživatele je zde rychlá verze instalačních pokynů (například pokud nevíte, jak nainstalovat nebo zkontrolovat nezbytný software v počítači). Většina uživatelů, bude chtít [[#Main-installation-guide|postupovat podle průvodce základní instalací]]. <ol> <li>Zkontrolujte, zda váš systém splňuje následující minimální požadavky. ''(Podrobnosti najdete v [[Special:MyLanguage/Manual:Installation requirements|požadavcích na instalaci]]. Nezapomeňte také zkontrolovat požadavky v [[Special:MyLanguage/Release notes|POZNÁMKÁCH K VYDÁNÍ]] (relase notes) dodaných s MediaWiki.)'' Budete potřebovat: * [[Special:MyLanguage/Download|Stáhněte si]] MediaWiki (aktuální stabilní verze je {{MW stable release number}}) * '''Webový server''' jako [[Special:MyLanguage/Apache_configuration|Apache]] nebo [https://www.iis.net/ IIS] ** Kvůli spouštění údržbových skriptů je vyžadován přístup k příkazové řádce * '''{{ll|PHP_configuration|PHP}}''' {{MW stable php requirement}}+ {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} ** MediaWiki requires some PHP extensions to be installed. These extensions are enabled in PHP by default. The MediaWiki installer will point out missing PHP extensions. See [[Manual:Installation requirements#PHP]] for a full list. * Jeden z následujících '''databázových serverů''': ** {{ll|Manual:MySQL|MySQL}} {{MW stable mysql requirement}}+ ** {{ll|Manual:MariaDB|MariaDB}} {{MW stable MariaDB requirement}}+ ** {{ll|Manual:PostgreSQL|PostgreSQL}} {{MW stable postgresql requirement}}+ ** {{ll|Manual:SQLite|SQLite}} {{MW stable sqlite requirement}}+ Další programy vyžadují [[Special:MyLanguage/Manual:image thumbnailing|miniatury obrázku]]. {{ll|Parsoid}} (vyžaduje [[Special:MyLanguage/VisualEditor|VisualEditor]]) a i jiné služby mají své vlastní požadavky.</li> <li>[[Special:MyLanguage/Download|Stáhněte si MediaWiki]] <small>({{MW stable release link|přímý odkaz na stažení aktuálního stabilního vydání}})</small> a umístěte archiv do složky, která může být přístupná z webu.</li> <li>Nasměrujte váš prohlížeč do adresáře, kam byla MediaWiki umístěna a postupujte podle pokynů na obrazovce. Mělo by to být ve formátu <code>http://''doména''/''adresář''/mw-config/index.php</code> Nahraďte příkaz ''adresář'' (directory) cestou do umístění vaší MediaWiki složky. Pokud instalujete do místního zařízení, nahraďte ''doména'' (domain) tímto textem: <code>localhost</code>. Pokud nainstalujete MediaWiki lokálně a poté chcete přistupovat k vaší wiki z ''domény'', musíte změnit LocalSetting.php z kódu <code>localhost</code> na ''doména''. Pokud je nainstalován na vzdáleném serveru, nahraďte ''doména'' jménem vaší domény (například www.example.com).</li> <li>Pro dokončení procesu [[Special:MyLanguage/Manual:Config script|postupujte podle pokynů na obrazovce]].</li> </ol> Tyto instrukce jsou úmyslně velmi stručné. Pokud máte pochybnosti, přečtěte si {{ll|Manual:Installing MediaWiki}}. <section end=short /><noinclude> {{clear}} {{anchor|Alternatives to manual installation|Alternative to manual installation}} == Alternativy k ruční instalaci == Ruční instalaci se můžete vyhnout využitím [[Special:MyLanguage/Software bundles#MediaWiki software appliances|automatizovaných instalačních balíčků]], [[Special:MyLanguage/Hosting services|některých hostingů se zjednodušenou instalací nebo wikifarem]]. {{Note|1=Hostingové služby, které poskytují automatickou instalaci aplikací, jako je MediaWiki, mohou nabízet zastaralé verze nebo mít jiné problémy. Pokud narazíte na problémy, ''neznamená to'', že nemůžete nainstalovat MediaWiki. To znamená, že byste měli nainstalovat MediaWiki ručně.}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == Přílohy == === Pokročilá konfigurace === Následující stránky popisují některé pokročilejší konfigurační možnosti: * {{ll|Manual:System administration#Configuration}} - Pokročilá konfigurace * {{ll|Manual:Administrators}} - Správa wiki For running several wikis or importing content into a MediaWiki installation, refer to [[Manual:FAQ#Installation and configuration]]. === Pomoc s instalací === * FAQ: [[Special:MyLanguage/FAQ#Installation and configuration|FAQ#Instalace a konfigurace]]. * {{ll|Manual:Common errors and symptoms#Installation Errors|2=MediaWiki installation errors}} * {{ll|Communication}} - Ask questions and receive help about installing MediaWiki === Pokyny pro konkrétní systémy === Stránky uvedené na {{ll|Manual:OS specific help}} poskytují podrobnější pokyny k instalaci zaměřené na konkrétní systémy. Celkově je však {{ll|Manual:Installing MediaWiki}} aktuálnější a lépe napsaná než dokumenty pro jednotlivé systémy a proto se doporučuje, abyste si nejprve prohlédli {{ll|Manual:Installing MediaWiki}}, než se podíváte na instalační dokumenty pro jednotlivé systémy. == Související stránky == * {{ll|Comparison of distribution options|2=Porovnání možností distribuce softwaru MediaWiki}} * {{ll|Manual:Uninstallation|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:MediaWiki Introduction{{#translation:}}]] [[Category:Installation{{#translation:}}|{{PAGENAME}}]] </noinclude> 5ewvjy6kwv85fl736qixbdvitps1m7x 5386639 5386472 2022-07-28T17:14:23Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/cs]] srwqz7ma3qlny8ld00bl9dxg88cjc3y Template:InstallationNav/ja 10 18827 5387168 5384790 2022-07-28T21:14:41Z Shirayuki 472859 Created page with "MediaWiki のインストール" wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span class="mw-translate-fuzzy">インストール要件</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] 95hr6lnsjdea2ztmnmjfa9jibdb6439 5387170 5387168 2022-07-28T21:14:46Z Shirayuki 472859 Created page with "要件" wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=要件}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span class="mw-translate-fuzzy">インストール要件</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] 99botc853n7cq3qn81maetjhfr4s74l 5387172 5387170 2022-07-28T21:15:38Z Shirayuki 472859 Created page with "アップロード" wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=要件}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=アップロード}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span class="mw-translate-fuzzy">インストール要件</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] c7hwgp42s36l75g4hcdj0u0wz5i0a6g 5387174 5387172 2022-07-28T21:15:48Z Shirayuki 472859 Created page with "データベースをセットアップする" wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=要件}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=アップロード}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=データベースをセットアップする}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span class="mw-translate-fuzzy">インストール要件</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] todd3mslntpbmkak11d8vu0sa6fkwon 5387176 5387174 2022-07-28T21:15:50Z Shirayuki 472859 Created page with "インストール" wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=要件}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=アップロード}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=データベースをセットアップする}} &bull; <!-- -->{{ll|Manual:Config script|2=インストール}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span class="mw-translate-fuzzy">インストール要件</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] 5sz7k3a3x3871bvy04ske269eg7dsvk 5387179 5387176 2022-07-28T21:15:57Z Shirayuki 472859 Created page with "環境設定" wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=要件}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=アップロード}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=データベースをセットアップする}} &bull; <!-- -->{{ll|Manual:Config script|2=インストール}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=環境設定}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span class="mw-translate-fuzzy">インストール要件</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] c8fr0o9yp0euaisfupcp4k21xafsdul 5387181 5387179 2022-07-28T21:16:19Z Shirayuki 472859 Created page with "よくある質問" wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=要件}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=アップロード}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=データベースをセットアップする}} &bull; <!-- -->{{ll|Manual:Config script|2=インストール}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=環境設定}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= よくある質問}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span class="mw-translate-fuzzy">インストール要件</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] e23m1r3zpg2pdvbpop4e73byo1i8mim 5387203 5387181 2022-07-28T21:17:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=要件}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=アップロード}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=データベースをセットアップする}} &bull; <!-- -->{{ll|Manual:Config script|2=インストール}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=環境設定}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= よくある質問}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] f37ugxe3qayj6uiftb6g934a6nawby5 5387216 5387203 2022-07-28T21:17:54Z Shirayuki 472859 Created page with "ヘルプ/サポート" wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=MediaWiki のインストール}}:''' <!-- -->{{ll|Manual:Installation requirements|2=要件}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=アップロード}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=データベースをセットアップする}} &bull; <!-- -->{{ll|Manual:Config script|2=インストール}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=環境設定}} &bull; <!-- -->{{ll|Customization|2=カスタマイズ}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= よくある質問}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=ヘルプ/サポート}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] jfvmw2irihkd5nmnba88lmmqk4ewcmr Manual:Installation/ja 100 18829 5387810 294731 2022-07-29T09:27:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ja]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ja]] py2vi5h7xkgtxh7fx7e96mdawd1gx0m Manual:Installing MediaWiki/ja 100 18831 5387218 5384973 2022-07-28T21:20:05Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== <div class="mw-translate-fuzzy"> まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。 </div> ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 <span class="mw-translate-fuzzy">Apacheがインストール済みなら、正しいディレクトリを <code>httpd.conf</code> ファイルで指定してください([$docroot ドキュメントルート]は通常は $1 または {{$2|apacheフォルダー}} に設定されています)。</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 <span class="mw-translate-fuzzy">あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。</span> {{Note|1=<span class="mw-translate-fuzzy">'''''もしそれを[[Special:MyLanguage/Manual:Short URL|Short URL]]として使うのであれば、<code>/wiki/</code> は使わないでください。'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == データベースの作成 == </div> <div class="mw-translate-fuzzy"> MediaWikiからデータベースのユーザ名を聞かれ、もしそのユーザがまだ存在しなければ作成してよいか尋ねられます。 </div> <div class="mw-translate-fuzzy"> 既にデータベース サーバーがあり、その root パスワードを知っている場合、MediaWiki のインストール スクリプトはあなたのウィキ用の新しいデータベースを作成できます。 </div> <div class="mw-translate-fuzzy"> ホスト サーバーを使用している場合など、root パスワードが分からない場合は、今ここで新しいデータベースを作成する必要があるでしょう。 </div> <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] o1lxx3cbuemwabohzhxgera98d18kmk 5387224 5387218 2022-07-28T21:25:33Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 <span class="mw-translate-fuzzy">Apacheがインストール済みなら、正しいディレクトリを <code>httpd.conf</code> ファイルで指定してください([$docroot ドキュメントルート]は通常は $1 または {{$2|apacheフォルダー}} に設定されています)。</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 <span class="mw-translate-fuzzy">あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。</span> {{Note|1=<span class="mw-translate-fuzzy">'''''もしそれを[[Special:MyLanguage/Manual:Short URL|Short URL]]として使うのであれば、<code>/wiki/</code> は使わないでください。'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == データベースの作成 == </div> <div class="mw-translate-fuzzy"> MediaWikiからデータベースのユーザ名を聞かれ、もしそのユーザがまだ存在しなければ作成してよいか尋ねられます。 </div> <div class="mw-translate-fuzzy"> 既にデータベース サーバーがあり、その root パスワードを知っている場合、MediaWiki のインストール スクリプトはあなたのウィキ用の新しいデータベースを作成できます。 </div> <div class="mw-translate-fuzzy"> ホスト サーバーを使用している場合など、root パスワードが分からない場合は、今ここで新しいデータベースを作成する必要があるでしょう。 </div> <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] p399s6tgc4tjrhig3csaju4wyfm8c1l 5387226 5387224 2022-07-28T21:27:05Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 <span class="mw-translate-fuzzy">あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。</span> {{Note|1=<span class="mw-translate-fuzzy">'''''もしそれを[[Special:MyLanguage/Manual:Short URL|Short URL]]として使うのであれば、<code>/wiki/</code> は使わないでください。'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == データベースの作成 == </div> <div class="mw-translate-fuzzy"> MediaWikiからデータベースのユーザ名を聞かれ、もしそのユーザがまだ存在しなければ作成してよいか尋ねられます。 </div> <div class="mw-translate-fuzzy"> 既にデータベース サーバーがあり、その root パスワードを知っている場合、MediaWiki のインストール スクリプトはあなたのウィキ用の新しいデータベースを作成できます。 </div> <div class="mw-translate-fuzzy"> ホスト サーバーを使用している場合など、root パスワードが分からない場合は、今ここで新しいデータベースを作成する必要があるでしょう。 </div> <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] jjagxxgi5q5o522lold4dtc1gvlcp81 5387229 5387226 2022-07-28T21:27:29Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span class="mw-translate-fuzzy">'''''もしそれを[[Special:MyLanguage/Manual:Short URL|Short URL]]として使うのであれば、<code>/wiki/</code> は使わないでください。'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == データベースの作成 == </div> <div class="mw-translate-fuzzy"> MediaWikiからデータベースのユーザ名を聞かれ、もしそのユーザがまだ存在しなければ作成してよいか尋ねられます。 </div> <div class="mw-translate-fuzzy"> 既にデータベース サーバーがあり、その root パスワードを知っている場合、MediaWiki のインストール スクリプトはあなたのウィキ用の新しいデータベースを作成できます。 </div> <div class="mw-translate-fuzzy"> ホスト サーバーを使用している場合など、root パスワードが分からない場合は、今ここで新しいデータベースを作成する必要があるでしょう。 </div> <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] jmocedbzpjdqo274fh9etw3a3r58kfg 5387230 5387229 2022-07-28T21:27:42Z Shirayuki 472859 outdated wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == データベースの作成 == </div> <div class="mw-translate-fuzzy"> MediaWikiからデータベースのユーザ名を聞かれ、もしそのユーザがまだ存在しなければ作成してよいか尋ねられます。 </div> <div class="mw-translate-fuzzy"> 既にデータベース サーバーがあり、その root パスワードを知っている場合、MediaWiki のインストール スクリプトはあなたのウィキ用の新しいデータベースを作成できます。 </div> <div class="mw-translate-fuzzy"> ホスト サーバーを使用している場合など、root パスワードが分からない場合は、今ここで新しいデータベースを作成する必要があるでしょう。 </div> <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] hbnedbtaav2s57f7uwrxwe0hp4key90 5387232 5387230 2022-07-28T21:28:07Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == <div class="mw-translate-fuzzy"> MediaWikiからデータベースのユーザ名を聞かれ、もしそのユーザがまだ存在しなければ作成してよいか尋ねられます。 </div> <div class="mw-translate-fuzzy"> 既にデータベース サーバーがあり、その root パスワードを知っている場合、MediaWiki のインストール スクリプトはあなたのウィキ用の新しいデータベースを作成できます。 </div> <div class="mw-translate-fuzzy"> ホスト サーバーを使用している場合など、root パスワードが分からない場合は、今ここで新しいデータベースを作成する必要があるでしょう。 </div> <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] gdbkcfnweg5n2sutxrsp4yo2p7wzmli 5387234 5387232 2022-07-28T21:29:26Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 <div class="mw-translate-fuzzy"> 既にデータベース サーバーがあり、その root パスワードを知っている場合、MediaWiki のインストール スクリプトはあなたのウィキ用の新しいデータベースを作成できます。 </div> <div class="mw-translate-fuzzy"> ホスト サーバーを使用している場合など、root パスワードが分からない場合は、今ここで新しいデータベースを作成する必要があるでしょう。 </div> <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 1yq9oxtcd4z5wcgwycovqob5894dmbp 5387236 5387234 2022-07-28T21:30:46Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 <div class="mw-translate-fuzzy"> ホスト サーバーを使用している場合など、root パスワードが分からない場合は、今ここで新しいデータベースを作成する必要があるでしょう。 </div> <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] edieeiygs3pkwqycpjtrl1mv4nbiw9b 5387238 5387236 2022-07-28T21:31:43Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 <span class="mw-translate-fuzzy">現在、SQLite、MariaDB/MySQL、PostgreSQL のいずれかを使わなくてはいけません。</span> どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 4ookjw5hyi2mqnstuj2qro87qm9bs0d 5387240 5387238 2022-07-28T21:32:05Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 <span class="mw-translate-fuzzy">多くの場合、このデータベースユーザのユーザ名は'''postgres'''です。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 94fvitwlm4mwvgqgjftxffjxm7g67mi 5387242 5387240 2022-07-28T21:32:24Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 多くの場合、このデータベース ユーザーのユーザー名は <code>postgres</code> です。 <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==さらなる手順== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 02urtyoe9vxrncnwvtqtafhcm3c0r8d 5387244 5387242 2022-07-28T21:32:46Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 多くの場合、このデータベース ユーザーのユーザー名は <code>postgres</code> です。 <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> ==さらなる環境設定== * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|リリース告知メーリングリストに登録する。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] cou2l4ri3u6zfphg5g75eikizjs6d2h 5387246 5387244 2022-07-28T21:33:05Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 多くの場合、このデータベース ユーザーのユーザー名は <code>postgres</code> です。 <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> ==さらなる環境設定== * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|MediaWiki リリース告知メーリングリストに登録する。|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] lhbhcper00kg8dnnywkllgnl0dh5er2 5387248 5387246 2022-07-28T21:33:09Z Shirayuki 472859 Created page with "== 付録 ==" wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 多くの場合、このデータベース ユーザーのユーザー名は <code>postgres</code> です。 <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> ==さらなる環境設定== * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|MediaWiki リリース告知メーリングリストに登録する。|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == 付録 == {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} <span class="mw-translate-fuzzy">({{ll|comparison of distribution options}} を参照してください。)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] k9dct67ron8jzlfygajq8qwutpuc2gb 5387250 5387248 2022-07-28T21:33:52Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 多くの場合、このデータベース ユーザーのユーザー名は <code>postgres</code> です。 <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> ==さらなる環境設定== * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|MediaWiki リリース告知メーリングリストに登録する。|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == 付録 == {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} {{ll|comparison of distribution options}} も参照してください。 <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] j2l1xvws9zabycxzynsxmgn53nnlo33 5387252 5387250 2022-07-28T21:34:01Z Shirayuki 472859 Created page with "=== システム固有の手順 ===" wikitext text/x-wiki <languages/> {{InstallationNav}} <span lang="en" dir="ltr" class="mw-content-ltr">This page covers all steps to manually install and configure MediaWiki.</span> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 多くの場合、このデータベース ユーザーのユーザー名は <code>postgres</code> です。 <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> ==さらなる環境設定== * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|MediaWiki リリース告知メーリングリストに登録する。|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} == 付録 == {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} {{ll|comparison of distribution options}} も参照してください。 === システム固有の手順 === <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] k7o6i1vf20dmq2hw3dcsqatr9o2imes 5387500 5387252 2022-07-28T22:45:23Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == MediaWiki ソフトウェアのダウンロード == MediaWiki の tar ファイルを[[Special:MyLanguage/Download|公式ダウンロード ページ]]からダウンロードします。 一般に、本番環境を使用している場合は、最新の安定版リリースである MediaWiki {{MW stable release number}} を実行することをお勧めします。 == MediaWiki ソフトウェアを展開する == ダウンロードされたファイルは、<code>.zip</code> または <code>.tar.gz</code> のファイル形式です。 このアーカイブ ファイルを使用する前に、展開する必要があります。 ローカルで展開 (その後 FTP でサーバーにアップロード) することも、サーバーで直接展開することもできます。 これは通常、Windows 上では [https://www.7-zip.org/ 7-Zip] (無料)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]、[https://www.izarc.org/ IZArc] (無料) のようなソフトウェアで実施します。 Linux、Mac OS Xの場合、以下で解凍できます。 <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==サーバーへのファイルのアップロード== まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが <code>localhost</code> でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) ウェブ サーバーのウェブ ディレクトリに、以下のいずれかの方法でファイルをアップロードします: # zip解凍したフォルダを直接コピーする、または # [https://filezilla-project.org/ FileZilla] (Windows、OSX、Linux) や [https://cyberduck.io/ Cyberduck] (Windows、OSX) のような FTP クライアントを使って行う # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> アップロードツールに「ファイル名を小文字に変換する」オプションがある場合は、これをOFFにする必要があります。 Apache HTTPD Web サーバーを使用する場合、<code>httpd.conf</code> ファイルの [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] ディレクティブで正しいディレクトリを指定します。 <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> Debian および Ubuntu では、Apache サーバー設定のファイル名とディレクトリ名は <code>/etc/apache2/apache2.conf</code> です。 <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> アップロードしたファイルの名前をURLに含めたい名前に変更してください。 あなたのウェブ サーバーが例えば <code>http://localhost</code> で動作している場合、ディレクトリ名を <code>/w/</code> に変更すればあなたのウィキは <code>http://localhost/w/index.php</code> でアクセスできることになります。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == データベースをセットアップする == MediaWiki の[[Special:MyLanguage/Manual:Config script|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[#Run the installation script|#Run the installation script]] の節まで読み飛ばしてください。 root ユーザーのパスワードを知らない場合、例えば[[Special:MyLanguage/Hosting services|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 どのデータベースを選択すればいいか分からない場合は、MariaDB を使用してください。 After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> SQLite のインストール ページでは、データベース名(どんな値でも結構です)とSQLite データベース ディレクトリを指定します。 インストーラはデータベースディレクトリをドキュメントルートの外側にあるサブディレクトリに設定し、必要があれば作成しようとします。 ディレクトリが安全ではない(例えば、ウェブ上で閲覧できる)場合、 手動で設定を変更して誰でもウェブでアクセスできるということがないようにしてください。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. ホスティング プロバイダーの、対応する説明文書を参照してください。 あるいは[[Special:MyLanguage/Hosting services|ホスティング プロバイダー]]に連絡してあなたのアカウントを作成してもらっても構いません。 The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> データベースがウェブサーバーと異なるサーバー上で動作している場合のみ、適切なウェブ サーバーのホスト名 (下記の例では <code>mediawiki.example.com</code>) を指定する必要があります: <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB は、すべてのクエリを履歴ファイルに記録します。これにはユーザー アカウントのパスワードが含まれます。 これが気になる場合は、[https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL の説明文書]に従って、これらのクエリを実行した後に <code>.mysql_history</code> ファイルを削除して無効にしてください。}} ===PostgreSQL=== [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]] を使っているのであれば、データベースとあなたが作ったユーザが必要です。あるいは「superuser」権限を持つPostgreSQLユーザのユーザ名を設定フォームで指定しても結構です。 多くの場合、このデータベース ユーザーのユーザー名は <code>postgres</code> です。 <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (そしてパスワードを入力) createdb -O wikiuser my_wiki あるいは特権ユーザ(初期値はpostgres)でデータベースプロンプトにて以下のコマンドを実行します。 <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> [[phab:tag/postgreSQL|PostgreSQLを使ってMediaWikiを実行する場合における既知の問題一覧]]に書かれている内容に注意してください。 {{anchor|Run the installation script}} == インストールスクリプトの実行 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> ==さらなる環境設定== * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 最新の状態に保つ == インストールした後も、最新リリース版がインストールされた状態を維持し、サーバーを安全に保つようにしてください。 {{Clickable button 2|MediaWiki リリース告知メーリングリストに登録する。|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} == 付録 == {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=rootアカウントを作成する時、パスワードはあなたが覚えられるものにしてください。}} {{ll|comparison of distribution options}} も参照してください。 === システム固有の手順 === <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 関連項目 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] ruifuwng4osis0784u8bp9o3dhhttb3 Manual:Installation guide/ja 100 18835 5386657 5381092 2022-07-28T17:14:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ja]] py2vi5h7xkgtxh7fx7e96mdawd1gx0m Manual:Installing third-party tools/ja 100 18918 5387823 5377081 2022-07-29T09:29:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ja]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ja]] py2vi5h7xkgtxh7fx7e96mdawd1gx0m Template:InstallationNav/ru 10 19097 5387208 5384795 2022-07-28T21:17:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Installation/pt 0 19764 5387794 938628 2022-07-29T09:24:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/pt]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pt]] hm3bwmhq55v0f70dk8b7yp6vzij4nt5 Template:InstallationNav/fr 10 20046 5387197 5384785 2022-07-28T21:17:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installing MediaWiki/fr 100 20055 5387496 5384969 2022-07-28T22:45:20Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">MediaWiki peut sembler difficile à installer pour un utilisateur moyen qui n'a pas d'expérience Apache, PHP ou MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Télécharger le logiciel MediaWiki == <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> Le fichier téléchargé est dans le format <code>.zip</code> ou <code>.tar.gz</code>. <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> Vous pouvez décompresser le fichier localement (puis téléversér vers le serveur via FTP) ou directement sur votre serveur. Ceci est habituellement fait avec un logiciel du type [https://www.7-zip.org/ 7-Zip] (gratuit), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] ou [https://www.izarc.org/ IZArc] (gratuit) sous Windows. Sous Linux et Mac OS X, vous pouvez décompresser le fichier en usant la commande : <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == Téléverser les fichiers sur votre serveur == <div class="mw-translate-fuzzy"> Si vous n'avez pas encore téléversé les fichiers sur votre serveur web, c'est le moment de le faire. </div> Téléversez les fichiers vers le répertoire web de votre serveur web soit en : # copiant directement le répertoire décompressé, soit <div class="mw-translate-fuzzy"> # en utilisant un client FTP tel que [https://filezilla-project.org/ FileZilla] (logiciel Open Source, Windows, OSX et Linux) ou [https://cyberduck.io/ Cyberduck] (OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> Si votre outil de téléversement possède une option « modifier les noms de fichiers en minuscules », vous devez le désactiver. <span class="mw-translate-fuzzy">Si vous avez installé Apache, le répertoire correct est spécifié dans votre fichier <code>httpd.conf</code> (c'est la directive [$docroot DocumentRoot], généralement $1 ou {{$2|dossier-apache}}). C'est la racine principale de l'arborescence des documents visible depuis internet.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">{{note|Ceci a changé dans Ubuntu 14.04 avec Apache 2.4.7 où le fichier de configuration principal pour les paramètres du serveur Apache et les répertoires est <code>/etc/apache2/apache2.conf</code>.}}</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Renommez le répertoire téléversé selon le nom que vous voulez avoir dans l'URL. <span class="mw-translate-fuzzy">Si votre serveur web fonctionne en tant que <code>http://localhost</code> par exemple, le renommer en <code>/w/</code> voudrait dire que vous accèderiez à votre wiki avec <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span class="mw-translate-fuzzy">'''''N'utilisez pas <code>/wiki/</code> si vous souhaitez l'utiliser comme [[Special:MyLanguage/Manual:Short URL|URL courte]].'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Créer une base de données == </div> <div class="mw-translate-fuzzy"> MediaWiki vous demandera une base de données et un nom d'utilisateur et tentera de les créer s'ils n'existent pas déjà. </div> <div class="mw-translate-fuzzy"> Si vous disposez déjà d'un serveur de base de données et connaissez le mot de passe root pour y accéder, le script d'installation de MediaWiki peut créer une nouvelle base de données pour vous. </div> <div class="mw-translate-fuzzy"> Si vous ne connaissez pas le mot de passe root, par exemple si vous vous trouvez sur un serveur hébergé, vous devez créer une nouvelle base de données dès maintenant. </div> <span class="mw-translate-fuzzy">A ce moment, vous devrez utiliser SQLite, MariaDB/MySQL ou Postgres pour stocker le contenu actuel de votre wiki.</span> <span class="mw-translate-fuzzy">Si vous ne savez pas de quelle base de données il s'agit, choisissez MariaDB car c'est celle qui est la mieux prise en charge par MediaWiki.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">Sur la page d'installation, vous aurez besoin de choisir un nom de base de données (c'est vous qui voyez) et le répertoire de la base de données SQLite.</span> Pour le répertoire de la base de données, l'installateur tentera d'utiliser un sous-répertoire en dehors de la racine des documents ou le créera si nécessaire. Si ce répertoire n'est pas sécurisé (par exemple, lisible à partir du web), modifiez le manuellement pour empêcher de le rendre accessible à chacun à partir du web. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Voir la documentation associée.</span> <span class="mw-translate-fuzzy">Autrement, contactez votre fournisseur d'hébergement pour lui demander de vous créer un compte.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Si votre base de données ne s'exécute pas sur le même serveur que votre serveur web, vous devez indiquer le nom d'hôte du serveur web approprié &mdash; mediawiki.exemple.com dans l'exemple suivant &mdash; comme suit : </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL et MariaDB enregistrent toutes les requêtes dans un fichier historique, ce qui incluera le mot de passe utilisé pour le compte utilisateur. Si cela vous concerne, supprimez et désactivez le fichier <code>.mysql_history</code> après avoir exécuté ces requêtes en suivant la [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file documentation MySQL].}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Si vous utilisez PostgreSQL, vous aurez besoin soit de vous faire créer un utilisateur et une base de données ou simplement de donner le nom d'un utilisateur PostgreSQL avec les droits de ''superuser'' au script d'installation.</span> <span class="mw-translate-fuzzy">L'utilisateur de la base de données ayant ces privilèges s'appelle souvent '''postgres'''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (puis entrez le mot de passe) createdb -O wikiuser my_wiki Ou bien en tant que superutilisateur (par defaut postgres) exécutez les commandes suivantes à l'invite de la base de données : <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> Faites attention à la [[phab:tag/postgreSQL|liste des problèmes connus lorsque MediaWiki s'exécute avec PostgreSQL]]. {{anchor|Run the installation script}} == Exécuter le script d'installation == <div class="mw-translate-fuzzy"> Une fois toutes les étapes ci-dessus achevées, vous pouvez terminer l'installation depuis un navigateur web en vous rendant à l'URL index.php dans votre navigateur — voir les instructions dans {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> == Pour aller plus loin == </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Restez à jour ! == Une fois installé, assurez-vous de rester à jour au niveau des versions et gardez votre serveur sécurisé ! {{Clickable button 2|<span class="mw-translate-fuzzy">[[$maillist|Abonnez-vous à notre liste de diffusion concernant les annonces de diffusion des versions.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=Au moment de créer le compte initial, utilisez un mot de passe dont vous vous souviendrez.}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Voir aussi == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] ed7o8ut0m8mqahfb667iqfsqeerig9l Manual:Installation/fr 100 20057 5387809 196667 2022-07-29T09:26:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/fr]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/fr]] ezkxxg8g5rvukcyd6rc5fyrnipfeb8r Manual:Installation guide/fr 100 20078 5386650 5381088 2022-07-28T17:14:28Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/fr]] ezkxxg8g5rvukcyd6rc5fyrnipfeb8r Manual:Installation/ru 100 21174 5387815 161037 2022-07-29T09:27:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ru]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ru]] dszrz7cbezxeak88ngzg6sexsb1tipm Manual:$wgMaxCredits/ja 100 21183 5386442 5385412 2022-07-28T14:05:29Z AdamMillerchip 17433733 Created page with "ユーザーが最終編集時間順に表示される。" wikitext text/x-wiki <languages/> {{SettingSummary |name=MaxCredits |version_min=1.3.0 |section=Copyright |range=(整数) |default=0 |summary=記事のテキストの下に表示したい作者の人数を設定する。 }} == 詳細 == この変数では、記事のテキストの下 (フッター内) に表示したい作者の人数を設定します。 帰属ブロックを非表示にするには、この変数に 0 を設定してください。すべての作者を表示するには、負の値 (-1 など) を設定してください。 この設定は、ページ閲覧のたびに2~3回の余分なデータベース検索を必要とするため、大規模なウィキではパフォーマンスに'''かなり大きな'''影響を与える場合があることにご注意ください。 ユーザーが最終編集時間順に表示される。 <span lang="en" dir="ltr" class="mw-content-ltr">Example:</span> ''{{int|lastmodifiedatby|<tt>date</tt>|<tt>time</tt>|{{int|siteuser|XXX}}}} {{int|othercontribs|{{int|siteusers|Foo, Bar, Baz}}}}'' == 関連するシステム メッセージ == * [[MediaWiki:Lastmodifiedatby]] ({{int|lastmodifiedatby}}) * [[MediaWiki:Othercontribs]] ({{int|othercontribs}}) * [[MediaWiki:Siteusers]] ({{int|siteusers}}) * [[MediaWiki:Siteuser]] ({{int|siteuser}}) * [[MediaWiki:Anonymous]] ({{int|anonymous}}) * [[MediaWiki:Anonuser]] ({{int|anonuser}}) * [[MediaWiki:Anonusers]] ({{int|anonusers}}) == 関連項目 == * {{ll|Manual:$wgShowCreditsIfMax|$wgShowCreditsIfMax}} * {{ll|Extension:PageAuthors}} - <span lang="en" dir="ltr" class="mw-content-ltr">Gets a sensible list of the main page authors</span> 4xu7a95xbr78lmczrg1yb682dn3kiil 5386444 5386442 2022-07-28T14:05:41Z AdamMillerchip 17433733 Created page with "例:" wikitext text/x-wiki <languages/> {{SettingSummary |name=MaxCredits |version_min=1.3.0 |section=Copyright |range=(整数) |default=0 |summary=記事のテキストの下に表示したい作者の人数を設定する。 }} == 詳細 == この変数では、記事のテキストの下 (フッター内) に表示したい作者の人数を設定します。 帰属ブロックを非表示にするには、この変数に 0 を設定してください。すべての作者を表示するには、負の値 (-1 など) を設定してください。 この設定は、ページ閲覧のたびに2~3回の余分なデータベース検索を必要とするため、大規模なウィキではパフォーマンスに'''かなり大きな'''影響を与える場合があることにご注意ください。 ユーザーが最終編集時間順に表示される。 例: ''{{int|lastmodifiedatby|<tt>date</tt>|<tt>time</tt>|{{int|siteuser|XXX}}}} {{int|othercontribs|{{int|siteusers|Foo, Bar, Baz}}}}'' == 関連するシステム メッセージ == * [[MediaWiki:Lastmodifiedatby]] ({{int|lastmodifiedatby}}) * [[MediaWiki:Othercontribs]] ({{int|othercontribs}}) * [[MediaWiki:Siteusers]] ({{int|siteusers}}) * [[MediaWiki:Siteuser]] ({{int|siteuser}}) * [[MediaWiki:Anonymous]] ({{int|anonymous}}) * [[MediaWiki:Anonuser]] ({{int|anonuser}}) * [[MediaWiki:Anonusers]] ({{int|anonusers}}) == 関連項目 == * {{ll|Manual:$wgShowCreditsIfMax|$wgShowCreditsIfMax}} * {{ll|Extension:PageAuthors}} - <span lang="en" dir="ltr" class="mw-content-ltr">Gets a sensible list of the main page authors</span> 4k6ebkcehdb0s9g24477kbw7vuuvma6 Manual:Installing MediaWiki/ru 100 21224 5387505 5384977 2022-07-28T22:45:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">Установка MediaWiki может вызывать сложности у рядового пользователя компьютера, который не имеет опыта работы с Apache, PHP и MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Скачивание ПО MediaWiki == <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">Скачанные файлы будут в формате <code>.tar.gz</code>, так что будет нужно распаковать их перед использованием.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span class="mw-translate-fuzzy">Это может быть сделано локально (а потом загружено через FTP) или напрямую на вашем сервере.</span> Обычно это делается с помощью специального ПО, таким как [https://www.7-zip.org/ 7-Zip] (бесплатно), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] или [https://www.izarc.org/ IZArc] (бесплатно) в Windows. В Linux и Mac OS X, вы можете распаковать файл с помощью следующей команды: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == Загрузить файлы на Ваш сервер== <div class="mw-translate-fuzzy"> Если вы еще не залили файлы на веб-сервер, сделайте это сейчас. </div> Загрузите файлы в директорию на веб-сервере: # непосредственно копируя распакованную папку или <div class="mw-translate-fuzzy"> # используя FTP-клиент, такой как [https://filezilla-project.org/ FileZilla] (открытое программное обеспечение, Windows, OSX и Linux) или [https://cyberduck.io/ Cyberduck] (OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span class="mw-translate-fuzzy">Если вы установили Apache, правильная директория указана в файле <code>httpd.conf</code> (обычно это <code><apache-folder>/htdocs</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Примечание: начиная с Ubuntu 14:04 и Apache 2.4.7 файлом первичной конфигурации Apache является <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Создание базы данных == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div class="mw-translate-fuzzy"> Если у вас уже есть сервер базы данных, и вы знаете пароль от нее, скрипт установки MediaWiki может создать новую базу данных. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (затем введите пароль) createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Поддерживайте в актуальном состоянии! == <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=При создании root аккаунта, используйте пароль, который вы можете запомнить.}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == См. также == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 56wcrx7hjejokk7azbqsqr435u6mhu9 Project:Deliberately unused templates 4 21253 5387269 4720517 2022-07-28T21:51:43Z Pppery 5901069 /* Subst templates */ wikitext text/x-wiki {{outdated}} This page includes templates that we want to keep but which we do not actually want to include in any pages. Including them on this page helps to document ''why'' they are unused, and stops them appearing on [[Special:UnusedTemplates]]. == Subst templates == The following templates are designed to be included using {{magic word|code=1|nowrap=1|subst|<nowiki> ... </nowiki>}}, so any inclusion will not create a link back to the template. We don't want these showing up in the list, or being deleted. {{/include|Add-desc-E}} {{/include|Add-desc-I}} {{/include|Barnstar ExtensionsDev/Congrats}} {{/include|Barnstar ExtensionsDev/First}} {{/include|Barnstar ExtensionsDev/Thanks}} {{/include|Barnstar SysAdmins/Congrats}} {{/include|Barnstar SysAdmins/Launch}} {{/include|Barnstar SysAdmins/Thanks}} {{/include|CSD notice}} {{/include|Deleted userpage}} {{/include|Hackathon}} {{/include|InitDoc}} {{/include|InitCategory}} {{/include|Norecreate}} {{/include|Selfsubst|See [[Special:Search/insource:selfsubst]]}} {{/include|Selfsubst/now string}} {{/include|Selfsubst/ language/js}} {{/include|Uw-delete1}} {{/include|Uw-editsummary}} {{/include|Welcome-anon}} == User interface templates == The following templates are used either by the MediaWiki interface or to provide some extra UI functionality, but are not directly included on any page. {{/include|Abusefilter-blocked-display|Abuse filter notice appears when a user blocked from the wiki for doing bad things.}} {{/include|Anonblock|Used as the edit summary for some blocks.}} {{/include|Anontalkpagetext|Anonymous' user talk page notice.}} {{/include|Anontools|Used to look at the anonymous' contributions, like IP location, IP range, etc.}} {{/include|Brokenredirectstext|It is used to look at the [[Special:BrokenRedirects]].}} {{/include|Core Platform 10 Percent Project|Used as the preload for the "create new project" box on [[Core Platform Team/Development Practices/10% time]].}} {{/include|Documentation/mirror}} {{/include|Documentation/preload}} {{/include|Documentation/preload-module-doc}} {{/include|Documentation/preload-module-sandbox}} {{/include|Documentation/preload-module-testcases}} {{/include|Documentation/preload-testcases}} {{/include|Editinginterface|Used to MediaWiki: namespaces when a user is trying to edit the MediaWiki interface or viewing.}} {{/include|Extension/Sample|Used by the input-box extension as the default text when creating new extension pages.}} {{/include|Newarticletext|Used when a user is about to create a non-existed page.}} {{/include|Protectedinterface|Used when a page is protected while a regular user is not administrator or bureaucrat.}} {{/include|Proxy|Used as the edit summary for some blocks.}} {{/include|Recentchangestext|Used in [[Special:RecentChanges]].}} {{/include|RfC template}} {{/include|Rightslogtext|Used in [[Special:Log/rights]].}} {{/include|Skin/Sample}} {{/include|Sp-contributions-footer|Used for user's contribution page tools.}} {{/include|Sp-contributions-footer-anon|Used for anonymous' contribution page tools.}} {{/include|Unusedtemplatestext|Used in [[Special:UnusedTemplates]].}} == Translated admin templates == The following templates are translations of English-language admin templates, which should never be included on actual pages (the English version should always be used). No decision has yet been made about whether it is useful to keep these translations, so they may all be deleted in the future, but in the mean-time they are included here to stop them showing up in the list. {{/include|Obsolete/de}} {{/include|Outdated/de}} {{/include|Outdated/fr}} {{/include|Outdated/nl}} {{/include|Outdated/ru}} {{/include|Speedy/de}} {{/include|Speedy/es}} {{/include|Speedy/fr}} {{/include|Speedy/it}} {{/include|Speedy/ru}} == Temporarily unused == Templates that are sometimes unused, to stop them being accidentally deleted when this is the case. {{/include|Main page/site news|Used when we need to display site news on the main page, unused when we don't.}} {{/include|Unmaintained extension|Used to tag unmaintained and/or abandoned extensions, but it may be that there are none.}} {{/include|Deprecated|Used to mark deprecated features. If these are removed the template will also be removed, potentially leaving it unused.}} {{/include|Undocumented configuration setting|Sometimes there are no undocumented configuration settings}} {{/include|Undocumented MediaWiki Hook|Sometimes there are no undocumented MediaWiki hooks}} {{/include|Undocumented Extension Hook|Sometimes there are no undocumented extension hooks}} {{/include|Badtrans}} {{/include|Delete|Deletion template|3=}} {{/include|Speedy|Speedy-deletion template|3=}} {{/include|VisualEditor:Test/Text}} {{/include|Error}} {{/include|Error:must be substituted}} == Miscellaneous == {{/include|Foo|This template is used as an example on [[Extension:LoopFunctions]].}} {{/include|Test TD}} {{/include|Wikidata Infobox|Multi-site page, see [[Multilingual Templates and Modules]]}} {{#if:{{Module:Universal infocard}}}}[[Module:Universal infocard]] - Multi-site page, see [[Multilingual Templates and Modules]] [[Category:Maintenance{{#translation:}}]] [[Category:Templates]] hti389kpd0npkkwlaen83wl47siup0l Help talk:Editing 13 21762 5387699 4549619 2022-07-29T05:56:49Z 2402:8100:224D:6B45:894D:FCAD:3EA4:EE3E /* MediaWiki hardcoded page name. Redirected */ wikitext text/x-wiki {{help talk}} On September 13, 1948, Hyderabad was invaded by India, and within four days Hyderabad's accession to India was achieved. After a period of military and provisional civil government, a popular ministry and legislature were set up in the state in March 1952.This was how Sardar Vallabhbhai Patel exulted after India’s Agent General K M Munshi informed him of the Nizam’s ‘no’ to a proposal by Mountbatten. This was exactly what the ‘Iron Man’ (Sardar Patel) needed to justify the Police Action or Operation Polo that led to the fall of the princely state of Hyderabad and its accession to the Indian Union this day 73 years agoVallabhbhai Jhaverbhai Patel (Gujarati: [ʋəlːəbːʰɑi dʒʰəʋeɾbʰɑi pəʈel]; pə-TEL; 31 October 1875 – 15 December 1950), endeared as Sardar,[a] was an Indian lawyer, influential political leader and statesman who served as the first Deputy Prime Minister of India from 1947 to 1950. He is also called the "Unifier of India".[1] The Statue of Unity, the ruling BJP government erected world's tallest statue at a cost of USD420 million, was dedicated to him on 31 October 2018 and is approximately 182 metres (597 ft) in height.[2] He was a barrister and a senior leader of the Indian National Congress, who played a leading role in the country's struggle for independence, guiding its integration into a united, independent nation.[3] He was one of the conservative members of the Indian National Congress. In India and elsewhere, he was often called Sardar, meaning "chief" in Hindi, Urdu, and Persian. He acted as the Home Minister during the political integration of India and the Indo-Pakistani War of 1947 == How to edit a page with translations markup == Current translations documentation is oriented towards translations administrators, translation extension managers, and translations applications for translators. Editors need there own or section in Help:editing. *It should be compact and concentrate on the syntax and grammar of &lt;translate> <tvar>, <!--T:##--> and other translations markup. *It should focus on the needs of editors. Perhaps a section in Help:Editing. Translations markings on a page discourage editing. There is no documentation for translations whose audience is editors. * It should bring pages such as Help:CirrusSearch, back to life, "edited by anyone, mercilessly" as the proven saying goes. Help:CirrusSearch is a ghost town, yet Search is a hot technology -- you can get a college degree in it -- and Elastica is a hot open source movement. Help:Searching on Wikipedia has little or nothing on CirrusSearch, perhaps as a result of Help:CirrusSearch paralysis. As an editor at Help:CirrusSearch I struggled with 1) the documentation on translations and 2) with unresponsive translations "editors" for months before becoming fed up with it and removing it. Documenting how to edit a page with translations will prove that translations and translators care about editing, not just translations. [[User:Cpiral|Cpiral]] ([[User talk:Cpiral|talk]]) 19:11, 29 September 2015 (UTC) == Strange Link to "Help:Talk pages" == I apologize but I'm not familiar enough with the translation/localization systems to fix it myself. The link to "Help:Talk pages" under the Editing header currently shows as a nonsensical ".8:;" instead of simply saying "Talk pages". This should be fixed. Thank you! --[[User:Squingynaut|Squingynaut]] ([[User talk:Squingynaut|talk]]) 15:03, 29 April 2021 (UTC) 9y4u0rppbnnkohdocwlvk7m4nxcgiyv 5387702 5387699 2022-07-29T06:02:10Z 2402:8100:224D:6B45:894D:FCAD:3EA4:EE3E /* Strange Link to "Help:Talk pages" */ wikitext text/x-wiki {{help talk}} On September 13, 1948, Hyderabad was invaded by India, and within four days Hyderabad's accession to India was achieved. After a period of military and provisional civil government, a popular ministry and legislature were set up in the state in March 1952.This was how Sardar Vallabhbhai Patel exulted after India’s Agent General K M Munshi informed him of the Nizam’s ‘no’ to a proposal by Mountbatten. This was exactly what the ‘Iron Man’ (Sardar Patel) needed to justify the Police Action or Operation Polo that led to the fall of the princely state of Hyderabad and its accession to the Indian Union this day 73 years agoVallabhbhai Jhaverbhai Patel (Gujarati: [ʋəlːəbːʰɑi dʒʰəʋeɾbʰɑi pəʈel]; pə-TEL; 31 October 1875 – 15 December 1950), endeared as Sardar,[a] was an Indian lawyer, influential political leader and statesman who served as the first Deputy Prime Minister of India from 1947 to 1950. He is also called the "Unifier of India".[1] The Statue of Unity, the ruling BJP government erected world's tallest statue at a cost of USD420 million, was dedicated to him on 31 October 2018 and is approximately 182 metres (597 ft) in height.[2] He was a barrister and a senior leader of the Indian National Congress, who played a leading role in the country's struggle for independence, guiding its integration into a united, independent nation.[3] He was one of the conservative members of the Indian National Congress. In India and elsewhere, he was often called Sardar, meaning "chief" in Hindi, Urdu, and Persian. He acted as the Home Minister during the political integration of India and the Indo-Pakistani War of 1947 == How to edit a page with translations markup == Current translations documentation is oriented towards translations administrators, translation extension managers, and translations applications for translators. Editors need there own or section in Help:editing. *It should be compact and concentrate on the syntax and grammar of &lt;translate> <tvar>, <!--T:##--> and other translations markup. *It should focus on the needs of editors. Perhaps a section in Help:Editing. Translations markings on a page discourage editing. There is no documentation for translations whose audience is editors. * It should bring pages such as Help:CirrusSearch, back to life, "edited by anyone, mercilessly" as the proven saying goes. Help:CirrusSearch is a ghost town, yet Search is a hot technology -- you can get a college degree in it -- and Elastica is a hot open source movement. Help:Searching on Wikipedia has little or nothing on CirrusSearch, perhaps as a result of Help:CirrusSearch paralysis. As an editor at Help:CirrusSearch I struggled with 1) the documentation on translations and 2) with unresponsive translations "editors" for months before becoming fed up with it and removing it. Documenting how to edit a page with translations will prove that translations and translators care about editing, not just translations. [[User:Cpiral|Cpiral]] ([[User talk:Cpiral|talk]]) 19:11, 29 September 2015 (UTC) In the 1901 Census of the British Indian Empire, the population of the princely state of Kashmir was 2,905,578. Of these 2,154,695 were Muslims, 689,073 Hindus, 25,828 Sikhs, and 35,047 Buddhists. The Hindus were found mainly in Jammu, where they constituted a little less than 50% of the population.[99] In the Kashmir Valley, the Hindus represented "only 524 in every 10,000 of the population (i.e. 5.24%), and in the frontier wazarats of Ladhakh and Gilgit only 94 out of every 10,000 persons (0.94%)."[99] In the same Census of 1901, in the Kashmir Valley, the total population was recorded to be 1,157,394, of which the Muslim population was 1,083,766, or 93.6% of the population.[99] These percentages have remained fairly stable for the last 100 years.[100] In the 1941 Census of British India, Muslims accounted for 93.6% of the population of the Kashmir Valley and the Hindus constituted 4%.[100] In 2003, the percentage of Muslims in the Kashmir Valley was 95%[101] and those of Hindus 4%; the same year, in Jammu, the percentage of Hindus was 67% and those of Muslims 27%.[101] Among the Muslims of the Kashmir province within the princely state, four divisions were recorded: "Shaikhs, Saiyids, Mughals, and Pathans. The Shaikhs, who are by far the most numerous, are the descendants of Hindus, but have retained none of the caste rules of their forefathers. They have clan names known as krams ..."[102] It was recorded that these kram names included "Tantre", "Shaikh", "Bat", "Mantu", "Ganai", "Dar", "Damar", "Lon", etc. The Saiyids, it was recorded, "could be divided into those who follow the profession of religion and those who have taken to agriculture and other pursuits. Their kram name is 'Mir.' While a Saiyid retains his saintly profession Mir is a prefix; if he has taken to agriculture, Mir is an affix to his name."[102] The Mughals who were not numerous were recorded to have kram names like "Mir" (a corruption of "Mirza"), "Beg", "Bandi", "Bach" and "Ashaye". Finally, it was recorded that the Pathans "who are more numerous than the Mughals, ... are found chiefly in the south-west of the valley, where Pathan colonies have from time to time been founded. The most interesting of these colonies is that of Kuki-Khel Afridis at Dranghaihama, who retain all the old customs and speak Pashtu."[102] Among the main tribes of Muslims in the princely state are the Butts, Dar, Lone, Jat, Gujjar, Rajput, Sudhan and Khatri. A small number of Butts, Dar and Lone use the title Khawaja and the Khatri use the title Shaikh the Gujjar use the title of Chaudhary. All these tribes are indigenous of the princely state which converted to Islam from Hinduism during its arrival in region. Among the Hindus of Jammu province, who numbered 626,177 (or 90.87% of the Hindu population of the princely state), the most important castes recorded in the census were "Brahmans (186,000), the Rajputs (167,000), the Khattris (48,000) and the Thakkars (93,000)."[ odr19e6d98jfmuaq46sl9ng8ezboczw 5387703 5387702 2022-07-29T06:04:01Z 2402:8100:224D:6B45:894D:FCAD:3EA4:EE3E /* How to edit a page with translations markup */ wikitext text/x-wiki {{help talk}} On September 13, 1948, Hyderabad was invaded by India, and within four days Hyderabad's accession to India was achieved. After a period of military and provisional civil government, a popular ministry and legislature were set up in the state in March 1952.This was how Sardar Vallabhbhai Patel exulted after India’s Agent General K M Munshi informed him of the Nizam’s ‘no’ to a proposal by Mountbatten. This was exactly what the ‘Iron Man’ (Sardar Patel) needed to justify the Police Action or Operation Polo that led to the fall of the princely state of Hyderabad and its accession to the Indian Union this day 73 years agoVallabhbhai Jhaverbhai Patel (Gujarati: [ʋəlːəbːʰɑi dʒʰəʋeɾbʰɑi pəʈel]; pə-TEL; 31 October 1875 – 15 December 1950), endeared as Sardar,[a] was an Indian lawyer, influential political leader and statesman who served as the first Deputy Prime Minister of India from 1947 to 1950. He is also called the "Unifier of India".[1] The Statue of Unity, the ruling BJP government erected world's tallest statue at a cost of USD420 million, was dedicated to him on 31 October 2018 and is approximately 182 metres (597 ft) in height.[2] He was a barrister and a senior leader of the Indian National Congress, who played a leading role in the country's struggle for independence, guiding its integration into a united, independent nation.[3] He was one of the conservative members of the Indian National Congress. In India and elsewhere, he was often called Sardar, meaning "chief" in Hindi, Urdu, and Persian. He acted as the Home Minister during the political integration of India and the Indo-Pakistani War of 1947 == How to edit a page with translations markup == Current translations documentation is oriented towards translations administrators, translation extension managers, and translations applications for translators. Editors need there own or section in Help:editing. *It should be compact and concentrate on the syntax and grammar of &lt;translate> <tvar>, <!--T:##--> and other translations markup. *It should focus on the needs of editors. Perhaps a section in Help:Editing. Translations markings on a page discourage editing. There is no documentation for translations whose audience is editors. * It should bring pages such as Help:CirrusSearch, back to life, "edited by anyone, mercilessly" as the proven saying goes. Help:CirrusSearch is a ghost town, yet Search is a hot technology -- you can get a college degree in it -- and Elastica is a hot open source movement. Help:Searching on Wikipedia has little or nothing on CirrusSearch, perhaps as a result of Help:CirrusSearch paralysis. As an editor at Help:CirrusSearch I struggled with 1) the documentation on translations and 2) with unresponsive translations "editors" for months before becoming fed up with it and removing it. Documenting how to edit a page with translations will prove that translations and translators care about editing, not just translations. [[User:Cpiral|Cpiral]] ([[User talk:Cpiral|talk]]) 19:11, 29 September 2015 (UTC) In the 1901 Census of the British Indian Empire, the population of the princely state of Kashmir was 2,905,578. Of these 2,154,695 were Muslims, 689,073 Hindus, 25,828 Sikhs, and 35,047 Buddhists. The Hindus were found mainly in Jammu, where they constituted a little less than 50% of the population.[99] In the Kashmir Valley, the Hindus represented "only 524 in every 10,000 of the population (i.e. 5.24%), and in the frontier wazarats of Ladhakh and Gilgit only 94 out of every 10,000 persons (0.94%)."[99] In the same Census of 1901, in the Kashmir Valley, the total population was recorded to be 1,157,394, of which the Muslim population was 1,083,766, or 93.6% of the population.[99] These percentages have remained fairly stable for the last 100 years.[100] In the 1941 Census of British India, Muslims accounted for 93.6% of the population of the Kashmir Valley and the Hindus constituted 4%.[100] In 2003, the percentage of Muslims in the Kashmir Valley was 95%[101] and those of Hindus 4%; the same year, in Jammu, the percentage of Hindus was 67% and those of Muslims 27%.[101] Among the Muslims of the Kashmir province within the princely state, four divisions were recorded: "Shaikhs, Saiyids, Mughals, and Pathans. The Shaikhs, who are by far the most numerous, are the descendants of Hindus, but have retained none of the caste rules of their forefathers. They have clan names known as krams ..."[102] It was recorded that these kram names included "Tantre", "Shaikh", "Bat", "Mantu", "Ganai", "Dar", "Damar", "Lon", etc. The Saiyids, it was recorded, "could be divided into those who follow the profession of religion and those who have taken to agriculture and other pursuits. Their kram name is 'Mir.' While a Saiyid retains his saintly profession Mir is a prefix; if he has taken to agriculture, Mir is an affix to his name."[102] The Mughals who were not numerous were recorded to have kram names like "Mir" (a corruption of "Mirza"), "Beg", "Bandi", "Bach" and "Ashaye". Finally, it was recorded that the Pathans "who are more numerous than the Mughals, ... are found chiefly in the south-west of the valley, where Pathan colonies have from time to time been founded. The most interesting of these colonies is that of Kuki-Khel Afridis at Dranghaihama, who retain all the old customs and speak Pashtu."[102] Among the main tribes of Muslims in the princely state are the Butts, Dar, Lone, Jat, Gujjar, Rajput, Sudhan and Khatri. A small number of Butts, Dar and Lone use the title Khawaja and the Khatri use the title Shaikh the Gujjar use the title of Chaudhary. All these tribes are indigenous of the princely state which converted to Islam from Hinduism during its arrival in region. Among the Hindus of Jammu province, who numbered 626,177 (or 90.87% of the Hindu population of the princely state), the most important castes recorded in the census were "Brahmans (186,000), the Rajputs (167,000), the Khattris (48,000) and the Thakkars (93,000)."[ राजेश पायलट भारतीय राष्ट्रीय कांग्रेस से सबंध एक राजनेता है।उसका नाम था राजेश्वर प्रसाद बिधूरी जो बाद में राजेश पायलट के नाम से मशहूर हुआ। 1974 में उनकी रमा पायलट से शादी हुई।वे पूर्व केन्द्रीय मंत्री तथा राजस्थान के दौसा लोक सभा निर्वाचन क्षेत्र से कई बार सांसद रहे है।राजेश पायलटजी ने 1971 के भारत-पाक युद्ध में भारतीय वायुसेना कि तरफ महत्वपूर्ण भूमिका निभाई थी। परंतु जन सेवा की भावना से प्रेरित होकर वायुसेना से इस्तीफा देकर राजनीति में प्रवेश किया था। 1980 में भरतपुर से सांसद चुने गये और 1984,1991,1996,1998 एवं 1999 दौसा से सांसद चुने गये। 20 साल तक सांसद रहे। जब 1984 में राजीव गाँधी प्रधानमंत्री बने, तो उन्होंने उन्हें भूतल राज्यमंत्री बनाया। उत्तरपूर्व और कश्मीर दोनों राजेश पायलट के बहुत प्रिय विषय थे। कश्मीर में सामान्य स्थिति लाने के लिए उन्होंने अपनी तरफ़ से काफ़ी कोशिश की., हाँलाकि वहाँ उन पर कई हमले भी हुए। राजेश पायलट को भारतीय राजनीति में अभी बहुत कुछ करना था लेकिन मात्र 55 वर्ष की आयु में एक सड़क दुर्घटना में उनका असामयिक निधन हो गया. उस समय वो गाड़ी को खुद ड्राइव कर रहे थे.[1][2] myhib7reffyrnrlgc6h8ld94zwrlzsv 5387756 5387703 2022-07-29T08:25:21Z ~aanzx 17539795 Reverted 3 edits by [[Special:Contributions/2402:8100:224D:6B45:894D:FCAD:3EA4:EE3E|2402:8100:224D:6B45:894D:FCAD:3EA4:EE3E]] ([[User talk:2402:8100:224D:6B45:894D:FCAD:3EA4:EE3E|talk]]): Junk edit (TwinkleGlobal) wikitext text/x-wiki {{help talk}} == MediaWiki hardcoded page name. Redirected == The page title "[[Help:Editing]]" is an important one which is kind of hardcoded into the mediawiki software. While editing a page, a link appears below the box "Editing help (opens in new window)". So it's kind of ugly to have that redirecting as it is here at the moment. Now I'm aware that this is controlleable by sysops, who can edit the 'System Messages' page [[MediaWiki:Edithelppage]]. But there's added dimension to the problem, because these help pages are supposed to be copyable into other wikis. See [[Project:PD help]]. This means we need to make sure that the redirect gets copied, so I guess it should be added to [[Help:Copying#File_list]] (although can you even export/import redirects? never tried it) But this means ugly redirects get copied to all these various other wiki installations. Now we could recommend they ''also'' use sysop permissions to edit ''their'' [[MediaWiki:Edithelppage]] page. But this all starts to seem a bit messy. I think the best solution is going to be to rethink the page naming such that there is something on the "[[Help:Editing]]" page (not just a redirect) Maybe move [[Help:Editing pages]] to here. -- [[User:Harry Wood|Harry Wood]] 16:49, 5 December 2007 (UTC) :...But then again... I realise there's lots of translation pages for [[Help:Editing pages]]. These would also need to move, so that's a bit of hassle. -- [[User:Harry Wood|Harry Wood]] 09:54, 11 December 2007 (UTC) ::Maybe it's best just to go back to what it was; an abbreviated index of editing topics. It shouldn't be linked from the index, since it is redundant, but just be used as another entry point to the help system -[[User:Sanbeg|Steve Sanbeg]] 18:43, 19 December 2007 (UTC) :::Ah yeah. That works. -- [[User:Harry Wood|Harry Wood]] 09:58, 20 December 2007 (UTC) == How to edit a page with translations markup == Current translations documentation is oriented towards translations administrators, translation extension managers, and translations applications for translators. Editors need there own or section in Help:editing. *It should be compact and concentrate on the syntax and grammar of &lt;translate> <tvar>, <!--T:##--> and other translations markup. *It should focus on the needs of editors. Perhaps a section in Help:Editing. Translations markings on a page discourage editing. There is no documentation for translations whose audience is editors. * It should bring pages such as Help:CirrusSearch, back to life, "edited by anyone, mercilessly" as the proven saying goes. Help:CirrusSearch is a ghost town, yet Search is a hot technology -- you can get a college degree in it -- and Elastica is a hot open source movement. Help:Searching on Wikipedia has little or nothing on CirrusSearch, perhaps as a result of Help:CirrusSearch paralysis. As an editor at Help:CirrusSearch I struggled with 1) the documentation on translations and 2) with unresponsive translations "editors" for months before becoming fed up with it and removing it. Documenting how to edit a page with translations will prove that translations and translators care about editing, not just translations. [[User:Cpiral|Cpiral]] ([[User talk:Cpiral|talk]]) 19:11, 29 September 2015 (UTC) == Strange Link to "Help:Talk pages" == I apologize but I'm not familiar enough with the translation/localization systems to fix it myself. The link to "Help:Talk pages" under the Editing header currently shows as a nonsensical ".8:;" instead of simply saying "Talk pages". This should be fixed. Thank you! --[[User:Squingynaut|Squingynaut]] ([[User talk:Squingynaut|talk]]) 15:03, 29 April 2021 (UTC) 63gyl77liid50856awzi7w8evu5d8ii Manual:Installation guide/es 100 21858 5386647 5381083 2022-07-28T17:14:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/es]] 2gqtb4xa5rfmo3773s65aritcwisa9u Manual:Installation guide/ru 100 22224 5386666 5381105 2022-07-28T17:14:35Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ru]] dszrz7cbezxeak88ngzg6sexsb1tipm Manual:Installation guide/it 100 23008 5386655 5381572 2022-07-28T17:14:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/it]] tqhmp7ofn2m4czho71m8f239k3y1wuq Template:InstallationNav/ko 10 23079 5387205 5384791 2022-07-28T21:17:32Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installation guide/ko 100 23081 5386656 5381094 2022-07-28T17:14:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ko]] 2mv5oubsjsrbcsagzy12ozik9wg3xf7 Manual:Installing MediaWiki/ko 100 23094 5387501 5384974 2022-07-28T22:45:24Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">미디어위키는 Apache, PHP, MySQL/MariaDB 경험이 없는 일반 사용자가 설치하기는 어려울 수 있습니다.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == 미디어위키 소프트웨어 다운로드 == [[Special:MyLanguage/Download|공식 다운로드 페이지]]에서 미디어위키 tar 파일 다운로드합니다. 일반적으로 프로덕션 환경을 사용하는 경우, 최신 안정 릴리즈인 MediaWiki {{MW stable release number}}을 실행하길 원합니다. <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">다운로드한 파일은 <code>.tar.gz</code> 파일 형식이며, 사용하기 전에 압축을 풀어야 합니다.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == 파일을 업로드하기 == <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == 데이터베이스 만들기 == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (저기에 비밀번호를 입력하세요) createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} == 설치 스크립트 실행 == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 같이 보기 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] nb9ezhui40vys1mou4nh0ovkyx7bc00 Manual:Installation guide/pl 100 23300 5386662 5381101 2022-07-28T17:14:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pl]] b6zf9uu302z9prb61dalq114ribkgg6 Template:InstallationNav/it 10 23303 5387202 5384788 2022-07-28T21:17:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installing MediaWiki/it 100 23459 5387497 5385461 2022-07-28T22:45:22Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> MediaWiki può essere difficile da installare se non si ha esperienza con Apache (software web server), PHP e MySQL/MariaDB (database). <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Download del software MediaWiki == Scaricare il file tar MediaWiki dalla [[Special:MyLanguage/Download|pagina ufficiale di download]]. Generalmente, se si utilizza un ambiente di produzione, si vuole eseguire l'ultima versione stabile, che è MediaWiki {{MW stable release number}}. <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> I file scaricati sono nel formato <code>.zip</code> o <code>.tar.gz</code>. <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> È possibile decomprimere il file localmente (e poi caricarlo via FTP sul server) o direttamente sul server. In Windows puoi farlo con programmi come [https://www.7-zip.org/ 7-Zip] (libero), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] o [https://www.izarc.org/ IZArc] (libero). Su Linux e Mac OS X, puoi decomprimere il file utilizzando questo comando: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==Caricare i file sul server== Se non avete ancora caricato i file sul vostro [[Special:MyLanguage/Manual:Installation requirements#Web server|server web]] (o copiato, se il software del server web gira localmente sul vostro <code>localhost</code>), fatelo ora. Caricare i file nella directory web del server web tramite: # Copiando direttamente la cartella decompressa oppure # Mediante un client FTP come [https://filezilla-project.org/ FileZilla] (Windows, OSX e Linux) o [https://cyberduck.io/ Cyberduck] (Windows e OSX). # utilizzando il software già fornito dal tuo [[Special:MyLanguage/Hosting services|servizio di hosting]], come ''cPanel File Manager'' Se il tuo strumento per il caricamento ha un'opzione "modifica i nomi file in minuscolo", lo devi disabilitare. Se stai utilizzando il web server Apache HTTPD, la directory corretta è specificata nel tuo file <code>httpd.conf</code> nella direttiva [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>]. <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> In Debian e Ubuntu, il file per le impostazioni e le directory del server Apache è <code>/etc/apache2/apache2.conf</code>. <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} == Impostare il database == <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Vedi anche == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] kh9cdh5tfuq04amke4dlegnfwyshzn7 Installation/tr 0 24309 5387800 1378814 2022-07-29T09:25:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/tr]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/tr]] 5f585xjemd904uqfsrqnejiy5zjz0jz Template:InstallationNav/zh 10 25074 5387214 5384801 2022-07-28T21:17:36Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=-{zh:自訂; zh-hans:自定义; zh-hant:自訂;}-}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] f19716k2ljwaw91ynkw8wj2xlmuufng Template:InstallationNav/pl 10 25492 5387204 5384793 2022-07-28T21:17:32Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installation guide/pt 100 25807 5386663 5381098 2022-07-28T17:14:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pt]] hm3bwmhq55v0f70dk8b7yp6vzij4nt5 Template:InstallationNav/pt 10 25808 5387207 5384792 2022-07-28T21:17:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Installation/sv 0 26957 5387798 1378815 2022-07-29T09:25:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/sv]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/sv]] 6ygndy3khxczu516p8ywc2msv9xo5v0 Manual:Installation guide/he 100 27615 5386651 5381087 2022-07-28T17:14:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/he]] temgau06ur1pm0dsv0i46lav0z66875 5386692 5386651 2022-07-28T17:26:18Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/he]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Installation/nl 0 28340 5387792 1378816 2022-07-29T09:24:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Installation/uk 100 29296 5387816 202936 2022-07-29T09:28:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Installation guide/uk 100 29297 5386674 5381113 2022-07-28T17:14:38Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/uk]] koiq9d6txly1i0ac2dzgw6ijd6owklw 5386689 5386674 2022-07-28T17:25:41Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/uk]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Template:InstallationNav/uk 10 29298 5387212 5384799 2022-07-28T21:17:35Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installing MediaWiki/de 100 29586 5387492 5384965 2022-07-28T22:45:18Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">Die Installation von MediaWiki kann für den durchschnittlichen Computeranwender schwierig werden, der keine Erfahrung mit Apache, PHP und MySQL/MariaDB hat.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Herunterladen der MediaWiki-Software == Lade die MediaWiki tar-Datei von der [[Special:MyLanguage/Download|offiziellen Download-Seite]] herunter. Wenn du eine Produktionsumgebung verwendest, sollte man in der Regel die aktuellste stabile Version (MediaWiki {{MW stable release number}}) einsetzen. == Extrahiere die MediaWiki-Software == Die heruntergeladene Datei liegt im <code>.zip</code>- oder im <code>.tar.gz</code>-Format vor. Du musst diese Archivdatei vor der Verwendung entpacken. Du kannst die Datei lokal entpacken (und dann per FTP auf den Server hochladen) oder direkt auf deinem Server entpacken. Unter Windows werden dafür gewöhnlich Programme wie [https://www.7-zip.org/ 7-Zip] (quelltextoffene Software), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] oder [https://www.izarc.org/ IZArc] benutzt. Unter Linux und Mac OS X kannst du die Datei entpacken (untar), indem du folgenden Befehl anwendest: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==Dateien auf den Server hochladen== <div class="mw-translate-fuzzy"> Wenn du die Dateien noch nicht auf deinen Webserver hochgeladen hast, tu dies jetzt. </div> Lade die Dateien in das Webverzeichnis deines Webservers hoch, in dem du entweder: # das entpackte Verzeichnis direkt kopierst oder <div class="mw-translate-fuzzy"> # einen FTP-Clienten wie [https://filezilla-project.org/ FileZilla] (Open Source Software, Windows, OSX und Linux) oder [https://cyberduck.io/ Cyberduck] (OSX) nutzt. </div> # <span class="mw-translate-fuzzy">cPanel File Manager benutzt ([[Special:MyLanguage/Hosting services|siehe unten]])</span> Wenn dein Kopier- oder FTP-Programm eine Option zur Umwandlung des Dateinamens in Kleinbuchstaben hat (change file names to lowercase), musst du diese ausschalten. <span class="mw-translate-fuzzy">Wenn du Apache installiert hast, steht das korrekte Verzeichnis in deiner <code>httpd.conf</code>-Datei (es ist die [$docroot DocumentRoot]-Richtlinie, normalerweise $1 oder {{$2|apache-folder}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Hinweis: Dies änderte sich in Ubuntu 14.04 mit Apache 2.4.7, wo die ursprüngliche Konfigurationsdatei für Apache-Server-Einstellungen und -Verzeichnisse <code>/etc/apache2/apache2.conf</code> ist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Benenne den hochgeladenen Ordner (oder den symbolischen Link) so um, wie du ihn in der URL haben willst. <span class="mw-translate-fuzzy">Wenn dein Web-Server z.&nbsp;B. wie <code>http://localhost</code> läuft, würde eine Umbenennung zu einem <code>/w/</code>-Verzeichnis bedeuten, dass du dein Wiki über <code>http://localhost/w/index.php</code> erreichst.</span> {{Note|1=<span class="mw-translate-fuzzy">'''''Benutze nicht <code>/wiki/</code>, wenn du es als einen [[Special:MyLanguage/Manual:Short URL|Kurzlink]] benutzen möchtest.'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Eine Datenbank erstellen == </div> <div class="mw-translate-fuzzy"> MediaWiki wird dich nach der Datenbank und dem Benutzernamen fragen und versuchen, diese zu erstellen, wenn sie noch nicht vorhanden sind. </div> <div class="mw-translate-fuzzy"> Sofern du das root-Passwort deiner Datenbank kennst, kann das Installationsprogramm von MediaWiki eine Datenbank für dich erstellen. </div> <div class="mw-translate-fuzzy"> Wenn du das root-Passwort nicht kennst, z.&nbsp;B. wenn du auf einem gemieteten Server bist, musst du eine neue Datenbank erzeugen. </div> <span class="mw-translate-fuzzy">Derzeit musst du entweder MariaDB/MySQL oder Postgres benutzen, um die aktuellen Inhalte des Wikis zu speichern.</span> <span class="mw-translate-fuzzy">Wenn du dir nicht sicher bist, welche Datenbank du auswählen sollst, benutze MariaDB, da diese am besten von MediaWiki unterstützt wird.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">Auf der Installationsseite musst du einen Datenbanknamen (ein frei wählbarer Name) und das SQLite-Datenbankverzeichnis auswählen.</span> Für das Datenbankverzeichnis versucht das Installationsprogramm, ein Unterverzeichnis außerhalb des Dokument-Root-Verzeichnisses zu benutzen und erstellt es bei Bedarf. Wenn dieses Verzeichnis nicht sicher ist (z.&nbsp;B. für das Web lesbar), dann solltest du es manuell ändern, damit es nicht für das gesamte Web zugänglich ist. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Siehe die entsprechende Dokumentation.</span> <span class="mw-translate-fuzzy">Alternativ kann auch der Host-Provider ein Konto für dich einrichten.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Wenn deine Datenbank nicht auf dem gleichen Server wie dein Webserver läuft, musst du den zugehörigen Webserverhostnamen – im folgenden Beispiel ''mediawiki.example.com'' – wie folgt eingeben: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span class="mw-translate-fuzzy">MySQL/MariaDB unter UNIX/Linux protokolliert alle Abfragen, die an die Datenbank gesendet werden, in einer Datei, die auch das Passwort enthält, das für das Benutzerkonto verwendet wird.</span> Wenn das für dich bedenklich ist, lösche und deaktiviere die <code>.mysql_history</code>-Datei, nachdem du diese Abfragen ausgeführt hast, indem du die [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL-Dokumentation] befolgst.}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Wenn du PostgreSQL verwendest, musst du entweder eine Datenbank und einen Benutzer für dich erstellen lassen oder einfach den Namen eines PostgreSQL-Benutzers mit „Superuser“-Rechten in das Konfigurationsformular eingeben.</span> <span class="mw-translate-fuzzy">Dieser Datenbankbenutzer wird häufig '''postgres''' genannt.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (gib dann das Passwort ein) createdb -O wikiuser my_wiki oder du gibst, als Superuser (standardmäßig „postgres“), die folgenden Befehle in die Datenbank-Eingabezeile ein: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> '''Achtung:''' die [[phab:tag/postgreSQL|Liste bekannter Probleme beim Betrieb von MediaWiki mit PostgreSQL]] sollte beachtet werden. {{anchor|Run the installation script}} == Das Installationsskript ausführen == <div class="mw-translate-fuzzy"> Wenn alle oben genannten Schritte abgeschlossen sind, kann die Installation über einen Webbrowser abgeschlossen werden, indem die URL der index.php im Browser aufgerufen wird – bitte die in {{ll|Manual:Config script}} beschriebenen Anweisungen beachten. </div> <div class="mw-translate-fuzzy"> == Nächste Schritte == </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Auf dem Laufenden bleiben == Einmal installiert, sollte man immer auf dem Laufenden bleiben, was die neuen Versionen angeht, und seinen Server entsprechend schützen! {{Clickable button 2|<span class="mw-translate-fuzzy">[[$maillist|Abonniere unsere Mailingliste über Mitteilungen zu Versionsankündigungen.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Siehe auch == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 46qaojslof291f3jkcgnd1dgod7o8la Template:InstallationNav/de 10 30446 5387193 5384778 2022-07-28T21:17:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=Anpassung}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] 9230m3ybbkmj5slr64rvj1nx62jh5fi Installation/uk 0 30473 5387801 1378817 2022-07-29T09:25:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Installation guide/de 100 30656 5386641 5381746 2022-07-28T17:14:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/de]] d5kmxqmeba5eoob88wqnq12eaf1a6rj Manual:Installing MediaWiki/zh 100 30889 5387509 5384982 2022-07-28T22:45:28Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">如果没有 Apache, PHP 和 MySQL/MariaDB 的使用经验的话,安装 MediaWiki 可能会很吃力。</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == 下载 MediaWiki 软件 == 从 [[Special:MyLanguage/Download|official download page]]下载MediaWiki tar文件 <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">下载的文件是 <code>.tar.gz</code> 格式,所以在使用前需要先从压缩文件中提取。</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span class="mw-translate-fuzzy">可以在本地提取并上传到服务器,或者上传压缩包然后在服务器上提取,或者直接在服务器上下载并提取.</span> 在Windows上,这通常由[https://www.7-zip.org/ 7-Zip](免费)、[http://www.winzip.com/ WinZip]、[https://www.rarlab.com/ WinRAR]或[https://www.izarc.org/ IZArc](免费)来完成。 Linux 和 macOS 系统上可以通过这个命令来提取: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==上传文件到你的服务器== <div class="mw-translate-fuzzy"> 如果尚未将文件上载到Web服务器,请立即执行此操作。 </div> 通过以下方式将文件上传到Web服务器的Web目录: # 直接复制解压的文件夹或 <div class="mw-translate-fuzzy"> #使用FTP客户端,如[https://filezilla-project.org/ FileZilla](开源软件、Windows、OSX和Linux)或[https://cyberduck.io/ Cyberduck](OSX)。 </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> 如果您的上传工具有“将文件名更改为小写”选项,则必须禁用此选项。 <span class="mw-translate-fuzzy">如果您安装了Apache,则会在<code>httpd.conf</code>文件中指定正确的目录(它是[$docroot DocumentRoot]指令,通常是<code>/var/www/</code>或<code><apache-folder>/htdocs</code>)。</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">注意:这在Ubuntu 14.04 与Apache 2.4.7的中发生了变化,其中Apache服务器设置和目录的主要配置文件是<code>/etc/apache2/apache2.conf</code>。</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> 将上传的文件夹重命名为您希望在URL中拥有的任何内容。 <span class="mw-translate-fuzzy">如果您的Web服务器以<code>http://localhost</code>运行,例如,重命名为<code>/w/</code>目录意味着你将在<code>http://localhost/w/index.php</code>访问你的wiki。</span> {{Note|1=<span class="mw-translate-fuzzy">'''如果您希望将其用作[[Special:MyLanguage/Manual:Short URL|缩短URL]]的话,不要使用<code>/wiki/</code>。'''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> ==创建数据库== </div> <div class="mw-translate-fuzzy"> MediaWiki将询问您是否有数据库和用户名,如果它们尚不存在,将尝试创建它们。 </div> <div class="mw-translate-fuzzy"> 如果您已有数据库服务器并且知道它的root密码,则MediaWiki安装脚本可以为您创建新数据库。 </div> <div class="mw-translate-fuzzy"> 如果您不知道root密码,例如,如果您在托管服务器上,则必须立即创建新数据库。 </div> <span class="mw-translate-fuzzy">目前,您必须使用SQLite、MariaDB、MySQL或PostgreSQL来存储Wiki的实际内容。</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">在安装页面上,您需要选择数据库名称(可以是任何内容)和SQLite数据库目录。</span> 对于数据库目录,安装程序将尝试使用文档根目录之外的子目录,并在需要时创建它。 如果此目录不安全(例如Web可读),请手动更改它以避免Web上的每个人都可以访问它。 ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">请参阅相应的文档。</span> <span class="mw-translate-fuzzy">或者,与您的主机提供商联系,让他们为您创建一个帐户。</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> 如果您的数据库未在与Web服务器相同的服务器上运行,则需要提供相应的Web服务器主机名,以下示例中的mediawiki.example.com,如下: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span class="mw-translate-fuzzy">UNIX/Linux上的MySQL/MariaDB将发送给它的所有查询记录到一个文件中,该文件将包含您用于该用户帐户的密码。</span> <span class="mw-translate-fuzzy">如果这与您有关,请在运行这些查询后删除<code>.mysql_history</code>文件。</span>}} ===PostgreSQL=== <span class="mw-translate-fuzzy">如果您使用的是PostgreSQL,则需要为您创建数据库和用户,或者只是为配置表单提供具有“超级用户”权限的PostgreSQL用户的名称。</span> <span class="mw-translate-fuzzy">通常,这是名为'''postgres'''的数据库用户。</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (然后输入密码) createdb -O wikiuser my_wiki 或者作为超级用户(默认postgres)在数据库提示符下执行以下命令: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> 注意[[phab:tag/postgreSQL|使用PostgreSQL运行MediaWiki时已知问题的列表]]。 {{anchor|Run the installation script}} == 启动安装脚本 == <div class="mw-translate-fuzzy"> 完成上述所有步骤后,您可以通过浏览器中的index.php通过Web浏览器完成安装:查看{{ll|Manual:Config script}}中提到的说明。 </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == 保持最新! == 安装后,请确保您及时了解版本,并确保您的服务器安全! {{Clickable button 2|<span class="mw-translate-fuzzy">[[$maillist|订阅我们的发布公告邮件列表。]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=当你创建根账户时,使用一个你能够记住的密码。}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == 参见 == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 2lezhean65223oylr9z4isd4rsxjtel Installation/el 0 31528 5387782 1378818 2022-07-29T09:22:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u User talk:MarcoAurelio 3 32274 5387903 5021496 2022-07-29T11:05:34Z MarcoAurelio 36007 [[User talk:MarcoAurelio/Archives/2020|archived]] wikitext text/x-wiki <div class="borderc8 backgroundc1" style="padding:0.3em 0.5em 0.3em 0.5em; border-style:solid; border-width:medium"> [[File:MediaWiki.svg|right|180px|link=Main Page]] <span style="color:teal; font-size:140%;">'''Welcome to [[Special:MyLanguage/Project:About|<span style="color:teal; ">MediaWiki.org</span>]]!'''</span> <br /> <br /> Yes, welcome! This site is dedicated to documenting the [[Special:MyLanguage/How does MediaWiki work?|MediaWiki software]], the software behind many wikis, including that of [[w:|Wikipedia]] and the [[wikimedia:Our projects|Wikimedia Foundation projects]]. <br /> Please, take a look at the following pages. They might prove useful to you as a newcomer here: *[[Special:MyLanguage/Communication#Landing|Landing instructions]] *[[Special:MyLanguage/Project:About|Project:About]] *[[Special:MyLanguage/How does MediaWiki work?|How does MediaWiki work?]] *[[Special:MyLanguage/Help:Editing pages|Help:Editing pages]] *[[Special:MyLanguage/Manual:FAQ|Frequently asked questions]] *[[Special:MyLanguage/How to contribute|How to contribute]] *[[Special:MyLanguage/Project:Policy|Policies]] </div> ---- {{Archive box| * [[/Archives/2016|2016]] * [[/Archives/2019|2019]] * [[/Archives/2020|2020]] }} rsqek7vk1gbt8ajbbgix0w0h63m2iz4 Manual:Installation guide/ca 100 35388 5386638 5381075 2022-07-28T17:14:23Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ca]] b9f6tlf0wmlb1f9vcbxcxapr7ob2eqy Template:InstallationNav/ca 10 35440 5387189 5384774 2022-07-28T21:17:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Template:InstallationNav/yue 10 35514 5387213 5384800 2022-07-28T21:17:35Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installation guide/yue 100 35518 5386676 5381115 2022-07-28T17:14:39Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/yue]] ro85k36xvrojv0ws1m4zevk4n3e78do Manual:Installation guide/pt-br 100 35552 5386664 5381429 2022-07-28T17:14:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pt-br]] fkiaxxukhcv6mkzadk6rrcpdrqpm9ci Template:InstallationNav/pt-br 10 35555 5387206 5384794 2022-07-28T21:17:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Installation/pt-br 0 35675 5387795 1378819 2022-07-29T09:24:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/pt-br]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pt-br]] fkiaxxukhcv6mkzadk6rrcpdrqpm9ci Manual:Installing MediaWiki/ca 100 35713 5387490 5384963 2022-07-28T22:45:16Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">MediaWiki pot ser difícil d'instal·lar per a l'usuari mitjà que no té experiència amb Apache, PHP i MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 9olyp4gr7y867i8iunkbzmesfzj68ta Manual:Installing MediaWiki/pt-br 100 36201 5387504 5384976 2022-07-28T22:45:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">Pode ser difícil instalar o MediaWiki para um usuário médio, sem experiência com Apache, PHP e MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Baixar o software MediaWiki == Baixe o arquivo tar do MediaWiki da [[Special:MyLanguage/Download|página oficial de baixar]]. Geralmente, se estiver usando um ambiente de produção, você deseja executar a versão estável mais recente, que é MediaWiki {{MW stable release number}}. <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">Os arquivos baixados estarão no formato <code>.tar.gz</code>, então deverão ser descomprimidos antes de serem usados.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span class="mw-translate-fuzzy">Isto pode ser feito localmente (e então subido via FTP) ou diretamente em seu servidor.</span> No Windows, a descompactação pode ser feita com programas como [https://www.7-zip.org/ 7-Zip] (grátis), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] ou [https://www.izarc.org/ IZArc] (grátis). No Linux e Mac OS X, você pode descompactar o arquivo usando este comando: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == Fazer upload de arquivos para seu sevidor == <div class="mw-translate-fuzzy"> Se você ainda não carregou os arquivos para seu servidor web, carregue agora. </div> É possível fazer o upload dos arquivos para o diretório de seu servidor web: # copiando diretamente a pasta descompactada ou <div class="mw-translate-fuzzy"> # usando um cliente FTP como [https://filezilla-project.org/ FileZilla] (Software de código aberto, com versões para Windows, OSX e Linux) ou [https://cyberduck.io/ Cyberduck] (OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> Se sua ferramenta de carregamento tiver uma opção "alterar nomes de arquivo para minúsculas", então você deve desabilitar isso. <span class="mw-translate-fuzzy">Se você instalou o Apache, o diretório correto é especificado em seu <code>httpd.conf</code> file (é o diretiva, tipicamente $1 ou {{$2|apache-folder}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Nota: Isso mudou em Ubuntu 14.04 com Apache 2.4.7 onde o arquivo de configuração primário para configurações e diretórios do servidor Apache é <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Renomeie a pasta que subiu como você quiser que seja na URL. <span class="mw-translate-fuzzy">Se seu servidor web estiver rodando como <code>http://localhost</code> por exemplo, ao renomear o diretório para <code>/w/</code> significará que você acessará seu wiki em <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span class="mw-translate-fuzzy">'''''Não use <code>/wiki/</code> se desejar usá-la como uma [[Special:MyLanguage/Manual:Short URL|Short URL]].'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Criar uma base de dados == </div> <div class="mw-translate-fuzzy"> O MediaWiki solicitará a base de dados e nome de usuário, e tentará criá-los, se não existirem ainda. </div> <div class="mw-translate-fuzzy"> Se você já tem um servidor de base de dados e sabe a senha do root para ele, o instalador do MediaWiki poderá criar uma nova base de dados pra você. </div> <div class="mw-translate-fuzzy"> Se você não sabe a senha de root, por exemplo, se está em um servidor do provedor, você terá de criar uma nova base de dados agora. </div> <span class="mw-translate-fuzzy">Atualmente, você deve usar SQLite, MariaDB/MySQL ou PostgreSQL para armazenar o conteúdo de sua wiki.</span> <span class="mw-translate-fuzzy"> Se você não tiver certeza sobre qual banco de dados escolher, use o MariaDB, pois é o melhor suportado pelo MediaWiki.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">Na página de instalação, você deverá escolher o nome da base de dados (que pode ser qualquer um) e o diretório da base de dados SQLite.</span> Para o diretório da base de dados, o instalador tentará usar um subdiretório fora do document root, e irá criá-lo se necessário. Se este diretório não for seguro (por exemplo, puder ser lido via web), mude-o manualmente para evitar que fique acessível a todos na web. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Consulte a documentação correspondente.</span> <span class="mw-translate-fuzzy">Opcionalmente, entre em contato com seu provedor para que eles criem esta conta para você.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Se sua base de dados não estiver rodando no mesmo servidor de ser servidor web, você precisará fornecer o hostname de seu servidor web -- mediawiki.example.com no meu exemplo -- como se segue: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span class="mw-translate-fuzzy">O MySQL/MariaDB no UNIX/Linux registra todas queries enviadas a ele em um arquivo, que incluirá a senha que você usou para a conta do usuário.</span> <span class="mw-translate-fuzzy">Se isto for preocupante para você, apague seu arquivo <code>.mysql_history</code> após rodar estas queries.</span>}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Se você estiver usando o PostgreSQL, precisará, ou ter uma base de dados e usuário já criados para você, ou simplesmente fornecer o nome de um usuário do PostgreSQL com privilégios de "superusuário" para efetuar a configuração.</span> <span class="mw-translate-fuzzy">Geralmente, este usuário tem o nome '''postgres'''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (então insira a senha) createdb -O wikiuser my_wiki ou como superusuário (que por padrão é postgres) execute os seguintes comandos no prompt da base de dados: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> Atenção para a [[phab:tag/postgreSQL|lista de problemas conhecidos ao rodar o MediaWiki com PostgreSQL]]. {{anchor|Run the installation script}} == Executar o script de instalação == <div class="mw-translate-fuzzy"> Uma vez completados os passos acima, você poderá completar a instalação através do navegador de internet, acessando a URI index.php em seu navegador -- verifique as instruções mencionadas em {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> ==Próximas etapas== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Mantenha atualizado! == Uma vez instalado, tenha certeza de manter atualizado, e manter seu servidor seguro! {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|Assine nosso mailing list de avisos de lançamentos.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=Ao criar uma conta root, use uma senha que você se lembrará.}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Ver também == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 1dgb82mkgs43e2xnkwo6r1m78h1agyc Installation/ar 0 37025 5387777 1378820 2022-07-29T09:21:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Help:Bots 12 38687 5386240 5379369 2022-07-28T12:22:50Z 2601:644:4480:EFD0:49D4:706E:8046:E22 /* See also */ wikitext text/x-wiki <languages /> {{PD Help Page}} <translate><!--T:1--> A '''bot''' is a computer program that automatically retrieves or updates wiki pages when it is executed.</translate> <translate><!--T:19--> In general, bots are used for repetitive maintenance tasks, whose volume and characteristics are too large to be performed manually by users.</translate> <translate> <!--T:2--> Developing and executing bots is normally outside the role of normal users, requires programming experience and must be done in coordination with the wiki's [[<tvar|1>Special:MyLanguage/Help:Sysops and permissions</>|admins]]. <!--T:3--> By default, bot edits are hidden in <tvar|1>[[Special:RecentChanges]]</>. == Framework and interface for bot development == <!--T:4--> </translate> <translate><!--T:5--> Bots do not access the wiki through the normal graphical user interface.</translate> <translate><!--T:20--> MediaWiki has an API (Application Programming Interface) available for this purpose.</translate> <translate><!--T:21--> An API is a protocol for standardized communication between two computer programs.</translate> <translate><!--T:22--> Check <tvar|1>{{ll|API:Client code}}</> for more information.</translate> <translate> <!--T:6--> To access a wiki through the API a bot must have a user account which has been granted 'bot' [[<tvar|1>Special:MyLanguage/Help:User rights and groups</>|permissions]]. </translate> === pywikibot === <translate> <!--T:8--> <tvar|5>{{ll|Manual:Pywikibot|Pywikibot}}</> provides a framework for the development of bots, which are commonly used to perform maintenance tasks such as adding a footer to some categorized pages (<tvar|6>{{ll|Manual:pywikibot/add text.py|add_text.py}}</>), adding some [[<tvar|7>Special:MyLanguage/Help:Links</>|wikilinks]] (<tvar|1>{{ll|Manual:pywikibot/replace.py|replace.py}}</>), moving old contents of [[<tvar|8>Special:MyLanguage/Help:Talk pages</>|talk pages]] to [[<tvar|9>Special:MyLanguage/Help:Subpages</>|subpages]] (<tvar|2>{{ll|Manual:pywikibot/archivebot.py|archivebot.py}}</>), editing [[<tvar|10>Special:MyLanguage/Help:Categories</>|categories]] (<tvar|3>{{ll|Manual:pywikibot/category.py|category.py}}</>), or managing [[<tvar|11>Special:MyLanguage/Help:Templates</>|templates]] (<tvar|4>{{ll|Manual:pywikibot/template.py|template.py}}</>). </translate> === wiki-java === <translate><!--T:10--> <tvar|url>[https://github.com/mer-c/wiki-java wiki-java]</> is a lightweight Java framework for bot/application development and can be used to perform various tasks, such as uploading files, adding text to articles, parsing templates, basic I/O, etc.</translate> <translate><!--T:23--> The library also comes with simple, but powerful standalone bot methods that can be readily utilized by a programmer.</translate> <translate> === Chris G's botclasses === <!--T:16--> <!--T:17--> [[<tvar|1>Special:MyLanguage/Manual:Chris G's botclasses</>|Chris G's botclasses]] compose a PHP MediaWiki bot framework hosted at the toolserver. == Extension alternatives == <!--T:11--> </translate> * {{ll|Extension:MassEditRegex}} — <translate><!--T:12--> provides an alternative way to perform mass edits using regular expressions, through a special page in the wiki.</translate> <translate><!--T:24--> Only admins can normally use this extension.</translate> * {{ll|Extension:Replace Text}} — <translate><!--T:13--> another option.</translate> <translate> == See also == <!--T:14--> </translate> * Bplwu it[[m:Special:MyLanguage/Bot|<translate><!--T:18--> m:Bot</translate>]] [[Category:Help{{#translation:}}|{{PAGENAME}}]] 7s9p1npcwdmcf7rsdp8airxv6y0ul8s 5386241 5386240 2022-07-28T12:23:09Z Tegel 154870 Reverted edits by [[Special:Contribs/2601:644:4480:EFD0:49D4:706E:8046:E22|2601:644:4480:EFD0:49D4:706E:8046:E22]] ([[User talk:2601:644:4480:EFD0:49D4:706E:8046:E22|talk]]) to last version by Clump wikitext text/x-wiki <languages /> {{PD Help Page}} <translate><!--T:1--> A '''bot''' is a computer program that automatically retrieves or updates wiki pages when it is executed.</translate> <translate><!--T:19--> In general, bots are used for repetitive maintenance tasks, whose volume and characteristics are too large to be performed manually by users.</translate> <translate> <!--T:2--> Developing and executing bots is normally outside the role of normal users, requires programming experience and must be done in coordination with the wiki's [[<tvar|1>Special:MyLanguage/Help:Sysops and permissions</>|admins]]. <!--T:3--> By default, bot edits are hidden in <tvar|1>[[Special:RecentChanges]]</>. == Framework and interface for bot development == <!--T:4--> </translate> <translate><!--T:5--> Bots do not access the wiki through the normal graphical user interface.</translate> <translate><!--T:20--> MediaWiki has an API (Application Programming Interface) available for this purpose.</translate> <translate><!--T:21--> An API is a protocol for standardized communication between two computer programs.</translate> <translate><!--T:22--> Check <tvar|1>{{ll|API:Client code}}</> for more information.</translate> <translate> <!--T:6--> To access a wiki through the API a bot must have a user account which has been granted 'bot' [[<tvar|1>Special:MyLanguage/Help:User rights and groups</>|permissions]]. </translate> === pywikibot === <translate> <!--T:8--> <tvar|5>{{ll|Manual:Pywikibot|Pywikibot}}</> provides a framework for the development of bots, which are commonly used to perform maintenance tasks such as adding a footer to some categorized pages (<tvar|6>{{ll|Manual:pywikibot/add text.py|add_text.py}}</>), adding some [[<tvar|7>Special:MyLanguage/Help:Links</>|wikilinks]] (<tvar|1>{{ll|Manual:pywikibot/replace.py|replace.py}}</>), moving old contents of [[<tvar|8>Special:MyLanguage/Help:Talk pages</>|talk pages]] to [[<tvar|9>Special:MyLanguage/Help:Subpages</>|subpages]] (<tvar|2>{{ll|Manual:pywikibot/archivebot.py|archivebot.py}}</>), editing [[<tvar|10>Special:MyLanguage/Help:Categories</>|categories]] (<tvar|3>{{ll|Manual:pywikibot/category.py|category.py}}</>), or managing [[<tvar|11>Special:MyLanguage/Help:Templates</>|templates]] (<tvar|4>{{ll|Manual:pywikibot/template.py|template.py}}</>). </translate> === wiki-java === <translate><!--T:10--> <tvar|url>[https://github.com/mer-c/wiki-java wiki-java]</> is a lightweight Java framework for bot/application development and can be used to perform various tasks, such as uploading files, adding text to articles, parsing templates, basic I/O, etc.</translate> <translate><!--T:23--> The library also comes with simple, but powerful standalone bot methods that can be readily utilized by a programmer.</translate> <translate> === Chris G's botclasses === <!--T:16--> <!--T:17--> [[<tvar|1>Special:MyLanguage/Manual:Chris G's botclasses</>|Chris G's botclasses]] compose a PHP MediaWiki bot framework hosted at the toolserver. == Extension alternatives == <!--T:11--> </translate> * {{ll|Extension:MassEditRegex}} — <translate><!--T:12--> provides an alternative way to perform mass edits using regular expressions, through a special page in the wiki.</translate> <translate><!--T:24--> Only admins can normally use this extension.</translate> * {{ll|Extension:Replace Text}} — <translate><!--T:13--> another option.</translate> <translate> == See also == <!--T:14--> </translate> * [[m:Special:MyLanguage/Bot|<translate><!--T:18--> m:Bot</translate>]] [[Category:Help{{#translation:}}|{{PAGENAME}}]] mjfnf8hrejccqlj86d6ffeakvcmr1v0 Manual:Installing third-party tools/ru 100 40984 5387826 5377085 2022-07-29T09:29:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ru]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ru]] dszrz7cbezxeak88ngzg6sexsb1tipm Installation/fa 0 41728 5387784 1378821 2022-07-29T09:22:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/fa]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/fa]] q9bg7mkxug8hhqv4u6qlrv888iayzs0 Manual:Installing MediaWiki/yue 100 43169 5387506 5384981 2022-07-28T22:45:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki can be difficult to install if you do not have any experience with Apache (web server software), PHP and MySQL/MariaDB (database).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] bd693ay6chakbf1f85bfgfdez5xwpqx Manual:Installation/pt-br 100 43703 5387814 494143 2022-07-29T09:27:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/pt-br]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pt-br]] fkiaxxukhcv6mkzadk6rrcpdrqpm9ci Wikitext standard 0 43857 5387863 3797111 2022-07-29T10:32:51Z Shirayuki 472859 make untranslatable wikitext text/x-wiki <languages /> {{Historical|1=<translate><!--T:14--> Most of the text found on this page was written from 2003-2006.</translate> <translate><!--T:15--> See <tvar|1>{{ll|Wikitext}}</> for the latest status on wikitext standardization efforts.</translate>}} <translate> <!--T:1--> A single '''[[<tvar name=1>Special:MyLanguage/wikitext</tvar>|wikitext]] standard''' is of great importance for the long-term stability of the MediaWiki software. We need to describe and formalize a [[<tvar name=2>meta:Special:MyLanguage/WikiReader#Wikipedia 1.0</tvar>|1.0]] version of the Wikitext language, based on what is used currently. In other words this work should not (for right now) involve incorporating improvements or changes to the Wikitext language. Releases must be stable and predictable so that other software developers can work to the same markup syntax, and know for sure that they will not be facing random or arbitrary changes for some fixed time period, like a year. This suggests there may be [[<tvar name=3>Special:MyLanguage/wikitext 2005</tvar>|wikitext 2005]], [[<tvar name=4>Special:MyLanguage/wikitext 2006</tvar>|wikitext 2006]] and so on. <!--T:2--> <tvar|1>[http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb]</> was tracking which mediawiki sites are doing what best. Wikipedia won't always be the furthest ahead on an issue, nor should its needs necessarily always trump others in the mediawiki software design effort. For instance [[meta:Wikitravel|Wikitravel]] may do better on geography and [[meta:Spacetime DTD|map]] issues. The first useful map and underlying data standards like an [[meta:Ecoregion DTD|ecoregion DTD]] and [[meta:Spacetime DTD|spacetime DTD]] may be easier to work on there, where these are more central issues. Other subtasks like a [[meta:Person DTD|person DTD]] may become WikiProjects undertaken by a disciplined group of scholars who know, or want to know, everything about documenting people. ==Tasks== <!--T:3--> <!--T:4--> #Write a [[<tvar name=1>Special:MyLanguage/markup spec</tvar>|markup spec]] #Write an efficient [[<tvar name=2>Special:MyLanguage/Alternative parsers</tvar>|Wikitext to HTML converter]], to replace the current PHP code. #Write a set of unit tests to validate the correctness of a Wikitext to HTML converter. ===XML-Related Tasks=== <!--T:5--> <!--T:6--> #Write a [[<tvar name=1>Special:MyLanguage/Markup spec/DTD</tvar>|Wikitext DTD]] that can serve as a canonical translation of Wikitext <=> XML, for further processing by XML tools. ''Or use [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. #Write a Wikitext to XML converter. #* Evaluate [http://www.tldp.org/wt2db/ wt2db]. #* Or use [http://schematics.sourceforge.net WebBot], A PLT Scheme package that acts as a Bot on MediaWiki and contains the parser to convert WikiText to the [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. ==Publishing the Standard== <!--T:7--> <!--T:8--> A clear standard can be published and supported by other wikis, like MoinMoinWiki ([[:en:Python_programming_language|python]]-based) and tikiwiki (see [http://tikiwiki.sourceforge.net sourceforge]), which are very popular, and more extensible than mediawiki, which has serious structural problems <!--T:9--> Even if mediawiki can keep up with those other packages, text import/export has to be one of our priorities, given the objectives of this project to become a central GNU FDL repository of trusted text for use all over the place. <!--T:10--> The [[meta:Wikimedia|Wikimedia]] activities shouldn't be in any way trapped or tied to MediaWiki, if drastically better software emerges from tikiwiki or the Python world. And it will, eventually. ===Long Term Plans === <!--T:11--> <!--T:12--> #when things settle down, say [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], then: #create a consortium of all users, developers of various types of software, including [[meta:IRC/Channels|chat]] and [[Special:MyLanguage/email|email]] based systems that incorporate features like [[Special:MyLanguage/Trillian Instant Lookup|Trillian Instant Lookup]] - not all users of Wikipedia use a web browser #agree on a [[meta:Simple ideology of Wikitax|simple ideology of Wikitax]] to make it easy for content generated elsewhere to quickly become wiki pages #develop a unified base boot like KnoppixTiki that supports the new standard so it can be used for any kind of data storage like in a PIM #stabilize and publish something like [[Special:MyLanguage/wikitext 2008|wikitext 2008]] as a real RFC #aim for [[Special:MyLanguage/wikitext 2009|wikitext 2009]] or [[Special:MyLanguage/wikitext 2010|wikitext 2010]] to be an ITU standard <!--T:13--> See also: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] </translate> [[Category:Wikitext{{#translation:}}]] bhaz8pedsqzub0q9esznr9xef090chg Wikitext standard/es 0 43861 5387867 4771637 2022-07-29T10:33:04Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Historical|1=<span lang="en" dir="ltr" class="mw-content-ltr">Most of the text found on this page was written from 2003-2006.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Wikitext}} for the latest status on wikitext standardization efforts.</span>}} <div class="mw-translate-fuzzy"> Un '''[[Special:MyLanguage/wikitext|wikitexto]] estándar''' único es de gran importancia para la estabilidad a largo plazo del software MediaWiki. Necesitamos describir y formalizar una versión [[meta:WikiReader#Wikipedia_1.0|1.0]] del lenguaje wikitexto, basado en lo que se usa actualmente. En otras palabras, este trabajo no debe (por ahora) incorporar mejoras o cambios en el lenguaje. Las liberaciones deben ser estables y predecibles de manera que los desarrolladores de software puedan trabajar con una misma sintaxis del lenguaje de hipertexto, y puedan saber con certeza que no se enfrentarán a cambios arbitrarios y al azar por algún período fijo, por ejemplo un año. Esto sugiere que puede haber [[Special:MyLanguage/wikitext 2005|wikitexto 2005]], [[Special:MyLanguage/wikitext 2006|wikitexto 2006]] y demás. </div> <div class="mw-translate-fuzzy"> [http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] hacen seguimiento de los sitios mediawiki haciendo lo que es mejor. Wikipedia no siempre estará adelante en un problema, no siempre es necesario triunfar sobre otros en cuanto a los diseños de software. Por ejemplo [[meta:Wikitravel|Wikitravel]] puede hacer un esfuerzo mayor en geografía y [[meta:Spacetime DTD|mapa]]. El primer mapa utilizable y las capas de software subyacentes como una [[meta:ecoregion DTD|ecoregion DTD]] y un [[meta:spacetime DTD|DTD de espacion]] pueden ser mas faciles de trabajar desde aqui, porque estos son problemas mas centralizados. Otras subtareas como una [[meta:person DTD|DTD personalizada]] pueden convertirse en un WikiProject superpuesto a un grupo disciplinado de escolares que saben o quieren conocer, todo sobre las personas que documentan. </div> ==Tareas== <div class="mw-translate-fuzzy"> #Escribir una [[Special:MyLanguage/markup spec|especificación del lenguaje wikitexto]] #Escribir un [[Special:MyLanguage/Alternative parsers|conversor de wikitexto a HTML]] eficiente, que reemplace el código PHP actual. #Escribir una serie de unidades de pruebas para validar la exactitud del conversor de wikitexto a HTML. </div> ===Tareas relacionadas con XML=== <div class="mw-translate-fuzzy"> #Escribir un [[Wikitext DTD]] que sirva como traduccion canonica del Wikitext<=> XML, para las futuras herramientas de procesamiento de XML. ''O usar [http://schematics.sourceforge.net/wikitext.xsd.zip este XML Schema]''. #Escribir un [[Alternative parsers|conversor Wikitext a XML]]. #Evaluar [http://www.tldp.org/wt2db/ wt2db]. #* O usar [http://schematics.sourceforge.net WebBot], Un paquete de esquemas PLT que actual como Boot en el Media Wiki y que contiene un [[parser]] que convierte Wikitext a [http://schematics.sourceforge.net/wikitext.xsd.zip desde un esquema XML dado]. </div> ==Publicación del estándar== Un estándar claro puede ser publicado y mantenido por otras wikis, como MoinMoinWiki (basada en [[w:Python_programming_language|python]]) y tikiwiki (ver [http://tikiwiki.sourceforge.net sourceforge]), que son muy populares y más extensibles que mediawiki, que tiene serios problemas estructurales Incluso si media wiki puede mantener esos paquetes, importadores/exportadores de texto no tiene que se una de sus prioridades, dado que los objeticos de proyecto se convierte en ser un repositorio central de texto confiable GNU FDL por sobre todo. Las actividades de [[Wikimedia]] no deben estar de ninguna manera atadas a MediaWiki, si drasticamente surgen programas de tikiwiki o del mundo Python/. Y lo hará eventualmente. ===Planes a largo plazo=== #Cuando los problemas se estabilicen, para decir [[wikitext standard 2007|estandares wikitext 2007]], entonces: #crear un congromerado de todos los usuarios, desarrolladores de varios de los tipos de softwares, incluidos los [[meta:IRC/channels|chat]] y [[email|Correos electrónicos]] que incorporan muchos sistemas como Trillian Instant Lookup - no todos los usuarios de Wikipedia usan un navegador de web #de acuerdo con una [[meta:Simple ideology of Wikitax|ideología simple de Wikitax]] para hacer mas facil el contenido generado sino crear mas rapidamente wikipaginas. #desarrollar una base unificada como KnoppixTiki que soporte los nuevos estandares, de manera que pueda se rusada para cualquier tipo de almacenamiento de informacion como un PIM #establilizar y publicar algo como [[wikitext 2008]] como un RFC real. #enfasis en [[wikitext 2009]] o [[wikitext 2010]] para ser un estandar ITU. Véase también: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] i7a1ygdxqfcc5aecckzzecw5fp6adff 5387877 5387867 2022-07-29T10:34:39Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=<span lang="en" dir="ltr" class="mw-content-ltr">Most of the text found on this page was written from 2003-2006.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Wikitext}} for the latest status on wikitext standardization efforts.</span>}} Un '''[[Special:MyLanguage/wikitext|wikitexto]] estándar''' único es de gran importancia para la estabilidad a largo plazo del software MediaWiki. Necesitamos describir y formalizar una versión [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] del lenguaje wikitexto, basado en lo que se usa actualmente. En otras palabras, este trabajo no debe (por ahora) incorporar mejoras o cambios en el lenguaje. Las liberaciones deben ser estables y predecibles de manera que los desarrolladores de software puedan trabajar con una misma sintaxis del lenguaje de hipertexto, y puedan saber con certeza que no se enfrentarán a cambios arbitrarios y al azar por algún período fijo, por ejemplo un año. Esto sugiere que puede haber [[Special:MyLanguage/wikitext 2005|wikitexto 2005]], [[Special:MyLanguage/wikitext 2006|wikitexto 2006]] y demás. <div class="mw-translate-fuzzy"> [http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] hacen seguimiento de los sitios mediawiki haciendo lo que es mejor. Wikipedia no siempre estará adelante en un problema, no siempre es necesario triunfar sobre otros en cuanto a los diseños de software. Por ejemplo [[meta:Wikitravel|Wikitravel]] puede hacer un esfuerzo mayor en geografía y [[meta:Spacetime DTD|mapa]]. El primer mapa utilizable y las capas de software subyacentes como una [[meta:ecoregion DTD|ecoregion DTD]] y un [[meta:spacetime DTD|DTD de espacion]] pueden ser mas faciles de trabajar desde aqui, porque estos son problemas mas centralizados. Otras subtareas como una [[meta:person DTD|DTD personalizada]] pueden convertirse en un WikiProject superpuesto a un grupo disciplinado de escolares que saben o quieren conocer, todo sobre las personas que documentan. </div> ==Tareas== <div class="mw-translate-fuzzy"> #Escribir una [[Special:MyLanguage/markup spec|especificación del lenguaje wikitexto]] #Escribir un [[Special:MyLanguage/Alternative parsers|conversor de wikitexto a HTML]] eficiente, que reemplace el código PHP actual. #Escribir una serie de unidades de pruebas para validar la exactitud del conversor de wikitexto a HTML. </div> ===Tareas relacionadas con XML=== <div class="mw-translate-fuzzy"> #Escribir un [[Wikitext DTD]] que sirva como traduccion canonica del Wikitext<=> XML, para las futuras herramientas de procesamiento de XML. ''O usar [http://schematics.sourceforge.net/wikitext.xsd.zip este XML Schema]''. #Escribir un [[Alternative parsers|conversor Wikitext a XML]]. #Evaluar [http://www.tldp.org/wt2db/ wt2db]. #* O usar [http://schematics.sourceforge.net WebBot], Un paquete de esquemas PLT que actual como Boot en el Media Wiki y que contiene un [[parser]] que convierte Wikitext a [http://schematics.sourceforge.net/wikitext.xsd.zip desde un esquema XML dado]. </div> ==Publicación del estándar== Un estándar claro puede ser publicado y mantenido por otras wikis, como MoinMoinWiki (basada en [[w:Python_programming_language|python]]) y tikiwiki (ver [http://tikiwiki.sourceforge.net sourceforge]), que son muy populares y más extensibles que mediawiki, que tiene serios problemas estructurales Incluso si media wiki puede mantener esos paquetes, importadores/exportadores de texto no tiene que se una de sus prioridades, dado que los objeticos de proyecto se convierte en ser un repositorio central de texto confiable GNU FDL por sobre todo. Las actividades de [[Wikimedia]] no deben estar de ninguna manera atadas a MediaWiki, si drasticamente surgen programas de tikiwiki o del mundo Python/. Y lo hará eventualmente. ===Planes a largo plazo=== #Cuando los problemas se estabilicen, para decir [[wikitext standard 2007|estandares wikitext 2007]], entonces: #crear un congromerado de todos los usuarios, desarrolladores de varios de los tipos de softwares, incluidos los [[meta:IRC/channels|chat]] y [[email|Correos electrónicos]] que incorporan muchos sistemas como Trillian Instant Lookup - no todos los usuarios de Wikipedia usan un navegador de web #de acuerdo con una [[meta:Simple ideology of Wikitax|ideología simple de Wikitax]] para hacer mas facil el contenido generado sino crear mas rapidamente wikipaginas. #desarrollar una base unificada como KnoppixTiki que soporte los nuevos estandares, de manera que pueda se rusada para cualquier tipo de almacenamiento de informacion como un PIM #establilizar y publicar algo como [[wikitext 2008]] como un RFC real. #enfasis en [[wikitext 2009]] o [[wikitext 2010]] para ser un estandar ITU. Véase también: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] 5tu9vp39tlnqc93o7rh4e4cv0ivrxm8 5387883 5387877 2022-07-29T10:36:41Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=<span lang="en" dir="ltr" class="mw-content-ltr">Most of the text found on this page was written from 2003-2006.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Wikitext}} for the latest status on wikitext standardization efforts.</span>}} Un '''[[Special:MyLanguage/wikitext|wikitexto]] estándar''' único es de gran importancia para la estabilidad a largo plazo del software MediaWiki. Necesitamos describir y formalizar una versión [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] del lenguaje wikitexto, basado en lo que se usa actualmente. En otras palabras, este trabajo no debe (por ahora) incorporar mejoras o cambios en el lenguaje. Las liberaciones deben ser estables y predecibles de manera que los desarrolladores de software puedan trabajar con una misma sintaxis del lenguaje de hipertexto, y puedan saber con certeza que no se enfrentarán a cambios arbitrarios y al azar por algún período fijo, por ejemplo un año. Esto sugiere que puede haber [[Special:MyLanguage/wikitext 2005|wikitexto 2005]], [[Special:MyLanguage/wikitext 2006|wikitexto 2006]] y demás. <div class="mw-translate-fuzzy"> [http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] hacen seguimiento de los sitios mediawiki haciendo lo que es mejor. Wikipedia no siempre estará adelante en un problema, no siempre es necesario triunfar sobre otros en cuanto a los diseños de software. Por ejemplo [[meta:Wikitravel|Wikitravel]] puede hacer un esfuerzo mayor en geografía y [[meta:Spacetime DTD|mapa]]. El primer mapa utilizable y las capas de software subyacentes como una [[meta:ecoregion DTD|ecoregion DTD]] y un [[meta:spacetime DTD|DTD de espacion]] pueden ser mas faciles de trabajar desde aqui, porque estos son problemas mas centralizados. Otras subtareas como una [[meta:person DTD|DTD personalizada]] pueden convertirse en un WikiProject superpuesto a un grupo disciplinado de escolares que saben o quieren conocer, todo sobre las personas que documentan. </div> ==Tareas== #Escribir una [[Special:MyLanguage/markup spec|especificación del lenguaje wikitexto]] #Escribir un [[Special:MyLanguage/Alternative parsers|conversor de wikitexto a HTML]] eficiente, que reemplace el código PHP actual. #Escribir una serie de unidades de pruebas para validar la exactitud del conversor de wikitexto a HTML. ===Tareas relacionadas con XML=== <div class="mw-translate-fuzzy"> #Escribir un [[Wikitext DTD]] que sirva como traduccion canonica del Wikitext<=> XML, para las futuras herramientas de procesamiento de XML. ''O usar [http://schematics.sourceforge.net/wikitext.xsd.zip este XML Schema]''. #Escribir un [[Alternative parsers|conversor Wikitext a XML]]. #Evaluar [http://www.tldp.org/wt2db/ wt2db]. #* O usar [http://schematics.sourceforge.net WebBot], Un paquete de esquemas PLT que actual como Boot en el Media Wiki y que contiene un [[parser]] que convierte Wikitext a [http://schematics.sourceforge.net/wikitext.xsd.zip desde un esquema XML dado]. </div> ==Publicación del estándar== Un estándar claro puede ser publicado y mantenido por otras wikis, como MoinMoinWiki (basada en [[w:Python_programming_language|python]]) y tikiwiki (ver [http://tikiwiki.sourceforge.net sourceforge]), que son muy populares y más extensibles que mediawiki, que tiene serios problemas estructurales Incluso si media wiki puede mantener esos paquetes, importadores/exportadores de texto no tiene que se una de sus prioridades, dado que los objeticos de proyecto se convierte en ser un repositorio central de texto confiable GNU FDL por sobre todo. Las actividades de [[Wikimedia]] no deben estar de ninguna manera atadas a MediaWiki, si drasticamente surgen programas de tikiwiki o del mundo Python/. Y lo hará eventualmente. ===Planes a largo plazo=== #Cuando los problemas se estabilicen, para decir [[wikitext standard 2007|estandares wikitext 2007]], entonces: #crear un congromerado de todos los usuarios, desarrolladores de varios de los tipos de softwares, incluidos los [[meta:IRC/channels|chat]] y [[email|Correos electrónicos]] que incorporan muchos sistemas como Trillian Instant Lookup - no todos los usuarios de Wikipedia usan un navegador de web #de acuerdo con una [[meta:Simple ideology of Wikitax|ideología simple de Wikitax]] para hacer mas facil el contenido generado sino crear mas rapidamente wikipaginas. #desarrollar una base unificada como KnoppixTiki que soporte los nuevos estandares, de manera que pueda se rusada para cualquier tipo de almacenamiento de informacion como un PIM #establilizar y publicar algo como [[wikitext 2008]] como un RFC real. #enfasis en [[wikitext 2009]] o [[wikitext 2010]] para ser un estandar ITU. Véase también: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] lx3nv63tde24hly1rqqs08fie012oh6 5387890 5387883 2022-07-29T10:38:34Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=<span lang="en" dir="ltr" class="mw-content-ltr">Most of the text found on this page was written from 2003-2006.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Wikitext}} for the latest status on wikitext standardization efforts.</span>}} Un '''[[Special:MyLanguage/wikitext|wikitexto]] estándar''' único es de gran importancia para la estabilidad a largo plazo del software MediaWiki. Necesitamos describir y formalizar una versión [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] del lenguaje wikitexto, basado en lo que se usa actualmente. En otras palabras, este trabajo no debe (por ahora) incorporar mejoras o cambios en el lenguaje. Las liberaciones deben ser estables y predecibles de manera que los desarrolladores de software puedan trabajar con una misma sintaxis del lenguaje de hipertexto, y puedan saber con certeza que no se enfrentarán a cambios arbitrarios y al azar por algún período fijo, por ejemplo un año. Esto sugiere que puede haber [[Special:MyLanguage/wikitext 2005|wikitexto 2005]], [[Special:MyLanguage/wikitext 2006|wikitexto 2006]] y demás. <div class="mw-translate-fuzzy"> [http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] hacen seguimiento de los sitios mediawiki haciendo lo que es mejor. Wikipedia no siempre estará adelante en un problema, no siempre es necesario triunfar sobre otros en cuanto a los diseños de software. Por ejemplo [[meta:Wikitravel|Wikitravel]] puede hacer un esfuerzo mayor en geografía y [[meta:Spacetime DTD|mapa]]. El primer mapa utilizable y las capas de software subyacentes como una [[meta:ecoregion DTD|ecoregion DTD]] y un [[meta:spacetime DTD|DTD de espacion]] pueden ser mas faciles de trabajar desde aqui, porque estos son problemas mas centralizados. Otras subtareas como una [[meta:person DTD|DTD personalizada]] pueden convertirse en un WikiProject superpuesto a un grupo disciplinado de escolares que saben o quieren conocer, todo sobre las personas que documentan. </div> ==Tareas== #Escribir una [[Special:MyLanguage/markup spec|especificación del lenguaje wikitexto]] #Escribir un [[Special:MyLanguage/Alternative parsers|conversor de wikitexto a HTML]] eficiente, que reemplace el código PHP actual. #Escribir una serie de unidades de pruebas para validar la exactitud del conversor de wikitexto a HTML. ===Tareas relacionadas con XML=== #Escribir un [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]] que sirva como traduccion canonica del Wikitext<=> XML, para las futuras herramientas de procesamiento de XML. ''O usar [http://schematics.sourceforge.net/wikitext.xsd.zip este XML Schema]''. #Escribir un [[Alternative parsers|conversor Wikitext a XML]]. #Evaluar [http://www.tldp.org/wt2db/ wt2db]. #* O usar [http://schematics.sourceforge.net WebBot], Un paquete de esquemas PLT que actual como Boot en el Media Wiki y que contiene un [[parser]] que convierte Wikitext a [http://schematics.sourceforge.net/wikitext.xsd.zip desde un esquema XML dado]. ==Publicación del estándar== Un estándar claro puede ser publicado y mantenido por otras wikis, como MoinMoinWiki (basada en [[w:Python_programming_language|python]]) y tikiwiki (ver [http://tikiwiki.sourceforge.net sourceforge]), que son muy populares y más extensibles que mediawiki, que tiene serios problemas estructurales Incluso si media wiki puede mantener esos paquetes, importadores/exportadores de texto no tiene que se una de sus prioridades, dado que los objeticos de proyecto se convierte en ser un repositorio central de texto confiable GNU FDL por sobre todo. Las actividades de [[Wikimedia]] no deben estar de ninguna manera atadas a MediaWiki, si drasticamente surgen programas de tikiwiki o del mundo Python/. Y lo hará eventualmente. ===Planes a largo plazo=== #Cuando los problemas se estabilicen, para decir [[wikitext standard 2007|estandares wikitext 2007]], entonces: #crear un congromerado de todos los usuarios, desarrolladores de varios de los tipos de softwares, incluidos los [[meta:IRC/channels|chat]] y [[email|Correos electrónicos]] que incorporan muchos sistemas como Trillian Instant Lookup - no todos los usuarios de Wikipedia usan un navegador de web #de acuerdo con una [[meta:Simple ideology of Wikitax|ideología simple de Wikitax]] para hacer mas facil el contenido generado sino crear mas rapidamente wikipaginas. #desarrollar una base unificada como KnoppixTiki que soporte los nuevos estandares, de manera que pueda se rusada para cualquier tipo de almacenamiento de informacion como un PIM #establilizar y publicar algo como [[wikitext 2008]] como un RFC real. #enfasis en [[wikitext 2009]] o [[wikitext 2010]] para ser un estandar ITU. Véase también: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] q1md64qqmt80se0l10ric8mk24hnjhf Template:InstallationNav/es 10 44206 5387195 5384782 2022-07-28T21:17:28Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=Personalización}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] 52vby3275mopdh1kof3qn1u80rjt2fn Manual:Installation/ko 100 44547 5387811 1986506 2022-07-29T09:27:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ko]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ko]] 2mv5oubsjsrbcsagzy12ozik9wg3xf7 Help:Installation 12 48399 5387807 343241 2022-07-29T09:26:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u UploadWizard 0 48510 5387136 5385204 2022-07-28T20:59:44Z 2603:9000:AD00:2B85:6C92:3140:997C:9505 wikitext text/x-wiki [[8632771332]]<noinclude> <languages /> </noinclude><includeonly>{{Wikimedia engineering project information | name = UploadWizard | description = <translate><!--T:1--> A feature that provides an easier way of uploading files to [[<tvar name=1>:commons:</tvar>|Wikimedia Commons]], the media library associated with Wikipedia.</translate> | start = 2015-01-01 | end = 2015-06-30 | group = [[Wikimedia Platform Engineering|Platform]] | EPM = [[User:RobLa-WMF|Rob Lanphier]] (engineering director) | team = [[User:GDubuc_%28WMF%29|Gilles Dubuc]], [[mw:User:Pginer|Pau Giner]], [[User:MarkTraceur|Mark Holmquist]], [[user:NeilK|Neil Kandalgaonkar]], [[mw:User:Keegan_(WMF)|Keegan Peterzell]], [[meta:User:Tgr|Gergő Tisza]] | previous = | next = | projectpage = UploadWizard | display = {{{display|}}} }}</includeonly> <translate><!--T:2--> '''UploadWizard''' is a multi-file, step-by-step JavaScript wizard to upload multimedia files to a MediaWiki website.</translate> <translate><!--T:3--> It is available as an <tvar name=1>{{ll|Extension:UploadWizard}}</tvar>.</translate> {{TOC|align=right|limit=2}} <translate> == Rationale == <!--T:4--> <!--T:14--> The Upload Wizard aims to make it easier to contribute multimedia works to Wikimedia projects. </translate> <translate><!--T:43--> This tool is now widely used to upload images on Wikimedia Commons, the free media repository associated with Wikipedia; any media file shared on that site can be used in any Wikipedia page in any language.</translate> <translate><!--T:44--> Wikimedia Commons is curated by a multilingual community and recently reached 21 million files.</translate> <translate> <!--T:45--> More details about the origins of this project can be found in the [[<tvar name=1>Special:MyLanguage/UploadWizard/Archive</tvar>|Upload Wizard archive page]]; the main feedback page is located at [[<tvar name=2>commons:Commons:Upload Wizard feedback</tvar>|Commons:Upload Wizard feedback]]. == Goals == <!--T:5--> <!--T:15--> Here are some of our goals for Upload Wizard: </translate> * <translate><!--T:46--> '''engage more users''' to contribute media</translate> * <translate><!--T:47--> provide a '''smoother experience''' for all</translate> * <translate><!--T:48--> '''add more media''' content on our sites</translate> * <translate><!--T:49--> '''fix critical bugs''', to make things work better</translate> <translate><!--T:50--> In coming months, we propose to:</translate> * <translate><!--T:51--> '''Plan & discuss''' improvements</translate> * <translate><!--T:52--> Solve '''bugs & technical debt'''</translate> * <translate><!--T:53--> Improve the '''user experience'''</translate> * <translate><!--T:54--> Incremental '''code refactoring'''</translate> * <translate><!--T:55--> Develop new '''modal tool''' for other uses</translate> <translate> == Timeline == <!--T:6--> <!--T:16--> This is an estimated timeline based on our current work, as of January 2015. </translate> ; <translate><!--T:56--> Q3 (Jan-Mar 2015)</translate> * <translate><!--T:57--> Implement and deploy JS error logging to automatically capture errors affecting users</translate> ; <translate><!--T:58--> Q4 (Apr.-June 2015)</translate> * <translate><!--T:59--> Identify the main sources of the [<tvar name=url>http://multimedia-metrics.wmflabs.org/dashboards/uw#</tvar> current drop-off] happening on the file step</translate> * <translate><!--T:60--> Significantly reduce the drop-off</translate> <translate> == Users == <!--T:7--> <!--T:17--> Our primary users for Upload Wizard include: </translate> * <translate><!--T:61--> new contributors</translate> * <translate><!--T:62--> experienced contributors</translate> <translate><!--T:63--> We will aim to support both user groups evenly, with an initial focus on Commons users - then contributors on Wikipedia and other sites.</translate> <translate><!--T:64--> Note that you must be registered and logged-in to use Upload Wizard.</translate> <translate><!--T:65--> We also aim to serve these secondary users:</translate> * <translate><!--T:66--> editors</translate> * <translate><!--T:67--> campaign organizers</translate> * <translate><!--T:68--> developers</translate> <translate> == Metrics == <!--T:8--> </translate> [[File:Upload Wizard Slides.pdf|thumb|400px|page=36]] [[File:Upload Wizard Slides.pdf|thumb|400px|page=37]] <translate> === First metrics === <!--T:9--> </translate> Here are upload metrics for Upload Wizard from February 2014: (1) * 18k uploaders / month * 292k uploads / month It's worth noting that Upload Wizard represents: * 80% of all uploaders (14k per month, a lot more during Wiki Loves Monuments) * 56% of all uploads (141k per month, the rest are handled by bots and other uploads tools) For more info, click on the metrics graph thumbnails to the right. (1) Data from Wikimedia Commons in Feb 2014. Source: Wikimedia Foundation <translate> === More metrics === <!--T:10--> <!--T:18--> Here are key metrics we're considering to track the upload process: </translate> * number of uploaders * number of uploads * upload drop-off rate * number of uploaded files used * number of uploaded files viewed We are starting development to collect more metrics data, and are tracking this work in these tickets: * <translate><!--T:19--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/541</tvar> Funnel Metrics for Upload Wizard (#541)] (in development for this sprint)</translate> * <translate><!--T:20--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/609</tvar> Upload Wizard funnel metrics - basics (#609)] (done, but only 4 data points for now)</translate> * <translate><!--T:21--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/305</tvar> Upload Wizard Metrics - Data collection 1: Major steps (#305)] (to be developed in coming weeks)</translate> * <translate><!--T:22--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/603</tvar> Upload Wizard Metrics - Data Collection 2: Detailed Steps (#603)] (to be developed in coming weeks)</translate> * <translate><!--T:23--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/587</tvar> Upload Wizard Metrics - Dashboards (#587)] (to be developed in coming weeks)</translate> <translate> == Feedback == <!--T:11--> </translate> We are now reviewing hundreds of [[commons:Commons:Upload_Wizard_feedback|feedback posts]] and [[commons:Commons:Upload_help|help questions]] about Upload Wizard last year, which have been analyzed in [https://docs.google.com/a/wikimedia.org/spreadsheets/d/1AUKUODbKVQMtFgTbCm8l3Pee7l7xbpxf9idx_3PsCXE/edit#gid=0 this spreadsheet]. <translate> <!--T:24--> Here are some of the key issues reported: </translate> * upload hangs * upload takes too long * issues with multiple files * confused by license forms * unclear prompts and error messages * problems with categories (e.g. can't search them) * issues with large files that don't load well * would like a progress bar during upload * want to add info while image loads * would like simple explanations * want other info templates <translate> == Usability == <!--T:12--> <!--T:25--> We have done a number of usability studies for Upload Wizard and plan to do more. <!--T:26--> Here are videos of some initial testing sessions: </translate> * [https://www.usertesting.com/videos/AI1Psz9uNro?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T1] * [https://www.usertesting.com/videos/eM8j0rwubH0?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T2] * [https://www.usertesting.com/videos/pE4nRhgRmS0?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T3] * [https://www.usertesting.com/videos/katNyUV7qtw?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T4] We will consolidate these results when we run more user tests. For now, here are some [http://etherpad.wikimedia.org/p/design-multimedia-uploader preliminary observations and analysis of the current design] by our designer Pau Giner. <translate> == Current Workflow == <!--T:27--> <!--T:28--> Here are the main steps of the current workflow for Upload Wizard: </translate> * '''<translate><!--T:73--> Start</translate>''' - <translate><!--T:74--> Click on the Upload link</translate> * '''<translate><!--T:75--> Learn</translate>''' - <translate><!--T:76--> Reading the help infographic, click 'Continue'</translate> * '''<translate><!--T:77--> Upload</translate>''' - <translate><!--T:78--> Select media files to upload, add more files if needed</translate> * '''<translate><!--T:79--> Rights</translate>''' - <translate><!--T:80--> Fill in author, source and license information</translate> * '''<translate><!--T:81--> Describe</translate>''' - <translate><!--T:82--> Fill in title, description, date or other info</translate> * '''<translate><!--T:83--> Use</translate>''' - <translate><!--T:84--> copy code to add images to articles or share them with others</translate> <translate> <!--T:85--> To see how Upload Wizard currently works, [[<tvar name=1>commons:Special:UploadWizard</tvar>|visit this page]] (must be logged in). == New designs == <!--T:29--> </translate> <translate><!--T:86--> Based on current feedback and usability tests, our designer Pau Giner has prepared some preliminary design ideas to help define our vision for Upload Wizard (see [[<tvar name=1>:File:Upload Wizard Slides.pdf</tvar>|slides]] below).</translate> <translate><!--T:87--> These are explorations and reflections about a more modern upload experience, but don't necessarily reflect what will be built, as more community consultation would be required.</translate> <translate> ====Mockups==== <!--T:30--> </translate> <gallery mode="nolines" perrow="3" widths="320px" heights="240px"> File:Upload Wizard Slides.pdf|page=11| File:Upload Wizard Slides.pdf|page=12| File:Upload Wizard Slides.pdf|page=13| File:Upload Wizard Slides.pdf|page=14| File:Upload Wizard Slides.pdf|page=15| File:Upload Wizard Slides.pdf|page=16| File:Upload Wizard Slides.pdf|page=17| File:Upload Wizard Slides.pdf|page=18| File:Upload Wizard Slides.pdf|page=19| File:Upload Wizard Slides.pdf|page=20| File:Upload Wizard Slides.pdf|page=21| File:Upload Wizard Slides.pdf|page=22| File:Upload Wizard Slides.pdf|page=23| File:Upload Wizard Slides.pdf|page=24| File:Upload Wizard Slides.pdf|page=25| </gallery> <translate> <!--T:31--> These mockups will be adjusted based on community feedback. </translate> <translate><!--T:88--> These designs can be viewed together in [[<tvar name=1>:File:Upload Wizard Slides.pdf</tvar>|these vision slides]].</translate> <translate><!--T:89--> Individual screenshots will be added to this page soon.</translate> <translate> ===Scenarios=== <!--T:32--> <!--T:33--> These first designs are based on these user scenarios: </translate> * <translate><!--T:90--> Upload images to a page</translate> * <translate><!--T:91--> Upload a single image on a topic</translate> * <translate><!--T:92--> Upload multiple files on different topics</translate> <translate> ===Issues=== <!--T:34--> <!--T:35--> They attempt to address these key issues: </translate> * <translate><!--T:93--> Adding a picture to a page is disconnected</translate> * <translate><!--T:94--> Providing metadata is a big upfront effort</translate> * <translate><!--T:95--> Categorization is painful</translate> * <translate><!--T:96--> Multiple file upload</translate> * <translate><!--T:97--> Lack of aids for input</translate> * <translate><!--T:98--> Meaningless untranslatable titles</translate> * <translate><!--T:99--> Initial infographic is too verbose</translate> * <translate><!--T:100--> Help needed to understand licenses</translate> * <translate><!--T:101--> Upload button on Commons homepage is hard to find</translate> <translate> <!--T:36--> To learn more, check out [<tvar name=url>http://etherpad.wikimedia.org/p/design-multimedia-uploader</tvar> these design notes] by our designer Pau Giner. == Bugs == <!--T:37--> <!--T:38--> We keep track of Upload Wizard bugs [[<tvar name=1>phab:tag/mediawiki-extensions-uploadwizard/</tvar>|in the bug tracker]]. </translate> <translate><!--T:69--> Over the years, many bugs have accumulated for this project, because Wikimedia Foundation did not have a dedicated team to address them.</translate> <translate><!--T:70--> Now that the multimedia team has taken ownership of Upload Wizard, we will work diligently to fix the most important bugs first, then gradually resolve the rest of the relevant issues over time.</translate> <translate><!--T:71--> Thanks for your patience and understanding :)</translate> <translate><!--T:39--> If you find any technical bugs, please [<tvar name=url>https://phabricator.wikimedia.org/maniphest/task/create/?projects=MediaWiki-extensions-UploadWizard</tvar> report them].</translate> {{anchor|Compatibility}} <translate> == Compatibility == <!--T:13--> <!--T:40--> To be able to run UploadWizard, the user's browser must: </translate> * <translate><!--T:102--> Have [[w:JavaScript|JavaScript]] enabled</translate> * <translate><!--T:103--> Support [[w:ECMAScript#5th Edition|ECMAScript 5]]</translate> * <translate><!--T:104--> Support [[w:HTML5 File API|HTML5 File API]]</translate> * <translate><!--T:105--> Support [[w:MIME#Form-Data|form-data]] in [[w:XMLHttpRequest|XMLHttpRequest]]</translate> <translate> <!--T:106--> Otherwise, the standard MediaWiki file upload form is displayed. <!--T:107--> Supported browsers include Firefox 13+, Chrome 21+, Internet Explorer 10+, Safari 7+ and Opera 12+. == Tasks == <!--T:41--> </translate> [[phab:tag/mediawiki-extensions-uploadwizard/|https://phabricator.wikimedia.org/tag/mediawiki-extensions-uploadwizard/]] <translate> == Other tools == <!--T:42--> <!--T:72--> Besides Upload Wizard, other upload tools are available to users, which are tracked at [[<tvar name=1>commons:Special:MyLanguage/Commons:Upload tools</tvar>|commons:Commons:Upload tools]]. </translate> [[Category:Multimedia{{#translation:}}]] qr1l1xou9sovy24z17vp8tviwnmwd0s 5387263 5387136 2022-07-28T21:38:21Z Shirayuki 472859 Reverted edits by [[Special:Contribs/2603:9000:AD00:2B85:6C92:3140:997C:9505|2603:9000:AD00:2B85:6C92:3140:997C:9505]] ([[User talk:2603:9000:AD00:2B85:6C92:3140:997C:9505|talk]]) to last version by Gaardn wikitext text/x-wiki <noinclude> <languages /> </noinclude><includeonly>{{Wikimedia engineering project information | name = UploadWizard | description = <translate><!--T:1--> A feature that provides an easier way of uploading files to [[<tvar name=1>:commons:</tvar>|Wikimedia Commons]], the media library associated with Wikipedia.</translate> | start = 2015-01-01 | end = 2015-06-30 | group = [[Wikimedia Platform Engineering|Platform]] | EPM = [[User:RobLa-WMF|Rob Lanphier]] (engineering director) | team = [[User:GDubuc_%28WMF%29|Gilles Dubuc]], [[mw:User:Pginer|Pau Giner]], [[User:MarkTraceur|Mark Holmquist]], [[user:NeilK|Neil Kandalgaonkar]], [[mw:User:Keegan_(WMF)|Keegan Peterzell]], [[meta:User:Tgr|Gergő Tisza]] | previous = | next = | projectpage = UploadWizard | display = {{{display|}}} }}</includeonly> <translate><!--T:2--> '''UploadWizard''' is a multi-file, step-by-step JavaScript wizard to upload multimedia files to a MediaWiki website.</translate> <translate><!--T:3--> It is available as an <tvar name=1>{{ll|Extension:UploadWizard}}</tvar>.</translate> {{TOC|align=right|limit=2}} <translate> == Rationale == <!--T:4--> <!--T:14--> The Upload Wizard aims to make it easier to contribute multimedia works to Wikimedia projects. </translate> <translate><!--T:43--> This tool is now widely used to upload images on Wikimedia Commons, the free media repository associated with Wikipedia; any media file shared on that site can be used in any Wikipedia page in any language.</translate> <translate><!--T:44--> Wikimedia Commons is curated by a multilingual community and recently reached 21 million files.</translate> <translate> <!--T:45--> More details about the origins of this project can be found in the [[<tvar name=1>Special:MyLanguage/UploadWizard/Archive</tvar>|Upload Wizard archive page]]; the main feedback page is located at [[<tvar name=2>commons:Commons:Upload Wizard feedback</tvar>|Commons:Upload Wizard feedback]]. == Goals == <!--T:5--> <!--T:15--> Here are some of our goals for Upload Wizard: </translate> * <translate><!--T:46--> '''engage more users''' to contribute media</translate> * <translate><!--T:47--> provide a '''smoother experience''' for all</translate> * <translate><!--T:48--> '''add more media''' content on our sites</translate> * <translate><!--T:49--> '''fix critical bugs''', to make things work better</translate> <translate><!--T:50--> In coming months, we propose to:</translate> * <translate><!--T:51--> '''Plan & discuss''' improvements</translate> * <translate><!--T:52--> Solve '''bugs & technical debt'''</translate> * <translate><!--T:53--> Improve the '''user experience'''</translate> * <translate><!--T:54--> Incremental '''code refactoring'''</translate> * <translate><!--T:55--> Develop new '''modal tool''' for other uses</translate> <translate> == Timeline == <!--T:6--> <!--T:16--> This is an estimated timeline based on our current work, as of January 2015. </translate> ; <translate><!--T:56--> Q3 (Jan-Mar 2015)</translate> * <translate><!--T:57--> Implement and deploy JS error logging to automatically capture errors affecting users</translate> ; <translate><!--T:58--> Q4 (Apr.-June 2015)</translate> * <translate><!--T:59--> Identify the main sources of the [<tvar name=url>http://multimedia-metrics.wmflabs.org/dashboards/uw#</tvar> current drop-off] happening on the file step</translate> * <translate><!--T:60--> Significantly reduce the drop-off</translate> <translate> == Users == <!--T:7--> <!--T:17--> Our primary users for Upload Wizard include: </translate> * <translate><!--T:61--> new contributors</translate> * <translate><!--T:62--> experienced contributors</translate> <translate><!--T:63--> We will aim to support both user groups evenly, with an initial focus on Commons users - then contributors on Wikipedia and other sites.</translate> <translate><!--T:64--> Note that you must be registered and logged-in to use Upload Wizard.</translate> <translate><!--T:65--> We also aim to serve these secondary users:</translate> * <translate><!--T:66--> editors</translate> * <translate><!--T:67--> campaign organizers</translate> * <translate><!--T:68--> developers</translate> <translate> == Metrics == <!--T:8--> </translate> [[File:Upload Wizard Slides.pdf|thumb|400px|page=36]] [[File:Upload Wizard Slides.pdf|thumb|400px|page=37]] <translate> === First metrics === <!--T:9--> </translate> Here are upload metrics for Upload Wizard from February 2014: (1) * 18k uploaders / month * 292k uploads / month It's worth noting that Upload Wizard represents: * 80% of all uploaders (14k per month, a lot more during Wiki Loves Monuments) * 56% of all uploads (141k per month, the rest are handled by bots and other uploads tools) For more info, click on the metrics graph thumbnails to the right. (1) Data from Wikimedia Commons in Feb 2014. Source: Wikimedia Foundation <translate> === More metrics === <!--T:10--> <!--T:18--> Here are key metrics we're considering to track the upload process: </translate> * number of uploaders * number of uploads * upload drop-off rate * number of uploaded files used * number of uploaded files viewed We are starting development to collect more metrics data, and are tracking this work in these tickets: * <translate><!--T:19--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/541</tvar> Funnel Metrics for Upload Wizard (#541)] (in development for this sprint)</translate> * <translate><!--T:20--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/609</tvar> Upload Wizard funnel metrics - basics (#609)] (done, but only 4 data points for now)</translate> * <translate><!--T:21--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/305</tvar> Upload Wizard Metrics - Data collection 1: Major steps (#305)] (to be developed in coming weeks)</translate> * <translate><!--T:22--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/603</tvar> Upload Wizard Metrics - Data Collection 2: Detailed Steps (#603)] (to be developed in coming weeks)</translate> * <translate><!--T:23--> [<tvar name=url>https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/587</tvar> Upload Wizard Metrics - Dashboards (#587)] (to be developed in coming weeks)</translate> <translate> == Feedback == <!--T:11--> </translate> We are now reviewing hundreds of [[commons:Commons:Upload_Wizard_feedback|feedback posts]] and [[commons:Commons:Upload_help|help questions]] about Upload Wizard last year, which have been analyzed in [https://docs.google.com/a/wikimedia.org/spreadsheets/d/1AUKUODbKVQMtFgTbCm8l3Pee7l7xbpxf9idx_3PsCXE/edit#gid=0 this spreadsheet]. <translate> <!--T:24--> Here are some of the key issues reported: </translate> * upload hangs * upload takes too long * issues with multiple files * confused by license forms * unclear prompts and error messages * problems with categories (e.g. can't search them) * issues with large files that don't load well * would like a progress bar during upload * want to add info while image loads * would like simple explanations * want other info templates <translate> == Usability == <!--T:12--> <!--T:25--> We have done a number of usability studies for Upload Wizard and plan to do more. <!--T:26--> Here are videos of some initial testing sessions: </translate> * [https://www.usertesting.com/videos/AI1Psz9uNro?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T1] * [https://www.usertesting.com/videos/eM8j0rwubH0?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T2] * [https://www.usertesting.com/videos/pE4nRhgRmS0?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T3] * [https://www.usertesting.com/videos/katNyUV7qtw?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T4] We will consolidate these results when we run more user tests. For now, here are some [http://etherpad.wikimedia.org/p/design-multimedia-uploader preliminary observations and analysis of the current design] by our designer Pau Giner. <translate> == Current Workflow == <!--T:27--> <!--T:28--> Here are the main steps of the current workflow for Upload Wizard: </translate> * '''<translate><!--T:73--> Start</translate>''' - <translate><!--T:74--> Click on the Upload link</translate> * '''<translate><!--T:75--> Learn</translate>''' - <translate><!--T:76--> Reading the help infographic, click 'Continue'</translate> * '''<translate><!--T:77--> Upload</translate>''' - <translate><!--T:78--> Select media files to upload, add more files if needed</translate> * '''<translate><!--T:79--> Rights</translate>''' - <translate><!--T:80--> Fill in author, source and license information</translate> * '''<translate><!--T:81--> Describe</translate>''' - <translate><!--T:82--> Fill in title, description, date or other info</translate> * '''<translate><!--T:83--> Use</translate>''' - <translate><!--T:84--> copy code to add images to articles or share them with others</translate> <translate> <!--T:85--> To see how Upload Wizard currently works, [[<tvar name=1>commons:Special:UploadWizard</tvar>|visit this page]] (must be logged in). == New designs == <!--T:29--> </translate> <translate><!--T:86--> Based on current feedback and usability tests, our designer Pau Giner has prepared some preliminary design ideas to help define our vision for Upload Wizard (see [[<tvar name=1>:File:Upload Wizard Slides.pdf</tvar>|slides]] below).</translate> <translate><!--T:87--> These are explorations and reflections about a more modern upload experience, but don't necessarily reflect what will be built, as more community consultation would be required.</translate> <translate> ====Mockups==== <!--T:30--> </translate> <gallery mode="nolines" perrow="3" widths="320px" heights="240px"> File:Upload Wizard Slides.pdf|page=11| File:Upload Wizard Slides.pdf|page=12| File:Upload Wizard Slides.pdf|page=13| File:Upload Wizard Slides.pdf|page=14| File:Upload Wizard Slides.pdf|page=15| File:Upload Wizard Slides.pdf|page=16| File:Upload Wizard Slides.pdf|page=17| File:Upload Wizard Slides.pdf|page=18| File:Upload Wizard Slides.pdf|page=19| File:Upload Wizard Slides.pdf|page=20| File:Upload Wizard Slides.pdf|page=21| File:Upload Wizard Slides.pdf|page=22| File:Upload Wizard Slides.pdf|page=23| File:Upload Wizard Slides.pdf|page=24| File:Upload Wizard Slides.pdf|page=25| </gallery> <translate> <!--T:31--> These mockups will be adjusted based on community feedback. </translate> <translate><!--T:88--> These designs can be viewed together in [[<tvar name=1>:File:Upload Wizard Slides.pdf</tvar>|these vision slides]].</translate> <translate><!--T:89--> Individual screenshots will be added to this page soon.</translate> <translate> ===Scenarios=== <!--T:32--> <!--T:33--> These first designs are based on these user scenarios: </translate> * <translate><!--T:90--> Upload images to a page</translate> * <translate><!--T:91--> Upload a single image on a topic</translate> * <translate><!--T:92--> Upload multiple files on different topics</translate> <translate> ===Issues=== <!--T:34--> <!--T:35--> They attempt to address these key issues: </translate> * <translate><!--T:93--> Adding a picture to a page is disconnected</translate> * <translate><!--T:94--> Providing metadata is a big upfront effort</translate> * <translate><!--T:95--> Categorization is painful</translate> * <translate><!--T:96--> Multiple file upload</translate> * <translate><!--T:97--> Lack of aids for input</translate> * <translate><!--T:98--> Meaningless untranslatable titles</translate> * <translate><!--T:99--> Initial infographic is too verbose</translate> * <translate><!--T:100--> Help needed to understand licenses</translate> * <translate><!--T:101--> Upload button on Commons homepage is hard to find</translate> <translate> <!--T:36--> To learn more, check out [<tvar name=url>http://etherpad.wikimedia.org/p/design-multimedia-uploader</tvar> these design notes] by our designer Pau Giner. == Bugs == <!--T:37--> <!--T:38--> We keep track of Upload Wizard bugs [[<tvar name=1>phab:tag/mediawiki-extensions-uploadwizard/</tvar>|in the bug tracker]]. </translate> <translate><!--T:69--> Over the years, many bugs have accumulated for this project, because Wikimedia Foundation did not have a dedicated team to address them.</translate> <translate><!--T:70--> Now that the multimedia team has taken ownership of Upload Wizard, we will work diligently to fix the most important bugs first, then gradually resolve the rest of the relevant issues over time.</translate> <translate><!--T:71--> Thanks for your patience and understanding :)</translate> <translate><!--T:39--> If you find any technical bugs, please [<tvar name=url>https://phabricator.wikimedia.org/maniphest/task/create/?projects=MediaWiki-extensions-UploadWizard</tvar> report them].</translate> {{anchor|Compatibility}} <translate> == Compatibility == <!--T:13--> <!--T:40--> To be able to run UploadWizard, the user's browser must: </translate> * <translate><!--T:102--> Have [[w:JavaScript|JavaScript]] enabled</translate> * <translate><!--T:103--> Support [[w:ECMAScript#5th Edition|ECMAScript 5]]</translate> * <translate><!--T:104--> Support [[w:HTML5 File API|HTML5 File API]]</translate> * <translate><!--T:105--> Support [[w:MIME#Form-Data|form-data]] in [[w:XMLHttpRequest|XMLHttpRequest]]</translate> <translate> <!--T:106--> Otherwise, the standard MediaWiki file upload form is displayed. <!--T:107--> Supported browsers include Firefox 13+, Chrome 21+, Internet Explorer 10+, Safari 7+ and Opera 12+. == Tasks == <!--T:41--> </translate> [[phab:tag/mediawiki-extensions-uploadwizard/|https://phabricator.wikimedia.org/tag/mediawiki-extensions-uploadwizard/]] <translate> == Other tools == <!--T:42--> <!--T:72--> Besides Upload Wizard, other upload tools are available to users, which are tracked at [[<tvar name=1>commons:Special:MyLanguage/Commons:Upload tools</tvar>|commons:Commons:Upload tools]]. </translate> [[Category:Multimedia{{#translation:}}]] 18tz9k78sunfleyi2wyskslzczfi2hp Installation/id 0 52733 5387788 1378822 2022-07-29T09:23:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/id]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/id]] s1n2g3lyke2lhc3tu2p7xtjqhjnov17 Manual:Installation guide/id 100 52738 5386654 5381091 2022-07-28T17:14:30Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/id]] s1n2g3lyke2lhc3tu2p7xtjqhjnov17 Template:InstallationNav/id 10 52740 5387201 5384789 2022-07-28T21:17:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installing MediaWiki/id 100 52746 5387499 5384971 2022-07-28T22:45:22Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">MediaWIki bisa jadi sulit diinstal bagi pengguna komputer rata-rata yang tidak punya pengalaman menggunakan Apache, PHP dan MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Mengunduh perangkat lunak MediaWiki == Unduh berkas tar MediaWiki dari [[Special:MyLanguage/Download|halaman pengunduhan resmi]]. Pada umumnya, jika Anda menggunakan lingkungan produksi, Anda sebaiknya menjalankan rilis stabil terbaru, yaitu MediaWiki {{MW stable release number}}. <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">Berkas-berkas yang diunduh memiliki format <code>.tar.gz</code>, jadi mereka perlu diekstrak sebelum digunakan.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span class="mw-translate-fuzzy">Ini bisa dilakukan secara lokal (dan kemudian diunggah via FTP) atau secara langsung di peladen Anda.</span> Ini biasanya dilakukan dengan perangkat lunak seperti [https://www.7-zip.org/ 7-Zip] (gratis), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] atau [https://www.izarc.org/ IZArc] (gratis) di Windows. Di Linux dan Mac OS X, Anda bisa mengekstrak berkasnya menggunakan perintah ini: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == Mengunggah berkas ke peladen anda== <div class="mw-translate-fuzzy"> Jika Anda belum mengunggah berkas-berkas ke peladen web Anda, lakukanlah sekarang. </div> Unggah berkas-berkasnya ke direktori web peladen web Anda dengan cara: # menyalin folder yang telah diekstrak secara langsung atau <div class="mw-translate-fuzzy"> # dengan menggunakan sebuah klien FTP seperti [https://filezilla-project.org/ FileZilla] (Perangkat Lunak Sumber Terbuka, Windows, OSX dan Linux) atau [https://cyberduck.io/ Cyberduck] (OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> Jika alat pengunggah Anda punya pilihan "ubah nama berkas menjadi huruf kecil", Anda harus menonaktifkannya. <span class="mw-translate-fuzzy">Jika Anda menginstal Apache, direktori yang benar ditentukan dalam berkas <code>httpd.conf</code> Anda (direktif [$docroot DocumentRoot], biasanya $1 atau {{$2|apache-folder}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Catatan: Ini diubah di Ubuntu 14.04 dengan Apache 2.4.7 di mana berkas konfigurasi utama untuk pengaturan peladen dan direktori Apache adalah <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Ubah nama folder yang diunggah menjadi apapun yang Anda ingin tampilkan di URL. <span class="mw-translate-fuzzy">Jika peladen web Anda dijalankan sebagai misalnya <code>http://localhost</code>, mengubah namanya menjadi direktori <code>/w/</code> berarti Anda akan mengakses wiki Anda di <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span class="mw-translate-fuzzy">'''''Jangan gunakan <code>/wiki/</code> apabila Anda ingin menggunaknnya sebagai [[Special:MyLanguage/Manual:Short URL|URL Singkat]].'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Membuat sebuah basis data == </div> <div class="mw-translate-fuzzy"> MediaWiki akan menanyakan nama basis data dan pengguna dan akan mencoba membuat mereka apabila mereka belum ada. </div> <div class="mw-translate-fuzzy"> Jika Anda sudah punya peladen basis data dan tahu kata sandi root untuknya, skrip instalasi MediaWiki bisa membuat basis data baru untuk Anda. </div> <div class="mw-translate-fuzzy"> Jika Anda tidak tahu kata sandi rootnya, misalnya apabila Anda menggunakan peladen yang dihos, Anda harus membuat basis data yang baru. </div> <span class="mw-translate-fuzzy">Untuk sekarang, Anda harus menggunakan SQLite, MariaDB/MySQL atau PostgreSQL untuk menyimpan isi wiki Anda.</span> <span class="mw-translate-fuzzy">Jika Anda tidak yakin basis data yang mana yang mau dipilih, gunakan MariaDB karena itulah yang didukung dengan paling baik oleh MediaWiki.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">Di halaman instalasi, Anda perlu memilih nama basis data (bisa apapun namanya) dan direktori basis data SQLite.</span> Untuk direktori basis data, penginstal akan mencoba menggunakan sebuah subdirektori di luar akar dokumen dan membuatnya apabila diperlukan. Jika direktori ini tidak aman (contohnya, bisa dibaca dari web), ubah secara manual agar direktorinya tidak bisa diakses oleh semua orang di web. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Lihat dokumentasi yang sesuai.</span> <span class="mw-translate-fuzzy">Untuk alternatifnya, hubungi penyedia hos Anda untuk meminta mereka membuat akun bagi Anda.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Jika basis data Anda tidak dijalankan di peladen yang sama dengan peladen web Anda, Anda perlu memberikan nama hos peladen web &mdash; mediawiki.example.com dalam contoh di bawah &mdash; sebagaimana berikut: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span class="mw-translate-fuzzy">MySQL/MariaDB di UNIX/Linux mencatat semua kueri yang dikirimkan kepadanya ke dalam satu berkas, yang akan mengandung kata sandi yang Anda gunakan untuk akun pengguna.</span> <span class="mw-translate-fuzzy">Jika ini membuat Anda khawatir, hapus berkas <code>.mysql_history</code> Anda setelah menjalankan kueri-kueri tersebut.</span>}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Jika Anda menggunakan PostgreSQL, Anda akan memerlukan antara basis data dan pengguna yang dibuatkan untuk Anda, atau tinggal menyediakan nama pengguna PostgreSQL dengan hak "superuser" ke isian konfigurasi.</span> <span class="mw-translate-fuzzy">Biasanya, ini adalah pengguna basis data yang bernama '''postgres'''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (kemudian masukkan kata sandi) createdb -O wikiuser my_wiki atau sebagai superuser (''default'' postgres) jalankan perintah-perintah berikut di wantian basis data: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> Perhatikan [[phab:tag/postgreSQL|daftar masalah yang diketahui apabila menjalankan MediaWiki menggunakan PostgreSQL]]. {{anchor|Run the installation script}} == Menjalankan skrip instalasi == <div class="mw-translate-fuzzy"> Setelah semua langkah di atas selesai, Anda bisa menyelesaikan instalasi melalui peramban web dengan pergi ke URL index.php di peramban Anda — periksa instruksi yang disebutkan di {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> == Langkah selanjutnya == </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Pastikan muktahir! == Setelah menginstal, pastikan Anda memerhatikan rilis yang mutakhir, dan tetap jaga keamanan peladen Anda! {{Clickable button 2|<span class="mw-translate-fuzzy">[[$maillist|Berlanggananlah dengan milis pengumuman rilis kami.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Lihat pula == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] t8rwm9cki64ti51qkeymwgutar6z54v Manual:Installation guide/ro 100 56911 5386665 5381104 2022-07-28T17:14:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ro]] 9m5lxj1g0c43hyn1858rfjeir8sqsv0 5386683 5386665 2022-07-28T17:21:50Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/ro]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Installation/th 0 58238 5387799 1378823 2022-07-29T09:25:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Instalacja mediawiki 0 61845 5387774 429907 2022-07-29T09:21:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/pl]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pl]] b6zf9uu302z9prb61dalq114ribkgg6 Extension talk:Page Schemas 103 62783 5386330 5385523 2022-07-28T13:05:43Z Yaron Koren 15560 /* TypeError: Illegal offset type in isset or empty */ wikitext text/x-wiki {{Archive box| * [[Extension talk:Page Schemas/Archive 2013 to 2015|2013 to 2015]] }} == Only for editors == Is it possible to use ''<nowiki><span class="onlyforeditors">{{{Lorem ipsum|}}}</span></nowiki>'' in combination with Page Schemas? :What is "onlyforeditors"? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:22, 15 May 2018 (UTC) I think I can help here by clarifying things: what we would like to have is something like this in the schema XML: <pre> <Field name="somefieldname" display="nonempty" displayclass="somehtmlclassname"> </pre> This should result to this in the generated template: <pre> {#if:{{{somefieldname|}}}| {{!}}- class="somehtmlclassname" ! somefieldlabel {{!}} [[somepropertyname::{{{somefieldname|}}}]]}} </pre> Is this possible? Does it need a code change? If yes, any hints where and how complex? :I don't think there's any way to add an HTML class to a generated table row, unfortunately. I don't know how complex it would be to add it. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:23, 23 May 2018 (UTC) == Change allowed values == If I change the names of the allowed values (e.g. to correct a typo) I get the message "[new name] is not in the list of the allowed values of the ... property". Is it possible to change the spelling of the allowed values? :The [[Extension:ReplaceText|ReplaceText]] extension may help with this, if I understand the issue correctly. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:26, 19 March 2018 (UTC) == Customise templates == This is similar to a query back in 2014 ([[#Adding additional information to generated templates]]) but I wondered if anything had changed. I would like to add some custom information to the template, but each time I edit the Schema and generate pages, this is lost. (In my case I'd like to add a Cargo query which displays a location on a map.) Is this possible, without having to manually cut and paste each time? Thanks. [[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 23:41, 21 November 2016 (UTC) :Still no. There's a lot that could be improved in Page Schemas - it's not that popular an extension, I don't think, so it hasn't gotten a lot of attention. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 03:30, 22 November 2016 (UTC) ::That's a shame, as the ability easily to change the data structure and the associated template/form pages seems invaluable. I found it very useful at the start when working things out. [[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 00:37, 3 December 2016 (UTC) :: Regarding "popularity", I've tried both the manual and the schema way, and this extension has the potential to make really smooth the use of of Forms. And this little feature is the stumbling block. Untill it's fixed, you have to edit + generate forms in 2-steps, to redo customizations. :: Thanks anyways [[User:Ankostis|Ankostis]] ([[User talk:Ankostis|talk]]) 02:41, 20 September 2018 (UTC) == tooltips in page forms using Cargo == --[[Special:Contributions/138.232.124.69|138.232.124.69]] 12:42, 28 March 2018 (UTC) Since switching to Cargo from SMW the tooltips I have on my forms don't display as tooltips. They're just text on the page, even though the schema generator has this notation in it "Show description as pop-up tooltip" :I'm guessing that the template is calling #info. That's no longer working because #info is defined by SMW (strangely, SMW includes its own tooltip functionality). I would recommend installing the [[Extension:SimpleTooltip|SimpleTooltip]] extension - then, if you recreate the template from the schema, the #info calls will hopefully get changed to #tip-text calls. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:01, 2 June 2017 (UTC) : that does it! The new class is actually: #tip-info cheers --[[User:Anrake|Anrake]] ([[User talk:Anrake|talk]]) 14:53, 2 June 2017 (UTC) == Jobs not running == I've had several Page Schemas jobs in the queue for over 3 days. I'm adding a new category and want to use it to scaffold the template, form and new semantic properties. I've tried all the tricks I can find to force them to run including changing job_attempts to 0, various combinations of $wgJobRunRate and $wgRunJobsAsync but nothing seems to work. Tonight I tried to delete the jobs and run Generate Pages again, but they still got stuck. I even ran update.php and rebuilt the Semantic index. The last time I used Page Schemas was probably last July. Are there any ideas to force these to run? MediaWiki 1.28.0 PHP 5.6.33 (cgi-fcgi) MySQL 5.6.38-83.0 Semantic MediaWiki 2.5.5 Page Schemas 0.4.6 --[[User:Anrake|Anrake]] ([[User talk:Anrake|talk]]) 11:39, 22 January 2018 (UTC) :Have you tried calling runJobs.php? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:08, 22 January 2018 (UTC) :yeah, many times. --[[User:Anrake|Anrake]] ([[User talk:Anrake|talk]]) 14:43, 22 January 2018 (UTC) ::And what happens? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 17:35, 22 January 2018 (UTC) ::: nothing, there's no output, as though the jobs don't exist. Other jobs run, if they exist, but not anything from "pageSchemasCreatePage". showJobs.php outputs 0. --[[User:Anrake|Anrake]] ([[User talk:Anrake|talk]]) 21:19, 22 January 2018 (UTC) == Unregistered users may see only certain fields == Is it possible to configure Page Schemas/MediaWiki so that unregistered users are able to see only certain fields? :No. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 00:41, 26 March 2018 (UTC) ::To bad. Is a woraround possible? --[[Special:Contributions/138.232.124.69|138.232.124.69]] 12:42, 28 March 2018 (UTC) :::Could you explain what the need is? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 19:15, 28 March 2018 (UTC) ::::I'm using Mediawiki in combination with PageSchemas to create a DB. Until now the DB is only a working tool, but we plan to go online in a few weeks. Since it is for the moment a private DB there are some fields in our schemas containing notes that are supposed to be only private notes for the contributors. Is it possible to cofigure MediaWiki/PageSchemas in such a way, that certain fields may not bee seen by unregistered users? --[[Special:Contributions/93.70.101.215|93.70.101.215]] 07:45, 1 April 2018 (UTC) :Oh, I see - you mean actual data fields; I thought you meant fields within the Special:EditSchema form. In either case, the answer is no. If there's data that you don't want certain users to see, the best solution is to keep it out of the wiki altogether - and it may make sense to create a separate, more restricted wiki to contain just that data. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 18:00, 2 April 2018 (UTC) == Issue Installing to MW 1.31 == Should this extension work with 1.31? I Downloaded the version of this extension marked for MW 1.31. Trying to run update.php. Getting the following error: <pre> /home/gunsywtx/public_html/maintenance$ php update.php Fatal error: Uncaught Exception: /home/gunsywtx/public_html/extensions/PageSchemas/extension.json does not exist! in /home/gunsywtx/public_html/includes/registration/ExtensionRegistry.php:107 Stack trace: #0 /home/gunsywtx/public_html/includes/GlobalFunctions.php(50): ExtensionRegistry->queue('/home/gunsywtx/...') #1 /home/gunsywtx/public_html/LocalSettings.php(230): wfLoadExtension('PageSchemas') #2 /home/gunsywtx/public_html/includes/Setup.php(94): require_once('/home/gunsywtx/...') #3 /home/gunsywtx/public_html/maintenance/doMaintenance.php(81): require_once('/home/gunsywtx/...') #4 /home/gunsywtx/public_html/maintenance/update.php(245): require_once('/home/gunsywtx/...') #5 {main} thrown in /home/gunsywtx/public_html/includes/registration/ExtensionRegistry.php on line 107 </pre> :Yes, using the "ExtensionDistributor" with any of my extensions is generally not a good idea, because it just represents a random, and usually outdated, snapshot. I would try using the latest Page Schemas code instead. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 15:13, 25 June 2018 (UTC) == More Documentation? == Besides the video and the landing page for this extension, is there any other source of documentation? [[User:Ankostis|Ankostis]] ([[User talk:Ankostis|talk]]) 14:06, 19 September 2018 (UTC) :There's also [http://workingwithmediawiki.com/book/chapter18.html#toc-Section-111 this], though it's not much. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 01:05, 20 September 2018 (UTC) == Page Schema Infobox Templates == Can you set a template created by Page Schemas to output an Infobox or that can only be done by editing the source code after Page Schemas creates the template? :What do you mean by an "infobox"? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 16:13, 15 November 2018 (UTC) == Schema Not Saving == I have two issues, really. 1) I've found a scenario where the "Save Page" function in the "Edit Schema" tab no longer actually saves the schema. If I create a schema from a blank category, and use the form in "Edit Schema" to do so, everything is great. If, however, I edit the schema using the "Edit" tab, then I'm no longer able to save changes made to the schema using the "Edit Schema" form. The schema is locked to the revision created during the manual "Edit". I first noticed this when I was attempting to manually fix another issue... 2) When adding a Semantic property of type "Telephone Number", the "Edit Schema" form would show it in the dropdown as "Telephone 2ber" if it was the 2nd field, or "Telephone 3ber" if it was the third, and so on. That strange "2ber" or "3ber" or "7ber" would show up in the raw schema XML. I changed it manually in the "Edit" tab, but then realized that I was locked to that revision. I thought I was losing my mind for a bit, but I was able to determine the above. Any thoughts? I enabled debug in LocalSettings.php, but no messages show up. {| | MediaWiki | 1.31.1 |- | PHP | 7.0.33-0+deb9u1 (apache2handler) |- | MariaDB | 10.1.37-MariaDB-0+deb9u1 |- | Semantic Forms Select | 3.0.0 |- | Semantic MediaWiki | 3.0.0 |- | Semantic Result Formats | 3.0.0 |- | Page Forms | 4.4.2 |- | Page Schemas | 0.4.8 |- | WYSIWYG editor Wysiwyg | 1.5.6_0 |} --[[User:dvicci|dvicci]] ([[User talk:dvicci|talk]]) 02:23, 29 December 2018 (UTC) :Sorry about that! No, you're not losing your mind. I actually had a fix for this right after you reported it, but forgot to check it in until now. I just checked it in. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 19:22, 14 January 2019 (UTC) == Values parameter + Documentation == How do I enter multiple values for a dropdown input type? I can easily get this working with Page Forms but can't figure out what to put in the field to make this happen in Page Schemas. It would be very helpful to have some documentation for this plugin that outlines how to write parameters and values for each input type as well as providing direct examples. Thx. [[User:TiltedCerebellum|TiltedCerebellum]] ([[User talk:TiltedCerebellum|talk]]) 05:13, 5 June 2019 (UTC) :Sorry for the long delay. I think you're using neither Cargo nor SMW, so the set the values has to be defined for the form input itself. If you add into the big "Enter parameter names ..." input something like "values=A\,B\,C", that should hopefully work. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 16:26, 12 August 2019 (UTC) == Mysterious error == When I try to create a schema, I get this error after trying to save: <code>[468c584a827a82492f74bb3f] 2019-08-11 00:20:09: Fatal exception of type "Error"</code> I've turned on PHP debugging and nothing shows up. I don't know how to debug this. :If you add "$wgShowExceptionDetails = true;" to LocalSettings.php, it may produce a more useful error message. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 15:53, 12 August 2019 (UTC) == Link to schema value? == If I were to include a field in the schema that provided a unique ID for the page could I link to the page using the value of the field? :If you're using Cargo or SMW, you can do it by querying on the ID field... if I understand your question correctly. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 18:35, 3 October 2019 (UTC) == Template from Schema with display="nonempty" == The template code seems to be missing two brackets closing the #if statement. This is the schema: <syntaxhighlight> <PageSchema> <pageforms_Form name="Test (Form Name)"> <standardInputs freeTextLabel="Free text" inputFreeText="1" inputWatch="1" inputSave="1" inputPreview="1" inputChanges="1" inputCancel="1"/> </pageforms_Form> <Template name="Test"> <Field name="has property1 (Name)" display="nonempty"> <Label>Property1 (Display label)</Label> <pageforms_FormInput> <InputType>checkboxes</InputType> </pageforms_FormInput> <semanticmediawiki_Property name=""> <Type>Page</Type> <AllowedValue>Value1</AllowedValue> <AllowedValue>Value2</AllowedValue> <AllowedValue>Value3</AllowedValue> </semanticmediawiki_Property> </Field> </Template> </PageSchema> </syntaxhighlight> This is the template generated: <syntaxhighlight> <noinclude> This is the "Test" template. It should be called in the following format: <pre> {{Test |has property1 (Name)= }} </pre> Edit the page to see the template text. </noinclude><includeonly>{| class="wikitable" {{#if:{{{has property1 (Name)|}}}|! Property1 (Display label) {{!}} [[has property1 (Name)::{{{has property1 (Name)|}}}]] |} [[Category:Test]] </includeonly> </syntaxhighlight> Installed versions are: MW 1.33.1 , PHP 7.3.10 (cgi-fcgi) , SMW 3.1.1 , Page Forms 4.6 , Page Schemas 0.4.9 , ParserFunctions 1.6.0 Maybe it is related to the [[Extension_talk:Page_Forms#Similar_Problem|other problem]] i am having? Thanx for your great work! Any suggestions? [[User:Andi 3ö|Andi 3ö]] ([[User talk:Andi 3ö|talk]]) 16:03, 6 December 2019 (UTC) == No permission on Create Schema == Hi, I haven't used SMW since 2008 so forgive me if this is something obvious. After installing the extension the Create Schema button is showing up in a Category page, but on clicking it I only get: ''Permission error'' ''You do not have permission to edit this page, for the following reason:'' ''The action you have requested is limited to users in the group: Users.'' This is as admin, staff, etc. across multiple users. I edited LocalSettings.php with: <pre> $wgGroupPermissions['user']['generatepages'] = true; </pre> and added: <pre> $wgGroupPermissions['user']['editschema'] = true; $wgGroupPermissions['user']['createschema'] = true; </pre> for safe measure. Also tried with 'staff' and 'admin' but the message never changes. Thanks! :What version of Page Schemas and MediaWiki are you running? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 02:41, 3 March 2020 (UTC) <pre> MediaWiki 1.31.6 PHP 7.2.24-0ubuntu0.18.04.3 (apache2handler) MySQL 5.7.29-0ubuntu0.18.04.1 Page Schemas 0.5 (d493e62) 08:25, 26 February 2020 </pre> Thank you, sorry for not noticing your response earlier. :Sorry about that! It turns out that I accidentally inserted a major bug into Page Schemas a few weeks ago - permissions for "action=createschema" were reversed for those using MediaWiki 1.32 or lower. I just checked in a fix for it - hopefully it works correctly now. :By the way, there is a 'generatepages' permission, but there's no 'editschema' or 'createschema' permission - the simple 'edit' permission is used for those. Also, there's no 'admin' user group, at least by default - you're probably thinking of 'sysop'. Not really related to this problem; I just figured I should mention it. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 00:29, 11 March 2020 (UTC) == Possible conflict on using Page Schemas with both Cargo and Semantic Mediawiki == Hello, I'm currently working on a project that utilizes both Cargo and Semantic Mediawiki extensions. The problem I have is that when I define the XML schema and generate the Model and Category pages, the Cargo table declaration is removed from the Model page. This happens when I load the SM extension below the Cargo extension and be resolved if I reverse the order. My question is: is this behavior work as expected? Do we have side effects regarding the order of the two extensions? Thank you so much, :Yes, when both Cargo and SMW are installed, Page Schemas just goes with SMW. I could change it to just go with Cargo, but having it support both at the same time would take a good amount of work, unfortunately. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:07, 27 August 2020 (UTC) == 'Generate pages' action leads to Internal Error == PageSchemas generates an error when attempting to create new schemas: After defining the schema parameters, clicking the <code>Generate pages</code> button generates a MediaWiki error page describing an internal error (PageSchemas, not Apache). Here's the error I get: <pre> [e87dbf557df5020d7d144c03] /mediawiki/index.php?title=Category:MyCategoryName&action=generatepages Error from line 124 of /var/lib/mediawiki/extensions/SemanticInternalObjects/SIO_PageSchemas.php: Call to a member function getDatatypeLabels() on null Backtrace: #0 /var/lib/mediawiki/extensions/PageSchemas/includes/PSSchema.php(99): SIOPageSchemas::generatePages(PSSchema, array) #1 /var/lib/mediawiki/extensions/PageSchemas/includes/specials/PSGeneratePages.php(120): PSSchema->generateAllPages(array) #2 /var/lib/mediawiki/extensions/PageSchemas/includes/specials/PSGeneratePages.php(34): PSGeneratePages->generatePages(string, array) #3 /var/lib/mediawiki/extensions/PageSchemas/includes/PSGeneratePagesAction.php(37): PSGeneratePages->execute(string) #4 /usr/share/mediawiki/includes/MediaWiki.php(511): PSGeneratePagesAction->show() #5 /usr/share/mediawiki/includes/MediaWiki.php(302): MediaWiki->performAction(CategoryTreeCategoryPage, Title) #6 /usr/share/mediawiki/includes/MediaWiki.php(900): MediaWiki->performRequest() #7 /usr/share/mediawiki/includes/MediaWiki.php(527): MediaWiki->main() #8 /usr/share/mediawiki/index.php(44): MediaWiki->run() #9 {main} </pre> It's not really clear to me whether the cause of the error is Page Schemas or Semantic Internal Objects, so I re-installed both and re-ran <code>update.php</code> but no change in status. P.S. Existing schemas work just fine as-is, but cannot be modified (same error, if attempted). :The cause is Semantic Internal Objects - it clearly hasn't been updated to work with the latest SMW version. I would just uninstall SIO - you don't need it, since SMW's own #subobject does the same thing. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 00:17, 24 September 2020 (UTC) ::That fixed it! And I appreciate the insight; we weren't using the extension, it had been installed for eval & testing, which never happened of course, and then I'm guessing a recent extension upgrade created an incompatibility that hadn't existed before -- [[User:Milliard Gargantubrain|Milliard Gargantubrain]] ([[User talk:Milliard Gargantubrain|talk]]) 04:23, 24 September 2020 (UTC) == Error from line 841 of /PATH/extensions/PageForms/includes/PF_PageSchemas.php: Call to a member function setSectionLevel() on null == Hi everyone ! This is my setup: MediaWiki 1.31.10 PHP 7.3.25 (cgi-fcgi) MySQL 5.6.41-84.1 Page Schemas 0.5.1 Page Forms 4.9.5 Cought an error while creating my first schema: <pre> [X-n7TtcrY-TO@OHod5-r8wAAACE] /index.php?title=Categoria:Refer%C3%AAncias&action=generatepages Error from line 841 of /PATH/extensions/PageForms/includes/PF_PageSchemas.php: Call to a member function setSectionLevel() on null Backtrace: #0 /PATH/extensions/PageSchemas/PageSchemas.classes.php(385): PFPageSchemas::generatePages(PSSchema, array) #1 /PATH/extensions/PageSchemas/specials/PS_GeneratePages.php(87): PSSchema->generateAllPages(array) #2 /PATH/extensions/PageSchemas/specials/PS_GeneratePages.php(27): PSGeneratePages->generatePages(string, array) #3 /PATH/extensions/PageSchemas/PS_Tabs.php(70): PSGeneratePages->execute(string) #4 /PATH/includes/Hooks.php(177): PSTabs::onUnknownAction(string, CategoryTreeCategoryPage) #5 /PATH/includes/Hooks.php(205): Hooks::callHook(string, array, array, string) #6 /PATH/includes/MediaWiki.php(510): Hooks::run(string, array, string) #7 /PATH/includes/MediaWiki.php(294): MediaWiki->performAction(CategoryTreeCategoryPage, Title) #8 /PATH/includes/MediaWiki.php(818): MediaWiki->performRequest() #9 /PATH/includes/MediaWiki.php(524): MediaWiki->main() #10 /PATH/index.php(42): MediaWiki->run() #11 {main} </pre> Can you please help me solve this out ? Thanks in advance '''UPDATE:''' I managed to solve it. Upgraded to the master git version and disabled the HeaderTabs extension. Looks like there's a conflict. Thank you guys! :Sorry about the problem. I just checked in what I think is better handling for this, to the Page Forms code. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 15:33, 12 January 2021 (UTC) == How to use Start date, End date data type? == Can ''Start date, End date'' be used as data type for a Cargo field? If so, how? == Error when creating a schema == Hi I hope someone can help me with the following: When I click 'Create Schema' in a category, the following error appears: Internal error [ea03c8f0b07f04ef7fa2be09] /index.php?title=Category:Testcategory&action=editschema Error: Call to a member function getFormattedNamespaces() on null Backtrace: from [my-local-path]\extensions\PageSchemas\includes\specials\PSEditSchema.php(229) #0 [my-local-path]\extensions\PageSchemas\includes\specials\PSEditSchema.php(334): PSEditSchema::printNamespaceDropdown(string, string) #1 [my-local-path]\extensions\PageSchemas\includes\specials\PSEditSchema.php(469): PSEditSchema->printFieldSection() #2 [my-local-path]\extensions\PageSchemas\includes\specials\PSEditSchema.php(618): PSEditSchema->printTemplateSection() #3 [my-local-path]\extensions\PageSchemas\includes\specials\PSEditSchema.php(795): PSEditSchema->printForm() #4 [my-local-path]\extensions\PageSchemas\includes\PSEditSchemaAction.php(40): PSEditSchema->execute(string) #5 [my-local-path]\includes\MediaWiki.php(531): PSEditSchemaAction->show() #6 [my-local-path]\includes\MediaWiki.php(315): MediaWiki->performAction(CategoryTreeCategoryPage, Title) #7 [my-local-path]\includes\MediaWiki.php(913): MediaWiki->performRequest() #8 [my-local-path]\includes\MediaWiki.php(546): MediaWiki->main() #9 [my-local-path]\index.php(53): MediaWiki->run() #10 [my-local-path]\index.php(46): wfIndexMain() #11 {main} This error occurs in two local setups on my Windows 10 laptop, ''not'' in a third online SMW I am testing (so although I am not really good at this I did manage to get it working in one case, which is great!). One local setup is done with WinNMP 20.11, Mediawiki 1.36.0, with PHP 7.4.13, MariaDB 10.4.17, SMW 3.2.3, Page Schemas 0.5.2, Page Forms 5.2.1<br> The other failing setup is with XAMPP-portable, Mediawiki 1.36.0, PHP 8.07, MariaDB 10.4.19, SMW 3.2.3, Page Schemas 0.5.1, Page Forms 5.2.1<br> I guess there's something wrong with my Namespace configuration but I have no idea what. Thanks in advance for any help! :Sorry about the problem. It has nothing to do with your configuration - this is was a bug with the handling of MW 1.36 and higher that wasn't fixed until about a month ago. There hasn't been a new version released since the fix, so you'll have to use the latest Page Schemas code. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 20:07, 21 June 2021 (UTC) :: thank you for your prompt reply! That fixed it (I didn't notice my online version wasn't using MW 1.36, hence my fix on the local versions) Thanks again for your great work! ::: I hadn't fully tested until now: creating the schema works fine now but when I try to generate the pages I get this error, in my WinNMP-setup (not when doing the same in the MW 1.35 online version). [54fc1107f777db0d71ba2a05] /index.php?title=Category:Testcategory&action=generatepages Error: Call to a member function formatNum() on null Backtrace: from [my-local-path]extensions\SemanticMediaWiki\includes\SMW_PageSchemas.php(328) #0 [my-local-path]extensions\SemanticMediaWiki\includes\SMW_PageSchemas.php(297): SMWPageSchemas::createPropertyText(string, array, NULL) #1 [my-local-path]extensions\PageSchemas\includes\PSSchema.php(99): SMWPageSchemas::generatePages(PSSchema, array) #2 [my-local-path]extensions\PageSchemas\includes\specials\PSGeneratePages.php(122): PSSchema->generateAllPages(array) #3 [my-local-path]extensions\PageSchemas\includes\specials\PSGeneratePages.php(36): PSGeneratePages->generatePages(string, array) #4 [my-local-path]extensions\PageSchemas\includes\PSGeneratePagesAction.php(37): PSGeneratePages->execute(string) #5 [my-local-path]includes\MediaWiki.php(531): PSGeneratePagesAction->show() #6 [my-local-path]includes\MediaWiki.php(315): MediaWiki->performAction(CategoryTreeCategoryPage, Title) #7 [my-local-path]includes\MediaWiki.php(913): MediaWiki->performRequest() #8 [my-local-path]includes\MediaWiki.php(546): MediaWiki->main() #9 [my-local-path]index.php(53): MediaWiki->run() #10 [my-local-path]index.php(46): wfIndexMain() #11 {main} Again, all help is much appreciated ::::It looks like this is a bug in SMW - specifically, on [https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/includes/SMW_PageSchemas.php#L328 this line], the code shouldn't be using $wgContLang any longer, since it was removed in MW 1.36. I would let the SMW developers know about the problem. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:53, 27 June 2021 (UTC) ::::: Thanks again. I reported the problem and made another local setup for myself, using MW 1.35, so I can use your great extension. == Cargo query and Page Schemas == Hello, I need to include a Cargo query in my Template. I have a Template called "Project" and one called "Activities". Each Project can have multiple Activities. I do not want to manually select the Activities when editing a Project. I just need to show them on the Project page via a Cargo query. I could manually insert the query in the Template but it would get deleted if I modified the Page Schema. Am I right? Is there a way to accomplish this? Thank you. Carlo :Yes, regenerating the pages would wipe out whatever changes you made. At some point, if the template or anything else can't be created by Page Schemas, then you'll have to switch to just editing these pages manually, unfortunately. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:56, 14 October 2021 (UTC) == Missing #set function in multiple instance templates? == I created a schema with a multiple instance template and observed that hidden fields defined in the multiple instance template are displayed, actually as simple unformatted text. Comparing the template code with one of a common, single instance template, it seems that a call of the #set parser function is missing. At least, adding #set fixes the problem and the fields don't show up anymore as expected. Template code generated by Page Schemas: <pre> {{#subobject: [...]}} {| class="wikitable" [[P-PPN::{{{P-PPN|}}}]] [[E-PPN::{{{E-PPN|}}}]] [...] </pre> Fixed template code after inserting the #set-call: <pre> {{#subobject: [...]}} {{#set:P-PPN={{{P-PPN|}}}|E-PPN={{{E-PPN|}}}|}} {| class="wikitable" </pre> :Regular properties (outside of #subobject) shouldn't be getting set at all in multiple-instance templates - so the real bug is that it included those lines in the first place, it seems to me. I would just delete them; you don't need a #set call in their place either. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:58, 14 October 2021 (UTC) ::Thanks for your help! Deleting them solves the problem. [[User:MMFSoftwares|MMFSoftwares]] ([[User talk:MMFSoftwares|talk]]) 21:12, 14 October 2021 (UTC) == Custom delimiters not applied in generated forms and subobject section of templates. == I defined a custom delimiter (_) in ''text with autocomplete'' fields. In the template, the expected #arraymap function is included but in the form definition the parameters ''list'' and ''delimiter='' seems to be missing. Also, the sep parameter in #subobject does not contain the customized separator. == TypeError: Illegal offset type in isset or empty == Hello! Having a PHP error, and I can't quite figure my way to debugging it. When creating or editing a schema I get... === Error === <pre> [0f2bde35fd61a6941fcdf737] /index.php?title=Category:Person&action=editschema TypeError: Illegal offset type in isset or empty Backtrace: from /var/www/html/includes/Html.php(695) #0 /var/www/html/extensions/SemanticMediaWiki/includes/SMW_PageSchemas.php(194): Html::input() #1 /var/www/html/extensions/PageSchemas/includes/specials/PSEditSchema.php(436): SMWPageSchemas::getTemplateEditingHTML() #2 /var/www/html/extensions/PageSchemas/includes/specials/PSEditSchema.php(617): PSEditSchema->printTemplateSection() #3 /var/www/html/extensions/PageSchemas/includes/specials/PSEditSchema.php(794): PSEditSchema->printForm() #4 /var/www/html/extensions/PageSchemas/includes/PSEditSchemaAction.php(40): PSEditSchema->execute() #5 /var/www/html/includes/MediaWiki.php(543): PSEditSchemaAction->show() #6 /var/www/html/includes/MediaWiki.php(320): MediaWiki->performAction() #7 /var/www/html/includes/MediaWiki.php(930): MediaWiki->performRequest() #8 /var/www/html/includes/MediaWiki.php(564): MediaWiki->main() #9 /var/www/html/index.php(53): MediaWiki->run() #10 /var/www/html/index.php(46): wfIndexMain() #11 {main} </pre> === Versions === * PageSchemas version: `REL1_37` branch (<code>26e5cca</code>), though Special:Version shows <code>0.6 (bda97b1)</code> * MediaWiki 1.37.1 * PHP 8.0.8 * SMW 4.0.0 * Page Forms 5.3.4 <code>(16589e0)</code> :That looks like a bug in line 194 of SMW_PageSchemas.php, in Semantic MediaWiki. And it looks like a bug that I introduced, a very long time ago! I wonder how no one noticed it until now. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 01:18, 8 March 2022 (UTC) ::was any fix found for this? [[User:Sneeze5555|Sneeze5555]] ([[User talk:Sneeze5555|talk]]) 07:50, 28 July 2022 (UTC) :::I believe that line I mentioned, line 194 of [https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/includes/SMW_PageSchemas.php SMW_PageSchemas.php], which currently looks like: <syntaxhighlight lang="php"> $text .= Html::input( 'smw_connecting_property_num', $propName, [ 'size' => 15 ] ) . "\n"; </syntaxhighlight> :::...should instead look like: <syntaxhighlight lang="php"> $text .= Html::input( 'smw_connecting_property_num', $propName, 'text', [ 'size' => 15 ] ) . "\n"; </syntaxhighlight> :::And actually, looking at the code now, it looks like two other lines in that same file, 217 and 240, have the same problem. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:04, 28 July 2022 (UTC) == Understanding Sections == Can you explain two things please ? # If the output format is set to Sections - what is that supposed to do ? # What does the Add Section button achieve ? I tried to play with it but simply got this error when saving the changes '''Warning''': count(): Parameter must be an array or an object that implements Countable in '''xxxxxxx/extensions/PageSchemas/includes/PageSchemas.php''' on line '''247''' [[Special:Contributions/91.85.121.33|91.85.121.33]] 07:22, 31 May 2022 (UTC) :Sorry about that second problem - I just checked in what I think is a fix for it. But the "sections" format is supposed to make every field a separate section of the page, i.e. the field name becomes a section name (with the '==' around it), and then the field value is the contents of that section. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:03, 31 May 2022 (UTC) ::Brilliant. Thanks. Makes sense (though not something I can think of a use case ATM). [[Special:Contributions/91.85.121.33|91.85.121.33]] 21:03, 31 May 2022 (UTC) == Errors with Page Schema == I have been experimenting with Page Schema for a couple of days and getting to understand it better. I currently cannot get a Form to present itself as expected for a Library application I am building. I start by entering a unique book title, this end up appended to the Page title. # I get no Field for the book Title but get a Field Name and Label, # all field 'names' and field Labels appear concatenated after the field input box, Form input screen says Label will be before the field # One field I have specified as a Dropdown but the dropdown is part of the next field, # there is no label for the last field on the page, # even though I have marked the check box for 'pop-up tooltips' the text appears under the field (and not easy to read) # All dropdowns are empty. How are dropdowns meant to be populated? I assumed they would be taken from the Cargo specification where you need to enter the allowable values. I am using Mediawiki 1.36.2, Page Schemas 0.6 and Page Forms 5.3.4 Thank, Robert [[Special:Contributions/119.224.101.52|119.224.101.52]] 23:18, 14 July 2022 (UTC) :That's pretty bad. You are using somewhat old versions of Page Schemas and Page Forms, so I encourage you to get the latest versions of these extensions, to make sure that that's not the issue. (Don't worry, they will still work with MW 1.36.) I hope that will fix at least some of these problems... [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:55, 15 July 2022 (UTC) :: I have had both Extensions updated and it made little to no difference, so I started changing some options. I found the Culprit, is the "Allow multiple instances of this Template" option. If this is checked, the form is unuseable. I have since worked out I did not want that option anyway, not understanding exactly what is was doing. However, there are still two items that do not appear to behave as expected: 1. Pop-up tooltips, they still appear under the Field Name/Label, and 2. I am still intrigued why the Field Name and the Field Label are both displayed, one after the other in front of the Field box. I would have thought if you do not specify a Label, the Field Name will be used, otherwise just the Label, but never both straight after each other. It appears to just be a cosmetic thing so not all that important. Robert :::I tried replicating these problems with the current versions of Page Schemas and Page Forms, but I can't replicate any of the these many problems you list. I'm not sure how to go about debugging this - what are the biggest problem(s) you're seeing right now? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:45, 18 July 2022 (UTC) ::::I now only get the big errors if I have "Allow multiple instances of the Template" checked, that makes the form unuseable. So the two items that remain are, the field Name and Label are both displayed in front of the field. This causes confusion Why does the Field name display? Should that not just be an internal identifier? Secondly the Tooltip text does not seem to be working as a pop-up, it just displays under the Field Name/Label as a single line of text. Some of mine are of reasonable length placing the Field a long way from its Label. Is this the same issue as logged on 28 March 2018? Do I need to install an additional Extension? Thanks, Robert :::::I don't know why you're seeing both the field name and the label, and I can't replicate that problem. (I also can't replicate the problem with "allow multiple instances".) Could you pastebin the generated form and template? That might be helpful. As for tooltips - yes, you need an extension; the best one to use for that is [[Extension:RegularTooltips|RegularTooltips]]. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:17, 19 July 2022 (UTC) :::::: This is the Form <pre> <noinclude> This is the "Books" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Books|autocomplete on category=Books}} </noinclude><includeonly> {{{info|create title=Add a Book or Booklet}}} <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Books}}} {| class="formtable" ! Short-name Short-name: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Enter a unique short-name for this book. Differentiate similar titles by adding an Author abreviation.</p> | {{{field|BOOK_SHORT_NAME|size=50|mandatory}}} |- ! Full Title Full Title: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">enter the full Title of the Book or Booklet</p> | {{{field|Book_Full_Title|mandatory}}} |- ! Author(s) Authour Name(s): <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Enter all Author names, separated by commas, no spaces, eventually selectable from drop-down</p> | {{{field|AUTHOR_NAME|mandatory}}} |- ! Publisher Publisher: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Enter the Publishers name, eventually selectable from drop-down</p> | {{{field|PUBR_NAME|mandatory}}} |- ! Book Type Book Type: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Select a book type from the list</p> | {{{field|Book_Type|input type=dropdown}}} |- ! ISBN No ISBN No: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Enter Book's ISBN number</p> | {{{field|ISBN}}} |- ! Book Width in mm Width (mm): <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Enter book width in mm</p> | {{{field|Width}}} |- ! Book Height in mm Height: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Enter Book height in mm</p> | {{{field|Height}}} |- ! Orientation Orientation: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Select orientation from list</p> | {{{field|Orientation|input type=dropdown|Portrait=|Landscape=}}} |- ! Book Format Format: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">Select the format from the list</p> | {{{field|Format|input type=dropdown}}} |} {{{end template}}} '''Free text:''' {{{standard input|free text|rows=10}}} </includeonly> </pre> And this is the Template <pre> <noinclude> {{#template_params:BOOK_SHORT_NAME (label=Short-name;namespace=User)|Book_Full_Title (label=Full Title;namespace=User)|AUTHOR_NAME (label=Authour Name(s);list;namespace=User)|PUBR_NAME (label=Publisher)|Book_Type (label=Book Type;namespace=User)|ISBN (label=ISBN No;namespace=User)|Width (label=Width (mm);namespace=User)|Height (namespace=User)|Orientation|Format}} {{#cargo_declare:_table=Books|BOOK_SHORT_NAME=Page|Book_Full_Title=Text|AUTHOR_NAME=List (,) of Text|PUBR_NAME=Text|Book_Type=Text (allowed values=Book,Booklet,Pamphlet,Report)|ISBN=Text|Width=Integer|Height=Integer|Orientation=Page (allowed values=Portrait,Landscape)|Format=Text (allowed values=Hard-cover,Soft-cover,Spiral-bound,Staple-bound,Stapled,Loose-leaf)}} </noinclude><includeonly>{{#cargo_store:_table=Books}} {{#template_display:_format=standard}} [[Category:Books]] </includeonly> </pre> Thanks for your time on this, I note that the majority of the Form code does not display but it is visible if you look at the Source Code of this page. I will be extending this table today, merging in another table that no longer needs to be separate. A useful feature of Page Schema would be 'Add a field above' just like you have in "Create a Class". Robert :Thanks, that's helpful. Now I see the issue: you filled in that "Text that will be printed before the field:" value for each field. That's the issue - I confess that I don't remember what that is for, but it's ''not'' the field label - it's text that's meant to go before it. So if you just blank those values, the problem should go away. And I agree that being able to add fields above would be helpful, as would being able to rearrange them. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 21:36, 19 July 2022 (UTC) 3v8d5gafdkn2yk51k6a4pmcl1gtpssx Manual:Hooks/GetDefaultSortkey 100 62916 5387515 4439815 2022-07-29T00:37:21Z RobinHood70 167869 /* Details */ Name didn't match example wikitext text/x-wiki {{MediaWikiHook |name=GetDefaultSortkey |version=1.18.0 |rev=91510 |args=$title, &$sortkey |source=Title.php |summary=Called when determining what the default sortkey would be for a page }} == Details == * <code>$title</code>: A Title object representing the page in question * <code>&$sortkey</code>: What sortkey to use unless a custom one is specified. If a custom sortkey was specified, this value would be used as a tie breaker for the specified sortkey. == Notes == After adding an extension that uses this hook, you should run <code>php [[Manual:updateCollation.php|updateCollation.php]] --force</code> to re-sort any existing category entries. What the default sortkey for a page is, is not stored in the DB, so things won't get updated until the category is removed and re-added to a page, or the maintenance script is run. This should not use any information that could change other then the title object, because such sortkeys are only re-calculated on page moves or if the category is removed and re-added. [[Category:Category hooks{{#translation:}}|{{SUBPAGENAME}}]] 1gvblz8m1wtdgvzr4ewcxeyeawb3zew Installation/diq 0 71788 5387781 1378824 2022-07-29T09:22:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Pywikibot/category.py 100 74194 5387691 5298487 2022-07-29T04:59:07Z Conan 180001 +source wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} <translate> == Syntax == <!--T:1--> <!--T:2--> The syntax is: </translate> python pwb.py category action [-option] <translate> <!--T:18--> where action can be one of the following. </translate> {| class="wikitable |- | <code>add</code> || <translate><!--T:19--> mass-add a category to a list of pages</translate> |- | <code>remove</code> || <translate><!--T:20--> remove category tag from all pages in a category</translate> |- | <code>move</code> || <translate><!--T:21--> move all pages in a category to another category</translate> |- | <code>tidy</code> || <translate><!--T:22--> tidy up a category by moving its articles into subcategories</translate> |- | <code>tree</code> || <translate><!--T:23--> show a tree of subcategories of a given category</translate> |- | <code>listify</code> || <translate><!--T:24--> make a list of all of the articles that are in a category</translate> |} <translate> <!--T:3--> and option can be one of the following. </translate> === <translate><!--T:4--> Options for <tvar name=1><code>add</code></tvar> action</translate> === {| class="wikitable" |- | <code>-person</code> || <translate><!--T:25--> sort persons by their last name</translate> |- | <code>-create</code> || <translate><!--T:26--> If a page doesn't exist, do not skip it, create it instead</translate> |- | <code>-redirect</code> || <translate><!--T:27--> Follow redirects</translate> |} <translate> <!--T:5--> For this action, [[<tvar name=1>#page_generators</tvar>|page generator options]] are supported. </translate> === <translate><!--T:6--> Options for <tvar name=1><code>listify</code></tvar> action</translate> === * -overwrite - <translate><!--T:28--> This overwrites the current page with the list even if something is already there.</translate> * -showimages - <translate><!--T:29--> This displays images rather than linking them in the list.</translate> * -talkpages - <translate><!--T:30--> This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</translate> === <translate><!--T:7--> Options for <tvar name=1><code>remove</code></tvar> action</translate> === * -nodelsum - <translate><!--T:31--> This specifies not to use the custom edit summary as the deletion reason.</translate> <translate><!--T:32--> Instead, it uses the default deletion reason for the language, which is "<tvar name=1>Category was disbanded</tvar>" in English.</translate> <translate> === Options for <tvar name=1><code>move</code></tvar> action === <!--T:8--> </translate> {| class="wikitable" | -hist || <translate><!--T:33--> Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</translate> |- | -nodelete || <translate><!--T:34--> Don't delete the old category after move</translate> |- | -nowb || <translate><!--T:35--> Don't update the wikibase repository</translate> |- | -allowsplit || <translate><!--T:36--> If that option is not set, it only moves the talk and main page together.</translate> |- | -mvtogether || <translate><!--T:37--> Only move the pages/subcategories of a category, if the target page (and talk page, if <tvar name=1>-allowsplit</tvar> is not set) doesn't exist.</translate> |- | -keepsortkey | <translate><!--T:38--> Use sortKey of the old category also for the new category.</translate> <translate><!--T:39--> If not specified, sortKey is removed.</translate> <translate><!--T:40--> An alternative method to keep sortKey is to use <tvar name=1>-inplace</tvar> option.</translate> |} === <translate><!--T:9--> Options for <tvar name=1><code>tidy</code></tvar> action</translate> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <translate><!--T:41--> Filter the articles in the specified namespaces.</translate> <translate><!--T:42--> Separate multiple namespace numbers or names with commas.</translate> <translate><!--T:43--> Examples:</translate> -ns:0,2,4 -ns:Help,MediaWiki |} === <translate><!--T:10--> Options for several actions</translate> === {| class="wikitable" | -rebuild || <translate><!--T:44--> reset the database</translate> |- | -from: | <translate><!--T:45--> The category to move from (for the <tvar name=1>move</tvar> option)</translate> <translate><!--T:46--> Also, the category to remove from in the <tvar name=1>remove</tvar> option</translate> <translate><!--T:47--> Also, the category to make a list of in the <tvar name=1>listify</tvar> option</translate> <translate><!--T:60--> See note below table.</translate> |- | -to: | <translate><!--T:48--> The category to move to (for the <tvar name=1>move</tvar> option)</translate> <translate><!--T:49--> Also, the name of the list to make in the <tvar name=1>listify</tvar> option</translate> <translate><!--T:61--> See note below table.</translate> |- | -batch || <translate><!--T:53--> Don't prompt to delete emptied categories (do it automatically).</translate> |- | -summary: || <translate><!--T:54--> Pick a custom edit summary for the bot.</translate> |- | -inplace || <translate><!--T:55--> Use this flag to change categories in place rather than rearranging them.</translate> |- | -recurse || <translate><!--T:56--> Recurse through all subcategories of categories.</translate> |- | -pagesonly || <translate><!--T:57--> While removing pages from a category, keep the subpage links and do not remove them</translate> |- | -match || <translate><!--T:58--> Only work on pages whose titles match the given regex (for <tvar name=1>move</tvar> and <tvar name=2>remove</tvar> actions).</translate> |- | -depth: || <translate><!--T:59--> The max depth limit beyond which no subcategories will be listed.</translate> |} {{note|1= <translate><!--T:62--> For options <tvar name=1>''-from''</tvar> and <tvar name=2>''-to''</tvar>:</translate> <translate><!--T:51--> If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</translate> <translate><!--T:52--> For instance, in BASH, use single quotes, e.g. <tvar name=1><code>-from:'Polar bears'</code></tvar>.</translate> <translate><!--T:63--> For categories containing a colon you must explicitly prepend the namespace prefix <tvar name=fromto2><code>category:</code></tvar> or its localized equivalent.</translate> <translate><!--T:11--> For actions <tvar name=2>''tidy''</tvar> and <tvar name=3>''tree''</tvar>, the bot will store the category structure locally in <tvar name=1><code>category.dump</code></tvar>.</translate> <translate><!--T:12--> This saves time and server load, but if it uses these data later, they may be outdated; use the <tvar name=1><code>-rebuild</code></tvar> parameter in this case.</translate> <translate><!--T:13--> For example, to create a new category from a list of persons, type:</translate> python pwb.py category add -person <translate> <!--T:14--> and follow the on-screen instructions. <!--T:15--> Or to do it all from the command-line, use the following syntax: </translate> python pwb.py category move -from:US -to:"United States" <translate> <!--T:16--> This will move all pages in the category <tvar name=1>US</tvar> to the category <tvar name=2>United States</tvar>. </translate> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <translate> == See also == <!--T:17--> </translate> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] 3y158s2bf8vyb1298r9bplwv860y03i 5387694 5387691 2022-07-29T05:33:38Z Conan 180001 function "clean" to diffuse large categories wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} <translate> == Syntax == <!--T:1--> <!--T:2--> The syntax is: </translate> python pwb.py category action [-option] <translate> <!--T:18--> where action can be one of the following. </translate> {| class="wikitable |- | <code>add</code> || <translate><!--T:19--> mass-add a category to a list of pages</translate> |- | <code>remove</code> || <translate><!--T:20--> remove category tag from all pages in a category</translate> |- | <code>move</code> || <translate><!--T:21--> move all pages in a category to another category</translate> |- | <code>tidy</code> || <translate><!--T:22--> tidy up a category by moving its articles into subcategories</translate> |- | <code>clean</code> || <translate><!--T:22--> assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories]</translate> |- | <code>tree</code> || <translate><!--T:23--> show a tree of subcategories of a given category</translate> |- | <code>listify</code> || <translate><!--T:24--> make a list of all of the articles that are in a category</translate> |} <translate> <!--T:3--> and option can be one of the following. </translate> === <translate><!--T:4--> Options for <tvar name=1><code>add</code></tvar> action</translate> === {| class="wikitable" |- | <code>-person</code> || <translate><!--T:25--> sort persons by their last name</translate> |- | <code>-create</code> || <translate><!--T:26--> If a page doesn't exist, do not skip it, create it instead</translate> |- | <code>-redirect</code> || <translate><!--T:27--> Follow redirects</translate> |} <translate> <!--T:5--> For this action, [[<tvar name=1>#page_generators</tvar>|page generator options]] are supported. </translate> === <translate><!--T:6--> Options for <tvar name=1><code>listify</code></tvar> action</translate> === * -overwrite - <translate><!--T:28--> This overwrites the current page with the list even if something is already there.</translate> * -showimages - <translate><!--T:29--> This displays images rather than linking them in the list.</translate> * -talkpages - <translate><!--T:30--> This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</translate> === <translate><!--T:7--> Options for <tvar name=1><code>remove</code></tvar> action</translate> === * -nodelsum - <translate><!--T:31--> This specifies not to use the custom edit summary as the deletion reason.</translate> <translate><!--T:32--> Instead, it uses the default deletion reason for the language, which is "<tvar name=1>Category was disbanded</tvar>" in English.</translate> <translate> === Options for <tvar name=1><code>move</code></tvar> action === <!--T:8--> </translate> {| class="wikitable" | -hist || <translate><!--T:33--> Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</translate> |- | -nodelete || <translate><!--T:34--> Don't delete the old category after move</translate> |- | -nowb || <translate><!--T:35--> Don't update the wikibase repository</translate> |- | -allowsplit || <translate><!--T:36--> If that option is not set, it only moves the talk and main page together.</translate> |- | -mvtogether || <translate><!--T:37--> Only move the pages/subcategories of a category, if the target page (and talk page, if <tvar name=1>-allowsplit</tvar> is not set) doesn't exist.</translate> |- | -keepsortkey | <translate><!--T:38--> Use sortKey of the old category also for the new category.</translate> <translate><!--T:39--> If not specified, sortKey is removed.</translate> <translate><!--T:40--> An alternative method to keep sortKey is to use <tvar name=1>-inplace</tvar> option.</translate> |} === <translate><!--T:9--> Options for <tvar name=1><code>tidy</code></tvar> action</translate> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <translate><!--T:41--> Filter the articles in the specified namespaces.</translate> <translate><!--T:42--> Separate multiple namespace numbers or names with commas.</translate> <translate><!--T:43--> Examples:</translate> -ns:0,2,4 -ns:Help,MediaWiki |} === <translate><!--T:10--> Options for several actions</translate> === {| class="wikitable" | -rebuild || <translate><!--T:44--> reset the database</translate> |- | -from: | <translate><!--T:45--> The category to move from (for the <tvar name=1>move</tvar> option)</translate> <translate><!--T:46--> Also, the category to remove from in the <tvar name=1>remove</tvar> option</translate> <translate><!--T:47--> Also, the category to make a list of in the <tvar name=1>listify</tvar> option</translate> <translate><!--T:60--> See note below table.</translate> |- | -to: | <translate><!--T:48--> The category to move to (for the <tvar name=1>move</tvar> option)</translate> <translate><!--T:49--> Also, the name of the list to make in the <tvar name=1>listify</tvar> option</translate> <translate><!--T:61--> See note below table.</translate> |- | -batch || <translate><!--T:53--> Don't prompt to delete emptied categories (do it automatically).</translate> |- | -summary: || <translate><!--T:54--> Pick a custom edit summary for the bot.</translate> |- | -inplace || <translate><!--T:55--> Use this flag to change categories in place rather than rearranging them.</translate> |- | -recurse || <translate><!--T:56--> Recurse through all subcategories of categories.</translate> |- | -pagesonly || <translate><!--T:57--> While removing pages from a category, keep the subpage links and do not remove them</translate> |- | -match || <translate><!--T:58--> Only work on pages whose titles match the given regex (for <tvar name=1>move</tvar> and <tvar name=2>remove</tvar> actions).</translate> |- | -depth: || <translate><!--T:59--> The max depth limit beyond which no subcategories will be listed.</translate> |} {{note|1= <translate><!--T:62--> For options <tvar name=1>''-from''</tvar> and <tvar name=2>''-to''</tvar>:</translate> <translate><!--T:51--> If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</translate> <translate><!--T:52--> For instance, in BASH, use single quotes, e.g. <tvar name=1><code>-from:'Polar bears'</code></tvar>.</translate> <translate><!--T:63--> For categories containing a colon you must explicitly prepend the namespace prefix <tvar name=fromto2><code>category:</code></tvar> or its localized equivalent.</translate> <translate><!--T:11--> For actions <tvar name=2>''tidy''</tvar> and <tvar name=3>''tree''</tvar>, the bot will store the category structure locally in <tvar name=1><code>category.dump</code></tvar>.</translate> <translate><!--T:12--> This saves time and server load, but if it uses these data later, they may be outdated; use the <tvar name=1><code>-rebuild</code></tvar> parameter in this case.</translate> <translate><!--T:13--> For example, to create a new category from a list of persons, type:</translate> python pwb.py category add -person <translate> <!--T:14--> and follow the on-screen instructions. <!--T:15--> Or to do it all from the command-line, use the following syntax: </translate> python pwb.py category move -from:US -to:"United States" <translate> <!--T:16--> This will move all pages in the category <tvar name=1>US</tvar> to the category <tvar name=2>United States</tvar>. </translate> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <translate> == See also == <!--T:17--> </translate> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] rg9hcmsbnixiuhvlc9c3km4gtr0t215 5387842 5387694 2022-07-29T10:19:32Z Shirayuki 472859 wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} <translate> == Syntax == <!--T:1--> <!--T:2--> The syntax is: </translate> python pwb.py category action [-option] <translate> <!--T:18--> where action can be one of the following. </translate> {| class="wikitable |- | <code>add</code> || <translate><!--T:19--> mass-add a category to a list of pages</translate> |- | <code>remove</code> || <translate><!--T:20--> remove category tag from all pages in a category</translate> |- | <code>move</code> || <translate><!--T:21--> move all pages in a category to another category</translate> |- | <code>tidy</code> || <translate><!--T:22--> tidy up a category by moving its articles into subcategories</translate> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <translate><!--T:23--> show a tree of subcategories of a given category</translate> |- | <code>listify</code> || <translate><!--T:24--> make a list of all of the articles that are in a category</translate> |} <translate> <!--T:3--> and option can be one of the following. </translate> === <translate><!--T:4--> Options for <tvar name=1><code>add</code></tvar> action</translate> === {| class="wikitable" |- | <code>-person</code> || <translate><!--T:25--> sort persons by their last name</translate> |- | <code>-create</code> || <translate><!--T:26--> If a page doesn't exist, do not skip it, create it instead</translate> |- | <code>-redirect</code> || <translate><!--T:27--> Follow redirects</translate> |} <translate> <!--T:5--> For this action, [[<tvar name=1>#page_generators</tvar>|page generator options]] are supported. </translate> === <translate><!--T:6--> Options for <tvar name=1><code>listify</code></tvar> action</translate> === * -overwrite - <translate><!--T:28--> This overwrites the current page with the list even if something is already there.</translate> * -showimages - <translate><!--T:29--> This displays images rather than linking them in the list.</translate> * -talkpages - <translate><!--T:30--> This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</translate> === <translate><!--T:7--> Options for <tvar name=1><code>remove</code></tvar> action</translate> === * -nodelsum - <translate><!--T:31--> This specifies not to use the custom edit summary as the deletion reason.</translate> <translate><!--T:32--> Instead, it uses the default deletion reason for the language, which is "<tvar name=1>Category was disbanded</tvar>" in English.</translate> <translate> === Options for <tvar name=1><code>move</code></tvar> action === <!--T:8--> </translate> {| class="wikitable" | -hist || <translate><!--T:33--> Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</translate> |- | -nodelete || <translate><!--T:34--> Don't delete the old category after move</translate> |- | -nowb || <translate><!--T:35--> Don't update the wikibase repository</translate> |- | -allowsplit || <translate><!--T:36--> If that option is not set, it only moves the talk and main page together.</translate> |- | -mvtogether || <translate><!--T:37--> Only move the pages/subcategories of a category, if the target page (and talk page, if <tvar name=1>-allowsplit</tvar> is not set) doesn't exist.</translate> |- | -keepsortkey | <translate><!--T:38--> Use sortKey of the old category also for the new category.</translate> <translate><!--T:39--> If not specified, sortKey is removed.</translate> <translate><!--T:40--> An alternative method to keep sortKey is to use <tvar name=1>-inplace</tvar> option.</translate> |} === <translate><!--T:9--> Options for <tvar name=1><code>tidy</code></tvar> action</translate> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <translate><!--T:41--> Filter the articles in the specified namespaces.</translate> <translate><!--T:42--> Separate multiple namespace numbers or names with commas.</translate> <translate><!--T:43--> Examples:</translate> -ns:0,2,4 -ns:Help,MediaWiki |} === <translate><!--T:10--> Options for several actions</translate> === {| class="wikitable" | -rebuild || <translate><!--T:44--> reset the database</translate> |- | -from: | <translate><!--T:45--> The category to move from (for the <tvar name=1>move</tvar> option)</translate> <translate><!--T:46--> Also, the category to remove from in the <tvar name=1>remove</tvar> option</translate> <translate><!--T:47--> Also, the category to make a list of in the <tvar name=1>listify</tvar> option</translate> <translate><!--T:60--> See note below table.</translate> |- | -to: | <translate><!--T:48--> The category to move to (for the <tvar name=1>move</tvar> option)</translate> <translate><!--T:49--> Also, the name of the list to make in the <tvar name=1>listify</tvar> option</translate> <translate><!--T:61--> See note below table.</translate> |- | -batch || <translate><!--T:53--> Don't prompt to delete emptied categories (do it automatically).</translate> |- | -summary: || <translate><!--T:54--> Pick a custom edit summary for the bot.</translate> |- | -inplace || <translate><!--T:55--> Use this flag to change categories in place rather than rearranging them.</translate> |- | -recurse || <translate><!--T:56--> Recurse through all subcategories of categories.</translate> |- | -pagesonly || <translate><!--T:57--> While removing pages from a category, keep the subpage links and do not remove them</translate> |- | -match || <translate><!--T:58--> Only work on pages whose titles match the given regex (for <tvar name=1>move</tvar> and <tvar name=2>remove</tvar> actions).</translate> |- | -depth: || <translate><!--T:59--> The max depth limit beyond which no subcategories will be listed.</translate> |} {{note|1= <translate><!--T:62--> For options <tvar name=1>''-from''</tvar> and <tvar name=2>''-to''</tvar>:</translate> <translate><!--T:51--> If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</translate> <translate><!--T:52--> For instance, in BASH, use single quotes, e.g. <tvar name=1><code>-from:'Polar bears'</code></tvar>.</translate> <translate><!--T:63--> For categories containing a colon you must explicitly prepend the namespace prefix <tvar name=fromto2><code>category:</code></tvar> or its localized equivalent.</translate> <translate><!--T:11--> For actions <tvar name=2>''tidy''</tvar> and <tvar name=3>''tree''</tvar>, the bot will store the category structure locally in <tvar name=1><code>category.dump</code></tvar>.</translate> <translate><!--T:12--> This saves time and server load, but if it uses these data later, they may be outdated; use the <tvar name=1><code>-rebuild</code></tvar> parameter in this case.</translate> <translate><!--T:13--> For example, to create a new category from a list of persons, type:</translate> python pwb.py category add -person <translate> <!--T:14--> and follow the on-screen instructions. <!--T:15--> Or to do it all from the command-line, use the following syntax: </translate> python pwb.py category move -from:US -to:"United States" <translate> <!--T:16--> This will move all pages in the category <tvar name=1>US</tvar> to the category <tvar name=2>United States</tvar>. </translate> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <translate> == See also == <!--T:17--> </translate> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] iyls9vuofma99z388t5ql6v4atmf0r5 Manual:Pywikibot/category.py/ca 100 74195 5387844 5299624 2022-07-29T10:19:54Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Syntax == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The syntax is: </div> python pwb.py category action [-option] <div lang="en" dir="ltr" class="mw-content-ltr"> where action can be one of the following. </div> {| class="wikitable |- | <code>add</code> || <span lang="en" dir="ltr" class="mw-content-ltr">mass-add a category to a list of pages</span> |- | <code>remove</code> || <span lang="en" dir="ltr" class="mw-content-ltr">remove category tag from all pages in a category</span> |- | <code>move</code> || <span lang="en" dir="ltr" class="mw-content-ltr">move all pages in a category to another category</span> |- | <code>tidy</code> || <span lang="en" dir="ltr" class="mw-content-ltr">tidy up a category by moving its articles into subcategories</span> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <span lang="en" dir="ltr" class="mw-content-ltr">show a tree of subcategories of a given category</span> |- | <code>listify</code> || <span lang="en" dir="ltr" class="mw-content-ltr">make a list of all of the articles that are in a category</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> and option can be one of the following. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>add</code> action</span> === {| class="wikitable" |- | <code>-person</code> || <span lang="en" dir="ltr" class="mw-content-ltr">sort persons by their last name</span> |- | <code>-create</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If a page doesn't exist, do not skip it, create it instead</span> |- | <code>-redirect</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Follow redirects</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> For this action, [[#page_generators|page generator options]] are supported. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>listify</code> action</span> === * -overwrite - <span lang="en" dir="ltr" class="mw-content-ltr">This overwrites the current page with the list even if something is already there.</span> * -showimages - <span lang="en" dir="ltr" class="mw-content-ltr">This displays images rather than linking them in the list.</span> * -talkpages - <span lang="en" dir="ltr" class="mw-content-ltr">This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>remove</code> action</span> === * -nodelsum - <span lang="en" dir="ltr" class="mw-content-ltr">This specifies not to use the custom edit summary as the deletion reason.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Options for <code>move</code> action === </div> {| class="wikitable" | -hist || <span lang="en" dir="ltr" class="mw-content-ltr">Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</span> |- | -nodelete || <span lang="en" dir="ltr" class="mw-content-ltr">Don't delete the old category after move</span> |- | -nowb || <span lang="en" dir="ltr" class="mw-content-ltr">Don't update the wikibase repository</span> |- | -allowsplit || <span lang="en" dir="ltr" class="mw-content-ltr">If that option is not set, it only moves the talk and main page together.</span> |- | -mvtogether || <span lang="en" dir="ltr" class="mw-content-ltr">Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist.</span> |- | -keepsortkey | <span lang="en" dir="ltr" class="mw-content-ltr">Use sortKey of the old category also for the new category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not specified, sortKey is removed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alternative method to keep sortKey is to use -inplace option.</span> |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>tidy</code> action</span> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Filter the articles in the specified namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Separate multiple namespace numbers or names with commas.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Examples:</span> -ns:0,2,4 -ns:Help,MediaWiki |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for several actions</span> === {| class="wikitable" | -rebuild || <span lang="en" dir="ltr" class="mw-content-ltr">reset the database</span> |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] 5a396zi19etbe5msq0dry2sfx3cvnrc Manual:Pywikibot/category.py/it 100 74196 5387849 5299631 2022-07-29T10:19:58Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Syntax == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The syntax is: </div> python pwb.py category action [-option] <div lang="en" dir="ltr" class="mw-content-ltr"> where action can be one of the following. </div> {| class="wikitable |- | <code>add</code> || <span lang="en" dir="ltr" class="mw-content-ltr">mass-add a category to a list of pages</span> |- | <code>remove</code> || <span lang="en" dir="ltr" class="mw-content-ltr">remove category tag from all pages in a category</span> |- | <code>move</code> || <span lang="en" dir="ltr" class="mw-content-ltr">move all pages in a category to another category</span> |- | <code>tidy</code> || <span lang="en" dir="ltr" class="mw-content-ltr">tidy up a category by moving its articles into subcategories</span> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <span lang="en" dir="ltr" class="mw-content-ltr">show a tree of subcategories of a given category</span> |- | <code>listify</code> || <span lang="en" dir="ltr" class="mw-content-ltr">make a list of all of the articles that are in a category</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> and option can be one of the following. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>add</code> action</span> === {| class="wikitable" |- | <code>-person</code> || <span lang="en" dir="ltr" class="mw-content-ltr">sort persons by their last name</span> |- | <code>-create</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If a page doesn't exist, do not skip it, create it instead</span> |- | <code>-redirect</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Follow redirects</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> For this action, [[#page_generators|page generator options]] are supported. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>listify</code> action</span> === * -overwrite - <span lang="en" dir="ltr" class="mw-content-ltr">This overwrites the current page with the list even if something is already there.</span> * -showimages - <span lang="en" dir="ltr" class="mw-content-ltr">This displays images rather than linking them in the list.</span> * -talkpages - <span lang="en" dir="ltr" class="mw-content-ltr">This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>remove</code> action</span> === * -nodelsum - <span lang="en" dir="ltr" class="mw-content-ltr">This specifies not to use the custom edit summary as the deletion reason.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Options for <code>move</code> action === </div> {| class="wikitable" | -hist || <span lang="en" dir="ltr" class="mw-content-ltr">Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</span> |- | -nodelete || <span lang="en" dir="ltr" class="mw-content-ltr">Don't delete the old category after move</span> |- | -nowb || <span lang="en" dir="ltr" class="mw-content-ltr">Don't update the wikibase repository</span> |- | -allowsplit || <span lang="en" dir="ltr" class="mw-content-ltr">If that option is not set, it only moves the talk and main page together.</span> |- | -mvtogether || <span lang="en" dir="ltr" class="mw-content-ltr">Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist.</span> |- | -keepsortkey | <span lang="en" dir="ltr" class="mw-content-ltr">Use sortKey of the old category also for the new category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not specified, sortKey is removed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alternative method to keep sortKey is to use -inplace option.</span> |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>tidy</code> action</span> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Filter the articles in the specified namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Separate multiple namespace numbers or names with commas.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Examples:</span> -ns:0,2,4 -ns:Help,MediaWiki |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for several actions</span> === {| class="wikitable" | -rebuild || <span lang="en" dir="ltr" class="mw-content-ltr">reset the database</span> |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] 5a396zi19etbe5msq0dry2sfx3cvnrc Manual:Pywikibot/category redirect.py 100 74197 5387829 4821165 2022-07-29T09:46:55Z MarcoAurelio 36007 category was renamed, and it has a different name at each project so link to the Wikidata item instead, but allow translation wikitext text/x-wiki <languages/> {{Git/pywikibot}} {{Pywikibot|scripts}} <translate> <!--T:1--> '''<tvar|filename>category_redirect.py</>''' is a {{<tvar|pywikibot>ll|Manual:Pywikibot</>|Pywikibot}} script used to move pages out of redirected categories. <!--T:2--> The bot will look for categories that are marked with a category redirect template, take the first parameter of the template as the target of the redirect, and move all pages and subcategories of the category there. It also changes hard redirects into soft redirects, and fixes double redirects. A log is written under &lt;userpage>/<tvar|crl>category_redirect_log</>. Only category pages that haven't been edited for a certain cooldown period (7 days by default) are taken into account. <!--T:3--> The following parameters are supported: </translate> {{Pywikibot command table beginning}} {{option|delay:#|2=<translate><!--T:4--> Set an amount of days. If the category is edited more recenty than given days, ignore it. Default is 7</translate>}} {{option|tiny|2=<translate><!--T:5--> Only loops over [[<tvar name="srcat">:d:Q8099903</tvar>|Category:Wikipedia non-empty soft redirected categories]] and moves all images, pages and categories in redirect categories to the target category</translate>}} {{Pywikibot command table end}} <translate> == Usage == <!--T:6--> </translate> <syntaxhighlight lang=shell-session> $ python pwb.py category_redirect [options] </syntaxhighlight> {{Manual:Pywikibot/Global Options}} [[Category:Pywikibot scripts{{#translation:}}|category_redirect]] 79hkuexc5yse64z5gaxmrti23rvivtx 5387856 5387829 2022-07-29T10:22:24Z Shirayuki 472859 make variable names untranslatable wikitext text/x-wiki <languages/> {{Git/pywikibot}} {{Pywikibot|scripts}} <translate> <!--T:1--> '''<tvar|filename>category_redirect.py</>''' is a {{<tvar|pywikibot>ll|Manual:Pywikibot</>|Pywikibot}} script used to move pages out of redirected categories. <!--T:2--> The bot will look for categories that are marked with a category redirect template, take the first parameter of the template as the target of the redirect, and move all pages and subcategories of the category there. It also changes hard redirects into soft redirects, and fixes double redirects. A log is written under &lt;userpage>/<tvar|crl>category_redirect_log</>. Only category pages that haven't been edited for a certain cooldown period (7 days by default) are taken into account. <!--T:3--> The following parameters are supported: </translate> {{Pywikibot command table beginning}} {{option|delay:#|2=<translate><!--T:4--> Set an amount of days. If the category is edited more recenty than given days, ignore it. Default is 7</translate>}} {{option|tiny|2=<translate><!--T:5--> Only loops over [[<tvar name=1>:d:Q8099903</tvar>|Category:Wikipedia non-empty soft redirected categories]] and moves all images, pages and categories in redirect categories to the target category</translate>}} {{Pywikibot command table end}} <translate> == Usage == <!--T:6--> </translate> <syntaxhighlight lang=shell-session> $ python pwb.py category_redirect [options] </syntaxhighlight> {{Manual:Pywikibot/Global Options}} [[Category:Pywikibot scripts{{#translation:}}|category_redirect]] 7jq8hf7i6d55vz3f6o1kxiij9wuvris Manual:Pywikibot/category.py/ko 100 74431 5387851 5299632 2022-07-29T10:20:00Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Syntax == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The syntax is: </div> python pwb.py category action [-option] <div lang="en" dir="ltr" class="mw-content-ltr"> where action can be one of the following. </div> {| class="wikitable |- | <code>add</code> || <span lang="en" dir="ltr" class="mw-content-ltr">mass-add a category to a list of pages</span> |- | <code>remove</code> || <span lang="en" dir="ltr" class="mw-content-ltr">remove category tag from all pages in a category</span> |- | <code>move</code> || <span lang="en" dir="ltr" class="mw-content-ltr">move all pages in a category to another category</span> |- | <code>tidy</code> || <span lang="en" dir="ltr" class="mw-content-ltr">tidy up a category by moving its articles into subcategories</span> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <span lang="en" dir="ltr" class="mw-content-ltr">show a tree of subcategories of a given category</span> |- | <code>listify</code> || <span lang="en" dir="ltr" class="mw-content-ltr">make a list of all of the articles that are in a category</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> and option can be one of the following. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>add</code> action</span> === {| class="wikitable" |- | <code>-person</code> || <span lang="en" dir="ltr" class="mw-content-ltr">sort persons by their last name</span> |- | <code>-create</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If a page doesn't exist, do not skip it, create it instead</span> |- | <code>-redirect</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Follow redirects</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> For this action, [[#page_generators|page generator options]] are supported. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>listify</code> action</span> === * -overwrite - <span lang="en" dir="ltr" class="mw-content-ltr">This overwrites the current page with the list even if something is already there.</span> * -showimages - <span lang="en" dir="ltr" class="mw-content-ltr">This displays images rather than linking them in the list.</span> * -talkpages - <span lang="en" dir="ltr" class="mw-content-ltr">This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>remove</code> action</span> === * -nodelsum - <span lang="en" dir="ltr" class="mw-content-ltr">This specifies not to use the custom edit summary as the deletion reason.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Options for <code>move</code> action === </div> {| class="wikitable" | -hist || <span lang="en" dir="ltr" class="mw-content-ltr">Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</span> |- | -nodelete || <span lang="en" dir="ltr" class="mw-content-ltr">Don't delete the old category after move</span> |- | -nowb || <span lang="en" dir="ltr" class="mw-content-ltr">Don't update the wikibase repository</span> |- | -allowsplit || <span lang="en" dir="ltr" class="mw-content-ltr">If that option is not set, it only moves the talk and main page together.</span> |- | -mvtogether || <span lang="en" dir="ltr" class="mw-content-ltr">Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist.</span> |- | -keepsortkey | <span lang="en" dir="ltr" class="mw-content-ltr">Use sortKey of the old category also for the new category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not specified, sortKey is removed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alternative method to keep sortKey is to use -inplace option.</span> |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>tidy</code> action</span> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Filter the articles in the specified namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Separate multiple namespace numbers or names with commas.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Examples:</span> -ns:0,2,4 -ns:Help,MediaWiki |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for several actions</span> === {| class="wikitable" | -rebuild || <span lang="en" dir="ltr" class="mw-content-ltr">reset the database</span> |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] 5a396zi19etbe5msq0dry2sfx3cvnrc Extension:Wikibase Client 102 85614 5387085 5244917 2022-07-28T20:22:32Z 203.96.241.26 wikitext text/x-wiki <languages/> {{shortcut|WBC}} {{Extension | status = stable | type1 = ajax | type2 = interface | type3 = data extraction | type4 = parser function | hook1 = LocalUserCreated | hook2 = WikibaseHandleChange | hook3 = ChangesListSpecialPageStructuredFilters | hook4 = UnitTestsList | hook5 = BaseTemplateToolbox | hook6 = OldChangesListRecentChangesLine | hook7 = EnhancedChangesListModifyLineData | hook8 = EnhancedChangesListModifyBlockLineData | hook9 = OutputPageParserOutput | hook10 = SkinTemplateGetLanguageLink | hook11 = ContentAlterParserOutput | hook12 = SidebarBeforeOutput | hook13 = ParserFirstCallInit | hook14 = SkinTemplateOutputPageBeforeExec | hook15 = SpecialMovepageAfterMove | hook16 = GetPreferences | hook17 = BeforePageDisplay | hook18 = ScribuntoExternalLibraries | hook19 = InfoAction | hook20 = EditPage::showStandardInputs:options | hook21 = BaseTemplateAfterPortlet | hook22 = ArticleDeleteAfterSuccess | hook23 = ParserLimitReportPrepare | hook24 = FormatAutocomments | hook25 = ParserClearState | hook26 = AbortEmailNotification | hook27 = SearchDataForIndex | hook28 = SearchIndexFields | hook29 = CirrusSearchAddQueryFeatures | hook30 = SkinAfterBottomScripts | hook31 = BeforeCreateEchoEvent | hook32 = EchoGetBundleRules | hook33 = LinksUpdateComplete | hook34 = ArticleDeleteComplete | hook35 = ParserCacheSaveComplete | hook36 = TitleMoveComplete | hook37 = ChangesListSpecialPageQuery | hook38 = MagicWordwgVariableIDs | hook39 = ParserGetVariableValueSwitch | hook40 = ResourceLoaderJqueryMsgModuleMagicWords | hook41 = LoadExtensionSchemaUpdates | hook42 = wgQueryPages | hook43 = SearchResultProvideDescription | newhook1 = WikibaseClientDataTypes | newhook2 = WikibaseClientEntityTypes | newhook3 = WikibaseClientOtherProjectsSidebar | newhook4 = WikibaseHandleChange | newhook5 = WikibaseHandleChanges | newhook6 = WikibaseClientSiteLinksForItem | author = [[WMDE_Engineering|The Wikidata team]]<br />([https://www.openhub.net/p/wikibase/contributors contributors list]) | image = | imagesize = 200 | version = | update = continuous updates | mediawiki = master | license = GPL-2.0+ | needs-updatephp = yes | download = {{WikimediaDownload|Wikibase|phab=EWBA}} | description = <translate><!--T:1--> Client for structured data repository</translate> | rights = | php = | phabricator = mediawiki-extensions-wikibaseclient | readme = {{git file|project=mediawiki/extensions/Wikibase|file=README.md|text=readme}} | changelog = | translate = ext-wikibase-client | compatibility policy = rel }} <translate> '''Wikibase Client''' is part of <tvar name=1>{{ll|Wikibase}}</tvar>.</translate> <translate><!--T:7--> Wikibase Client is an extension that acts as a client to the <tvar name=1>{{ll|Extension:Wikibase Repository|nsp=0}}</tvar> extension.</translate> <translate><!--T:8--> Its development is part of the [[<tvar name=1>m:Special:MyLanguage/Wikidata</tvar>|Wikidata]] project.</translate> <translate><!--T:9--> It allows to use and display data from a Wikibase Repository {{<tvar name=1>ll|Extension:Wikibase Client/Lua</tvar>|via Lua modules}} (<tvar name=2><code>mw.wikibase</code></tvar>) or {{<tvar name=3>ll|Wikibase/Installation/Advanced configuration#Data transclusion</tvar>|parser functions}} (<tvar name=4><code>#statements</code></tvar>, <tvar name=5><code>#property</code></tvar>).</translate> <translate><!--T:10--> Clients can also use centralized language links or {{<tvar name=1>ll|Extension:ArticlePlaceholder</tvar>|article placeholders}}.</translate> <translate> == Installation == <!--T:2--> </translate> <translate><!--T:11--> See {{<tvar name=1>ll|Wikibase/Installation</tvar>|basic installation instructions}}.</translate> <translate><!--T:12--> For experienced configuration options see {{<tvar name=1>ll|Wikibase/Installation/Advanced configuration#Wikibase Client</tvar>|Advanced Configuration}}.</translate> <translate> <!--T:13--> A complete documentation exists in the docs folder for Wikibase, and is published to [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/index.html</tvar> the Wikimedia documentation site]. == Features & Usage == <!--T:3--> <!--T:14--> For a list of features and how to use them see {{<tvar name=1>ll|Wikibase/Installation/Advanced configuration#Features & Usage</tvar>|Advanced configuration}}. == Available hooks == <!--T:4--> <!--T:15--> The documentation of the available PHP and JavaScript hooks can be found in these pages: <!--T:17--> * [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_hooks_php.html</tvar> PHP Hooks]</translate> <translate> <!--T:18--> * [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_hooks_js.html</tvar> JavaScript Hooks] == See also == <!--T:5--> </translate> * {{ll|Wikibase}} * {{ll|Extension:Wikibase Repository}} * [https://test.wikidata.org/ <translate><!--T:16--> Test client and repository site</translate>] * [[:d:Wikidata:How to use data on Wikimedia projects]] {{OnWikimedia}} [[Category:Wikibase extensions{{#translation:}}]] [[Category:Scribunto extensions{{#translation:}}]] lem5lrkl6tncji17wxaakz67vxqeufy 5387087 5387085 2022-07-28T20:23:34Z 203.96.241.26 wikitext text/x-wiki <languages/> <translate> '''Wikibase Client''' is part of <tvar name=1>{{ll|Wikibase}}</tvar>.</translate> <translate><!--T:7--> Wikibase Client is an extension that acts as a client to the <tvar name=1>{{ll|Extension:Wikibase Repository|nsp=0}}</tvar> extension.</translate> <translate><!--T:8--> Its development is part of the [[<tvar name=1>m:Special:MyLanguage/Wikidata</tvar>|Wikidata]] project.</translate> <translate><!--T:9--> It allows to use and display data from a Wikibase Repository {{<tvar name=1>ll|Extension:Wikibase Client/Lua</tvar>|via Lua modules}} (<tvar name=2><code>mw.wikibase</code></tvar>) or {{<tvar name=3>ll|Wikibase/Installation/Advanced configuration#Data transclusion</tvar>|parser functions}} (<tvar name=4><code>#statements</code></tvar>, <tvar name=5><code>#property</code></tvar>).</translate> <translate><!--T:10--> Clients can also use centralized language links or {{<tvar name=1>ll|Extension:ArticlePlaceholder</tvar>|article placeholders}}.</translate> <translate> == Installation == <!--T:2--> </translate> <translate><!--T:11--> See {{<tvar name=1>ll|Wikibase/Installation</tvar>|basic installation instructions}}.</translate> <translate><!--T:12--> For experienced configuration options see {{<tvar name=1>ll|Wikibase/Installation/Advanced configuration#Wikibase Client</tvar>|Advanced Configuration}}.</translate> <translate> <!--T:13--> A complete documentation exists in the docs folder for Wikibase, and is published to [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/index.html</tvar> the Wikimedia documentation site]. == Features & Usage == <!--T:3--> <!--T:14--> For a list of features and how to use them see {{<tvar name=1>ll|Wikibase/Installation/Advanced configuration#Features & Usage</tvar>|Advanced configuration}}. == Available hooks == <!--T:4--> <!--T:15--> The documentation of the available PHP and JavaScript hooks can be found in these pages: <!--T:17--> * [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_hooks_php.html</tvar> PHP Hooks]</translate> <translate> <!--T:18--> * [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_hooks_js.html</tvar> JavaScript Hooks] == See also == <!--T:5--> </translate> * {{ll|Wikibase}} * {{ll|Extension:Wikibase Repository}} * [https://test.wikidata.org/ <translate><!--T:16--> Test client and repository site</translate>] * [[:d:Wikidata:How to use data on Wikimedia projects]] {{OnWikimedia}} [[Category:Wikibase extensions{{#translation:}}]] [[Category:Scribunto extensions{{#translation:}}]] nl39j6akun2xyyawclfywqa6kzc4lkb 5387096 5387087 2022-07-28T20:28:43Z Hasley 11030752 Reverted edits by [[Special:Contribs/203.96.241.26|203.96.241.26]] ([[User talk:203.96.241.26|talk]]) to last version by Jon Harald Søby wikitext text/x-wiki <languages/> {{shortcut|WBC}} {{Extension | status = stable | type1 = ajax | type2 = interface | type3 = data extraction | type4 = parser function | hook1 = LocalUserCreated | hook2 = WikibaseHandleChange | hook3 = ChangesListSpecialPageStructuredFilters | hook4 = UnitTestsList | hook5 = BaseTemplateToolbox | hook6 = OldChangesListRecentChangesLine | hook7 = EnhancedChangesListModifyLineData | hook8 = EnhancedChangesListModifyBlockLineData | hook9 = OutputPageParserOutput | hook10 = SkinTemplateGetLanguageLink | hook11 = ContentAlterParserOutput | hook12 = SidebarBeforeOutput | hook13 = ParserFirstCallInit | hook14 = SkinTemplateOutputPageBeforeExec | hook15 = SpecialMovepageAfterMove | hook16 = GetPreferences | hook17 = BeforePageDisplay | hook18 = ScribuntoExternalLibraries | hook19 = InfoAction | hook20 = EditPage::showStandardInputs:options | hook21 = BaseTemplateAfterPortlet | hook22 = ArticleDeleteAfterSuccess | hook23 = ParserLimitReportPrepare | hook24 = FormatAutocomments | hook25 = ParserClearState | hook26 = AbortEmailNotification | hook27 = SearchDataForIndex | hook28 = SearchIndexFields | hook29 = CirrusSearchAddQueryFeatures | hook30 = SkinAfterBottomScripts | hook31 = BeforeCreateEchoEvent | hook32 = EchoGetBundleRules | hook33 = LinksUpdateComplete | hook34 = ArticleDeleteComplete | hook35 = ParserCacheSaveComplete | hook36 = TitleMoveComplete | hook37 = ChangesListSpecialPageQuery | hook38 = MagicWordwgVariableIDs | hook39 = ParserGetVariableValueSwitch | hook40 = ResourceLoaderJqueryMsgModuleMagicWords | hook41 = LoadExtensionSchemaUpdates | hook42 = wgQueryPages | hook43 = SearchResultProvideDescription | newhook1 = WikibaseClientDataTypes | newhook2 = WikibaseClientEntityTypes | newhook3 = WikibaseClientOtherProjectsSidebar | newhook4 = WikibaseHandleChange | newhook5 = WikibaseHandleChanges | newhook6 = WikibaseClientSiteLinksForItem | author = [[WMDE_Engineering|The Wikidata team]]<br />([https://www.openhub.net/p/wikibase/contributors contributors list]) | image = | imagesize = 200 | version = | update = continuous updates | mediawiki = master | license = GPL-2.0+ | needs-updatephp = yes | download = {{WikimediaDownload|Wikibase|phab=EWBA}} | description = <translate><!--T:1--> Client for structured data repository</translate> | rights = | php = | phabricator = mediawiki-extensions-wikibaseclient | readme = {{git file|project=mediawiki/extensions/Wikibase|file=README.md|text=readme}} | changelog = | translate = ext-wikibase-client | compatibility policy = rel }} <translate><!--T:6--> '''Wikibase Client''' is part of <tvar name=1>{{ll|Wikibase}}</tvar>.</translate> <translate><!--T:7--> Wikibase Client is an extension that acts as a client to the <tvar name=1>{{ll|Extension:Wikibase Repository|nsp=0}}</tvar> extension.</translate> <translate><!--T:8--> Its development is part of the [[<tvar name=1>m:Special:MyLanguage/Wikidata</tvar>|Wikidata]] project.</translate> <translate><!--T:9--> It allows to use and display data from a Wikibase Repository {{<tvar name=1>ll|Extension:Wikibase Client/Lua</tvar>|via Lua modules}} (<tvar name=2><code>mw.wikibase</code></tvar>) or {{<tvar name=3>ll|Wikibase/Installation/Advanced configuration#Data transclusion</tvar>|parser functions}} (<tvar name=4><code>#statements</code></tvar>, <tvar name=5><code>#property</code></tvar>).</translate> <translate><!--T:10--> Clients can also use centralized language links or {{<tvar name=1>ll|Extension:ArticlePlaceholder</tvar>|article placeholders}}.</translate> <translate> == Installation == <!--T:2--> </translate> <translate><!--T:11--> See {{<tvar name=1>ll|Wikibase/Installation</tvar>|basic installation instructions}}.</translate> <translate><!--T:12--> For experienced configuration options see {{<tvar name=1>ll|Wikibase/Installation/Advanced configuration#Wikibase Client</tvar>|Advanced Configuration}}.</translate> <translate> <!--T:13--> A complete documentation exists in the docs folder for Wikibase, and is published to [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/index.html</tvar> the Wikimedia documentation site]. == Features & Usage == <!--T:3--> <!--T:14--> For a list of features and how to use them see {{<tvar name=1>ll|Wikibase/Installation/Advanced configuration#Features & Usage</tvar>|Advanced configuration}}. == Available hooks == <!--T:4--> <!--T:15--> The documentation of the available PHP and JavaScript hooks can be found in these pages: <!--T:17--> * [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_hooks_php.html</tvar> PHP Hooks]</translate> <translate> <!--T:18--> * [<tvar name=url>https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_hooks_js.html</tvar> JavaScript Hooks] == See also == <!--T:5--> </translate> * {{ll|Wikibase}} * {{ll|Extension:Wikibase Repository}} * [https://test.wikidata.org/ <translate><!--T:16--> Test client and repository site</translate>] * [[:d:Wikidata:How to use data on Wikimedia projects]] {{OnWikimedia}} [[Category:Wikibase extensions{{#translation:}}]] [[Category:Scribunto extensions{{#translation:}}]] srthdze50b09fkwc1p3yrsaopmaw1e5 Manual:Combating spam/ru 100 94260 5387481 5200694 2022-07-28T22:40:21Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Как и для всех динамично развивающихся сайтов, спамеры на вики - обычное дело. <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki offers a number of features designed to [[Special:MyLanguage/Manual:Combating vandalism|combat vandalism in general]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">On this page we deal specifically with [[m:Wiki spam|wiki spam]], which is often automated.</span> == Общие сведения == Инструменты для борьбы со спамом на вики таковы: * Включение обязательности авторизации или/и капчи. * Блокировка возможности редактирования определённых IP-адресов. * Блокировка правок которые содержат нежелательные ссылки и ключевые слова. * Блокировка пользователей, чьи имена используются спам-ботами. Блокирование изменений, вносимых новыми или анонимными пользователями на определенные часто используемые страницы. Внесение в белый список известных хороших редакторов (например, администраторов, постоянных участников) при наложении ограничений на новых или анонимных пользователей Скрипты очистки или массовое удаление ({{ll|Extension:Nuke}}) существующих сообщений из недавно заблокированных спам-ботов Обычно будет использоваться комбинация различных методов, чтобы попытаться свести к минимуму количество спама, изменений, вносимых роботами и открытыми прокси, при одновременном ограничении количества нарушений, причиняемых законным пользователям сайта. Обратите внимание, что многие из этих функций не активированы по умолчанию. Если вы запускаете установку MediaWiki на своем сервере / хосте, то вы единственный, кто может внести необходимые изменения в конфигурацию! Обязательно просите своих пользователей [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (и делайте это сами), но в наши дни спам может легко сокрушить небольшие сообщества вики. Это помогает немного поднять планку. Однако следует также отметить, что ни одно из этих решений не может считаться полностью защищенным от спама. <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> Самые быстрые решения, которые стоит попробовать в первую очередь Борьба со спамом не должна быть слишком сложной. Если вы хотите быстро и радикально уменьшить спам, попробуйте сначала выполнить эти несколько шагов. <div lang="en" dir="ltr" class="mw-content-ltr"> * Install the [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] extension to block known spammer IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> Основы настройки антиспама {{anchor|CAPTCHA}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===CAPTCHA=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * all edits </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * edits adding new, unrecognized external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * user registration </div> <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Individual page protection=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. <div lang="en" dir="ltr" class="mw-content-ltr"> === Abuse filter === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Open proxies === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Apache configuration changes === </div> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Other ideas == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> == См. также == *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. <div lang="en" dir="ltr" class="mw-content-ltr"> === Extensions === </div> *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users <div lang="en" dir="ltr" class="mw-content-ltr"> === Settings === </div> * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External links === </div> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] 8qry0oro91wuorezk4cth0e9nmrg08c Extension:EventLogging 102 95343 5387099 5385008 2022-07-28T20:34:25Z HMonroy (WMF) 17151033 wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = <translate><!--T:21--> Provides a framework for logging analytics events</translate> |version = <translate><!--T:22--> continuous updates</translate> |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} <translate> <!--T:23--> The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. == Features == <!--T:24--> </translate> * <translate><!--T:25--> EventLogging supports client-side logging from JavaScript and server-side logging from PHP.</translate> * <translate><!--T:26--> Logging behavior can be dynamically configured using <tvar name=1>{{ll|Extension:EventStreamConfig}}</tvar>.</translate> * <translate><!--T:27--> The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository.</translate> * <translate><!--T:28--> The extension does not include any back-end code for transporting, parsing, or loading these events.</translate> <translate><!--T:29--> A separate service, <tvar name=1>[[wikitech:Event Platform/EventGate|EventGate]]</tvar>, implements this functionality and deals with inserting events into Kafka.</translate> <translate><!--T:30--> Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines.</translate> <translate><!--T:31--> The details of these components are specific to Wikimedia Foundation's configuration.</translate> <translate> == EventLogging at Wikimedia == <!--T:32--> <!--T:33--> The Wikimedia Foundation uses the EventLogging extension as part of a [[<tvar name=1>wikitech:Analytics/Systems/EventLogging</tvar>|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[<tvar name=2>m:Special:MyLanguage/Privacy policy</tvar>|privacy policy]] and [[<tvar name=3>m:Special:MyLanguage/Data retention guidelines</tvar>|data retention guidelines]]. </translate> <translate><!--T:34--> This page is about general use of the EventLogging extension.</translate> <translate><!--T:35--> The Wikimedia Foundation uses EventLogging with WMF specific backend components and [<tvar name=url>https://schema.wikimedia.org/#!/</tvar> schema repositories].</translate> <translate><!--T:36--> For Wikimedia specific and maintained documentation, see <tvar name=1>[[wikitech:Analytics/Systems/EventLogging]]</tvar> and <tvar name=2>[[wikitech:Event Platform]]</tvar>.</translate> ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <translate> === Configuring the schema location === <!--T:58--> <!--T:59--> By default, the extension will look for schemas on [[<tvar name=1>m:Special:MyLanguage/Meta-Wiki</tvar>|Meta-Wiki]].</translate> <translate><!--T:60--> The relevant default settings are:</translate> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <translate><!--T:61--> To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</translate> <translate><!--T:62--> E.g. to use the <tvar name=1><code>Schema</code></tvar> namespace of the local wiki, set</translate> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <translate><!--T:63--> (and ensure the user account that will create the schemas is [[<tvar name=1>Special:MyLanguage/Manual:Autoconfirmed users</tvar>|autoconfirmed]]).</translate> <translate> == Logging events using EventLogging == <!--T:37--> </translate> * {{ll|Extension:EventLogging/Guide}} - <translate><!--T:38--> to developing and deploying EventLogging schemas, and more</translate> * {{ll|Extension:EventLogging/Programming}} - <translate><!--T:39--> tips and suggestions for developers writing code to log events</translate> <translate> == Developing the EventLogging extension == <!--T:40--> === Developer setup === <!--T:41--> <!--T:42--> As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. ==== Using Docker ==== <!--T:43--> </translate> ''<translate><!--T:44--> See <tvar name=1>{{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}</tvar></translate>'' <translate> ==== Using <tvar name=1>mediawiki-vagrant</tvar> ==== <!--T:45--> </translate> <translate><!--T:46--> If you develop using mediawiki-vagrant, everything you need is encapsulated in the <tvar name=1><code>eventlogging</code></tvar> role.</translate> <translate><!--T:47--> To enable it, run:</translate> <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> <translate> ==== For JavaScript development ==== <!--T:48--> </translate> <translate><!--T:49--> If working on the JavaScript client, you'll need to install dependencies with <tvar name=1><code>npm install</code></tvar> from the folder you're developing in.</translate> <translate><!--T:50--> Then you can use <tvar name=1><code>npm test</code></tvar> to run ESLint for example.</translate> <translate><!--T:51--> The "How to run tests" section below points out how to see JavaScript test results.</translate> <translate>By adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered.</translate> <translate> ==== How to run tests ==== <!--T:52--> <!--T:53--> There are PHP tests, Python tests, and JavaScript tests. </translate> <translate><!--T:54--> To run JavaScript tests, visit <tvar name=1>Special:JavaScriptTest/qunit</tvar> on your development wiki.</translate> <translate><!--T:55--> (See <tvar name=1>{{ll|Manual:JavaScript unit testing}}</tvar>.)</translate> <translate><!--T:56--> To run PHP tests, we use PHPUnit.</translate> <translate><!--T:57--> Make sure it is installed, then:</translate> <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] fi8gddauum7ocg2wb09sinxis4ofjd6 5387100 5387099 2022-07-28T20:34:51Z HMonroy (WMF) 17151033 wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = <translate><!--T:21--> Provides a framework for logging analytics events</translate> |version = <translate><!--T:22--> continuous updates</translate> |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} <translate> <!--T:23--> The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. == Features == <!--T:24--> </translate> * <translate><!--T:25--> EventLogging supports client-side logging from JavaScript and server-side logging from PHP.</translate> * <translate><!--T:26--> Logging behavior can be dynamically configured using <tvar name=1>{{ll|Extension:EventStreamConfig}}</tvar>.</translate> * <translate><!--T:27--> The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository.</translate> * <translate><!--T:28--> The extension does not include any back-end code for transporting, parsing, or loading these events.</translate> <translate><!--T:29--> A separate service, <tvar name=1>[[wikitech:Event Platform/EventGate|EventGate]]</tvar>, implements this functionality and deals with inserting events into Kafka.</translate> <translate><!--T:30--> Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines.</translate> <translate><!--T:31--> The details of these components are specific to Wikimedia Foundation's configuration.</translate> <translate> == EventLogging at Wikimedia == <!--T:32--> <!--T:33--> The Wikimedia Foundation uses the EventLogging extension as part of a [[<tvar name=1>wikitech:Analytics/Systems/EventLogging</tvar>|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[<tvar name=2>m:Special:MyLanguage/Privacy policy</tvar>|privacy policy]] and [[<tvar name=3>m:Special:MyLanguage/Data retention guidelines</tvar>|data retention guidelines]]. </translate> <translate><!--T:34--> This page is about general use of the EventLogging extension.</translate> <translate><!--T:35--> The Wikimedia Foundation uses EventLogging with WMF specific backend components and [<tvar name=url>https://schema.wikimedia.org/#!/</tvar> schema repositories].</translate> <translate><!--T:36--> For Wikimedia specific and maintained documentation, see <tvar name=1>[[wikitech:Analytics/Systems/EventLogging]]</tvar> and <tvar name=2>[[wikitech:Event Platform]]</tvar>.</translate> ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <translate> === Configuring the schema location === <!--T:58--> <!--T:59--> By default, the extension will look for schemas on [[<tvar name=1>m:Special:MyLanguage/Meta-Wiki</tvar>|Meta-Wiki]].</translate> <translate><!--T:60--> The relevant default settings are:</translate> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <translate><!--T:61--> To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</translate> <translate><!--T:62--> E.g. to use the <tvar name=1><code>Schema</code></tvar> namespace of the local wiki, set</translate> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <translate><!--T:63--> (and ensure the user account that will create the schemas is [[<tvar name=1>Special:MyLanguage/Manual:Autoconfirmed users</tvar>|autoconfirmed]]).</translate> <translate> == Logging events using EventLogging == <!--T:37--> </translate> * {{ll|Extension:EventLogging/Guide}} - <translate><!--T:38--> to developing and deploying EventLogging schemas, and more</translate> * {{ll|Extension:EventLogging/Programming}} - <translate><!--T:39--> tips and suggestions for developers writing code to log events</translate> <translate> == Developing the EventLogging extension == <!--T:40--> === Developer setup === <!--T:41--> <!--T:42--> As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. ==== Using Docker ==== <!--T:43--> </translate> ''<translate><!--T:44--> See <tvar name=1>{{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}</tvar></translate>'' <translate> ==== Using <tvar name=1>mediawiki-vagrant</tvar> ==== <!--T:45--> </translate> <translate><!--T:46--> If you develop using mediawiki-vagrant, everything you need is encapsulated in the <tvar name=1><code>eventlogging</code></tvar> role.</translate> <translate><!--T:47--> To enable it, run:</translate> <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> <translate> ==== For JavaScript development ==== <!--T:48--> </translate> <translate><!--T:49--> If working on the JavaScript client, you'll need to install dependencies with <tvar name=1><code>npm install</code></tvar> from the folder you're developing in.</translate> <translate><!--T:50--> Then you can use <tvar name=1><code>npm test</code></tvar> to run ESLint for example.</translate> <translate><!--T:51--> The "How to run tests" section below points out how to see JavaScript test results.</translate> <translate>By adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered.</translate> <translate> ==== How to run tests ==== <!--T:52--> <!--T:53--> There are PHP tests, Python tests, and JavaScript tests. </translate> <translate><!--T:54--> To run JavaScript tests, visit <tvar name=1>Special:JavaScriptTest/qunit</tvar> on your development wiki.</translate> <translate><!--T:55--> (See <tvar name=1>{{ll|Manual:JavaScript unit testing}}</tvar>.)</translate> <translate><!--T:56--> To run PHP tests, we use PHPUnit.</translate> <translate><!--T:57--> Make sure it is installed, then:</translate> <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] a0tr7lj5r1kydqqo8sj4u55h2kzhj8p 5387116 5387100 2022-07-28T20:35:28Z HMonroy (WMF) 17151033 wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = <translate><!--T:21--> Provides a framework for logging analytics events</translate> |version = <translate><!--T:22--> continuous updates</translate> |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} <translate> <!--T:23--> The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. == Features == <!--T:24--> </translate> * <translate><!--T:25--> EventLogging supports client-side logging from JavaScript and server-side logging from PHP.</translate> * <translate><!--T:26--> Logging behavior can be dynamically configured using <tvar name=1>{{ll|Extension:EventStreamConfig}}</tvar>.</translate> * <translate><!--T:27--> The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository.</translate> * <translate><!--T:28--> The extension does not include any back-end code for transporting, parsing, or loading these events.</translate> <translate><!--T:29--> A separate service, <tvar name=1>[[wikitech:Event Platform/EventGate|EventGate]]</tvar>, implements this functionality and deals with inserting events into Kafka.</translate> <translate><!--T:30--> Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines.</translate> <translate><!--T:31--> The details of these components are specific to Wikimedia Foundation's configuration.</translate> <translate> == EventLogging at Wikimedia == <!--T:32--> <!--T:33--> The Wikimedia Foundation uses the EventLogging extension as part of a [[<tvar name=1>wikitech:Analytics/Systems/EventLogging</tvar>|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[<tvar name=2>m:Special:MyLanguage/Privacy policy</tvar>|privacy policy]] and [[<tvar name=3>m:Special:MyLanguage/Data retention guidelines</tvar>|data retention guidelines]]. </translate> <translate><!--T:34--> This page is about general use of the EventLogging extension.</translate> <translate><!--T:35--> The Wikimedia Foundation uses EventLogging with WMF specific backend components and [<tvar name=url>https://schema.wikimedia.org/#!/</tvar> schema repositories].</translate> <translate><!--T:36--> For Wikimedia specific and maintained documentation, see <tvar name=1>[[wikitech:Analytics/Systems/EventLogging]]</tvar> and <tvar name=2>[[wikitech:Event Platform]]</tvar>.</translate> ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <translate> === Configuring the schema location === <!--T:58--> <!--T:59--> By default, the extension will look for schemas on [[<tvar name=1>m:Special:MyLanguage/Meta-Wiki</tvar>|Meta-Wiki]].</translate> <translate><!--T:60--> The relevant default settings are:</translate> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <translate><!--T:61--> To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</translate> <translate><!--T:62--> E.g. to use the <tvar name=1><code>Schema</code></tvar> namespace of the local wiki, set</translate> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <translate><!--T:63--> (and ensure the user account that will create the schemas is [[<tvar name=1>Special:MyLanguage/Manual:Autoconfirmed users</tvar>|autoconfirmed]]).</translate> <translate> == Logging events using EventLogging == <!--T:37--> </translate> * {{ll|Extension:EventLogging/Guide}} - <translate><!--T:38--> to developing and deploying EventLogging schemas, and more</translate> * {{ll|Extension:EventLogging/Programming}} - <translate><!--T:39--> tips and suggestions for developers writing code to log events</translate> <translate> == Developing the EventLogging extension == <!--T:40--> === Developer setup === <!--T:41--> <!--T:42--> As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. ==== Using Docker ==== <!--T:43--> </translate> ''<translate><!--T:44--> See <tvar name=1>{{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}</tvar></translate>'' <translate> ==== Using <tvar name=1>mediawiki-vagrant</tvar> ==== <!--T:45--> </translate> <translate><!--T:46--> If you develop using mediawiki-vagrant, everything you need is encapsulated in the <tvar name=1><code>eventlogging</code></tvar> role.</translate> <translate><!--T:47--> To enable it, run:</translate> <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> <translate> ==== For JavaScript development ==== <!--T:48--> </translate> <translate><!--T:49--> If working on the JavaScript client, you'll need to install dependencies with <tvar name=1><code>npm install</code></tvar> from the folder you're developing in.</translate> <translate><!--T:50--> Then you can use <tvar name=1><code>npm test</code></tvar> to run ESLint for example.</translate> <translate><!--T:51--> The "How to run tests" section below points out how to see JavaScript test results.</translate> <translate>When adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered.</translate> <translate> ==== How to run tests ==== <!--T:52--> <!--T:53--> There are PHP tests, Python tests, and JavaScript tests. </translate> <translate><!--T:54--> To run JavaScript tests, visit <tvar name=1>Special:JavaScriptTest/qunit</tvar> on your development wiki.</translate> <translate><!--T:55--> (See <tvar name=1>{{ll|Manual:JavaScript unit testing}}</tvar>.)</translate> <translate><!--T:56--> To run PHP tests, we use PHPUnit.</translate> <translate><!--T:57--> Make sure it is installed, then:</translate> <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] e6ygh7vhq0txmmrcwoh66yi1lqcirm6 5387141 5387116 2022-07-28T21:07:29Z Shirayuki 472859 make untranslatable wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = <translate><!--T:21--> Provides a framework for logging analytics events</translate> |version = <translate><!--T:22--> continuous updates</translate> |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} <translate> <!--T:23--> The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. == Features == <!--T:24--> </translate> * <translate><!--T:25--> EventLogging supports client-side logging from JavaScript and server-side logging from PHP.</translate> * <translate><!--T:26--> Logging behavior can be dynamically configured using <tvar name=1>{{ll|Extension:EventStreamConfig}}</tvar>.</translate> * <translate><!--T:27--> The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository.</translate> * <translate><!--T:28--> The extension does not include any back-end code for transporting, parsing, or loading these events.</translate> <translate><!--T:29--> A separate service, <tvar name=1>[[wikitech:Event Platform/EventGate|EventGate]]</tvar>, implements this functionality and deals with inserting events into Kafka.</translate> <translate><!--T:30--> Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines.</translate> <translate><!--T:31--> The details of these components are specific to Wikimedia Foundation's configuration.</translate> <translate> == EventLogging at Wikimedia == <!--T:32--> <!--T:33--> The Wikimedia Foundation uses the EventLogging extension as part of a [[<tvar name=1>wikitech:Analytics/Systems/EventLogging</tvar>|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[<tvar name=2>m:Special:MyLanguage/Privacy policy</tvar>|privacy policy]] and [[<tvar name=3>m:Special:MyLanguage/Data retention guidelines</tvar>|data retention guidelines]]. </translate> <translate><!--T:34--> This page is about general use of the EventLogging extension.</translate> <translate><!--T:35--> The Wikimedia Foundation uses EventLogging with WMF specific backend components and [<tvar name=url>https://schema.wikimedia.org/#!/</tvar> schema repositories].</translate> <translate><!--T:36--> For Wikimedia specific and maintained documentation, see <tvar name=1>[[wikitech:Analytics/Systems/EventLogging]]</tvar> and <tvar name=2>[[wikitech:Event Platform]]</tvar>.</translate> ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <translate> === Configuring the schema location === <!--T:58--> <!--T:59--> By default, the extension will look for schemas on [[<tvar name=1>m:Special:MyLanguage/Meta-Wiki</tvar>|Meta-Wiki]].</translate> <translate><!--T:60--> The relevant default settings are:</translate> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <translate><!--T:61--> To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</translate> <translate><!--T:62--> E.g. to use the <tvar name=1><code>Schema</code></tvar> namespace of the local wiki, set</translate> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <translate><!--T:63--> (and ensure the user account that will create the schemas is [[<tvar name=1>Special:MyLanguage/Manual:Autoconfirmed users</tvar>|autoconfirmed]]).</translate> <translate> == Logging events using EventLogging == <!--T:37--> </translate> * {{ll|Extension:EventLogging/Guide}} - <translate><!--T:38--> to developing and deploying EventLogging schemas, and more</translate> * {{ll|Extension:EventLogging/Programming}} - <translate><!--T:39--> tips and suggestions for developers writing code to log events</translate> <translate> == Developing the EventLogging extension == <!--T:40--> === Developer setup === <!--T:41--> <!--T:42--> As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. ==== Using Docker ==== <!--T:43--> </translate> ''<translate><!--T:44--> See <tvar name=1>{{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}</tvar></translate>'' <translate> ==== Using <tvar name=1>mediawiki-vagrant</tvar> ==== <!--T:45--> </translate> <translate><!--T:46--> If you develop using mediawiki-vagrant, everything you need is encapsulated in the <tvar name=1><code>eventlogging</code></tvar> role.</translate> <translate><!--T:47--> To enable it, run:</translate> <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> <translate> ==== For JavaScript development ==== <!--T:48--> </translate> <translate><!--T:49--> If working on the JavaScript client, you'll need to install dependencies with <tvar name=1><code>npm install</code></tvar> from the folder you're developing in.</translate> <translate><!--T:50--> Then you can use <tvar name=1><code>npm test</code></tvar> to run ESLint for example.</translate> <translate><!--T:51--> The "How to run tests" section below points out how to see JavaScript test results.</translate> <translate> When adding the parameter <tvar name=1><code>trackdebug=true</code></tvar> to the URL, the console in the browser's devtools will show the event logging being triggered. ==== How to run tests ==== <!--T:52--> <!--T:53--> There are PHP tests, Python tests, and JavaScript tests. </translate> <translate><!--T:54--> To run JavaScript tests, visit <tvar name=1>Special:JavaScriptTest/qunit</tvar> on your development wiki.</translate> <translate><!--T:55--> (See <tvar name=1>{{ll|Manual:JavaScript unit testing}}</tvar>.)</translate> <translate><!--T:56--> To run PHP tests, we use PHPUnit.</translate> <translate><!--T:57--> Make sure it is installed, then:</translate> <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] 2e69kj7w1u75wpp71f2skbq2qtazyz4 5387142 5387141 2022-07-28T21:07:37Z Shirayuki 472859 Marked this version for translation wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = <translate><!--T:21--> Provides a framework for logging analytics events</translate> |version = <translate><!--T:22--> continuous updates</translate> |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} <translate> <!--T:23--> The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. == Features == <!--T:24--> </translate> * <translate><!--T:25--> EventLogging supports client-side logging from JavaScript and server-side logging from PHP.</translate> * <translate><!--T:26--> Logging behavior can be dynamically configured using <tvar name=1>{{ll|Extension:EventStreamConfig}}</tvar>.</translate> * <translate><!--T:27--> The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository.</translate> * <translate><!--T:28--> The extension does not include any back-end code for transporting, parsing, or loading these events.</translate> <translate><!--T:29--> A separate service, <tvar name=1>[[wikitech:Event Platform/EventGate|EventGate]]</tvar>, implements this functionality and deals with inserting events into Kafka.</translate> <translate><!--T:30--> Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines.</translate> <translate><!--T:31--> The details of these components are specific to Wikimedia Foundation's configuration.</translate> <translate> == EventLogging at Wikimedia == <!--T:32--> <!--T:33--> The Wikimedia Foundation uses the EventLogging extension as part of a [[<tvar name=1>wikitech:Analytics/Systems/EventLogging</tvar>|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[<tvar name=2>m:Special:MyLanguage/Privacy policy</tvar>|privacy policy]] and [[<tvar name=3>m:Special:MyLanguage/Data retention guidelines</tvar>|data retention guidelines]]. </translate> <translate><!--T:34--> This page is about general use of the EventLogging extension.</translate> <translate><!--T:35--> The Wikimedia Foundation uses EventLogging with WMF specific backend components and [<tvar name=url>https://schema.wikimedia.org/#!/</tvar> schema repositories].</translate> <translate><!--T:36--> For Wikimedia specific and maintained documentation, see <tvar name=1>[[wikitech:Analytics/Systems/EventLogging]]</tvar> and <tvar name=2>[[wikitech:Event Platform]]</tvar>.</translate> ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <translate> === Configuring the schema location === <!--T:58--> <!--T:59--> By default, the extension will look for schemas on [[<tvar name=1>m:Special:MyLanguage/Meta-Wiki</tvar>|Meta-Wiki]].</translate> <translate><!--T:60--> The relevant default settings are:</translate> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <translate><!--T:61--> To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</translate> <translate><!--T:62--> E.g. to use the <tvar name=1><code>Schema</code></tvar> namespace of the local wiki, set</translate> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <translate><!--T:63--> (and ensure the user account that will create the schemas is [[<tvar name=1>Special:MyLanguage/Manual:Autoconfirmed users</tvar>|autoconfirmed]]).</translate> <translate> == Logging events using EventLogging == <!--T:37--> </translate> * {{ll|Extension:EventLogging/Guide}} - <translate><!--T:38--> to developing and deploying EventLogging schemas, and more</translate> * {{ll|Extension:EventLogging/Programming}} - <translate><!--T:39--> tips and suggestions for developers writing code to log events</translate> <translate> == Developing the EventLogging extension == <!--T:40--> === Developer setup === <!--T:41--> <!--T:42--> As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. ==== Using Docker ==== <!--T:43--> </translate> ''<translate><!--T:44--> See <tvar name=1>{{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}</tvar></translate>'' <translate> ==== Using <tvar name=1>mediawiki-vagrant</tvar> ==== <!--T:45--> </translate> <translate><!--T:46--> If you develop using mediawiki-vagrant, everything you need is encapsulated in the <tvar name=1><code>eventlogging</code></tvar> role.</translate> <translate><!--T:47--> To enable it, run:</translate> <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> <translate> ==== For JavaScript development ==== <!--T:48--> </translate> <translate><!--T:49--> If working on the JavaScript client, you'll need to install dependencies with <tvar name=1><code>npm install</code></tvar> from the folder you're developing in.</translate> <translate><!--T:50--> Then you can use <tvar name=1><code>npm test</code></tvar> to run ESLint for example.</translate> <translate><!--T:51--> The "How to run tests" section below points out how to see JavaScript test results.</translate> <translate> <!--T:64--> When adding the parameter <tvar name=1><code>trackdebug=true</code></tvar> to the URL, the console in the browser's devtools will show the event logging being triggered. ==== How to run tests ==== <!--T:52--> <!--T:53--> There are PHP tests, Python tests, and JavaScript tests. </translate> <translate><!--T:54--> To run JavaScript tests, visit <tvar name=1>Special:JavaScriptTest/qunit</tvar> on your development wiki.</translate> <translate><!--T:55--> (See <tvar name=1>{{ll|Manual:JavaScript unit testing}}</tvar>.)</translate> <translate><!--T:56--> To run PHP tests, we use PHPUnit.</translate> <translate><!--T:57--> Make sure it is installed, then:</translate> <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] hjbe8dgni7bhgfz5oobt2jt48bw3wks Manual:Special pages/de 100 97362 5387047 5370131 2022-07-28T20:01:36Z ThisCarthing 17456337 Created page with "* Lokalisierungsdatei" wikitext text/x-wiki <languages/> {{ExtensionTypes}} [[File:MediaWiki-extensions-icon.svg|125px|alt=MediaWiki extensions|{{dir|{{pagelang}}|left|right}}]] '''Spezialseiten''' sind Seiten, die von der Software auf Anforderung erstellt werden, um eine bestimmte Funktion auszuführen. Beispielsweise könnte eine spezielle Seite alle Seiten anzeigen, die einen oder mehrere Links zu einer externen Webpräsenz haben, oder ein Formular erstellen, das von Benutzern eingereichte Rückmeldungen enthält. Spezialseiten befinden sich in einem eigenen [[Special:MyLanguage/Manual:Namespace|Namensraum]] ('''''Spezial:''''') und können nicht wie andere Seiten direkt bearbeitet werden. {{ll|Developers}} können auch neue Spezialseiten erstellen. Diese Seiten können für Benutzer zugänglich sein und werden im Allgemeinen in der Liste aller Sonderseiten bei [[Special:SpecialPages]] angezeigt. Einige Spezialseiten sind nur für Benutzer mit bestimmten Berechtigungen und Zugriffsrechten zugänglich. Andere Spezialseiten erscheinen überhaupt nicht auf der Spezialseiten-Liste und werden nur intern vom Wiki verwendet. == Allgemeine Informationen == <span lang="en" dir="ltr" class="mw-content-ltr">All built-in special pages that come with MediaWiki are called <code>SpecialSomename.php</code> and are located in the <code>includes/specials</code> directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Core special pages must be registered in the core list located in <code>includes/specialpage/SpecialPageFactory.php</code> in order to be loaded by MediaWiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Special pages created by third party developers are generally stored in the <code>extensions</code> directory in their own file or as part of a larger extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All special pages inherit from a class called {{class doclink|SpecialPage}} which is defined in <code>includes/specialpage/SpecialPage.php</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">When a new special page is created, the user rights needed to access the page can be defined.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These rights specify, among other things, whether the page will show up on [[Special:SpecialPages]] and whether the page is includable in other pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Special pages also have unique names that can be customized on a wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The general form is "Special:Pagename" where both "Special" and "Pagename" are customizable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Special pseudo {{ll|Manual:Namespaces|namespace}} can be translated in other languages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This translated namespace can be produced with the wikitext <nowiki>{{ns:special}}</nowiki>, on this wiki giving "{{ns:special}}".</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '''name''' of the special page can also be redefined in a system message, for the site language, with the generic name of the special page as the ID.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A special page may or may not allow input.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[Special:Export]] allows a user to define a specific page to export by calling [[Special:Export/Sun]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the special page allows complex input, additional parameters will be sent to the [[W:Query string|query string]] component of the URL for processing, e.g. https://www.mediawiki.org/w/index.php?title=Special:Recentchanges&days=3&limit=250.</span> {{Note|1=<nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * There are various ways to make [[Special:MyLanguage/Help:Special pages|special pages]], but the one below is used by the bulk of official {{ll|Manual:Extensions|extensions}}, and adherence to this style is recommended. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Also, be sure to include a credits block in the new special page for 'specialpage'. See <code>{{ll|Manual:$wgExtensionCredits|$wgExtensionCredits}}</code> for more details.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * After making a new special page, be sure to add it to {{ll|Category:Special page extensions}} so other people can find it. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * This method is only valid for MediaWiki running on PHP5 and above. If you're using an earlier version of MediaWiki on a more-recent version of PHP, {{ll|Manual:Upgrading|upgrade MediaWiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Special pages cannot be included within frames unless you use <code>$wgOut->allowClickjacking();</code> </div> }} == Grundlegende Vorlage für Spezialseiten == {{ombox|text=<span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki 1.25 introduced a [[Manual:Extension registration|new way]] to load an extension. For older unsupported versions of MediaWiki, see an [https://www.mediawiki.org/w/index.php?title=Manual:Special_pages&oldid=2331671 older revision].</span>}} Die meisten Spezialseiten-Erweiterungen erfordern drei Dateien: <div lang="en" dir="ltr" class="mw-content-ltr"> * Small setup file, which loads every time MediaWiki starts. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * File with the bulk of the code. </div> * Lokalisierungsdatei Die MediaWiki-Kodierungskonventionen definieren diese drei Dateien wie folgt: *<code>MyExtension/extension.json</code> - Die Konfigurationsdatei. *<code>MyExtension/includes/Special.php</code> - <span lang="en" dir="ltr" class="mw-content-ltr">The special page code.</span> *<code>i18n/*.json</code> - Die {{ll|localisation file}}. <div lang="en" dir="ltr" class="mw-content-ltr"> Place all of the files in a new directory inside your MediaWiki <code>extensions/</code> directory. </div> <span lang="en" dir="ltr" class="mw-content-ltr">You should name the special page file after the extension. For example, {{ll|Extension:Gadgets}} contains the file <code>SpecialGadgets.php</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your extension uses more than one special page, you'll need more names.</span> Im untenstehenden Beispiel lautet der Name der Spezialseite '''MyExtension'''. <div lang="en" dir="ltr" class="mw-content-ltr"> After creating the files listed below, adding the following line to '''LocalSettings.php''' enables the extension: </div> <syntaxhighlight lang=php> wfLoadExtension( 'MyExtension' ); </syntaxhighlight> {{anchor|The Setup File}} ===Die Konfigurationsdatei=== Beispiel für eine Konfigurationsdatei <code>MeineErweiterung/extension.json</code>: {{#tag:syntaxhighlight| { "name": "MyExtension", "version": "0.0.0", "author": [ "Your Name" ], "url": "https://www.mediawiki.org/wiki/Extension:MyExtension", "descriptionmsg": "myextension-desc", "license-name": "MIT", "type": "other", "AutoloadNamespaces": { "MediaWiki\\Extension\\MyExtension\\": "src/" }, "SpecialPages": { "MyExtension": "MediaWiki\\Extension\\MyExtension\\Special" }, "MessagesDirs": { "MyExtension": [ "i18n" ] }, "manifest_version": 2, "requires": { "MediaWiki": ">= {{MW legacy branch number}}.0", "platform": { "php": ">= 5.6" }, "extensions": { "dependendExtension": "*" } } } |lang=json}} <div lang="en" dir="ltr" class="mw-content-ltr"> This file registers several important and mandatory things: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The location of the MediaWiki\Extension\MyExtension\Special class; </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The location of the localisation files; </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The new special page and its class name. </div> {{anchor|The Special Page File}} ===Die Datei der Spezialseite=== <span lang="en" dir="ltr" class="mw-content-ltr">The body file (<code>MyExtension/src/Special.php</code>) should contain a subclass of <code>SpecialPage</code> or one of its subclasses.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This file loads automatically when someone requests the special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The example below implements the subclass SpecialMyExtension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need the <code>__construct()</code> constructor because its first parameter names your special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr"><code>execute()</code> is the main function called when a special page is accessed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This function overrides the function {{phpi|SpecialPage::execute()}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It passes the single parameter <code>$par</code>, the subpage component of the current title.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if someone follows a link to [[Special:MyExtension/blah]], <code>$par</code> contains "blah".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You should run Wikitext and HTML output through <code>$wgOut</code>. Do not use 'print' or 'echo' directly when working within the wiki's user interface. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> However, if you use your special page as an access point to custom XML or binary output, see {{ll|Taking over output in your special page}}. </div> <syntaxhighlight lang="php"> <?php namespace MediaWiki\Extension\MyExtension; class SpecialMyExtension extends \SpecialPage { function __construct() { parent::__construct( 'MyExtension' ); } function execute( $par ) { $request = $this->getRequest(); $output = $this->getOutput(); $this->setHeaders(); # Get request data from, e.g. $param = $request->getText( 'param' ); # Do stuff # ... $wikitext = 'Hello world!'; $output->addWikiTextAsInterface( $wikitext ); } } </syntaxhighlight> {{anchor|The localisation file}} ===Die Lokalisierungsdatei=== {{anchor|The Messages/Internationalization File}} :''<span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Help:System message#Adding new messages}} for how to get them translated.</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> All special pages specify a title, like <code>'My Extension'</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The title is used in the {{tag|title|open}} and {{tag|h1|open}} elements of the extension's page and on [[Special:SpecialPages]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * It can be anything, but should describe the special page and extension. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * It's specified through a message. The structure of the message is a key-value pair. The key, <code>'myextension'</code>, ''must'' be all lowercase. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An example of a localisation file in <code>MyExtension/i18n/en.json</code>: </div> <syntaxhighlight lang="javascript"> { "@metadata": { "authors": [ "<your username>" ] }, "myextension": "My Extension", "myextension-desc": "Adds the MyExtension functionality.", "myextension-summary": "On this special page, do this simple thing and earn wonders.", "group-myextensionrole": "Role of myextension", "group-myextensionrole-member": "Member of role of myextension", "grouppage-myextensionrole": "{{ns:project}}:Role of myextension", "action-myextension": "XYZ doing.", "right-myextension": "to do xyz" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">In <code>i18n/qqq.json</code>, the [[Special:MyLanguage/Help:System message#Message documentation|message documentation]]:</span> <syntaxhighlight lang="javascript"> { "@metadata": { "authors": [ "<your username>" ] }, "myextension": "The name of the extension's entry in Special:SpecialPages", "myextension-desc": "{{desc}}", "myextension-summary": "Description appearing on top of Special:MyExtension.", "action-myextension": "{{doc-action|myextension}}", "right-myextension": "{{doc-right|myextension}}" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Note that IDs should not start with an uppercase letter, and that a space in the ID should be written in the code as an underscore.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The -summary message is optional.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's created automatically by the parent class and shown on top of the special page, usually for a concise description of what the user can do on it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you don't define its content, it will only be used when wiki administrators customize it on the wiki.</span> {{anchor|The Aliases File}} === Die "aliases"-Datei === <span lang="en" dir="ltr" class="mw-content-ltr">You can also internationalize the name of the special page by creating aliases for it. The example below uses the file "MyExtension.i18n.alias.php".</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this example, the special page <code>MyExtension</code> registers an ''alias'' so the page becomes accessible at <code>.../Special:My Extension</code> and <code>.../Spezial:Meine_Erweiterung</code> in German.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Add your alias file to <code>extension.json</code>:</span> <syntaxhighlight lang="javascript"> ... "ExtensionMessagesFiles": { "MyExtensionAlias": "MyExtension.i18n.alias.php" }, ... </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Add special page aliases to <code>MyExtension.i18n.alias.php</code>:</span> <syntaxhighlight lang="php"> <?php /** * Aliases for myextension * * @file * @ingroup Extensions */ $specialPageAliases = []; /** English * @author <your username> */ $specialPageAliases['en'] = [ 'MyExtension' => [ 'MyExtension', 'My Extension' ], ]; /** Deutsch * @author <your username> */ $specialPageAliases['de'] = [ 'MyExtension' => [ 'MeineErweiterung', 'Meine Erweiterung' ], ]; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Again, you should write a space in the ID and an underscore in the code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For the page header and linking, the usual rules for page names apply. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If <code>{{ll|Manual:$wgCapitalLinks|$wgCapitalLinks}}</code> is true, a lowercase letter is converted to uppercase, and an underscore is displayed as a space. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, instead of the above, we could use <code>'my_extension' => 'My extension'</code>, assuming we consistently identified the extension as <code>my_extension</code> elsewhere. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that in the associative array for the English language, the string identifying our SpecialPage (<code>MyExtension</code> in the example) is ''also'' a valid title. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Also note, the first element of {{phpi|$specialPageAliases['en']['MyExtension']}} ''must'' be the same as the key (<code>'MyExtension'</code>)! Otherwise [[Special:Specialpages]] will not list the page. </div> {{anchor|Special page group}} ====Spezialseiten-Gruppe==== <div lang="en" dir="ltr" class="mw-content-ltr"> You can set which group your special page appears under on [[Special:SpecialPages]] by overriding <code>SpecialPage::getGroupName()</code> in your subclass. </div> <syntaxhighlight lang="php"> /** * Override the parent to set where the special page appears on Special:SpecialPages * 'other' is the default. If that's what you want, you do not need to override. * Specify 'media' to use the <code>specialpages-group-media</code> system interface message, which translates to 'Media reports and uploads' in English; * * @return string */ function getGroupName() { return 'media'; } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Some common values are 'login', 'maintenance', 'media', 'other', 'pagetools', 'redirects', 'users'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can see the accepted values at <nowiki>Special:AllMessages</nowiki> (search for '''specialpages-group''') or browse the wiki using the pseudo language 'qqx' by going to <nowiki>Special:SpecialPages?uselang=qqx</nowiki>) and looking at the headings.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Specify the word 'media' to use the interface message 'specialpages-group-media'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your special page doesn't fit into any of the preconfigured headings, you can add a new heading by adding it to your localisation file, see [[#The localisation file|The localisation file]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The standard page groups that come with MediaWiki are listed in the localisation file. For example, the English messages are in <code>languages/i18n/en.json</code> and begin with <code>specialpages-group-</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to categorize your special page under <code>users</code>, then the message is <code>specialpages-group-users</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value for this key is the text that appears as the name of that category, for example, <code>Users and rights</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your special page does not seem to fit under any of the existing categories, you can always make a new one.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In your extension's localisation file simply insert a new key for the <code>messages</code> array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this example, we define the <code>gamification</code> group:</span> <syntaxhighlight lang="json"> { "myextension": "My Extension", "myextension-desc": "Adds the MyExtension functionality.", "myextension-summary": "On this special page, do this simple thing and earn wonders", "specialpages-group-gamification": "Gamification" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Now, assuming you set the return value for the method <code>SpecialPage::getGroupName()</code> as <code>gamification</code> in your class definition, reload [[Special:SpecialPages]] to see your new category.</span> ==Andere wichtige Dateien== ===SpecialPage.php=== {{anchor|Constructor}} ====Konstruktor==== <span lang="en" dir="ltr" class="mw-content-ltr">You can [[w:Method overloading|overload]] the constructor to initialize your own data, but the main reason you would want to do it is to change the behavior of the SpecialPage class itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">When you call the base class constructor from your child class, the following parameters are available:</span> <syntaxhighlight lang="php"> function __construct( $name = '', $restriction = '', $listed = true ); </syntaxhighlight> * ''string'' <code>$name</code> <span lang="en" dir="ltr" class="mw-content-ltr">Name of the special page, as seen in links and URLs</span> * ''string'' <code>$restriction</code> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Manual:User rights|User right]] required, e.g. "block" or "delete"; also see [[Special:MyLanguage/Manual:Special_pages#Restricting_page_access|Restricting page access]]</span> * ''boolean'' <code>$listed</code> <span lang="en" dir="ltr" class="mw-content-ltr">Whether the page is listed in Special:Specialpages</span> ====<code>SpecialPage->setHeaders()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This initialises the OutputPage object <code>$wgOut</code> with the name and description of your special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It should always be called from your execute() method.</span> ====<code>SpecialPage->getOutput()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This method returns an OutputPage object which can be accessed as described below.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As in the example code, use</span> <syntaxhighlight lang="php"> $output = $this->getOutput(); $output->addWikiTextAsInterface( 'Hello, World' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> instead of the deprecated <code>$wgOut</code> global variable </div> ====<code>SpecialPage->getRequest()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This method returns a WebRequest object which can be accessed as described below.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As in the example code, use</span> <syntaxhighlight lang="php"> $request = $this->getRequest(); $myparam = $request->getText( 'myparam' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">instead of the deprecated {{$wg|Request}} global variable</span> ====<code>SpecialPage->including()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">Some special pages can be included from within another page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you add <nowiki>{{Special:RecentChanges}}</nowiki> to the wikitext of a page, it will insert a listing of recent changes within the existing content of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Including a special page from another web page is only possible if you declared the page to be includable in the constructor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can do this by adding the following in the <code>__construct()</code> method after the parent class initialization:</span> <syntaxhighlight lang="php"> $this->mIncludable = true; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You can also define your special page class as extending the IncludableSpecialPage class.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The SpecialPage->including() function returns a boolean value telling you what context the special page is being called from: false if it is a separate web page, and true if it is being included from within another web page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Usually you will want to strip down the presentation somewhat if the page is being included.</span> {{anchor|execute}} ====<code>SpecialPage->execute()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This is the function which your child class should overload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It passes a single parameter, usually referred to cryptically as <code>$par</code> (short for $parameter, as it is the parameter the users can feed to your special page).</span> <span lang="en" dir="ltr" class="mw-content-ltr">This parameter is the subpage component of the current title.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if someone follows a link to [[Special:MyExtension/blah]], <code>$par</code> will contain "blah".</span> =====Hilfe-Datei===== {{MW 1.25|and later}} <span lang="en" dir="ltr" class="mw-content-ltr">It's useful to add [[Special:MyLanguage/Project:PD help|help pages]] on MediaWiki.org, where they'll be [[Special:MyLanguage/Project:Language policy|translatable]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">To make sure users find your help page, it's advisable and very simple for your special page to link the help page in question:</span> <syntaxhighlight lang="php"> $this->addHelpLink( 'Help:Extension:MyExtension' ); </syntaxhighlight> ===OutputPage.php=== <span lang="en" dir="ltr" class="mw-content-ltr">OutputPage.php contains the class definition for objects of type <code>OutputPage</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can get an object of this class from your SpecialPage using</span> <syntaxhighlight lang="php"> $output = $this->getOutput(); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">The variablename $output is, of course, arbitrary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Whatever you call it, this is the variable you will use the most, because it is the way to send output to the browser (no, you don't use <code>echo</code> or <code>print</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to use it somewhere, declare the variable global:</span> <syntaxhighlight lang="php"> function randomFunction() { $output = $this->getOutput(); $output->addHTML( '<b>This is not a pipe...</b>' ); } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to, you can create multiple OutputPage objects in different methods in your SpecialPage extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They will add to the output in the order they are executed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can inspect the OutputPage class by viewing <code>{{ll|Manual:OutputPage.php|includes/OutputPage.php}}</code> (indeed, all of these can be inspected), but there are a few methods you should definitely know about.</span> ====<code>OutputPage->addHTML()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">Essentially the quick and dirty substitute for <code>echo</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It takes your input and adds it to the buffer: no questions asked.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In the below action, if <code>$action</code> contains user-data, it could easily have XSS, evil stuff, or the spawn of [[w:Satan|Satan]] injected in.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You're better off using escaping (such as with the php function htmlentities) or the XML builders class to build trusted output.</span> <syntaxhighlight lang="php"> $output->addHTML( '<form action="'.$action.'" method="post">' ); </syntaxhighlight> ====<code>OutputPage->addWikiText()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">For most output, you should be using this function.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's a bit of a black magic function: wikitext goes in, HTML comes out, and a whole lotta arcane code and demon summonings happen in between.</span> <syntaxhighlight lang="php"> $output->addWikiText("This is some ''lovely'' [[wikitext]] that will '''get''' parsed nicely."); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">What's worth noting is that the parser will view your chunks as cohesive wholes and paragraph accordingly. That is...</span> <syntaxhighlight lang="php"> $output->addWikiText( '* Item 1' ); $output->addWikiText( '* Item 2' ); $output->addWikiText( '* Item 3' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Will output three lists with one item each, which probably wasn't intended.</span> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">If your special page is intended to be included in other pages, you should probably not use <code>addWikiText()</code> (or any other function that calls the parser except for message related functions that parse ($this->msg()) which are OK to call on modern versions of MediaWiki).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Due to [http://www.ehartwell.com/TechNotes/MediaWikiExtensionParserDebug.htm a bug in MediaWiki] ([[phab:T18129]]), an included special page will mess up any inclusion before it on the same including page, showing strings like UNIQ10842e596cbb71da.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Note however, if you just want to insert a system message and have it treated like parsed wikitext, you can use code like {{phpi|$this->getOutput()->addHtml( $this->msg( 'key-of-message' )->parse() )}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will not have the issue with nested parser calls mentioned above.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> =====workaround #1===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Important: these work arounds are only needed if you are making a transcludable special page. Normal special pages do not need these. </div> <span lang="en" dir="ltr" class="mw-content-ltr">As a workaround, you can have your extensions convert Wikitext to HTML using a separate Parser object and then use <code>addHTML()</code>.</span> Beispiel: <syntaxhighlight lang="php"> $wgOut->addHTML( $this->sandboxParse( "Here's some '''formatted''' text." ) ); </syntaxhighlight> <syntaxhighlight lang="php"> # Assuming this is inside the same class as the rest of your special page code function sandboxParse( $wikiText ) { $myParser = new Parser(); $user = $this->getUser(); $title = self::getTitleFor('YourCanonicalSpecialPageName'); $myParserOptions = ParserOptions::newFromUser( $user ); $result = $myParser->parse( $wikiText, $title, $myParserOptions ); return $result->getText(); } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> =====workaround #2===== </div> <span lang="en" dir="ltr" class="mw-content-ltr">I tried the above, and found that the same problem now applied to any tags in the transcluded text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This won't be a problem for a lot of extensions, but the extension I was writing was intended to show wikitext from another page as part of its functionality, so this was a problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The process for parsing a page which transcludes a special page seems to be this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace <nowiki>{{Special:MyExtension}}</nowiki> with a [[Strip marker|UNIQ-QINU marker]] (because SpecialPage output is expected to be ready-to-output HTML)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace any tags with [[Strip marker|QINU markers]] as above</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Parse everything else from wikitext to HTML</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace all [[Strip marker|QINU markers]] with their respective stored values, in a single pass</span> <span lang="en" dir="ltr" class="mw-content-ltr">The process for parsing a page which transcludes a ''non''-special page, though, is apparently like this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace <nowiki>{{:Normal Article Name}}</nowiki> or <nowiki>{{Template Name}}</nowiki> with contents of transcluded page (because transcluded pages contain unparsed wikitext)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace any tags with [[Strip marker|QINU markers]] as above</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Parse everything else from wikitext to HTML</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace all [[Strip marker|QINU markers]] with their respective stored values, in a single pass</span> <span lang="en" dir="ltr" class="mw-content-ltr">The problem is apparently that in the earlier case, the parsing of the SpecialPage's wiki text is lacking the final QINU decoding step (why?), so all the [[Strip marker|QINU markers]] are left undecoded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(This may be a leftover from using the same syntax to invoke transclusion of a wikitext page, which is just pasted straight into the host page's wikitext contents and parsed, as is used to invoke transclusion of a SpecialPage, which must not be parsed at all. Wherever the code is that decides "wait, this is a special page -- replace it with a QINU", it should be doing the extra unstripGeneral before doing the QINU substitution.)</span> {{void|1= <span lang="en" dir="ltr" class="mw-content-ltr">Wherever the code is that decides "wait, this is a special page -- replace it with a QINU", it should be doing the extra unstripGeneral before doing the QINU substitution.)</span> }} <span lang="en" dir="ltr" class="mw-content-ltr">So I just did the following -- after this line:</span> <syntaxhighlight lang="php">$htOut = $wgParser->recursiveTagParse( $iText );</syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">...I added these lines (the second one is only because the function definition for the first one recommends it):</span> <syntaxhighlight lang="php"> $htOut = $wgParser->mStripState->unstripGeneral( $htOut ); $htOut = $wgParser->mStripState->unstripNoWiki( $htOut ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Since I have now documented this, of course, I will now find a tragic flaw with it and feel really stupid... but as long as it seems to be working, I had to note it here.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(It is also important to note the problem with work-around #1.)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, I have only tested this with MediaWiki 1.10.1.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The problem still exists under MW 1.14, but this solution may or may not work.</span> --[[User:Woozle|Woozle]] 18:26, 9 April 2009 (UTC) ====<code>OutputPage->showErrorPage()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">An error page is shown.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The arguments <code>$title</code> and <code>$msg</code> specify keys into $this->msg(), not text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An example:</span> <syntaxhighlight lang="php"> $output->showErrorPage( 'error', 'badarticleerror' ); </syntaxhighlight> *<span lang="en" dir="ltr" class="mw-content-ltr">'error' refers to the text ''"{{int|error}}"''.</span> *<span lang="en" dir="ltr" class="mw-content-ltr">'badarticleerror' refers to the text ''"{{int|badarticleerror}}"''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can also specify message objects or add parameters:</span> <syntaxhighlight lang="php"> $output->showErrorPage( 'error', 'badarticleerror', [ 'param1', 'param2' ] ); </syntaxhighlight> <syntaxhighlight lang="php"> $messageObject = new Message(...); ... $output->showErrorPage( 'error', $messageObject ); </syntaxhighlight> <syntaxhighlight lang="php"> $titleMessageObject = new Message(...); $messageObject = new Message(...); ... $output->showErrorPage( $titleMessageObject, $messageObject ); </syntaxhighlight> ===WebRequest.php=== <span lang="en" dir="ltr" class="mw-content-ltr">The {{manual|WebRequest.php|WebRequest}} class is used to obtain information from the GET and POST arrays.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Using this is recommended over directly accessing the superglobals.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The WebRequest object is accessible from extensions by using the {{ll|RequestContext}}.</span> ===Database.php=== <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki has a load of convenience functions and wrappers for interacting with the database, using the {{manual|Database.php|\Wikimedia\Rdbms\Database}} class.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It also has an interesting load balancing scheme in place.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's recommended you use these wrappers.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Check out <code>{{ll|Manual:Database.php|Database.php}}</code> for a complete listing of all the convenience functions, because these docs will only tell you about the non-obvious caveats.</span> Siehe {{ll|Manual:Database access}}. ===User.php=== <span lang="en" dir="ltr" class="mw-content-ltr">The {{manual|User.php|User}} class is used to represent users on the system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">SpecialPage->getUser() should be used to obtain a User object for the currently logged in user.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The use of the global <code>$wgUser</code> is deprecated</span> ===Title.php=== <span lang="en" dir="ltr" class="mw-content-ltr">Title represents the name of a page in the wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is useful because MediaWiki does all sorts of fun escaping and special case logic to page names, so instead of rolling your own convert title to URL function, you create a Title object with your page name, and then use <code>getLocalURL()</code> to get a URL to that page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To get a title object for your special page from outside of the special page class, you can use {{phpi|SpecialPage::getTitleFor( 'YourCanonicalSpecialPageName' )}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will give you a localised title in the wiki's language.</span> ==Benutzerspezifische Spezialseiten== <div lang="en" dir="ltr" class="mw-content-ltr"> There are various ways to provide your own special pages not bundled within MediaWiki: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">One method is to install an extension that generates a form to create or edit an article. A list of extensions currently available, can be found at {{ll|Category:Special page extensions}}.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">You can also write an extension which provides your own special page. Writing your own extension requires [[w:PHP|PHP]] coding skill and comfort with object oriented design and databases also is helpful. You will also need to know how to use code to create and edit MediaWiki articles. For more information, please see [[Special:MyLanguage/Manual:Forms#Articles_with_embedded_forms|this discussion]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">You can also display a custom page through JavaScript, in place of the default error message "Unknown special page" (or the "This page is intentionally left blank." message, if using a subpage of [[Special:BlankPage]]). In MediaWiki:Common.js, check for {{ll|Manual:Interface/JavaScript#mw.config|wgPageName}}, then hide the MediaWiki-generated content (just appendCSS <code>{visibility:hidden;}</code> ), and inject custom HTML (<code>innerHTML</code>) into the <code>document.getElementById('bodyContent')</code> or <code>document.getElementById('mw_contentholder')</code>. For an example, see [[:meta:User:Krinkle/Tools/Real-Time Recent Changes]].</span> ==Häufig gestellte Fragen== ===Das Setzen des Titels einer Erweiterung=== <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki does not set the title of the extension, which is the developer's job.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will look for the name of the extension when [[Special:Specialpages]] is called or the special page is loaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In the [[#execute|''function execute( $par )'']] section, use OutputPage methods to title the extension like: {{phpi|$this->getOutput()->setPageTitle("your title");}}</span> <span lang="en" dir="ltr" class="mw-content-ltr">The place where the extension can be found (as specified by what is passed into the SpecialPage constructor) is the key--'''except''' that it is not capitalized because of <code>getDescription()</code>, the internally used function that finds out the title (or, what they call description) of the special page, <code>strtolower</code> the name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">"ThisIsACoolSpecialPage"'s key would be "thisisacoolspecialpage."</span> <span lang="en" dir="ltr" class="mw-content-ltr">Theoretically, <code>getDescription</code> can be overloaded in order to avoid interacting with the message cache but, as the source code states: "Derived classes can override this, but usually it is easier to keep the default behavior.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Furthermore, this prevents the MediaWiki namespace from overloading the message, as below.</span> ===Lokalisierung des Namens der Erweiterung=== <span lang="en" dir="ltr" class="mw-content-ltr">So you've just installed a shiny new MediaWiki extension and realize: "Oh no, my wiki is in French, but the page is showing up as English!"</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most people wouldn't care, but it's actually a quite simple task to fix (as long as the developer used the method explained on this page).</span> <span lang="en" dir="ltr" class="mw-content-ltr">No noodling around in source code.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Let's say the name of the page is <code>DirtyPages</code> and the name comes out to "List of Dirty Pages" but you want it to be (and [[wikipedia:Pardon my French|excuse my poor French]]) "Liste de Pages Sales".</span> <span lang="en" dir="ltr" class="mw-content-ltr">Well, it's as simple as this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Navigate to [[MediaWiki:DirtyPages]], this page may not exist, but edit it anyway</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Insert "Liste de Pages Sales" and save</span> <span lang="en" dir="ltr" class="mw-content-ltr">And ''voilà'' (pardon the pun), the change is applied.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is also useful for customizing the title for your wiki within your language: for instance, the developer called it "List of Dirty Pages" but you don't like that name, so you rename it "List of Pages needing Cleanup".</span> <span lang="en" dir="ltr" class="mw-content-ltr">Check out [[Special:Allmessages]] to learn more.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, if your extension has a large block of text that does change, like a warning, don't directly output the text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, add it to the message cache and when the time comes to output the text in your code, do this:</span> <syntaxhighlight lang="php">$wgOut->addWikiText( $this->msg( 'dirtypageshelp' ) );</syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Then this message too can be customized at [[MediaWiki:Dirtypageshelp]]. </div> Siehe auch {{ll|Help:System message}}. ===Beschränkter Seitenzugang=== ====Die Spezialseite nicht auf [[Special:SpecialPages]] zeigen==== <span lang="en" dir="ltr" class="mw-content-ltr">Sometimes you may want to limit the visibility of your Special Page by removing it from [[Special:SpecialPages]] and making it visible to only those users with a particular right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can do this in the [[#Constructor|constructor]] by passing in a <code>$restriction</code> parameter; e.g., “editinterface”, a right only assigned to sysops by default; see the [[Special:MyLanguage/Manual:User_rights|User rights manual]] for other available user rights.</span> <syntaxhighlight lang="php"> function __construct() { parent::__construct( 'MyExtension', 'editinterface' ); // restrict to sysops } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Or you can create your own right in [[#The Setup File|the setup file]] and assign it to sysops, e.g.:</span> <syntaxhighlight lang="json"> "AvailableRights": [ "myextension-right" ], "GroupPermissions": { "sysop": { "myextension-right": true } } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">and then call the constructor with your right:</span> <syntaxhighlight lang="php"> function __construct() { parent::__construct( 'MyExtension', 'myextension-right' ); } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Prevent access to your Special Page==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Even if you restrict your page in the constructor, as mentioned above, it will still be viewable directly via the URL, e.g. at Special:MySpecialPage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In order to actually limit access to your SpecialPage you must call {{phpi|$this->checkPermissions()}} in the <code>execute</code> method.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you need more fine-grained control over permissions, you can override {{phpi|$this->checkPermissions()}}, and/or add whatever permissions-checking is required for your extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Disabling Special:UserLogin and Special:UserLogout pages=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">In LocalSettings.php you can use the {{ll|Manual:Hooks/SpecialPage_initList|SpecialPage_initList hook}} to ''unset'' unwanted built-in special pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[mailarchive:mediawiki-l/2009-June/031231.html|"making a few SpecialPages restricted"]] if you need ''conditional'' unsetting of special pages for example for certain user groups.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The general message "You have requested an invalid special page." is shown if users try to access such unset special pages.</span> <syntaxhighlight lang="php"> $wgHooks['SpecialPage_initList'][] = function ( &$list ) { unset( $list['Userlogout'] ); unset( $list['Userlogin'] ); return true; }; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">A different approach would be to use the DisabledSpecialPage callback.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This approach may be preferred if you're only disabling the special page "temporarily", because the default message in this case would say: "{{int|disabledspecialpage-disabled}}" instead of pretending the page does not exist at all.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This gives clear hint that the page maybe activated at a later time.</span> <syntaxhighlight lang="php"> $wgSpecialPages['Userlogout'] = DisabledSpecialPage::getCallback( 'Userlogout' ); $wgSpecialPages['Userlogin'] = DisabledSpecialPage::getCallback( 'Userlogin' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to add custom lengthy explanation of why you're disabling the special page, by giving a message key as the second argument of the callback.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To do so first create a system message "MediaWiki:Userlogout-disable-reason" and write all the explanation there.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The message will be parsed in a block format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then in LocalSettings.php add:</span> <syntaxhighlight lang="php"> $wgSpecialPages['Userlogout'] = DisabledSpecialPage::getCallback( 'Userlogout', 'Userlogout-disable-reason' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Adding logs=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">On MediaWiki, all actions by users on wiki are tracked for transparency and collaboration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Logging to Special:Log}} for how to do it.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Changing the groups on [[Special:Specialpages]]=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you're an extension developer, you have to implement the <code>getGroupName()</code> method as described in [[#Special page group|the Special page group section]] of this page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Since MediaWiki 1.21, the special page group can be overridden by editing a [[Special:MyLanguage/Help:System message|system message]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">This method is not intended to be used by extension developers, but by site admins.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The group name must be placed in the <code><nowiki>specialpages-specialpagegroup-<special page name></nowiki></code> message, where <code><nowiki><special page name></nowiki></code> is the canonical name (in english) of the special page in lowercase.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you want to set the group under which "Special:MyLittlePage" is displayed on [[Special:Specialpages]] to "MyLittleGroup", you just have to create "MediaWiki:Specialpages-specialpagegroup-mylittlepage" with content "MyLittleGroup".</span> <span lang="en" dir="ltr" class="mw-content-ltr">"Special:MyLittlePage" will then show up under the group "MyLittleGroup", which you can name under "MediaWiki:Specialpages-group-mylittlegroup".</span><br /> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to change the group of existing special pages, have a look on [https://www.mediawiki.org/w/index.php?title=Special:SpecialPages&uselang=qqx Special:SpecialPages&uselang=qqx] and use those names instead of "mylittlepage".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Unlisting the page from [[Special:Specialpages]]=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">To remove a special page from the [[Special:Specialpages]] altogether, pass a {{phpi|false}} as a third parameter to the SpecialPage parent constructor, as described in [[#Constructor|the SpecialPage Constructor section]] of this page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you need more complicated logic to determine whether the page should be listed or not, you can also override the <code>isListed()</code> function, but using the constructor parameter is simpler.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Getting a list of special pages and their aliases on a wiki=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Simply use the "siteinfo" API module to retrieve the information from the wiki like e.g. [https://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&siprop=specialpagealiases /api.php?action=query&meta=siteinfo&siprop=specialpagealiases].</span> ==Siehe auch== *[[Special:MyLanguage/HTMLForm|HTMLForm]] – <span lang="en" dir="ltr" class="mw-content-ltr">Tutorial on creating checkboxes, text areas, radio buttons, etc. in special pages</span> [[Category:MediaWiki development{{#translation:}}|{{PAGENAME}}]] [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:User interface{{#translation:}}|{{PAGENAME}}]] [[Category:Special Pages{{#translation:}}|{{PAGENAME}}]] 707onzfotbo582vrrlt8bth8palgb0i 5387049 5387047 2022-07-28T20:01:59Z ThisCarthing 17456337 Created page with "Ein Beispiel:" wikitext text/x-wiki <languages/> {{ExtensionTypes}} [[File:MediaWiki-extensions-icon.svg|125px|alt=MediaWiki extensions|{{dir|{{pagelang}}|left|right}}]] '''Spezialseiten''' sind Seiten, die von der Software auf Anforderung erstellt werden, um eine bestimmte Funktion auszuführen. Beispielsweise könnte eine spezielle Seite alle Seiten anzeigen, die einen oder mehrere Links zu einer externen Webpräsenz haben, oder ein Formular erstellen, das von Benutzern eingereichte Rückmeldungen enthält. Spezialseiten befinden sich in einem eigenen [[Special:MyLanguage/Manual:Namespace|Namensraum]] ('''''Spezial:''''') und können nicht wie andere Seiten direkt bearbeitet werden. {{ll|Developers}} können auch neue Spezialseiten erstellen. Diese Seiten können für Benutzer zugänglich sein und werden im Allgemeinen in der Liste aller Sonderseiten bei [[Special:SpecialPages]] angezeigt. Einige Spezialseiten sind nur für Benutzer mit bestimmten Berechtigungen und Zugriffsrechten zugänglich. Andere Spezialseiten erscheinen überhaupt nicht auf der Spezialseiten-Liste und werden nur intern vom Wiki verwendet. == Allgemeine Informationen == <span lang="en" dir="ltr" class="mw-content-ltr">All built-in special pages that come with MediaWiki are called <code>SpecialSomename.php</code> and are located in the <code>includes/specials</code> directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Core special pages must be registered in the core list located in <code>includes/specialpage/SpecialPageFactory.php</code> in order to be loaded by MediaWiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Special pages created by third party developers are generally stored in the <code>extensions</code> directory in their own file or as part of a larger extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All special pages inherit from a class called {{class doclink|SpecialPage}} which is defined in <code>includes/specialpage/SpecialPage.php</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">When a new special page is created, the user rights needed to access the page can be defined.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These rights specify, among other things, whether the page will show up on [[Special:SpecialPages]] and whether the page is includable in other pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Special pages also have unique names that can be customized on a wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The general form is "Special:Pagename" where both "Special" and "Pagename" are customizable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Special pseudo {{ll|Manual:Namespaces|namespace}} can be translated in other languages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This translated namespace can be produced with the wikitext <nowiki>{{ns:special}}</nowiki>, on this wiki giving "{{ns:special}}".</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '''name''' of the special page can also be redefined in a system message, for the site language, with the generic name of the special page as the ID.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A special page may or may not allow input.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[Special:Export]] allows a user to define a specific page to export by calling [[Special:Export/Sun]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the special page allows complex input, additional parameters will be sent to the [[W:Query string|query string]] component of the URL for processing, e.g. https://www.mediawiki.org/w/index.php?title=Special:Recentchanges&days=3&limit=250.</span> {{Note|1=<nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * There are various ways to make [[Special:MyLanguage/Help:Special pages|special pages]], but the one below is used by the bulk of official {{ll|Manual:Extensions|extensions}}, and adherence to this style is recommended. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Also, be sure to include a credits block in the new special page for 'specialpage'. See <code>{{ll|Manual:$wgExtensionCredits|$wgExtensionCredits}}</code> for more details.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * After making a new special page, be sure to add it to {{ll|Category:Special page extensions}} so other people can find it. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * This method is only valid for MediaWiki running on PHP5 and above. If you're using an earlier version of MediaWiki on a more-recent version of PHP, {{ll|Manual:Upgrading|upgrade MediaWiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Special pages cannot be included within frames unless you use <code>$wgOut->allowClickjacking();</code> </div> }} == Grundlegende Vorlage für Spezialseiten == {{ombox|text=<span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki 1.25 introduced a [[Manual:Extension registration|new way]] to load an extension. For older unsupported versions of MediaWiki, see an [https://www.mediawiki.org/w/index.php?title=Manual:Special_pages&oldid=2331671 older revision].</span>}} Die meisten Spezialseiten-Erweiterungen erfordern drei Dateien: <div lang="en" dir="ltr" class="mw-content-ltr"> * Small setup file, which loads every time MediaWiki starts. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * File with the bulk of the code. </div> * Lokalisierungsdatei Die MediaWiki-Kodierungskonventionen definieren diese drei Dateien wie folgt: *<code>MyExtension/extension.json</code> - Die Konfigurationsdatei. *<code>MyExtension/includes/Special.php</code> - <span lang="en" dir="ltr" class="mw-content-ltr">The special page code.</span> *<code>i18n/*.json</code> - Die {{ll|localisation file}}. <div lang="en" dir="ltr" class="mw-content-ltr"> Place all of the files in a new directory inside your MediaWiki <code>extensions/</code> directory. </div> <span lang="en" dir="ltr" class="mw-content-ltr">You should name the special page file after the extension. For example, {{ll|Extension:Gadgets}} contains the file <code>SpecialGadgets.php</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your extension uses more than one special page, you'll need more names.</span> Im untenstehenden Beispiel lautet der Name der Spezialseite '''MyExtension'''. <div lang="en" dir="ltr" class="mw-content-ltr"> After creating the files listed below, adding the following line to '''LocalSettings.php''' enables the extension: </div> <syntaxhighlight lang=php> wfLoadExtension( 'MyExtension' ); </syntaxhighlight> {{anchor|The Setup File}} ===Die Konfigurationsdatei=== Beispiel für eine Konfigurationsdatei <code>MeineErweiterung/extension.json</code>: {{#tag:syntaxhighlight| { "name": "MyExtension", "version": "0.0.0", "author": [ "Your Name" ], "url": "https://www.mediawiki.org/wiki/Extension:MyExtension", "descriptionmsg": "myextension-desc", "license-name": "MIT", "type": "other", "AutoloadNamespaces": { "MediaWiki\\Extension\\MyExtension\\": "src/" }, "SpecialPages": { "MyExtension": "MediaWiki\\Extension\\MyExtension\\Special" }, "MessagesDirs": { "MyExtension": [ "i18n" ] }, "manifest_version": 2, "requires": { "MediaWiki": ">= {{MW legacy branch number}}.0", "platform": { "php": ">= 5.6" }, "extensions": { "dependendExtension": "*" } } } |lang=json}} <div lang="en" dir="ltr" class="mw-content-ltr"> This file registers several important and mandatory things: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The location of the MediaWiki\Extension\MyExtension\Special class; </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The location of the localisation files; </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The new special page and its class name. </div> {{anchor|The Special Page File}} ===Die Datei der Spezialseite=== <span lang="en" dir="ltr" class="mw-content-ltr">The body file (<code>MyExtension/src/Special.php</code>) should contain a subclass of <code>SpecialPage</code> or one of its subclasses.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This file loads automatically when someone requests the special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The example below implements the subclass SpecialMyExtension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need the <code>__construct()</code> constructor because its first parameter names your special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr"><code>execute()</code> is the main function called when a special page is accessed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This function overrides the function {{phpi|SpecialPage::execute()}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It passes the single parameter <code>$par</code>, the subpage component of the current title.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if someone follows a link to [[Special:MyExtension/blah]], <code>$par</code> contains "blah".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You should run Wikitext and HTML output through <code>$wgOut</code>. Do not use 'print' or 'echo' directly when working within the wiki's user interface. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> However, if you use your special page as an access point to custom XML or binary output, see {{ll|Taking over output in your special page}}. </div> <syntaxhighlight lang="php"> <?php namespace MediaWiki\Extension\MyExtension; class SpecialMyExtension extends \SpecialPage { function __construct() { parent::__construct( 'MyExtension' ); } function execute( $par ) { $request = $this->getRequest(); $output = $this->getOutput(); $this->setHeaders(); # Get request data from, e.g. $param = $request->getText( 'param' ); # Do stuff # ... $wikitext = 'Hello world!'; $output->addWikiTextAsInterface( $wikitext ); } } </syntaxhighlight> {{anchor|The localisation file}} ===Die Lokalisierungsdatei=== {{anchor|The Messages/Internationalization File}} :''<span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Help:System message#Adding new messages}} for how to get them translated.</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> All special pages specify a title, like <code>'My Extension'</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The title is used in the {{tag|title|open}} and {{tag|h1|open}} elements of the extension's page and on [[Special:SpecialPages]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * It can be anything, but should describe the special page and extension. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * It's specified through a message. The structure of the message is a key-value pair. The key, <code>'myextension'</code>, ''must'' be all lowercase. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An example of a localisation file in <code>MyExtension/i18n/en.json</code>: </div> <syntaxhighlight lang="javascript"> { "@metadata": { "authors": [ "<your username>" ] }, "myextension": "My Extension", "myextension-desc": "Adds the MyExtension functionality.", "myextension-summary": "On this special page, do this simple thing and earn wonders.", "group-myextensionrole": "Role of myextension", "group-myextensionrole-member": "Member of role of myextension", "grouppage-myextensionrole": "{{ns:project}}:Role of myextension", "action-myextension": "XYZ doing.", "right-myextension": "to do xyz" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">In <code>i18n/qqq.json</code>, the [[Special:MyLanguage/Help:System message#Message documentation|message documentation]]:</span> <syntaxhighlight lang="javascript"> { "@metadata": { "authors": [ "<your username>" ] }, "myextension": "The name of the extension's entry in Special:SpecialPages", "myextension-desc": "{{desc}}", "myextension-summary": "Description appearing on top of Special:MyExtension.", "action-myextension": "{{doc-action|myextension}}", "right-myextension": "{{doc-right|myextension}}" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Note that IDs should not start with an uppercase letter, and that a space in the ID should be written in the code as an underscore.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The -summary message is optional.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's created automatically by the parent class and shown on top of the special page, usually for a concise description of what the user can do on it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you don't define its content, it will only be used when wiki administrators customize it on the wiki.</span> {{anchor|The Aliases File}} === Die "aliases"-Datei === <span lang="en" dir="ltr" class="mw-content-ltr">You can also internationalize the name of the special page by creating aliases for it. The example below uses the file "MyExtension.i18n.alias.php".</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this example, the special page <code>MyExtension</code> registers an ''alias'' so the page becomes accessible at <code>.../Special:My Extension</code> and <code>.../Spezial:Meine_Erweiterung</code> in German.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Add your alias file to <code>extension.json</code>:</span> <syntaxhighlight lang="javascript"> ... "ExtensionMessagesFiles": { "MyExtensionAlias": "MyExtension.i18n.alias.php" }, ... </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Add special page aliases to <code>MyExtension.i18n.alias.php</code>:</span> <syntaxhighlight lang="php"> <?php /** * Aliases for myextension * * @file * @ingroup Extensions */ $specialPageAliases = []; /** English * @author <your username> */ $specialPageAliases['en'] = [ 'MyExtension' => [ 'MyExtension', 'My Extension' ], ]; /** Deutsch * @author <your username> */ $specialPageAliases['de'] = [ 'MyExtension' => [ 'MeineErweiterung', 'Meine Erweiterung' ], ]; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Again, you should write a space in the ID and an underscore in the code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For the page header and linking, the usual rules for page names apply. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If <code>{{ll|Manual:$wgCapitalLinks|$wgCapitalLinks}}</code> is true, a lowercase letter is converted to uppercase, and an underscore is displayed as a space. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, instead of the above, we could use <code>'my_extension' => 'My extension'</code>, assuming we consistently identified the extension as <code>my_extension</code> elsewhere. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that in the associative array for the English language, the string identifying our SpecialPage (<code>MyExtension</code> in the example) is ''also'' a valid title. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Also note, the first element of {{phpi|$specialPageAliases['en']['MyExtension']}} ''must'' be the same as the key (<code>'MyExtension'</code>)! Otherwise [[Special:Specialpages]] will not list the page. </div> {{anchor|Special page group}} ====Spezialseiten-Gruppe==== <div lang="en" dir="ltr" class="mw-content-ltr"> You can set which group your special page appears under on [[Special:SpecialPages]] by overriding <code>SpecialPage::getGroupName()</code> in your subclass. </div> <syntaxhighlight lang="php"> /** * Override the parent to set where the special page appears on Special:SpecialPages * 'other' is the default. If that's what you want, you do not need to override. * Specify 'media' to use the <code>specialpages-group-media</code> system interface message, which translates to 'Media reports and uploads' in English; * * @return string */ function getGroupName() { return 'media'; } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Some common values are 'login', 'maintenance', 'media', 'other', 'pagetools', 'redirects', 'users'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can see the accepted values at <nowiki>Special:AllMessages</nowiki> (search for '''specialpages-group''') or browse the wiki using the pseudo language 'qqx' by going to <nowiki>Special:SpecialPages?uselang=qqx</nowiki>) and looking at the headings.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Specify the word 'media' to use the interface message 'specialpages-group-media'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your special page doesn't fit into any of the preconfigured headings, you can add a new heading by adding it to your localisation file, see [[#The localisation file|The localisation file]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The standard page groups that come with MediaWiki are listed in the localisation file. For example, the English messages are in <code>languages/i18n/en.json</code> and begin with <code>specialpages-group-</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to categorize your special page under <code>users</code>, then the message is <code>specialpages-group-users</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value for this key is the text that appears as the name of that category, for example, <code>Users and rights</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your special page does not seem to fit under any of the existing categories, you can always make a new one.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In your extension's localisation file simply insert a new key for the <code>messages</code> array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this example, we define the <code>gamification</code> group:</span> <syntaxhighlight lang="json"> { "myextension": "My Extension", "myextension-desc": "Adds the MyExtension functionality.", "myextension-summary": "On this special page, do this simple thing and earn wonders", "specialpages-group-gamification": "Gamification" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Now, assuming you set the return value for the method <code>SpecialPage::getGroupName()</code> as <code>gamification</code> in your class definition, reload [[Special:SpecialPages]] to see your new category.</span> ==Andere wichtige Dateien== ===SpecialPage.php=== {{anchor|Constructor}} ====Konstruktor==== <span lang="en" dir="ltr" class="mw-content-ltr">You can [[w:Method overloading|overload]] the constructor to initialize your own data, but the main reason you would want to do it is to change the behavior of the SpecialPage class itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">When you call the base class constructor from your child class, the following parameters are available:</span> <syntaxhighlight lang="php"> function __construct( $name = '', $restriction = '', $listed = true ); </syntaxhighlight> * ''string'' <code>$name</code> <span lang="en" dir="ltr" class="mw-content-ltr">Name of the special page, as seen in links and URLs</span> * ''string'' <code>$restriction</code> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Manual:User rights|User right]] required, e.g. "block" or "delete"; also see [[Special:MyLanguage/Manual:Special_pages#Restricting_page_access|Restricting page access]]</span> * ''boolean'' <code>$listed</code> <span lang="en" dir="ltr" class="mw-content-ltr">Whether the page is listed in Special:Specialpages</span> ====<code>SpecialPage->setHeaders()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This initialises the OutputPage object <code>$wgOut</code> with the name and description of your special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It should always be called from your execute() method.</span> ====<code>SpecialPage->getOutput()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This method returns an OutputPage object which can be accessed as described below.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As in the example code, use</span> <syntaxhighlight lang="php"> $output = $this->getOutput(); $output->addWikiTextAsInterface( 'Hello, World' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> instead of the deprecated <code>$wgOut</code> global variable </div> ====<code>SpecialPage->getRequest()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This method returns a WebRequest object which can be accessed as described below.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As in the example code, use</span> <syntaxhighlight lang="php"> $request = $this->getRequest(); $myparam = $request->getText( 'myparam' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">instead of the deprecated {{$wg|Request}} global variable</span> ====<code>SpecialPage->including()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">Some special pages can be included from within another page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you add <nowiki>{{Special:RecentChanges}}</nowiki> to the wikitext of a page, it will insert a listing of recent changes within the existing content of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Including a special page from another web page is only possible if you declared the page to be includable in the constructor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can do this by adding the following in the <code>__construct()</code> method after the parent class initialization:</span> <syntaxhighlight lang="php"> $this->mIncludable = true; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You can also define your special page class as extending the IncludableSpecialPage class.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The SpecialPage->including() function returns a boolean value telling you what context the special page is being called from: false if it is a separate web page, and true if it is being included from within another web page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Usually you will want to strip down the presentation somewhat if the page is being included.</span> {{anchor|execute}} ====<code>SpecialPage->execute()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This is the function which your child class should overload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It passes a single parameter, usually referred to cryptically as <code>$par</code> (short for $parameter, as it is the parameter the users can feed to your special page).</span> <span lang="en" dir="ltr" class="mw-content-ltr">This parameter is the subpage component of the current title.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if someone follows a link to [[Special:MyExtension/blah]], <code>$par</code> will contain "blah".</span> =====Hilfe-Datei===== {{MW 1.25|and later}} <span lang="en" dir="ltr" class="mw-content-ltr">It's useful to add [[Special:MyLanguage/Project:PD help|help pages]] on MediaWiki.org, where they'll be [[Special:MyLanguage/Project:Language policy|translatable]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">To make sure users find your help page, it's advisable and very simple for your special page to link the help page in question:</span> <syntaxhighlight lang="php"> $this->addHelpLink( 'Help:Extension:MyExtension' ); </syntaxhighlight> ===OutputPage.php=== <span lang="en" dir="ltr" class="mw-content-ltr">OutputPage.php contains the class definition for objects of type <code>OutputPage</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can get an object of this class from your SpecialPage using</span> <syntaxhighlight lang="php"> $output = $this->getOutput(); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">The variablename $output is, of course, arbitrary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Whatever you call it, this is the variable you will use the most, because it is the way to send output to the browser (no, you don't use <code>echo</code> or <code>print</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to use it somewhere, declare the variable global:</span> <syntaxhighlight lang="php"> function randomFunction() { $output = $this->getOutput(); $output->addHTML( '<b>This is not a pipe...</b>' ); } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to, you can create multiple OutputPage objects in different methods in your SpecialPage extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They will add to the output in the order they are executed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can inspect the OutputPage class by viewing <code>{{ll|Manual:OutputPage.php|includes/OutputPage.php}}</code> (indeed, all of these can be inspected), but there are a few methods you should definitely know about.</span> ====<code>OutputPage->addHTML()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">Essentially the quick and dirty substitute for <code>echo</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It takes your input and adds it to the buffer: no questions asked.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In the below action, if <code>$action</code> contains user-data, it could easily have XSS, evil stuff, or the spawn of [[w:Satan|Satan]] injected in.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You're better off using escaping (such as with the php function htmlentities) or the XML builders class to build trusted output.</span> <syntaxhighlight lang="php"> $output->addHTML( '<form action="'.$action.'" method="post">' ); </syntaxhighlight> ====<code>OutputPage->addWikiText()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">For most output, you should be using this function.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's a bit of a black magic function: wikitext goes in, HTML comes out, and a whole lotta arcane code and demon summonings happen in between.</span> <syntaxhighlight lang="php"> $output->addWikiText("This is some ''lovely'' [[wikitext]] that will '''get''' parsed nicely."); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">What's worth noting is that the parser will view your chunks as cohesive wholes and paragraph accordingly. That is...</span> <syntaxhighlight lang="php"> $output->addWikiText( '* Item 1' ); $output->addWikiText( '* Item 2' ); $output->addWikiText( '* Item 3' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Will output three lists with one item each, which probably wasn't intended.</span> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">If your special page is intended to be included in other pages, you should probably not use <code>addWikiText()</code> (or any other function that calls the parser except for message related functions that parse ($this->msg()) which are OK to call on modern versions of MediaWiki).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Due to [http://www.ehartwell.com/TechNotes/MediaWikiExtensionParserDebug.htm a bug in MediaWiki] ([[phab:T18129]]), an included special page will mess up any inclusion before it on the same including page, showing strings like UNIQ10842e596cbb71da.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Note however, if you just want to insert a system message and have it treated like parsed wikitext, you can use code like {{phpi|$this->getOutput()->addHtml( $this->msg( 'key-of-message' )->parse() )}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will not have the issue with nested parser calls mentioned above.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> =====workaround #1===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Important: these work arounds are only needed if you are making a transcludable special page. Normal special pages do not need these. </div> <span lang="en" dir="ltr" class="mw-content-ltr">As a workaround, you can have your extensions convert Wikitext to HTML using a separate Parser object and then use <code>addHTML()</code>.</span> Beispiel: <syntaxhighlight lang="php"> $wgOut->addHTML( $this->sandboxParse( "Here's some '''formatted''' text." ) ); </syntaxhighlight> <syntaxhighlight lang="php"> # Assuming this is inside the same class as the rest of your special page code function sandboxParse( $wikiText ) { $myParser = new Parser(); $user = $this->getUser(); $title = self::getTitleFor('YourCanonicalSpecialPageName'); $myParserOptions = ParserOptions::newFromUser( $user ); $result = $myParser->parse( $wikiText, $title, $myParserOptions ); return $result->getText(); } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> =====workaround #2===== </div> <span lang="en" dir="ltr" class="mw-content-ltr">I tried the above, and found that the same problem now applied to any tags in the transcluded text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This won't be a problem for a lot of extensions, but the extension I was writing was intended to show wikitext from another page as part of its functionality, so this was a problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The process for parsing a page which transcludes a special page seems to be this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace <nowiki>{{Special:MyExtension}}</nowiki> with a [[Strip marker|UNIQ-QINU marker]] (because SpecialPage output is expected to be ready-to-output HTML)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace any tags with [[Strip marker|QINU markers]] as above</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Parse everything else from wikitext to HTML</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace all [[Strip marker|QINU markers]] with their respective stored values, in a single pass</span> <span lang="en" dir="ltr" class="mw-content-ltr">The process for parsing a page which transcludes a ''non''-special page, though, is apparently like this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace <nowiki>{{:Normal Article Name}}</nowiki> or <nowiki>{{Template Name}}</nowiki> with contents of transcluded page (because transcluded pages contain unparsed wikitext)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace any tags with [[Strip marker|QINU markers]] as above</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Parse everything else from wikitext to HTML</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace all [[Strip marker|QINU markers]] with their respective stored values, in a single pass</span> <span lang="en" dir="ltr" class="mw-content-ltr">The problem is apparently that in the earlier case, the parsing of the SpecialPage's wiki text is lacking the final QINU decoding step (why?), so all the [[Strip marker|QINU markers]] are left undecoded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(This may be a leftover from using the same syntax to invoke transclusion of a wikitext page, which is just pasted straight into the host page's wikitext contents and parsed, as is used to invoke transclusion of a SpecialPage, which must not be parsed at all. Wherever the code is that decides "wait, this is a special page -- replace it with a QINU", it should be doing the extra unstripGeneral before doing the QINU substitution.)</span> {{void|1= <span lang="en" dir="ltr" class="mw-content-ltr">Wherever the code is that decides "wait, this is a special page -- replace it with a QINU", it should be doing the extra unstripGeneral before doing the QINU substitution.)</span> }} <span lang="en" dir="ltr" class="mw-content-ltr">So I just did the following -- after this line:</span> <syntaxhighlight lang="php">$htOut = $wgParser->recursiveTagParse( $iText );</syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">...I added these lines (the second one is only because the function definition for the first one recommends it):</span> <syntaxhighlight lang="php"> $htOut = $wgParser->mStripState->unstripGeneral( $htOut ); $htOut = $wgParser->mStripState->unstripNoWiki( $htOut ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Since I have now documented this, of course, I will now find a tragic flaw with it and feel really stupid... but as long as it seems to be working, I had to note it here.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(It is also important to note the problem with work-around #1.)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, I have only tested this with MediaWiki 1.10.1.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The problem still exists under MW 1.14, but this solution may or may not work.</span> --[[User:Woozle|Woozle]] 18:26, 9 April 2009 (UTC) ====<code>OutputPage->showErrorPage()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">An error page is shown.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The arguments <code>$title</code> and <code>$msg</code> specify keys into $this->msg(), not text.</span> Ein Beispiel: <syntaxhighlight lang="php"> $output->showErrorPage( 'error', 'badarticleerror' ); </syntaxhighlight> *<span lang="en" dir="ltr" class="mw-content-ltr">'error' refers to the text ''"{{int|error}}"''.</span> *<span lang="en" dir="ltr" class="mw-content-ltr">'badarticleerror' refers to the text ''"{{int|badarticleerror}}"''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can also specify message objects or add parameters:</span> <syntaxhighlight lang="php"> $output->showErrorPage( 'error', 'badarticleerror', [ 'param1', 'param2' ] ); </syntaxhighlight> <syntaxhighlight lang="php"> $messageObject = new Message(...); ... $output->showErrorPage( 'error', $messageObject ); </syntaxhighlight> <syntaxhighlight lang="php"> $titleMessageObject = new Message(...); $messageObject = new Message(...); ... $output->showErrorPage( $titleMessageObject, $messageObject ); </syntaxhighlight> ===WebRequest.php=== <span lang="en" dir="ltr" class="mw-content-ltr">The {{manual|WebRequest.php|WebRequest}} class is used to obtain information from the GET and POST arrays.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Using this is recommended over directly accessing the superglobals.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The WebRequest object is accessible from extensions by using the {{ll|RequestContext}}.</span> ===Database.php=== <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki has a load of convenience functions and wrappers for interacting with the database, using the {{manual|Database.php|\Wikimedia\Rdbms\Database}} class.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It also has an interesting load balancing scheme in place.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's recommended you use these wrappers.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Check out <code>{{ll|Manual:Database.php|Database.php}}</code> for a complete listing of all the convenience functions, because these docs will only tell you about the non-obvious caveats.</span> Siehe {{ll|Manual:Database access}}. ===User.php=== <span lang="en" dir="ltr" class="mw-content-ltr">The {{manual|User.php|User}} class is used to represent users on the system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">SpecialPage->getUser() should be used to obtain a User object for the currently logged in user.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The use of the global <code>$wgUser</code> is deprecated</span> ===Title.php=== <span lang="en" dir="ltr" class="mw-content-ltr">Title represents the name of a page in the wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is useful because MediaWiki does all sorts of fun escaping and special case logic to page names, so instead of rolling your own convert title to URL function, you create a Title object with your page name, and then use <code>getLocalURL()</code> to get a URL to that page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To get a title object for your special page from outside of the special page class, you can use {{phpi|SpecialPage::getTitleFor( 'YourCanonicalSpecialPageName' )}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will give you a localised title in the wiki's language.</span> ==Benutzerspezifische Spezialseiten== <div lang="en" dir="ltr" class="mw-content-ltr"> There are various ways to provide your own special pages not bundled within MediaWiki: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">One method is to install an extension that generates a form to create or edit an article. A list of extensions currently available, can be found at {{ll|Category:Special page extensions}}.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">You can also write an extension which provides your own special page. Writing your own extension requires [[w:PHP|PHP]] coding skill and comfort with object oriented design and databases also is helpful. You will also need to know how to use code to create and edit MediaWiki articles. For more information, please see [[Special:MyLanguage/Manual:Forms#Articles_with_embedded_forms|this discussion]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">You can also display a custom page through JavaScript, in place of the default error message "Unknown special page" (or the "This page is intentionally left blank." message, if using a subpage of [[Special:BlankPage]]). In MediaWiki:Common.js, check for {{ll|Manual:Interface/JavaScript#mw.config|wgPageName}}, then hide the MediaWiki-generated content (just appendCSS <code>{visibility:hidden;}</code> ), and inject custom HTML (<code>innerHTML</code>) into the <code>document.getElementById('bodyContent')</code> or <code>document.getElementById('mw_contentholder')</code>. For an example, see [[:meta:User:Krinkle/Tools/Real-Time Recent Changes]].</span> ==Häufig gestellte Fragen== ===Das Setzen des Titels einer Erweiterung=== <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki does not set the title of the extension, which is the developer's job.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will look for the name of the extension when [[Special:Specialpages]] is called or the special page is loaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In the [[#execute|''function execute( $par )'']] section, use OutputPage methods to title the extension like: {{phpi|$this->getOutput()->setPageTitle("your title");}}</span> <span lang="en" dir="ltr" class="mw-content-ltr">The place where the extension can be found (as specified by what is passed into the SpecialPage constructor) is the key--'''except''' that it is not capitalized because of <code>getDescription()</code>, the internally used function that finds out the title (or, what they call description) of the special page, <code>strtolower</code> the name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">"ThisIsACoolSpecialPage"'s key would be "thisisacoolspecialpage."</span> <span lang="en" dir="ltr" class="mw-content-ltr">Theoretically, <code>getDescription</code> can be overloaded in order to avoid interacting with the message cache but, as the source code states: "Derived classes can override this, but usually it is easier to keep the default behavior.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Furthermore, this prevents the MediaWiki namespace from overloading the message, as below.</span> ===Lokalisierung des Namens der Erweiterung=== <span lang="en" dir="ltr" class="mw-content-ltr">So you've just installed a shiny new MediaWiki extension and realize: "Oh no, my wiki is in French, but the page is showing up as English!"</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most people wouldn't care, but it's actually a quite simple task to fix (as long as the developer used the method explained on this page).</span> <span lang="en" dir="ltr" class="mw-content-ltr">No noodling around in source code.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Let's say the name of the page is <code>DirtyPages</code> and the name comes out to "List of Dirty Pages" but you want it to be (and [[wikipedia:Pardon my French|excuse my poor French]]) "Liste de Pages Sales".</span> <span lang="en" dir="ltr" class="mw-content-ltr">Well, it's as simple as this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Navigate to [[MediaWiki:DirtyPages]], this page may not exist, but edit it anyway</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Insert "Liste de Pages Sales" and save</span> <span lang="en" dir="ltr" class="mw-content-ltr">And ''voilà'' (pardon the pun), the change is applied.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is also useful for customizing the title for your wiki within your language: for instance, the developer called it "List of Dirty Pages" but you don't like that name, so you rename it "List of Pages needing Cleanup".</span> <span lang="en" dir="ltr" class="mw-content-ltr">Check out [[Special:Allmessages]] to learn more.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, if your extension has a large block of text that does change, like a warning, don't directly output the text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, add it to the message cache and when the time comes to output the text in your code, do this:</span> <syntaxhighlight lang="php">$wgOut->addWikiText( $this->msg( 'dirtypageshelp' ) );</syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Then this message too can be customized at [[MediaWiki:Dirtypageshelp]]. </div> Siehe auch {{ll|Help:System message}}. ===Beschränkter Seitenzugang=== ====Die Spezialseite nicht auf [[Special:SpecialPages]] zeigen==== <span lang="en" dir="ltr" class="mw-content-ltr">Sometimes you may want to limit the visibility of your Special Page by removing it from [[Special:SpecialPages]] and making it visible to only those users with a particular right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can do this in the [[#Constructor|constructor]] by passing in a <code>$restriction</code> parameter; e.g., “editinterface”, a right only assigned to sysops by default; see the [[Special:MyLanguage/Manual:User_rights|User rights manual]] for other available user rights.</span> <syntaxhighlight lang="php"> function __construct() { parent::__construct( 'MyExtension', 'editinterface' ); // restrict to sysops } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Or you can create your own right in [[#The Setup File|the setup file]] and assign it to sysops, e.g.:</span> <syntaxhighlight lang="json"> "AvailableRights": [ "myextension-right" ], "GroupPermissions": { "sysop": { "myextension-right": true } } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">and then call the constructor with your right:</span> <syntaxhighlight lang="php"> function __construct() { parent::__construct( 'MyExtension', 'myextension-right' ); } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Prevent access to your Special Page==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Even if you restrict your page in the constructor, as mentioned above, it will still be viewable directly via the URL, e.g. at Special:MySpecialPage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In order to actually limit access to your SpecialPage you must call {{phpi|$this->checkPermissions()}} in the <code>execute</code> method.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you need more fine-grained control over permissions, you can override {{phpi|$this->checkPermissions()}}, and/or add whatever permissions-checking is required for your extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Disabling Special:UserLogin and Special:UserLogout pages=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">In LocalSettings.php you can use the {{ll|Manual:Hooks/SpecialPage_initList|SpecialPage_initList hook}} to ''unset'' unwanted built-in special pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[mailarchive:mediawiki-l/2009-June/031231.html|"making a few SpecialPages restricted"]] if you need ''conditional'' unsetting of special pages for example for certain user groups.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The general message "You have requested an invalid special page." is shown if users try to access such unset special pages.</span> <syntaxhighlight lang="php"> $wgHooks['SpecialPage_initList'][] = function ( &$list ) { unset( $list['Userlogout'] ); unset( $list['Userlogin'] ); return true; }; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">A different approach would be to use the DisabledSpecialPage callback.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This approach may be preferred if you're only disabling the special page "temporarily", because the default message in this case would say: "{{int|disabledspecialpage-disabled}}" instead of pretending the page does not exist at all.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This gives clear hint that the page maybe activated at a later time.</span> <syntaxhighlight lang="php"> $wgSpecialPages['Userlogout'] = DisabledSpecialPage::getCallback( 'Userlogout' ); $wgSpecialPages['Userlogin'] = DisabledSpecialPage::getCallback( 'Userlogin' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to add custom lengthy explanation of why you're disabling the special page, by giving a message key as the second argument of the callback.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To do so first create a system message "MediaWiki:Userlogout-disable-reason" and write all the explanation there.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The message will be parsed in a block format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then in LocalSettings.php add:</span> <syntaxhighlight lang="php"> $wgSpecialPages['Userlogout'] = DisabledSpecialPage::getCallback( 'Userlogout', 'Userlogout-disable-reason' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Adding logs=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">On MediaWiki, all actions by users on wiki are tracked for transparency and collaboration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Logging to Special:Log}} for how to do it.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Changing the groups on [[Special:Specialpages]]=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you're an extension developer, you have to implement the <code>getGroupName()</code> method as described in [[#Special page group|the Special page group section]] of this page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Since MediaWiki 1.21, the special page group can be overridden by editing a [[Special:MyLanguage/Help:System message|system message]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">This method is not intended to be used by extension developers, but by site admins.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The group name must be placed in the <code><nowiki>specialpages-specialpagegroup-<special page name></nowiki></code> message, where <code><nowiki><special page name></nowiki></code> is the canonical name (in english) of the special page in lowercase.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you want to set the group under which "Special:MyLittlePage" is displayed on [[Special:Specialpages]] to "MyLittleGroup", you just have to create "MediaWiki:Specialpages-specialpagegroup-mylittlepage" with content "MyLittleGroup".</span> <span lang="en" dir="ltr" class="mw-content-ltr">"Special:MyLittlePage" will then show up under the group "MyLittleGroup", which you can name under "MediaWiki:Specialpages-group-mylittlegroup".</span><br /> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to change the group of existing special pages, have a look on [https://www.mediawiki.org/w/index.php?title=Special:SpecialPages&uselang=qqx Special:SpecialPages&uselang=qqx] and use those names instead of "mylittlepage".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Unlisting the page from [[Special:Specialpages]]=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">To remove a special page from the [[Special:Specialpages]] altogether, pass a {{phpi|false}} as a third parameter to the SpecialPage parent constructor, as described in [[#Constructor|the SpecialPage Constructor section]] of this page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you need more complicated logic to determine whether the page should be listed or not, you can also override the <code>isListed()</code> function, but using the constructor parameter is simpler.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Getting a list of special pages and their aliases on a wiki=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Simply use the "siteinfo" API module to retrieve the information from the wiki like e.g. [https://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&siprop=specialpagealiases /api.php?action=query&meta=siteinfo&siprop=specialpagealiases].</span> ==Siehe auch== *[[Special:MyLanguage/HTMLForm|HTMLForm]] – <span lang="en" dir="ltr" class="mw-content-ltr">Tutorial on creating checkboxes, text areas, radio buttons, etc. in special pages</span> [[Category:MediaWiki development{{#translation:}}|{{PAGENAME}}]] [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:User interface{{#translation:}}|{{PAGENAME}}]] [[Category:Special Pages{{#translation:}}|{{PAGENAME}}]] ab6al5u9tkplb4ln8k1vy5ku7y3lsl4 5387054 5387049 2022-07-28T20:04:23Z ThisCarthing 17456337 Created page with "Siehe $1 für die Vorgehensweise." wikitext text/x-wiki <languages/> {{ExtensionTypes}} [[File:MediaWiki-extensions-icon.svg|125px|alt=MediaWiki extensions|{{dir|{{pagelang}}|left|right}}]] '''Spezialseiten''' sind Seiten, die von der Software auf Anforderung erstellt werden, um eine bestimmte Funktion auszuführen. Beispielsweise könnte eine spezielle Seite alle Seiten anzeigen, die einen oder mehrere Links zu einer externen Webpräsenz haben, oder ein Formular erstellen, das von Benutzern eingereichte Rückmeldungen enthält. Spezialseiten befinden sich in einem eigenen [[Special:MyLanguage/Manual:Namespace|Namensraum]] ('''''Spezial:''''') und können nicht wie andere Seiten direkt bearbeitet werden. {{ll|Developers}} können auch neue Spezialseiten erstellen. Diese Seiten können für Benutzer zugänglich sein und werden im Allgemeinen in der Liste aller Sonderseiten bei [[Special:SpecialPages]] angezeigt. Einige Spezialseiten sind nur für Benutzer mit bestimmten Berechtigungen und Zugriffsrechten zugänglich. Andere Spezialseiten erscheinen überhaupt nicht auf der Spezialseiten-Liste und werden nur intern vom Wiki verwendet. == Allgemeine Informationen == <span lang="en" dir="ltr" class="mw-content-ltr">All built-in special pages that come with MediaWiki are called <code>SpecialSomename.php</code> and are located in the <code>includes/specials</code> directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Core special pages must be registered in the core list located in <code>includes/specialpage/SpecialPageFactory.php</code> in order to be loaded by MediaWiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Special pages created by third party developers are generally stored in the <code>extensions</code> directory in their own file or as part of a larger extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All special pages inherit from a class called {{class doclink|SpecialPage}} which is defined in <code>includes/specialpage/SpecialPage.php</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">When a new special page is created, the user rights needed to access the page can be defined.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These rights specify, among other things, whether the page will show up on [[Special:SpecialPages]] and whether the page is includable in other pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Special pages also have unique names that can be customized on a wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The general form is "Special:Pagename" where both "Special" and "Pagename" are customizable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Special pseudo {{ll|Manual:Namespaces|namespace}} can be translated in other languages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This translated namespace can be produced with the wikitext <nowiki>{{ns:special}}</nowiki>, on this wiki giving "{{ns:special}}".</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '''name''' of the special page can also be redefined in a system message, for the site language, with the generic name of the special page as the ID.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A special page may or may not allow input.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[Special:Export]] allows a user to define a specific page to export by calling [[Special:Export/Sun]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the special page allows complex input, additional parameters will be sent to the [[W:Query string|query string]] component of the URL for processing, e.g. https://www.mediawiki.org/w/index.php?title=Special:Recentchanges&days=3&limit=250.</span> {{Note|1=<nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * There are various ways to make [[Special:MyLanguage/Help:Special pages|special pages]], but the one below is used by the bulk of official {{ll|Manual:Extensions|extensions}}, and adherence to this style is recommended. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Also, be sure to include a credits block in the new special page for 'specialpage'. See <code>{{ll|Manual:$wgExtensionCredits|$wgExtensionCredits}}</code> for more details.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * After making a new special page, be sure to add it to {{ll|Category:Special page extensions}} so other people can find it. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * This method is only valid for MediaWiki running on PHP5 and above. If you're using an earlier version of MediaWiki on a more-recent version of PHP, {{ll|Manual:Upgrading|upgrade MediaWiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Special pages cannot be included within frames unless you use <code>$wgOut->allowClickjacking();</code> </div> }} == Grundlegende Vorlage für Spezialseiten == {{ombox|text=<span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki 1.25 introduced a [[Manual:Extension registration|new way]] to load an extension. For older unsupported versions of MediaWiki, see an [https://www.mediawiki.org/w/index.php?title=Manual:Special_pages&oldid=2331671 older revision].</span>}} Die meisten Spezialseiten-Erweiterungen erfordern drei Dateien: <div lang="en" dir="ltr" class="mw-content-ltr"> * Small setup file, which loads every time MediaWiki starts. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * File with the bulk of the code. </div> * Lokalisierungsdatei Die MediaWiki-Kodierungskonventionen definieren diese drei Dateien wie folgt: *<code>MyExtension/extension.json</code> - Die Konfigurationsdatei. *<code>MyExtension/includes/Special.php</code> - <span lang="en" dir="ltr" class="mw-content-ltr">The special page code.</span> *<code>i18n/*.json</code> - Die {{ll|localisation file}}. <div lang="en" dir="ltr" class="mw-content-ltr"> Place all of the files in a new directory inside your MediaWiki <code>extensions/</code> directory. </div> <span lang="en" dir="ltr" class="mw-content-ltr">You should name the special page file after the extension. For example, {{ll|Extension:Gadgets}} contains the file <code>SpecialGadgets.php</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your extension uses more than one special page, you'll need more names.</span> Im untenstehenden Beispiel lautet der Name der Spezialseite '''MyExtension'''. <div lang="en" dir="ltr" class="mw-content-ltr"> After creating the files listed below, adding the following line to '''LocalSettings.php''' enables the extension: </div> <syntaxhighlight lang=php> wfLoadExtension( 'MyExtension' ); </syntaxhighlight> {{anchor|The Setup File}} ===Die Konfigurationsdatei=== Beispiel für eine Konfigurationsdatei <code>MeineErweiterung/extension.json</code>: {{#tag:syntaxhighlight| { "name": "MyExtension", "version": "0.0.0", "author": [ "Your Name" ], "url": "https://www.mediawiki.org/wiki/Extension:MyExtension", "descriptionmsg": "myextension-desc", "license-name": "MIT", "type": "other", "AutoloadNamespaces": { "MediaWiki\\Extension\\MyExtension\\": "src/" }, "SpecialPages": { "MyExtension": "MediaWiki\\Extension\\MyExtension\\Special" }, "MessagesDirs": { "MyExtension": [ "i18n" ] }, "manifest_version": 2, "requires": { "MediaWiki": ">= {{MW legacy branch number}}.0", "platform": { "php": ">= 5.6" }, "extensions": { "dependendExtension": "*" } } } |lang=json}} <div lang="en" dir="ltr" class="mw-content-ltr"> This file registers several important and mandatory things: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The location of the MediaWiki\Extension\MyExtension\Special class; </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The location of the localisation files; </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The new special page and its class name. </div> {{anchor|The Special Page File}} ===Die Datei der Spezialseite=== <span lang="en" dir="ltr" class="mw-content-ltr">The body file (<code>MyExtension/src/Special.php</code>) should contain a subclass of <code>SpecialPage</code> or one of its subclasses.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This file loads automatically when someone requests the special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The example below implements the subclass SpecialMyExtension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need the <code>__construct()</code> constructor because its first parameter names your special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr"><code>execute()</code> is the main function called when a special page is accessed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This function overrides the function {{phpi|SpecialPage::execute()}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It passes the single parameter <code>$par</code>, the subpage component of the current title.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if someone follows a link to [[Special:MyExtension/blah]], <code>$par</code> contains "blah".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You should run Wikitext and HTML output through <code>$wgOut</code>. Do not use 'print' or 'echo' directly when working within the wiki's user interface. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> However, if you use your special page as an access point to custom XML or binary output, see {{ll|Taking over output in your special page}}. </div> <syntaxhighlight lang="php"> <?php namespace MediaWiki\Extension\MyExtension; class SpecialMyExtension extends \SpecialPage { function __construct() { parent::__construct( 'MyExtension' ); } function execute( $par ) { $request = $this->getRequest(); $output = $this->getOutput(); $this->setHeaders(); # Get request data from, e.g. $param = $request->getText( 'param' ); # Do stuff # ... $wikitext = 'Hello world!'; $output->addWikiTextAsInterface( $wikitext ); } } </syntaxhighlight> {{anchor|The localisation file}} ===Die Lokalisierungsdatei=== {{anchor|The Messages/Internationalization File}} :''<span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Help:System message#Adding new messages}} for how to get them translated.</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> All special pages specify a title, like <code>'My Extension'</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The title is used in the {{tag|title|open}} and {{tag|h1|open}} elements of the extension's page and on [[Special:SpecialPages]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * It can be anything, but should describe the special page and extension. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * It's specified through a message. The structure of the message is a key-value pair. The key, <code>'myextension'</code>, ''must'' be all lowercase. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An example of a localisation file in <code>MyExtension/i18n/en.json</code>: </div> <syntaxhighlight lang="javascript"> { "@metadata": { "authors": [ "<your username>" ] }, "myextension": "My Extension", "myextension-desc": "Adds the MyExtension functionality.", "myextension-summary": "On this special page, do this simple thing and earn wonders.", "group-myextensionrole": "Role of myextension", "group-myextensionrole-member": "Member of role of myextension", "grouppage-myextensionrole": "{{ns:project}}:Role of myextension", "action-myextension": "XYZ doing.", "right-myextension": "to do xyz" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">In <code>i18n/qqq.json</code>, the [[Special:MyLanguage/Help:System message#Message documentation|message documentation]]:</span> <syntaxhighlight lang="javascript"> { "@metadata": { "authors": [ "<your username>" ] }, "myextension": "The name of the extension's entry in Special:SpecialPages", "myextension-desc": "{{desc}}", "myextension-summary": "Description appearing on top of Special:MyExtension.", "action-myextension": "{{doc-action|myextension}}", "right-myextension": "{{doc-right|myextension}}" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Note that IDs should not start with an uppercase letter, and that a space in the ID should be written in the code as an underscore.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The -summary message is optional.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's created automatically by the parent class and shown on top of the special page, usually for a concise description of what the user can do on it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you don't define its content, it will only be used when wiki administrators customize it on the wiki.</span> {{anchor|The Aliases File}} === Die "aliases"-Datei === <span lang="en" dir="ltr" class="mw-content-ltr">You can also internationalize the name of the special page by creating aliases for it. The example below uses the file "MyExtension.i18n.alias.php".</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this example, the special page <code>MyExtension</code> registers an ''alias'' so the page becomes accessible at <code>.../Special:My Extension</code> and <code>.../Spezial:Meine_Erweiterung</code> in German.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Add your alias file to <code>extension.json</code>:</span> <syntaxhighlight lang="javascript"> ... "ExtensionMessagesFiles": { "MyExtensionAlias": "MyExtension.i18n.alias.php" }, ... </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Add special page aliases to <code>MyExtension.i18n.alias.php</code>:</span> <syntaxhighlight lang="php"> <?php /** * Aliases for myextension * * @file * @ingroup Extensions */ $specialPageAliases = []; /** English * @author <your username> */ $specialPageAliases['en'] = [ 'MyExtension' => [ 'MyExtension', 'My Extension' ], ]; /** Deutsch * @author <your username> */ $specialPageAliases['de'] = [ 'MyExtension' => [ 'MeineErweiterung', 'Meine Erweiterung' ], ]; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Again, you should write a space in the ID and an underscore in the code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For the page header and linking, the usual rules for page names apply. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If <code>{{ll|Manual:$wgCapitalLinks|$wgCapitalLinks}}</code> is true, a lowercase letter is converted to uppercase, and an underscore is displayed as a space. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, instead of the above, we could use <code>'my_extension' => 'My extension'</code>, assuming we consistently identified the extension as <code>my_extension</code> elsewhere. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that in the associative array for the English language, the string identifying our SpecialPage (<code>MyExtension</code> in the example) is ''also'' a valid title. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Also note, the first element of {{phpi|$specialPageAliases['en']['MyExtension']}} ''must'' be the same as the key (<code>'MyExtension'</code>)! Otherwise [[Special:Specialpages]] will not list the page. </div> {{anchor|Special page group}} ====Spezialseiten-Gruppe==== <div lang="en" dir="ltr" class="mw-content-ltr"> You can set which group your special page appears under on [[Special:SpecialPages]] by overriding <code>SpecialPage::getGroupName()</code> in your subclass. </div> <syntaxhighlight lang="php"> /** * Override the parent to set where the special page appears on Special:SpecialPages * 'other' is the default. If that's what you want, you do not need to override. * Specify 'media' to use the <code>specialpages-group-media</code> system interface message, which translates to 'Media reports and uploads' in English; * * @return string */ function getGroupName() { return 'media'; } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Some common values are 'login', 'maintenance', 'media', 'other', 'pagetools', 'redirects', 'users'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can see the accepted values at <nowiki>Special:AllMessages</nowiki> (search for '''specialpages-group''') or browse the wiki using the pseudo language 'qqx' by going to <nowiki>Special:SpecialPages?uselang=qqx</nowiki>) and looking at the headings.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Specify the word 'media' to use the interface message 'specialpages-group-media'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your special page doesn't fit into any of the preconfigured headings, you can add a new heading by adding it to your localisation file, see [[#The localisation file|The localisation file]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The standard page groups that come with MediaWiki are listed in the localisation file. For example, the English messages are in <code>languages/i18n/en.json</code> and begin with <code>specialpages-group-</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to categorize your special page under <code>users</code>, then the message is <code>specialpages-group-users</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value for this key is the text that appears as the name of that category, for example, <code>Users and rights</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your special page does not seem to fit under any of the existing categories, you can always make a new one.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In your extension's localisation file simply insert a new key for the <code>messages</code> array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this example, we define the <code>gamification</code> group:</span> <syntaxhighlight lang="json"> { "myextension": "My Extension", "myextension-desc": "Adds the MyExtension functionality.", "myextension-summary": "On this special page, do this simple thing and earn wonders", "specialpages-group-gamification": "Gamification" } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Now, assuming you set the return value for the method <code>SpecialPage::getGroupName()</code> as <code>gamification</code> in your class definition, reload [[Special:SpecialPages]] to see your new category.</span> ==Andere wichtige Dateien== ===SpecialPage.php=== {{anchor|Constructor}} ====Konstruktor==== <span lang="en" dir="ltr" class="mw-content-ltr">You can [[w:Method overloading|overload]] the constructor to initialize your own data, but the main reason you would want to do it is to change the behavior of the SpecialPage class itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">When you call the base class constructor from your child class, the following parameters are available:</span> <syntaxhighlight lang="php"> function __construct( $name = '', $restriction = '', $listed = true ); </syntaxhighlight> * ''string'' <code>$name</code> <span lang="en" dir="ltr" class="mw-content-ltr">Name of the special page, as seen in links and URLs</span> * ''string'' <code>$restriction</code> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Manual:User rights|User right]] required, e.g. "block" or "delete"; also see [[Special:MyLanguage/Manual:Special_pages#Restricting_page_access|Restricting page access]]</span> * ''boolean'' <code>$listed</code> <span lang="en" dir="ltr" class="mw-content-ltr">Whether the page is listed in Special:Specialpages</span> ====<code>SpecialPage->setHeaders()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This initialises the OutputPage object <code>$wgOut</code> with the name and description of your special page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It should always be called from your execute() method.</span> ====<code>SpecialPage->getOutput()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This method returns an OutputPage object which can be accessed as described below.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As in the example code, use</span> <syntaxhighlight lang="php"> $output = $this->getOutput(); $output->addWikiTextAsInterface( 'Hello, World' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> instead of the deprecated <code>$wgOut</code> global variable </div> ====<code>SpecialPage->getRequest()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This method returns a WebRequest object which can be accessed as described below.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As in the example code, use</span> <syntaxhighlight lang="php"> $request = $this->getRequest(); $myparam = $request->getText( 'myparam' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">instead of the deprecated {{$wg|Request}} global variable</span> ====<code>SpecialPage->including()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">Some special pages can be included from within another page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you add <nowiki>{{Special:RecentChanges}}</nowiki> to the wikitext of a page, it will insert a listing of recent changes within the existing content of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Including a special page from another web page is only possible if you declared the page to be includable in the constructor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can do this by adding the following in the <code>__construct()</code> method after the parent class initialization:</span> <syntaxhighlight lang="php"> $this->mIncludable = true; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You can also define your special page class as extending the IncludableSpecialPage class.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The SpecialPage->including() function returns a boolean value telling you what context the special page is being called from: false if it is a separate web page, and true if it is being included from within another web page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Usually you will want to strip down the presentation somewhat if the page is being included.</span> {{anchor|execute}} ====<code>SpecialPage->execute()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">This is the function which your child class should overload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It passes a single parameter, usually referred to cryptically as <code>$par</code> (short for $parameter, as it is the parameter the users can feed to your special page).</span> <span lang="en" dir="ltr" class="mw-content-ltr">This parameter is the subpage component of the current title.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if someone follows a link to [[Special:MyExtension/blah]], <code>$par</code> will contain "blah".</span> =====Hilfe-Datei===== {{MW 1.25|and later}} <span lang="en" dir="ltr" class="mw-content-ltr">It's useful to add [[Special:MyLanguage/Project:PD help|help pages]] on MediaWiki.org, where they'll be [[Special:MyLanguage/Project:Language policy|translatable]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">To make sure users find your help page, it's advisable and very simple for your special page to link the help page in question:</span> <syntaxhighlight lang="php"> $this->addHelpLink( 'Help:Extension:MyExtension' ); </syntaxhighlight> ===OutputPage.php=== <span lang="en" dir="ltr" class="mw-content-ltr">OutputPage.php contains the class definition for objects of type <code>OutputPage</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can get an object of this class from your SpecialPage using</span> <syntaxhighlight lang="php"> $output = $this->getOutput(); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">The variablename $output is, of course, arbitrary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Whatever you call it, this is the variable you will use the most, because it is the way to send output to the browser (no, you don't use <code>echo</code> or <code>print</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to use it somewhere, declare the variable global:</span> <syntaxhighlight lang="php"> function randomFunction() { $output = $this->getOutput(); $output->addHTML( '<b>This is not a pipe...</b>' ); } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to, you can create multiple OutputPage objects in different methods in your SpecialPage extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They will add to the output in the order they are executed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can inspect the OutputPage class by viewing <code>{{ll|Manual:OutputPage.php|includes/OutputPage.php}}</code> (indeed, all of these can be inspected), but there are a few methods you should definitely know about.</span> ====<code>OutputPage->addHTML()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">Essentially the quick and dirty substitute for <code>echo</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It takes your input and adds it to the buffer: no questions asked.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In the below action, if <code>$action</code> contains user-data, it could easily have XSS, evil stuff, or the spawn of [[w:Satan|Satan]] injected in.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You're better off using escaping (such as with the php function htmlentities) or the XML builders class to build trusted output.</span> <syntaxhighlight lang="php"> $output->addHTML( '<form action="'.$action.'" method="post">' ); </syntaxhighlight> ====<code>OutputPage->addWikiText()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">For most output, you should be using this function.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's a bit of a black magic function: wikitext goes in, HTML comes out, and a whole lotta arcane code and demon summonings happen in between.</span> <syntaxhighlight lang="php"> $output->addWikiText("This is some ''lovely'' [[wikitext]] that will '''get''' parsed nicely."); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">What's worth noting is that the parser will view your chunks as cohesive wholes and paragraph accordingly. That is...</span> <syntaxhighlight lang="php"> $output->addWikiText( '* Item 1' ); $output->addWikiText( '* Item 2' ); $output->addWikiText( '* Item 3' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Will output three lists with one item each, which probably wasn't intended.</span> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">If your special page is intended to be included in other pages, you should probably not use <code>addWikiText()</code> (or any other function that calls the parser except for message related functions that parse ($this->msg()) which are OK to call on modern versions of MediaWiki).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Due to [http://www.ehartwell.com/TechNotes/MediaWikiExtensionParserDebug.htm a bug in MediaWiki] ([[phab:T18129]]), an included special page will mess up any inclusion before it on the same including page, showing strings like UNIQ10842e596cbb71da.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Note however, if you just want to insert a system message and have it treated like parsed wikitext, you can use code like {{phpi|$this->getOutput()->addHtml( $this->msg( 'key-of-message' )->parse() )}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will not have the issue with nested parser calls mentioned above.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> =====workaround #1===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Important: these work arounds are only needed if you are making a transcludable special page. Normal special pages do not need these. </div> <span lang="en" dir="ltr" class="mw-content-ltr">As a workaround, you can have your extensions convert Wikitext to HTML using a separate Parser object and then use <code>addHTML()</code>.</span> Beispiel: <syntaxhighlight lang="php"> $wgOut->addHTML( $this->sandboxParse( "Here's some '''formatted''' text." ) ); </syntaxhighlight> <syntaxhighlight lang="php"> # Assuming this is inside the same class as the rest of your special page code function sandboxParse( $wikiText ) { $myParser = new Parser(); $user = $this->getUser(); $title = self::getTitleFor('YourCanonicalSpecialPageName'); $myParserOptions = ParserOptions::newFromUser( $user ); $result = $myParser->parse( $wikiText, $title, $myParserOptions ); return $result->getText(); } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> =====workaround #2===== </div> <span lang="en" dir="ltr" class="mw-content-ltr">I tried the above, and found that the same problem now applied to any tags in the transcluded text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This won't be a problem for a lot of extensions, but the extension I was writing was intended to show wikitext from another page as part of its functionality, so this was a problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The process for parsing a page which transcludes a special page seems to be this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace <nowiki>{{Special:MyExtension}}</nowiki> with a [[Strip marker|UNIQ-QINU marker]] (because SpecialPage output is expected to be ready-to-output HTML)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace any tags with [[Strip marker|QINU markers]] as above</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Parse everything else from wikitext to HTML</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace all [[Strip marker|QINU markers]] with their respective stored values, in a single pass</span> <span lang="en" dir="ltr" class="mw-content-ltr">The process for parsing a page which transcludes a ''non''-special page, though, is apparently like this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace <nowiki>{{:Normal Article Name}}</nowiki> or <nowiki>{{Template Name}}</nowiki> with contents of transcluded page (because transcluded pages contain unparsed wikitext)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace any tags with [[Strip marker|QINU markers]] as above</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Parse everything else from wikitext to HTML</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Replace all [[Strip marker|QINU markers]] with their respective stored values, in a single pass</span> <span lang="en" dir="ltr" class="mw-content-ltr">The problem is apparently that in the earlier case, the parsing of the SpecialPage's wiki text is lacking the final QINU decoding step (why?), so all the [[Strip marker|QINU markers]] are left undecoded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(This may be a leftover from using the same syntax to invoke transclusion of a wikitext page, which is just pasted straight into the host page's wikitext contents and parsed, as is used to invoke transclusion of a SpecialPage, which must not be parsed at all. Wherever the code is that decides "wait, this is a special page -- replace it with a QINU", it should be doing the extra unstripGeneral before doing the QINU substitution.)</span> {{void|1= <span lang="en" dir="ltr" class="mw-content-ltr">Wherever the code is that decides "wait, this is a special page -- replace it with a QINU", it should be doing the extra unstripGeneral before doing the QINU substitution.)</span> }} <span lang="en" dir="ltr" class="mw-content-ltr">So I just did the following -- after this line:</span> <syntaxhighlight lang="php">$htOut = $wgParser->recursiveTagParse( $iText );</syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">...I added these lines (the second one is only because the function definition for the first one recommends it):</span> <syntaxhighlight lang="php"> $htOut = $wgParser->mStripState->unstripGeneral( $htOut ); $htOut = $wgParser->mStripState->unstripNoWiki( $htOut ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Since I have now documented this, of course, I will now find a tragic flaw with it and feel really stupid... but as long as it seems to be working, I had to note it here.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(It is also important to note the problem with work-around #1.)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, I have only tested this with MediaWiki 1.10.1.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The problem still exists under MW 1.14, but this solution may or may not work.</span> --[[User:Woozle|Woozle]] 18:26, 9 April 2009 (UTC) ====<code>OutputPage->showErrorPage()</code>==== <span lang="en" dir="ltr" class="mw-content-ltr">An error page is shown.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The arguments <code>$title</code> and <code>$msg</code> specify keys into $this->msg(), not text.</span> Ein Beispiel: <syntaxhighlight lang="php"> $output->showErrorPage( 'error', 'badarticleerror' ); </syntaxhighlight> *<span lang="en" dir="ltr" class="mw-content-ltr">'error' refers to the text ''"{{int|error}}"''.</span> *<span lang="en" dir="ltr" class="mw-content-ltr">'badarticleerror' refers to the text ''"{{int|badarticleerror}}"''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can also specify message objects or add parameters:</span> <syntaxhighlight lang="php"> $output->showErrorPage( 'error', 'badarticleerror', [ 'param1', 'param2' ] ); </syntaxhighlight> <syntaxhighlight lang="php"> $messageObject = new Message(...); ... $output->showErrorPage( 'error', $messageObject ); </syntaxhighlight> <syntaxhighlight lang="php"> $titleMessageObject = new Message(...); $messageObject = new Message(...); ... $output->showErrorPage( $titleMessageObject, $messageObject ); </syntaxhighlight> ===WebRequest.php=== <span lang="en" dir="ltr" class="mw-content-ltr">The {{manual|WebRequest.php|WebRequest}} class is used to obtain information from the GET and POST arrays.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Using this is recommended over directly accessing the superglobals.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The WebRequest object is accessible from extensions by using the {{ll|RequestContext}}.</span> ===Database.php=== <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki has a load of convenience functions and wrappers for interacting with the database, using the {{manual|Database.php|\Wikimedia\Rdbms\Database}} class.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It also has an interesting load balancing scheme in place.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's recommended you use these wrappers.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Check out <code>{{ll|Manual:Database.php|Database.php}}</code> for a complete listing of all the convenience functions, because these docs will only tell you about the non-obvious caveats.</span> Siehe {{ll|Manual:Database access}}. ===User.php=== <span lang="en" dir="ltr" class="mw-content-ltr">The {{manual|User.php|User}} class is used to represent users on the system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">SpecialPage->getUser() should be used to obtain a User object for the currently logged in user.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The use of the global <code>$wgUser</code> is deprecated</span> ===Title.php=== <span lang="en" dir="ltr" class="mw-content-ltr">Title represents the name of a page in the wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is useful because MediaWiki does all sorts of fun escaping and special case logic to page names, so instead of rolling your own convert title to URL function, you create a Title object with your page name, and then use <code>getLocalURL()</code> to get a URL to that page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To get a title object for your special page from outside of the special page class, you can use {{phpi|SpecialPage::getTitleFor( 'YourCanonicalSpecialPageName' )}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will give you a localised title in the wiki's language.</span> ==Benutzerspezifische Spezialseiten== <div lang="en" dir="ltr" class="mw-content-ltr"> There are various ways to provide your own special pages not bundled within MediaWiki: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">One method is to install an extension that generates a form to create or edit an article. A list of extensions currently available, can be found at {{ll|Category:Special page extensions}}.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">You can also write an extension which provides your own special page. Writing your own extension requires [[w:PHP|PHP]] coding skill and comfort with object oriented design and databases also is helpful. You will also need to know how to use code to create and edit MediaWiki articles. For more information, please see [[Special:MyLanguage/Manual:Forms#Articles_with_embedded_forms|this discussion]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">You can also display a custom page through JavaScript, in place of the default error message "Unknown special page" (or the "This page is intentionally left blank." message, if using a subpage of [[Special:BlankPage]]). In MediaWiki:Common.js, check for {{ll|Manual:Interface/JavaScript#mw.config|wgPageName}}, then hide the MediaWiki-generated content (just appendCSS <code>{visibility:hidden;}</code> ), and inject custom HTML (<code>innerHTML</code>) into the <code>document.getElementById('bodyContent')</code> or <code>document.getElementById('mw_contentholder')</code>. For an example, see [[:meta:User:Krinkle/Tools/Real-Time Recent Changes]].</span> ==Häufig gestellte Fragen== ===Das Setzen des Titels einer Erweiterung=== <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki does not set the title of the extension, which is the developer's job.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will look for the name of the extension when [[Special:Specialpages]] is called or the special page is loaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In the [[#execute|''function execute( $par )'']] section, use OutputPage methods to title the extension like: {{phpi|$this->getOutput()->setPageTitle("your title");}}</span> <span lang="en" dir="ltr" class="mw-content-ltr">The place where the extension can be found (as specified by what is passed into the SpecialPage constructor) is the key--'''except''' that it is not capitalized because of <code>getDescription()</code>, the internally used function that finds out the title (or, what they call description) of the special page, <code>strtolower</code> the name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">"ThisIsACoolSpecialPage"'s key would be "thisisacoolspecialpage."</span> <span lang="en" dir="ltr" class="mw-content-ltr">Theoretically, <code>getDescription</code> can be overloaded in order to avoid interacting with the message cache but, as the source code states: "Derived classes can override this, but usually it is easier to keep the default behavior.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Furthermore, this prevents the MediaWiki namespace from overloading the message, as below.</span> ===Lokalisierung des Namens der Erweiterung=== <span lang="en" dir="ltr" class="mw-content-ltr">So you've just installed a shiny new MediaWiki extension and realize: "Oh no, my wiki is in French, but the page is showing up as English!"</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most people wouldn't care, but it's actually a quite simple task to fix (as long as the developer used the method explained on this page).</span> <span lang="en" dir="ltr" class="mw-content-ltr">No noodling around in source code.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Let's say the name of the page is <code>DirtyPages</code> and the name comes out to "List of Dirty Pages" but you want it to be (and [[wikipedia:Pardon my French|excuse my poor French]]) "Liste de Pages Sales".</span> <span lang="en" dir="ltr" class="mw-content-ltr">Well, it's as simple as this:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Navigate to [[MediaWiki:DirtyPages]], this page may not exist, but edit it anyway</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Insert "Liste de Pages Sales" and save</span> <span lang="en" dir="ltr" class="mw-content-ltr">And ''voilà'' (pardon the pun), the change is applied.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is also useful for customizing the title for your wiki within your language: for instance, the developer called it "List of Dirty Pages" but you don't like that name, so you rename it "List of Pages needing Cleanup".</span> <span lang="en" dir="ltr" class="mw-content-ltr">Check out [[Special:Allmessages]] to learn more.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, if your extension has a large block of text that does change, like a warning, don't directly output the text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, add it to the message cache and when the time comes to output the text in your code, do this:</span> <syntaxhighlight lang="php">$wgOut->addWikiText( $this->msg( 'dirtypageshelp' ) );</syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Then this message too can be customized at [[MediaWiki:Dirtypageshelp]]. </div> Siehe auch {{ll|Help:System message}}. ===Beschränkter Seitenzugang=== ====Die Spezialseite nicht auf [[Special:SpecialPages]] zeigen==== <span lang="en" dir="ltr" class="mw-content-ltr">Sometimes you may want to limit the visibility of your Special Page by removing it from [[Special:SpecialPages]] and making it visible to only those users with a particular right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can do this in the [[#Constructor|constructor]] by passing in a <code>$restriction</code> parameter; e.g., “editinterface”, a right only assigned to sysops by default; see the [[Special:MyLanguage/Manual:User_rights|User rights manual]] for other available user rights.</span> <syntaxhighlight lang="php"> function __construct() { parent::__construct( 'MyExtension', 'editinterface' ); // restrict to sysops } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Or you can create your own right in [[#The Setup File|the setup file]] and assign it to sysops, e.g.:</span> <syntaxhighlight lang="json"> "AvailableRights": [ "myextension-right" ], "GroupPermissions": { "sysop": { "myextension-right": true } } </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">and then call the constructor with your right:</span> <syntaxhighlight lang="php"> function __construct() { parent::__construct( 'MyExtension', 'myextension-right' ); } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Prevent access to your Special Page==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Even if you restrict your page in the constructor, as mentioned above, it will still be viewable directly via the URL, e.g. at Special:MySpecialPage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In order to actually limit access to your SpecialPage you must call {{phpi|$this->checkPermissions()}} in the <code>execute</code> method.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you need more fine-grained control over permissions, you can override {{phpi|$this->checkPermissions()}}, and/or add whatever permissions-checking is required for your extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Disabling Special:UserLogin and Special:UserLogout pages=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">In LocalSettings.php you can use the {{ll|Manual:Hooks/SpecialPage_initList|SpecialPage_initList hook}} to ''unset'' unwanted built-in special pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[mailarchive:mediawiki-l/2009-June/031231.html|"making a few SpecialPages restricted"]] if you need ''conditional'' unsetting of special pages for example for certain user groups.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The general message "You have requested an invalid special page." is shown if users try to access such unset special pages.</span> <syntaxhighlight lang="php"> $wgHooks['SpecialPage_initList'][] = function ( &$list ) { unset( $list['Userlogout'] ); unset( $list['Userlogin'] ); return true; }; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">A different approach would be to use the DisabledSpecialPage callback.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This approach may be preferred if you're only disabling the special page "temporarily", because the default message in this case would say: "{{int|disabledspecialpage-disabled}}" instead of pretending the page does not exist at all.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This gives clear hint that the page maybe activated at a later time.</span> <syntaxhighlight lang="php"> $wgSpecialPages['Userlogout'] = DisabledSpecialPage::getCallback( 'Userlogout' ); $wgSpecialPages['Userlogin'] = DisabledSpecialPage::getCallback( 'Userlogin' ); </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to add custom lengthy explanation of why you're disabling the special page, by giving a message key as the second argument of the callback.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To do so first create a system message "MediaWiki:Userlogout-disable-reason" and write all the explanation there.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The message will be parsed in a block format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then in LocalSettings.php add:</span> <syntaxhighlight lang="php"> $wgSpecialPages['Userlogout'] = DisabledSpecialPage::getCallback( 'Userlogout', 'Userlogout-disable-reason' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Adding logs=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">On MediaWiki, all actions by users on wiki are tracked for transparency and collaboration.</span> Siehe {{ll|Manual:Logging to Special:Log}} für die Vorgehensweise. <div lang="en" dir="ltr" class="mw-content-ltr"> ===Changing the groups on [[Special:Specialpages]]=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you're an extension developer, you have to implement the <code>getGroupName()</code> method as described in [[#Special page group|the Special page group section]] of this page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Since MediaWiki 1.21, the special page group can be overridden by editing a [[Special:MyLanguage/Help:System message|system message]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">This method is not intended to be used by extension developers, but by site admins.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The group name must be placed in the <code><nowiki>specialpages-specialpagegroup-<special page name></nowiki></code> message, where <code><nowiki><special page name></nowiki></code> is the canonical name (in english) of the special page in lowercase.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you want to set the group under which "Special:MyLittlePage" is displayed on [[Special:Specialpages]] to "MyLittleGroup", you just have to create "MediaWiki:Specialpages-specialpagegroup-mylittlepage" with content "MyLittleGroup".</span> <span lang="en" dir="ltr" class="mw-content-ltr">"Special:MyLittlePage" will then show up under the group "MyLittleGroup", which you can name under "MediaWiki:Specialpages-group-mylittlegroup".</span><br /> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to change the group of existing special pages, have a look on [https://www.mediawiki.org/w/index.php?title=Special:SpecialPages&uselang=qqx Special:SpecialPages&uselang=qqx] and use those names instead of "mylittlepage".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Unlisting the page from [[Special:Specialpages]]=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">To remove a special page from the [[Special:Specialpages]] altogether, pass a {{phpi|false}} as a third parameter to the SpecialPage parent constructor, as described in [[#Constructor|the SpecialPage Constructor section]] of this page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you need more complicated logic to determine whether the page should be listed or not, you can also override the <code>isListed()</code> function, but using the constructor parameter is simpler.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Getting a list of special pages and their aliases on a wiki=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Simply use the "siteinfo" API module to retrieve the information from the wiki like e.g. [https://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&siprop=specialpagealiases /api.php?action=query&meta=siteinfo&siprop=specialpagealiases].</span> ==Siehe auch== *[[Special:MyLanguage/HTMLForm|HTMLForm]] – <span lang="en" dir="ltr" class="mw-content-ltr">Tutorial on creating checkboxes, text areas, radio buttons, etc. in special pages</span> [[Category:MediaWiki development{{#translation:}}|{{PAGENAME}}]] [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:User interface{{#translation:}}|{{PAGENAME}}]] [[Category:Special Pages{{#translation:}}|{{PAGENAME}}]] cvieo0xf6er4dkurm95i6elvfxbxqrv Template:InstallationNav/diq 10 98386 5387192 5384779 2022-07-28T21:17:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installation/zh 100 99522 5387817 1396208 2022-07-29T09:28:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/zh]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/zh]] qrimzzgio3038yaymj8xbmi9ea03i0e Wikimedia Product 0 102066 5387486 5358133 2022-07-28T22:44:45Z MKampurath (WMF) 17517352 /* Metrics */ Added June 2022 Wikimedia Movement metrics wikitext text/x-wiki <languages /> {{Tech header|1=<translate><!--T:1--> '''Wikimedia Product''' staff [[<tvar|staff>foundationsite:role/staff-contractors/</>|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[<tvar|projects>m:Special:MyLanguage/Wikimedia projects</>|Wikimedia sites]].</translate>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198"><translate><!--T:3--> Contributors</translate></span>]] * [[Readers|<span style="color:#2aa198"><translate><!--T:4--> Readers</translate></span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <translate><!--T:46--> Across Product</translate> == * [[Special:MyLanguage/Product Principles|<translate><!--T:197--> Product Principles</translate>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<translate><!--T:280--> formerly:</translate> [[Special:MyLanguage/Technical Collaboration Guidance|<translate><!--T:47--> Technical Collaboration Guidance</translate>]]) * [[Special:MyLanguage/Design/Statement of purpose|<translate><!--T:49--> Design Statement of Purpose</translate>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<translate><!--T:50--> Data and research information for products</translate>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<translate><!--T:51--> Monthly Research Showcases</translate>]] === <translate><!--T:52--> Programs</translate> === * [[m:Special:MyLanguage/Communications/Audience research|<translate><!--T:58--> Audience Research</translate>]] * [[m:Special:MyLanguage/Community health initiative|<translate><!--T:53--> Community Health Initiative</translate>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<translate><!--T:200--> New Editor Experiences</translate>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<translate><!--T:55--> New Readers</translate>]] — <translate><!--T:56--> on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</translate> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<translate><!--T:54--> Structured Data on Commons</translate>]] === <translate><!--T:201--> Project Pages</translate> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<translate><!--T:202--> Annual Plan goal: New Content</translate>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<translate><!--T:203--> Advanced Mobile Contributions</translate>]] * [[Special:MyLanguage/Android editing features|<translate><!--T:204--> Android Editing Features</translate>]] * [[Special:MyLanguage/Content translation/V2|<translate><!--T:205--> Content Translation, V2</translate>]] * [[Special:MyLanguage/Growth/Growth team updates|<translate><!--T:206--> Growth</translate>]] * [[Special:MyLanguage/Language tools|<translate><!--T:207--> Improve Translate Extension and Translate Wiki process</translate>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<translate><!--T:208--> iOS Editing</translate>]] * [[Special:MyLanguage/VisualEditor on mobile|<translate><!--T:209--> Visual based mobile editing</translate>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<translate><!--T:210--> Annual Plan goal: Better Use of Data</translate>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<translate><!--T:211--> Better use of Data</translate>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<translate><!--T:212--> Data collection: Instrumentation</translate>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<translate><!--T:213--> Report stewardship</translate>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<translate><!--T:214--> Annual Plan goal: Community Wishlist</translate>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<translate><!--T:215--> Wishlist</translate>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<translate><!--T:216--> Support for smaller user groups</translate>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<translate><!--T:217--> Tech tools for program and event organizers</translate>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<translate><!--T:218--> Annual Plan goal: Anti-Harassment Tools</translate>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<translate><!--T:219--> Reporting system</translate>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<translate><!--T:220--> Annual Plan goal: Wikidata</translate>''']] '''<translate><!--T:221--> Other:</translate>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <translate><!--T:222--> Annual Pan goal: Platform Evolution CDP</translate>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<translate><!--T:223--> Invest in the MobileFrontend & MinervaNeue frontend architecture</translate>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<translate><!--T:224--> Parser unification</translate>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<translate><!--T:225--> TemplateStyles</translate>]] * [[m:Special:MyLanguage/Movement Organizers|<translate><!--T:226--> Movement Organizers Study</translate>]] (2019) <translate> == Metrics == <!--T:190--> </translate> <translate><!--T:227--> The [[<tvar|ProductAnalytics>Special:MyLanguage/Product Analytics</>|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</translate> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<translate><!--T:228--> The monthly report on key metrics tracking the overall health of the Wikimedia movement.</translate>]] == <translate><!--T:64--> Product teams</translate> == <translate><!--T:65--> A Product team covers a set of features developed according to specific user flows and needs.</translate> === <translate><!--T:87--> Contributors</translate> === <translate><!--T:88--> We build collaborative, inclusive tools for creating and editing free knowledge.</translate> * <translate><!--T:91--> Phabricator task boards:</translate> [[phab:tag/contributors-team/|#Contributors-Team]] <translate><!--T:175--> (rarely used)</translate> * <translate><!--T:89--> Page:</translate> [[Special:MyLanguage/Contributors|<translate><!--T:229--> Contributors</translate>]] * <translate><!--T:92--> Teams:</translate> ====== <translate><!--T:230--> Anti-Harassment Tools</translate> ====== * <translate><!--T:153--> Phabricator task board:</translate> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <translate><!--T:151--> Page:</translate> [[Special:MyLanguage/Anti-Harassment Tools|<translate><!--T:231--> Anti-Harassment Tools</translate>]] ====== <translate><!--T:232--> Community Tech</translate> ====== * [[phab:project/board/1274/|<translate><!--T:176--> Phabricator board</translate>]] * <translate><!--T:177--> Page:</translate> [[m:Special:MyLanguage/Community Tech|<translate><!--T:233--> Community Tech</translate>]] ====== <translate><!--T:234--> Editing</translate> ====== * <translate><!--T:178--> Phabricator task boards:</translate> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <translate><!--T:179--> Page:</translate> [[Special:MyLanguage/Editing team|<translate><!--T:236--> Editing team</translate>]] ====== <translate><!--T:237--> Growth</translate> ====== * <translate><!--T:180--> Phabricator task board:</translate> [[phab:project/board/1114/|#Growth-Team]] * <translate><!--T:181--> Page:</translate> [[Special:MyLanguage/Growth|<translate><!--T:238--> Growth</translate>]] ====== <translate><!--T:239--> Language</translate> ====== * <translate><!--T:182--> Phabricator task board:</translate> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <translate><!--T:183--> Page:</translate> [[Special:MyLanguage/Wikimedia Language engineering|<translate><!--T:240--> Wikimedia Language engineering</translate>]] === <translate><!--T:123--> Readers</translate> === <translate><!--T:124--> We build exceptional learning and reading experiences for the sum of all knowledge.</translate> * <translate><!--T:125--> Page:</translate> [[Special:MyLanguage/Readers|<translate><!--T:241--> Readers</translate>]] * <translate><!--T:127--> Phabricator task board:</translate> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <translate><!--T:128--> Teams:</translate> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<translate><!--T:242--> Android</translate>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<translate><!--T:243--> iOS</translate>]] ====== ====== [[Special:MyLanguage/Parsing|<translate><!--T:245--> Parsing</translate>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<translate><!--T:246--> Product Infrastructure</translate>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<translate><!--T:247--> Web</translate>]] ====== * [[Reading/Component responsibility|<translate><!--T:129--> Reading code responsibility</translate>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<translate><!--T:131--> Monthly page views, May 2013–January 2019.</translate> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<translate><!--T:130--> Total page views in year-over-year comparison, May 2013–February 2019.</translate> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<translate><!--T:248--> Desktop page views in year-over-year comparison, May 2013–February 2019.</translate> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<translate><!--T:249--> Mobile page views in year-over-year comparison, May 2013–February 2019.</translate> </gallery> === <translate><!--T:168--> Technical Program Management</translate> === <translate><!--T:250--> We are dedicated to guiding delivery processes and facilitating team health through good practices.</translate> <translate><!--T:251--> Page:</translate> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<translate><!--T:252--> Technical Program Management</translate>]] <translate><!--T:253--> Lead:</translate> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <translate><!--T:254--> Product Design</translate> === <translate><!--T:255--> We make sharing of all human knowledge easy and joyful. For everyone.</translate> <translate><!--T:256--> Page:</translate> [[Special:MyLanguage/Design#Product Design|<translate><!--T:257--> Product Design</translate>]] <translate><!--T:281--> Director:</translate> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <translate><!--T:259--> Product Analytics</translate> === <translate><!--T:260--> We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</translate> <translate><!--T:261--> Page:</translate> [[Special:MyLanguage/Product Analytics|<translate><!--T:262--> Product Analytics</translate>]] <translate><!--T:263--> Lead:</translate> Kate Zimmerman === <translate><!--T:264--> Product Design Strategy</translate> === <!--<translate><!--T:265--> ''[intro text here]''</translate>--> <translate><!--T:266--> Page:</translate> [[Special:MyLanguage/Design#Design Strategy|<translate><!--T:267--> Product Design Strategy</translate>]] <translate><!--T:268--> Lead:</translate> Margeigh Novotny === <translate><!--T:154--> Wikidata</translate> === <translate><!--T:155--> Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</translate> * <translate><!--T:156--> Page:</translate> [[d:Wikidata:Main Page|Wikidata]] * <translate><!--T:157--> Lead:</translate> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <translate><!--T:158--> Phabricator bugs & tasks board:</translate> [[phab:project/profile/71/|#wikidata]] * <translate><!--T:159--> Discussion List:</translate> wikidata@lists.wikimedia.org {|class="wikitable" |+ <translate><!--T:269--> Wikidata Team Goals</translate> |- !scope="row"| <translate><!--T:278--> WMDE Fiscal Year 2017</translate> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <translate><!--T:270--> Q1: January–March 2017</translate>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <translate><!--T:271--> Q2: April–June</translate>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <translate><!--T:272--> Q3: July–September</translate>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <translate><!--T:273--> Q4: October–December</translate>] |- !scope="row"| <translate><!--T:279--> WMDE Fiscal Year 2016</translate> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <translate><!--T:274--> Q1: January–March 2016</translate>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <translate><!--T:275--> Q2: April–June</translate>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <translate><!--T:276--> Q3: July–September</translate>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <translate><!--T:277--> Q4: October–December</translate>] |} == <translate><!--T:26--> Goals</translate> == {|class="wikitable" |- !scope="row"| <translate><!--T:191--> 2019–2020</translate> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<translate><!--T:192--> Q1: July–September 2019</translate>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<translate><!--T:193--> Q2: October–December 2019</translate>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<translate><!--T:194--> Q3: January–March 2020</translate>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<translate><!--T:195--> Q4: April–June 2020</translate>]]--> |- !scope="row"| <translate><!--T:163--> 2018–2019</translate> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<translate><!--T:164--> Q1: July–September 2018</translate>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<translate><!--T:172--> Q2: October–December 2018</translate>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<translate><!--T:169--> Q3: January–March 2019</translate>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<translate><!--T:171--> Q4: April–June 2019</translate>]] |- !scope="row"| <translate><!--T:29--> 2017–2018</translate> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<translate><!--T:32--> Q1: July–September 2017</translate>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<translate><!--T:35--> Q2: October–December 2017</translate>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<translate><!--T:38--> Q3: January–March 2018</translate>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<translate><!--T:170--> Q4: April–June 2018</translate>]] |- !scope="row"| <translate><!--T:28--> 2016–2017</translate> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<translate><!--T:31--> Q1: July–September 2016</translate>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<translate><!--T:34--> Q2: October–December 2016</translate>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<translate><!--T:37--> Q3: January–March 2017</translate>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<translate><!--T:40--> Q4: April–June 2017</translate>]] |- !scope="row"| <translate><!--T:27--> 2015–2016</translate> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<translate><!--T:30--> Q1: July–September 2015</translate>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<translate><!--T:33--> Q2: October–December 2015</translate>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<translate><!--T:36--> Q3: January–March 2016</translate>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<translate><!--T:39--> Q4: April–June 2016</translate>]] |} == <translate><!--T:41--> Annual Roadmap</translate> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<translate><!--T:196--> Annual Plan for Product 2018–2019</translate>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<translate><!--T:42--> Annual Plan for Product 2017–2018</translate>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<translate><!--T:43--> Annual Plan for Product 2016–2017</translate>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<translate><!--T:44--> 2016 Product Summary</translate>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<translate><!--T:45--> 2015 Product & Technology Review</translate>]] [[Category:WMF Projects{{#translation:}}]] bwa6rqecmfud3xk8opr9w5zw68u1o1m MediaWiki Language Extension Bundle/latest 0 104571 5387696 5185535 2022-07-29T05:44:01Z KartikMistry 550774 2022.07 wikitext text/x-wiki 2022.07 srlp5jeel4qugb8tk027tcwxtkp5pvz Groups 0 105370 5387352 5190117 2022-07-28T22:11:04Z Shirayuki 472859 make untranslatable wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] <translate><!--T:1--> '''MediaWiki groups''' organize open source community activities within the scope of specific topics and geographical areas.</translate> <translate><!--T:2--> They are [[meta:Special:MyLanguage/Wikimedia user groups|Wikimedia User Groups]] that agree on a level of coordination in the MediaWiki context.</translate> <translate><!--T:3--> As such, they extend the capacity of the [[wmf:|Wikimedia Foundation]] in [[Events|events]], [[Volunteer coordination and outreach/Training materials|training]], promotion and other technical activities benefiting Wikipedia, the Wikimedia movement and the MediaWiki software.</translate> <translate><!--T:4--> MediaWiki Groups are open to members of [[<tvar name=1>Special:MyLanguage/How to contribute</tvar>|different specialties]] and levels of expertise.</translate> <translate><!--T:5--> The richer and more diverse the better.</translate> <translate><!--T:6--> Non-technical users willing to contribute and learn are welcome too! All groups commit to the [[wmf:Friendly space policy|Friendly space policy]].</translate> <translate> <!--T:7--> MediaWiki groups can [[Groups/Wikimedia support|request support]] from the Wikimedia Foundation and chapters in various forms. == Thematic groups == <!--T:8--> <!--T:10--> Thematic MediaWiki groups collaborate with their logical counterparts in the wider [[w:FLOSS|FLOSS]] community. They are global groups, collaborating online.</translate> <translate> <!--T:11--> * They are in touch with communities within the same focus.</translate> <translate> <!--T:12--> * They participate in events of the same topic.</translate> <translate> <!--T:13--> * They promote related training and outreach activities.</translate> <translate> <!--T:14--> * They help improving the related documentation in wikimedia.org.</translate> <translate> <!--T:15--> * They collaborate with the related development teams.</translate> <translate> <!--T:16--> * Eventually some of them meet at [//wikimania.wikimedia.org/ Wikimania]. == Local groups == <!--T:17--> </translate> <div class="toccolours"> <translate> <!--T:18--> * [[Groups/San Francisco|San Francisco]] </translate> </div> <translate><!--T:19--> Local MediaWiki groups collaborate with [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia chapters]], See also [[w:Wikipedia:Meetup|Wikipedia meetups]] and other local communities related with Wikimedia, free software, free culture...</translate> <translate><!--T:20--> Their focus consists in face to face activities:</translate> <translate> <!--T:21--> * Organization of local events: meetups, training, hackfests... These events adhere to the [[wmf:Friendly_space_policy|WMF Friendly space policy]].</translate> <translate> <!--T:22--> * Participation in events held in their area.</translate> <translate> <!--T:23--> * Distribution of merchandising.</translate> <translate> <!--T:24--> * Promotion of local contributors to global MediaWiki and Wikimedia activities. <!--T:25--> Also for non-English speaking groups: * Localization of documentation and software following <tvar name=1>[[Special:MyLanguage/translatewiki.net|translatewiki.net]]</tvar> processes. </translate> <translate><!--T:26--> Local groups must be really local.</translate> <translate><!--T:27--> Starting points like e.g. Recife, Munich or Saint Petersburg are better than Brazil, Germany or Russia.</translate> <translate><!--T:28--> If you miss a channel for regional coordination then consider [[<tvar name=1>m:Special:MyLanguage/Mailing lists#Create a new list</tvar>|requesting the creation]] of a [[<tvar name=2>m:Special:MyLanguage/Mailing lists/Overview#Regional mailing lists</tvar>|regional mailing list]] and/or [[<tvar name=3>m:Special:MyLanguage/Mailing lists/Overview#Local</tvar>|local mailing list]].</translate> <translate> == Creating a group == <!--T:29--> </translate> <translate><!--T:30--> You don't need anyone to propose a group, just yourself.</translate> <translate><!--T:31--> To get it approved you must have at least three contributors.</translate> <translate> <!--T:32--> Check [[Groups/Proposals]] for more details to create your MediaWiki group. </translate> [[Category:MediaWiki Communication{{#translation:}}]] thd4fe09qi511niumgt37wgkysdxs8m Analytics/Server Admin Log 0 106289 5387055 5377335 2022-07-28T20:05:47Z Analyticslogbot 766884 SandraEbele: killing Oozie projectview-hourly and projectview-geo jobs to deploy corresponding jobs on airflow. wikitext text/x-wiki {{Tocright}} === 2022-07-28 === * 20:05 SandraEbele: killing Oozie projectview-hourly and projectview-geo jobs to deploy corresponding jobs on airflow. === 2022-07-24 === * 21:10 btullis: swapping disks on archiva1002 * 20:36 btullis: rebooting archiva1002 to pick up new disk * 15:36 btullis: btullis@ganeti1027:~$ sudo gnt-instance modify --disk add:size=200g archiva1002.wikimedia.org === 2022-07-22 === * 21:19 ottomata: restarted airflow-scheduler@platform_eng on an-airflow1003 for marco and cormac === 2022-07-19 === * 10:05 elukey: reboot an-worker1127 - hdfs datanode caused CPU stalls === 2022-07-13 === * 14:19 aqu: Deployed refinery using scap, then deployed onto hdfs (prod + test) * 06:16 aqu: analytics/refinery deployment === 2022-07-07 === * 13:38 btullis: restart refine_eventlogging_legacy_test.service on an-test-coord1001 * 09:56 btullis: restarted oozie on an-test-coord1001 * 09:23 btullis: rebooted dbstore1007 * 09:21 btullis: rebooted dbstore1005 * 09:02 btullis: restarting dbstore1003 as per announced maintenance window === 2022-07-06 === * 18:09 ottomata: enabling iceberg hive catalog connector on analytics_cluster presto * 17:57 ottomata: upgrading presto to 0.273.3 in analytics cluster - T311525 * 09:50 btullis: roll-restarting hadoop workers on the test cluster. * 09:46 btullis: restarting refinery-drop-webrequest-raw-partitions.service on an-test-coord1001 * 09:44 btullis: restarting refinery-drop-webrequest-refined-partitions.service on an-test-coord1001 * 09:42 btullis: restarted drop_event.service on an-test-coord1001 * 09:35 btullis: restarting hive-server2 and hive-metastore on an-test-coord1001 === 2022-07-05 === * 11:01 btullis: sudo cookbook sre.hadoop.roll-restart-masters test === 2022-07-04 === * 16:14 btullis: systemctl restart airflow-scheduler@research.service (on an-airflow1002) * 08:04 elukey: kill leftover processes of user `mewoph` on stat100x to allow puppet runs === 2022-06-29 === * 17:27 mforns: killed mediawiki-history-load bundle in Hue, and started corresponding mediawiki_history_load DAG in Airflow * 13:12 mforns: re-deployed refinery with scap and refinery-deploy-to-hdfs * 11:51 btullis: btullis@an-master1001:~$ sudo -u hdfs /usr/bin/hdfs haadmin -failover an-master1002-eqiad-wmnet an-master1001-eqiad-wmnet === 2022-06-28 === * 20:57 mforns: refinery deploy failed and I rolled back successfully, will try and repeat tomorrow when other people are present :] * 20:19 mforns: starting refinery deployment for refinery-source v0.2.2 * 20:19 mforns: starting refinery deploymenty * 17:25 ottomata: installing presto 0.273.3 on an-test-coord1001 and an-test-presto1001 * 12:48 milimetric: deploying airflow-dags/analytics to work on the metadata ingestion jobs === 2022-06-27 === * 20:33 btullis: systemctl reset-failed jupyter-aarora-singleuser and jupyter-seddon-singleuser on stat1005 * 20:16 btullis: checking and restarting prometheus-mysqld-exporter on an-coord1001 * 15:25 btullis: upgraded conda-base-env on an-test-client1001 from 0.0.1 to 0.0.4 === 2022-06-24 === * 15:14 ottomata: backfilled eventlogging data lost during failed gobblin job - T311263 === 2022-06-23 === * 13:48 btullis: started the namenode service on an-master1001 after failback failure * 13:41 btullis: The failback didn't work again. * 13:39 btullis: attempting failback of namenode service from an-master1002 to an-master1001 * 13:07 btullis: restarted hadoop-hdfs-namenode service on an-master1001 * 11:25 joal: kill oozie mediawiki-geoeditors-monthly-coord in favor of airflow job * 08:52 joal: Deploy airflow === 2022-06-22 === * 20:55 aqu: `scap deploy -f analytics/refinery` because of a crash during `git-fat pull` * 19:30 aqu: Deploying analytics/refinery === 2022-06-21 === * 14:56 aqu: RefineSanitize from an-launcher1002: sudo -u analytics kerberos-run-command analytics spark2-submit --class org.wikimedia.analytics.refinery.job.refine.RefineSanitize --master yarn --deploy-mode client /srv/deployment/analytics/refinery/artifacts/org/wikimedia/analytics/refinery/refinery-job-0.1.15.jar --config_file /home/aqu/refine.properties --since "2022-06-19T09:52:00+0000" --until * 13:33 aqu: sudo systemctl start monitor_refine_event_sanitized_main_immediate.service on an-launcher1002 * 10:47 btullis: proceeding with the hadoop.roll-restart-masters cookbook === 2022-06-20 === * 07:14 SandraEbele: Started Airflow 3 Wikidata metrics jobs (Articleplaceholder, Reliability and SpecialEntityData metrics). * 07:12 SandraEbele: Started Airflow3 Wikidata metrics jobs (Articleplaceholder, Relia) * 07:11 SandraEbele: killed Oozie wikidata-articleplaceholder_metrics-coord, wikidata-reliability_metrics-coord, and wikidata-specialentitydata_metrics-coord jobs. === 2022-06-17 === * 12:35 SandraEbele: deployed daily airflow dag for 3 Wikidata metrics. * 08:36 btullis: power cycled an-worker1109 as it was stuck with CPU soft lockups === 2022-06-16 === * 06:49 joal: Rerun webrequest-load-wf-upload-2022-6-15-22 after weird oozie failure === 2022-06-15 === * 14:48 btullis: deploying datahub 0.8.38 === 2022-06-14 === * 10:48 joal: unpause renamed dags * 10:44 joal: Deploy Airflow * 10:12 btullis: manually failing back hdfs-namenode to an-master1001 after fixing typo * 09:36 joal: deploy refinery onto HDFS * 08:48 btullis: roll-restarting hadoop masters T310293 * 08:40 joal: Deploying using scap again after failure cleanup on an-launcher1002 * 07:45 joal: deploy refinery using scap === 2022-06-13 === * 14:00 btullis: restarting presto service on an-coord1001 * 13:20 btullis: btullis@datahubsearch1001:~$ sudo systemctl reset-failed ifup@ens13.service T273026 * 13:09 btullis: restarting oozie service on an-coord1001 * 12:59 btullis: havaing failed over hive to an-coord1002 10 minutes ago, I'm restarting hive services on an-coord1001 * 12:26 btullis: restarting hive-server2 and hive-metastore on an-coord1002 * 09:54 joal: rerun failed refine for network_flows_internal * 09:54 joal: Rerun failed refine for mediawiki_talk_page_edit events * 09:51 joal: Manually rerun webrequest_text laod for hour 2022-06-13T03:00 * 07:18 joal: Manually rerun webrequest_text laod for hour 2022-06-12T08:00 === 2022-06-10 === * 17:00 ottomata: applied change to airflow instances to bump scheduler parsing_processes = # of cpu processors * 08:58 btullis: cookbook sre.hadoop.roll-restart-workers analytics === 2022-06-09 === * 17:17 joal: Rerun refine for failed datasets * 14:15 btullis: manually failing back HDFS namenode from an-master1002 to an-master1001 * 13:15 btullis: roll-restarting the hadoop masters to pick up new JRE === 2022-06-08 === * 18:06 joal: Restart airflow after deploy for dag reprocessing * 18:02 joal: deploying Airflow dags * 13:45 btullis: deploying refinery === 2022-06-07 === * 13:45 btullis: deploying updated eventgate images to all remaining deployments. * 11:33 btullis: deployed an updated version of eventgate to eventgate-analytics-external to address the timing mis-calculation. * 10:51 btullis: restart the eventlogging_to_druid_netflow-sanitization_daily service on an-launcher1002 === 2022-06-06 === * 13:45 btullis: restarting archiva service for new JRE * 06:31 elukey: restart memcached on an-tool1005 to pick up puppet settings and clear an alert in icinga === 2022-06-05 === * 03:14 milimetric: rerunning mw history since the last failure just looked like a fluke === 2022-06-04 === * 11:41 joal: Maunally launch refinery-sqoop-mediawiki-production after manual fix of refinery-sqoop-mediawiki * 11:39 joal: Manually sqoop enwiki:user and commonswiki:user and add _SUCCESS flag for following job to kick off === 2022-06-02 === * 15:50 mforns: deployed wikistats 2.9.5 * 14:02 joal: Start browser_general_daily on airflow * 13:19 joal: Drop and recreate wmf_raw.mediawiki_page table (field removal) * 12:44 joal: Remove wrongly formatted interlanguage data * 12:36 joal: Kill interlanguage-daily oozie job after successfull move to airflow * 12:15 joal: Deploy interlanguage fix to airflow * 09:56 joal: Relaunch sqoop after having deployed a corrective patch * 09:46 joal: Manually mark interlaguage historical tasks failed in airflow * 08:54 joal: Deploy airflow with spark3 jobs * 08:47 joal: Merging 2 airflow spark3 jobs now that their refinery counterpart is dpeloyed * 08:07 joal: Deploy refinery onto HDFS * 07:26 joal: Deploy refinery using scap === 2022-06-01 === * 21:04 milimetric: trying to rerun sqoop from a screen on an-launcher * 20:09 SandraEbele: Successfully deployed refinery using scap, then deployed onto hdfs. * 18:51 SandraEbele: About to deploy analytics/refinery (regular weekly train) * 08:39 elukey: powercycle an-worker1094 - OEM event registered in `racadm getsel`, host frozen === 2022-05-31 === * 18:48 ottomata: sudo -u hdfs hdfs dfsadmin -safemode leave on an-master1001 * 18:12 ottomata: sudo service hadoop-hdfs-namenode start on an-master1002 * 18:10 ottomata: sudo -u hdfs hdfs dfsadmin -safemode enter * 17:47 btullis: starting namenode services on am-master1001 * 17:44 btullis: restarting the datanodes on all five of the affected hadoop workers. * 17:43 btullis: restarting journalnode service on each of the five hadoop workers with journals. * 17:41 btullis: resizing each journalnode with resize2fs * 17:38 btullis: sudo lvresize -L+20G analytics1069-vg/journalnode * 17:38 btullis: increasing each of the hadoop journalnodes by 20 GB * 17:33 ottomata: stop journalnodes and datanodes on 5 hadoop journalnode hosts * 17:30 btullis: stopped the hdfs-namenode service on an-master100[1-2] * 15:36 milimetric: dropped razzi databases and deleted HDFS directories (in trash) * 06:26 elukey: `elukey@an-master1001:~$ sudo systemctl reset-failed hadoop-clean-fairscheduler-event-logs.service` === 2022-05-30 === * 20:19 SandraEbele: Restarted oozie job pageview-druid-daily-coord * 11:28 joal: deploy airflow spark3 aqs_hourly === 2022-05-25 === * 21:09 joal: Resume aqs_hourly job in airflow test * 20:33 joal: Pausing aqs_hourly job in airflow test intil we fix the spark3 issue * 06:20 elukey: `elukey@an-tool1011:~$ sudo systemctl reset-failed ifup@ens13.service` - T273026 === 2022-05-24 === * 19:54 SandraEbele: Deployed refinery using scap, then deployed onto hdfs successfully. * 18:34 SandraEbele: Deploying refinery, regular weekly deployment * 13:18 joal: Release refinery-source v0.2.0 to archiva * 10:21 btullis: restarted hadoop-yarn-nodemanager on an-worker1139 === 2022-05-23 === * 18:27 mforns: killed mobile_apps-session_metrics-coord (Airflow job is taking over) === 2022-05-21 === * 15:52 joal: Kill yarn app application_1651744501826_83884 in order to prevent the HDFS alerts === 2022-05-19 === * 16:59 ottomata: deploying airflow-dags analytics with new artifact names, first clearing artifacts cache dir - T307115 === 2022-05-18 === * 10:57 btullis: upgrading datahub to version 0.8.34 === 2022-05-17 === * 21:32 razzi: sudo systemctl reset-failed ifup@ens13.service on an-tool1007 * 08:54 btullis: booted an-tool1007 from network to begin buster upgrade === 2022-05-12 === * 14:49 razzi: undo the 2 previous confctl changes to repool dbproxy1019 to wikireplicas-b only * 14:35 razzi: razzi@cumin1001:~$ sudo confctl select service=wikireplicas-a,name=dbproxy1019.eqiad.wmnet set/pooled=yes # for T298940 === 2022-05-11 === * 18:20 razzi: disregard the above log; wrote out the command but then saw there was a warning for cr2-eqiad * 18:15 razzi: razzi@lvs1019:~$ systemctl stop pybal.service to apply change https://gerrit.wikimedia.org/r/c/operations/puppet/+/779915 * 18:06 razzi: razzi@lvs1020:~$ systemctl stop pybal.service to apply change https://gerrit.wikimedia.org/r/c/operations/puppet/+/779915 * 13:29 mforns: restarted oozie jobs after deployment: mediarequest_top_files, pageview_top_articles, unique_devices_per_domain_monthly, unique_devices_per_project_family_monthly === 2022-05-10 === * 20:32 mforns: finished refinery deploy (regular weekly train) * 19:34 mforns: starting refinery deploy (regular weekly train) === 2022-05-09 === * 15:06 SandraEbele: killed ‘apis-coord' oozie job and started corresponding airflow job ‘apis_metrics_to_graphite’ === 2022-05-06 === * 09:11 joal: kill cassandra-monthly-wf-local_group_default_T_mediarequest_top_files-2022-4 again * 08:44 joal: Rerun cassandra-monthly-wf-local_group_default_T_mediarequest_top_files-2022-4 with SRE watching network * 08:29 joal: kill cassandra-monthly-wf-local_group_default_T_mediarequest_top_files-2022-4 as it was probably saturating network === 2022-05-05 === * 18:53 btullis: restarting airflow-scheduler@platform_eng.service on an-airflow1003 * 18:53 btullis: restarted airflow-scheduler@research.service on an-airflow1002 * 18:49 btullis: restarting airflow-scheduler@analytics service on an-launcher1002 * 12:26 aqu: Regular analytics weekly train [analytics/refinery@cc4b2bd] * 09:53 btullis: roll-restarting hadoop masters to pick up new heap size * 09:16 btullis: re-enabling gobblin jobs now * 09:15 btullis: restarting failed eventlogging_to_druid_ services on an-launcher1002 * 09:00 btullis: restarting an-coord1001 * 08:53 btullis: stopping oozie on an-coord1001 === 2022-05-04 === * 08:47 btullis: rebooting an-coord1002 to pick up new kernel === 2022-05-03 === * 18:24 razzi: remove /etc/apache2/sites-available/50-superset-wikimedia-org.conf from an-tool1005 (superset staging) since it was removed from puppet but has no ensure: absent === 2022-04-27 === * 19:37 ottomata: restarting airflow services on all airflow instances after installing updated airflow debian package === 2022-04-26 === * 19:02 aqu: About to deploy analytics/refinery: Weekly deployment train + Artifacts to 0.1.27 * 12:02 joal: Rerun cassandra-daily-wf-local_group_default_T_mediarequest_per_file-2022-4-23 === 2022-04-25 === * 20:09 ottomata: dropping event.ios_notification_interaction hive table and data for backwards incompatible schema change in T290920 * 11:51 btullis: failing back hdfs active role to an-master1001 * 11:49 btullis: restarted hadoop-yarn-resourcemanager on an-master1002 to force the active role back to an-master1001 * 11:01 btullis: rebooting an-master1001 * 10:25 btullis: restarting the `check_webrequest_partitions` service on an-launcher1002 * 09:39 btullis: failover to an-master1002 successful at 3rd attempt * 09:30 btullis: 2nd attempt to switch HDFS services to an-master1002 * 09:13 btullis: switching HDFS services to an-master1002 * 08:53 btullis: rebooting an-master1002 - T304938 === 2022-04-23 === * 09:38 elukey: `apt-get clean` on an-airflow1001 to free some space === 2022-04-21 === * 22:26 mforns: killed browser_general oozie job and started corresponding airflow job === 2022-04-13 === * 16:40 razzi: reboot an-launcher1002 for security updates === 2022-04-12 === * 22:12 milimetric: deployed and synced refinery-source 0.1.26 to hdfs === 2022-04-11 === * 12:35 aqu: About to deploy analytics/refinery "Migrate mediarequest hourly from Oozie to Airflow" (replace previous msg) * 12:35 aqu: About to deploy refinery/source "Migrate mediarequest hourly from Oozie to Airflow" === 2022-04-06 === * 20:53 razzi: roll restart aqs to deploy new mediawiki history snapshot * 15:51 mforns: deployed airflow to analytics (big refactor) * 15:23 mforns: deployed Airflow to analytics_test (big refactor) * 09:18 btullis: restarted eventlogging_to_druid_netflow_hourly on an-launcher1002 === 2022-04-05 === * 20:41 razzi: deploying refinery for https://gerrit.wikimedia.org/r/c/analytics/refinery/+/776269/ * 15:54 razzi: razzi@cumin1001:~$ sudo cookbook sre.hosts.reimage --os bullseye -t T299481 dbstore1005 * 15:10 razzi: razzi@cumin1001:~$ sudo cookbook sre.hosts.reimage --os bullseye -t T299481 dbstore1003 * 15:02 razzi: set dbstore1003.eqiad.wmnet to downtime for upgrade T299481 * 15:01 razzi: set dbstore1003.eqiad.wmnet to downtime for upgrade === 2022-04-01 === * 09:05 btullis: restarted varnishkafka-eventlogging.service on cp3050 T300246 === 2022-03-29 === * 20:08 joal: rerun cassandra editors_bycountry_monthly for month 2022-02 * 20:08 mforns: restarted webrequest bundle * 19:57 mforns: restarted mediawiki-geoeditors-public_monthly-coord * 19:56 mforns: finished refinery deployment (regular weekly train) scap and hdfs * 19:53 joal: Add new columns to wmf.webrequest (high entropy CH-UA) * 19:16 joal: Drop/recreate wmf_raw.webrequest for schema change (high-entropy CH-UA) * 19:13 mforns: starting refinery deployment (regular weekly train) * 19:11 joal: kill webrequest-load oozie bundle for webrequest schema change * 17:13 razzi: razzi@cumin1001:~$ sudo cookbook sre.hosts.downtime an-tool1005.eqiad.wmnet -D 1 -r 'Testing deploy of superset 1.4.2 to staging' * 15:38 ntsako: Stopped geoeditor Airflow DAGs to check on data quality * 14:13 btullis: correction: restarted hadoop-yarn-nodemanager.service on an-worker1128 * 14:13 btullis: restarted hadoop-yarn-nodemanager.service on an-worker1238 === 2022-03-24 === * 11:15 btullis: roll-restarting kafka-jumbo brokers T300626 === 2022-03-21 === * 18:10 razzi: sudo systemctl restart jupyter-bearloga-singleuser on stat1008 === 2022-03-17 === * 17:10 ottomata: restart webrequest and pageview_actor data purge - https://gerrit.wikimedia.org/r/c/operations/puppet/+/771389 * 14:07 btullis: shutdown analytics1063 and analytics1067 with 120 minutes of downtime T303151 * 06:46 elukey: kill remaining hanging processes for ppche*lko and accra*ze on an-test-client1001 to allow users offboard (puppet broken) === 2022-03-16 === * 19:14 ottomata: deploying refinery to hadoop-test cluster with new gobblin-wmf-core jar * 18:00 razzi: sudo cookbook sre.hosts.downtime -D 3 -r 'Setting up karapace for the first time' karapace1001.eqiad.wmnet * 17:57 btullis: restarted mediawiki-history-drop-snapshot service on an-launcher1002 * 16:03 aqu: analytics/refinery - scap deply "Migrate session_length/daily from Oozie to Airflow" * 10:26 btullis: rerunning failed mediawiki_structured_task_article_link_suggestion_interaction refnie job === 2022-03-15 === * 22:16 razzi: upload karapace_2.1.3-py3.7-1_amd64.deb to apt.wikimedia.org * 19:58 razzi: upload karapace_2.1.3-py3.7-0_amd64.deb to apt.wikimedia.org * 17:24 ottomata: also change stats uid and gid to 918 on an-web1001 - T291384 * 14:35 ottomata: change stats uid and gid on all stat boxes to 918 - T291384 * 13:59 ottomata: roll restarting kafka jumbo brokers to set max.incremental.fetch.session.cache.slots=2000 - T303324 === 2022-03-14 === * 21:05 razzi: `sudo kill -9 15674` to stop unresponsive hive query === 2022-03-09 === * 21:05 ottomata: fix group ownership of cchen.db/new_editors/cohort=2021-12 after reverting T291664 - sudo -u hdfs kerberos-run-command hdfs hdfs dfs -chgrp -R analytics-privatedata-users /user/hive/warehouse/cchen.db/new_editors/cohort=2021-12 * 18:33 ottomata: fix group ownership of wmf_product.db//new_editors/cohort=2021-12 after reverting T291664 - sudo -u hdfs kerberos-run-command hdfs hdfs dfs -chgrp -R analytics-privatedata-users /user/hive/warehouse/wmf_product.db/new_editors/cohort=2021-12 * 18:32 ottomata: fix group ownership of wmf_product.db/global_markets_pageviews/year=2022/month=2 after reverting T291664 - sudo -u hdfs kerberos-run-command hdfs hdfs dfs -chgrp -R analytics-privatedata-users /user/hive/warehouse/wmf_product.db/global_markets_pageviews/year=2022/month=2 * 18:19 btullis: btullis@ganeti1024:~$ sudo gnt-instance start karapace1001.eqiad.wmnet (T301562) * 16:16 ottomata: fix group ownership of wmf_product.db/poageviews_corrected/year=222/month=2 after reverting T291664 - sudo -u hdfs kerberos-run-command hdfs hdfs dfs -chgrp -R analytics-privatedata-users /user/hive/warehouse/wmf_product.db/pageviews_corrected/year=2022/month=2 === 2022-03-08 === * 13:31 ottomata: restarted webrequest-load oozie bundle as 0073173-220113112502223-oozie-oozi-B starting at 2022-03-08T12:00Z * 13:09 ottomata: killing and rerunning webrequest-load-text-wf for webrequest_source=text/year=2022/month=3/day=7/hour=17, it was stuck in add_partition task as SUSPENDED, not sure why. * 12:47 btullis: roll-restarting druid-analytics T300626 * 12:08 btullis: roll-restarting druid-public. T300626 * 11:21 btullis: roll-restarting druid-test T300626 * 11:00 btullis: roll-restarting aqs T300626 * 10:57 btullis: restarted archiva T300626 === 2022-03-07 === * 19:14 ottomata: sudo -u hdfs kerberos-run-command hdfs hdfs dfs -chgrp -R analytics-privatedata-users /wmf/data/wmf/*/hourly/year=2022/month=3/day=7 to make sure perms are fixed after revert of T291664 * 19:13 ottomata: sudo -u hdfs kerberos-run-command hdfs hdfs dfs -chgrp -R analytics-privatedata-users /wmf/data/wmf/virtualpageview/hourly/year=2022/month=3/day=7 - revert of T291664 * 18:45 ottomata: sudo -u hdfs kerberos-run-command hdfs hdfs dfs -chgrp -R analytics-privatedata-users /wmf/data/wmf/mediacounts/year=2022/month=3/day=7 * 18:37 ottomata: sudo -u hdfs kerberos-run-command hdfs hdfs dfs -chgrp -R analytics-privatedata-users /wmf/data/wmf/webrequest/webrequest_source=text/year=2022/month=3/day=7 - after reverting - T291664 * 18:34 ottomata: restarting hive-server2 on an-coord1001 to revert hive.warehouse.subdir.inherit.perms change - T291664 * 14:44 btullis: failing back hive services to an-coord1001 * 13:09 aqu_: About to deploy analytics/refinery - Migrate wikidata/item_page_link/weekly from Oozie to Airflow * 12:45 aqu_: About to deploy airflow-dags/analytics - Migrates wikidata/item_page_link * 12:10 btullis: restarted hive-server2 process on an-coord1001 * 11:52 btullis: obtaining heap dump: `hive@an-coord1001:/srv/hive-tmp$ jmap -dump:format=b,file=hive_server2_heap_T303168.bin 16971` * 11:51 btullis: obtaining summary of heap objects and sizes: `hive@an-coord1001:/srv/hive-tmp$ jmap -histo:live 16971 > hive-object-storage-and-sizes.T303168.txt` * 11:38 btullis: failing over hive to an-coord1001 T303168 === 2022-03-05 === * 10:03 elukey: restart hadoop-yarn-nodemanager on an-worker1132 (unhealthy node, reason Linux Container Executor reached unrecoverable exception) === 2022-03-04 === * 17:46 mforns: deployed Airflow to analytics instance to fix skein logs problem * 15:50 mforns: deployed airflow in an-test-client1001 to test skein log fix * 05:19 milimetric: rerunning monthly edit hourly druid oozie coordinator === 2022-03-03 === * 17:48 ottomata: roll restart aqs to pick up new MW history snapshot === 2022-03-01 === * 18:38 SandraEbele: sandra testing * 18:34 razzi: demo irc logging to data eng team members * 10:19 btullis: btullis@an-coord1002:/srv$ sudo rm -rf an-coord1001-backup/ (#T302777) * 09:48 elukey: elukey@stat1004:~$ sudo kill `pgrep -u zpapierski` (offboarded user, puppet broken on the host) === 2022-02-28 === * 16:00 milimetric: refinery done deploying and syncing, new sqoop list is up * 15:01 milimetric: deploying new wikis to sqoop list ahead of sqoop job starting in a few hours === 2022-02-25 === * 17:00 milimetric: rerunning webrequest-load-wf-text-2022-2-25-15 after confirming all false positive loss === 2022-02-23 === * 23:00 razzi: sudo maintain-views --table flaggedrevs --databases fiwiki on clouddb1014.eqiad.wmnet and clouddb1018.eqiad.wmnet for T302233 === 2022-02-22 === * 10:37 btullis: re-enabled puppet on an-launcher1002, having absented the network_internal druid load job * 09:30 aqu: Deploying analytics/refinery on hadoop-test only. * 07:38 elukey: systemctl reset-failed mediawiki-history-drop-snapshot on an-launcher1002 (opened since a week ago) * 07:30 elukey: kill remaining processes of rhuang-ctr on stat1004 and an-test-client1001 (user offboarded, but still holding jupyter notebooks etc..). Puppet was broken trying to remove the user. === 2022-02-21 === * 17:55 elukey: kill remaining processes of rhuang-ctr on various stat nodes (user offboarded, but still holding jupyter notebooks etc..). Puppet was broken trying to remove the user. * 16:58 mforns: Deployed refinery using scap, then deployed onto hdfs (aqs hourly airflow queries) === 2022-02-19 === * 12:21 elukey: stop puppet on an-launcher1002, stop timers for eventlogging_to_druid_network_flows_internal_<nowiki>{</nowiki>hourly,daily<nowiki>}</nowiki> since no data is coming to the Kafka topic (expected due to some work for the Marseille DC) and it keeps alarming === 2022-02-17 === * 16:18 mforns: deployed wikistats2 === 2022-02-16 === * 14:13 mforns: deployed airflow-dags to analytics instance === 2022-02-15 === * 17:20 ottomata: split anaconda-wmf into 2 packages: anaconda-wmf-base and anaconda-wmf. anaconda-wmf-base is installed on workers, anaconda-wmf on clients. The size of the package on workers is now much smaller. Installing throught the cluster. relevant: T292699 === 2022-02-14 === * 17:38 razzi: razzi@an-test-client1001:~$ sudo systemctl reset-failed airflow-scheduler@analytics-test.service * 16:08 razzi: sudo cookbook sre.ganeti.makevm --vcpus 4 --memory 8 --disk 50 eqiad_B datahubsearch1002 for T301383 === 2022-02-12 === * 08:50 elukey: truncate /var/log/auth.log to 1g on krb1001 to free space on root partition (original log saved under /srv) === 2022-02-11 === * 15:06 ottomata: set hive.warehouse.subdir.inherit.perms = false - T291664 === 2022-02-10 === * 18:54 ottomata: setting up research airflow-dags scap deployment, recreating airflow database and starting from scractch (fab okayed this) - T295380 * 16:48 ottomata: deploying airflow analytics with lots of recent changes to airflow-dags repository === 2022-02-09 === * 17:41 joal: Deploy refinery onto HDFS * 17:05 joal: Deploying refinery with scap * 16:39 joal: Release refinery-source v0.1.25 to archiva === 2022-02-08 === * 07:27 elukey: restart hadoop-yarn-nodemanager on an-worker1115 (container executor reached unrecoverable exception, doesn't talk with the Yarn RM anymore) === 2022-02-07 === * 18:43 ottomata: manually installing airflow_2.1.4-py3.7-2_amd64.deb on an-test-client1001 * 14:38 ottomata: merged Set spark maxPartitionBytes to hadoop dfs block size - T300299 * 12:17 btullis: depooled aqs1009 * 11:59 btullis: depooled aqs1008 * 11:41 btullis: depooled aqs1007 * 11:03 btullis: depooled aqs1006 * 10:22 btullis: depooling aqs1005 === 2022-02-04 === * 16:05 elukey: unmask prometheus-mysqld-exporter.service and clean up the old @analytics + wmf_auto_restart units (service+timer) not used anymore on an-coord100[12] * 12:55 joal: Rerun cassandra-daily-wf-local_group_default_T_pageviews_per_article_flat-2022-2-3 * 07:12 elukey: `GRANT PROCESS, REPLICATION CLIENT ON *.* TO `prometheus`@`localhost` IDENTIFIED VIA unix_socket WITH MAX_USER_CONNECTIONS 5` on an-test-coord1001 to allow the prometheus exporter to gather metrics * 07:09 elukey: cleanup wmf_auto_restart_prometheus-mysqld-exporter@analytics-meta on an-test-coord1001 and unmasked wmf_auto_restart_prometheus-mysqld-exporter (now used) * 07:03 elukey: clean up wmf_auto_restart_prometheus-mysqld-exporter@matomo on matomo1002 (not used anymore, listed as failed) === 2022-02-03 === * 19:35 joal: Rerun virtualpageview-druid-monthly-wf-2022-1 * 19:32 btullis: re-running the failed refine_event job as per email. * 19:27 joal: Rerun virtualpageview-druid-daily-wf-2022-1-16 * 19:12 joal: Kill druid indexation stuck task on Druid (from 2022-01-17T02:31) * 19:09 joal: Kill druid-loading stuck yarn applications (3 HiveToDruid, 2 oozie launchers) * 10:04 btullis: pooling the remaining aqs_next nodes. * 07:01 elukey: kill leftover processes of decommed user on an-test-client1001 === 2022-02-01 === * 20:05 btullis: btullis@an-launcher1002:~$ sudo systemctl restart refinery-sqoop-whole-mediawiki.service * 19:01 joal: Deploying refinery with scap * 18:36 joal: Rerun virtualpageview-druid-daily-wf-2022-1-16 * 18:34 joal: rerun webrequest-druid-hourly-wf-2022-2-1-12 * 17:43 btullis: btullis@an-launcher1002:~$ sudo systemctl start refinery-sqoop-whole-mediawiki.service * 17:29 btullis: about to deploy analytics/refinery * 12:28 elukey: kill processes related to offboarded user on stat1006 to unblock puppet * 11:09 btullis: btullis@an-test-coord1001:~$ sudo apt-get -f install === 2022-01-31 === * 14:51 btullis: btullis@an-launcher1002:~$ sudo systemctl start mediawiki-history-drop-snapshot.service * 14:03 btullis: btullis@an-launcher1002:~$ sudo systemctl start mediawiki-history-drop-snapshot.service === 2022-01-27 === * 08:15 joal: Rerun failed cassandra-daily-wf-local_group_default_T_pageviews_per_article_flat-2022-1-26 === 2022-01-26 === * 15:54 joal: Add new CH-UA fields to wmf_raw.webrequest and wmf.webrequest * 15:44 joal: Kill-restart webrequest oozie job after deploy * 15:40 joal: Kill-restart edit-hourly oozie job after deploy * 15:27 joal: Deploy refinery to HDFS * 15:10 elukey: elukey@cp4036:~$ sudo systemctl restart varnishkafka-eventlogging * 15:10 elukey: elukey@cp4036:~$ sudo systemctl restart varnishkafka-statsv * 15:06 elukey: elukey@cp4035:~$ sudo systemctl restart varnishkafka-eventlogging.service - metrics showing messages stuck for a poll() * 14:56 elukey: elukey@cp4035:~$ sudo systemctl restart varnishkafka-webrequest.service - metrics showing messages stuck for a poll() * 14:52 joal: Deploy refinery with scap * 10:07 btullis: btullis@cumin1001:~$ sudo cumin 'O:cache::upload or O:cache::text' 'disable-puppet btullis-T296064-T299401' === 2022-01-25 === * 19:46 ottomata: removing hdfs druid deep storage from test cluster * 19:37 ottomata: reseting test cluster druid via druid reset-cluster https://druid.apache.org/docs/latest/operations/reset-cluster.html - T299930 * 14:30 ottomata: stopping services on an-test-coord1001 - T299930 * 14:29 ottomata: stopping druid* on an-test-druid1001 - T299930 * 11:30 btullis: pooled aqs1011 T298516 * 11:29 btullis: btullis@puppetmaster1001:~$ sudo -i confctl select name=aqs1011.eqiad.wmnet set/pooled=yes === 2022-01-24 === * 21:18 btullis: btullis@deploy1002:/srv/deployment/analytics/refinery$ scap deploy -e hadoop-test -l an-test-coord1001.eqiad.wmnet * 20:35 btullis: rebooting an-test-coord1001 after recreating the /srv/file system. * 20:28 btullis: root@an-test-coord1001:~# mke2fs -t ext4 -j -m 0.5 /dev/vg0/srv * 19:53 btullis: power cycled an-test-coord1001 from racadm * 19:50 btullis: rebooting an-test-coord1001 * 19:19 ottomata: kill mysqld on an-test-coord1001 - 19:19:04 [@an-test-coord1001:/etc] $ sudo kill 42433 * 19:02 razzi: razzi@an-test-coord1001:~$ sudo systemctl stop presto-server * 18:23 razzi: downtime an-test-coord1001 while attempting to fix /srv partition * 11:48 elukey: roll restart of kafka test brokers to pick up the new keystore/tls-certs (1y of validity) === 2022-01-22 === * 08:36 elukey: `apt-get clean` on an-test-coord1001 to free some space === 2022-01-21 === * 01:03 milimetric: rerunning the eventlogging_to_druid_network_flows_internal-sanitization_daily timer that failed to get logs === 2022-01-20 === * 11:58 btullis: re-enabled puppet on all hive nodes, deploying the updated log4j configuration for parquet * 11:36 btullis: temporarily disabling puppet on servers with hive installed T297734 * 07:49 joal: Rerun failed webrequest jobs (text and upload, 2022-01-19T19:00 === 2022-01-19 === * 15:44 ottomata: installing anaconda-wmf_2020.02~wmf6_amd64.deb on all analytics cluster nodes. - T292699 * 14:00 ottomata: installing anaconda-wmf_2020.02~wmf6_amd64.deb on stat1004 - T292699 === 2022-01-17 === * 07:19 elukey: launch webrequest bundle from 2022-01-16T01:00 (first hour missing for text) - 0003712-220113112502223-oozie-oozi-B * 07:17 elukey: kill webrequest bundle, text coordinator failed (logs/info/etc.. https://hue.wikimedia.org/hue/jobbrowser/#!id=0024621-210701181527401-oozie-oozi-B) * 07:13 elukey: umount/mount /mnt/hdfs on an-coord1001 to pick up java upgrades === 2022-01-16 === * 16:43 elukey: `elukey@an-launcher1002:~$ sudo systemctl reset-failed eventlogging_to_druid_network_internal_flows-sanitization_daily.service eventlogging_to_druid_network_internal_flows_daily.service eventlogging_to_druid_network_internal_flows_hourly.service === 2022-01-13 === * 12:41 joal: rerun failed instances of webrequest-load-coord * 11:59 btullis: stopped eventlogging service on eventlog1003 with 1 hour's downtime. * 11:52 btullis: Upgrading hive packages on stat1005 * 11:26 btullis: restarted hive-metastore and hive-server2 on an-coord1001 after running puppet. * 11:23 btullis: btullis@an-coord1001:~$ sudo apt install hive hive-hcatalog hive-jdbc hive-metastore hive-server2 oozie oozie-client * 11:18 btullis: btullis@an-coord1002:~$ sudo systemctl restart hive-metastore hive-server2 * 09:53 btullis: DNS change deployed, failing over hive to an-coord1002. * 09:42 btullis: btullis@an-coord1002:~$ sudo apt install hive hive-hcatalog hive-jdbc hive-metastore hive-server2 oozie-client * 08:45 joal: Kill-restart wikidata-json_entity-weekly-coord after deploy === 2022-01-12 === * 21:13 joal: Deploying refinery to HDFS * 20:46 joal: Deploying refinery with scap * 20:35 joal: refinery-source v0.1.24 released on archiva * 11:25 elukey: move kafka-jumbo nodes to fixed kafka uid/gid * 07:46 elukey: `systemctl reset-failed product-analytics-movement-metrics.service` on stat1007 === 2022-01-10 === * 13:56 btullis: Upgrading oozie packages on an-test-coord1001 to test new log4j versions === 2022-01-08 === * 10:51 elukey: start hive-server2 on an-coord1002 - failed to connect to the metastore due to restart * 10:41 elukey: restart hive daemons on an-coord1002 (after my last upgrade/rollback of packages the prometheus agent settings were not picked up, so no metrics) === 2022-01-07 === * 20:16 ottomata: altering hive table MobileWikiAppiOSUserHistory field event.device_level_enabled to string - T298721 * 17:29 btullis: deployed updated hive packages to an-test-worker100[1-3] and an-test-ui1001 * 14:52 btullis: root@aqs1014:~# jmap -dump:live,format=b,file=/srv/cassandra-b/tmp/aqs1014-b-dump202201071450.hprof 4468 === 2022-01-06 === * 18:02 btullis: btullis@aqs1010:~$ sudo systemctl restart cassandra-a.service * 12:22 btullis: restarting cassandra-a service on aqs1004.eqiad.wmnet in order to troubleshoot logging. * 11:24 btullis: restarting cassandra-a service on aqs1010.eqiad.wmnet in order to troubleshoot logging. * 08:12 joal: Rerun failed webrequest-load-wf-text-2022-1-6-7 * 07:58 joal: Rerun refine_event_sanitized_analytics_immediate missing hours after errors from the past days * 07:39 joal: Rerun failed refine_eventlogging_analytics for mobilewikiappiosuserhistory schema, hours 2022-01-05T2[123]:00:00 and 2022-01-06T00:00:00, dropping malformed rows as discussed with schema owner === 2022-01-05 === * 19:16 joal: Rerun failed refine_eventlogging_analytics for mobilewikiappiosuserhistory schema, hours 2022-01-04T1[5789]:00:00, dropping malformed rows as discussed with schema owner * 11:37 btullis: Upgrading hive on an-test-client1001 in order to test log4j upgrade * 11:35 btullis: Upgrading hive packages on an-test-coord1001 to test log4j changes. === 2022-01-04 === * 10:39 elukey: restart cassandra-a on aqs1010 (heap size used in full, high GC) * 10:20 elukey: restart cassandra-a on aqs1015 (heap size used in full, high GC) === 2022-01-03 === * 18:26 joal: rerun cassandra-daily-wf-local_group_default_T_mediarequest_per_file-2022-1-1 * 16:08 joal: Kill cassandra3-local_group_default_T_mediarequest_per_file-daily-2022-1-1 * 11:26 elukey: restart cassandra-b on aqs1015 (instance not responding, probably trashing) * 11:16 elukey: restart cassandra-b on aqs1010 (stuck trashing) * 10:34 elukey: depool aqs1010 (`sudo -i depool` on the node) to allow investigation of the cassandra -b instance * 10:22 elukey: powercycle an-worker1114 (CPU soft lockup errors in mgmt console) * 10:20 elukey: powercycle an-worker1120 (CPU soft lockup errors in mgmt console) {{Archive box| * [[/Archive/2021|2021]] * [[/Archive/2020|2020]] * [[/Archive/2019|2019]] * [[/Archive/2018|2018]] * [[/Archive/2017|2017]] * [[/Archive/2016|2016]] * [[/Archive/2015|2015]] * [[/Archive/2014|2014]] * [[/Archive/2013|2013]] * [[/Archive/2012|2012]] }} [[Category:Analytics]] 83g1unzps9irfr2l1dw2dwpgbrhro2i Template:InstallationNav/da 10 106427 5387191 5384776 2022-07-28T21:17:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Project:Language policy/ru 4 107345 5386714 5331057 2022-07-28T18:09:53Z Артём 13327 17625157 wikitext text/x-wiki <languages /> На этой странице описывается текущая политика '''многоязычности сайта MediaWiki.org'''. [[Image:Geographylogo.svg|{{dir|{{pagelang}}|left|right}}|150px|Языки]] == Пространство имён Help: == В рамках пространства имён <code>Help:</code> выстраивается набор [[Special:MyLanguage/Project:PD help|справочных страниц, находящихся в общественном достоянии]]. Цель состоит в том, чтобы обеспечить базовый набор охватывающих основы редактирования и инструкции по использованию справочных страниц, которые могут быть импортированными в новую вики. Эти страницы должны быть переведены на максимально возможное количество языков. * Английский язык выступает в качестве базового, и все корневые страницы названы и написаны по-английски. * Подстраницы должны использоваться ''исключительно'' для переводов на другие языки, а не для англоязычных материалов (так, например, вы не можете назвать страницу <code>Table editing/example</code> — воспользуйтесь вместо этого формой <code>Table editing example</code> или <code>Example of table editing</code>). * Если существует статья на каком-либо отличном от английского языке, и при этом у неё нет англоязычной версии, создайте, пожалуйста, для облегчения навигации заготовку такой статьи на английском. Эта система будет совместима с планируемым [[Automating help page export|автоматическим импортом/экспортом справочных страниц]], но, возможно, в переходный период потребуется некоторая работа, связанная с экспортом/импортом не-англоязычных страниц. {{anchor|translate-extension|Translate extension}} === Расширение перевода === Мы используем {{ll|Extension:Translate|Translate}} для большинства страниц. На таких страницах используются шаблоны $tpl-langcat для категорий и <nowiki>{{#translation:}}</nowiki> для включения переводимых шаблонов. Эту систему рекомендуется использовать для всех часто посещаемых страниц, для всех новых страниц помощи и технического руководства, а также для основных страниц с описанием расширений, но пока ещё на это счёт не было принято никакого строгого правила. * Для перевода: зайдите на [[Special:LanguageStats]] и начните переводить. * Для администраторов перевода: [[Special:PageTranslation]], [[Special:AggregateGroups]]. Вы можете оставить запрос на то, чтобы она была включена в список доступных для перевода страниц, — сначала вы должны подготовить (разметить) её для перевода, и только затем администратор перевода может её включить (см. [[Special:MyLanguage/Help:Extension:Translate/Page translation example|руководство на тему того, как подготовить страницу для перевода]]); или, как вариант, попросите об этом напрямую одного из [[Special:ListUsers/translationadmin|администраторов перевода]]. === Старая система === * Все не-англоязычные тексты должны размещаться на соответствующих подстраницах английской версии. Например, перевод [[Help:Contents]] на французский должен называться [[Help:Contents/fr]] (а не Help:Sommaire, Aide:Sommaire или Help:Sommaire/fr). * В названиях языковых подстраниц должны использоваться соответствующие языковые коды для этих языков (см. [[#langcodes|ниже]]). * Все страницы в справочном пространстве имён должны быть помечены шаблоном <code>{{tl|Languages}}</code>, который автоматически создаёт ссылки на все доступные переводы. ===Преобразование в систему перевода=== Имеющиеся страницы с переводами, как правило, стоит преобразовать в формат переводимых страниц. Подготовьте для перевода корневую (англоязычную) страницу (см. [[#translate-extension|Расширение перевода]]) и как только она будет отмечена как доступная для перевода, вручную импортируйте старые переводы из истории подстраниц, поместив их в соответствующие строки (элементы) нового перевода (перейдя по ссылке «Перевести эту страницу»). Новый инструмент [[Special:PagePreparation]] + [[Special:PageMigration]] поможет в этом (в настоящее время доступно только для администраторов перевода). Список страниц, которые были переведены по старой системе и теперь должны мигрировать на новую, ведётся на странице [[Project:Language policy/Migration list]]. Более подробные инструкции: <div class="mw-translate-fuzzy"> * Для более полного представления прочтите [[$help-ext-translate|основную справку]], [[$help-ext-translate-2|руководство переводчика]], [[$help-ext-translate-3|руководство по разметке страниц]] и [[$help-ext-translate-4|руководство для администратора перевода]]. </div> * Авторизуйтесь или зарегистрируйтесь на сайте mediawiki.org: вся ваша работа будет выполняться в этой вики. Выберите одну страницу из [[Project:Language_policy/Migration_list|списка страниц, назначенных к миграции]] на новый механизм перевода (задать любые вопросы вы можете прямо на странице обсуждения этого списка). По мере возможности, вычитайте и подправьте английский текст, чтобы избежать переноса устаревшего и низкокачественного текста; если в чём-то не уверены — просто пропускайте такие страницы. Подготовьте страницу для перевода (например, добавьте тег {{tag|translate|open}}, и т.п.), следуя вышеуказанным руководствам по переводу; затем отредактируйте список с очередью миграции страниц, записав около названия страницы, что вы её обработали. * [[Special:ListUsers/translationadmin|Администратор перевода]] (вы?) по своему усмотрению утвердит («отметит») страницу как доступную для перевода. Как только страница будет утверждена, завершите работу: скопируйте старые переводы соответствующих абзацев на странице Special:Translate (как это делает переводчик в вышеуказанном руководстве по переводу). Вам не нужно знать язык переведённых страниц, миграцию которых вы выполняете — вам нужно только уметь определить, какие фрагменты переводов соответствуют каким фрагментам английского текста, несмотря на то, что это может быть и не совсем верный перевод (машинный перевод может помочь вам понять смысл, если макет страницы не обеспечивает достаточно намёков). == Заглавная страница == Англоязычная версия нашей заглавной страницы расположена по адресу [[MediaWiki]]. Названия переведённых версий имеют формат MediaWiki/код, где код — это код языка (см., например, [[MediaWiki/ru]]). Чтобы узнать подробнее о создании и редактировании этих страниц, посетите, пожалуйста. специальный проект $project-mainpage. Важно, чтобы здесь, по возможности, строго выполнялось правило о кодах языков (см. [[#langcodes|ниже]]). == Другие пространства имён == За исключением Заглавной страницы, относительно других пространств имён до сих пор никаких правил не установлено. В настоящее время, если вы хотите создать переводы страниц в других пространствах имён, действуйте так, как описано для пространства имён Help: — однако эти материалы могут быть перемещены или удалены в зависимости от политики, которая, в конечном счёте, будет принята. Некоторые обсуждения по данному вопросу: см. обсуждения текущих задач [[Project:Village Pump/Archive 2#Languages|Languages]] и [[Thread:Project:Current_issues/_Project:Translate_extension|Translate extension]], а также текущие обсуждения. ''Заметьте, что правило, по которому англоязычное содержание не должно размещаться на подстраницах, не применяется к другим пространствам имён. Это одна из проблем, требующих решения.'' {{anchor|langcodes}} == Коды языков == Повсюду на MediaWiki.org при создании материалов на языках, отличных от английского, вы должны использовать коды языков, задаваемые программным обеспечением MediaWiki (см. полный и постоянно обновляемый список в файле [[phab:diffusion/MW/browse/master/includes/languages/data/Names.php|Names.php]]). Просьба также иметь в виду следующее: * Если в Names.php не нашлось кода для языка, то и здесь не следует пытаться размещать справочные страницы на этом языке. * Если вы хотите добавить отсутствующий язык, то он сначала должен быть добавлен в программное обеспечение (путём создания запроса в [[Special:MyLanguage/Phabricator|багтрекере]] по имени «Phabricator») и только после того, как изменения вступят в силу, можно будет создавать здесь справочные страницы на этом языке. * Если в MediaWiki для какого-либо языка использован «некорректный» код, то и вы должны также (для согласованности) использовать здесь этот некорректный код. Если вы считаете какой-либо из кодов некорректным, вы должны обсудить это в [[Special:MyLanguage/Phabricator|багтрекере]], и если это приведёт к изменению кода, мы также переименуем соответствующие страницы. * Обратите внимание, что некоторые коды языков в Names.php в настоящее время считаются устаревшими (например, <code>zh-yue</code> был заменён на <code>yue</code>). В этих случаях должен использоваться только самый последний код. * В общем случае перевод на варианты языков (например, <code>zh-hans</code>) запутывает, вместо него по возможности перевод должен производиться на главную страницу (например, <code>zh</code>). == См. также == * {{ll|Project:Translation}} * [[Special:TranslatorSignup]] — форма регистрации в качестве переводчика * {{ll|Project:PD help}} [[Category:MediaWiki Communication{{#translation:}}]] o48ofm6yqhbjhchnexkhf5rjvp4q0uz 5386716 5386714 2022-07-28T18:10:12Z Артём 13327 17625157 wikitext text/x-wiki <languages /> На этой странице описывается текущая политика '''многоязычности сайта MediaWiki.org'''. [[Image:Geographylogo.svg|{{dir|{{pagelang}}|left|right}}|150px|Языки]] == Пространство имён Help: == В рамках пространства имён <code>Help:</code> выстраивается набор [[Special:MyLanguage/Project:PD help|справочных страниц, находящихся в общественном достоянии]]. Цель состоит в том, чтобы обеспечить базовый набор охватывающих основы редактирования и инструкции по использованию справочных страниц, которые могут быть импортированными в новую вики. Эти страницы должны быть переведены на максимально возможное количество языков. * Английский язык выступает в качестве базового, и все корневые страницы названы и написаны по-английски. * Подстраницы должны использоваться ''исключительно'' для переводов на другие языки, а не для англоязычных материалов (так, например, вы не можете назвать страницу <code>Table editing/example</code> — воспользуйтесь вместо этого формой <code>Table editing example</code> или <code>Example of table editing</code>). * Если существует статья на каком-либо отличном от английского языке, и при этом у неё нет англоязычной версии, создайте, пожалуйста, для облегчения навигации заготовку такой статьи на английском. Эта система будет совместима с планируемым [[Automating help page export|автоматическим импортом/экспортом справочных страниц]], но, возможно, в переходный период потребуется некоторая работа, связанная с экспортом/импортом не-англоязычных страниц. {{anchor|translate-extension|Translate extension}} === Расширение перевода === Мы используем {{ll|Extension:Translate|Translate}} для большинства страниц. На таких страницах используются шаблоны $tpl-langcat для категорий и <nowiki>{{#translation:}}</nowiki> для включения переводимых шаблонов. Эту систему рекомендуется использовать для всех часто посещаемых страниц, для всех новых страниц помощи и технического руководства, а также для основных страниц с описанием расширений, но пока ещё на это счёт не было принято никакого строгого правила. * Для перевода: зайдите на [[Special:LanguageStats]] и начните переводить. * Для администраторов перевода: [[Special:PageTranslation]], [[Special:AggregateGroups]]. Вы можете оставить запрос на то, чтобы она была включена в список доступных для перевода страниц, — сначала вы должны подготовить (разметить) её для перевода, и только затем администратор перевода может её включить (см. [[Special:MyLanguage/Help:Extension:Translate/Page translation example|руководство на тему того, как подготовить страницу для перевода]]); или, как вариант, попросите об этом напрямую одного из [[Special:ListUsers/translationadmin|администраторов перевода]]. === Старая система === * Все не-англоязычные тексты должны размещаться на соответствующих подстраницах английской версии. Например, перевод [[Help:Contents]] на французский должен называться [[Help:Contents/fr]] (а не Help:Sommaire, Aide:Sommaire или Help:Sommaire/fr). * В названиях языковых подстраниц должны использоваться соответствующие языковые коды для этих языков (см. [[#langcodes|ниже]]). * Все страницы в справочном пространстве имён должны быть помечены шаблоном <code>{{tl|Languages}}</code>, который автоматически создаёт ссылки на все доступные переводы. ===Преобразование в систему перевода=== Имеющиеся страницы с переводами, как правило, стоит преобразовать в формат переводимых страниц. Подготовьте для перевода корневую (англоязычную) страницу (см. [[#translate-extension|Расширение перевода]]) и как только она будет отмечена как доступная для перевода, вручную импортируйте старые переводы из истории подстраниц, поместив их в соответствующие строки (элементы) нового перевода (перейдя по ссылке «Перевести эту страницу»). Новый инструмент [[Special:PagePreparation]] + [[Special:PageMigration]] поможет в этом (в настоящее время доступно только для администраторов перевода). Список страниц, которые были переведены по старой системе и теперь должны мигрировать на новую, ведётся на странице [[Project:Language policy/Migration list]]. Более подробные инструкции: * Для более полного представления прочтите [[Special:MyLanguage/Help:Extension:Translate|основную справку]], [[$help-ext-translate-2|руководство переводчика]], [[$help-ext-translate-3|руководство по разметке страниц]] и [[$help-ext-translate-4|руководство для администратора перевода]]. * Авторизуйтесь или зарегистрируйтесь на сайте mediawiki.org: вся ваша работа будет выполняться в этой вики. Выберите одну страницу из [[Project:Language_policy/Migration_list|списка страниц, назначенных к миграции]] на новый механизм перевода (задать любые вопросы вы можете прямо на странице обсуждения этого списка). По мере возможности, вычитайте и подправьте английский текст, чтобы избежать переноса устаревшего и низкокачественного текста; если в чём-то не уверены — просто пропускайте такие страницы. Подготовьте страницу для перевода (например, добавьте тег {{tag|translate|open}}, и т.п.), следуя вышеуказанным руководствам по переводу; затем отредактируйте список с очередью миграции страниц, записав около названия страницы, что вы её обработали. * [[Special:ListUsers/translationadmin|Администратор перевода]] (вы?) по своему усмотрению утвердит («отметит») страницу как доступную для перевода. Как только страница будет утверждена, завершите работу: скопируйте старые переводы соответствующих абзацев на странице Special:Translate (как это делает переводчик в вышеуказанном руководстве по переводу). Вам не нужно знать язык переведённых страниц, миграцию которых вы выполняете — вам нужно только уметь определить, какие фрагменты переводов соответствуют каким фрагментам английского текста, несмотря на то, что это может быть и не совсем верный перевод (машинный перевод может помочь вам понять смысл, если макет страницы не обеспечивает достаточно намёков). == Заглавная страница == Англоязычная версия нашей заглавной страницы расположена по адресу [[MediaWiki]]. Названия переведённых версий имеют формат MediaWiki/код, где код — это код языка (см., например, [[MediaWiki/ru]]). Чтобы узнать подробнее о создании и редактировании этих страниц, посетите, пожалуйста. специальный проект $project-mainpage. Важно, чтобы здесь, по возможности, строго выполнялось правило о кодах языков (см. [[#langcodes|ниже]]). == Другие пространства имён == За исключением Заглавной страницы, относительно других пространств имён до сих пор никаких правил не установлено. В настоящее время, если вы хотите создать переводы страниц в других пространствах имён, действуйте так, как описано для пространства имён Help: — однако эти материалы могут быть перемещены или удалены в зависимости от политики, которая, в конечном счёте, будет принята. Некоторые обсуждения по данному вопросу: см. обсуждения текущих задач [[Project:Village Pump/Archive 2#Languages|Languages]] и [[Thread:Project:Current_issues/_Project:Translate_extension|Translate extension]], а также текущие обсуждения. ''Заметьте, что правило, по которому англоязычное содержание не должно размещаться на подстраницах, не применяется к другим пространствам имён. Это одна из проблем, требующих решения.'' {{anchor|langcodes}} == Коды языков == Повсюду на MediaWiki.org при создании материалов на языках, отличных от английского, вы должны использовать коды языков, задаваемые программным обеспечением MediaWiki (см. полный и постоянно обновляемый список в файле [[phab:diffusion/MW/browse/master/includes/languages/data/Names.php|Names.php]]). Просьба также иметь в виду следующее: * Если в Names.php не нашлось кода для языка, то и здесь не следует пытаться размещать справочные страницы на этом языке. * Если вы хотите добавить отсутствующий язык, то он сначала должен быть добавлен в программное обеспечение (путём создания запроса в [[Special:MyLanguage/Phabricator|багтрекере]] по имени «Phabricator») и только после того, как изменения вступят в силу, можно будет создавать здесь справочные страницы на этом языке. * Если в MediaWiki для какого-либо языка использован «некорректный» код, то и вы должны также (для согласованности) использовать здесь этот некорректный код. Если вы считаете какой-либо из кодов некорректным, вы должны обсудить это в [[Special:MyLanguage/Phabricator|багтрекере]], и если это приведёт к изменению кода, мы также переименуем соответствующие страницы. * Обратите внимание, что некоторые коды языков в Names.php в настоящее время считаются устаревшими (например, <code>zh-yue</code> был заменён на <code>yue</code>). В этих случаях должен использоваться только самый последний код. * В общем случае перевод на варианты языков (например, <code>zh-hans</code>) запутывает, вместо него по возможности перевод должен производиться на главную страницу (например, <code>zh</code>). == См. также == * {{ll|Project:Translation}} * [[Special:TranslatorSignup]] — форма регистрации в качестве переводчика * {{ll|Project:PD help}} [[Category:MediaWiki Communication{{#translation:}}]] gg2uls1le8la9jfqxx6q1f3bl961tov Git/Reviewers 0 107670 5386394 5339153 2022-07-28T13:44:32Z MusikAnimal 422134 /* mediawiki/extensions/WikiEditor */ +me wikitext text/x-wiki {{Tool |name = Gerrit Reviewer Bot |status = stable |author = [[User:valhallasw]] ''Please send me a talk page message or e-mail if the bot is malfunctioning.'' |license = MIT |download = https://github.com/valhallasw/gerrit-reviewer-bot |description = Adds reviewers to Gerrit patchsets '''[//tools.wmflabs.org/gerrit-reviewer-bot/ Log of recent actions]''' }} :{{Note}} ''If you are looking for a list of people that could review your patch, please see [[Developers/Maintainers]].'' This is a page where people can register to be automatically added as reviewer to newly opened changes in [[Gerrit]] depending on specific conditions. After registering here, reviewer-bot will add you as reviewer to every change that matches the project and file filter. Gerrit supports a similar feature by itself (including filtering by modified file name and words appearing in commit message), see [[Gerrit/watched projects]] and https://gerrit.wikimedia.org/r/settings/projects. == How to add yourself == Each project has a header with the Gerrit project name, followed by a list of people (using [[Template:Gerrit-reviewer]]), for example: <pre>=== test/mediawiki/extensions/examples === * {{Gerrit-reviewer|User 2}} * {{Gerrit-reviewer|User 1|file_regexp=&lt;nowiki&gt;i18n&lt;/nowiki&gt;}} </pre> The <code>file_regexp</code> parameter can be used to filter for changes in specific files: <pre>* {{Gerrit-reviewer|User 1|file_regexp=&lt;nowiki&gt;i18n&lt;/nowiki&gt;}}</pre> will watch for changes where a file with 'i18n' in the name is changed, while <pre>* {{Gerrit-reviewer|User 1|file_regexp=&lt;nowiki&gt;^includes/specials&lt;/nowiki&gt;}}</pre> will watch for changes in the includes/specials directory. You can test the regexp using [https://pythex.org/] with IGNORECASE and DOTALL enabled. The &lt;nowiki&gt; tags are suggested but only required when the regexp contains characters that interfere with template parsing (e.g. | and }}). An optional <code>match_all_files</code> parameter makes the bot only mark changes where the <code>file_regexp</code> matches all the changed files: <pre>* {{Gerrit-reviewer|User 1|file_regexp=&lt;nowiki&gt;\.css|\.txt&lt;/nowiki&gt;|match_all_files}}</pre> This is useful since review scores apply to the whole changeset, rather than parts of it, so users that are comfortable with reviewing only a subsection of the changes wouldn't be able to review the whole patchset. For instance, front-end changes often touch both CSS and JavaScript files. A user who is confident about his CSS knowledge but not so much about his JavaScript ones can use <code>match_all_files</code> to restrict reviews attributed to them to those that only touch CSS files. == Listen to repository groups == Projects are matched based on unix filename matching [https://docs.python.org/2/library/fnmatch.html as implemented in the fnmatch module]. The idea is to set a file_regexp, which filters changesets by changed files instead of repository. === * === * {{Gerrit-reviewer|Jackmcbarn|file_regexp=<nowiki>([Ll]ibrary\.php|\.lua)$</nowiki>}} * {{Gerrit-reviewer|Zoranzoki21|file_regexp=<nowiki>(bs|hr|sr\-e[cl])\.json</nowiki>}} * {{Gerrit-reviewer|Thcipriani|file_regexp=<nowiki>scap/scap\.cfg</nowiki>}} * {{Gerrit-reviewer|Revi|file_regexp=<nowiki>ko\.json</nowiki>}} === cloud/metricsinfra/* === * {{Gerrit-reviewer|Majavah}} === integration/* === * {{Gerrit-reviewer|Hashar}} === integration/quibble === * {{Gerrit-reviewer|awight}} * {{Gerrit-reviewer|Kosta Harlan}} === search/* === * {{Gerrit-reviewer|dcausse}} === wikimedia/discovery/* === * {{Gerrit-reviewer|bearloga}} === mediawiki/extensions/BlueSpice* === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/skins/BlueSpice* === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/tools/phan* === * {{Gerrit-reviewer|Daimona Eaytoy}} === wikimedia-cz/* === * {{Gerrit-reviewer|Urbanecm}} === mediawiki/services/wikispeech* === * {{Gerrit-reviewer|Sebastian Berlin (WMSE)}} * {{Gerrit-reviewer|Lokal Profil}} * {{Gerrit-reviewer|Karl Wettin (WMSE)}} == Listen to specific repositories == === cergen === * {{Gerrit-reviewer|Ottomata}} === integration/tox-wikimedia === * {{Gerrit-reviewer|Legoktm}} * {{Gerrit-reviewer|Volans}} === mediawiki/core === * {{Gerrit-reviewer|Aaron Schulz|file_regexp=<nowiki>^(includes/(filebackend|db|objectcache|externalstore)/|includes/libs/|maintenance/archive/[a-zA-Z]+)</nowiki>}} * {{Gerrit-reviewer|ArielGlenn|file_regexp=<nowiki>^includes/export/|^maintenance/includes/(Backup|TextPass|SevenZip)|^maintenance/(fetchText|dump)</nowiki>}} * {{Gerrit-reviewer|Hokwelum|file_regexp=<nowiki>^(includes/export/|maintenance/includes/(Backup|TextPass|SevenZip)|maintenance/(fetchText|dump))</nowiki>}} * {{Gerrit-reviewer|Catrope|file_regexp=<nowiki>includes/resourceloader|CSSMin|JavaScriptMinifier|resources/src/startup/|resources/src/mediawiki.base/|resources/src/vue/|SpecialJavaScriptTest</nowiki>}} * {{Gerrit-reviewer|cscott|file_regexp=<nowiki>[Pp]arser|virtualrest</nowiki>}} * {{Gerrit-reviewer|Cwhite|file_regexp=<nowiki>^((tests/phpunit/unit/)?includes/libs/Metrics)</nowiki>}} * {{Gerrit-reviewer|daniel|file_regexp=<nowiki>^includes/content/</nowiki>}} * {{Gerrit-reviewer|DannyS712|file_regexp=<nowiki>(ServiceWiring|MediaWikiServices|[Uu]ser|[Bb]lock|Special|api|[Aa]ction|resourceloader|resources/src/startup/|resources/src/mediawiki\.base/)</nowiki>}} * {{Gerrit-reviewer|dcausse|file_regexp=<nowiki>^includes/search/</nowiki>}} * {{Gerrit-reviewer|Huji|file_regexp=<nowiki>(Equivset|MessagesFa)</nowiki>}} * {{Gerrit-reviewer|Jackmcbarn|file_regexp=<nowiki>(?<!^includes/Template)[Pp]arse|^includes/content/|^includes/(EditPage|Linker|MagicWord|Sanitizer|api/ApiExpandTemplates).php$</nowiki>}} * {{Gerrit-reviewer|Jforrester|file_regexp=<nowiki>oojs</nowiki>}} * {{Gerrit-reviewer|Jjanes|file_regexp=<nowiki>\.sql$</nowiki>}} * {{Gerrit-reviewer|Kosta Harlan|file_regexp=<nowiki>^tests/phpunit/MediaWikiUnitTestCase.php</nowiki>}} * {{Gerrit-reviewer|Krinkle|file_regexp=<nowiki>includes/resourceloader|CSSMin|JavaScriptMinifier|resources/src/startup/|resources/src/mediawiki.base/|SpecialJavaScriptTest</nowiki>}} * {{Gerrit-reviewer|Legoktm|file_regexp=<nowiki>registration|[Cc]onfig</nowiki>}} * {{Gerrit-reviewer|Liangent|file_regexp=<nowiki>^includes/ZhConversion\.php|^maintenance/language/zhtable/|^languages/LanguageConverter\.php|^languages/classes/LanguageZh</nowiki>}} * {{Gerrit-reviewer|Majavah|file_regexp=<nowiki>includes/auth/|includes/session/</nowiki>}} * {{Gerrit-reviewer|Revi|file_regexp=<nowiki>languages/messages/MessagesKo.php</nowiki>}} * {{Gerrit-reviewer|Skizzerz|file_regexp=<nowiki>[Mm]ssql</nowiki>}} * {{Gerrit-reviewer|Tchanders|file_regexp=<nowiki>^includes/.*block</nowiki>}} * {{Gerrit-reviewer|Tpt|file_regexp=<nowiki>(DjVu|EditPage\.php)</nowiki>}} * {{Gerrit-reviewer|TTO|file_regexp=<nowiki>Import</nowiki>}} * {{Gerrit-reviewer|Urbanecm|file_regexp=<nowiki>(Messages(Cs|Sk)|includes/block/(UnblockUser|BlockUser|UserBlockCommandFactory|BlockPermissionChecker)|includes/specials/(SpecialBlock|SpecialUnblock).php)</nowiki>}} * {{Gerrit-reviewer|Zabe|file_regexp=<nowiki>^includes/.*block</nowiki>}} * {{Gerrit-reviewer|Zppix|file_regexp=<nowiki>languages/l18n/en.json</nowiki>}} === mediawiki/event-schemas === * {{Gerrit-reviewer|Ottomata}} === mediawiki/extensions/AbuseFilter === * {{Gerrit-reviewer|Daimona Eaytoy}} * {{Gerrit-reviewer|DannyS712}} === mediawiki/extensions/ActiveAbstract === * {{Gerrit-reviewer|ArielGlenn}} * {{Gerrit-reviewer|Hokwelum}} === mediawiki/extensions/AdvancedSearch === * {{Gerrit-reviewer|Andrew-WMDE}} * {{Gerrit-reviewer|Tobias Gritschacher}} * {{Gerrit-reviewer|WMDE-Fisch}} === mediawiki/extensions/AdvancedMeta === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/Annotator === * {{Gerrit-reviewer|Rjain}} === mediawiki/extensions/BlogPage === * {{Gerrit-reviewer|Lewis Cawte}} * {{Gerrit-reviewer|ultrasonicnext}} === mediawiki/extensions/CampaignEvents === * {{Gerrit-reviewer|Daimona Eaytoy}} === mediawiki/extensions/Campaigns === * {{Gerrit-reviewer|AndyRussG}} === mediawiki/extensions/Capiunto === * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/extensions/CirrusSearch === * {{Gerrit-reviewer|DCausse}} * {{Gerrit-reviewer|EBernhardson}} * {{Gerrit-reviewer|TJones}} === mediawiki/extensions/Cite === * {{Gerrit-reviewer|Huji}} * {{Gerrit-reviewer|Awight}} * {{Gerrit-reviewer|WMDE-Fisch}} === mediawiki/extensions/CentralAuth === * {{Gerrit-reviewer|DannyS712}} * {{Gerrit-reviewer|Majavah}} * {{Gerrit-reviewer|Zabe}} === mediawiki/extensions/CentralNotice === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|mepps}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|AndyRussG}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|cstone}} === mediawiki/extensions/ChessBrowser === * {{Gerrit-reviewer|DannyS712}} * {{Gerrit-reviewer|Wugapodes}} === mediawiki/extensions/CheckUser === * {{Gerrit-reviewer|Huji}} * {{Gerrit-reviewer|Tchanders|file_regexp=<nowiki>^src</nowiki>}} * {{Gerrit-reviewer|Zabe}} <!-- while I do actor migration --> * {{Gerrit-reviewer|samtar}} * {{Gerrit-reviewer|Dreamy Jazz}} === mediawiki/extensions/CodeEditor === * {{Gerrit-reviewer|TheDJ}} * {{Gerrit-reviewer|TheresNoTime}} === mediawiki/extensions/CodeReview === * {{Gerrit-reviewer|Jack Phoenix}} === mediawiki/extensions/CognitiveProcessDesigner === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/Collection === * {{Gerrit-reviewer|cscott}} === mediawiki/extensions/Collection/OfflineContentGenerator === * {{Gerrit-reviewer|cscott}} === mediawiki/extensions/Collection/OfflineContentGenerator/bundler === * {{Gerrit-reviewer|cscott}} === mediawiki/extensions/Collection/OfflineContentGenerator/latex_renderer === * {{Gerrit-reviewer|cscott}} === mediawiki/extensions/Comments === * {{Gerrit-reviewer|ultrasonicnext}} === mediawiki/extensions/CommentStreams === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/ContactPage === * {{Gerrit-reviewer|Ammarpad}} === mediawiki/extensions/CreateUserPage === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/DeletePagesForGood === * {{Gerrit-reviewer|Zoranzoki21}} === mediawiki/extensions/DisplayTitle === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/DonationInterface === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|AndyRussG}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|Wfan}} === mediawiki/extensions/DrawioEditor === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/Echo === * {{Gerrit-reviewer|Kosta Harlan}} * {{Gerrit-reviewer|samtar}} === mediawiki/extensions/EUCopyrightCampaign === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/EducationProgram === * {{Gerrit-reviewer|AndyRussG}} === mediawiki/extensions/ElectronPdfService === * {{Gerrit-reviewer|Tobias Gritschacher}} * {{Gerrit-reviewer|WMDE-Fisch}} * {{Gerrit-reviewer|Andrew-WMDE}} * {{Gerrit-reviewer|polishdeveloper}} === mediawiki/extensions/EmailAuthorization === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/EventBus === * {{Gerrit-reviewer|Ottomata}} === mediawiki/extensions/FileExporter === * {{Gerrit-reviewer|Tobias Gritschacher}} * {{Gerrit-reviewer|WMDE-Fisch}} * {{Gerrit-reviewer|Andrew-WMDE}} === mediawiki/extensions/FileImporter === * {{Gerrit-reviewer|Tobias Gritschacher}} * {{Gerrit-reviewer|WMDE-Fisch}} * {{Gerrit-reviewer|Andrew-WMDE}} * {{Gerrit-reviewer|Awight}} === mediawiki/extensions/FlaggedRevs === * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/extensions/Forms === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/Gadgets === * {{Gerrit-reviewer|DannyS712}} * {{Gerrit-reviewer|Ammarpad}} === mediawiki/extensions/Genealogy === * {{Gerrit-reviewer|Samwilson}} === mediawiki/extensions/GeoData === * {{Gerrit-reviewer|TheDJ}} === mediawiki/extensions/GettingStarted === * {{Gerrit-reviewer|phuedx}} * {{Gerrit-reviewer|swalling}} === mediawiki/extensions/GlobalBlocking === * {{Gerrit-reviewer|Majavah}} === mediawiki/extensions/GlobalPreferences === * {{Gerrit-reviewer|Samwilson}} === mediawiki/extensions/GlobalWatchlist === * {{Gerrit-reviewer|DannyS712}} === mediawiki/extensions/GraphViz === === mediawiki/extensions/GrowthExperiments === * {{Gerrit-reviewer|Kosta Harlan}} * {{Gerrit-reviewer|Gergő Tisza}} * {{Gerrit-reviewer|Sergio Gimeno}} === mediawiki/extensions/GuidedTour === * {{Gerrit-reviewer|phuedx}} * {{Gerrit-reviewer|swalling}} * {{Gerrit-reviewer|samtar}} === mediawiki/extensions/GuidedTour/guiders === * {{Gerrit-reviewer|phuedx}} * {{Gerrit-reviewer|swalling}} === mediawiki/extensions/HierarchyBuilder === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/Ids === * {{Gerrit-reviewer|Shoichi}} === mediawiki/extensions/InputBox === * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/extensions/JSBreadCrumbs === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/Kartographer === * {{Gerrit-reviewer|TheDJ}} === mediawiki/extensions/LabeledSectionTransclusion === * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/extensions/LDAPAuthentication2 === * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|Cicalese}} * {{Gerrit-reviewer|Zoranzoki21}} === mediawiki/extensions/LDAPAuthorization === * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/LDAPGroups === * {{Gerrit-reviewer|Robert Vogel}} === mediawiki/extensions/LDAPProvider === * {{Gerrit-reviewer|Robert Vogel}} === mediawiki/extensions/LDAPUserInfo === * {{Gerrit-reviewer|Robert Vogel}} === mediawiki/extensions/Lingo === * {{Gerrit-reviewer|Foxtrott}} === mediawiki/extensions/LoginNotify === * {{Gerrit-reviewer|Huji}} === mediawiki/extensions/MachineVision === * {{Gerrit-reviewer|Cparle}} === mediawiki/extensions/Math === * {{Gerrit-reviewer|Physikerwelt}} * {{Gerrit-reviewer|AndreG-P}} === mediawiki/extensions/MathSearch === * {{Gerrit-reviewer|Hcohl}} * {{Gerrit-reviewer|Physikerwelt}} * {{Gerrit-reviewer|AndreG-P}} === mediawiki/extensions/MassMessage === * {{Gerrit-reviewer|wctaiwan}} * {{Gerrit-reviewer|DannyS712}} === mediawiki/extensions/MediaUploader === * {{Gerrit-reviewer|Ostrzyciel}} === mediawiki/extensions/MediaWikiChat === * {{Gerrit-reviewer|ultrasonicnext}} === mediawiki/extensions/MediaWikiFarm === * {{Gerrit-reviewer|Seb35}} === mediawiki/extensions/MediaSearch === * {{Gerrit-reviewer|Cparle}} === mediawiki/extensions/MissedPages === * {{Gerrit-reviewer|Samwilson}} === mediawiki/extensions/MobileApp === * {{Gerrit-reviewer|dbrant}} * {{Gerrit-reviewer|Mhurd}} === mediawiki/extensions/MobileFrontend === * {{Gerrit-reviewer|polishdeveloper}} * {{Gerrit-reviewer|D3r1ck01|file_regexp=<nowiki>^tests/phpunit</nowiki>}} === mediawiki/extensions/MolHandler === * {{Gerrit-reviewer|rillke}} === mediawiki/extensions/NSFileRepo === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/OpenBadges === * {{Gerrit-reviewer|Lokal Profil}} === mediawiki/extensions/OpenIDConnect === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/PageCheckout === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/PageHeader === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/PageTriage === * {{Gerrit-reviewer|TheresNoTime}} === mediawiki/extensions/ParserFunctions === * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/extensions/PluggableAuth === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/Phonos === * {{Gerrit-reviewer|samtar}} * {{Gerrit-reviewer|Samwilson}} === mediawiki/extensions/ReadingLists === * {{Gerrit-reviewer|MSantos}} === mediawiki/extensions/RedirectManager === * {{Gerrit-reviewer|Samwilson}} === mediawiki/extensions/RevisionSlider === * {{Gerrit-reviewer|Tobias Gritschacher}} * {{Gerrit-reviewer|WMDE-Fisch}} * {{Gerrit-reviewer|Andrew-WMDE}} === mediawiki/extensions/Scribunto === * {{Gerrit-reviewer|Hoo man|file_regexp=<nowiki>^engines/LuaCommon/(lualib/mw.html.lua|HtmlLibrary.php)|^tests/engines/LuaCommon/HtmlLibraryTest.*</nowiki>}} * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/extensions/SecureAuth === * {{Gerrit-reviewer|Jayprakash12345}} === mediawiki/extensions/SecurePoll === * {{Gerrit-reviewer|Huji}} === mediawiki/extensions/SendGrid === * {{Gerrit-reviewer|D3r1ck01}} === mediawiki/extensions/SimpleSAMLphp === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/SocialProfile === * {{Gerrit-reviewer|Lewis Cawte}} === mediawiki/extensions/SpamBlacklist === * {{Gerrit-reviewer|Jackmcbarn}} * {{Gerrit-reviewer|Ammarpad}} === mediawiki/extensions/SparkPost === * {{Gerrit-reviewer|D3r1ck01}} === mediawiki/extensions/StandardDialogs === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/TemplateData === === mediawiki/extensions/TemplateSandbox === * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/extensions/TemplateWizard === * {{Gerrit-reviewer|Samwilson}} === mediawiki/extensions/TitleBlacklist === * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/extensions/TitleIcon === * {{Gerrit-reviewer|Cicalese}} === mediawiki/extensions/TwoColConflict === * {{Gerrit-reviewer|Tobias Gritschacher}} * {{Gerrit-reviewer|WMDE-Fisch}} * {{Gerrit-reviewer|Andrew-WMDE}} * {{Gerrit-reviewer|Awight}} === mediawiki/extensions/UnifiedTaskOverview === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/extensions/UploadWizard === * {{Gerrit-reviewer|Cparle}} === mediawiki/extensions/UrlShortener === * {{Gerrit-reviewer|Ammarpad}} === mediawiki/extensions/Wikibase === * {{Gerrit-reviewer|Hoo man|file_regexp=<nowiki>^client/resources/|^client/includes/DataAccess/|^(client|lib|repo)/includes/UpdateRepo.*</nowiki>}} === mediawiki/extensions/WikibaseMediaInfo === * {{Gerrit-reviewer|Cparle}} === mediawiki/extensions/WikiEditor === * {{Gerrit-reviewer|TheDJ}} * {{Gerrit-reviewer|samtar}} * {{Gerrit-reviewer|Samwilson}} * {{Gerrit-reviewer|MusikAnimal}} === mediawiki/extensions/WikiForum === * {{Gerrit-reviewer|ultrasonicnext}} === mediawiki/extensions/WikimediaApiPortalOAuth === * {{Gerrit-reviewer|Alex Paskulin}} === mediawiki/extensions/Wikisource === * {{Gerrit-reviewer|Samwilson}} === mediawiki/extensions/Wikispeech === * {{Gerrit-reviewer|Sebastian Berlin (WMSE)}} * {{Gerrit-reviewer|Lokal Profil}} * {{Gerrit-reviewer|Karl Wettin (WMSE)}} === mediawiki/extensions/WikispeechSpeechDataCollector === * {{Gerrit-reviewer|Sebastian Berlin (WMSE)}} * {{Gerrit-reviewer|Lokal Profil}} * {{Gerrit-reviewer|Karl Wettin (WMSE)}} === mediawiki/extensions/WikimediaEvents === * {{Gerrit-reviewer|Krinkle}} === mediawiki/extensions/Workflows === * {{Gerrit-reviewer|mglaser}} * {{Gerrit-reviewer|Robert Vogel}} * {{Gerrit-reviewer|ItSpiderman}} === mediawiki/libs/phpstorm-stubs === * {{Gerrit-reviewer|EBernhardson}} === mediawiki/php/luasandbox === * {{Gerrit-reviewer|Jackmcbarn}} === mediawiki/php/wikidiff2=== * {{Gerrit-reviewer|MaxSem}} * {{Gerrit-reviewer|Tobias Gritschacher}} * {{Gerrit-reviewer|WMDE-Fisch}} * {{Gerrit-reviewer|Awight}} === mediawiki/services/citoid === * {{Gerrit-reviewer|Mvolz}} === mediawiki/services/citoid/deploy === * {{Gerrit-reviewer|Mvolz}} === mediawiki/services/mathoid === * {{Gerrit-reviewer|Physikerwelt}} === mediawiki/services/mobileapps === * {{Gerrit-reviewer|Jforrester}} * {{Gerrit-reviewer|MSantos}} <!-- Don't auto-add Jon here - manually add him to reviews as needed --> === mediawiki/services/ocg-collection === * {{Gerrit-reviewer|cscott}} === mediawiki/services/trending-edits=== * {{Gerrit-reviewer|Jdlrobson}} === mediawiki/services/wikifeeds === * {{Gerrit-reviewer|mbsantos}} === mediawiki/services/eventstreams=== * {{Gerrit-reviewer|Ottomata}} === mediawiki/services/eventstreams/deploy === * {{Gerrit-reviewer|Ottomata}} === mediawiki/skins === * {{Gerrit-reviewer|Jack Phoenix}} * {{Gerrit-reviewer|Jdlrobson}} === mediawiki/skins/BlueSpiceSkin === * {{Gerrit-reviewer|Dvogel hallowelt}} === mediawiki/skins/EUCopyrightCampaignSkin === * {{Gerrit-reviewer|Cicalese}} === mediawiki/skins/Metrolook === * {{Gerrit-reviewer|Paladox}} === mediawiki/skins/MinervaNeue === * {{Gerrit-reviewer|polishdeveloper}} === mediawiki/skins/Vector === * <!-- {{Gerrit-reviewer|jdlrobson}} please create a phab ticket if you need my review. --> === mediawiki/skins/WikimediaApiPortal === * {{Gerrit-reviewer|Alex Paskulin}} === mediawiki/ruby/api === * {{Gerrit-reviewer|Dduvall}} === mediawiki/selenium === * {{Gerrit-reviewer|Dduvall}} === mediawiki/tools/cli=== * {{Gerrit-reviewer|Kosta Harlan}} === mediawiki/tools/codesniffer=== * {{Gerrit-reviewer|DannyS712}} === mediawiki/tools/release === * {{Gerrit-reviewer|Florianschmidtwelzow|file_regexp=^make-deploy-notes}} === mediawiki/vagrant === * {{Gerrit-reviewer|Dduvall}} * {{Gerrit-reviewer|ejegg|file_regexp=<nowiki>^puppet/modules/(crm|payments|smashpig)</nowiki>}} * {{Gerrit-reviewer|XenoRyet|file_regexp=<nowiki>^puppet/modules/(crm|payments|smashpig)</nowiki>}} * {{Gerrit-reviewer|jgleeson|file_regexp=<nowiki>^puppet/modules/(crm|payments|smashpig)</nowiki>}} * {{Gerrit-reviewer|cstone|file_regexp=<nowiki>^puppet/modules/(crm|payments|smashpig)</nowiki>}} * {{Gerrit-reviewer|ArielGlenn|file_regexp=<nowiki>^puppet/modules/dumps</nowiki>}} * {{Gerrit-reviewer|Hokwelum|file_regexp=<nowiki>^puppet/modules/dumps</nowiki>}} === wikimedia/communications/WMBlog === * {{Gerrit-reviewer|HaeB}} === wikimedia/communications/WP-Victor === * {{Gerrit-reviewer|HaeB}} === wikimedia/discovery/relevanceForge === * {{Gerrit-reviewer|dcausse}} === wikimedia/discovery/discernatron === * {{Gerrit-reviewer|EBernhardson}} === wikimedia/fundraising/crm === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|Eileen}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === wikimedia/fundraising/crm/civicrm === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|Eileen}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === wikimedia/fundraising/crm/drupal === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|Eileen}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === wikimedia/fundraising/dash === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === wikimedia/fundraising/FRUEC === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|AndyRussG}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === wikimedia/fundraising/php-queue === * {{Gerrit-reviewer|cwdent}} * {{Gerrit-reviewer|ejegg}} === wikimedia/fundraising/process-control === * {{Gerrit-reviewer|cwdent}} * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === wikimedia/fundraising/SmashPig === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === wikimedia/fundraising/stats === * {{Gerrit-reviewer|ejegg}} === wikimedia/fundraising/tools === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|AndyRussG}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === wikimedia/fundraising/tools/DjangoBannerStats === * {{Gerrit-reviewer|ejegg}} * {{Gerrit-reviewer|XenoRyet}} * {{Gerrit-reviewer|jgleeson}} * {{Gerrit-reviewer|AndyRussG}} * {{Gerrit-reviewer|cstone}} * {{Gerrit-reviewer|damilare}} * {{Gerrit-reviewer|Wfan}} === operations/cookbooks === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/debs/wmf-certificates === * {{Gerrit-reviewer|Jbond}} === operations/debs/debdeploy === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/debs/pybal === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Giuseppe Lavagetto}} * {{Gerrit-reviewer|Vgutierrez}} * {{Gerrit-reviewer|Alexandros Kosiaris}} === operations/deployment-charts === * {{Gerrit-reviewer|bd808|file_regexp=<nowiki>^(helmfile\.d/services|charts)/toolhub</nowiki>}} === operations/docker-images/docker-pkg === * {{Gerrit-reviewer|Giuseppe Lavagetto}} * {{Gerrit-reviewer|Alexandros Kosiaris}} * {{Gerrit-reviewer|Hashar}} === operations/homer/public === *{{Gerrit-reviewer|Ayounsi}} *{{Gerrit-reviewer|Cathal Mooney}} *{{Gerrit-reviewer|Jbond}} === operations/puppet === * {{Gerrit-reviewer|bd808|file_regexp=<nowiki>^modules/toollabs/|^hieradata/labs/tools/</nowiki>}} * {{Gerrit-reviewer|Dzahn|file_regexp=<nowiki>^modules/(gerrit|phabricator|bugzilla_static|wikistats|planet)/|^module/(profile|role)/manifests/(gerrit|phabricator|bugzilla_static|planet)</nowiki>}} * {{Gerrit-reviewer|Filippo Giunchedi|file_regexp=<nowiki>^.*icinga.*</nowiki>}} * {{Gerrit-reviewer|bblack|file_regexp=<nowiki>^modules/(authdns|pybal|lvs|nginx|tlsproxy|varnish|sslcert)/|^modules/role/manifests/(cache|lvs)/|^manifests/role/(authdns|lvs|tlsproxy)\.pp|^files/ssl/|^templates/varnish/</nowiki>}} * {{Gerrit-reviewer|Krenair|file_regexp=<nowiki>^modules/(mediawiki|admin|openstack)/</nowiki>}} * {{Gerrit-reviewer|Volans|file_regexp=<nowiki>(\.py(\.erb)?$|cumin|failoid|debmonitor|spicerack|cookbook|netbox|homer|puppetboard|reimage)</nowiki>}} * {{Gerrit-reviewer|Giuseppe Lavagetto|file_regexp=<nowiki>^hieradata/regex.yaml|^modules/(mediawiki|service|httpd|php|etcd)</nowiki>}} * {{Gerrit-reviewer|Muehlenhoff|file_regexp=<nowiki>^modules/admin/</nowiki>}} * {{Gerrit-reviewer|Jbond|file_regexp=<nowiki>modules/admin|apereo_cas|apt|wmflib|modules/base|cumin|cfssl|debian|debdeploy|debmonitor|kerberos|yubiauth|puppet|pki|ssh|sudo|sslcert|sysctl|modules/systemd?|ulogd|ferm|modules/security|standard|wikidough|\.rb$|(Gem|Rake)file|CONTRIBUTORS|^vendor_modules/</nowiki>}} * {{Gerrit-reviewer|Alexandros Kosiaris|file_regexp=<nowiki>^modules/(calico|docker|k8s|profile/kubernetes|etherpad|ferm|ganeti|lvs|network|ores|otrs|package_builder|service)</nowiki>}} * {{Gerrit-reviewer|paladox|file_regexp=<nowiki>^modules/(gerrit|phabricator)</nowiki>}} * {{Gerrit-reviewer|ArielGlenn|file_regexp=<nowiki>^modules/(dumps|snapshot)/|^modules/(profile|role)/manifests/dumps/</nowiki>}} * {{Gerrit-reviewer|Hokwelum|file_regexp=<nowiki>^modules/(dumps|snapshot)/|^modules/(profile|role)/manifests/dumps/</nowiki>}} * {{Gerrit-reviewer|Arturo Borrero Gonzalez|file_regexp=<nowiki>^modules/(toollabs|openstack)/|^hieradata/labs/tools/|^modules/(profile|role)/*/(toolforge|openstack|toollabs|labs)|modules/base/*/standard_packages/</nowiki>}} * {{Gerrit-reviewer|Ssingh|file_regexp=<nowiki>^modules/(auditd|dnsdist|dnsrecursor)|^modules/(profile|role)/*/(wikidough|durum)</nowiki>}} * {{Gerrit-reviewer|Legoktm|file_regexp=<nowiki>^modules/(extdist|codesearch|libraryupgrader|mailman|mailman3)/</nowiki>}} * {{Gerrit-reviewer|Cwhite|file_regexp=<nowiki>(opensearch|logstash)</nowiki>}} === operations/puppet/cdh === * {{Gerrit-reviewer|Ottomata}} === operations/puppet/cdh4 === * {{Gerrit-reviewer|Ottomata}} === operations/puppet/kafka === * {{Gerrit-reviewer|Ottomata}} === operations/puppet/zookeeper === * {{Gerrit-reviewer|Ottomata}} === operations/mediawiki-config === * {{Gerrit-reviewer|Hoo man|file_regexp=<nowiki>^wmf-config/(abusefilter|Wikibase.*)\.php</nowiki>}} === operations/software === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Alexandros Kosiaris}} === operations/software/conftool === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Giuseppe Lavagetto}} * {{Gerrit-reviewer|Alexandros Kosiaris}} * {{Gerrit-reviewer|CDanis}} === operations/software/cumin === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/software/debmonitor === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/software/debmonitor/deploy === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/software/ecs === * {{Gerrit-reviewer|Cwhite}} === operations/software/external-monitoring === * {{Gerrit-reviewer|Volans}} === operations/software/homer === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Ayounsi}} * {{Gerrit-reviewer|Cathal Mooney}} * {{Gerrit-reviewer|Jbond}} === operations/software/keyholder === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Alexandros Kosiaris}} === operations/software/netbox === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Alexandros Kosiaris}} * {{Gerrit-reviewer|Jbond}} === operations/software/netbox-deploy === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/software/netbox-extras === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/software/pywmflib === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/software/spicerack === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Jbond}} === operations/software/tools-webservice === * {{Gerrit-reviewer|Zhuyifei1999}} === operations/software/varnish/varnishkafka === * {{Gerrit-reviewer|Elukey}} * {{Gerrit-reviewer|Ottomata}} === operations/switchdc === * {{Gerrit-reviewer|Volans}} * {{Gerrit-reviewer|Alexandros Kosiaris}} === labs/codesearch === * {{Gerrit-reviewer|Legoktm}} * {{Gerrit-reviewer|D3r1ck01}} === labs/icinga2 === * {{Gerrit-reviewer|awight}} === labs/libraryupgrader === * {{Gerrit-reviewer|Legoktm}} === labs/toollabs === * {{Gerrit-reviewer|bd808}} * {{Gerrit-reviewer|Zhuyifei1999}} === labs/tools/awmd-stats === * {{Gerrit-reviewer|African Hope}} === labs/tools/Commons-twitter-bot === * {{Gerrit-reviewer|ArielGlenn}} * {{Gerrit-reviewer|Dereckson}} * {{Gerrit-reviewer|Rosalieper}} === labs/tools/extjsonuploader === * {{Gerrit-reviewer|Samwilson}} === labs/tools/watch-translations === * {{Gerrit-reviewer|Urbanecm}} === labs/tools/wikibugs2 === * {{Gerrit-reviewer|Merlijn van Deen}} * {{Gerrit-reviewer|Merlijn van Deen - alternative}} === labs/tools/wikisource-ocr === * {{Gerrit-reviewer|Samwilson}} === labs/tools/map-of-monuments === * {{Gerrit-reviewer|Urbanecm}} === labs/tools/massmailer === * {{Gerrit-reviewer|Urbanecm}} === labs/tools/wikinity === * {{Gerrit-reviewer|Urbanecm}} === labs/tools/weapon-of-mass-description === * {{Gerrit-reviewer|Urbanecm}} === labs/tools/commons-mass-description === * {{Gerrit-reviewer|Urbanecm}} === labs/tools/harvesting-data-refinery === * {{Gerrit-reviewer|Urbanecm}} === labs/tools/heritage === * {{Gerrit-reviewer|Jean-Frédéric}} * {{Gerrit-reviewer|Multichill}} * {{Gerrit-reviewer|Lokal Profil}} === labs/tools/sonarqubebot === * {{Gerrit-reviewer|Kosta Harlan}} === labs/tools/urbanecmbot === * {{Gerrit-reviewer|Urbanecm}} === labs/tools/train-blockers === * {{Gerrit-reviewer|Majavah}} === labs/tools/github-pr-closer === * {{Gerrit-reviewer|Majavah}} === labs/tools/majavah-bot === * {{Gerrit-reviewer|Majavah}} === maps/kartotherian/package === * {{Gerrit-reviewer|MSantos}} === maps/kartotherian/deploy === * {{Gerrit-reviewer|MSantos}} === maps/tilerator/package === * {{Gerrit-reviewer|MSantos}} === maps/tilerator/deploy === * {{Gerrit-reviewer|MSantos}} === sink_nova_ldap === * {{Gerrit-reviewer|Andrew Bogott}} === sink_nova_fixed_multi === * {{Gerrit-reviewer|Andrew Bogott}} === apps/android/java-mwapi === * {{Gerrit-reviewer|dbrant}} === apps/android/wikipedia === * {{Gerrit-reviewer|Brion VIBBER}} * {{Gerrit-reviewer|dbrant}} * {{Gerrit-reviewer|Sharvaniharan}} * {{Gerrit-reviewer|Cooltey}} === pywikibot/core === * {{Gerrit-reviewer|D3r1ck01|file_regexp=<nowiki>^scripts</nowiki>}} === pywikibot/bots/FLOSSbot === * {{Gerrit-reviewer|Dachary}} === pywikibot/spelling === * {{Gerrit-reviewer|Ladsgroup}} === pywikibot/i18n === * {{Gerrit-reviewer|Zoranzoki21}} === pywikibot/compat === * {{Gerrit-reviewer|John Vandenberg}} === analytics/aqs === * {{Gerrit-reviewer|joal}} === analytics/gobblin-wmf === * {{Gerrit-reviewer|joal}} === analytics/quarry/web === * {{Gerrit-reviewer|zhuyifei1999}} === analytics/refinery === * {{Gerrit-reviewer|ottomata}} * {{Gerrit-reviewer|joal}} === analytics/refinery/source === * {{Gerrit-reviewer|ottomata}} * {{Gerrit-reviewer|joal}} === analytics/wikihadoop === * {{Gerrit-reviewer|joal}} === analytics/limn-mobile-data === * {{Gerrit-reviewer|milimetric}} * {{Gerrit-reviewer|Nuria}} * {{Gerrit-reviewer|YuviPanda}} === wikidata/query/rdf === * {{Gerrit-reviewer|DCausse}} === wikidata/query/deploy === * {{Gerrit-reviewer|DCausse}} * {{Gerrit-reviewer|BKing}} === wikidata/query/gui === === wikidata/query/gui-deploy === === wikidata/query/flink-swift-plugin === * {{Gerrit-reviewer|DCausse}} * {{Gerrit-reviewer|BKing}} === wikimedia/textcat === * {{Gerrit-reviewer|TJones}} === integration/commit-message-validator === * {{Gerrit-reviewer|Legoktm}} === wikimedia/portals === * {{Gerrit-reviewer|Jdrewniak}} * {{Gerrit-reviewer|Mxn}} === wikimedia-cz/tracker === * {{Gerrit-reviewer|Takidelfin}} === labs/tools/stewardbots === * {{Gerrit-reviewer|Revi}} * {{Gerrit-reviewer|Majavah}} === labs/tools/ZppixBot === *{{Gerrit-reviewer|MacFan4000}} === eventlogging === * {{Gerrit-reviewer|Ottomata}} === wmf-utils === * {{Gerrit-reviewer|fgiunchedi}} === wikimedia/security/tooling === * {{Gerrit-reviewer|SBassett}} === research/mwaddlink === * {{Gerrit-reviewer|Kosta Harlan}} === wikimedia/toolhub === * {{Gerrit-reviewer|bd808}} * {{Gerrit-reviewer|raymond-ndibe}} * {{Gerrit-reviewer|sstefanova}} === design/codex === * {{Gerrit-reviewer|Catrope}} * {{Gerrit-reviewer|DannyS712}} * {{Gerrit-reviewer|Volker-E}} * {{Gerrit-reviewer|AnneT}} === wikimedia/developer-portal === * {{Gerrit-reviewer|bd808}} * {{Gerrit-reviewer|Alex Paskulin}} * {{Gerrit-reviewer|aklapper}} * {{Gerrit-reviewer|triciaburmeister}} * {{Gerrit-reviewer|KBach}} === mediawiki/extensions/Wikistories === * {{Gerrit-reviewer|Sbisson}} * {{Gerrit-reviewer|Huei Tan}} * {{Gerrit-reviewer|Eamedina}} 4gh8jfqfxbmxwdi3ygymcwdt2vjx48u Extension:OfflineImportLexicon 102 107800 5386568 4305771 2022-07-28T15:32:41Z MStyles (WMF) 17237175 archived wikitext text/x-wiki {{Archived extension|4305771|task=T313860}} qj6163vd6u9k9gj3hbbqwhmcs78sr4c Manual:Installation guide/da 100 108295 5386643 5381076 2022-07-28T17:14:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/da]] h1aaflpruagsumk10wl7z2psvvyaks8 Manual:Installing MediaWiki/da 100 109126 5387488 5384962 2022-07-28T22:45:16Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">MediaWiki kan være svær at installere for den gennemsnitlige computerbruger, der ikke har erfaring med Apache, PHP og MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Download MediaWiki-softwaren == <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">Download-filerne er i <code>.tar.gz</code> format og skal udpakkes før brug.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span class="mw-translate-fuzzy">Dette kan gøres lokalt (og så oploades via FTP) eller direkte på serveren.</span> Dette gøres normalt med software såsom [https://www.7-zip.org/ 7-Zip] (gratis), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] eller [https://www.izarc.org/ IZArc] (gratis) på Windows. På Linux og Mac OS X kan du udpakke filen med kommandoen: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div class="mw-translate-fuzzy"> == Oploadede filer == </div> <div class="mw-translate-fuzzy"> Hvis du ikke allerede har uploadet filerne til din webserver, så gør det nu. </div> Overføre filerne til din webservers web-mappe enten ved at: # direkte kopiering af den udpakkede mappe eller <div class="mw-translate-fuzzy"> # ved brug af en FTP client såsom [https://filezilla-project.org/ FileZilla] (Open Source Software, Windows, OSX og Linux) eller [https://cyberduck.io/ Cyberduck] (OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div class="mw-translate-fuzzy"> '''Sørg for, at "ændre filnavne til små bogstaver"-indstillingen for upload er deaktiveret.''' </div> <span class="mw-translate-fuzzy">Hvis du har installeret Apache er den korrekte mappe specificeret i din <code>httpd.conf</code> fil (den normale <code><apache-folder>/htdocs</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Hvis du bruger Linux eller Unix server kan du kopiere filerne til enhver mappe på serveren og så lave et [[Wikipedia:Symbolic link|symbolsk link]] til mappen fra serverens web-mappe.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Omdøb den oploadede mappe til et hvilket som helst navn, som du vil have i URL'en. <span class="mw-translate-fuzzy">Hvis webserveren for eks. kører som <code>http://localhost</code> betyder omdøbning til <code>/w/</code> mappen, at adgang wikien fås på <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span class="mw-translate-fuzzy">''Brug ikke <code>/wiki/</code> hvis du vil bruge det som [[Manual:Short URL|Short URL]]/[[Manual:Short URL/da|da]].''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Opret en database == </div> <div class="mw-translate-fuzzy"> MediaWiki spørger dig om database- og brugernavn og forsøger at oprette dem, hvis de ikke allerede findes. </div> <div class="mw-translate-fuzzy"> Hvis du allerede har en database og kender rod-password til den, kan MediaWiki installationsscriptet oprette en ny database til dig. </div> <div class="mw-translate-fuzzy"> Hvis du ikke kender rod-passwordet, for eksempel hvis du er på en hosted server, bliver du nødt til at oprette en ny database nu. </div> <span class="mw-translate-fuzzy">P.t. kan du bruge SQLite, MariaDB/MySQL eller Postgres til at gemme det faktiske indhold af din wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">På installationssiden er du nød til at vælge et database-navn (hvad som helst) og SQLite database-mappen.</span> Til database-mappe vil installations-programmet forsøge at anvende en undermappe uden for dokumentroden og om nødvendig oprette den. Hvis mappen ikke er sikker (for eks. web-læsbar), skift navnet manuelt for at undgå den bliver tilgængelig for alle på internettet. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Se den tilhørende dokumentation.</span> <span class="mw-translate-fuzzy">Alternativt kan du kontakte din vært udbyder, for at få dem til at oprette en konto til dig.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Hvis din database ikke kører på samme server som din webserver, skal du give den rette web-server værtnavn - eksempelvis mediawiki.example.com - som følger: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Hvis du bruger Postgres, skal du enten have en database og bruger oprettet til dig, eller blot levere navnet på en Postgres bruger med 'superbruger'-privilegier til konfigurations-skemaet.</span> <span class="mw-translate-fuzzy">Dette er ofte database-brugeren med navnet '''postgres'''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki eller som superbruger (standandnavn: postgres) udfør følgende forespørgsler i database-prompten: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div class="mw-translate-fuzzy"> Når alle ovenstående trin er fuldført, kan du fuldføre installationen gennem en webbrowser ved at gå til index.php URI i din browser - læs instruktionen nævnt i {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Opdater! == Efter installationen skal du sørge for at holde dig ajour med opdateringer, for at holde din server sikker! {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|Tilmelding til mail-listen med annoncering af udgivelser]].</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=Ved oprettelse af rod-kontoen, brug en adgangskode, som du er i stand til at huske.}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Se også == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] fo3vt1shc2qquvpf7i4fqsdfgf48qm8 Groups/pl 0 112375 5387360 4924007 2022-07-28T22:11:30Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] Grupy '''MediaWiki''' pozwalają na organizowanie zadań społeczności open source według poszczególnych tematów oraz stref geograficznych. Są to [[meta:Wikimedia User Groups/pl|Grupy Użytkowników Wikimedia]], które dotyczą koordynacji na temat MediaWiki. Poszerzają one możliwości udziału [[wmf:Main|Fundacji Wikimedia]] w [[Events|wydarzeniach]], [[Volunteer coordination and outreach/Training materials|szkoleniach]], promocji i innych aktywnościach dotyczących spraw technicznych Wikipedii, ruchu Wikimedia oraz oprogramowania MediaWiki. <span class="mw-translate-fuzzy">Grupy użytkowników MediaWiki są otwarte dla ludzi z [[How to contribute/pl|różnymi specjalnościami]] oraz poziomem wiedzy. Im bardziej zróżnicowane tym lepiej.</span> Osoby niezaznajomione ze sprawami technicznymi, ale chcący mieć swój udział lub się czegoś nauczyć są także mile widziani! Wszystkie grupy zobowiązują się do [[wmf:Friendly space policy|Polityki przyjaznego miejsca]]. Grupy MediaWiki mogą [[Groups/Wikimedia support|poprosić o pomoc]] ze strony Fundacji Wikimedia na różny sposób. == Grupy tematyczne == Tematyczne grupy użytkowników MediaWiki współpracują z logicznymi odpowiednikami w szerszej społeczności [[w:pl:FLOSS|Wolnego Oprogramowania]]. Są one grupami globalnymi, współpracującymi online. * Są w kontakcie ze społecznościami z tego samego zakresu. * Uczestniczą w wydarzeniach dotyczących tego samego tematu. * Promują powiązane szkolenia i zasięg działania. * Pomagają wprowadzać dokumentację na wikimedia.org. * Współpracują z powiązanymi grupami twórców. * Ewentualnie niektóre z nich spotykają się na [//wikimania.wikimedia.org/ Wikimanii]. == Grupy lokalne == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Lokalne grupy użytkowników MediaWiki współpracują z [[meta:Wikimedia chapters|chapterami Wikimedia]], Zobacz też [[w:pl:Wikipedia:Zloty|spotkania Wikipedii]] oraz inne lokalne społeczności powiązane z Wikimedią, wolnym oprogramowaniem, wolną kulturą... Polegają one na działaniach wymagających bezpośredniego kontaktu z uczestnikami: * Organizowanie wydarzeń lokalnych: zloty, szkolenia, hackfests... These events adhere to the [[wmf:Friendly space policy|WMF Friendly space policy]]. * Uczestnictwo w wydarzeniach organizowanych na ich obszarze. * Distribution of merchandising. * Zachęcanie lokalnych współpracowników do czynności globalnych dla MediaWiki oraz Wikimedii. <div class="mw-translate-fuzzy"> Także dla grup nie mówiących po angielsku: * Tłumaczenie dokumentacji i oprogramowania poprzez [[translatewiki.net]]. </div> Lokalne grupy muszą być naprawdę lokalne. Lokalne grupy muszą być naprawdę lokalne. Dokładnie określone terytorium np. Recife, Monachium lub Saint Petersburg są lepsze niż określenia: Brazylia, Niemcy lub Rosja ze względu na ścisły zasięg działania. <span class="mw-translate-fuzzy">Jeśli zauważysz kanał dla regionalnej koordynacji, rozważ [[Mailing lists/Regional/pl|regionalną listę dyskusyjną]].</span> == Tworzenie grupy == Aby zaproponować grupę, nie musisz mieć jeszcze członków. Jednak, aby została zatwierdzona, musisz mieć minimum trzech współpracowników. <span lang="en" dir="ltr" class="mw-content-ltr">To get it approved you must have at least three contributors.</span> Zobacz [[Groups/Proposals|propozycje]], aby uzyskać więcej szczegółów na temat tworzenia własnej grupy użytkowników MediaWiki. [[Category:MediaWiki Communication{{#translation:}}]] qje07izlgb0gs85ib83l9v0fqhwxg5c 5387380 5387360 2022-07-28T22:12:58Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] Grupy '''MediaWiki''' pozwalają na organizowanie zadań społeczności open source według poszczególnych tematów oraz stref geograficznych. Są to [[meta:Wikimedia User Groups/pl|Grupy Użytkowników Wikimedia]], które dotyczą koordynacji na temat MediaWiki. Poszerzają one możliwości udziału [[wmf:Main|Fundacji Wikimedia]] w [[Events|wydarzeniach]], [[Volunteer coordination and outreach/Training materials|szkoleniach]], promocji i innych aktywnościach dotyczących spraw technicznych Wikipedii, ruchu Wikimedia oraz oprogramowania MediaWiki. Grupy użytkowników MediaWiki są otwarte dla ludzi z [[Special:MyLanguage/How to contribute|różnymi specjalnościami]] oraz poziomem wiedzy. Im bardziej zróżnicowane tym lepiej. Osoby niezaznajomione ze sprawami technicznymi, ale chcący mieć swój udział lub się czegoś nauczyć są także mile widziani! Wszystkie grupy zobowiązują się do [[wmf:Friendly space policy|Polityki przyjaznego miejsca]]. Grupy MediaWiki mogą [[Groups/Wikimedia support|poprosić o pomoc]] ze strony Fundacji Wikimedia na różny sposób. == Grupy tematyczne == Tematyczne grupy użytkowników MediaWiki współpracują z logicznymi odpowiednikami w szerszej społeczności [[w:pl:FLOSS|Wolnego Oprogramowania]]. Są one grupami globalnymi, współpracującymi online. * Są w kontakcie ze społecznościami z tego samego zakresu. * Uczestniczą w wydarzeniach dotyczących tego samego tematu. * Promują powiązane szkolenia i zasięg działania. * Pomagają wprowadzać dokumentację na wikimedia.org. * Współpracują z powiązanymi grupami twórców. * Ewentualnie niektóre z nich spotykają się na [//wikimania.wikimedia.org/ Wikimanii]. == Grupy lokalne == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Lokalne grupy użytkowników MediaWiki współpracują z [[meta:Wikimedia chapters|chapterami Wikimedia]], Zobacz też [[w:pl:Wikipedia:Zloty|spotkania Wikipedii]] oraz inne lokalne społeczności powiązane z Wikimedią, wolnym oprogramowaniem, wolną kulturą... Polegają one na działaniach wymagających bezpośredniego kontaktu z uczestnikami: * Organizowanie wydarzeń lokalnych: zloty, szkolenia, hackfests... These events adhere to the [[wmf:Friendly space policy|WMF Friendly space policy]]. * Uczestnictwo w wydarzeniach organizowanych na ich obszarze. * Distribution of merchandising. * Zachęcanie lokalnych współpracowników do czynności globalnych dla MediaWiki oraz Wikimedii. <div class="mw-translate-fuzzy"> Także dla grup nie mówiących po angielsku: * Tłumaczenie dokumentacji i oprogramowania poprzez [[translatewiki.net]]. </div> Lokalne grupy muszą być naprawdę lokalne. Lokalne grupy muszą być naprawdę lokalne. Dokładnie określone terytorium np. Recife, Monachium lub Saint Petersburg są lepsze niż określenia: Brazylia, Niemcy lub Rosja ze względu na ścisły zasięg działania. <span class="mw-translate-fuzzy">Jeśli zauważysz kanał dla regionalnej koordynacji, rozważ [[Mailing lists/Regional/pl|regionalną listę dyskusyjną]].</span> == Tworzenie grupy == Aby zaproponować grupę, nie musisz mieć jeszcze członków. Jednak, aby została zatwierdzona, musisz mieć minimum trzech współpracowników. <span lang="en" dir="ltr" class="mw-content-ltr">To get it approved you must have at least three contributors.</span> Zobacz [[Groups/Proposals|propozycje]], aby uzyskać więcej szczegółów na temat tworzenia własnej grupy użytkowników MediaWiki. [[Category:MediaWiki Communication{{#translation:}}]] hpjy40v4669n1zzevyvvjrnw61jeak5 5387411 5387380 2022-07-28T22:15:24Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] Grupy '''MediaWiki''' pozwalają na organizowanie zadań społeczności open source według poszczególnych tematów oraz stref geograficznych. Są to [[meta:Wikimedia User Groups/pl|Grupy Użytkowników Wikimedia]], które dotyczą koordynacji na temat MediaWiki. Poszerzają one możliwości udziału [[wmf:Main|Fundacji Wikimedia]] w [[Events|wydarzeniach]], [[Volunteer coordination and outreach/Training materials|szkoleniach]], promocji i innych aktywnościach dotyczących spraw technicznych Wikipedii, ruchu Wikimedia oraz oprogramowania MediaWiki. Grupy użytkowników MediaWiki są otwarte dla ludzi z [[Special:MyLanguage/How to contribute|różnymi specjalnościami]] oraz poziomem wiedzy. Im bardziej zróżnicowane tym lepiej. Osoby niezaznajomione ze sprawami technicznymi, ale chcący mieć swój udział lub się czegoś nauczyć są także mile widziani! Wszystkie grupy zobowiązują się do [[wmf:Friendly space policy|Polityki przyjaznego miejsca]]. Grupy MediaWiki mogą [[Groups/Wikimedia support|poprosić o pomoc]] ze strony Fundacji Wikimedia na różny sposób. == Grupy tematyczne == Tematyczne grupy użytkowników MediaWiki współpracują z logicznymi odpowiednikami w szerszej społeczności [[w:pl:FLOSS|Wolnego Oprogramowania]]. Są one grupami globalnymi, współpracującymi online. * Są w kontakcie ze społecznościami z tego samego zakresu. * Uczestniczą w wydarzeniach dotyczących tego samego tematu. * Promują powiązane szkolenia i zasięg działania. * Pomagają wprowadzać dokumentację na wikimedia.org. * Współpracują z powiązanymi grupami twórców. * Ewentualnie niektóre z nich spotykają się na [//wikimania.wikimedia.org/ Wikimanii]. == Grupy lokalne == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Lokalne grupy użytkowników MediaWiki współpracują z [[meta:Wikimedia chapters|chapterami Wikimedia]], Zobacz też [[w:pl:Wikipedia:Zloty|spotkania Wikipedii]] oraz inne lokalne społeczności powiązane z Wikimedią, wolnym oprogramowaniem, wolną kulturą... Polegają one na działaniach wymagających bezpośredniego kontaktu z uczestnikami: * Organizowanie wydarzeń lokalnych: zloty, szkolenia, hackfests... These events adhere to the [[wmf:Friendly space policy|WMF Friendly space policy]]. * Uczestnictwo w wydarzeniach organizowanych na ich obszarze. * Distribution of merchandising. * Zachęcanie lokalnych współpracowników do czynności globalnych dla MediaWiki oraz Wikimedii. Także dla grup nie mówiących po angielsku: * Tłumaczenie dokumentacji i oprogramowania poprzez [[Special:MyLanguage/translatewiki.net|translatewiki.net]]. Lokalne grupy muszą być naprawdę lokalne. Lokalne grupy muszą być naprawdę lokalne. Dokładnie określone terytorium np. Recife, Monachium lub Saint Petersburg są lepsze niż określenia: Brazylia, Niemcy lub Rosja ze względu na ścisły zasięg działania. <span class="mw-translate-fuzzy">Jeśli zauważysz kanał dla regionalnej koordynacji, rozważ [[Mailing lists/Regional/pl|regionalną listę dyskusyjną]].</span> == Tworzenie grupy == Aby zaproponować grupę, nie musisz mieć jeszcze członków. Jednak, aby została zatwierdzona, musisz mieć minimum trzech współpracowników. <span lang="en" dir="ltr" class="mw-content-ltr">To get it approved you must have at least three contributors.</span> Zobacz [[Groups/Proposals|propozycje]], aby uzyskać więcej szczegółów na temat tworzenia własnej grupy użytkowników MediaWiki. [[Category:MediaWiki Communication{{#translation:}}]] aj43ousfpp687bz67apznd11jrag4ru Manual:Combating spam/de 100 113013 5387470 5255692 2022-07-28T22:40:13Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Wie alle aktuellen dynamischen Websites sind Wikis ein häufiges Ziel für Spammer, die Produkte oder Websites bewerben möchten. MediaWiki bietet eine Reihe von Funktionen zur [[Special:MyLanguage/Manual:Combating vandalism|Bekämpfung von Vandalismus im Allgemeinen]]. Auf dieser Seite beschäftigen wir uns speziell mit [[m:Wiki spam|Wiki-Spam]]. ==Überblick== Übliche Tools zur Bekämpfung von Wiki-Spam fallen normalerweise in folgende Kategorien: * Erfordern einer Anmeldung und/oder eines CAPTCHA für bestimmte Vorgänge, z. B. Bearbeitungen, Hinzufügen externer Links oder Erstellen neuer Benutzer * Blockieren von Bearbeitungen von bekannten IP-Adressen auf der schwarzen Liste oder IPs, auf denen Proxys ausgeführt werden * Blockieren von Bearbeitungen, die bestimmte unerwünschte Schlüsselwörter oder externe Links hinzufügen * Blockieren von bestimmten Benutzernamen und Seitentiteln, die häufig von Spambots verwendet werden * Blockieren von Bearbeitungen durch neue oder anonyme Benutzer für bestimmte, häufig anvisierte Seiten * Whitelisting von bekannten Redakteuren (wie Admins, regelmäßige Mitwirkende) und Einschränkungen für neue oder anonyme Benutzer * Bereinigungsskripte oder Massenlöschung ({{ll|Extension:Nuke}}) vorhandener Posts von kürzlich gesperrten Spambots Normalerweise wird eine Kombination verschiedener Methoden verwendet, um die Anzahl der Spam-, Roboter- und Open-Proxy-Bearbeitungen so gering wie möglich zu halten und gleichzeitig die Anzahl der Störungen zu begrenzen, die für rechtmäßige Benutzer der Website verursacht werden. Beachte, dass viele dieser Funktionen standardmäßig nicht aktiviert sind. Wenn du eine MediaWiki-Installation auf deinem Server/Host ausführst, kannst nur du die erforderlichen Konfigurationsänderungen vornehmen! Bitte deine Benutzer auf jeden Fall, zu helfen, [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|auf Wiki-Spam zu achten]] (und tu dies selbst). Es hilft, die Messlatte etwas höher zu legen. Du solltest jedoch auch beachten, dass keine dieser Lösungen als vollständig Spam-sicher angesehen werden kann. Das regelmäßige Überprüfen von "{{int|recentchanges}}" ([[Special:RecentChanges]]) ist eine effektive Maßnahme. == Schnellste Lösungen zum Ausprobieren == Spam zu bekämpfen sollte nicht zu schwer sein. Wenn Du Spam schnell und drastisch reduzieren möchtest, versuche zunächst diese Schritte. * Installiere die [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]]-Erweiterung, um bekannte Spammer-IPs zu blockieren. * Installiere und richte grundlegende Antivandalismus-Erweiterungen ein (bereits in den [[Special:MyLanguage/Download|letzten Versionen]] eingebaut), insbesondere {{ll|Extension:ConfirmEdit}}. <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam setup basics== </div> {{anchor|CAPTCHA}} === CAPTCHA === <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> * alle Bearbeitungen * Bearbeitungen, die neue, unerkannte externe Links hinzufügen * Benutzerregistrierung <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} ===Schutz einzelner Seiten=== <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === Missbrauchsfilter === <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> === Offene Proxies === <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Apache configuration changes === </div> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> == Weitere Ideen == <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> ==Siehe auch== *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === Erweiterungen === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === Einstellungen === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} === Weblinks === * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] n01tqn8gx1fru83syv84ucnnpdfdes3 Installer 0 116720 5387805 656735 2022-07-29T09:26:17Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Installation/cs 0 121389 5387779 674835 2022-07-29T09:21:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/cs]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/cs]] srwqz7ma3qlny8ld00bl9dxg88cjc3y Template:InstallationNav/cs 10 121391 5387188 5384777 2022-07-28T21:17:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Configuring MediaWiki/cs 100 121396 5386474 5385117 2022-07-28T14:30:42Z ENeRZet 17359278 wikitext text/x-wiki <languages/> == Základní konfigurace == Když poprvé [[Special:MyLanguage/Manual:Installing MediaWiki|instalujete MediaWiki]], měli byste spustit dodaný konfigurační skript prostřednictvím vašeho webového prohlížeče. <span lang="en" dir="ltr" class="mw-content-ltr">This will perform the basic configuration required to get the wiki up and running. See {{ll|Manual:Config script}} for full details running the script.</span> == Další nastavení == Jakmile byla wiki nainstalována a výše uvedeným skriptem nastavena, veškerá další nastavení musíte provádět úpravami souboru '''<code>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</code>''' Pomoc s pokročilejším nastavením najdete na stránkách {{ll|Manual:System administration}} a {{ll|Manual:Administrators}}. == Související stránky == * {{ll|Manual:Installing MediaWiki|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] hmqylrnuhdg005rd6vhj84downht27p 5386476 5386474 2022-07-28T14:31:28Z ENeRZet 17359278 Created page with "Tím se provede základní konfigurace potřebná pro zprovoznění wiki. Úplné podrobnosti o spuštění skriptu najdete v $config." wikitext text/x-wiki <languages/> == Základní konfigurace == Když poprvé [[Special:MyLanguage/Manual:Installing MediaWiki|instalujete MediaWiki]], měli byste spustit dodaný konfigurační skript prostřednictvím vašeho webového prohlížeče. Tím se provede základní konfigurace potřebná pro zprovoznění wiki. Úplné podrobnosti o spuštění skriptu najdete v {{ll|Manual:Config script}}. == Další nastavení == Jakmile byla wiki nainstalována a výše uvedeným skriptem nastavena, veškerá další nastavení musíte provádět úpravami souboru '''<code>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</code>''' Pomoc s pokročilejším nastavením najdete na stránkách {{ll|Manual:System administration}} a {{ll|Manual:Administrators}}. == Související stránky == * {{ll|Manual:Installing MediaWiki|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] i367ys0lcr2zyrws1oos71t1944acwv 5386478 5386476 2022-07-28T14:31:57Z ENeRZet 17359278 wikitext text/x-wiki <languages/> == Základní konfigurace == Když poprvé [[Special:MyLanguage/Manual:Installing MediaWiki|instalujete MediaWiki]], měli byste spustit dodaný konfigurační skript prostřednictvím vašeho webového prohlížeče. Tím se provede základní konfigurace potřebná pro zprovoznění wiki. Úplné podrobnosti o spuštění skriptu najdete na stránce {{ll|Manual:Config script}}. == Další nastavení == Jakmile byla wiki nainstalována a výše uvedeným skriptem nastavena, veškerá další nastavení musíte provádět úpravami souboru '''<code>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</code>''' Pomoc s pokročilejším nastavením najdete na stránkách {{ll|Manual:System administration}} a {{ll|Manual:Administrators}}. == Související stránky == * {{ll|Manual:Installing MediaWiki|nsp=0}} * {{ll|Manual:FAQ|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] jtci8bf4ki7v2iex6vp8uns0t1q50yh Manual:Installation/pl 100 129218 5387812 707829 2022-07-29T09:27:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/pl]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pl]] b6zf9uu302z9prb61dalq114ribkgg6 Help:Extension:Translate/lt 12 129266 5386857 5379863 2022-07-28T19:25:13Z Pavel1513 17650776 Created page with "Pakeitimų sekimas galimas ir išoriškai sekamiems failams, nes plėtinio viduje naudojama lokalizacijos failų išsaugotą išvestinę versiją, kur saugomi pirminis tekstas ir jo vertimai, vietoje to, kad panaudoti juos tiesiogiai originaliu formatu." wikitext text/x-wiki <languages/> {{Extension-Translate}} [[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|Plėtinio "[[Special:Translate]]" pagrindinio specialiojo puslapio dažniausiai naudojamas režimas, "žiūrėk visus neišverstus pranešimus".]] __NOEDITSECTION__ [[Special:MyLanguage/Extension:Translate|Vertimo plėtinys]] papildo "MediaViki" esminėmis funkcijomis, reikalingomis vertimo darbui atlikti. Jį galima naudoti turiniui, "viki" sąsajai ir net kitai programinei įrangai, kaip tai daroma svetainėje [[Special:MyLanguage/translatewiki|translatewiki.net]], versti. "Translate" plėtinys turi lengvai naudojamą vertimo sąsają ir gali atskirti puslapio struktūrą nuo paties turinio, kurį reikia išversti, rodydamas vertėjams tik verčiamą tekstą, ir suskirstydamas turinį į lengvai valdomus vienetus. Kiekvienas teksto vienetas stebimas dėl pakeitimų, ir vertėjai iš karto mato ką reikia atnaujinti tiek atskirame puslapyje, tiek visoje "viki". Kiekvieną mėnesį šimtai vertėjų naudoja plėtinį "Translation" "MediaViki" naudotojo sąsajai bei kitiems programinės įrangos projektams svetainėje translatewiki.net, versti. Svetainėje [http://userbase.kde.org userbase.kde.org] jis naudojamas beveik tūkstančio puslapių tūriniui, kartu su naudotojo dokumentacija, išversti. Pradėti naudoti plėtinį "Translate" yra lengva, bet jis taip pat yra plečiamas ir turi pažangias ataskaitų teikimo, patikrinimo ir darbo eigos funkcijas. == Ypatumai == [[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|Vertimo redaktorius: verčiamas pranešimas su patarimu (jo paveikslėlyje nesimato) ir pasiūlymais iš dviejų pagalbinių kalbų]] '''Sąsaja:''' Pagrindinis "Translate" plėtinio ypatumas - paprasta, tačiau funkcionali vertimo sąsaja. Be tokios svarbios informacijos kaip verčiamo pranešimo apibrėžimai ir dokumentacija, taip pat galima peržiūrėti vertimus į kitas kalbas. Jei apibrėžimai pasikeičia, jūs tuos pakeitimus matysite. Į plėtinį integruotos patikros padės ištaisyti dažniausiai pasitaikančias klaidas, tokias kaip skliaustelių nesubalansavimas arba nenaudojami kintamieji. Priklausomai nuo konfigūracijos, taip pat gali būti pasiūlymų iš jau išversto teksto ("translation memory") bei mašininio vertimo sistemų, tokių kaip Google Translate, Microsoft's Bing Translator ir Apertium. Vertimo sąsajos patogumą naudotis pagerina "JavaScript" ir AJAX. Vidinė sąsaja ("backend") pateikia WebAPI (Aplikacijų programavimo sąsąjas), kurios gali būti naudojamos mobiliuosiose sąsajose arba sąsajose, skirtose tam tikram turiniui. Taip pat įmanoma eksportuoti pranešimus vertimui į kitus autonominius ("off-line") bei prie interneto prisijungusius ("on-line") įrankius, kurie supranta [[:en:Gettext|Gettext po]] failo formatą. '''Pranešimų grupės ir uždaviniai:''' Daugelis ypatumų pagrįsti dviem pagrindinėmis sąvokomis: pranešimų grupės ir uždaviniai. Pranešimų grupė yra pranešimų rinkinys. Vieno puslapio turinys būtų viena pranešimų grupė, kur paprasčiausiu atveju, kiekviena pastraipa būtų vienas pranešimas toje grupėje. Kiekviename "MediaViki" plėtinyje naudojami pranešimai sudaro svetainės translatedwiki.net pranešimų grupes, o keli ypač stambūs plėtiniai turi kelias grupes. Taip pat galite sukurti grupių grupę, kaip pvz., ''Visi naujienlaiškai'' arba ''Visi vertimo plėtinių pranešimai''. Daugelis statistinių duomenų ir uždavinių veikia pranešimų grupių pagrindu. Uždaviniai, arba kitaip tariant, skirtingi grupės pranešimų sąrašai, palengvina įvairius darbo atlikimo scenarijus. Paprastai, vertėjas gauna visų grupėje neišverstų pranešimų sąrašą, bet būna uždavinių, kur pranešimus galima peržiūrėti arba gauti visų, tiek išverstų tiek neišverstų, pranešimų sąrašą. [[Image:Translate manual - Translate example - 01. LanguageStats long.png|thumb|300px|Šiame puslapyje pranešama apie kiekvienos pranešimų grupės vertimo būseną]] '''Ataskaitos ir statistika:''' Plėtinys turi platų [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting|ataskaitos funkcijų]] sąrašą, pradedant neišverstų pranešimų parodymu tam tikrai kalbai visose pranešimų grupėse, ir baigiant vertėjų sąrašu kiekvienai kalbai, kartu su jų aktyvumo lygio parodymu. '''Turinio vertimas:''' Jei kada nors mėginote versti medžiagą iš "MediaViki" be jokių įrankių, jūs suprantate problemos mastą. Išverstos versijos pasensta ir nėra galimybės sekti pakeitimus pagrindiniame puslapyje, todėl atsiranda daug pusiau išverstos ir pasenusios medžiagos, neturint galimybės sužinoti jos tikslią būseną. Vertėjai dažani būna nusiminę, kai negali dirbti su mažesnėmis teksto atkarpomis, kurias lengva valdyti. Jiems sunkiau rasti ką dirbti ir ką reikia atnaujinti. Naudotojai taip pat pasimeta tarp pasenusios informacijos. Visa tai išsprendžiama plėtinio "Translate" ir jo puslapių vertimo funkcijų pagalba. Tai kiek padidina puslapio, kurį reikia išversti apkrovą, tačiau nauda persveria visą. Iš esmės, reikia tik pažymėti tas puslapio dalis, kurias reikia išversti. Toliau, plėtinys suskirstys jas į pastraipos didžio segmentus ir sukurs jiems pranešimų grupę. Tada vertėjai galės pasinaudoti visomis pirmiau paminėtomis funkcijomis. Be to, lengvai galima pridėti kalbos juostą su žyma {{tag|languages|single}} arba padaryti, kad nuorodos automatiškai nukreiptų į naudotojo pageidaujamą kalbos versiją (tik), jei tokia yra, naudojant <nowiki>[[Special:MyLanguage/Pagename]]</nowiki> formos nuorodas. Daugiau informacijos rasite vadovėliuose [[Special:MyLanguage/Help:Extension:Translate/Page translation example|"Kaip paruoši puslapį vertimui"]] ir [[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration|"Išsami puslapio vertimo funkcijos dokumentacija"]]. '''Programuotojai:''' Į plėtinį integruotas daugelio įprastų vertimo failų formatų, pavyzdžiui, Java savybių ir Gettext po, palaikymas. Plėtinys turi platų įrankių rinkinį, tiek pačioje "Viki" tiek komandų eilutėje ("command line"), kad būtų galima sėkmingai importuoti ir eksportuoti vertimus. {{anchor|searching}} '''Paieška:''' Be paieškos funkcijos vertėjams būtų sunku rasti tam tikrus pranešimus, kuriuos jie norėtų išversti. Visų vertimų arba projekto eilučių peržiūra nėra efektyvi. Be to, vertėjai dažnai nori patikrinti, kaip tam tikras terminas išverstas į tam tikrą kalbą tame projekte. Šis uždavinys išsprendžiamas specialiojo [[Special:SearchTranslations]] puslapio pabalba. Vertėjai gali surasti pranešimus, kuriuose yra tam tirkų terminų bet kuria kalba ir filtruoti juos pagal įvairius kriterijus: tai numatytoji reikšmė. Po paieškos, jie gali perjungti rezultatus į minėtų pranešimų vertimus, pavyzdžiui, surasti tam tikro termino esamus, nesamus ar pasenusius vertimus. == Naudojimo pavyzdžiai == Plėtinio "Translate" pagalba galima išversti beveik viską. Žinoma, yra specializuotų įrankių, skirtų tam tikram turiniui, tokiam kaip vaizdo įrašų subtitrai, versti, ir tai geriausia padaryti naudojant tuos įrankus, bet apskritai, plėtinys gerai apdoroja bet kokį tekstą, kurį galima suskirstyti į vieno žodžio arba vienos didelės pastraipos didžio pranešimus. Ilgesni pranešimai per daug gremėzdiški vertimui ir su jais sunkiau dirbti. Trys pagrindiniai plėtinio "Translate" naudojimo vairantai yra '''turinio vertimas''', '''sąsajos lokalizacija''' ir '''programinės įrangos vertimas'''. Visi jie aptariami tolesniuose skyriuose su nuorodomis (kur tai prieinama) į mokomąją bei informacinę medžiagą, taip pat išsamią teminę pagalbą. Iš trijų naudojimo variantų, "sąsajos lokalizacija" yra mažiausiai naudojama. === Turinio vertimas === [[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|Šis vertimas paseno: pasenusios dalys pakeistos nauju pirminiu tekstu ir vertėjai vienu spustelėjimu gali pasiekti pranešimus, kuriuos reikia atnaujinti.]] Dauguma "viki" turi turinio, kuris, kaip jie norėtų, būtų pasiekiamas keliomis kalbomis. Nesvarbu, ar tai tik keli ar šimtai puslapių. Tam, kad nebūtų gaištamas vertėjų laikas, puslapiai turi būti pažymėti vertimui tik tuomet, kai jie yra pakankamai stabilūs. Dėl kiekvieno vėliau padaryto pakeitimo dešimtys ar šimtai vertimų taps pasenusiais, ir jiems atnaujinti reikalingas laikas padidės. Reikia turėti tai omenyje, ypač jei vertėjai - savanoriai, branginti laiką, kurį jie skiria vertimui ir atnaujinimui, ir vengti bereikalingo darbo. Jei puslapių vertimui naudojate plėtinį "Translate", esate teisingame kelyje į veiksmingiausią ir efektyviausią vertėjų turimo laiko panaudojimą. Dėl to, kad "Translate" plėtinys suskirsto puslapį į pastraipos didžio segmentus, vertėjai neturi per daug laisvės keisti turinį. Paprastai, tai gerai ir idealiai tinka, kai pageidaujamas turinio tęstinumas ir nuoseklumas visomis kalbomis. Galima tai apeiti, bet iš esmės toks vertimo būdas ne visada tinka, pavyzdžiui, "Vikipedijos" straipsniams, kurie paprastai yra visiškai nepriklausomi vieni nuo kitų. Net jei iš pradžių jie prasideda kaip vertimo iš kitos kalbos variantas, paprastai toliau jie pradeda gyventi savo, nuo originalo kalbos nepriklausomą gyvenimą. Naudojant gi "Translate" plėtinį, originalus puslapis visada yra pagrindinė versija, ir išverstoje puslapio versijoje negali atsirasti naujas turinys. Turint omenyje šiuos apribojimus, vis dar yra daugybė atvejų, kai ši funkcija puikiai tinka. Į šią kategoriją patenka dauguma, jei ne visi, naudotojo dokumentai, taip pat į naujienas panašus turinys, kuris po parašymo nesikeičia. Jei jau turite įdiegtą plėtinį "Translate" ir sukonfigūruotas prieigos teises, pabandykite sukurti puslapį ir visą tekstą suvynioti į {{#tag:syntaxhighlight|{{^(}}languages />{{^(}}translate>...{{^(}}/translate>|lang=html|inline=1}} ir vadovaukitės nuorodomis arba vadovaukitės vadovėliu [[Special:MyLanguage/Help:Extension:Translate/Page translation example|"Kaip paruošti puslapį vertimui"]]. Puslapių grupės gali būti tolaiu grupuojamos kartu puslapio [[Special:AggregateGroups]] pagalba. === Sąsajos lokalizacija daugiakalbiuose "viki" projektuose === Beveik kiekvienoje "viki" pritaikoma [[Special:MyLanguage/Manual:Interface/Sidebar|šoninė juosta]]. Galima sukurti pranešimų grupę šoninės juostos bei kitų sąsajos nustatymų lokalizacijai. Vienas įdomių išplėtimų - daugiakalbiai puslapiai arba šablonai, sukurti naudojant stebuklaingąjį žodį <nowiki>{{int:}}</nowiki>. Geri to pavyzdžiai yra [[translatewiki:|translatewiki.net]] pagrindinis puslapis ir kai kurie "Wikimedia Commons" šablonai. Stebuklingasis žodis <nowiki>{{int:}}</nowiki> yra turinio vertimo funkcijos alternatyva, ir labiau tinka sunkių puslapių, tokių kaip translatewiki.net pagrindinis puslapis, žymėjimui. Kitas patrauklus ypatumas yra tas, kad puslapio kalba automatiškai nusistato pagal naudotojo sąsajos kalba, dėl to nėra būtinybės turėti kalbų parinkimo juostą, nors jūs, vietoj to, galbūt norėtumėte turėti galimybę pačiam pasirnkti sąsajos kalbą. Šiuo metu šis būdas yra kiek sudetingesnis nei turinio vertimas, ir reikalauja programinės įrangos konfigūravimo, tačiau visa tai aprašoma pamokoje [[Special:MyLanguage/Help:Extension:Translate/Unstructured_element_translation|"Kaip sukurti sąsajos pranešimų grupę]]. === Programos vertimas === Plėtinys "Translation" puikiai tinka programinės įrangos sąsajos pranešimams versti. Puslapyje translatewiki.net jis naudojamas dišimtims programinės įrangos produktų, nuo žaidimų iki žiniatinklio programų, versti. Plėtinys palaiko vertimų skaitymą ir atnaujinimą iš ir į įprastus formatus, naudojamus kuriant žiniatinklio svetaines, įskaitant [[w:.properties|Java savybių]], [[w:Gettext|Gettext]] ir [[w:YAML|Yaml]] failus. Pakeitimų sekimas galimas ir išoriškai sekamiems failams, nes plėtinio viduje naudojama lokalizacijos failų išsaugotą išvestinę versiją, kur saugomi pirminis tekstas ir jo vertimai, vietoje to, kad panaudoti juos tiesiogiai originaliu formatu. <div lang="en" dir="ltr" class="mw-content-ltr"> With simple command line tools, translation administrators can easily import even a large set of existing translations and with just one command they can export all translations in the correct format and in the correct directory structure. You can export directly to your [[w:Version control system|VCS]] repository checkout, where you can easily commit changes and new files. </div> == Tolimesnis skaitymas ir pamokos == === Vertėjams ir vertimo administratoriams === {{anchor|For translators and translation administrators}} [[File:How to use ExtensionTranslate - Wikimania 2017.pdf|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Slides of a workshop about how to use {{ll|Extension:Translate}} at Wikimania17.</span>]] * {{ll|Help:Extension:Translate/Translation example|2=Kaip versti}} [Pamoka] * {{ll|Help:Extension:Translate/Translation best practices|2=Geros vertimo praktikos}} * {{ll|Help:Extension:Translate/Statistics and reporting|2=Statistikos ir pranešimas}} * {{ll|Help:Extension:Translate/Quality assurance|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quality assurance</span>}} * {{ll|Help:Extension:Translate/Message group states|2=<span lang="en" dir="ltr" class="mw-content-ltr">Message group states</span>}} * [Vykdoma] {{ll|Help:Extension:Translate/Search|2=Paieška}} * {{ll|Help:Extension:Translate/Off-line translation|2=Autonominis vertimas}} * [Vykdoma] {{ll|Help:Extension:Translate/Glossary|2=Žodynas}} == Vertimo administratoriams == * {{ll|Help:Extension:Translate/Page translation example|2=Kaip paruošti puslapį vertimui}} [Pamoka] * {{ll|Help:Extension:Translate/Page translation administration|2=Puslapio vertimo administracija}} * {{ll|Help:Extension:Translate/Unstructured element translation|2=<span lang="en" dir="ltr" class="mw-content-ltr">Interface message groups (localised sidebar, main page and templates)</span>}} [Pamoka] * [Vykdoma] {{ll|Help:Extension:Translate/Group management|2=<span lang="en" dir="ltr" class="mw-content-ltr">Message group management</span>}} * {{ll|Help:Extension:Translate/Group configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">YAML configuration format</span>}} * {{ll|Help:Extension:Translate/Group configuration example|2=<span lang="en" dir="ltr" class="mw-content-ltr">How to write YAML configuration for file based message groups</span>}} [Pamoka] <div lang="en" dir="ltr" class="mw-content-ltr"> === Reference documents for developers === </div> * {{ll|Help:Extension:Translate/Installation|2=Įdiegimas}}{{int|and}}{{int|word-separator}}{{ll|Help:Extension:Translate/Configuration|2=Konfigūracija}} - <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|MediaWiki Language Extension Bundle}} should be enough in most cases.</span> * {{ll|Help:Extension:Translate/Translation memories|2=Vertimo prisiminimai}} * {{ll|Help:Extension:Translate/Developer guide|2=<span lang="en" dir="ltr" class="mw-content-ltr">Developer guide</span>}} * [Vykdoma] {{ll|Help:Extension:Translate/Components|2=<span lang="en" dir="ltr" class="mw-content-ltr">Translate explained for developers</span>}} ** {{ll|Help:Extension:Translate/Hooks|2=Kabliukai (hooks)}} ** [Vykdoma] {{ll|Help:Extension:Translate/Message groups|2=Pranešimų grupės}} ** [Vykdoma] {{ll|Help:Extension:Translate/File format support|2=Failų formatų palaikymas}} ** {{ll|Help:Extension:Translate/Translation_aids|2=<span lang="en" dir="ltr" class="mw-content-ltr">Translation aids</span>}} ** [<span lang="en" dir="ltr" class="mw-content-ltr">Unwritten</span>] {{ll|Help:Extension:Translate/API|2=<span lang="en" dir="ltr" class="mw-content-ltr">action API</span>}} ** {{ll|Help:Extension:Translate/Insertables|2=<span lang="en" dir="ltr" class="mw-content-ltr">Insertables</span>}} ** {{ll|Help:Extension:Translate/Command line scripts|2=<span lang="en" dir="ltr" class="mw-content-ltr">Command line scripts</span>}} ** {{ll|Help:Extension:Translate/Process flow in MediaWiki jobs|2=<span lang="en" dir="ltr" class="mw-content-ltr">Process flow in MediaWiki jobs</span>}} - <span lang="en" dir="ltr" class="mw-content-ltr">Describes what jobs are involved when a page is marked for translation or a section is translated</span> ** {{ll|Help:Extension:Translate/Translation memory architecture|2=<span lang="en" dir="ltr" class="mw-content-ltr">Translation memory architecture</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Related === </div> * {{ll|Extension:TranslationNotifications#Special_pages}} * {{ll|Localisation/Tutorial}} - <span lang="en" dir="ltr" class="mw-content-ltr">General localisation tutorial for developers, for use at hackathons & trainings</span> * {{ll|Extension:TranslateSvg}} - <span lang="en" dir="ltr" class="mw-content-ltr">Adds support for translating SVG files</span> * {{ll|Universal Language Selector}} - <span lang="en" dir="ltr" class="mw-content-ltr">Provides web fonts and input methods</span> * [[m:Special:MyLanguage/Translatability|m:Translatability]] – <span lang="en" dir="ltr" class="mw-content-ltr">things to think about when creating pages or processes on multilingual wikis</span> * [[m:Tech/Translators/List|m:Tech/Translators/List]] - Įtraukite save į aktyvių techninių vertėjų sąrašą [[Category:Extension:Translate{{#translation:}}| ]] ln6rlz3tatrlzfu56lsei2hw7uvwb2y 5386859 5386857 2022-07-28T19:26:40Z Pavel1513 17650776 wikitext text/x-wiki <languages/> {{Extension-Translate}} [[Image:Translate manual - Translate example - 04. Untranslated.png|thumb|300px|Plėtinio "[[Special:Translate]]" pagrindinio specialiojo puslapio dažniausiai naudojamas režimas, "žiūrėk visus neišverstus pranešimus".]] __NOEDITSECTION__ [[Special:MyLanguage/Extension:Translate|Vertimo plėtinys]] papildo "MediaViki" esminėmis funkcijomis, reikalingomis vertimo darbui atlikti. Jį galima naudoti turiniui, "viki" sąsajai ir net kitai programinei įrangai, kaip tai daroma svetainėje [[Special:MyLanguage/translatewiki|translatewiki.net]], versti. "Translate" plėtinys turi lengvai naudojamą vertimo sąsają ir gali atskirti puslapio struktūrą nuo paties turinio, kurį reikia išversti, rodydamas vertėjams tik verčiamą tekstą, ir suskirstydamas turinį į lengvai valdomus vienetus. Kiekvienas teksto vienetas stebimas dėl pakeitimų, ir vertėjai iš karto mato ką reikia atnaujinti tiek atskirame puslapyje, tiek visoje "viki". Kiekvieną mėnesį šimtai vertėjų naudoja plėtinį "Translation" "MediaViki" naudotojo sąsajai bei kitiems programinės įrangos projektams svetainėje translatewiki.net, versti. Svetainėje [http://userbase.kde.org userbase.kde.org] jis naudojamas beveik tūkstančio puslapių tūriniui, kartu su naudotojo dokumentacija, išversti. Pradėti naudoti plėtinį "Translate" yra lengva, bet jis taip pat yra plečiamas ir turi pažangias ataskaitų teikimo, patikrinimo ir darbo eigos funkcijas. == Ypatumai == [[Image:Translate manual - Translate example - 07. Editor assistant.png|thumb|300px|Vertimo redaktorius: verčiamas pranešimas su patarimu (jo paveikslėlyje nesimato) ir pasiūlymais iš dviejų pagalbinių kalbų]] '''Sąsaja:''' Pagrindinis "Translate" plėtinio ypatumas - paprasta, tačiau funkcionali vertimo sąsaja. Be tokios svarbios informacijos kaip verčiamo pranešimo apibrėžimai ir dokumentacija, taip pat galima peržiūrėti vertimus į kitas kalbas. Jei apibrėžimai pasikeičia, jūs tuos pakeitimus matysite. Į plėtinį integruotos patikros padės ištaisyti dažniausiai pasitaikančias klaidas, tokias kaip skliaustelių nesubalansavimas arba nenaudojami kintamieji. Priklausomai nuo konfigūracijos, taip pat gali būti pasiūlymų iš jau išversto teksto ("translation memory") bei mašininio vertimo sistemų, tokių kaip Google Translate, Microsoft's Bing Translator ir Apertium. Vertimo sąsajos patogumą naudotis pagerina "JavaScript" ir AJAX. Vidinė sąsaja ("backend") pateikia WebAPI (Aplikacijų programavimo sąsąjas), kurios gali būti naudojamos mobiliuosiose sąsajose arba sąsajose, skirtose tam tikram turiniui. Taip pat įmanoma eksportuoti pranešimus vertimui į kitus autonominius ("off-line") bei prie interneto prisijungusius ("on-line") įrankius, kurie supranta [[:en:Gettext|Gettext po]] failo formatą. '''Pranešimų grupės ir uždaviniai:''' Daugelis ypatumų pagrįsti dviem pagrindinėmis sąvokomis: pranešimų grupės ir uždaviniai. Pranešimų grupė yra pranešimų rinkinys. Vieno puslapio turinys būtų viena pranešimų grupė, kur paprasčiausiu atveju, kiekviena pastraipa būtų vienas pranešimas toje grupėje. Kiekviename "MediaViki" plėtinyje naudojami pranešimai sudaro svetainės translatedwiki.net pranešimų grupes, o keli ypač stambūs plėtiniai turi kelias grupes. Taip pat galite sukurti grupių grupę, kaip pvz., ''Visi naujienlaiškai'' arba ''Visi vertimo plėtinių pranešimai''. Daugelis statistinių duomenų ir uždavinių veikia pranešimų grupių pagrindu. Uždaviniai, arba kitaip tariant, skirtingi grupės pranešimų sąrašai, palengvina įvairius darbo atlikimo scenarijus. Paprastai, vertėjas gauna visų grupėje neišverstų pranešimų sąrašą, bet būna uždavinių, kur pranešimus galima peržiūrėti arba gauti visų, tiek išverstų tiek neišverstų, pranešimų sąrašą. [[Image:Translate manual - Translate example - 01. LanguageStats long.png|thumb|300px|Šiame puslapyje pranešama apie kiekvienos pranešimų grupės vertimo būseną]] '''Ataskaitos ir statistika:''' Plėtinys turi platų [[Special:MyLanguage/Help:Extension:Translate/Statistics and reporting|ataskaitos funkcijų]] sąrašą, pradedant neišverstų pranešimų parodymu tam tikrai kalbai visose pranešimų grupėse, ir baigiant vertėjų sąrašu kiekvienai kalbai, kartu su jų aktyvumo lygio parodymu. '''Turinio vertimas:''' Jei kada nors mėginote versti medžiagą iš "MediaViki" be jokių įrankių, jūs suprantate problemos mastą. Išverstos versijos pasensta ir nėra galimybės sekti pakeitimus pagrindiniame puslapyje, todėl atsiranda daug pusiau išverstos ir pasenusios medžiagos, neturint galimybės sužinoti jos tikslią būseną. Vertėjai dažani būna nusiminę, kai negali dirbti su mažesnėmis teksto atkarpomis, kurias lengva valdyti. Jiems sunkiau rasti ką dirbti ir ką reikia atnaujinti. Naudotojai taip pat pasimeta tarp pasenusios informacijos. Visa tai išsprendžiama plėtinio "Translate" ir jo puslapių vertimo funkcijų pagalba. Tai kiek padidina puslapio, kurį reikia išversti apkrovą, tačiau nauda persveria visą. Iš esmės, reikia tik pažymėti tas puslapio dalis, kurias reikia išversti. Toliau, plėtinys suskirstys jas į pastraipos didžio segmentus ir sukurs jiems pranešimų grupę. Tada vertėjai galės pasinaudoti visomis pirmiau paminėtomis funkcijomis. Be to, lengvai galima pridėti kalbos juostą su žyma {{tag|languages|single}} arba padaryti, kad nuorodos automatiškai nukreiptų į naudotojo pageidaujamą kalbos versiją (tik), jei tokia yra, naudojant <nowiki>[[Special:MyLanguage/Pagename]]</nowiki> formos nuorodas. Daugiau informacijos rasite vadovėliuose [[Special:MyLanguage/Help:Extension:Translate/Page translation example|"Kaip paruoši puslapį vertimui"]] ir [[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration|"Išsami puslapio vertimo funkcijos dokumentacija"]]. '''Programuotojai:''' Į plėtinį integruotas daugelio įprastų vertimo failų formatų, pavyzdžiui, Java savybių ir Gettext po, palaikymas. Plėtinys turi platų įrankių rinkinį, tiek pačioje "Viki" tiek komandų eilutėje ("command line"), kad būtų galima sėkmingai importuoti ir eksportuoti vertimus. {{anchor|searching}} '''Paieška:''' Be paieškos funkcijos vertėjams būtų sunku rasti tam tikrus pranešimus, kuriuos jie norėtų išversti. Visų vertimų arba projekto eilučių peržiūra nėra efektyvi. Be to, vertėjai dažnai nori patikrinti, kaip tam tikras terminas išverstas į tam tikrą kalbą tame projekte. Šis uždavinys išsprendžiamas specialiojo [[Special:SearchTranslations]] puslapio pabalba. Vertėjai gali surasti pranešimus, kuriuose yra tam tirkų terminų bet kuria kalba ir filtruoti juos pagal įvairius kriterijus: tai numatytoji reikšmė. Po paieškos, jie gali perjungti rezultatus į minėtų pranešimų vertimus, pavyzdžiui, surasti tam tikro termino esamus, nesamus ar pasenusius vertimus. == Naudojimo pavyzdžiai == Plėtinio "Translate" pagalba galima išversti beveik viską. Žinoma, yra specializuotų įrankių, skirtų tam tikram turiniui, tokiam kaip vaizdo įrašų subtitrai, versti, ir tai geriausia padaryti naudojant tuos įrankus, bet apskritai, plėtinys gerai apdoroja bet kokį tekstą, kurį galima suskirstyti į vieno žodžio arba vienos didelės pastraipos didžio pranešimus. Ilgesni pranešimai per daug gremėzdiški vertimui ir su jais sunkiau dirbti. Trys pagrindiniai plėtinio "Translate" naudojimo vairantai yra '''turinio vertimas''', '''sąsajos lokalizacija''' ir '''programinės įrangos vertimas'''. Visi jie aptariami tolesniuose skyriuose su nuorodomis (kur tai prieinama) į mokomąją bei informacinę medžiagą, taip pat išsamią teminę pagalbą. Iš trijų naudojimo variantų, "sąsajos lokalizacija" yra mažiausiai naudojama. === Turinio vertimas === [[Image:Translate manual - Translate example - 10. Outdated clicking.png|thumb|300px|Šis vertimas paseno: pasenusios dalys pakeistos nauju pirminiu tekstu ir vertėjai vienu spustelėjimu gali pasiekti pranešimus, kuriuos reikia atnaujinti.]] Dauguma "viki" turi turinio, kuris, kaip jie norėtų, būtų pasiekiamas keliomis kalbomis. Nesvarbu, ar tai tik keli ar šimtai puslapių. Tam, kad nebūtų gaištamas vertėjų laikas, puslapiai turi būti pažymėti vertimui tik tuomet, kai jie yra pakankamai stabilūs. Dėl kiekvieno vėliau padaryto pakeitimo dešimtys ar šimtai vertimų taps pasenusiais, ir jiems atnaujinti reikalingas laikas padidės. Reikia turėti tai omenyje, ypač jei vertėjai - savanoriai, branginti laiką, kurį jie skiria vertimui ir atnaujinimui, ir vengti bereikalingo darbo. Jei puslapių vertimui naudojate plėtinį "Translate", esate teisingame kelyje į veiksmingiausią ir efektyviausią vertėjų turimo laiko panaudojimą. Dėl to, kad "Translate" plėtinys suskirsto puslapį į pastraipos didžio segmentus, vertėjai neturi per daug laisvės keisti turinį. Paprastai, tai gerai ir idealiai tinka, kai pageidaujamas turinio tęstinumas ir nuoseklumas visomis kalbomis. Galima tai apeiti, bet iš esmės toks vertimo būdas ne visada tinka, pavyzdžiui, "Vikipedijos" straipsniams, kurie paprastai yra visiškai nepriklausomi vieni nuo kitų. Net jei iš pradžių jie prasideda kaip vertimo iš kitos kalbos variantas, paprastai toliau jie pradeda gyventi savo, nuo originalo kalbos nepriklausomą gyvenimą. Naudojant gi "Translate" plėtinį, originalus puslapis visada yra pagrindinė versija, ir išverstoje puslapio versijoje negali atsirasti naujas turinys. Turint omenyje šiuos apribojimus, vis dar yra daugybė atvejų, kai ši funkcija puikiai tinka. Į šią kategoriją patenka dauguma, jei ne visi, naudotojo dokumentai, taip pat į naujienas panašus turinys, kuris po parašymo nesikeičia. Jei jau turite įdiegtą plėtinį "Translate" ir sukonfigūruotas prieigos teises, pabandykite sukurti puslapį ir visą tekstą suvynioti į {{#tag:syntaxhighlight|{{^(}}languages />{{^(}}translate>...{{^(}}/translate>|lang=html|inline=1}} ir vadovaukitės nuorodomis arba vadovaukitės vadovėliu [[Special:MyLanguage/Help:Extension:Translate/Page translation example|"Kaip paruošti puslapį vertimui"]]. Puslapių grupės gali būti tolaiu grupuojamos kartu puslapio [[Special:AggregateGroups]] pagalba. === Sąsajos lokalizacija daugiakalbiuose "viki" projektuose === Beveik kiekvienoje "viki" pritaikoma [[Special:MyLanguage/Manual:Interface/Sidebar|šoninė juosta]]. Galima sukurti pranešimų grupę šoninės juostos bei kitų sąsajos nustatymų lokalizacijai. Vienas įdomių išplėtimų - daugiakalbiai puslapiai arba šablonai, sukurti naudojant stebuklaingąjį žodį <nowiki>{{int:}}</nowiki>. Geri to pavyzdžiai yra [[translatewiki:|translatewiki.net]] pagrindinis puslapis ir kai kurie "Wikimedia Commons" šablonai. Stebuklingasis žodis <nowiki>{{int:}}</nowiki> yra turinio vertimo funkcijos alternatyva, ir labiau tinka sunkių puslapių, tokių kaip translatewiki.net pagrindinis puslapis, žymėjimui. Kitas patrauklus ypatumas yra tas, kad puslapio kalba automatiškai nusistato pagal naudotojo sąsajos kalba, dėl to nėra būtinybės turėti kalbų parinkimo juostą, nors jūs, vietoj to, galbūt norėtumėte turėti galimybę pačiam pasirnkti sąsajos kalbą. Šiuo metu šis būdas yra kiek sudetingesnis nei turinio vertimas, ir reikalauja programinės įrangos konfigūravimo, tačiau visa tai aprašoma pamokoje [[Special:MyLanguage/Help:Extension:Translate/Unstructured_element_translation|"Kaip sukurti sąsajos pranešimų grupę]]. === Programos vertimas === Plėtinys "Translation" puikiai tinka programinės įrangos sąsajos pranešimams versti. Puslapyje translatewiki.net jis naudojamas dišimtims programinės įrangos produktų, nuo žaidimų iki žiniatinklio programų, versti. Plėtinys palaiko vertimų skaitymą ir atnaujinimą iš ir į įprastus formatus, naudojamus kuriant žiniatinklio svetaines, įskaitant [[w:.properties|Java savybių]], [[w:Gettext|Gettext]] ir [[w:YAML|Yaml]] failus. Pakeitimų sekimas galimas ir išoriškai sekamiems failams, nes plėtinio viduje naudojama lokalizacijos failų išsaugotą išvestinę versiją, kur saugomi pirminis tekstas ir jo vertimai, vietoje jų tiesioginio naudojimo originaliu formatu. <div lang="en" dir="ltr" class="mw-content-ltr"> With simple command line tools, translation administrators can easily import even a large set of existing translations and with just one command they can export all translations in the correct format and in the correct directory structure. You can export directly to your [[w:Version control system|VCS]] repository checkout, where you can easily commit changes and new files. </div> == Tolimesnis skaitymas ir pamokos == === Vertėjams ir vertimo administratoriams === {{anchor|For translators and translation administrators}} [[File:How to use ExtensionTranslate - Wikimania 2017.pdf|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Slides of a workshop about how to use {{ll|Extension:Translate}} at Wikimania17.</span>]] * {{ll|Help:Extension:Translate/Translation example|2=Kaip versti}} [Pamoka] * {{ll|Help:Extension:Translate/Translation best practices|2=Geros vertimo praktikos}} * {{ll|Help:Extension:Translate/Statistics and reporting|2=Statistikos ir pranešimas}} * {{ll|Help:Extension:Translate/Quality assurance|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quality assurance</span>}} * {{ll|Help:Extension:Translate/Message group states|2=<span lang="en" dir="ltr" class="mw-content-ltr">Message group states</span>}} * [Vykdoma] {{ll|Help:Extension:Translate/Search|2=Paieška}} * {{ll|Help:Extension:Translate/Off-line translation|2=Autonominis vertimas}} * [Vykdoma] {{ll|Help:Extension:Translate/Glossary|2=Žodynas}} == Vertimo administratoriams == * {{ll|Help:Extension:Translate/Page translation example|2=Kaip paruošti puslapį vertimui}} [Pamoka] * {{ll|Help:Extension:Translate/Page translation administration|2=Puslapio vertimo administracija}} * {{ll|Help:Extension:Translate/Unstructured element translation|2=<span lang="en" dir="ltr" class="mw-content-ltr">Interface message groups (localised sidebar, main page and templates)</span>}} [Pamoka] * [Vykdoma] {{ll|Help:Extension:Translate/Group management|2=<span lang="en" dir="ltr" class="mw-content-ltr">Message group management</span>}} * {{ll|Help:Extension:Translate/Group configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">YAML configuration format</span>}} * {{ll|Help:Extension:Translate/Group configuration example|2=<span lang="en" dir="ltr" class="mw-content-ltr">How to write YAML configuration for file based message groups</span>}} [Pamoka] <div lang="en" dir="ltr" class="mw-content-ltr"> === Reference documents for developers === </div> * {{ll|Help:Extension:Translate/Installation|2=Įdiegimas}}{{int|and}}{{int|word-separator}}{{ll|Help:Extension:Translate/Configuration|2=Konfigūracija}} - <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|MediaWiki Language Extension Bundle}} should be enough in most cases.</span> * {{ll|Help:Extension:Translate/Translation memories|2=Vertimo prisiminimai}} * {{ll|Help:Extension:Translate/Developer guide|2=<span lang="en" dir="ltr" class="mw-content-ltr">Developer guide</span>}} * [Vykdoma] {{ll|Help:Extension:Translate/Components|2=<span lang="en" dir="ltr" class="mw-content-ltr">Translate explained for developers</span>}} ** {{ll|Help:Extension:Translate/Hooks|2=Kabliukai (hooks)}} ** [Vykdoma] {{ll|Help:Extension:Translate/Message groups|2=Pranešimų grupės}} ** [Vykdoma] {{ll|Help:Extension:Translate/File format support|2=Failų formatų palaikymas}} ** {{ll|Help:Extension:Translate/Translation_aids|2=<span lang="en" dir="ltr" class="mw-content-ltr">Translation aids</span>}} ** [<span lang="en" dir="ltr" class="mw-content-ltr">Unwritten</span>] {{ll|Help:Extension:Translate/API|2=<span lang="en" dir="ltr" class="mw-content-ltr">action API</span>}} ** {{ll|Help:Extension:Translate/Insertables|2=<span lang="en" dir="ltr" class="mw-content-ltr">Insertables</span>}} ** {{ll|Help:Extension:Translate/Command line scripts|2=<span lang="en" dir="ltr" class="mw-content-ltr">Command line scripts</span>}} ** {{ll|Help:Extension:Translate/Process flow in MediaWiki jobs|2=<span lang="en" dir="ltr" class="mw-content-ltr">Process flow in MediaWiki jobs</span>}} - <span lang="en" dir="ltr" class="mw-content-ltr">Describes what jobs are involved when a page is marked for translation or a section is translated</span> ** {{ll|Help:Extension:Translate/Translation memory architecture|2=<span lang="en" dir="ltr" class="mw-content-ltr">Translation memory architecture</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Related === </div> * {{ll|Extension:TranslationNotifications#Special_pages}} * {{ll|Localisation/Tutorial}} - <span lang="en" dir="ltr" class="mw-content-ltr">General localisation tutorial for developers, for use at hackathons & trainings</span> * {{ll|Extension:TranslateSvg}} - <span lang="en" dir="ltr" class="mw-content-ltr">Adds support for translating SVG files</span> * {{ll|Universal Language Selector}} - <span lang="en" dir="ltr" class="mw-content-ltr">Provides web fonts and input methods</span> * [[m:Special:MyLanguage/Translatability|m:Translatability]] – <span lang="en" dir="ltr" class="mw-content-ltr">things to think about when creating pages or processes on multilingual wikis</span> * [[m:Tech/Translators/List|m:Tech/Translators/List]] - Įtraukite save į aktyvių techninių vertėjų sąrašą [[Category:Extension:Translate{{#translation:}}| ]] e9ic09orxeutfr4p3yuhfrjif721cc0 Template:PD Help Page/id 10 132423 5386559 5359583 2022-07-28T15:04:23Z 140.213.48.138 wikitext text/x-wiki <languages/> <onlyinclude>{{#switch: | = <templatestyles src="Template:PD Help Page/styles.css"/><table class="template-pd-help-page"><tr> <td class="icon-cell">[[File:PD-icon.svg|30px|link=|alt=PD]]</td> <td>'''Catatan:''' Ketika anda menyunting halaman ini, anda setuju untuk memberi izin kontribusi anda tunduk di bawah [https://creativecommons.org/publicdomain/zero/1.0/{{cclang}} CC0]. Lihat [[Special:MyLanguage/Project:PD help|Situs Bantuan Domain Publik]] untuk informasi lebih lanjut. {{#if:{{{imported|}}}|<br />'''Beberapa revisi lama untuk halaman ini telah diimpor di bawah lisensi CC BY-SA. Hanya kontribusi baru yang DP.'''|}} ---- <div class="plainlinks">{{center|{{small|[{{FULLURL:Special:Translate/page-Template:PD Help Page|action=translate&task=view}} {{int:translate-taction-translate}}]}}}}</div> </td> <td class="icon-cell">[[File:PD-icon.svg|30px|link=|alt=PD]]</td> </tr></table> | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:PD Help Page|noshift=1|uselang={{int:lang}}}} }}</onlyinclude> {{Documentation|content= {{Uses TemplateStyles|Template:PD Help Page/styles.css}} Pemberitahuan {{ll|Project:PD help}}. == Contoh == * <code><nowiki>{{PD Help Page}}</nowiki></code> {{PD Help Page}} * <code><nowiki>{{PD Help Page|imported=1}}</nowiki></code> {{PD Help Page|imported=1}} == TemplateData == {{PD Help Page/doc}} }} [[Category:Templates{{#translation:}}]] lkf4y7sxnrhrkkdqh3qf9vb4qn2xhah Manual:Installing MediaWiki/es 100 145927 5387495 5384968 2022-07-28T22:45:20Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">MediaWiki puede ser difícil de instalar para un usuario promedio que no tiene experiencia con Apache, PHP y MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Descarga el software MediaWiki == Descarga el archivo comprimido de MediaWiki desde [[Special:MyLanguage/Download|la página oficial de descarga]]. Por lo general, si estás utilizando un entorno de producción, querrás usar la versión estable más reciente, que es MediaWiki {{MW stable release number}}. <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">Los archivos descargados están en formato <code>.tar.gz</code>, por lo que tendrás que descomprimirlos antes de usarlos.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span class="mw-translate-fuzzy">Esto lo puedes hacer en local, y subir posteriormente los archivos por FTP, o bien directamente en el servidor.</span> En Windows puedes hacerlo con programas como [https://www.7-zip.org/ 7-Zip] (libre), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] o [https://www.izarc.org/ IZArc] (libre). En Linux y Mac OS X puedes descomprimirlo usando este comando: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == Subir los archivos al servidor == <div class="mw-translate-fuzzy"> Si aun no has subido los archivos al servidor web, este es el momento de hacerlo. </div> Puedes subir los archivos al directorio web de tu servidor de una de estas formas: # Copiando directamente la carpeta descomprimida o <div class="mw-translate-fuzzy"> # Mediante un cliente FTP como [https://filezilla-project.org/ FileZilla] (Software de código abierto, Windows, OSX y Linux) o [https://cyberduck.io/ Cyberduck] (OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> Si la herramienta que usas para subir los archivos tiene una opción "Cambiar a minúsculas los nombres de archivos", debes desactivarla. <span class="mw-translate-fuzzy">Si has instalado Apache, el directorio correcto se especifica en el archivo <code>httpd.conf</code> (es la directiva [$docroot DocumentRoot], que es normalmente $1 o {{$2|directorio-apache}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Nota: Esto cambió en Ubuntu 14.04 con Apache 2.4.7 donde el archivo principal de configuración de Apache y los directorios se encuentran en <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Cambia el nombre de la carpeta de la instalación de MediaWiki a lo que quieras que se vea en la URL del wiki. <span class="mw-translate-fuzzy">Si el servidor web se ejecuta como <code>http://localhost</code> por ejemplo, cambiar el nombre al directorio por <code>/w/</code> significa que podrás acceder al wiki usando <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span class="mw-translate-fuzzy">'''No uses <code>/wiki/</code> si deseas utilizarlo como [[Special:MyLanguage/Manual:Short URL|URL corta]].'''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Crear una base de datos == </div> <div class="mw-translate-fuzzy"> MediaWiki te preguntará por un nombre para la base de datos y un nombre de usuario, y tratará de crearlos si no existen. </div> <div class="mw-translate-fuzzy"> Si ya dispones de un servidor de base de datos y conoces la contraseña de root, el script de instalación de MediaWiki puede crear la nueva base de datos por ti. </div> <div class="mw-translate-fuzzy"> Si no conoces la contraseña de root, por ejemplo si estás en un alojamiento compartido, ahora tendrás que crear una nueva base de datos. </div> <span class="mw-translate-fuzzy">En la actualidad, debes utilizar SQLite, MariaDB/MySQL o PostgreSQL para almacenar el contenido del wiki.</span> <span class="mw-translate-fuzzy">Si no estás seguro sobre qué base de datos escoger, utiliza MariaDB la cual es la mejor soportada por MediaWiki.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">En la página de instalación, tendrás que elegir un nombre para la base de datos (que puede ser cualquier cosa) y el directorio de la base de datos SQLite.</span> Para el directorio de la base de datos, el instalador intentará utilizar un subdirectorio fuera de la raíz y crearlo si es necesario. Si este directorio no es seguro (por ejemplo, es accesible desde la web), cámbialo manualmente para evitar que sea accesible por todo el mundo en la web. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Consulta la documentación correspondiente.</span> <span class="mw-translate-fuzzy">Como alternativa, contacta con tu proveedor de alojamiento para que ellos creen la cuenta de usuario por ti.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Si tu base de datos no está en el mismo servidor que el servidor web, tendrás que otorgarle el nombre del servidor web de forma correcta (mediawiki.example.com en este ejemplo) de esta forma: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span class="mw-translate-fuzzy">MySQL/MariaDB en UNIX/Linux registra todas las consultas enviadas a la base de datos en un archivo, incluyendo la contraseña que usaste para crear la cuenta de usuario.</span> <span class="mw-translate-fuzzy">Si esto te incomoda, borra el archivo <code>.mysql_history</code> después de ejecutar estas consultas:</span>}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Si utiliza Postgres, tendrá que o bien tienen una base de datos y el usuario creado para usted, o simplemente proporcionar el nombre de un usuario con privilegios de Postgres "Superuser" en el formulario de configuración.</span> <span class="mw-translate-fuzzy">A menudo, este es el usuario de base de datos llamado postgres.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (ahora introduce la contraseña) createdb -O wikiuser my_wiki O superusuario (por defecto postgres) ejecutar los siguientes comandos en la base de datos del sistema: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> Ten en cuenta la [[phab:tag/postgreSQL|lista de problemas conocidos cuando uses MediaWiki con PostgreSQL]]. {{anchor|Run the installation script}} == Ejecutar el script de instalación == <div class="mw-translate-fuzzy"> Una vez que todos los pasos anteriores se han completado, puedes completar la instalación a través de un navegador web, accediendo a la URI <code>index.php</code> en el navegador. Consulte las instrucciones mencionadas en {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> == Pasos adicionales == </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == !Mantente al día! == Una vez esté instalado, ¡asegúrate de estar al día con las publicaciones de software, y mantén tu servidor seguro! {{Clickable button 2|<span class="mw-translate-fuzzy">[[mail:mediawiki-announce|Suscríbete a nuestro boletín de anuncios en lista de correos.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=Cuando crees la cuenta de root, recuerda la contraseña que introduzcas aquí.}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Vease también == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] fzgaov494dgk81e87of04c9fq00eoc7 Manual:Installation guide/zh 100 162290 5386677 5381114 2022-07-28T17:14:39Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/zh]] qrimzzgio3038yaymj8xbmi9ea03i0e Parsoid/Deployments 0 163731 5387086 5369658 2022-07-28T20:23:27Z Arlolra 270019 /* Jul 26 - Jul 28: v0.16.0-a17 as part of 1.39.0-wmf.22 */ wikitext text/x-wiki Planned deployments, linked from [[wikitech:Deployments]]. For a list of past deployments, look for 'parsoid' in [[wikitech:Server Admin Log]]. For the current train deploy schedule, see [[MediaWiki 1.39/Roadmap#Schedule for the deployments]]. See [[wikitech:Parsoid#Deploying changes]] to learn how to deploy a new version of Parsoid. __TOC__<!-- This sentence is so that the TOC doesn't need to be relocated after adding a deploy to the list in VE. --> == Jul 26 - Jul 28: {{Done|v0.16.0-a17 as part of 1.39.0-wmf.22}} == * Followup on d28f22a2: Additional fixes * Additional normalization of HTML to improve diff classification * parserTests.txt: Add test case for piped link using {{!}}, [[phab:T290526|T290526]] * e2e test: cover etag handling with structure test, [[phab:T311819|T311819]] * Allow multivalues in rel attributes, [[phab:T186241|T186241]] * Remove isExtendedAnnotationWrapperTag utility * Generalize DOMTraversing with state * Implement T2529 sol-nl hack in Parsoid's native template expansion path, [[phab:T241150|T241150]] == Jul 19 - Jul 21: {{Done|v0.16.0-a16 as part of 1.39.0-wmf.21}} == * Implement relative redirects in parsoid extension., [[phab: T311867| T311867]] * composer.json: Allow wikimedia/scoped-callback v4.0.0 * Add type hints to match built-in interface for php 8.1, [[phab: T289879| T289879]] * Fix bug in Parsoid's Poem implementation, [[phab: T311953| T311953]] * Omit DisplaySpace processing inside pre nodes, [[phab: T305658| T305658]] * Use core's TransformHandler and ParsoidHandler, [[phab: T310467| T310467]] == Jul 5 - Jul 7: {{Done|v0.16.0-a15 as part of 1.39.0-wmf.19}} == * Revert "Only disable nested template expansion when not native" * ParserTests: Update <tag> hook implementation to match core * Fix edge case bug in TableFixups exposed by integrated parsertest run * ParserTests: Redlink missing templates. Don't output empty spans. * Fix bug in expanding and encapsulating params * Only disable nested template expansion when not native * TemplateHandler: Document decoupled template processing model * Minor: Fix comment by removing stray JS code line == Jun 28 - Jun 30: {{Done|v0.16.0-a14 as part of 1.39.0-wmf.18}} == * Bump output content version to 2.5.0, [[phab: T273505| T273505]] * Account for format being in gallery media options, [[phab: T214601| T214601]] * Use caption as alt on imgs when not present and caption isn't visible, [[phab: T297443| T297443]], [[phab: T162360| T162360]], [[phab: T63566| T63566]] * Consolidate media types to mw:File, [[phab: T273505| T273505]] == Jun 21 - Jun 23: {{Done|v0.16.0-a13 as part of 1.39.0-wmf.17}} == * Change DOMTraverser to stay within the subtree of the passed in node * ParserTests: Make <indicator> mocks match output in integraged mode * Avoid a call to get file info if there are no valid containers * TestRunner.php: Update comments w/r/t interwiki setup * TemplateHandler: Check explicitly for an empty string, [[phab:T310667|T310667]] * Stop recognizing noicon and noplayer media options, [[phab:T134880|T134880]] * Copy changes to core api tests to soften schema version check * Make end-to-end API test more robust == Jun 14 - Jun 16: {{Done|v0.16.0-a12 as part of 1.39.0-wmf.16}} == * Followup on e71d5197: Check for nulls before calling traverse * Followup to 0042a88e: Fix broken usage of DOMTraverser, [[phab: T310220| T310220]] * Add forward compatibility to avoid serializing alt from caption, [[phab: T297443| T297443]], [[phab: T162360| T162360]], [[phab: T63566| T63566]] * Strip parser function prefix from content, [[phab: T310025| T310025]] * Get rid of nonsensical complexity in TemplateHandler, [[phab: T303368| T303368]] * Colon escape is already stripped in getWikiLinkTargetInfo * Allow colon escape after interwiki prefix, [[phab: T286425| T286425]] * Assure we have a figure if $forceBlock is set when rendering media, [[phab: T309901| T309901]] == Jun 7 - Jun 9: {{Done|v0.16.0-a11 as part of 1.39.0-wmf.15}} == * WTS: Minor cleanup for code readability * WTS: Remove a few unnecessary PORT-FIXME comments * Only adjust for parser func safesubst in tpl target resolution, [[phab:T309405|T309405]] * Remove priority hints and element timing from test normalization, [[phab:T308621|T308621]], [[phab:T308707|T308707]] * Account for multiple active formatting elts reopened in media == May 31 - June 2: {{Done|v0.16.0-a10 as part of 1.39.0-wmf.14}} == * StubMetadataCollector: fix "already set" test for MERGE_STRATEGY_WRITE_ONCE * AutoLoader: use registerNamespaces instead of $psr4Namespaces * Add forward compatibility to serialize mw:File, [[phab: T273505| T273505]] * Set title for tooltips if caption isn't visible, [[phab: T297443| T297443]], [[phab: T108380| T108380]] * SiteConfig: Clear extension cache on extension registration == May 24-26: {{Done|v0.16.0-a9 as part of 1.39.0-wmf.13}} == * Improve robustness of tagging misnested link-in-link content, [[phab:T307412|T307412]] == May 17-19: {{Done|v0.16.0-a8 as part of 1.39.0-wmf.12}} == * Remove guard against missing figcaption * Set a title attribute for files linking to pages * Revert "Lint captions on inline media without an explicit alt options", [[phab: T297443| T297443]] * Hoisting references outside of links, [[phab: T301293| T301293]] * Resolve linter test port-fixme, [[phab: T237463| T237463]] * Use isset to eliminate warnings * Cleanup variable naming and documentation for clarity * Cleanup confusing halign setting * Don't escape extension tags shadowing html5 tags if found in source, [[phab: T300436| T300436]] * Lint html stashed in data-mw of mw:Extension/references, [[phab: T214994| T214994]] * Only lint content defined by a specific ref, [[phab: T301293| T301293]], [[phab: T214994| T214994]] * Prioritize body->html over body->id when diffing refs * Fix using sort order from data-mw when serializing template params, [[phab: T304730| T304730]] * Move escapeNowikiTags to WTSUtils * Escape dom elements with extension tag names when serializing, [[phab: T300436| T300436]] == April 26-28: {{Done|v0.16.0-a7 as part of 1.39.0-wmf.9}} == * Use DOMRangeBuilder "top level range" algorithm for nested ranges, [[phab: T306186| T306186]] == Not deployed separately: v0.16.0-a6 == * Lint defined width for framed or manualthumb formats * Add lint test for multiple media formats defined, [[phab:T305641| T305641]] * Drop sizing when serializing frame or manualthumb, [[phab:T64938| T64938]] * Manualthumb does not do automatic scaling, [[phab:T305759| T305759]], [[phab:T64938| T64938]] * Manualthumb is a format, like the others, [[phab:T305641| T305641]], [[phab:T305759| T305759]] * Stop using ParsoidServices * Add check for bad files, [[phab:T75581| T75581]] * Apply manualthumb consistently across media types, [[phab:T302114| T302114]] * Don't rely on the link element to roundtrip the |page= option, [[phab:T259931| T259931]] == April 12-14: {{Done|v0.16.0-a5 as part of 1.39.0-wmf.7}} == * ParserTests: Don't normalize style attributes * ParserTests: Bunch of minor tweaks / refactoring * Test.php: Remove Env references + make a function public * Run `npm audit fix` * ParserTests: Add a normalizeWT helper to Test.php * Followup to 11cde591: Update rt-testing node.js scripts as well * Remove ServiceWiring and Config from Parsoid extension * Don't strip mw:IndentPre meta tags till the very end, [[phab:T305597|T305597]] * Making Translate extended ranges uneditable - fixing bugs, [[phab:T305066|T305066]] * Revert "Adjust whiteline handling around table for extended annotation ranges" * ParserTests: Extract HTML normalization to the Test.php class * Lint invalid upright options, [[phab:T216003|T216003]] * Drop ip-utils 3.x compatibility, core is on 4.0.0 now * Making Translate extended ranges uneditable, [[phab:T305066|T305066]] * Adjust whiteline handling around table for extended annotation ranges == April 9: {{In progress|v0.15.0-a27 on REL1_38 branch}} == Cherry-picked changes since v0.15.0-a26: * Making Translate extended ranges uneditable - fixing bugs, [[phab:T305066|T305066]] * Making Translate extended ranges uneditable, [[phab:T305066|T305066]] * Followup to 29a92a69: Fix missing unwrap invocation in PWrap * PWrap: Improve p-wrapping behavior to minimize DOM range expansion * PWrap: Improve readability by renaming and documenting a helper * Make the `null` value clearer in PWrap * Revert "Add temporary ParsoidSiteConfigInit hook", [[phab:T303029|T303029]] == April 5-7: {{Done|v0.16.0-a4 as part of 1.39.0-wmf.6}} == * Add a class for unwrapping of optional nodes in dom pwrapper * Additional simplification of PreHandler * Fix off-by-1 DSR error by cleaning up and simplifying PreHandler, [[phab: T277415| T277415]] * Followup to 29a92a69: Fix missing unwrap invocation in PWrap * PWrap: Improve p-wrapping behavior to minimize DOM range expansion * Add base constructors for abstract Config types * PWrap: Improve readability by renaming and documenting a helper * Make the `null` value clearer in PWrap * Log extra info if we're unable to get link source when bailing, [[phab: T302092| T302092]] * Use in_array instead of array_search, where possible * Followup of bb14815b: Refine TemplateHandler::convertToString == March 30: {{Done|v0.15.0-a26 on REL1_38 branch}} == Cherry-picked changes since v0.15.0-a25: * Add a class on the span representing the broken media element, [[phab:T304010|T304010]], [[phab:T270150|T270150]] * Fix complaint that test did not perform any assertions * Document known failures testing functionality * Drawings are derived and therefore always need the thumbnail treatment * Add html/parsoid sections for svg rendering by page language tests, [[phab:T208620|T208620]] * Add baseconfig for ruwiki and refresh existing baseconfigs * Support rendering SVG based on page language, [[phab:T208620|T208620]] * Use the check from RevisionRecord::getContent, [[phab:T273111|T273111]] == Mar 29-31: {{Done|v0.16.0-a3 as part of 1.39.0-wmf.5}} == * Improve performance of getAutoUrlTerminatingChars * Add badFile to standalone response, [[phab:T75581|T75581]] * Sync mediaParserTests with core * Document timing metrics we collect == Mar 22-23: {{Done|v0.16.0-a2 as part of 1.39.0-wmf.4}} == * Collect html2wt metrics on non-selser path as well * Sync parser tests files with core, [[phab:T295187|T295187]] * Add a class on the span representing the broken media element, [[phab:T304010|T304010]], [[phab:T270150|T270150]] == Mar 22: {{Done|v0.16.0-a1 as part of 1.39.0-wmf.3}} == * Fix complaint that test did not perform any assertions * Document known failures testing functionality * Drawings are derived and therefore always need the thumbnail treatment * Add html/parsoid sections for svg rendering by page language tests, [[phab:T208620|T208620]] * Add baseconfig for ruwiki and refresh existing baseconfigs * Support rendering SVG based on page language, [[phab:T208620|T208620]] * Use the check from RevisionRecord::getContent, [[phab:T273111|T273111]] Also, the following patches, which were tagged in v0.15.0-a25 but not released: * Create abstract marker interface for the PageConfigFactory type * [take 2] Expose ParserOutput/ContentMetadataCollector via ParsoidExtensionAPI == Unreleased: v0.15.0-a25 == This release was tagged in order to allow CI to test patches which moved portions of Parsoid to core. * Create abstract marker interface for the PageConfigFactory type * [take 2] Expose ParserOutput/ContentMetadataCollector via ParsoidExtensionAPI == Mar 15-17: {{Done|v0.15.0-a24 as part of 1.38.0-wmf.26}} == * Allow wikimedia/object-factory ^4.0.0 * Env isn't needed to dump diff marks * Fix dumping diff marks * Remove seemingly unnecessary template target resolution * Add a class for the return value of the template expand call * Construct TemplateEncapsulator earlier and pass it around * Split template expansion / preprocessing from encapsulation == Mar 8-10: {{Done|v0.15.0-a23 as part of 1.38.0-wmf.25}} == * Rename frame method s/fetchArg/expandArg/ * PreHandler: s/MULTILINE_PRE/SOL_AFTER_PRE to better reflect state * Run ParserBeforePreprocess hook in DataAccess::preprocessWikitext * Fix Grammar to not assume that a Token is returned, [[phab:T303057|T303057]] * Do not break heading detection on annotations, [[phab:T296412|T296412]] * html2wt: Use info level for unactionable Cite logspam caused by CX usage * DOMDiff: Don't attempt to mark DOM Fragments, [[phab:T302885|T302885]] * Remove obsolete comment from parserTests SiteConfig * Make processExtensionModule consistent for ease of reading * Fix unsetting native extension tags in parserTests * AttributeExpander: tokensToString invalidates srcOffsets * AttributeExpander: Update token attributes/tsr correctly after processing, [[phab:T299374|T299374]] * Add mw-file-description class on links to the file description page, [[phab:T292657|T292657]] * Followup to df3124f9: Fix bad refactoring * PreHandler: s/popLastNL/pushLastNL * PreHandler: Get rid of recursion in onAny handler * Clean up TemplateHandler::resolveTemplateTarget == Mar 1-3: {{Done|v0.15.0-a22 as part of 1.38.0-wmf.24}} == * Account for strtok boolean return type, [[phab:T302093| T302093]] * Change Config/* classes to be abstract classes instead of interfaces, [[phab:T261161| T261161]] * Move bulk of template arg expansion to the Frame class * Add logging of nested annotation tag removals * Add description links consistently * Don't repeat request for width if file is missing * Only define our services if they haven't already been moved to core, [[phab:T302118| T302118]] * Move sanitization to when we're actually setting an external link == Feb 22-24: {{Done|v0.15.0-a21 as part of 1.38.0-wmf.23}} == * ContentMetadataCollector: Use PHP constants to store merge strategy strings * Tweak signature of ContentMetadataCollector::addCategory() * Revert part of 55da3090: Setting up template args exposes other bugs, [[phab:T301948|T301948]], [[phab:T302007|T302007]], [[phab:T301986|T301986]] * Benchmark read view content stripping, [[phab:T272331|T272331]] * Cleanup unnecessary data-parsoid="{}" in parser tests. * Minor cleanup in TableFixups & WrapSectionsState for future DRYing * Followup to 50461b53: Fixup code updating transclusion parts, [[phab:T301524|T301524]] * Tweak parameters for API requests to add more metadata * Don't add synthetic magic words to the output * Move ::appendToHead() into DOMUtils * Move substTopLevelTemplates logic to Core/ == Feb 15-17: {{Done|v0.15.0-a20 as part of 1.38.0-wmf.22}} == * Minor improvements to the ContentMetadataCollector interface * Move ContentModelHandler back to Core/ * Consolidate some files under src/Wikitext/ * Get rid of the ExtensionContentModelHandler * Move ContentModelHandler stuff from Core/ to Config/ * SiteConfig handler caching: Use an instance variable vs a static * Cache extension tag handlers * Fix old wikitext escaping bug, [[phab:T277592|T277592]] * Add preprocessWikitext to ParsoidExtensionAPI * Introduce Parsoid\Core\Wikitext to hold wikitext concepts / operations * Don't add synthetic categories from template expansion either * Ensure frame args are properly set up in the pipeline * Get rid of unused noDataAccess() mode * Reorganize code in TemplateHandler::onTemplate for clarity * Don't add synthetic categories to output HTML * Get rid of optionalNewlines production from the grammar added in 6f4cd078 * build: Updating dependencies * Moving Translate annotation declaration to the Translate repository, [[phab:T295170|T295170]] == Feb 8-10: {{Done|v0.15.0-a19 as part of 1.38.0-wmf.21}} == * Update Parsoid's CoreMetadataCollector to reflect patches made to core * If we aren't expanding templates don't bother with the template name * Move convertToString outside of call to encapTokens * Simplify TemplateHandler::convertAttribsToString * Assert that we aren't expanding an already expanded token, [[phab:T300393|T300393]] * Minor tweak to function name in ParsoidExtensionAPI * TemplateHandler: Simplify resolveTemplateTarget * Augment the CompoundTemplateInfo to indicate if it came from a param * Get rid of retry signal from TokenHandlerResult * Don't retry AttributeExpansion on templated attribute tokens, [[phab:T300393|T300393]] * Minor tweaks to lookupArg * Set pipeline opts for attribute expander used in TemplateHandler * Improve output of regression-testing.php script * Simplify bailTokens == Feb 1-3: {{Done|v0.15.0-a18 as part of 1.38.0-wmf.20}} == * Add temporary ParsoidSiteConfigInit hook * Allow wikimedia/ip-utils ^4.0.0 * Support lang= option for SVGs, [[phab:T208620|T208620]] * Better handling of templated annotation attributes, [[phab:T299375|T299375]] * Initialize 'inTemplate' pipeline option always and fix usages, [[phab:T226437|T226437]] * ParserPipelineFactory: Remove duplicate call to defaultOptions == Jan 25-27: {{Done|v0.15.0-a17 as part of 1.38.0-wmf.19}} == * WikiLinkHandler: Reprocess incorrect tokens to the right stage, [[phab:T299185| T299185]], [[phab:T299454| T299454]], [[phab:T299457| T299457]] * Use MediaWiki's object factory when instantiating extensions * Shuttle tokens to the end of the stage == Jan 20: {{Done|v0.15.0-a16 to beta}} == Parsoid v0.15.0-16 was tagged in order to push out CI changes for [[phab:T240775]]/[[gerrit:753824]] It should be replaced with a thoroughly tested release build before the next train deploy. * Simplify DOM class aliases., [[phab:T240775|T240775]] == Jan 18-20: {{Done|v0.15.0-a15 as part of 1.38.0-wmf.18}} == * Clarify a comment around special case for <nowiki>{{!}}</nowiki>, [[phab:T299311|T299311]] * Revert "Remove special case for <nowiki>{{!}}</nowiki> magic word", [[phab:T299311|T299311]] * Stop emitting "inline-media-caption" lints, [[phab:T297443|T297443]], [[phab:T299302|T299302]] * Fix parsing of interlanguage links with spaces, [[phab:T156308|T156308]] * WikitextSerializer: Fix production crasher, [[phab:T299196|T299196]] * Don't log wt2html metrics for linter requests + other tweaks * Merge the first two token transform stages == Jan 11-14: {{Done|v0.15.0-a14 as part of 1.38.0-wmf.17}} == '''Big wt2html changes''' * Detect auto-insertion and tag deletion in RemexPipeline, [[phab:T221145|T221145]] * Followup to 819630e5: Match handling of mixed-syntax tags * Followup to 819630e5: Make endTSR behave like tsr on mw:EndTag metas * Followup to 819630e5: Handle autoInsertedFlags on tokens * Partially mimic impact of mw:TSRMarker metas on MigrateTrailingNLs '''Other notable changes''' * Remove special case for <nowiki>{{!}}</nowiki> magic word * TSP: Process retokenized tokens through TTM stages 1 & 2, [[phab:T297922|T297922]] * SiteConfig: Address old FIXME related to computing function synonyms * TableFixups: Minor perf tweaks and cleanup, [[phab:T298665|T298665]] * TableFixups: Log error on reparse failure, don't crash * Logging: Add pages with wt2html timePerKB > 500 ms to slow-parsoid log * Add metrics to track time spent linting * Add strict_type declaration to a number of files missing them * Resolve a few more stale PORT-FIXMEs + update method docs * Followup to 78e60013: Eliminate spurious semantic diff reports * Replace usages of deprecated wfWikiID(), [[phab:T298059|T298059]] * Use ParserOptions::newFromAnon instead of ParserOptions::newCanonical * Remove scrubWikitext as an option, [[phab:T297298|T297298]] * Lint captions on inline media without an explicit alt options, [[phab:T297443|T297443]] ==Deployments from previous years == {{Special:PrefixIndex/Parsoid/Deployments/}} [[Category:Parsoid]] flkzie1ar0hsls7iy3jiojoh6dbdyvn Manual:Installation guide/en 100 184908 5386646 5381082 2022-07-28T17:14:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/en]] ep2omt629u3b99k59akhk57r2ef2gew Translations:Manual:Installation guide/11/en 1198 184919 5387273 4699614 2022-07-28T21:53:26Z Baris6161TURK 17188421 wikitext text/x-wiki Image thumbnailing requires additional programs. $1 (required by VisualEditor) and other services have their own requirements. 9p35obodfe3fpnron0hsqmjgpqd1pmy Translations:Manual:Installation guide/17/cs 1198 185032 5386461 4814790 2022-07-28T14:24:45Z ENeRZet 17359278 wikitext text/x-wiki Tyto instrukce jsou úmyslně velmi stručné. 6iu9n7lpyfdz2zho8j8v6m3hqwc3w4b Translations:Manual:Installation guide/29/cs 1198 185044 5386467 4994753 2022-07-28T14:26:46Z ENeRZet 17359278 wikitext text/x-wiki Následující stránky popisují některé pokročilejší konfigurační možnosti: p259j8ysm8b3prqmyuu4qhwa7zxcivw Translations:Manual:Installation guide/11/da 1198 185074 5387274 4700832 2022-07-28T21:53:38Z Baris6161TURK 17188421 wikitext text/x-wiki Miniaturebillede kræver yderligere programmer. $1 (kræves af VisualEditor) og andre tjenester har deres egne krav. po32pvibrcv6j6jxljdoe52fsovy5tn Translations:Manual:Installation guide/11/de 1198 185118 5387275 4700834 2022-07-28T21:53:52Z Baris6161TURK 17188421 wikitext text/x-wiki Für Vorschaubilder und $texvc-Unterstützung werden zusätzliche Programme benötigt. $1 (erforderlich für den VisualEditor) und andere Dienste haben ihre eigenen Anforderungen 726rlv0p2cllplbv5tu1amp629pcvd2 Translations:Manual:Installation guide/11/fr 1198 185208 5387276 4700840 2022-07-28T21:54:10Z Baris6161TURK 17188421 wikitext text/x-wiki La mise en vignette des images nécessite des programmes supplémentaires. $1 (requis par [[$visualeditor|VisualEditor]]) et d'autres services ont leurs besoins propres. hbd6np0un40d49y8u4yvu9teor4hdk1 5387300 5387276 2022-07-28T21:59:33Z Baris6161TURK 17188421 wikitext text/x-wiki La mise en vignette des images nécessite des programmes supplémentaires. $1 (requis par VisualEditor) et d'autres services ont leurs besoins propres. frxw1p5jmlyo0l0pkt71nwigzo0evqk Translations:Manual:Installation guide/11/zh 1198 188704 5387277 4700884 2022-07-28T21:54:23Z Baris6161TURK 17188421 wikitext text/x-wiki 缩略图需要扩展程序支持。$1(用于可视化编辑器)及其他服务亦有各自配置需求。 1a5witx9yullrekwwe2303p5xpnaquv Translations:Download/12/cs 1198 194318 5386448 5006081 2022-07-28T14:09:01Z ENeRZet 17359278 wikitext text/x-wiki Někteří uživatelé mohou raději přeskočit ruční instalaci pomocí předem integrovaného [[$1|softwarového zařízení]] nebo [[$2|hostingových služeb]] MediaWiki. rq0v39tj2uaca2k765i5aifwexcobzd Translations:Download/6/zh 1198 196601 5386446 5301579 2022-07-28T14:08:12Z 103.173.255.162 wikitext text/x-wiki === 从Git下载(开发者) === dxaczub9qb5iz4hssx1niluoz433iuc Manual:Installation guide/el 100 197880 5386645 5381081 2022-07-28T17:14:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/el]] rc0bwx1eb3q9natz7faf0cv7snvimkj 5386686 5386645 2022-07-28T17:23:23Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/el]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Translations:Project:Language policy/12/ru 1198 200060 5386713 1939287 2022-07-28T18:09:52Z Артём 13327 17625157 wikitext text/x-wiki * Все не-англоязычные тексты должны размещаться на соответствующих подстраницах английской версии. Например, перевод $1 на французский должен называться $2 (а не Help:Sommaire, Aide:Sommaire или Help:Sommaire/fr). l8iylot2s2e2xtgukajccst1zyjo08l Translations:Project:Language policy/16/ru 1198 200082 5386715 2569028 2022-07-28T18:10:11Z Артём 13327 17625157 wikitext text/x-wiki * Для более полного представления прочтите [[$1|основную справку]], [[$help-ext-translate-2|руководство переводчика]], [[$help-ext-translate-3|руководство по разметке страниц]] и [[$help-ext-translate-4|руководство для администратора перевода]]. htu8oxbzx51rcldrer1p5825kpyottp Translations:Manual:Installation guide/11/pt-br 1198 202025 5387278 4700861 2022-07-28T21:54:37Z Baris6161TURK 17188421 wikitext text/x-wiki A miniaturização de imagens requer programas adicionais. O $1 (exigido pelo VisualEditor) e outros serviços têm os seus requisitos próprios. 5s3wa61n0dui6p6cpkusn36ofdkcs1n HHVM 0 203100 5387445 5240433 2022-07-28T22:31:26Z Shirayuki 472859 make untranslatable wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = <translate><!--T:27--> Support in MediaWiki for HHVM (HipHop Virtual Machine) and deployment to the Wikimedia cluster</translate> | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<translate><!--T:28--> See [[<tvar name=1>Special:MyLanguage/HHVM/About</tvar>|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[<tvar name=blog>https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/</tvar> How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work.</translate> {{note|1=<translate><!--T:26--> In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref> After discussion<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See {{phabricator|T176209}} and {{phabricator|T192166}}.</translate>}} <translate><!--T:3--> '''[[w:HHVM|HHVM]]''' is a PHP interpreter tool (concretely a virtual machine that compiles PHP bytecode to native instructions at runtime) that was deployed on Wikimedia servers in 2014, decreasing the loading time for: any page you view while logged in, and for saving pages that you've edited whether you are logged in or not.</translate> <translate> == Roadmap == <!--T:4--> </translate> <translate><!--T:5--> HHVM is a new way for websites to run [[<tvar name=1>Special:MyLanguage/Manual:What is MediaWiki?</tvar>|MediaWiki]] (written in [[w:PHP|PHP]]).</translate> <translate><!--T:29--> It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT).</translate> <translate><!--T:30--> HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.</translate> <translate> <!--T:6--> This page is about Wikimedia-sponsored work on HipHop support in MediaWiki, and its deployment to Wikimedia production wikis. <!--T:7--> Historically, the HipHop compiler was a project by Facebook which involved compiling PHP code into C++ for purposes of speeding up the language. Facebook has since abandoned this project, and now their development efforts are focused on HHVM itself instead. <!--T:8--> Here is the general plan for deploying HHVM to the production cluster in 2014: <!--T:9--> * Deployment to Beta Cluster (currently ongoing work, in parallel with other work) {{done}} * Week of July 21: deployment to a few job runners in production {{done}} * Deploy to test.wikipedia.org application server {{done}} * Deploy Varnish module allowing partial deployment to a fraction of application servers{{Done}} * Limited deployment to small number of application servers {{Done}} * Ramp up deployment to more application servers until most servers use HHVM{{done}} * Deploy to remainder of services{{done}} === HHVM work === <!--T:10--> <!--T:11--> Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. == Rationale == <!--T:12--> </translate> <translate><!--T:13--> It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.</translate><ref> <translate><!--T:43--> [<tvar name=radar>http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html</tvar> "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</translate> </ref><ref> <translate><!--T:44--> [<tvar name=glinden>http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html</tvar> Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</translate> </ref> <translate><!--T:31--> As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular.</translate> <translate><!--T:32--> Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.</translate><ref> <translate><!--T:45--> "[<tvar name=nytimes>http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html</tvar> Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</translate> </ref> <translate><!--T:33--> Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.</translate> <translate><!--T:14--> Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref><tvar name=1>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</tvar></ref> in a solution: [<tvar name=url>http://hhvm.com</tvar> HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages.</translate> <translate><!--T:34--> We're quite confident that this will result in big performance improvements on our sites as well.</translate> <translate> == What does HipHop do for our end users? == <!--T:15--> </translate> <translate><!--T:16--> MediaWiki is written in PHP, a language that is [[w:Interpreter (computing)|interpreted]] at run-time.</translate> <translate><!--T:35--> The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed.</translate> <translate><!--T:36--> These caches only serve users that are not logged in.</translate><ref> <translate><!--T:46--> By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</translate> <translate><!--T:47--> This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</translate> </ref> <translate><!--T:37--> Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include:</translate> <translate> <!--T:38--> *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. <!--T:17--> HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. == How does our development work on HipHop affect MediaWiki developers? == <!--T:18--> </translate> <translate><!--T:19--> In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend.</translate> <translate><!--T:39--> This will be on a totally opt-in basis which can be disabled at any time.</translate> <translate><!--T:40--> This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases.</translate> <translate><!--T:41--> It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.</translate> <translate><!--T:20--> For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to.</translate> <translate><!--T:42--> However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.</translate> <translate> == See also == <!--T:21--> <!--T:22--> * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Setting up HHVM in {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [<tvar name=yt1>https://www.youtube.com/watch?v=vgXgDVrb-BU</tvar> Ori presenting at @Scale about migrating to HHVM] * [<tvar name=yt2>https://www.youtube.com/watch?v=IKvILMSNNpk</tvar> HHVM in production: what that means for Wikimedia developers] == References and footnotes == <!--T:23--> </translate> <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] 8ztx8yfzuqfnjculm4mg69s6kq7spuw Translations:Manual:Configuring MediaWiki/2/cs 1198 217108 5386473 4815993 2022-07-28T14:30:41Z ENeRZet 17359278 wikitext text/x-wiki Když poprvé [[$1|instalujete MediaWiki]], měli byste spustit dodaný konfigurační skript prostřednictvím vašeho webového prohlížeče. 4yl5xdmsucsb0bctek38d03rnrhtx3p Translations:Manual:Installation guide/11/ru 1198 227399 5387279 4700868 2022-07-28T21:54:49Z Baris6161TURK 17188421 wikitext text/x-wiki Для поддержки создания миниатюр изображений требуются дополнительные программы. У $1 (требуется для VisualEditor) и других служб есть свои требования. nuuf9njv0e9it7xsll1oa1kv8crukz3 Manual:Installation guide/fa 100 228483 5386648 5381084 2022-07-28T17:14:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/fa]] q9bg7mkxug8hhqv4u6qlrv888iayzs0 Groups/vi 0 234108 5387364 4924014 2022-07-28T22:11:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Các nhóm MediaWiki''' tổ chức các hoạt động cộng đồng nguồn mở trong một phạm vi đề tài và khu vực địa lý cụ thể. Họ là những [[meta:WUG|Nhóm người dùng Wikimedia]] đồng ý điều phối trong một mức độ nào đó các nội dung MediaWiki. Như vậy, họ giúp mở rộng năng lực của [[wmf:Main|Wikimedia Foundation]] trong các [[Events|sự kiện]], [[Volunteer coordination and outreach/Training materials|quá trình đào tạo]], quảng bá và các hoạt động kỹ thuật khác liên quan đến lợi ích của Wikipedia, phong trào Wikimedia và phần mềm MediaWiki. <span class="mw-translate-fuzzy">Các nhóm MediaWiki chào đón những thành viên thuộc nhiều [[How to contribute|lĩnh vực cụ thể]] và các cấp chuyên môn khác nhau. Càng phong phú và đa dạng thì càng tốt.</span> Những người dùng không hiểu về kỹ thuật nhưng sẵn sàng đóng góp và học hỏi cũng được hoan nghênh! Tất cả các nhóm cam kết tuân thủ [[wmf:Friendly space policy|chính sách về Không gian thân thiện]]. Các nhóm MediaWiki có thể [[Groups/Wikimedia support|yêu cầu hỗ trợ]] từ Wikimedia Foundation và các chi hội dưới nhiều hình thức. == Nhóm theo chuyên đề == Các nhóm chuyên đề MediaWiki hợp tác với những đối tác hợp lý của họ trong cộng đồng rộng hơn là [[w:FLOSS|FLOSS]]. Họ là những nhóm toàn cầu, cộng tác trực tuyến. * Họ liên lạc để quy tụ các cộng đồng lại với nhau. * Họ tham gia các sự kiện có cùng chung đề tài. * Họ thúc đẩy các hoạt động đào tạo và tiếp cận cộng đồng có liên quan. * Họ giúp cải thiện các tài liệu liên quan trong wikimedia.org. * Họ hợp tác với những nhóm phát triển có liên quan. * Sau cùng, một số người đã họp mặt tại [//wikimania.wikimedia.org/ Wikimania]. <div lang="en" dir="ltr" class="mw-content-ltr"> * They participate in events of the same topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They promote related training and outreach activities. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They help improving the related documentation in wikimedia.org. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They collaborate with the related development teams. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Eventually some of them meet at [//wikimania.wikimedia.org/ Wikimania]. </div> == Nhóm theo địa phương == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Các nhóm địa phương MediaWiki hợp tác với [[meta:Wikimedia chapters|những chi hội Wikimedia]], Xem thêm tại [[w:Wikipedia:Meetup|trang họp mặt của Wikipedia tiếng Anh]] và các cộng đồng địa phương khác liên quan đến Wikimedia, phần mềm tự do, văn hóa mở... Hoạt động chủ yếu của họ diễn ra trong các cuộc gặp gỡ trực tiếp: * Tổ chức các sự kiện địa phương: họp mặt, đào tạo, tiệc hack... Những sự kiện này tuân thủ các nguyên tắc trong [[wmf:Friendly_space_policy|chính sách WMF về Không gian thân thiện]]. * Tham gia vào các sự kiện được tổ chức tại khu vực của họ. * Phân phối các sản phẩm. * Giới thiệu đến các cộng tác viên địa phương về những hoạt động trên toàn cầu của MediaWiki và Wikimedia. <div class="mw-translate-fuzzy"> Đối với các nhóm không sử dụng tiếng Anh: * Bản địa hóa các tài liệu và phần mềm theo quy trình ở [[translatewiki.net]]. </div> Các nhóm địa phương phải thực sự thuộc về một địa phương cụ thể. Bắt đầu từ những địa hạt như Recife, Munich hay Saint Petersburg thì tốt hơn là Brazil, Đức hay Nga. <span class="mw-translate-fuzzy">Nếu bạn đã bỏ lỡ một kênh về điều phối trong khu vực, hãy xem xét dùng một [[Mailing lists/Regional|danh sách thư theo khu vực]].</span> == Tạo một nhóm == Không cần phải có ai đó đứng ra đề xuất lập nhóm, chính bạn tạo cũng được. Để nhóm được phê duyệt, cần có ít nhất ba công tác viên. Xem trang [[Groups/Proposals]] để biết thêm chi tiết về quy trình tạo một nhóm MediaWiki của bạn. [[Category:MediaWiki Communication{{#translation:}}]] 8u34zsru2plvbnh89xflfts01e54hn2 5387384 5387364 2022-07-28T22:13:43Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Các nhóm MediaWiki''' tổ chức các hoạt động cộng đồng nguồn mở trong một phạm vi đề tài và khu vực địa lý cụ thể. Họ là những [[meta:WUG|Nhóm người dùng Wikimedia]] đồng ý điều phối trong một mức độ nào đó các nội dung MediaWiki. Như vậy, họ giúp mở rộng năng lực của [[wmf:Main|Wikimedia Foundation]] trong các [[Events|sự kiện]], [[Volunteer coordination and outreach/Training materials|quá trình đào tạo]], quảng bá và các hoạt động kỹ thuật khác liên quan đến lợi ích của Wikipedia, phong trào Wikimedia và phần mềm MediaWiki. Các nhóm MediaWiki chào đón những thành viên thuộc nhiều [[Special:MyLanguage/How to contribute|lĩnh vực cụ thể]] và các cấp chuyên môn khác nhau. Càng phong phú và đa dạng thì càng tốt. Những người dùng không hiểu về kỹ thuật nhưng sẵn sàng đóng góp và học hỏi cũng được hoan nghênh! Tất cả các nhóm cam kết tuân thủ [[wmf:Friendly space policy|chính sách về Không gian thân thiện]]. Các nhóm MediaWiki có thể [[Groups/Wikimedia support|yêu cầu hỗ trợ]] từ Wikimedia Foundation và các chi hội dưới nhiều hình thức. == Nhóm theo chuyên đề == Các nhóm chuyên đề MediaWiki hợp tác với những đối tác hợp lý của họ trong cộng đồng rộng hơn là [[w:FLOSS|FLOSS]]. Họ là những nhóm toàn cầu, cộng tác trực tuyến. * Họ liên lạc để quy tụ các cộng đồng lại với nhau. * Họ tham gia các sự kiện có cùng chung đề tài. * Họ thúc đẩy các hoạt động đào tạo và tiếp cận cộng đồng có liên quan. * Họ giúp cải thiện các tài liệu liên quan trong wikimedia.org. * Họ hợp tác với những nhóm phát triển có liên quan. * Sau cùng, một số người đã họp mặt tại [//wikimania.wikimedia.org/ Wikimania]. <div lang="en" dir="ltr" class="mw-content-ltr"> * They participate in events of the same topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They promote related training and outreach activities. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They help improving the related documentation in wikimedia.org. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They collaborate with the related development teams. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Eventually some of them meet at [//wikimania.wikimedia.org/ Wikimania]. </div> == Nhóm theo địa phương == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Các nhóm địa phương MediaWiki hợp tác với [[meta:Wikimedia chapters|những chi hội Wikimedia]], Xem thêm tại [[w:Wikipedia:Meetup|trang họp mặt của Wikipedia tiếng Anh]] và các cộng đồng địa phương khác liên quan đến Wikimedia, phần mềm tự do, văn hóa mở... Hoạt động chủ yếu của họ diễn ra trong các cuộc gặp gỡ trực tiếp: * Tổ chức các sự kiện địa phương: họp mặt, đào tạo, tiệc hack... Những sự kiện này tuân thủ các nguyên tắc trong [[wmf:Friendly_space_policy|chính sách WMF về Không gian thân thiện]]. * Tham gia vào các sự kiện được tổ chức tại khu vực của họ. * Phân phối các sản phẩm. * Giới thiệu đến các cộng tác viên địa phương về những hoạt động trên toàn cầu của MediaWiki và Wikimedia. <div class="mw-translate-fuzzy"> Đối với các nhóm không sử dụng tiếng Anh: * Bản địa hóa các tài liệu và phần mềm theo quy trình ở [[translatewiki.net]]. </div> Các nhóm địa phương phải thực sự thuộc về một địa phương cụ thể. Bắt đầu từ những địa hạt như Recife, Munich hay Saint Petersburg thì tốt hơn là Brazil, Đức hay Nga. <span class="mw-translate-fuzzy">Nếu bạn đã bỏ lỡ một kênh về điều phối trong khu vực, hãy xem xét dùng một [[Mailing lists/Regional|danh sách thư theo khu vực]].</span> == Tạo một nhóm == Không cần phải có ai đó đứng ra đề xuất lập nhóm, chính bạn tạo cũng được. Để nhóm được phê duyệt, cần có ít nhất ba công tác viên. Xem trang [[Groups/Proposals]] để biết thêm chi tiết về quy trình tạo một nhóm MediaWiki của bạn. [[Category:MediaWiki Communication{{#translation:}}]] nl6xkibi7pl9zv3bggg8nphmitfim1n 5387419 5387384 2022-07-28T22:15:43Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Các nhóm MediaWiki''' tổ chức các hoạt động cộng đồng nguồn mở trong một phạm vi đề tài và khu vực địa lý cụ thể. Họ là những [[meta:WUG|Nhóm người dùng Wikimedia]] đồng ý điều phối trong một mức độ nào đó các nội dung MediaWiki. Như vậy, họ giúp mở rộng năng lực của [[wmf:Main|Wikimedia Foundation]] trong các [[Events|sự kiện]], [[Volunteer coordination and outreach/Training materials|quá trình đào tạo]], quảng bá và các hoạt động kỹ thuật khác liên quan đến lợi ích của Wikipedia, phong trào Wikimedia và phần mềm MediaWiki. Các nhóm MediaWiki chào đón những thành viên thuộc nhiều [[Special:MyLanguage/How to contribute|lĩnh vực cụ thể]] và các cấp chuyên môn khác nhau. Càng phong phú và đa dạng thì càng tốt. Những người dùng không hiểu về kỹ thuật nhưng sẵn sàng đóng góp và học hỏi cũng được hoan nghênh! Tất cả các nhóm cam kết tuân thủ [[wmf:Friendly space policy|chính sách về Không gian thân thiện]]. Các nhóm MediaWiki có thể [[Groups/Wikimedia support|yêu cầu hỗ trợ]] từ Wikimedia Foundation và các chi hội dưới nhiều hình thức. == Nhóm theo chuyên đề == Các nhóm chuyên đề MediaWiki hợp tác với những đối tác hợp lý của họ trong cộng đồng rộng hơn là [[w:FLOSS|FLOSS]]. Họ là những nhóm toàn cầu, cộng tác trực tuyến. * Họ liên lạc để quy tụ các cộng đồng lại với nhau. * Họ tham gia các sự kiện có cùng chung đề tài. * Họ thúc đẩy các hoạt động đào tạo và tiếp cận cộng đồng có liên quan. * Họ giúp cải thiện các tài liệu liên quan trong wikimedia.org. * Họ hợp tác với những nhóm phát triển có liên quan. * Sau cùng, một số người đã họp mặt tại [//wikimania.wikimedia.org/ Wikimania]. <div lang="en" dir="ltr" class="mw-content-ltr"> * They participate in events of the same topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They promote related training and outreach activities. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They help improving the related documentation in wikimedia.org. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They collaborate with the related development teams. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Eventually some of them meet at [//wikimania.wikimedia.org/ Wikimania]. </div> == Nhóm theo địa phương == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Các nhóm địa phương MediaWiki hợp tác với [[meta:Wikimedia chapters|những chi hội Wikimedia]], Xem thêm tại [[w:Wikipedia:Meetup|trang họp mặt của Wikipedia tiếng Anh]] và các cộng đồng địa phương khác liên quan đến Wikimedia, phần mềm tự do, văn hóa mở... Hoạt động chủ yếu của họ diễn ra trong các cuộc gặp gỡ trực tiếp: * Tổ chức các sự kiện địa phương: họp mặt, đào tạo, tiệc hack... Những sự kiện này tuân thủ các nguyên tắc trong [[wmf:Friendly_space_policy|chính sách WMF về Không gian thân thiện]]. * Tham gia vào các sự kiện được tổ chức tại khu vực của họ. * Phân phối các sản phẩm. * Giới thiệu đến các cộng tác viên địa phương về những hoạt động trên toàn cầu của MediaWiki và Wikimedia. Đối với các nhóm không sử dụng tiếng Anh: * Bản địa hóa các tài liệu và phần mềm theo quy trình ở [[Special:MyLanguage/translatewiki.net|translatewiki.net]]. Các nhóm địa phương phải thực sự thuộc về một địa phương cụ thể. Bắt đầu từ những địa hạt như Recife, Munich hay Saint Petersburg thì tốt hơn là Brazil, Đức hay Nga. <span class="mw-translate-fuzzy">Nếu bạn đã bỏ lỡ một kênh về điều phối trong khu vực, hãy xem xét dùng một [[Mailing lists/Regional|danh sách thư theo khu vực]].</span> == Tạo một nhóm == Không cần phải có ai đó đứng ra đề xuất lập nhóm, chính bạn tạo cũng được. Để nhóm được phê duyệt, cần có ít nhất ba công tác viên. Xem trang [[Groups/Proposals]] để biết thêm chi tiết về quy trình tạo một nhóm MediaWiki của bạn. [[Category:MediaWiki Communication{{#translation:}}]] 0zdojpwo39o2kcuo91xqzbsupc715jo Translations:Manual:Installation guide/11/es 1198 240091 5387280 5080307 2022-07-28T21:54:59Z Baris6161TURK 17188421 wikitext text/x-wiki La generación de imágenes en miniatura y $texvc requieren programas adicionales. $1 (requerido por el editor visual) y otros servicios tienen sus propios requisitos. ryofzi4qhhs17uy2b2u720olca4z72o Manual:Installation guide/hu 100 248991 5386652 5381515 2022-07-28T17:14:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/hu]] 4apmsov1n5tohqerhaeov88a77u2wgv Translations:Manual:Installation guide/11/hu 1198 249925 5387281 4701003 2022-07-28T21:55:31Z Baris6161TURK 17188421 wikitext text/x-wiki A képminiatűrökhöz további programok szükségesek. A (VisualEditorhöz szükséges) Parsoidnak és más szolgáltatásoknak saját követelményeik lehetnek. 2xci49mi0txtndzbj23pquabgjmke88 Translations:Groups/4/en 1198 251528 5387353 1093706 2022-07-28T22:11:21Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki MediaWiki Groups are open to members of [[$1|different specialties]] and levels of expertise. ii6qbnp2skqu8l2y37mq5gxomlln4n2 Translations:Groups/25/en 1198 251554 5387354 1093732 2022-07-28T22:11:22Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki Also for non-English speaking groups: * Localization of documentation and software following $1 processes. dexlgxqv5jwjrx9ud5lunwv262rixmu Translations:Groups/4/pl 1198 251561 5387379 1093766 2022-07-28T22:12:57Z Shirayuki 472859 update wikitext text/x-wiki Grupy użytkowników MediaWiki są otwarte dla ludzi z [[$1|różnymi specjalnościami]] oraz poziomem wiedzy. Im bardziej zróżnicowane tym lepiej. 7744zszfunbp3swu0lq1fx35uza435p Translations:Groups/25/pl 1198 251582 5387410 1093806 2022-07-28T22:15:24Z Shirayuki 472859 update wikitext text/x-wiki Także dla grup nie mówiących po angielsku: * Tłumaczenie dokumentacji i oprogramowania poprzez $1. b60siw8vr938yqrc3h19yit2p1xjuof Translations:Groups/4/vi 1198 251600 5387383 3495589 2022-07-28T22:13:42Z Shirayuki 472859 update wikitext text/x-wiki Các nhóm MediaWiki chào đón những thành viên thuộc nhiều [[$1|lĩnh vực cụ thể]] và các cấp chuyên môn khác nhau. Càng phong phú và đa dạng thì càng tốt. 93t3iqf7lkhkd2ukjzpvsjts4p8mqpj Translations:Groups/25/vi 1198 251616 5387417 1093872 2022-07-28T22:15:42Z Shirayuki 472859 update wikitext text/x-wiki Đối với các nhóm không sử dụng tiếng Anh: * Bản địa hóa các tài liệu và phần mềm theo quy trình ở $1. mgo2a3ivl5ohmeu1wdoym0pfy6w2uin Groups/ru 0 255344 5387363 4924011 2022-07-28T22:11:32Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Группы MediaWiki''' организуют мероприятия сообщества с открытым исходным кодом в рамках определенных тем и географических областей. Это [[meta:Special:MyLanguage/Wikimedia user groups|группы пользователей Викимедиа]], которые согласовывают уровень координации в контексте MediaWiki. Таким образом, они расширяют возможности [[wmf:|Фонда Викимедиа]] в [[Events|мероприятиях]], [[Volunteer coordination and outreach/Training materials|обучение]], продвижении и других технических мероприятиях, полезных для Википедии, движения Викимедиа и программном обеспечении MediaWiki. <span class="mw-translate-fuzzy">Группы MediaWiki открыты для участников [[Special:MyLanguage/How to contribute|различных специальностей]] и уровня знаний.</span> Чем богаче и разнообразнее, тем лучше. Нетехнические пользователи, желающие внести свой вклад и учиться, также приветствуются! Все группы придерживаются [[wmf:Friendly space policy|Политики дружественного пространства]]. Группы MediaWiki могут [[Groups/Wikimedia support|запросить поддержку]] из Фонда Викимедиа и глав в различных формах. == Тематические группы == Тематические группы MediaWiki сотрудничают со своими логическими партнерами в более широком сообществе [[w:FLOSS|FLOSS]]. Это глобальные группы, сотрудничающие онлайн. * Они находятся в контакте с сообществами в рамках одной и той же направленности. * Они участвуют в мероприятиях на ту же тему. * Они продвигают соответствующие учебные и информационные мероприятия. * Они помогают улучшить соответствующую документацию на wikimedia.org. * Они сотрудничают с соответствующими командами разработчиков. * В конце концов, некоторые из них встречаются на [//wikimania.wikimedia.org/ Wikimania]. == Локальные группы == <div class="toccolours"> * [[Groups/San Francisco|Сан-Франциско]] </div> Локальные группы MediaWiki сотрудничают с [[meta:Special:MyLanguage/Wikimedia chapters|главами Викимедиа]], смотрите также [[w:ru:Википедия:Вики-встречи|Вики-встречи]] и другие локальные сообщества, связанные с Викимедиа, свободным программным обеспечением, свободной культурой ... Их фокус заключается в личных мероприятиях: Организация локальных мероприятий: встречи, обучение, хакфесты... Эти мероприятия соответствуют [[wmf:Friendly_space_policy|политики дружественного пространства WMF]]. * Участие в мероприятиях, проводимых в своей области. * Распространение мерчендайзинга. * Продвижение локальных участников глобальных мероприятий MediaWiki и Wikimedia. <div class="mw-translate-fuzzy"> Также для неанглоговорящих групп: * Локализация документации и программного обеспечения в соответствии с процессами [[Special:MyLanguage/translatewiki.net|translatewiki.net]]. </div> Локальные группы должны быть действительно локальными. Начальные точки, такие как, например, Ресифи, Мюнхен или Санкт-Петербург лучше, чем Бразилия, Германия или Россия. <span class="mw-translate-fuzzy">Если вы пропустили канал для региональной координации, рассмотрите [[Mailing lists/Regional|региональный список рассылки]].</span> == Создание группы == Вам не нужен кто-то, чтобы предложить группу, только вы сами. Для её одобрения у вас должно быть как минимум три участника. Проверьте [[Groups/Proposals]] для получения более подробной информации о создании вашей группы MediaWiki. [[Category:MediaWiki Communication{{#translation:}}]] 0nnkykxrfsltbz7763hu7jc10kcn2ry Translations:Wikitext standard/1/en 1198 258568 5387864 1113223 2022-07-29T10:33:02Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki A single '''[[$1|wikitext]] standard''' is of great importance for the long-term stability of the MediaWiki software. We need to describe and formalize a [[$2|1.0]] version of the Wikitext language, based on what is used currently. In other words this work should not (for right now) involve incorporating improvements or changes to the Wikitext language. Releases must be stable and predictable so that other software developers can work to the same markup syntax, and know for sure that they will not be facing random or arbitrary changes for some fixed time period, like a year. This suggests there may be [[$3|wikitext 2005]], [[$4|wikitext 2006]] and so on. ctyza08z3373emmko04xx3hse36t90l Translations:Wikitext standard/4/en 1198 258570 5387865 1113225 2022-07-29T10:33:02Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki #Write a [[$1|markup spec]] #Write an efficient [[$2|Wikitext to HTML converter]], to replace the current PHP code. #Write a set of unit tests to validate the correctness of a Wikitext to HTML converter. 7y5c4j5n6yed3s2u0tfpkxx13giqk9m Translations:Wikitext standard/6/en 1198 258572 5387866 1113227 2022-07-29T10:33:02Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki #Write a [[$1|Wikitext DTD]] that can serve as a canonical translation of Wikitext <=> XML, for further processing by XML tools. ''Or use [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. #Write a Wikitext to XML converter. #* Evaluate [http://www.tldp.org/wt2db/ wt2db]. #* Or use [http://schematics.sourceforge.net WebBot], A PLT Scheme package that acts as a Bot on MediaWiki and contains the parser to convert WikiText to the [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. m16wc4mduqhizgl8zrwdxkffi7ruu8u Translations:Wikitext standard/1/es 1198 258636 5387876 1116303 2022-07-29T10:34:38Z Shirayuki 472859 update wikitext text/x-wiki Un '''[[$1|wikitexto]] estándar''' único es de gran importancia para la estabilidad a largo plazo del software MediaWiki. Necesitamos describir y formalizar una versión [[$2|1.0]] del lenguaje wikitexto, basado en lo que se usa actualmente. En otras palabras, este trabajo no debe (por ahora) incorporar mejoras o cambios en el lenguaje. Las liberaciones deben ser estables y predecibles de manera que los desarrolladores de software puedan trabajar con una misma sintaxis del lenguaje de hipertexto, y puedan saber con certeza que no se enfrentarán a cambios arbitrarios y al azar por algún período fijo, por ejemplo un año. Esto sugiere que puede haber [[$3|wikitexto 2005]], [[$4|wikitexto 2006]] y demás. tn447flg4h9wnox4vw7tsy0uifgo7kr Translations:Wikitext standard/4/es 1198 258639 5387882 1116650 2022-07-29T10:36:41Z Shirayuki 472859 update wikitext text/x-wiki #Escribir una [[$1|especificación del lenguaje wikitexto]] #Escribir un [[$2|conversor de wikitexto a HTML]] eficiente, que reemplace el código PHP actual. #Escribir una serie de unidades de pruebas para validar la exactitud del conversor de wikitexto a HTML. if30dwjjq3dc1fgcmsvsn55zi6uwno5 Translations:Wikitext standard/6/es 1198 258641 5387889 1113321 2022-07-29T10:38:33Z Shirayuki 472859 update wikitext text/x-wiki #Escribir un [[$1|Wikitext DTD]] que sirva como traduccion canonica del Wikitext<=> XML, para las futuras herramientas de procesamiento de XML. ''O usar [http://schematics.sourceforge.net/wikitext.xsd.zip este XML Schema]''. #Escribir un [[Alternative parsers|conversor Wikitext a XML]]. #Evaluar [http://www.tldp.org/wt2db/ wt2db]. #* O usar [http://schematics.sourceforge.net WebBot], Un paquete de esquemas PLT que actual como Boot en el Media Wiki y que contiene un [[parser]] que convierte Wikitext a [http://schematics.sourceforge.net/wikitext.xsd.zip desde un esquema XML dado]. ge06qmx51a8shy6u44u3mp70qm3em55 Wikitext standard/pl 0 261812 5387872 4771640 2022-07-29T10:33:07Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Historical|1=<span lang="en" dir="ltr" class="mw-content-ltr">Most of the text found on this page was written from 2003-2006.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Wikitext}} for the latest status on wikitext standardization efforts.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> A single '''[[Special:MyLanguage/wikitext|wikitext]] standard''' is of great importance for the long-term stability of the MediaWiki software. We need to describe and formalize a [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] version of the Wikitext language, based on what is used currently. In other words this work should not (for right now) involve incorporating improvements or changes to the Wikitext language. Releases must be stable and predictable so that other software developers can work to the same markup syntax, and know for sure that they will not be facing random or arbitrary changes for some fixed time period, like a year. This suggests there may be [[Special:MyLanguage/wikitext 2005|wikitext 2005]], [[Special:MyLanguage/wikitext 2006|wikitext 2006]] and so on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] was tracking which mediawiki sites are doing what best. Wikipedia won't always be the furthest ahead on an issue, nor should its needs necessarily always trump others in the mediawiki software design effort. For instance [[meta:Wikitravel|Wikitravel]] may do better on geography and [[meta:Spacetime DTD|map]] issues. The first useful map and underlying data standards like an [[meta:Ecoregion DTD|ecoregion DTD]] and [[meta:Spacetime DTD|spacetime DTD]] may be easier to work on there, where these are more central issues. Other subtasks like a [[meta:Person DTD|person DTD]] may become WikiProjects undertaken by a disciplined group of scholars who know, or want to know, everything about documenting people. </div> == Zadania == <div lang="en" dir="ltr" class="mw-content-ltr"> #Write a [[Special:MyLanguage/markup spec|markup spec]] #Write an efficient [[Special:MyLanguage/Alternative parsers|Wikitext to HTML converter]], to replace the current PHP code. #Write a set of unit tests to validate the correctness of a Wikitext to HTML converter. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===XML-Related Tasks=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> #Write a [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]] that can serve as a canonical translation of Wikitext <=> XML, for further processing by XML tools. ''Or use [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. #Write a Wikitext to XML converter. #* Evaluate [http://www.tldp.org/wt2db/ wt2db]. #* Or use [http://schematics.sourceforge.net WebBot], A PLT Scheme package that acts as a Bot on MediaWiki and contains the parser to convert WikiText to the [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Publishing the Standard== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A clear standard can be published and supported by other wikis, like MoinMoinWiki ([[:en:Python_programming_language|python]]-based) and tikiwiki (see [http://tikiwiki.sourceforge.net sourceforge]), which are very popular, and more extensible than mediawiki, which has serious structural problems </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if mediawiki can keep up with those other packages, text import/export has to be one of our priorities, given the objectives of this project to become a central GNU FDL repository of trusted text for use all over the place. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[meta:Wikimedia|Wikimedia]] activities shouldn't be in any way trapped or tied to MediaWiki, if drastically better software emerges from tikiwiki or the Python world. And it will, eventually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Long Term Plans === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> #when things settle down, say [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], then: #create a consortium of all users, developers of various types of software, including [[meta:IRC/Channels|chat]] and [[Special:MyLanguage/email|email]] based systems that incorporate features like [[Special:MyLanguage/Trillian Instant Lookup|Trillian Instant Lookup]] - not all users of Wikipedia use a web browser #agree on a [[meta:Simple ideology of Wikitax|simple ideology of Wikitax]] to make it easy for content generated elsewhere to quickly become wiki pages #develop a unified base boot like KnoppixTiki that supports the new standard so it can be used for any kind of data storage like in a PIM #stabilize and publish something like [[Special:MyLanguage/wikitext 2008|wikitext 2008]] as a real RFC #aim for [[Special:MyLanguage/wikitext 2009|wikitext 2009]] or [[Special:MyLanguage/wikitext 2010|wikitext 2010]] to be an ITU standard </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See also: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] </div> [[Category:Wikitext{{#translation:}}]] e82ym2eh9v00aqg04wjljc4g36xlmtt Wikitext standard/ja 0 262749 5387870 4771639 2022-07-29T10:33:06Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Historical|1=<span lang="en" dir="ltr" class="mw-content-ltr">Most of the text found on this page was written from 2003-2006.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Wikitext}} for the latest status on wikitext standardization efforts.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> A single '''[[Special:MyLanguage/wikitext|wikitext]] standard''' is of great importance for the long-term stability of the MediaWiki software. We need to describe and formalize a [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] version of the Wikitext language, based on what is used currently. In other words this work should not (for right now) involve incorporating improvements or changes to the Wikitext language. Releases must be stable and predictable so that other software developers can work to the same markup syntax, and know for sure that they will not be facing random or arbitrary changes for some fixed time period, like a year. This suggests there may be [[Special:MyLanguage/wikitext 2005|wikitext 2005]], [[Special:MyLanguage/wikitext 2006|wikitext 2006]] and so on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] was tracking which mediawiki sites are doing what best. Wikipedia won't always be the furthest ahead on an issue, nor should its needs necessarily always trump others in the mediawiki software design effort. For instance [[meta:Wikitravel|Wikitravel]] may do better on geography and [[meta:Spacetime DTD|map]] issues. The first useful map and underlying data standards like an [[meta:Ecoregion DTD|ecoregion DTD]] and [[meta:Spacetime DTD|spacetime DTD]] may be easier to work on there, where these are more central issues. Other subtasks like a [[meta:Person DTD|person DTD]] may become WikiProjects undertaken by a disciplined group of scholars who know, or want to know, everything about documenting people. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Tasks== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> #Write a [[Special:MyLanguage/markup spec|markup spec]] #Write an efficient [[Special:MyLanguage/Alternative parsers|Wikitext to HTML converter]], to replace the current PHP code. #Write a set of unit tests to validate the correctness of a Wikitext to HTML converter. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===XML-Related Tasks=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> #Write a [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]] that can serve as a canonical translation of Wikitext <=> XML, for further processing by XML tools. ''Or use [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. #Write a Wikitext to XML converter. #* Evaluate [http://www.tldp.org/wt2db/ wt2db]. #* Or use [http://schematics.sourceforge.net WebBot], A PLT Scheme package that acts as a Bot on MediaWiki and contains the parser to convert WikiText to the [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Publishing the Standard== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A clear standard can be published and supported by other wikis, like MoinMoinWiki ([[:en:Python_programming_language|python]]-based) and tikiwiki (see [http://tikiwiki.sourceforge.net sourceforge]), which are very popular, and more extensible than mediawiki, which has serious structural problems </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if mediawiki can keep up with those other packages, text import/export has to be one of our priorities, given the objectives of this project to become a central GNU FDL repository of trusted text for use all over the place. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[meta:Wikimedia|Wikimedia]] activities shouldn't be in any way trapped or tied to MediaWiki, if drastically better software emerges from tikiwiki or the Python world. And it will, eventually. </div> ===長期計画 === <div lang="en" dir="ltr" class="mw-content-ltr"> #when things settle down, say [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], then: #create a consortium of all users, developers of various types of software, including [[meta:IRC/Channels|chat]] and [[Special:MyLanguage/email|email]] based systems that incorporate features like [[Special:MyLanguage/Trillian Instant Lookup|Trillian Instant Lookup]] - not all users of Wikipedia use a web browser #agree on a [[meta:Simple ideology of Wikitax|simple ideology of Wikitax]] to make it easy for content generated elsewhere to quickly become wiki pages #develop a unified base boot like KnoppixTiki that supports the new standard so it can be used for any kind of data storage like in a PIM #stabilize and publish something like [[Special:MyLanguage/wikitext 2008|wikitext 2008]] as a real RFC #aim for [[Special:MyLanguage/wikitext 2009|wikitext 2009]] or [[Special:MyLanguage/wikitext 2010|wikitext 2010]] to be an ITU standard </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See also: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] </div> [[Category:Wikitext{{#translation:}}]] phcz3i419a3azp6sgoj88316jhhlvqp Groups/ja 0 263360 5387359 5190127 2022-07-28T22:11:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki グループ'''は、主題ごと、地理的範囲ごとに特化したオープンソースのコミュニティ活動をまとめます。 これらは MediaWiki の文脈の範囲で特定レベルの合意の元に設置する[[meta:Special:MyLanguage/Wikimedia user groups|ウィキメディア利用者グループ]]です。 前述により[[Events|イベント]]や[[Volunteer coordination and outreach/Training materials|研修]]、周知活動その他、ウィキペディア、ウィキメディア運動、MediaWiki ソフトウェアに有益な技術関連の活動を行い、[[wmf:|ウィキメディア財団]]のキャパシティ拡大に寄与します。 <span class="mw-translate-fuzzy">MediaWiki グループには[[Special:MyLanguage/How to contribute|それぞれの特性]]や技術その他の習熟度に関わらず、どなたでもご参加いただけます。</span> 多様性が豊かであるほどよいのです。 技術系ではないけれど参加して学びたい、貢献したい人も歓迎です! どのグループでも原則は[[wmf:Friendly space policy|有効であるべき場所の方針]]の順守です。 MediaWiki グループは、ウィキメディア財団や国別協会にさまざまな形の[[Groups/Wikimedia support|支援を申請]]できます。 == テーマ別グループ == テーマ別 MediaWiki グループ (以下テーマ別グループ) が行う共同作業は、理論上の対応付けがされる[[w:FLOSS|FLOSS]]コミュニティという、グローバルで活動範囲がより広範な場所です。 * 同じ活動目標を掲げる他のコミュニティとも連絡を取り合う。 *同じ議題のイベントに参加。 * 関連のある研修会や普及活動(アウトリーチ)の広報を手がける。 * wikimedia.org にホストされる関連分野の説明文書の品質向上を支援。 *関連する開発チームと協働。 * ときには参加したウィキマニア [//wikimania.wikimedia.org/ Wikimania]の会場でばったり会ったりする。 == 地域別グループ == <div class="toccolours"> * [[Groups/San Francisco|サンフランシスコ]] </div> 複数のローカルの MediaWiki グループが連携し、複数の[[meta:Special:MyLanguage/Wikimedia chapters|ウィキメディア協会]]と共同作業をしています。オフ会情報[[:w:Wikipedia:Meetup|Wikipedia meetups]]や、その他ウィキメディアの関連グループとしてローカルのコミュニティや無料ソフト、自由な文化など、関連の情報源も合わせてご参照ください。 対面型の次のような活動を重視しています。 * 地元でイベントを主催:オフ会、研修会、ハック会など…...。いずれも[[wmf:Friendly_space_policy|WMF 友好的である場の方針]]を順守します。 * 地元で開かれるイベントに参加する。 * 商品の配布。 * 地元の貢献者をグローバルな MediaWiki 活動やウィキメディア活動へ推薦する。 <div class="mw-translate-fuzzy"> さらに英語以外の話者グループを対象とした活動を行う: * 説明文書とソフトウェアについて、[[Special:MyLanguage/translatewiki.net|translatewiki.net]]の手順に従った翻訳を実施。 </div> ローカルと言うからには、まったく地元優先であること。 ローカルの範囲はまず[[:ja:レシフェ|レシフェ]]、[[:ja:ミュンヘン|ミュンヘン]]、[[:ja:サンクトペテルブルク|サンクトペテルブルク]]などから始めるのがよく、ブラジル、ドイツ、ロシアなどは現実的ではありません。 <span lang="en" dir="ltr" class="mw-content-ltr">If you miss a channel for regional coordination then consider [[m:Special:MyLanguage/Mailing lists#Create a new list|requesting the creation]] of a [[m:Special:MyLanguage/Mailing lists/Overview#Regional mailing lists|regional mailing list]] and/or [[m:Special:MyLanguage/Mailing lists/Overview#Local|local mailing list]].</span> == グループの設立 == 誰かが設立を表明するのを待つのではなく、あなたご自身が発起人になってください。 承認の条件は、貢献者が3名以上参加することです。 自身の MediaWiki グループを立ち上げるには、[[Groups/Proposals]] で詳細を確認してください。 [[Category:MediaWiki Communication{{#translation:}}]] 3brlty4geb8qap48c3z53rp59pxtfmg 5387370 5387359 2022-07-28T22:11:55Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki グループ'''は、主題ごと、地理的範囲ごとに特化したオープンソースのコミュニティ活動をまとめます。 これらは MediaWiki の文脈の範囲で特定レベルの合意の元に設置する[[meta:Special:MyLanguage/Wikimedia user groups|ウィキメディア利用者グループ]]です。 前述により[[Events|イベント]]や[[Volunteer coordination and outreach/Training materials|研修]]、周知活動その他、ウィキペディア、ウィキメディア運動、MediaWiki ソフトウェアに有益な技術関連の活動を行い、[[wmf:|ウィキメディア財団]]のキャパシティ拡大に寄与します。 MediaWiki グループには[[Special:MyLanguage/How to contribute|それぞれの特性]]や技術その他の習熟度に関わらず、どなたでもご参加いただけます。 多様性が豊かであるほどよいのです。 技術系ではないけれど参加して学びたい、貢献したい人も歓迎です! どのグループでも原則は[[wmf:Friendly space policy|有効であるべき場所の方針]]の順守です。 MediaWiki グループは、ウィキメディア財団や国別協会にさまざまな形の[[Groups/Wikimedia support|支援を申請]]できます。 == テーマ別グループ == テーマ別 MediaWiki グループ (以下テーマ別グループ) が行う共同作業は、理論上の対応付けがされる[[w:FLOSS|FLOSS]]コミュニティという、グローバルで活動範囲がより広範な場所です。 * 同じ活動目標を掲げる他のコミュニティとも連絡を取り合う。 *同じ議題のイベントに参加。 * 関連のある研修会や普及活動(アウトリーチ)の広報を手がける。 * wikimedia.org にホストされる関連分野の説明文書の品質向上を支援。 *関連する開発チームと協働。 * ときには参加したウィキマニア [//wikimania.wikimedia.org/ Wikimania]の会場でばったり会ったりする。 == 地域別グループ == <div class="toccolours"> * [[Groups/San Francisco|サンフランシスコ]] </div> 複数のローカルの MediaWiki グループが連携し、複数の[[meta:Special:MyLanguage/Wikimedia chapters|ウィキメディア協会]]と共同作業をしています。オフ会情報[[:w:Wikipedia:Meetup|Wikipedia meetups]]や、その他ウィキメディアの関連グループとしてローカルのコミュニティや無料ソフト、自由な文化など、関連の情報源も合わせてご参照ください。 対面型の次のような活動を重視しています。 * 地元でイベントを主催:オフ会、研修会、ハック会など…...。いずれも[[wmf:Friendly_space_policy|WMF 友好的である場の方針]]を順守します。 * 地元で開かれるイベントに参加する。 * 商品の配布。 * 地元の貢献者をグローバルな MediaWiki 活動やウィキメディア活動へ推薦する。 <div class="mw-translate-fuzzy"> さらに英語以外の話者グループを対象とした活動を行う: * 説明文書とソフトウェアについて、[[Special:MyLanguage/translatewiki.net|translatewiki.net]]の手順に従った翻訳を実施。 </div> ローカルと言うからには、まったく地元優先であること。 ローカルの範囲はまず[[:ja:レシフェ|レシフェ]]、[[:ja:ミュンヘン|ミュンヘン]]、[[:ja:サンクトペテルブルク|サンクトペテルブルク]]などから始めるのがよく、ブラジル、ドイツ、ロシアなどは現実的ではありません。 <span lang="en" dir="ltr" class="mw-content-ltr">If you miss a channel for regional coordination then consider [[m:Special:MyLanguage/Mailing lists#Create a new list|requesting the creation]] of a [[m:Special:MyLanguage/Mailing lists/Overview#Regional mailing lists|regional mailing list]] and/or [[m:Special:MyLanguage/Mailing lists/Overview#Local|local mailing list]].</span> == グループの設立 == 誰かが設立を表明するのを待つのではなく、あなたご自身が発起人になってください。 承認の条件は、貢献者が3名以上参加することです。 自身の MediaWiki グループを立ち上げるには、[[Groups/Proposals]] で詳細を確認してください。 [[Category:MediaWiki Communication{{#translation:}}]] cdsdz0kwajmsexna78j6rb3dzy53g2p 5387406 5387370 2022-07-28T22:15:11Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki グループ'''は、主題ごと、地理的範囲ごとに特化したオープンソースのコミュニティ活動をまとめます。 これらは MediaWiki の文脈の範囲で特定レベルの合意の元に設置する[[meta:Special:MyLanguage/Wikimedia user groups|ウィキメディア利用者グループ]]です。 前述により[[Events|イベント]]や[[Volunteer coordination and outreach/Training materials|研修]]、周知活動その他、ウィキペディア、ウィキメディア運動、MediaWiki ソフトウェアに有益な技術関連の活動を行い、[[wmf:|ウィキメディア財団]]のキャパシティ拡大に寄与します。 MediaWiki グループには[[Special:MyLanguage/How to contribute|それぞれの特性]]や技術その他の習熟度に関わらず、どなたでもご参加いただけます。 多様性が豊かであるほどよいのです。 技術系ではないけれど参加して学びたい、貢献したい人も歓迎です! どのグループでも原則は[[wmf:Friendly space policy|有効であるべき場所の方針]]の順守です。 MediaWiki グループは、ウィキメディア財団や国別協会にさまざまな形の[[Groups/Wikimedia support|支援を申請]]できます。 == テーマ別グループ == テーマ別 MediaWiki グループ (以下テーマ別グループ) が行う共同作業は、理論上の対応付けがされる[[w:FLOSS|FLOSS]]コミュニティという、グローバルで活動範囲がより広範な場所です。 * 同じ活動目標を掲げる他のコミュニティとも連絡を取り合う。 *同じ議題のイベントに参加。 * 関連のある研修会や普及活動(アウトリーチ)の広報を手がける。 * wikimedia.org にホストされる関連分野の説明文書の品質向上を支援。 *関連する開発チームと協働。 * ときには参加したウィキマニア [//wikimania.wikimedia.org/ Wikimania]の会場でばったり会ったりする。 == 地域別グループ == <div class="toccolours"> * [[Groups/San Francisco|サンフランシスコ]] </div> 複数のローカルの MediaWiki グループが連携し、複数の[[meta:Special:MyLanguage/Wikimedia chapters|ウィキメディア協会]]と共同作業をしています。オフ会情報[[:w:Wikipedia:Meetup|Wikipedia meetups]]や、その他ウィキメディアの関連グループとしてローカルのコミュニティや無料ソフト、自由な文化など、関連の情報源も合わせてご参照ください。 対面型の次のような活動を重視しています。 * 地元でイベントを主催:オフ会、研修会、ハック会など…...。いずれも[[wmf:Friendly_space_policy|WMF 友好的である場の方針]]を順守します。 * 地元で開かれるイベントに参加する。 * 商品の配布。 * 地元の貢献者をグローバルな MediaWiki 活動やウィキメディア活動へ推薦する。 さらに英語以外の話者グループを対象とした活動を行う: * 説明文書とソフトウェアについて、[[Special:MyLanguage/translatewiki.net|translatewiki.net]] の手順に従った翻訳を実施。 ローカルと言うからには、まったく地元優先であること。 ローカルの範囲はまず[[:ja:レシフェ|レシフェ]]、[[:ja:ミュンヘン|ミュンヘン]]、[[:ja:サンクトペテルブルク|サンクトペテルブルク]]などから始めるのがよく、ブラジル、ドイツ、ロシアなどは現実的ではありません。 <span lang="en" dir="ltr" class="mw-content-ltr">If you miss a channel for regional coordination then consider [[m:Special:MyLanguage/Mailing lists#Create a new list|requesting the creation]] of a [[m:Special:MyLanguage/Mailing lists/Overview#Regional mailing lists|regional mailing list]] and/or [[m:Special:MyLanguage/Mailing lists/Overview#Local|local mailing list]].</span> == グループの設立 == 誰かが設立を表明するのを待つのではなく、あなたご自身が発起人になってください。 承認の条件は、貢献者が3名以上参加することです。 自身の MediaWiki グループを立ち上げるには、[[Groups/Proposals]] で詳細を確認してください。 [[Category:MediaWiki Communication{{#translation:}}]] a44cljfegzssz3qkifzgesik4sprlt1 Manual:Namespace/it 100 275212 5386616 5385942 2022-07-28T17:02:26Z GpieroMW 17587484 Created page with "L'elenco completo è mostrato nella tabella sotto." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione <div lang="en" dir="ltr" class="mw-content-ltr"> * 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces. </div> L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Editing a User talk page generates a notification for the user.</span></ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | <span lang="en" dir="ltr" class="mw-content-ltr">Information about the wiki.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | <span lang="en" dir="ltr" class="mw-content-ltr">Category description pages</span> | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | <span lang="en" dir="ltr" class="mw-content-ltr">Holds special pages</span> | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> <span lang="en" dir="ltr" class="mw-content-ltr">File and Category pages have special functionality, as described in {{ll|Help:Managing files}} and {{ll|Help:Categories}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Files can be moved by users with the "movefile" right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] </div> * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 8piwsrdhh1k5as77in5vv76wliobfrw 5386618 5386616 2022-07-28T17:04:36Z GpieroMW 17587484 Created page with "Modificare una pagina di discussione utente genera una notifica per l'utente." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione <div lang="en" dir="ltr" class="mw-content-ltr"> * 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces. </div> L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | <span lang="en" dir="ltr" class="mw-content-ltr">Information about the wiki.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | <span lang="en" dir="ltr" class="mw-content-ltr">Category description pages</span> | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | <span lang="en" dir="ltr" class="mw-content-ltr">Holds special pages</span> | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> <span lang="en" dir="ltr" class="mw-content-ltr">File and Category pages have special functionality, as described in {{ll|Help:Managing files}} and {{ll|Help:Categories}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Files can be moved by users with the "movefile" right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] </div> * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 6276ft554w22fey6dw7940u1z7v4s5g 5386620 5386618 2022-07-28T17:04:45Z GpieroMW 17587484 Created page with "Informazione sul wiki." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione <div lang="en" dir="ltr" class="mw-content-ltr"> * 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces. </div> L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | <span lang="en" dir="ltr" class="mw-content-ltr">Category description pages</span> | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | <span lang="en" dir="ltr" class="mw-content-ltr">Holds special pages</span> | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> <span lang="en" dir="ltr" class="mw-content-ltr">File and Category pages have special functionality, as described in {{ll|Help:Managing files}} and {{ll|Help:Categories}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Files can be moved by users with the "movefile" right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] </div> * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 8mz8386v9zofotqxy13c1dd65qdw7ip 5386622 5386620 2022-07-28T17:05:18Z GpieroMW 17587484 Created page with "Contiene pagine speciali" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione <div lang="en" dir="ltr" class="mw-content-ltr"> * 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces. </div> L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | <span lang="en" dir="ltr" class="mw-content-ltr">Category description pages</span> | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> <span lang="en" dir="ltr" class="mw-content-ltr">File and Category pages have special functionality, as described in {{ll|Help:Managing files}} and {{ll|Help:Categories}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Files can be moved by users with the "movefile" right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] </div> * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] gczw1xzd3jcr4k8f75782ofql8unfkj 5386624 5386622 2022-07-28T17:05:33Z GpieroMW 17587484 Created page with "Pagine di descrizione di categorie" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione <div lang="en" dir="ltr" class="mw-content-ltr"> * 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces. </div> L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> <span lang="en" dir="ltr" class="mw-content-ltr">File and Category pages have special functionality, as described in {{ll|Help:Managing files}} and {{ll|Help:Categories}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Files can be moved by users with the "movefile" right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] </div> * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 35i3f9auruvecqo8yfs4fxvhcd8v6pu 5386626 5386624 2022-07-28T17:06:29Z GpieroMW 17587484 Created page with "* [[$confset-ns|Manual:Configuration settings#Namespaces]]" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione <div lang="en" dir="ltr" class="mw-content-ltr"> * 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces. </div> L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> <span lang="en" dir="ltr" class="mw-content-ltr">File and Category pages have special functionality, as described in {{ll|Help:Managing files}} and {{ll|Help:Categories}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Files can be moved by users with the "movefile" right.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] kptw51croojvf2nbq63v0mejiw5lx38 5386628 5386626 2022-07-28T17:07:23Z GpieroMW 17587484 Created page with "I file possono essere spostati dagli utenti con il permesso "$1"." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione <div lang="en" dir="ltr" class="mw-content-ltr"> * 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces. </div> L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> <span lang="en" dir="ltr" class="mw-content-ltr">File and Category pages have special functionality, as described in {{ll|Help:Managing files}} and {{ll|Help:Categories}}.</span> I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] q86yw7vaeqogq1pbw1ok2qyf4m5cobw 5386630 5386628 2022-07-28T17:08:14Z GpieroMW 17587484 Created page with "Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in $h-manage e $h-cat." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione <div lang="en" dir="ltr" class="mw-content-ltr"> * 2 "virtual" namespaces (one for dynamically generated special pages, and one serving as an alias for direct file links), numbered -1 and -2, respectively. Since these namespaces don't correspond to pages stored in the database, one cannot create or delete pages in these namespaces, and there are no corresponding discussion namespaces. </div> L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] kf5nt63591c4tdbn704bdr8dybs94zq 5387710 5386630 2022-07-29T06:14:52Z GpieroMW 17587484 Created page with "* 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | <span lang="en" dir="ltr" class="mw-content-ltr">Site interface customization</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] mh4zom27t5j5kr3ahluijsvkur4ard1 5387712 5387710 2022-07-29T06:15:14Z GpieroMW 17587484 Created page with "Personalizzazione dell'interfaccia del sito" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref><span lang="en" dir="ltr" class="mw-content-ltr">Only editable by users with the '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]' permission.</span><br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] np69v57j8j7g4b1hslb4auhlvumo81v 5387714 5387712 2022-07-29T06:15:43Z GpieroMW 17587484 Created page with "Modificabile solo dall'utente con permessi '[[$edit-if|editinterface]]'." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | <span lang="en" dir="ltr" class="mw-content-ltr">Template pages</span> | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] saz94bdcasmouzetauuk816vfpwwc7s 5387716 5387714 2022-07-29T06:16:03Z GpieroMW 17587484 Created page with "Pagine template" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Custom namespaces== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 5knp3iaruw0c0qw3m12j8n6g5xe25iu 5387718 5387716 2022-07-29T06:16:18Z GpieroMW 17587484 Created page with "=== Namespace personalizzati ===" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === <span lang="en" dir="ltr" class="mw-content-ltr">Extensions and site administrators can define additional namespaces to group additional classes of pages together.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] nyg8nejz5koq41e99113u0kapctggvk 5387720 5387718 2022-07-29T06:17:11Z GpieroMW 17587484 Created page with "Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">The subject namespace has no prefix.</span></ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] hmf7ndpq0s4yzokriqj21r6zeyrykkx 5387724 5387720 2022-07-29T06:18:52Z GpieroMW 17587484 Created page with "Il namespace soggetto non ha prefisso." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Help:User page|User pages}}.</span><ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] tc4h3vaapa7snpk9yep3gpybqxtd501 5387726 5387724 2022-07-29T06:19:08Z GpieroMW 17587484 Created page with "{{$1|Pagine utente}}." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref><span lang="en" dir="ltr" class="mw-content-ltr">Defined by <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, which unless manually set otherwise, defaults to <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</span></ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 7fwxqgu95gr3sjxr766cwser6x8x6vt 5387728 5387726 2022-07-29T06:20:07Z GpieroMW 17587484 Created page with "Definito da $1, e se non impostato manualmente in modo diverso, ha come valore predefinito $2." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. <div lang="en" dir="ltr" class="mw-content-ltr"> === Subject and talk namespaces === </div> :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] qsa1ax8jdqo4zg0ig4h7g77ji649i09 5387730 5387728 2022-07-29T06:20:29Z GpieroMW 17587484 Created page with "=== Namespace soggetti e discussioni ===" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | <span lang="en" dir="ltr" class="mw-content-ltr">Talk</span> |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] ks8j3mwg31op4gepysnb027dchvcqhk 5387732 5387730 2022-07-29T06:20:44Z GpieroMW 17587484 Created page with "Discussione" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. <span lang="en" dir="ltr" class="mw-content-ltr">For a thorough overview, see {{ll|Manual:Using custom namespaces}}.</span> ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 7ra2n3sr3a53hg8hh1opfjlt3tfjwtk 5387734 5387732 2022-07-29T06:21:38Z GpieroMW 17587484 Created page with "Per una panoramica approfondita, vedere $1." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== <div lang="en" dir="ltr" class="mw-content-ltr"> Some namespaces, like Project and Help, only exist for convenience and do not have any extra functionality compared to the Main namespace. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] nz3fafj5n8njoxxlsdkjfyq2sr9bzmy 5387736 5387734 2022-07-29T06:23:11Z GpieroMW 17587484 Created page with "Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. <div lang="en" dir="ltr" class="mw-content-ltr"> Template namespace pages can be [[Special:MyLanguage/Help:Transclusion|transcluded]] without namespace prefix. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] kkbl3mjfgkr1w6ahnansi8j7zrylijc 5387738 5387736 2022-07-29T06:24:18Z GpieroMW 17587484 Created page with "Le pagine del namespace dei template possono essere [[$transclusion|transcluded]] senza il prefisso del namespace." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. <div lang="en" dir="ltr" class="mw-content-ltr"> User namespace pages are associated with user accounts or IP addresses. Changes to [[Special:MyLanguage/Help:Talk pages#User talk pages|user talk pages]] generate an automatic message notification. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] b25ogq9202v4d1nzpp4o4kspwp0dcwo 5387740 5387738 2022-07-29T06:25:19Z GpieroMW 17587484 Created page with "Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[$user-talkpg|pagine di discussione degli utenti]] generano un messaggio di notifica automatico." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". <span lang="en" dir="ltr" class="mw-content-ltr">Category pages can be moved by users with the "move-categorypages" right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] ry6zkleni67s8uxvx60e4gqb5hoprra 5387742 5387740 2022-07-29T06:26:04Z GpieroMW 17587484 Created page with "Le pagine Categorie possono essere spostate dagli utenti con permesso "$1"." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Built-in namespaces== </div> MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] jg1rd9zhvpi3r2o04w0hm8ci2br6f78 5387748 5387742 2022-07-29T08:13:38Z GpieroMW 17587484 Created page with "==Namespaces incorporati==" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> ==Namespaces incorporati== MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. <div lang="en" dir="ltr" class="mw-content-ltr"> Pages in the [[Special:MyLanguage/Help:System message|"MediaWiki" namespace]] are used to override default messages in [[Special:MyLanguage/Localisation|language file]] and can only be edited by administrators or other users with the [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]] permission. </div> Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] eab51pu7s3fts9bq9iwibvrfvqmqsyl 5387750 5387748 2022-07-29T08:15:19Z GpieroMW 17587484 Created page with "Le pagine nel namespace [[$sysmsg|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[$locale|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[$edit-if|editinterface]]." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> ==Namespaces incorporati== MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Each namespace also has a constant derived from its name, with all letters in uppercase, spaces replaced by underscores, and prefixed by "NS_". For example, the constant for the "User talk" namespace is NS_USER_TALK. A complete list can be found in {{ll|Manual:Namespace constants}}. </div> ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. Le pagine nel namespace [[Special:MyLanguage/Help:System message|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[Special:MyLanguage/Localisatione|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]. Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 6oryaoh2eq9yfws2h0ijnhzsofwq4fa 5387752 5387750 2022-07-29T08:16:12Z GpieroMW 17587484 Created page with "Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in $1." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> ==Namespaces incorporati== MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | <span lang="en" dir="ltr" class="mw-content-ltr">Alias for direct links to media files</span> |} Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in {{ll|Manual:Namespace constants}}. ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. Le pagine nel namespace [[Special:MyLanguage/Help:System message|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[Special:MyLanguage/Localisatione|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]. Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 78wo262g12710n156sid9we4d66ioyl 5387755 5387752 2022-07-29T08:23:52Z GpieroMW 17587484 Created page with "Alias per collegamenti diretti a file audio video" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> ==Namespaces incorporati== MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=<span lang="en" dir="ltr" class="mw-content-ltr">Some [[Special:MyLanguage/Manual:$wgRawHtmlMessages|few pages]] in this namespace require <code>editsitecss</code> and <code>editesitejs</code> permissions, in addition to that.</span>}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | Alias per collegamenti diretti a file audio video |} Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in {{ll|Manual:Namespace constants}}. ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. Le pagine nel namespace [[Special:MyLanguage/Help:System message|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[Special:MyLanguage/Localisatione|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]. Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] d5sxdpy5l23qnqv1o0n6r16tyc2erez 5387758 5387755 2022-07-29T08:27:50Z GpieroMW 17587484 Created page with "Solo [[$1|alcunew pagine]] in questo namespace richiedono i permessi $2 e $3, oltre a questo." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> ==Namespaces incorporati== MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=Solo [[Special:MyLanguage/Manual:$wgRawHtmlMessages|alcunew pagine]] in questo namespace richiedono i permessi <code>editsitecss</code> e <code>editesitejs</code>, oltre a questo.}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | Alias per collegamenti diretti a file audio video |} Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in {{ll|Manual:Namespace constants}}. ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. Le pagine nel namespace [[Special:MyLanguage/Help:System message|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[Special:MyLanguage/Localisatione|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]. Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] h5g331zq5x0dt5vwd9zcukzyczru2j9 5387760 5387758 2022-07-29T08:28:04Z GpieroMW 17587484 typo wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> ==Namespaces incorporati== MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | <span lang="en" dir="ltr" class="mw-content-ltr">Media description pages</span> | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=Solo [[Special:MyLanguage/Manual:$wgRawHtmlMessages|alcune pagine]] in questo namespace richiedono i permessi <code>editsitecss</code> e <code>editesitejs</code>, oltre a questo.}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | Alias per collegamenti diretti a file audio video |} Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in {{ll|Manual:Namespace constants}}. ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. Le pagine nel namespace [[Special:MyLanguage/Help:System message|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[Special:MyLanguage/Localisatione|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]. Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 0abliehc1l6ndqpbz6n262u87du9ty4 5387762 5387760 2022-07-29T08:28:42Z GpieroMW 17587484 Created page with "Pagine di descrizione di multimedia" wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> ==Namespaces incorporati== MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgContentNamespaces|"Real" content articles}}.</span><ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | Pagine di descrizione di multimedia | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=Solo [[Special:MyLanguage/Manual:$wgRawHtmlMessages|alcune pagine]] in questo namespace richiedono i permessi <code>editsitecss</code> e <code>editesitejs</code>, oltre a questo.}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | Alias per collegamenti diretti a file audio video |} Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in {{ll|Manual:Namespace constants}}. ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. Le pagine nel namespace [[Special:MyLanguage/Help:System message|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[Special:MyLanguage/Localisatione|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]. Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] tehhyrs1u1vlhf85433dkpvorcr8dr0 5387764 5387762 2022-07-29T08:30:11Z GpieroMW 17587484 Created page with "{{$1|Articoli di contenuto "reale"}}." wikitext text/x-wiki <languages/> Un '''namespace''' è un insieme di pagine i cui contenuti possiedono uno scopo analogo, cioè la cui destinazione d'uso è la stessa. I namespace possono essere pensati come partizioni all'interno dello stesso wiki, ognuna delle quali raccoglie un differente tipo di informazioni, che mantengono il "vero" contenuto separato da [[Special:PrefixIndex/User:|profili utente]], [[Special:PrefixIndex/Help:|pagine di aiuto]] ecc. ==Panoramica tecnica== Le pagine esistono all'interno di un namespace ed esso può essere contraddistinto dal '''prefisso''' di una pagina, separato dal resto del titolo con i due punti (<code>:</code>). Per esempio: {| class="wikitable" ! Titolo !! Namespace ! Codice |- | <code>Foo</code> || Main |0 |- | <code>Template:Foo</code> || Template |10 |- | <code>Module:Foo</code> || Module |828 |} Il "namespace principale" non ha un prefisso. In più, le pagine del namespace principale non possono avere nomi il cui inizio coincide al prefisso di un namespace esistente seguito dai due punti. Le pagine posso essere [[Special:MyLanguage/Help:Moving a page|spostate]] tra un namespace e l'altro semplicemente cambiandone la parte del titolo corrispondente al prefisso. I prefissi dei namespace possono essere tradotti e per ognuno di essi possono essere configurati alias (vedi <code>{{ll|Manual:$wgNamespaceAliases|$wgNamespaceAliases}}</code>). Tutti i namespace hanno anche un prefisso "canonico", che funziona su tutti i wiki indipendentemente dalla configurazione. Gli alias e i nomi canonici possono essere usati nei link, nell'eseguire una [[Special:MyLanguage/Help:Searching|ricerca]] e nel titolo della pagina con l'aiuto della [[Special:MyLanguage/Help:Magic words|parola magica]] <nowiki>{{DISPLAYTITLE}}</nowiki>. Ogni namespace ha un corrispondente ''indice del namespace''. All'interno del database, il titolo è suddiviso in indice del namespace e titolo del testo, che viene utilizzato per la memorizzazione nelle colonne <code>page.page_namespace</code> e <code>page.page_title</code>, tra le altre. === Namespace soggetti e discussioni === :''Vedere {{ll|Help:Talk pages}} per istruzioni sull'utilizzo della pagine di discussione.'' La maggioranza dei namespace hanno un '''namespace di discussione''' associato (o namespace "talk"). Tutti i namespace di discussione hanno indici dispari interi e l'indice del namespace di discussione in un spazio di nomi specifici con l'indice ''n'' è ''n+1''. I namespace con gli indici interi sono '''namespace di soggetti''' (si noti che questo è un concetto distinto da [[Special:MyLanguage/Manual:$wgContentNamespaces|namespace di contenuto]]). Il dualismo tra il soggetto e la discussione si può esplorare utilizzando le [[Special:MyLanguage/Help:Magic words#Page names|parole magiche]] <code><nowiki>{{SUBJECTPAGENAME}}</nowiki></code> e <code><nowiki>{{TALKPAGENAME}}</nowiki></code>. L'etichetta {{tag|body|open}} delle pagine nel namespace di discussione ha la classe CSS "<code>ns-talk</code>", che potrebbe essere utile nello stile. {{anchor|built-in-namespaces|Built-in_namespaces}}<!-- Anchor name is used to link to this section with Special:MyLanguage (since the title would be translated) --> ==Namespaces incorporati== MediaWiki viene fornito con 18 namespace integrati: * 16 namespace "reali", corrispondenti alle pagine effettive, numerate da 0 a 15, e raggruppate in coppie soggetto/discussione * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. L'elenco completo è mostrato nella tabella sotto. {| class="wikitable" |- ! Indice ! Nome ! Scopo ! colspan="2" | Discussione |- ! 0 | (Main) | {{ll|Manual:$wgContentNamespaces|Articoli di contenuto "reale"}}.<ref>Il namespace soggetto non ha prefisso.</ref> | {{ns:1}} ! 1 |- ! 2 | {{ns:2}} | {{ll|Help:User page|Pagine utente}}.<ref>Modificare una pagina di discussione utente genera una notifica per l'utente.</ref> | {{ns:3}} ! 3 |- ! 4 | {{ns:4}} | Informazione sul wiki.<ref>Definito da <code>{{ll|Manual:$wgMetaNamespace|$wgMetaNamespace}}</code>, e se non impostato manualmente in modo diverso, ha come valore predefinito <code>{{ll|Manual:$wgSitename|$wgSitename}}</code>.</ref> | {{ns:5}} ! 5 |- ! 6 | {{ns:6}} | Pagine di descrizione di multimedia | {{ns:7}} ! 7 |- ! 8 | {{ns:8}} | Personalizzazione dell'interfaccia del sito<ref>Modificabile solo dall'utente con permessi '[[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]'.<br/>{{note|inline=1|1=Solo [[Special:MyLanguage/Manual:$wgRawHtmlMessages|alcune pagine]] in questo namespace richiedono i permessi <code>editsitecss</code> e <code>editesitejs</code>, oltre a questo.}}</ref> | {{ns:9}} ! 9 |- ! 10 | {{ns:10}} | Pagine template | {{ns:11}} ! 11 |- ! 12 | {{ns:12}} | Pagine di aiuto | {{ns:13}} ! 13 |- ! 14 | {{ns:14}} | Pagine di descrizione di categorie | {{ns:15}} ! 15 |- ! colspan="5" | |- ! -1 | Special | Contiene pagine speciali | colspan="2" rowspan="2" style="background:#ddd; text-align:center; vertical-align:middle;" | N/A |- ! -2 | Media | Alias per collegamenti diretti a file audio video |} Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in {{ll|Manual:Namespace constants}}. ---- <references /> === Namespace personalizzati === Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. Per una panoramica approfondita, vedere {{ll|Manual:Using custom namespaces}}. ==Funzionalità== Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. Le pagine del namespace dei template possono essere [[Special:MyLanguage/Help:Transclusion|transcluded]] senza il prefisso del namespace. Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[Special:MyLanguage/Help:Talk pages#User talk pages|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. Le pagine nel namespace [[Special:MyLanguage/Help:System message|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[Special:MyLanguage/Localisatione|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[Special:MyLanguage/Manual:User rights#editinterface|editinterface]]. Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in {{ll|Help:Managing files}} e {{ll|Help:Categories}}. I file possono essere spostati dagli utenti con il permesso "movefile". Le pagine Categorie possono essere spostate dagli utenti con permesso "move-categorypages". <div lang="en" dir="ltr" class="mw-content-ltr"> All pages in discussion namespaces have a "post a comment" feature (see [[meta:Special:MyLanguage/Help:Section#Adding a section at the end|Help:Section#Adding a section at the end]] on Meta). </div> == Vedi anche == * {{Ll|Help:Namespaces}} * {{Ll|Extension default namespaces}} * [[Special:MyLanguage/Manual:Configuration settings#Namespaces|Manual:Configuration settings#Namespaces]] * {{Ll|Manual:Help namespace}} * {{Ll|Manual:Using custom namespaces}} * {{Ll|Manual:Namespace constants}} <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|Manual:MWNamespace.php}}, containing the MWNamespace class * [[meta:Special:MyLanguage/Help:Namespace|Help:Namespace]] on [[m:|Meta]] </div> (outdated) [[Category:Namespace{{#translation:}}|{{PAGENAME}}]] 0re4aq3rc3uq6hjw5kbwrk4am28wmmb Translations:Manual:Installation guide/11/uk 1198 294157 5387282 4731969 2022-07-28T21:55:41Z Baris6161TURK 17188421 wikitext text/x-wiki Для cтворення мініатюр зображень потрібні додаткові програми. $1 (потрібний для VisualEditor) та інші служби мають власні потреби. f1j7b6xbi3jbb3q5x0e51doe6ihpehp Translations:Manual:Installation guide/11/el 1198 299268 5387284 4700836 2022-07-28T21:55:53Z Baris6161TURK 17188421 wikitext text/x-wiki Η μικρογραφία εικόνας απαιτεί επιπλέον προγράμματα. Το $1 (απαιτείται από τον Οπτικό επεξεργαστή) και άλλες υπηρεσίες έχουν τις δικές τους απαιτήσεις. dub177p7m00ek3oes9o8fxvr59cyi3w Manual:Installation guide/tr 100 311495 5386672 5383501 2022-07-28T17:14:37Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/tr]] 5f585xjemd904uqfsrqnejiy5zjz0jz Manual:Installation guide/diq 100 311499 5386644 5381079 2022-07-28T17:14:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/diq]] 0pemp547h60v1saozgmt9wq27yug3ez 5386681 5386644 2022-07-28T17:18:16Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/diq]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Groups/pt-br 0 316706 5387361 5190129 2022-07-28T22:11:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Grupos do MediaWiki''' organizam atividades da comunidade open source dentro do escopo de tópicos específicos e áreas geográficas. <span lang="en" dir="ltr" class="mw-content-ltr">They are [[meta:Special:MyLanguage/Wikimedia user groups|Wikimedia User Groups]] that agree on a level of coordination in the MediaWiki context.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As such, they extend the capacity of the [[wmf:|Wikimedia Foundation]] in [[Events|events]], [[Volunteer coordination and outreach/Training materials|training]], promotion and other technical activities benefiting Wikipedia, the Wikimedia movement and the MediaWiki software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki Groups are open to members of [[Special:MyLanguage/How to contribute|different specialties]] and levels of expertise.</span> Quanto mais rico e diversificado, melhor. <span lang="en" dir="ltr" class="mw-content-ltr">Non-technical users willing to contribute and learn are welcome too! All groups commit to the [[wmf:Friendly space policy|Friendly space policy]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki groups can [[Groups/Wikimedia support|request support]] from the Wikimedia Foundation and chapters in various forms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Thematic groups == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Thematic MediaWiki groups collaborate with their logical counterparts in the wider [[w:FLOSS|FLOSS]] community. They are global groups, collaborating online. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They are in touch with communities within the same focus. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They participate in events of the same topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They promote related training and outreach activities. </div> * Eles ajudam a melhorar a documentação relacionada em wikimedia.org. * Eles colaboram com as equipes de desenvolvimento relacionadas. * Eventualmente, alguns deles se encontram na [//wikimania.wikimedia.org/ Wikimania]. == Grupos locais == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> <span lang="en" dir="ltr" class="mw-content-ltr">Local MediaWiki groups collaborate with [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia chapters]], See also [[w:Wikipedia:Meetup|Wikipedia meetups]] and other local communities related with Wikimedia, free software, free culture...</span> Seu foco consiste em atividades face a face: <div lang="en" dir="ltr" class="mw-content-ltr"> * Organization of local events: meetups, training, hackfests... These events adhere to the [[wmf:Friendly_space_policy|WMF Friendly space policy]]. </div> * Participação em eventos realizados em sua área. * Distribuição de merchandising. * Promoção de colaboradores locais para atividades globais da MediaWiki e da Wikimedia. <div class="mw-translate-fuzzy"> Também para grupos que não falam inglês: * Localização de documentação e software seguindo processos do [[Special:MyLanguage/translatewiki.net|translatewiki.net]]. </div> Grupos locais devem ser realmente locais. Pontos de partida, como por exemplo Recife, Munique ou São Petersburgo são melhores que o Brasil, a Alemanha ou a Rússia. <span lang="en" dir="ltr" class="mw-content-ltr">If you miss a channel for regional coordination then consider [[m:Special:MyLanguage/Mailing lists#Create a new list|requesting the creation]] of a [[m:Special:MyLanguage/Mailing lists/Overview#Regional mailing lists|regional mailing list]] and/or [[m:Special:MyLanguage/Mailing lists/Overview#Local|local mailing list]].</span> == Criando um grupo == <span lang="en" dir="ltr" class="mw-content-ltr">You don't need anyone to propose a group, just yourself.</span> Para obtê-lo aprovado, você deve ter pelo menos três colaboradores. <div lang="en" dir="ltr" class="mw-content-ltr"> Check [[Groups/Proposals]] for more details to create your MediaWiki group. </div> [[Category:MediaWiki Communication{{#translation:}}]] sedoqqo8g2yw6o3bk5tj5d4fw0si1hi 5387415 5387361 2022-07-28T22:15:34Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Grupos do MediaWiki''' organizam atividades da comunidade open source dentro do escopo de tópicos específicos e áreas geográficas. <span lang="en" dir="ltr" class="mw-content-ltr">They are [[meta:Special:MyLanguage/Wikimedia user groups|Wikimedia User Groups]] that agree on a level of coordination in the MediaWiki context.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As such, they extend the capacity of the [[wmf:|Wikimedia Foundation]] in [[Events|events]], [[Volunteer coordination and outreach/Training materials|training]], promotion and other technical activities benefiting Wikipedia, the Wikimedia movement and the MediaWiki software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki Groups are open to members of [[Special:MyLanguage/How to contribute|different specialties]] and levels of expertise.</span> Quanto mais rico e diversificado, melhor. <span lang="en" dir="ltr" class="mw-content-ltr">Non-technical users willing to contribute and learn are welcome too! All groups commit to the [[wmf:Friendly space policy|Friendly space policy]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki groups can [[Groups/Wikimedia support|request support]] from the Wikimedia Foundation and chapters in various forms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Thematic groups == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Thematic MediaWiki groups collaborate with their logical counterparts in the wider [[w:FLOSS|FLOSS]] community. They are global groups, collaborating online. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They are in touch with communities within the same focus. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They participate in events of the same topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * They promote related training and outreach activities. </div> * Eles ajudam a melhorar a documentação relacionada em wikimedia.org. * Eles colaboram com as equipes de desenvolvimento relacionadas. * Eventualmente, alguns deles se encontram na [//wikimania.wikimedia.org/ Wikimania]. == Grupos locais == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> <span lang="en" dir="ltr" class="mw-content-ltr">Local MediaWiki groups collaborate with [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia chapters]], See also [[w:Wikipedia:Meetup|Wikipedia meetups]] and other local communities related with Wikimedia, free software, free culture...</span> Seu foco consiste em atividades face a face: <div lang="en" dir="ltr" class="mw-content-ltr"> * Organization of local events: meetups, training, hackfests... These events adhere to the [[wmf:Friendly_space_policy|WMF Friendly space policy]]. </div> * Participação em eventos realizados em sua área. * Distribuição de merchandising. * Promoção de colaboradores locais para atividades globais da MediaWiki e da Wikimedia. Também para grupos que não falam inglês: * Localização de documentação e software seguindo processos do [[Special:MyLanguage/translatewiki.net|translatewiki.net]]. Grupos locais devem ser realmente locais. Pontos de partida, como por exemplo Recife, Munique ou São Petersburgo são melhores que o Brasil, a Alemanha ou a Rússia. <span lang="en" dir="ltr" class="mw-content-ltr">If you miss a channel for regional coordination then consider [[m:Special:MyLanguage/Mailing lists#Create a new list|requesting the creation]] of a [[m:Special:MyLanguage/Mailing lists/Overview#Regional mailing lists|regional mailing list]] and/or [[m:Special:MyLanguage/Mailing lists/Overview#Local|local mailing list]].</span> == Criando um grupo == <span lang="en" dir="ltr" class="mw-content-ltr">You don't need anyone to propose a group, just yourself.</span> Para obtê-lo aprovado, você deve ter pelo menos três colaboradores. <div lang="en" dir="ltr" class="mw-content-ltr"> Check [[Groups/Proposals]] for more details to create your MediaWiki group. </div> [[Category:MediaWiki Communication{{#translation:}}]] m64t0x1tsuztrwlgr2ngk1p82icjtw7 Manual:Installation guide/fi 100 332686 5386649 5381086 2022-07-28T17:14:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/fi]] gn4d8iwiwl5d41w4mpykqlgioeembqu Phabricator/Projects 0 340261 5386454 5385538 2022-07-28T14:11:35Z Crystal-bot 5243179 Bot: Updating project taxonomy wikitext text/x-wiki {{/Header}} Data as of: 14:11, 28 July 2022 (UTC) === Projects === * [[phab:project/view/5930/|2022 Wikimedia Google.org Fellowship]] * [[phab:project/view/1929/|3D]] * [[phab:project/view/3147/|3D2Commons]] * [[phab:project/view/5054/|Abstract Wikipedia UX]] * [[phab:project/view/217/|AbuseFilter]] * Accuracy ** [[phab:project/view/1994/|Accuracy-Review-of-Wikipedias]] * Acme ** [[phab:project/view/3694/|Acme-chief]] * [[phab:project/view/651/|ActiveAbstract]] * Add ** [[phab:project/view/5045/|Add-Link]] * address ** [[phab:project/view/4382/|address-knowledge-gaps]] * [[phab:project/view/3755/|Advanced Mobile Contributions]] * Advanced ** [[phab:project/view/2798/|Advanced-Search]] * [[phab:project/view/1295/|AhoCorasick]] * AHT ** [[phab:project/view/5313/|AHT-Roadmap]] * [[phab:project/view/527/|AJAXPoll]] * [[phab:project/view/11/|Analytics]] ** [[phab:project/view/655/|Analytics-Clusters]] ** [[phab:project/view/817/|Analytics-Dashiki]] ** [[phab:project/view/2886/|Analytics-Data-Quality]] ** [[phab:project/view/3711/|Analytics-Jupyter]] ** [[phab:project/view/3153/|Analytics-Legal]] ** [[phab:project/view/4824/|Analytics-Radar]] ** [[phab:project/view/206/|Analytics-Wikistats]] * [[phab:project/view/2255/|Android Design]] * Android ** [[phab:project/view/2824/|Android-app-feature-Compilations-v1]] ** [[phab:project/view/2237/|Android-app-feature-Description-Editing]] * [[phab:project/view/3826/|Anisa]] * [[phab:project/view/257/|AntiSpoof]] * [[phab:project/view/941/|Apex]] * [[phab:project/view/5376/|API Platform]] * API ** [[phab:project/view/5046/|API-Portal]] * [[phab:project/view/842/|ApiFeatureUsage]] * [[phab:project/view/4465/|Application Security Reviews]] * Arc ** [[phab:project/view/4222/|Arc-Lamp]] * Article ** [[phab:project/view/1351/|Article-Recommendation]] ** [[phab:project/view/2749/|Article-Reminder-Notifications]] * [[phab:project/view/481/|ArticleFeedbackv5]] * [[phab:project/view/1416/|ArticlePlaceholder]] * articlequality ** [[phab:project/view/1675/|articlequality-modeling]] * [[phab:project/view/1948/|ArticleRatings]] * [[phab:project/view/4724/|Articles Needing links]] * at ** [[phab:project/view/1304/|at-ease]] ** [[phab:project/view/5890/|Authentication-Experiments-2022]] * [[phab:project/view/5713/|Auto schema]] * [[phab:project/view/2294/|Automated list generation]] * [[phab:project/view/1012/|AutoWikiBrowser]] * AvoinGLAM ** [[phab:project/view/4190/|AvoinGLAM-Saami]] * [[phab:project/view/5371/|bacula]] * Bad ** [[phab:project/view/1470/|Bad-Words-Detection-System]] * [[phab:project/view/3372/|base_convert]] * Beta ** [[phab:project/view/497/|Beta-Cluster-Infrastructure]] * [[phab:project/view/741/|BetaFeatures]] * [[phab:project/view/1250/|BiblioPlus]] * [[phab:project/view/676/|BlogPage]] * [[phab:project/view/1092/|BlueSky]] * Book ** [[phab:project/view/4256/|Book-Referencing]] * Bot ** [[phab:project/view/2746/|Bot-Frameworks]] * [[phab:project/view/2258/|Bouquet]] * [[phab:project/view/5662/|CampaignEvents]] * [[phab:project/view/1976/|Cassandra]] * [[phab:project/view/1808/|CatWatch]] * CFSSL ** [[phab:project/view/5338/|CFSSL-PKI]] * [[phab:project/view/2264/|Challenge]] * [[phab:project/view/2114/|ChangeProp]] * [[phab:project/view/185/|CharInsert]] * [[phab:project/view/203/|CheckUser]] * [[phab:project/view/4398/|ChessBrowser]] * [[phab:project/view/209/|CirrusSearch]] * [[phab:project/view/172/|Cite]] ** [[phab:project/view/4050/|Cite-Unseen]] * [[phab:project/view/980/|CiteThisPage]] * [[phab:project/view/62/|Citoid]] * [[phab:project/view/5263/|Cloud Services Proposals]] * Cloud ** [[phab:project/view/474/|Cloud-VPS]] * Code ** [[phab:project/view/3672/|Code-Health-First-Responder]] ** [[phab:project/view/3779/|Code-Health-Newsletter]] * [[phab:project/view/580/|CodeEditor]] * [[phab:project/view/5587/|Codex]] * [[phab:project/view/2320/|Cognate]] * Collab ** [[phab:project/view/1922/|Collab-Notifications-Page]] ** [[phab:project/view/1691/|Collaboration-Community-Engagement]] * [[phab:project/view/329/|Collection]] * [[phab:project/view/322/|CologneBlue]] * commit ** [[phab:project/view/2163/|commit-message-validator]] * [[phab:project/view/4829/|CommonPasswords]] * [[phab:project/view/5429/|Commons Deletion Notification bot]] * Commons ** [[phab:project/view/1986/|Commons-Datasets]] ** [[phab:project/view/3166/|Commons-Mass-Description]] ** [[phab:project/view/3616/|Commons-Twitter-Bot]] * [[phab:project/view/736/|CommonsMetadata]] * CommRel ** [[phab:project/view/3456/|CommRel-Documentation]] ** [[phab:project/view/3451/|CommRel-Specialists-Support]] * Community ** [[phab:project/view/973/|Community-IdeaLab]] * community ** [[phab:project/view/2348/|community-labs-monitoring]] * Community ** [[phab:project/view/978/|Community-LearningPatterns]] * [[phab:project/view/3862/|Confirmation prompt for rollback action]] * [[phab:project/view/225/|ConfirmEdit (CAPTCHA extension)]] * [[phab:project/view/4218/|conftool]] * [[phab:project/view/776/|ContentTranslation]] * Continuous ** [[phab:project/view/401/|Continuous-Integration-Infrastructure]] * [[phab:project/view/388/|ContributionScores]] * Convenient ** [[phab:project/view/3851/|Convenient-Discussions]] * [[phab:project/view/1638/|CopyPatrol]] * [[phab:project/view/5017/|Cosmos]] * [[phab:project/view/5841/|CoverMe]] * COVID ** [[phab:project/view/4721/|COVID-19 Global Dashboard]] ** [[phab:project/view/4676/|COVID-19-Graphics]] * [[phab:project/view/5309/|CreateAPage]] * [[phab:project/view/1224/|crosswatch]] * css ** [[phab:project/view/2598/|css-sanitizer]] * CX ** [[phab:project/view/3437/|CX-analytics]] ** [[phab:project/view/4191/|CX-boost]] ** [[phab:project/view/3435/|CX-cxserver]] ** [[phab:project/view/3421/|CX-deployments]] ** [[phab:project/view/3434/|CX-mobile]] ** [[phab:project/view/3419/|CX-out-of-beta]] ** [[phab:project/view/3457/|CX-template-improvements]] ** [[phab:project/view/3420/|CX-TranslationList]] * [[phab:project/view/2669/|Cyberbot]] * [[phab:project/view/4006/|DarkMode]] * [[phab:project/view/6010/|Data Engineering Planning]] * [[phab:project/view/5616/|Data Pipelines]] * [[phab:project/view/4422/|Data Protection]] * Data ** [[phab:project/view/5697/|Data-Catalog]] ** [[phab:project/view/5996/|Data-Engineering-Operations]] ** [[phab:project/view/4997/|Data-Persistence-Backup]] ** [[phab:project/view/5006/|Data-Persistence-Misc]] ** [[phab:project/view/1393/|Data-release]] ** [[phab:project/view/2874/|Data-Services]] * database ** [[phab:project/view/5372/|database-backups]] * Datasets ** [[phab:project/view/1135/|Datasets-Archiving]] ** [[phab:project/view/189/|Datasets-General-or-Unknown]] ** [[phab:project/view/191/|Datasets-Webstatscollector]] * [[phab:project/view/123/|DataTypes]] * [[phab:project/view/122/|DataValues]] ** [[phab:project/view/924/|DataValues-JavaScript]] * [[phab:project/view/5304/|Data³]] * dbbackups ** [[phab:project/view/5291/|dbbackups-dashboard]] * decommission ** [[phab:project/view/3364/|decommission-hardware]] * Dependency ** [[phab:project/view/3502/|Dependency-Tracking]] * [[phab:project/view/349/|Deployments]] * [[phab:project/view/2259/|DeskMessMirrored]] * [[phab:project/view/4281/|Desktop Improvements]] * dev ** [[phab:project/view/4032/|dev-images]] * [[phab:project/view/5853/|DicoAdo.org]] * Diff ** [[phab:project/view/328/|Diff-blog]] * [[phab:project/view/53/|Diffusion]] * [[phab:project/view/4358/|DiscussionTools]] * [[phab:project/view/266/|DismissableSiteNotice]] * [[phab:project/view/154/|DNS]] * Docker ** [[phab:project/view/3094/|Docker-Hub-MediaWiki]] * docker ** [[phab:project/view/3161/|docker-pkg]] * Documentation ** [[phab:project/view/5093/|Documentation-Review-Board]] * [[phab:project/view/1040/|Domains]] * [[phab:project/view/3499/|donate.wikimedia.org]] * [[phab:project/view/4400/|Doxygen]] * draftquality ** [[phab:project/view/2369/|draftquality-modeling]] * drafttopic ** [[phab:project/view/3086/|drafttopic-modeling]] * DSE ** [[phab:project/view/5959/|DSE-Kubernetes-Cluster]] * Dumps ** [[phab:project/view/1519/|Dumps-Generation]] ** [[phab:project/view/1729/|Dumps-Rewrite]] * [[phab:project/view/2260/|Dusk]] * [[phab:project/view/2261/|DuskToDawn]] * DynamicPageList (third ** [[phab:project/view/246/|DynamicPageList (third-party)]] * [[phab:project/view/201/|DynamicPageList (Wikimedia)]] * [[phab:project/view/140/|EasyTimeline]] * Edit ** [[phab:project/view/2040/|Edit-Review-Improvements]] ** [[phab:project/view/2721/|Edit-Review-Improvements-Integrated-Filters]] ** [[phab:project/view/2201/|Edit-Review-Improvements-RC-Page]] ** [[phab:project/view/4796/|Editing-Team-Request]] * editquality ** [[phab:project/view/1673/|editquality-modeling]] * edittypes ** [[phab:project/view/1674/|edittypes-modeling]] * Education ** [[phab:project/view/1052/|Education-Program-Dashboard]] * [[phab:project/view/77/|Elasticsearch]] * Electron ** [[phab:project/view/2162/|Electron-PDFs]] * [[phab:project/view/5184/|envoy]] * Equity ** [[phab:project/view/5828/|Equity-Landscape]] * [[phab:project/view/3068/|Equivset]] * [[phab:project/view/4432/|ERM]] * Europeana ** [[phab:project/view/1580/|Europeana-280]] * [[phab:project/view/3543/|Event Metrics]] * Event ** [[phab:project/view/1474/|Event-Platform]] * [[phab:project/view/789/|EventStreams]] * [[phab:project/view/2783/|Example (skin)]] * [[phab:project/view/3708/|Excimer]] * Expiring ** [[phab:project/view/1995/|Expiring-Watchlist-Items]] * [[phab:project/view/336/|ExtensionDistributor]] * [[phab:project/view/2603/|ExternalArticles]] * [[phab:project/view/3780/|ExternalGuidance]] * [[phab:project/view/3673/|FactGrid]] * [[phab:project/view/810/|FanBoxes]] * [[phab:project/view/2120/|FileAnnotations]] * Fix ** [[phab:project/view/5519/|Fix-Suggester-Bot]] * [[phab:project/view/3570/|fixcopyright.wikimedia.org]] * [[phab:project/view/1496/|FormWizard]] ** [[phab:project/view/3568/|FormWizard-Gadget]] * [[phab:project/view/3501/|foundation.wikimedia.org]] * [[phab:project/view/5489/|Foundational Technology Requests]] * [[phab:project/view/3093/|Fountain]] * FR ** [[phab:project/view/1895/|FR-ActiveMQ]] ** [[phab:project/view/1602/|FR-Adyen]] ** [[phab:project/view/6035/|FR-Alerts]] ** [[phab:project/view/1600/|FR-Amazon]] ** [[phab:project/view/5239/|FR-Australia]] ** [[phab:project/view/4660/|FR-AutoTY-Email]] ** [[phab:project/view/5273/|FR-BigBundle]] ** [[phab:project/view/5754/|FR-Braintree-Integration]] ** [[phab:project/view/5829/|FR-Brazil]] ** [[phab:project/view/5236/|FR-Canada]] * Fr ** [[phab:project/view/3546/|Fr-CentralNotice-Caching]] ** [[phab:project/view/3233/|Fr-CentralNotice-Translation-Bugs]] ** [[phab:project/view/3545/|Fr-CentralNotice-translations]] * FR ** [[phab:project/view/4263/|FR-Civi-Dedupe]] ** [[phab:project/view/4037/|FR-Civi-Planned-Giving]] ** [[phab:project/view/4036/|FR-Civi-Prospect]] * Fr ** [[phab:project/view/2928/|Fr-CiviCRM-dedupe-FY2017/18]] * FR ** [[phab:project/view/5223/|FR-CiviCRM-Searchkit]] * Fr ** [[phab:project/view/4356/|Fr-cross-training]] * FR ** [[phab:project/view/1603/|FR-dlocal]] ** [[phab:project/view/5137/|FR-Docker]] * fr ** [[phab:project/view/4915/|fr-donorservices]] * Fr ** [[phab:project/view/5128/|Fr-drupal-upgrade-2021]] * fr ** [[phab:project/view/5159/|fr-email-preference-center]] * FR ** [[phab:project/view/5274/|FR-EN6C]] * Fr ** [[phab:project/view/4975/|Fr-endowment]] * FR ** [[phab:project/view/4076/|FR-event logging as primary]] ** [[phab:project/view/4075/|FR-event logging in parallel ]] ** [[phab:project/view/3692/|FR-failmail]] ** [[phab:project/view/5770/|FR-form-chooser-refactor]] * Fr ** [[phab:project/view/4264/|Fr-fortnightly]] ** [[phab:project/view/5233/|FR-France]] * FR ** [[phab:project/view/5753/|FR-Gpay-Integration]] ** [[phab:project/view/5229/|FR-India]] ** [[phab:project/view/1604/|FR-Ingenico]] * Fr ** [[phab:project/view/2894/|Fr-Ingenico-integration_2017-18]] * FR ** [[phab:project/view/5234/|FR-Ireland]] ** [[phab:project/view/5232/|FR-Italy]] ** [[phab:project/view/5230/|FR-Japan]] ** [[phab:project/view/5228/|FR-LATAM]] * fr ** [[phab:project/view/5464/|fr-matching-gifts]] * FR ** [[phab:project/view/4769/|FR-MW-Vagrant]] ** [[phab:project/view/5272/|FR-Netherlands]] ** [[phab:project/view/5238/|FR-New-Zealand]] ** [[phab:project/view/1605/|FR-OtherProcessors]] ** [[phab:project/view/5764/|FR-payments-general]] ** [[phab:project/view/1601/|FR-Paypal]] ** [[phab:project/view/1893/|FR-PayPal-ExpressCheckout]] ** [[phab:project/view/1894/|FR-PCI]] * Fr ** [[phab:project/view/4494/|Fr-planning-ahead]] * FR ** [[phab:project/view/1653/|FR-Smashpig]] ** [[phab:project/view/5231/|FR-Sweden]] ** [[phab:project/view/5384/|FR-Target-Smart]] ** [[phab:project/view/3232/|FR-Tech-Analytics]] * fr ** [[phab:project/view/4507/|fr-tech-ops-okr]] * FR ** [[phab:project/view/5235/|FR-UK]] ** [[phab:project/view/5237/|FR-US]] ** [[phab:project/view/1931/|FR-WMF-Audit]] ** [[phab:project/view/1599/|FR-Worldpay]] * [[phab:project/view/59/|freigabe3]] * [[phab:project/view/4744/|Fresh]] * [[phab:project/view/3893/|Fresnel]] * function ** [[phab:project/view/5276/|function-evaluator]] ** [[phab:project/view/5277/|function-orchestrator]] ** [[phab:project/view/5364/|function-schemata]] * fundraising ** [[phab:project/view/1091/|fundraising-tech-ops]] * [[phab:project/view/2262/|Gamepress]] * [[phab:project/view/5999/|Ganeti]] * [[phab:project/view/1391/|GapFinder]] * Gendered ** [[phab:project/view/5066/|Gendered-Categories]] * [[phab:project/view/2912/|Genealogy]] * [[phab:project/view/605/|GeoCrumbs]] * [[phab:project/view/600/|GeoData]] * [[phab:project/view/330/|Gerrit]] * [[phab:project/view/2003/|GerritBot]] * Github ** [[phab:project/view/2762/|Github-notif-bot]] * [[phab:project/view/5793/|Gitiles]] * [[phab:project/view/5057/|GitLab]] * Gitlab ** [[phab:project/view/5984/|Gitlab-Application-Security-Pipeline]] * gitlab ** [[phab:project/view/5484/|gitlab-settings]] * GitLab ** [[phab:project/view/4954/|GitLab-Test]] * GLAM ** [[phab:project/view/2087/|GLAM-Tech]] * [[phab:project/view/2690/|glam2commons]] * [[phab:project/view/315/|GlobalBlocking]] * [[phab:project/view/1949/|GlobalContribs]] * [[phab:project/view/749/|GlobalCssJs]] * [[phab:project/view/1219/|GlobalRename]] * [[phab:project/view/394/|GlobalUsage]] * [[phab:project/view/802/|GlobalUserPage]] * [[phab:project/view/4288/|GLOW]] * [[phab:project/view/2926/|Goatification]] * Google ** [[phab:project/view/4740/|Google-api-proxy]] ** [[phab:project/view/4068/|Google-Drive-to-Commons]] * [[phab:project/view/23/|GoogleLogin]] * [[phab:project/view/3695/|GraphQL]] * [[phab:project/view/943/|GraphViz]] * [[phab:project/view/866/|GreyStuff]] * [[phab:project/view/5663/|Growth community maintenance]] * [[phab:project/view/4094/|Growth Design]] * Growth ** [[phab:project/view/5971/|Growth-Positive-Reinforcement]] ** [[phab:project/view/4738/|Growth-Scaling]] ** [[phab:project/view/4780/|Growth-Structured-Tasks]] ** [[phab:project/view/5314/|Growth-Team-Filtering]] ** [[phab:project/view/4908/|Growth-Team-Leftovers]] * [[phab:project/view/3716/|GrowthExperiments]] ** [[phab:project/view/5475/|GrowthExperiments-CommunityConfiguration]] ** [[phab:project/view/3985/|GrowthExperiments-Help panel]] ** [[phab:project/view/4099/|GrowthExperiments-HelpModule]] ** [[phab:project/view/3986/|GrowthExperiments-Homepage]] ** [[phab:project/view/4100/|GrowthExperiments-HomepageDiscovery]] ** [[phab:project/view/4097/|GrowthExperiments-ImpactModule]] ** [[phab:project/view/5219/|GrowthExperiments-MentorDashboard]] ** [[phab:project/view/4098/|GrowthExperiments-Mentorship]] ** [[phab:project/view/4226/|GrowthExperiments-NewcomerTasks]] ** [[phab:project/view/4095/|GrowthExperiments-StartModule]] * [[phab:project/view/3229/|Hashtags]] * [[phab:project/view/2771/|HasSomeColours]] * [[phab:project/view/3067/|HAWelcome]] * [[phab:project/view/5722/|Header Tabs]] * [[phab:project/view/4373/|homer]] * [[phab:project/view/1822/|Horizon]] * [[phab:project/view/4892/|HtmlFormatter]] * [[phab:project/view/520/|Huggle]] * [[phab:project/view/4967/|Humaniki]] * [[phab:project/view/1746/|HyperSwitch]] * [[phab:project/view/2793/|IA Upload]] * [[phab:project/view/80/|Icinga]] * IDS ** [[phab:project/view/2407/|IDS-extension]] * Image ** [[phab:project/view/5253/|Image-Suggestion-API]] ** [[phab:project/view/5098/|Image-Suggestions]] * [[phab:project/view/243/|ImageMap]] * [[phab:project/view/2461/|ImageRating]] * [[phab:project/view/1650/|ImageTweaks]] * import ** [[phab:project/view/3503/|import-500px]] * [[phab:project/view/1431/|ImportUsers]] * Improving ** [[phab:project/view/1401/|Improving-access]] * Incident ** [[phab:project/view/4038/|Incident-Reporting-System]] * [[phab:project/view/3752/|incubator.wikimedia.org]] * Instrument ** [[phab:project/view/5018/|Instrument-ClientError]] * [[phab:project/view/3156/|InteractionTimeline]] * International ** [[phab:project/view/4045/|International-Developer-Events]] * Internet ** [[phab:project/view/1576/|Internet-Archive]] * [[phab:project/view/2160/|InternetArchiveBot]] * iOS ** [[phab:project/view/1876/|iOS-app-Bugs]] ** [[phab:project/view/1882/|iOS-app-feature-Accessibility]] ** [[phab:project/view/1883/|iOS-app-feature-Analytics]] ** [[phab:project/view/2009/|iOS-app-feature-Database]] ** [[phab:project/view/2232/|iOS-app-feature-Feed]] ** [[phab:project/view/1884/|iOS-app-feature-iPad]] ** [[phab:project/view/1900/|iOS-app-feature-Links]] ** [[phab:project/view/2234/|iOS-app-feature-Login]] ** [[phab:project/view/1924/|iOS-app-feature-Multilingual]] ** [[phab:project/view/1875/|iOS-app-feature-Namespaces]] ** [[phab:project/view/5640/|iOS-app-feature-Navigation]] ** [[phab:project/view/2010/|iOS-app-feature-Notifications]] ** [[phab:project/view/1874/|iOS-app-feature-Offline]] ** [[phab:project/view/1879/|iOS-app-feature-Performance]] ** [[phab:project/view/2008/|iOS-app-feature-Places]] ** [[phab:project/view/1877/|iOS-app-feature-Saved]] ** [[phab:project/view/5714/|iOS-app-feature-Talkpages]] ** [[phab:project/view/1881/|iOS-app-feature-TOC]] ** [[phab:project/view/1878/|iOS-app-feature-TopRead]] ** [[phab:project/view/2233/|iOS-app-feature-Widgets]] * ios ** [[phab:project/view/5726/|ios-app-feature-wikitext-editor]] * iOS ** [[phab:project/view/5830/|iOS-app-next-os-update]] * [[phab:project/view/4923/|IP Info]] * [[phab:project/view/5751/|IP Masking]] * IPA ** [[phab:project/view/5901/|IPA-Audio-Renderer-Wish-2022]] * [[phab:project/view/5805/|IPFS]] * [[phab:project/view/1553/|IPSet]] * [[phab:project/view/4624/|IPUtils]] * [[phab:project/view/3382/|Ipwatcher]] * [[phab:project/view/2122/|IRCecho]] * [[phab:project/view/5357/|ircservserv]] * [[phab:project/view/3981/|ISA]] * [[phab:project/view/5209/|Item Quality Evaluator]] * [[phab:project/view/4932/|Item Quality Scoring Improvement]] * [[phab:project/view/3249/|Jouncebot]] * jQuery ** [[phab:project/view/1119/|jQuery-Client]] * [[phab:project/view/3689/|JSDoc WMF theme]] * [[phab:project/view/1103/|JsonConfig]] * [[phab:project/view/2809/|Junta Directiva]] * KaiOS ** [[phab:project/view/4305/|KaiOS-Wikipedia-app]] * [[phab:project/view/5847/|Kanban]] * [[phab:project/view/2777/|KartoEditor]] * [[phab:project/view/3771/|Keyholder]] * Knowledge ** [[phab:project/view/4384/|Knowledge-Integrity]] * LabsDB ** [[phab:project/view/939/|LabsDB-Auditor]] * Ladies ** [[phab:project/view/2329/|Ladies-That-FOSS-Wikidata]] * Language ** [[phab:project/view/4247/|Language-analytics]] ** [[phab:project/view/5974/|Language-Diversity-Hub]] ** [[phab:project/view/4361/|Language-research]] ** [[phab:project/view/3709/|Language-strategy]] * [[phab:project/view/547/|LastModified]] * LDAP ** [[phab:project/view/1564/|LDAP-Access-Requests]] * [[phab:project/view/4/|Legalpad]] * [[phab:project/view/43/|Librarization]] * Library ** [[phab:project/view/2765/|Library-Card-Platform]] ** [[phab:project/view/3401/|Library-Card-Platform-Discovery]] * [[phab:project/view/2930/|LibUp]] * Lift ** [[phab:project/view/5020/|Lift-Wing]] * [[phab:project/view/3393/|Lingua Libre]] * Linked ** [[phab:project/view/5893/|Linked-Open-Data-Network-Program]] * [[phab:project/view/799/|LinkFilter]] * [[phab:project/view/3916/|Loading Screen]] * local ** [[phab:project/view/3942/|local-charts]] * [[phab:project/view/4000/|LogoFunctions]] * [[phab:project/view/373/|LookupUser]] * [[phab:project/view/5876/|LSC]] * [[phab:project/view/3225/|LuaSandbox]] * [[phab:project/view/4081/|MachineVision]] * [[phab:project/view/983/|Mail]] * Map ** [[phab:project/view/3607/|Map-of-monuments]] * [[phab:project/view/1127/|Maps]] * [[phab:project/view/4011/|Mask]] * [[phab:project/view/4417/|Massmailer]] * [[phab:project/view/717/|MassMessage]] * [[phab:project/view/5541/|masz]] * [[phab:project/view/2422/|Material]] * [[phab:project/view/130/|Math]] ** [[phab:project/view/4847/|Math-Chemistry-Support]] ** [[phab:project/view/4848/|Math-Macro-Proposals]] ** [[phab:project/view/4849/|Math-Non-WMF-Installations]] ** [[phab:project/view/3743/|Mathe für Nicht-Freaks]] * [[phab:project/view/796/|Mathoid]] * [[phab:project/view/737/|MathSearch]] * [[phab:project/view/4056/|Matrix]] * Measuring ** [[phab:project/view/1400/|Measuring-value-added]] * media ** [[phab:project/view/5373/|media-backups]] ** [[phab:project/view/2455/|media-reports-tool]] * [[phab:project/view/5204/|MediaUploader]] * [[phab:project/view/230/|MediaViewer]] * [[phab:project/view/1464/|MediaWiki Language Extension Bundle]] * [[phab:project/view/4835/|MediaWiki Train Development Environment]] * MediaWiki ** [[phab:project/view/200/|MediaWiki-Action-API]] ** [[phab:project/view/1037/|MediaWiki-Authentication-and-authorization]] ** [[phab:project/view/4731/|MediaWiki-Blocks]] ** [[phab:project/view/150/|MediaWiki-Categories]] ** [[phab:project/view/181/|MediaWiki-Change-tagging]] ** [[phab:project/view/1087/|MediaWiki-Codesniffer]] ** [[phab:project/view/3742/|MediaWiki-Comment-store]] ** [[phab:project/view/359/|MediaWiki-Configuration]] ** [[phab:project/view/1687/|MediaWiki-Containers]] ** [[phab:project/view/256/|MediaWiki-ContentHandler]] ** [[phab:project/view/4730/|MediaWiki-Core-Hooks]] ** [[phab:project/view/5723/|MediaWiki-Core-HTTP-Cache]] ** [[phab:project/view/269/|MediaWiki-Core-JobQueue]] ** [[phab:project/view/163/|MediaWiki-Core-Preferences]] ** [[phab:project/view/4586/|MediaWiki-Core-Profiler]] ** [[phab:project/view/3880/|MediaWiki-Core-Revision-backend]] ** [[phab:project/view/4795/|MediaWiki-Core-Skin-Architecture]] ** [[phab:project/view/174/|MediaWiki-Core-Snapshots]] ** [[phab:project/view/313/|MediaWiki-Core-Tests]] ** [[phab:project/view/1694/|MediaWiki-Debian]] ** [[phab:project/view/1129/|MediaWiki-Debug-Logger]] ** [[phab:project/view/234/|MediaWiki-DjVu]] ** [[phab:project/view/4585/|MediaWiki-Docker]] ** [[phab:project/view/132/|MediaWiki-Documentation]] ** [[phab:project/view/216/|MediaWiki-Email]] ** [[phab:project/view/137/|MediaWiki-extension-requests]] ** [[phab:project/view/564/|MediaWiki-extensions-AccessControl]] ** [[phab:project/view/887/|MediaWiki-extensions-AccountInfo]] ** [[phab:project/view/3299/|MediaWiki-extensions-AddPersonalUrls]] ** [[phab:project/view/389/|MediaWiki-extensions-AdminLinks]] ** [[phab:project/view/454/|MediaWiki-extensions-AdvancedMeta]] ** [[phab:project/view/4601/|MediaWiki-extensions-AkismetKlik]] ** [[phab:project/view/3574/|MediaWiki-extensions-Approved-Revs]] ** [[phab:project/view/3565/|MediaWiki-extensions-Arrays]] ** [[phab:project/view/2887/|MediaWiki-extensions-ArticleCreationWorkflow]] ** [[phab:project/view/4489/|MediaWiki-extensions-ArticleToCategory2]] ** [[phab:project/view/2719/|MediaWiki-extensions-Auth_remoteuser]] ** [[phab:project/view/354/|MediaWiki-extensions-AutoCreateCategoryPages]] ** [[phab:project/view/4484/|MediaWiki-extensions-AutoProxyBlock]] ** [[phab:project/view/317/|MediaWiki-extensions-Babel]] ** [[phab:project/view/4594/|MediaWiki-extensions-BibManager]] ** [[phab:project/view/4514/|MediaWiki-extensions-Blackout]] ** [[phab:project/view/3024/|MediaWiki-extensions-BlockAndNuke]] ** [[phab:project/view/806/|MediaWiki-extensions-BounceHandler]] ** [[phab:project/view/760/|MediaWiki-extensions-BreadCrumbs]] ** [[phab:project/view/706/|MediaWiki-extensions-Campaigns]] ** [[phab:project/view/787/|MediaWiki-extensions-Capiunto]] ** [[phab:project/view/1029/|MediaWiki-extensions-Cargo]] ** [[phab:project/view/236/|MediaWiki-extensions-CategoryTree]] ** [[phab:project/view/2832/|MediaWiki-extensions-CategoryWatch]] ** [[phab:project/view/167/|MediaWiki-extensions-CentralAuth]] ** [[phab:project/view/291/|MediaWiki-extensions-CentralNotice]] ** [[phab:project/view/3615/|MediaWiki-extensions-ChangeUserPasswords]] ** [[phab:project/view/5907/|MediaWiki-extensions-CiteDrawer]] ** [[phab:project/view/455/|MediaWiki-extensions-CLDR]] ** [[phab:project/view/586/|MediaWiki-extensions-CleanChanges]] ** [[phab:project/view/4588/|MediaWiki-extensions-CloseWikis]] ** [[phab:project/view/1162/|MediaWiki-extensions-CodeMirror]] ** [[phab:project/view/318/|MediaWiki-extensions-CodeReview]] ** [[phab:project/view/1778/|MediaWiki-extensions-CollaborationKit]] ** [[phab:project/view/5908/|MediaWiki-extensions-CollapsibleSections]] ** [[phab:project/view/889/|MediaWiki-extensions-CollapsibleVector]] ** [[phab:project/view/649/|MediaWiki-extensions-Commentbox]] ** [[phab:project/view/506/|MediaWiki-extensions-Comments]] ** [[phab:project/view/2820/|MediaWiki-extensions-CommentStreams]] ** [[phab:project/view/4642/|MediaWiki-extensions-CommonMessages]] ** [[phab:project/view/288/|MediaWiki-extensions-ConfirmAccount]] ** [[phab:project/view/4590/|MediaWiki-extensions-CongressLookup]] ** [[phab:project/view/405/|MediaWiki-extensions-ContactPage]] ** [[phab:project/view/253/|MediaWiki-extensions-Contributors]] ** [[phab:project/view/2240/|MediaWiki-extensions-CookieWarning]] ** [[phab:project/view/4602/|MediaWiki-extensions-CountDownClock]] ** [[phab:project/view/2827/|MediaWiki-extensions-Create-User-Page]] ** [[phab:project/view/4483/|MediaWiki-extensions-CreateRedirect]] ** [[phab:project/view/598/|MediaWiki-extensions-CreditsSource]] ** [[phab:project/view/477/|MediaWiki-extensions-CSS]] ** [[phab:project/view/2924/|MediaWiki-extensions-Dashiki]] ** [[phab:project/view/791/|MediaWiki-extensions-DataTransfer]] ** [[phab:project/view/4512/|MediaWiki-extensions-DeleteBatch]] ** [[phab:project/view/885/|MediaWiki-extensions-DeleteOwn]] ** [[phab:project/view/1549/|MediaWiki-extensions-DeletePagesForGood]] ** [[phab:project/view/4462/|MediaWiki-extensions-DisableAccount]] ** [[phab:project/view/212/|MediaWiki-extensions-Disambiguator]] ** [[phab:project/view/6041/|MediaWiki-extensions-Discourse]] ** [[phab:project/view/798/|MediaWiki-extensions-DiscussionThreading]] ** [[phab:project/view/2694/|MediaWiki-extensions-DisplayTitle]] ** [[phab:project/view/4227/|MediaWiki-extensions-DocBookExport]] ** [[phab:project/view/409/|MediaWiki-extensions-DonationInterface]] ** [[phab:project/view/395/|MediaWiki-extensions-DoubleWiki]] ** [[phab:project/view/4640/|MediaWiki-extensions-DPLforum]] ** [[phab:project/view/316/|MediaWiki-extensions-Drafts]] ** [[phab:project/view/4999/|MediaWiki-extensions-DrawioEditor]] ** [[phab:project/view/4675/|MediaWiki-extensions-DumpsOnDemand]] ** [[phab:project/view/3955/|MediaWiki-extensions-Duplicator]] ** [[phab:project/view/614/|MediaWiki-extensions-DynamicSidebar]] ** [[phab:project/view/5909/|MediaWiki-extensions-EditAccount]] ** [[phab:project/view/220/|MediaWiki-extensions-Editcount]] ** [[phab:project/view/2007/|MediaWiki-extensions-EditNotify]] ** [[phab:project/view/560/|MediaWiki-extensions-EditUser]] ** [[phab:project/view/2826/|MediaWiki-extensions-Email_Authorization]] ** [[phab:project/view/2358/|MediaWiki-extensions-EmailAuth]] ** [[phab:project/view/5910/|MediaWiki-extensions-EncryptedUploads]] ** [[phab:project/view/534/|MediaWiki-extensions-EtherpadLite]] ** [[phab:project/view/589/|MediaWiki-extensions-EventLogging]] ** [[phab:project/view/1405/|MediaWiki-extensions-Examples]] ** [[phab:project/view/494/|MediaWiki-extensions-ExternalData]] ** [[phab:project/view/5911/|MediaWiki-extensions-ExternalLinkConfirm]] ** [[phab:project/view/792/|MediaWiki-extensions-ExtraLanguageLink]] ** [[phab:project/view/4637/|MediaWiki-extensions-Farmer]] ** [[phab:project/view/514/|MediaWiki-extensions-FeaturedFeeds]] ** [[phab:project/view/296/|MediaWiki-extensions-FlaggedRevs]] ** [[phab:project/view/5912/|MediaWiki-extensions-FlickrAPI]] ** [[phab:project/view/3117/|MediaWiki-extensions-Form]] ** [[phab:project/view/622/|MediaWiki-extensions-FundraiserLandingPage]] ** [[phab:project/view/285/|MediaWiki-extensions-Gadgets]] ** [[phab:project/view/176/|MediaWiki-extensions-General]] ** [[phab:project/view/590/|MediaWiki-extensions-GettingStarted]] ** [[phab:project/view/884/|MediaWiki-extensions-Git2Pages]] ** [[phab:project/view/763/|MediaWiki-extensions-GlobalPreferences]] ** [[phab:project/view/4828/|MediaWiki-extensions-GlobalWatchlist]] ** [[phab:project/view/4228/|MediaWiki-extensions-GoogleAdSense]] ** [[phab:project/view/5913/|MediaWiki-extensions-GoogleAnalyticsMetrics]] ** [[phab:project/view/5914/|MediaWiki-extensions-GoogleCustomWikiSearch]] ** [[phab:project/view/509/|MediaWiki-extensions-GoogleNewsSitemap]] ** [[phab:project/view/1548/|MediaWiki-extensions-GPGMail]] ** [[phab:project/view/816/|MediaWiki-extensions-Graph]] ** [[phab:project/view/3902/|MediaWiki-extensions-GraphQL]] ** [[phab:project/view/5294/|MediaWiki-extensions-Gravatar]] ** [[phab:project/view/5915/|MediaWiki-extensions-GroupWhitelist]] ** [[phab:project/view/582/|MediaWiki-extensions-GuidedTour]] ** [[phab:project/view/744/|MediaWiki-extensions-GWToolset]] ** [[phab:project/view/853/|MediaWiki-extensions-Hierarchy-Builder]] ** [[phab:project/view/1320/|MediaWiki-extensions-HitCounters]] ** [[phab:project/view/2350/|MediaWiki-extensions-HostStats]] ** [[phab:project/view/1094/|MediaWiki-extensions-Html2Wiki]] ** [[phab:project/view/3763/|MediaWiki-extensions-ImageCompare]] ** [[phab:project/view/1512/|MediaWiki-extensions-ImportArticles]] ** [[phab:project/view/290/|MediaWiki-extensions-ImportFreeImages]] ** [[phab:project/view/374/|MediaWiki-extensions-IndexFunction]] ** [[phab:project/view/180/|MediaWiki-extensions-InputBox]] ** [[phab:project/view/690/|MediaWiki-extensions-Insider]] ** [[phab:project/view/443/|MediaWiki-extensions-Interlanguage]] ** [[phab:project/view/333/|MediaWiki-extensions-Interwiki]] ** [[phab:project/view/4366/|MediaWiki-extensions-InterwikiExtracts]] ** [[phab:project/view/2374/|MediaWiki-extensions-InterwikiSorting]] ** [[phab:project/view/4600/|MediaWiki-extensions-InviteSignup]] ** [[phab:project/view/1032/|MediaWiki-extensions-Josa]] ** [[phab:project/view/3242/|MediaWiki-extensions-JSBreadCrumbs]] ** [[phab:project/view/4501/|MediaWiki-extensions-JsonData]] ** [[phab:project/view/302/|MediaWiki-extensions-LabeledSectionTransclusion]] ** [[phab:project/view/371/|MediaWiki-extensions-LanguageSelector]] ** [[phab:project/view/5202/|MediaWiki-extensions-LastUserLogin]] ** [[phab:project/view/414/|MediaWiki-extensions-LdapAuthentication]] ** [[phab:project/view/4169/|MediaWiki-extensions-LDAPAuthentication2]] ** [[phab:project/view/863/|MediaWiki-extensions-LDAPAuthorization]] ** [[phab:project/view/3070/|MediaWiki-extensions-LDAPGroups]] ** [[phab:project/view/3952/|MediaWiki-extensions-LDAPProvider]] ** [[phab:project/view/3953/|MediaWiki-extensions-LDAPUserInfo]] ** [[phab:project/view/5916/|MediaWiki-extensions-LegalLogin]] ** [[phab:project/view/723/|MediaWiki-extensions-Lingo]] ** [[phab:project/view/2164/|MediaWiki-extensions-LinkedWiki]] ** [[phab:project/view/4499/|MediaWiki-extensions-LinkSuggest]] ** [[phab:project/view/5917/|MediaWiki-extensions-LinkTarget]] ** [[phab:project/view/2318/|MediaWiki-extensions-Linter]] ** [[phab:project/view/303/|MediaWiki-extensions-LiquidThreads]] ** [[phab:project/view/597/|MediaWiki-extensions-Listings]] ** [[phab:project/view/376/|MediaWiki-extensions-LocalisationUpdate]] ** [[phab:project/view/5207/|MediaWiki-extensions-LockAuthor]] ** [[phab:project/view/416/|MediaWiki-extensions-Lockdown]] ** [[phab:project/view/321/|MediaWiki-extensions-LogEntry]] ** [[phab:project/view/2419/|MediaWiki-extensions-LoginNotify]] ** [[phab:project/view/3567/|MediaWiki-extensions-Loops]] ** [[phab:project/view/4596/|MediaWiki-extensions-MagicNoCache]] ** [[phab:project/view/1424/|MediaWiki-extensions-Mailgun]] ** [[phab:project/view/451/|MediaWiki-extensions-Maintenance (by Skizzerz)]] ** [[phab:project/view/643/|MediaWiki-extensions-MaintenanceShell]] ** [[phab:project/view/640/|MediaWiki-extensions-MapSources]] ** [[phab:project/view/769/|MediaWiki-extensions-MarkAsHelpful]] ** [[phab:project/view/4486/|MediaWiki-extensions-MassEditRegex]] ** [[phab:project/view/5918/|MediaWiki-extensions-MassMessageEmail]] ** [[phab:project/view/286/|MediaWiki-extensions-MediaFunctions]] ** [[phab:project/view/4608/|MediaWiki-extensions-MediaModeration]] ** [[phab:project/view/2687/|MediaWiki-extensions-MediaWikiFarm]] ** [[phab:project/view/5919/|MediaWiki-extensions-MetaMaster]] ** [[phab:project/view/3577/|MediaWiki-extensions-MintyDocs]] ** [[phab:project/view/793/|MediaWiki-extensions-MobileApp]] ** [[phab:project/view/5145/|MediaWiki-extensions-MobileDetect]] ** [[phab:project/view/804/|MediaWiki-extensions-MolHandler]] ** [[phab:project/view/2421/|MediaWiki-extensions-MsCalendar]] ** [[phab:project/view/926/|MediaWiki-extensions-MsCatSelect]] ** [[phab:project/view/883/|MediaWiki-extensions-MsUpload]] ** [[phab:project/view/295/|MediaWiki-extensions-MultiBoilerplate]] ** [[phab:project/view/6007/|MediaWiki-extensions-MultiMail]] ** [[phab:project/view/4490/|MediaWiki-extensions-MultiMaps]] ** [[phab:project/view/5920/|MediaWiki-extensions-MyVariables]] ** [[phab:project/view/5921/|MediaWiki-extensions-NamespaceHTML]] ** [[phab:project/view/4515/|MediaWiki-extensions-NetworkAuth]] ** [[phab:project/view/319/|MediaWiki-extensions-NewestPages]] ** [[phab:project/view/4589/|MediaWiki-extensions-News]] ** [[phab:project/view/888/|MediaWiki-extensions-Newsletter]] ** [[phab:project/view/1863/|MediaWiki-extensions-NewUserActions]] ** [[phab:project/view/305/|MediaWiki-extensions-NewUserMessage]] ** [[phab:project/view/450/|MediaWiki-extensions-NewUserNotif]] ** [[phab:project/view/563/|MediaWiki-extensions-NSFileRepo]] ** [[phab:project/view/231/|MediaWiki-extensions-Nuke]] ** [[phab:project/view/554/|MediaWiki-extensions-OATHAuth]] ** [[phab:project/view/682/|MediaWiki-extensions-OAuth]] ** [[phab:project/view/1263/|MediaWiki-extensions-OAuthAuthentication]] ** [[phab:project/view/4904/|MediaWiki-extensions-OAuthRateLimiter]] ** [[phab:project/view/343/|MediaWiki-extensions-OnlineStatus]] ** [[phab:project/view/553/|MediaWiki-extensions-OnlineStatusBar]] ** [[phab:project/view/882/|MediaWiki-extensions-OnlyRecentRecentChanges]] ** [[phab:project/view/4498/|MediaWiki-extensions-OpenGraphMeta]] ** [[phab:project/view/244/|MediaWiki-extensions-OpenID]] ** [[phab:project/view/862/|MediaWiki-extensions-OpenID-Connect]] ** [[phab:project/view/4530/|MediaWiki-extensions-OpenJsCad]] ** [[phab:project/view/420/|MediaWiki-extensions-OpenStackManager]] ** [[phab:project/view/1662/|MediaWiki-extensions-ORES]] ** [[phab:project/view/2861/|MediaWiki-extensions-OrphanedTalkPages]] ** [[phab:project/view/308/|MediaWiki-extensions-Other]] ** [[phab:project/view/272/|MediaWiki-extensions-Page_Forms]] ** [[phab:project/view/1936/|MediaWiki-extensions-PageAssessments]] ** [[phab:project/view/403/|MediaWiki-extensions-PagedTiffHandler]] ** [[phab:project/view/5922/|MediaWiki-extensions-PageMagic]] ** [[phab:project/view/392/|MediaWiki-extensions-PageNotice]] ** [[phab:project/view/652/|MediaWiki-extensions-PageSchemas]] ** [[phab:project/view/4487/|MediaWiki-extensions-ParserMigration]] ** [[phab:project/view/261/|MediaWiki-extensions-Patroller]] ** [[phab:project/view/393/|MediaWiki-extensions-PdfHandler]] ** [[phab:project/view/1851/|MediaWiki-extensions-PerformanceInspector]] ** [[phab:project/view/5923/|MediaWiki-extensions-PerPageLanguage]] ** [[phab:project/view/786/|MediaWiki-extensions-Petition]] ** [[phab:project/view/4513/|MediaWiki-extensions-PGFTikZ]] ** [[phab:project/view/1159/|MediaWiki-extensions-PhpTags]] ** [[phab:project/view/861/|MediaWiki-extensions-Pluggable-Auth]] ** [[phab:project/view/232/|MediaWiki-extensions-Poem]] ** [[phab:project/view/415/|MediaWiki-extensions-Poll]] ** [[phab:project/view/5924/|MediaWiki-extensions-PopupAlerts]] ** [[phab:project/view/2796/|MediaWiki-extensions-PropertySuggester]] ** [[phab:project/view/4395/|MediaWiki-extensions-ProtectionIndicator]] ** [[phab:project/view/4643/|MediaWiki-extensions-Push]] ** [[phab:project/view/4500/|MediaWiki-extensions-PushToWatch]] ** [[phab:project/view/1984/|MediaWiki-extensions-QuickGV]] ** [[phab:project/view/5881/|MediaWiki-extensions-QuickInstantCommons]] ** [[phab:project/view/289/|MediaWiki-extensions-Quiz]] ** [[phab:project/view/248/|MediaWiki-extensions-RandomImage]] ** [[phab:project/view/4639/|MediaWiki-extensions-RandomInCategory]] ** [[phab:project/view/6042/|MediaWiki-extensions-Realnames]] ** [[phab:project/view/5782/|MediaWiki-extensions-RedirectManager]] ** [[phab:project/view/780/|MediaWiki-extensions-RefreshSpecial]] ** [[phab:project/view/595/|MediaWiki-extensions-RelatedSites]] ** [[phab:project/view/204/|MediaWiki-extensions-Renameuser]] ** [[phab:project/view/344/|MediaWiki-extensions-ReplaceText]] ** [[phab:project/view/4625/|MediaWiki-extensions-RevisionCommentSupplement]] ** [[phab:project/view/4615/|MediaWiki-extensions-RightFunctions]] ** [[phab:project/view/430/|MediaWiki-extensions-RSS]] ** [[phab:project/view/822/|MediaWiki-extensions-SandboxLink]] ** [[phab:project/view/5925/|MediaWiki-extensions-SaveSpinner]] ** [[phab:project/view/613/|MediaWiki-extensions-Score]] ** [[phab:project/view/1550/|MediaWiki-extensions-Screenplay]] ** [[phab:project/view/558/|MediaWiki-extensions-Scribunto]] ** [[phab:project/view/876/|MediaWiki-extensions-SearchExtraNS]] ** [[phab:project/view/4674/|MediaWiki-extensions-SearchStats]] ** [[phab:project/view/3366/|MediaWiki-extensions-SecureAuth]] ** [[phab:project/view/3495/|MediaWiki-extensions-SecureLinkFixer]] ** [[phab:project/view/238/|MediaWiki-extensions-SecurePoll]] ** [[phab:project/view/704/|MediaWiki-extensions-SecureSessions]] ** [[phab:project/view/260/|MediaWiki-extensions-SelectCategory]] ** [[phab:project/view/860/|MediaWiki-extensions-Semantic-Dependency]] ** [[phab:project/view/855/|MediaWiki-extensions-Semantic-Rating]] ** [[phab:project/view/4497/|MediaWiki-extensions-SemanticACL]] ** [[phab:project/view/293/|MediaWiki-extensions-SemanticDrilldown]] ** [[phab:project/view/2051/|MediaWiki-extensions-SemanticQueryInterface]] ** [[phab:project/view/2954/|MediaWiki-extensions-SendGrid]] ** [[phab:project/view/491/|MediaWiki-extensions-ShortUrl]] ** [[phab:project/view/5926/|MediaWiki-extensions-ShowMe]] ** [[phab:project/view/859/|MediaWiki-extensions-SimpleSAMLphp]] ** [[phab:project/view/4502/|MediaWiki-extensions-Site_Settings]] ** [[phab:project/view/1406/|MediaWiki-extensions-SkinPerNamespace]] ** [[phab:project/view/4616/|MediaWiki-extensions-SkinPerPage]] ** [[phab:project/view/625/|MediaWiki-extensions-SlimboxThumbs]] ** [[phab:project/view/1252/|MediaWiki-extensions-SmiteSpam]] ** [[phab:project/view/5931/|MediaWiki-extensions-SpamDiffTool]] ** [[phab:project/view/3794/|MediaWiki-extensions-SparkPost]] ** [[phab:project/view/467/|MediaWiki-extensions-SphinxSearch]] ** [[phab:project/view/4641/|MediaWiki-extensions-StalkerLog]] ** [[phab:project/view/2324/|MediaWiki-extensions-StlHandler]] ** [[phab:project/view/781/|MediaWiki-extensions-StopForumSpam]] ** [[phab:project/view/411/|MediaWiki-extensions-StringFunctionsEscaped]] ** [[phab:project/view/4587/|MediaWiki-extensions-SubPageList3]] ** [[phab:project/view/874/|MediaWiki-extensions-SubpageSortkey]] ** [[phab:project/view/4638/|MediaWiki-extensions-Sudo]] ** [[phab:project/view/660/|MediaWiki-extensions-Survey]] ** [[phab:project/view/872/|MediaWiki-extensions-SwiftMailer]] ** [[phab:project/view/4016/|MediaWiki-extensions-TEI]] ** [[phab:project/view/604/|MediaWiki-extensions-TemplateSandbox]] ** [[phab:project/view/3284/|MediaWiki-extensions-TemplateWizard]] ** [[phab:project/view/1363/|MediaWiki-extensions-TestLanguageNameGrammar]] ** [[phab:project/view/671/|MediaWiki-extensions-ThrottleOverride]] ** [[phab:project/view/3575/|MediaWiki-extensions-TinyMCE]] ** [[phab:project/view/854/|MediaWiki-extensions-Title-Icon]] ** [[phab:project/view/397/|MediaWiki-extensions-TitleKey]] ** [[phab:project/view/666/|MediaWiki-extensions-TocTree]] ** [[phab:project/view/6037/|MediaWiki-extensions-Toolhub]] ** [[phab:project/view/444/|MediaWiki-extensions-TorBlock]] ** [[phab:project/view/271/|MediaWiki-extensions-Translate]] ** [[phab:project/view/1272/|MediaWiki-extensions-TranslateSvg]] ** [[phab:project/view/551/|MediaWiki-extensions-TranslationNotifications]] ** [[phab:project/view/2138/|MediaWiki-extensions-TrustedXFF]] ** [[phab:project/view/764/|MediaWiki-extensions-TweetANew]] ** [[phab:project/view/619/|MediaWiki-extensions-TwitterCards]] ** [[phab:project/view/4598/|MediaWiki-extensions-TwitterLogin]] ** [[phab:project/view/650/|MediaWiki-extensions-TwnMainPage]] ** [[phab:project/view/4509/|MediaWiki-extensions-UIFeedback]] ** [[phab:project/view/4599/|MediaWiki-extensions-UnicodeConverter]] ** [[phab:project/view/4593/|MediaWiki-extensions-UploadBlacklist]] ** [[phab:project/view/1846/|MediaWiki-extensions-UploadsLink]] ** [[phab:project/view/809/|MediaWiki-extensions-UrlShortener]] ** [[phab:project/view/3531/|MediaWiki-extensions-UserAgreement]] ** [[phab:project/view/5208/|MediaWiki-extensions-UseResource]] ** [[phab:project/view/453/|MediaWiki-extensions-UserMerge]] ** [[phab:project/view/5927/|MediaWiki-extensions-UserProtect]] ** [[phab:project/view/3326/|MediaWiki-extensions-Variables]] ** [[phab:project/view/3576/|MediaWiki-extensions-VEForAll]] ** [[phab:project/view/3213/|MediaWiki-extensions-VersionCompare]] ** [[phab:project/view/858/|MediaWiki-extensions-VIKI]] ** [[phab:project/view/857/|MediaWiki-extensions-VikiSemanticTitle]] ** [[phab:project/view/505/|MediaWiki-extensions-VipsScaler]] ** [[phab:project/view/4488/|MediaWiki-extensions-WatchSubpages]] ** [[phab:project/view/3888/|MediaWiki-extensions-WebDAV]] ** [[phab:project/view/4266/|MediaWiki-extensions-WebToolsManager]] ** [[phab:project/view/4491/|MediaWiki-extensions-WhoIsWatching]] ** [[phab:project/view/358/|MediaWiki-extensions-Widgets]] ** [[phab:project/view/4747/|MediaWiki-extensions-WikEdDiff]] ** [[phab:project/view/114/|MediaWiki-extensions-WikibaseClient]] ** [[phab:project/view/5043/|MediaWiki-extensions-WikibaseManifest]] ** [[phab:project/view/113/|MediaWiki-extensions-WikibaseRepository]] ** [[phab:project/view/1176/|MediaWiki-extensions-WikibaseView]] ** [[phab:project/view/242/|MediaWiki-extensions-WikiLexicalData-or-OmegaWiki]] ** [[phab:project/view/4823/|MediaWiki-extensions-WikimediaApiPortalOAuth]] ** [[phab:project/view/3286/|MediaWiki-extensions-WikimediaBadges]] ** [[phab:project/view/707/|MediaWiki-extensions-WikimediaEvents]] ** [[phab:project/view/471/|MediaWiki-extensions-WikimediaIncubator]] ** [[phab:project/view/492/|MediaWiki-extensions-WikimediaMaintenance]] ** [[phab:project/view/1309/|MediaWiki-extensions-WikiShare]] ** [[phab:project/view/5370/|MediaWiki-extensions-WSOAuth]] ** [[phab:project/view/131/|MediaWiki-File-management]] ** [[phab:project/view/1498/|MediaWiki-Gallery]] ** [[phab:project/view/135/|MediaWiki-General]] ** [[phab:project/view/1525/|MediaWiki-HTML-Templating]] ** [[phab:project/view/540/|MediaWiki-HTMLForm]] ** [[phab:project/view/147/|MediaWiki-Installer]] ** [[phab:project/view/155/|MediaWiki-Interface]] ** [[phab:project/view/144/|MediaWiki-Internationalization]] ** [[phab:project/view/1685/|MediaWiki-Interwiki]] ** [[phab:project/view/223/|MediaWiki-Language-converter]] ** [[phab:project/view/5082/|MediaWiki-libs-Assert]] ** [[phab:project/view/3777/|MediaWiki-libs-HTTP]] ** [[phab:project/view/5583/|MediaWiki-libs-Metrics]] ** [[phab:project/view/4783/|MediaWiki-libs-Mime]] ** [[phab:project/view/1329/|MediaWiki-libs-ObjectCache]] * mediawiki ** [[phab:project/view/5496/|mediawiki-libs-RequestTimeout]] * MediaWiki ** [[phab:project/view/3390/|MediaWiki-libs-Services]] ** [[phab:project/view/356/|MediaWiki-Logevents]] ** [[phab:project/view/268/|MediaWiki-Maintenance-system]] ** [[phab:project/view/4728/|MediaWiki-MergeHistory]] ** [[phab:project/view/213/|MediaWiki-Page-deletion]] ** [[phab:project/view/3881/|MediaWiki-Page-derived-data]] ** [[phab:project/view/149/|MediaWiki-Page-diffs]] ** [[phab:project/view/139/|MediaWiki-Page-editing]] ** [[phab:project/view/4287/|MediaWiki-Page-history]] ** [[phab:project/view/278/|MediaWiki-Page-protection]] ** [[phab:project/view/4727/|MediaWiki-Page-rename]] ** [[phab:project/view/136/|MediaWiki-Parser]] ** [[phab:project/view/195/|MediaWiki-Patrolling]] ** [[phab:project/view/194/|MediaWiki-Recent-changes]] ** [[phab:project/view/160/|MediaWiki-Redirects]] ** [[phab:project/view/3044/|MediaWiki-Release-Tools]] ** [[phab:project/view/274/|MediaWiki-ResourceLoader]] ** [[phab:project/view/4020/|MediaWiki-REST-API]] ** [[phab:project/view/337/|MediaWiki-Revision-deletion]] ** [[phab:project/view/146/|MediaWiki-Search]] ** [[phab:project/view/3150/|MediaWiki-Shell]] ** [[phab:project/view/656/|MediaWiki-Site-system]] ** [[phab:project/view/5070/|MediaWiki-skins-Amethyst]] ** [[phab:project/view/5703/|MediaWiki-skins-Cavendish]] ** [[phab:project/view/5077/|MediaWiki-skins-Erudite]] ** [[phab:project/view/5131/|MediaWiki-skins-GuMaxDD]] ** [[phab:project/view/5134/|MediaWiki-skins-Mirage]] ** [[phab:project/view/5073/|MediaWiki-skins-p2wiki]] ** [[phab:project/view/5130/|MediaWiki-skins-Schulenburg]] ** [[phab:project/view/5072/|MediaWiki-skins-Strapping]] ** [[phab:project/view/5074/|MediaWiki-skins-Tempo]] ** [[phab:project/view/5075/|MediaWiki-skins-WebPlatform]] ** [[phab:project/view/133/|MediaWiki-Special-pages]] ** [[phab:project/view/142/|MediaWiki-Templates]] ** [[phab:project/view/4634/|MediaWiki-TrackingCategories]] ** [[phab:project/view/158/|MediaWiki-Uploading]] ** [[phab:project/view/148/|MediaWiki-User-login-and-signup]] ** [[phab:project/view/198/|MediaWiki-User-management]] ** [[phab:project/view/627/|MediaWiki-Vagrant]] ** [[phab:project/view/818/|MediaWiki-Vendor]] ** [[phab:project/view/173/|MediaWiki-Watchlist]] * [[phab:project/view/1950/|MediaWikiChat]] * Mention ** [[phab:project/view/2101/|Mention-Notification]] * Metrics ** [[phab:project/view/5324/|Metrics-Platform]] * [[phab:project/view/1023/|Metrolook]] * [[phab:project/view/2799/|MinervaNeue]] * [[phab:project/view/2390/|MiniInvite]] * [[phab:project/view/2998/|MinusX]] * [[phab:project/view/5385/|Mismatch Finder]] * [[phab:project/view/3458/|Mitmachen]] * ML ** [[phab:project/view/5244/|ML-Governance]] * Mobile ** [[phab:project/view/1323/|Mobile-Content-Service]] * [[phab:project/view/1157/|MobileFrontend]] * [[phab:project/view/5482/|MobileFrontend Content Provider]] * [[phab:project/view/396/|Modern]] * [[phab:project/view/355/|MonoBook]] * [[phab:project/view/2287/|Montage]] * [[phab:project/view/3379/|MontserratFont]] * [[phab:project/view/2696/|Monumental]] * Move ** [[phab:project/view/2671/|Move-Files-To-Commons]] * Multi ** [[phab:project/view/3112/|Multi-Content-Revisions]] * MW ** [[phab:project/view/4946/|MW-on-K8s]] * [[phab:project/view/5331/|mwcli]] * [[phab:project/view/4910/|Nagf]] * Navigation ** [[phab:project/view/2055/|Navigation-Popups-Gadget]] * [[phab:project/view/642/|NavigationTiming]] * [[phab:project/view/4609/|NearbyPages]] * [[phab:project/view/4031/|netbox]] * [[phab:project/view/950/|netops]] * [[phab:project/view/4282/|NewcomerTasks 1.0 ]] * [[phab:project/view/4283/|NewcomerTasks 1.1]] * [[phab:project/view/4284/|NewcomerTasks 1.2]] * [[phab:project/view/4285/|NewcomerTasks Future Release ]] * [[phab:project/view/2265/|NewSignupPage]] * [[phab:project/view/807/|Nimbus]] * [[phab:project/view/5986/|noc.wikimedia.org]] * Nonpublic ** [[phab:project/view/1485/|Nonpublic-Information-Access-Policy]] * [[phab:project/view/5414/|NormalizedException]] * [[phab:project/view/865/|Nostalgia]] * [[phab:project/view/182/|Notifications]] * [[phab:project/view/2734/|OABot]] * [[phab:project/view/3244/|ObjectFactory]] * [[phab:project/view/84/|observability]] * Observability ** [[phab:project/view/5394/|Observability-Alerting]] ** [[phab:project/view/5393/|Observability-Logging]] ** [[phab:project/view/5392/|Observability-Metrics]] ** [[phab:project/view/5395/|Observability-Tracing]] * [[phab:project/view/5710/|ogv.js]] * [[phab:project/view/748/|OOjs core]] * OOjs ** [[phab:project/view/2119/|OOjs-Router]] * [[phab:project/view/697/|OOUI]] * [[phab:project/view/916/|OpenBadges]] * ops ** [[phab:project/view/955/|ops-codfw]] ** [[phab:project/view/5329/|ops-drmrs]] ** [[phab:project/view/1635/|ops-eqdfw]] ** [[phab:project/view/952/|ops-eqiad]] ** [[phab:project/view/1636/|ops-eqord]] ** [[phab:project/view/3127/|ops-eqsin]] ** [[phab:project/view/951/|ops-esams]] ** [[phab:project/view/954/|ops-ulsfo]] * [[phab:project/view/5061/|Orchestrator]] * [[phab:project/view/1467/|ORES]] ** [[phab:project/view/3327/|ORES-Support-Checklist]] * Other ** [[phab:project/view/824/|Other-skins]] * Outreach ** [[phab:project/view/2537/|Outreach-Programs-Projects]] * [[phab:project/view/4178/|OWC2020]] * [[phab:project/view/1782/|Packaging]] * [[phab:project/view/2885/|Page Content Service]] * Page ** [[phab:project/view/765/|Page-Previews]] * [[phab:project/view/731/|PageImages]] * [[phab:project/view/541/|PageTriage]] * [[phab:project/view/1753/|PageViewInfo]] * Pageviews ** [[phab:project/view/1772/|Pageviews-API]] * [[phab:project/view/237/|ParserFunctions]] * [[phab:project/view/487/|Parsoid]] ** [[phab:project/view/1046/|Parsoid-Nowiki]] ** [[phab:project/view/5532/|Parsoid-Read-Views]] ** [[phab:project/view/1286/|Parsoid-Rendering]] ** [[phab:project/view/1045/|Parsoid-Robustness]] ** [[phab:project/view/488/|Parsoid-Serializer]] ** [[phab:project/view/610/|Parsoid-Tests]] ** [[phab:project/view/581/|Parsoid-Tokenizer]] * Password ** [[phab:project/view/4275/|Password-Reset-Update]] * [[phab:project/view/4058/|PasswordlessLogin]] * [[phab:project/view/1648/|PAWS]] * [[phab:project/view/4800/|Peek]] * Performance ** [[phab:project/view/4983/|Performance-Device-Lab]] * [[phab:project/view/5/|Phabricator]] * [[phab:project/view/4460/|Phabricator Antivandalism Extension]] * [[phab:project/view/5254/|phabricator maintenance bot]] * Phabricator ** [[phab:project/view/981/|Phabricator-Bot-Requests]] * [[phab:project/view/3065/|PhabTaskGraph]] * [[phab:project/view/3906/|phan]] ** [[phab:project/view/3149/|phan-taint-check-plugin]] * [[phab:project/view/4578/|Phatality]] * [[phab:project/view/5900/|PhotoSwipe]] * PHP ** [[phab:project/view/2349/|PHP-API-for-Wikisource]] * php ** [[phab:project/view/1581/|php-session-serializer]] ** [[phab:project/view/4060/|php-wmerrors]] ** [[phab:project/view/3222/|phpunit-patch-coverage]] * [[phab:project/view/880/|PictureGame]] * Pilot ** [[phab:project/view/5021/|Pilot-Flag]] * [[phab:project/view/510/|PollNY]] * [[phab:project/view/4144/|Poncho]] * [[phab:project/view/437/|PoolCounter]] * preview ** [[phab:project/view/5365/|preview-environment]] * [[phab:project/view/2830/|PrivateDomains]] * [[phab:project/view/1155/|procurement]] * Prod ** [[phab:project/view/2290/|Prod-Kubernetes]] * [[phab:project/view/5040/|Product Infrastructure Roadmap]] * [[phab:project/view/5582/|Product Roadmap]] * Product ** [[phab:project/view/3348/|Product-Design-Strategy]] ** [[phab:project/view/4982/|Product-Platform Operations]] * [[phab:project/view/645/|PronunciationRecording]] * [[phab:project/view/276/|ProofreadPage]] * [[phab:project/view/2960/|Proton]] * ProveIt ** [[phab:project/view/2317/|ProveIt-Gadget]] * puppet ** [[phab:project/view/1807/|puppet-compiler]] * [[phab:project/view/5750/|Purtle]] * Push ** [[phab:project/view/2699/|Push-Notification-Service]] * [[phab:project/view/984/|PyBal]] * [[phab:project/view/87/|Pywikibot]] ** [[phab:project/view/92/|Pywikibot-archivebot.py]] * pywikibot ** [[phab:project/view/2250/|pywikibot-bots-FLOSSbot]] * Pywikibot ** [[phab:project/view/93/|Pywikibot-category.py]] ** [[phab:project/view/755/|Pywikibot-catfiles]] ** [[phab:project/view/1484/|Pywikibot-Commons]] ** [[phab:project/view/95/|Pywikibot-cosmetic-changes.py]] ** [[phab:project/view/1247/|Pywikibot-Flow]] ** [[phab:project/view/99/|Pywikibot-i18n]] ** [[phab:project/view/100/|Pywikibot-interwiki.py]] ** [[phab:project/view/101/|Pywikibot-login.py]] ** [[phab:project/view/1246/|Pywikibot-OAuth]] ** [[phab:project/view/104/|Pywikibot-pagegenerators.py]] ** [[phab:project/view/105/|Pywikibot-redirect.py]] ** [[phab:project/view/1293/|Pywikibot-replace.py]] ** [[phab:project/view/103/|Pywikibot-Scripts]] ** [[phab:project/view/106/|Pywikibot-solve-disambiguation.py]] ** [[phab:project/view/108/|Pywikibot-textlib.py]] ** [[phab:project/view/109/|Pywikibot-weblinkchecker.py]] * QRpedia ** [[phab:project/view/728/|QRpedia-General]] * Quality ** [[phab:project/view/4725/|Quality-and-Test-Engineering-Retrospectives]] * [[phab:project/view/800/|Quarry]] ** [[phab:project/view/2572/|QuarryBot-enwiki]] * [[phab:project/view/2772/|Quibble]] * [[phab:project/view/1429/|QuickSurveys]] * [[phab:project/view/879/|QuizGame]] * [[phab:project/view/877/|RandomGameUnit]] * React ** [[phab:project/view/5048/|React-i18n]] * Reader ** [[phab:project/view/1787/|Reader-research]] ** [[phab:project/view/1538/|Readers-Community-Engagement]] * [[phab:project/view/3910/|Reading Depth]] * [[phab:project/view/2740/|Reading List Service]] * Reading ** [[phab:project/view/1682/|Reading-Web-Local-Wiki-Issues]] * Recommendation ** [[phab:project/view/2128/|Recommendation-API]] * [[phab:project/view/5458/|Reconciliation]] * [[phab:project/view/3840/|Reference Previews]] * [[phab:project/view/1956/|Refreshed]] * [[phab:project/view/345/|RegexBlock]] * [[phab:project/view/688/|RelatedArticles]] * [[phab:project/view/1276/|ReleaseTaggerBot]] * [[phab:project/view/2978/|RemexHtml]] * Reports ** [[phab:project/view/1940/|Reports-bot]] * [[phab:project/view/1292/|Research ideas]] * Research ** [[phab:project/view/1396/|Research-and-Data-VisualEditor ]] ** [[phab:project/view/2113/|Research-collaborations]] ** [[phab:project/view/1402/|Research-consulting]] ** [[phab:project/view/4383/|Research-foundational]] ** [[phab:project/view/3243/|Research-landing-page]] ** [[phab:project/view/1395/|Research-management]] ** [[phab:project/view/1394/|Research-outreach]] * [[phab:project/view/833/|RESTBase]] ** [[phab:project/view/851/|RESTBase-API]] ** [[phab:project/view/834/|RESTBase-Cassandra]] * restbase ** [[phab:project/view/4389/|restbase-mysql]] * Retro ** [[phab:project/view/4788/|Retro-Actions]] * Revision ** [[phab:project/view/1639/|Revision-Slider]] * [[phab:project/view/1677/|revscoring]] * Riksarkivet ** [[phab:project/view/5289/|Riksarkivet-NAD]] * [[phab:project/view/3395/|RunningStat]] * [[phab:project/view/1449/|Scap]] * [[phab:project/view/2283/|ScopedCallback]] * [[phab:project/view/4051/|Scribe]] * SDAW ** [[phab:project/view/4899/|SDAW-MediaSearch]] ** [[phab:project/view/5877/|SDAW-Search-Improvements]] ** [[phab:project/view/5979/|SDAW-SearchVue]] * [[phab:project/view/34/|SDC General]] * SDC ** [[phab:project/view/3936/|SDC-Statements]] * Search ** [[phab:project/view/5882/|Search-Console-access-request]] * [[phab:project/view/3915/|Section Editing (Mobile)]] * Section ** [[phab:project/view/6012/|Section-Level-Image-Suggestions]] ** [[phab:project/view/4668/|Section-Name-Diff]] ** [[phab:project/view/6013/|Section-Topics]] * [[phab:project/view/4909/|SectionTranslation]] * [[phab:project/view/4430/|Security Architecture Tooling]] * [[phab:project/view/4428/|Security Awareness]] * [[phab:project/view/4424/|Security Incident Response]] * [[phab:project/view/4423/|Security policy and procedure]] * [[phab:project/view/4466/|Security Preview]] * [[phab:project/view/4421/|Security Risk Management]] * [[phab:project/view/4427/|Security Supplier Assessments]] * [[phab:project/view/4429/|Security Team AppSec]] * Security ** [[phab:project/view/5870/|Security-API-Service]] * [[phab:project/view/976/|Sentry]] * Server ** [[phab:project/view/5629/|Server-side-upload-request]] * service ** [[phab:project/view/1062/|service-runner]] ** [[phab:project/view/1072/|service-template-node]] * [[phab:project/view/5125/|Shellbox]] * Shop ** [[phab:project/view/913/|Shop-Theme]] * [[phab:project/view/620/|ShoutWiki Calendar]] * [[phab:project/view/5310/|ShoutWikiAds]] * Show ** [[phab:project/view/5954/|Show-Recent-Block-History-for-IPs-and-Ranges-Wish-2022]] * [[phab:project/view/5773/|Similar Editors]] * [[phab:project/view/186/|SiteMatrix]] * [[phab:project/view/875/|SiteMetrics]] * Small ** [[phab:project/view/4657/|Small-Wiki-Toolkits]] * [[phab:project/view/326/|SocialProfile]] * [[phab:project/view/4418/|SonarQube Bot]] * [[phab:project/view/3476/|Soweego]] * [[phab:project/view/192/|SpamBlacklist]] * [[phab:project/view/2383/|SpamRegex]] * [[phab:project/view/5674/|Special:NewLexeme revival]] * [[phab:project/view/903/|SpellingDictionary]] * [[phab:project/view/5222/|Spicerack]] * [[phab:project/view/1928/|Splash]] * [[phab:project/view/4544/|SRE Program Management]] * SRE ** [[phab:project/view/956/|SRE-Access-Requests]] ** [[phab:project/view/76/|SRE-swift-storage]] ** [[phab:project/view/1828/|SRE-tools]] * [[phab:project/view/1364/|Stashbot]] * [[phab:project/view/3903/|Status]] * [[phab:project/view/1821/|stewardbots]] * [[phab:project/view/2134/|Striker]] * [[phab:project/view/3633/|Structured Data Engineering]] * [[phab:project/view/657/|StructuredDiscussions]] * [[phab:project/view/5633/|SuenaWiki Reloaded]] * [[phab:project/view/2340/|Suggestor]] * [[phab:project/view/5683/|Superset]] * [[phab:project/view/3542/|SVG Translate Tool]] * [[phab:project/view/277/|SyntaxHighlight]] * [[phab:project/view/4237/|Talk Pages]] * [[phab:project/view/1582/|TaxonBot]] * Tech ** [[phab:project/view/4953/|Tech-Product API Roadmap]] * [[phab:project/view/4610/|Technical blog]] * Technical ** [[phab:project/view/4654/|Technical-blog-posts]] ** [[phab:project/view/2235/|Technical-Tool-Request]] * [[phab:project/view/638/|TemplateData]] * [[phab:project/view/1932/|TemplateStyles]] * Test ** [[phab:project/view/5022/|Test-Grounds]] * [[phab:project/view/747/|TextExtracts]] * [[phab:project/view/1771/|Texvcjs]] * [[phab:project/view/5678/|Teyora]] * Thank ** [[phab:project/view/4977/|Thank-You-Page]] * [[phab:project/view/628/|Thanks]] * The ** [[phab:project/view/1690/|The-Wikipedia-Adventure]] * [[phab:project/view/1388/|Theme]] * [[phab:project/view/4426/|Threat Modeling]] * [[phab:project/view/1672/|Thumbor]] * [[phab:project/view/5851/|Thumbor Migration]] * [[phab:project/view/299/|TimedMediaHandler]] ** [[phab:project/view/1590/|TimedMediaHandler-TimedText]] ** [[phab:project/view/1591/|TimedMediaHandler-Transcode]] * [[phab:project/view/1912/|Timeless]] * [[phab:project/view/292/|TitleBlacklist]] * [[phab:project/view/2423/|tofawiki]] * Tool ** [[phab:project/view/3261/|Tool-admin]] ** [[phab:project/view/5356/|Tool-ameisenbot]] ** [[phab:project/view/1138/|Tool-anagrimes]] ** [[phab:project/view/762/|Tool-Article-request]] ** [[phab:project/view/1290/|Tool-Attribution-Generator]] ** [[phab:project/view/5166/|Tool-bodh]] ** [[phab:project/view/5355/|Tool-botmahmood]] ** [[phab:project/view/6018/|Tool-boxybot]] ** [[phab:project/view/4955/|Tool-bridgebot]] ** [[phab:project/view/4889/|Tool-commonsapi]] ** [[phab:project/view/4968/|Tool-cycling-init-bot]] ** [[phab:project/view/5401/|Tool-deploy-commands]] * tool ** [[phab:project/view/5936/|tool-docs]] * Tool ** [[phab:project/view/5350/|Tool-drift-tracker]] ** [[phab:project/view/775/|Tool-Erwin's-tools]] ** [[phab:project/view/5058/|Tool-explore-TopicContribs]] ** [[phab:project/view/4010/|Tool-extjsonuploader]] ** [[phab:project/view/2834/|Tool-fatameh]] ** [[phab:project/view/4052/|Tool-flickrdash]] ** [[phab:project/view/4972/|Tool-g8-patrol]] ** [[phab:project/view/5290/|Tool-gawa]] ** [[phab:project/view/986/|Tool-Gerrit-Patch-Uploader]] ** [[phab:project/view/4053/|Tool-global-search]] ** [[phab:project/view/766/|Tool-Global-user-contributions]] ** [[phab:project/view/5211/|Tool-image-content-filtration]] ** [[phab:project/view/5135/|Tool-infogeek244-grammabot]] ** [[phab:project/view/4059/|Tool-inteGraality]] ** [[phab:project/view/5348/|Tool-ip]] ** [[phab:project/view/5295/|Tool-itwiki]] ** [[phab:project/view/5333/|Tool-klexiboxen]] ** [[phab:project/view/5955/|Tool-kuwikibot]] ** [[phab:project/view/3999/|Tool-ldap]] ** [[phab:project/view/5342/|Tool-leksem-indonesia]] ** [[phab:project/view/708/|Tool-lists]] ** [[phab:project/view/5182/|Tool-logo-test]] ** [[phab:project/view/5330/|Tool-lokasbot]] ** [[phab:project/view/4678/|Tool-MajavahBot]] ** [[phab:project/view/750/|Tool-Matthewrbowker's-tools]] ** [[phab:project/view/4771/|Tool-mdvt]] ** [[phab:project/view/773/|Tool-meetbot]] ** [[phab:project/view/4746/|Tool-MoeData]] ** [[phab:project/view/112/|Tool-nlwikibots]] ** [[phab:project/view/5016/|Tool-openstack-browser]] ** [[phab:project/view/2045/|Tool-Pageviews]] ** [[phab:project/view/6054/|Tool-pdlarcher]] ** [[phab:project/view/2159/|Tool-Phabricator-bug-status]] ** [[phab:project/view/5049/|Tool-rangeblockfinder]] ** [[phab:project/view/5987/|Tool-rc-discord]] ** [[phab:project/view/5013/|Tool-refill]] ** [[phab:project/view/5549/|Tool-sbdjwhsh]] ** [[phab:project/view/5037/|Tool-search-filters]] ** [[phab:project/view/5138/|Tool-socks]] ** [[phab:project/view/4235/|Tool-spacemedia]] * tool ** [[phab:project/view/5673/|tool-sql-optimizer]] * Tool ** [[phab:project/view/5085/|Tool-sqlchecker]] ** [[phab:project/view/4988/|Tool-suggestbotbn]] ** [[phab:project/view/5425/|Tool-test-stats]] ** [[phab:project/view/5518/|Tool-topictagging]] ** [[phab:project/view/743/|Tool-tsreports]] ** [[phab:project/view/4956/|Tool-wiki-importer]] ** [[phab:project/view/5056/|Tool-wikiauthbot]] ** [[phab:project/view/1262/|Tool-Wikidata-Periodic-Table]] ** [[phab:project/view/1847/|Tool-wikiloves]] * tool ** [[phab:project/view/3758/|tool-ws-cat-browser]] ** [[phab:project/view/3422/|tool-wscontest]] * Tool ** [[phab:project/view/5325/|Tool-zhwpvg-article-list]] * [[phab:project/view/539/|Toolforge]] * [[phab:project/view/5596/|Toolforge Build Service]] * [[phab:project/view/5969/|Toolforge Jobs framework]] * [[phab:project/view/5196/|ToolforgeBundle]] * [[phab:project/view/3224/|Toolhub]] * tox ** [[phab:project/view/4548/|tox-wikimedia]] * [[phab:project/view/2263/|Truglass]] * Twinkle ** [[phab:project/view/5589/|Twinkle-on-Turkish-Wikipedia]] * Twitter ** [[phab:project/view/4176/|Twitter-to-Commons]] * Two ** [[phab:project/view/2277/|Two-Column-Edit-Conflict-Merge]] * UI ** [[phab:project/view/24/|UI-Standardization]] * ULS ** [[phab:project/view/1116/|ULS-CompactLinks]] * UNESCO ** [[phab:project/view/2761/|UNESCO-Wikimedian-in-Residence]] * [[phab:project/view/442/|UniversalLanguageSelector]] * [[phab:project/view/2204/|UnusedRedirects]] * [[phab:project/view/402/|UploadWizard]] * [[phab:project/view/2386/|uprightdiff]] * [[phab:project/view/4324/|urbanecmbot]] * User ** [[phab:project/view/2853/|User-Testing]] * [[phab:project/view/2268/|UserStatus]] * [[phab:project/view/1069/|utfnormal]] * Utilities ** [[phab:project/view/446/|Utilities-code-utils]] ** [[phab:project/view/753/|Utilities-grabbers]] ** [[phab:project/view/251/|Utilities-mwdumper]] ** [[phab:project/view/864/|Utilities-UnicodeJS]] * [[phab:project/view/4269/|Vabatahtlikule]] * [[phab:project/view/918/|ValueView]] * [[phab:project/view/166/|Vector]] * Video (non ** [[phab:project/view/1827/|Video (non-WMF)]] * [[phab:project/view/2141/|video2commons]] * [[phab:project/view/4054/|VideoCutTool]] * [[phab:project/view/4375/|VideoJS player]] * [[phab:project/view/3383/|VisualCategories]] * VisualEditor ** [[phab:project/view/480/|VisualEditor-ContentEditable]] ** [[phab:project/view/499/|VisualEditor-ContentLanguage]] ** [[phab:project/view/898/|VisualEditor-CopyPaste]] ** [[phab:project/view/503/|VisualEditor-DataModel]] ** [[phab:project/view/4171/|VisualEditor-Edit Cards ]] ** [[phab:project/view/486/|VisualEditor-EditingTools]] ** [[phab:project/view/612/|VisualEditor-Initialisation]] ** [[phab:project/view/899/|VisualEditor-InterfaceLanguage]] ** [[phab:project/view/1268/|VisualEditor-LanguageTool]] ** [[phab:project/view/1020/|VisualEditor-Links]] ** [[phab:project/view/1021/|VisualEditor-Media]] ** [[phab:project/view/484/|VisualEditor-MediaWiki]] ** [[phab:project/view/2301/|VisualEditor-MediaWiki-2017WikitextEditor]] ** [[phab:project/view/830/|VisualEditor-MediaWiki-Links]] ** [[phab:project/view/828/|VisualEditor-MediaWiki-Media]] ** [[phab:project/view/515/|VisualEditor-MediaWiki-Mobile]] ** [[phab:project/view/1019/|VisualEditor-MediaWiki-Plugins]] ** [[phab:project/view/827/|VisualEditor-MediaWiki-References]] ** [[phab:project/view/829/|VisualEditor-MediaWiki-Templates]] ** [[phab:project/view/4111/|VisualEditor-Mobile-UsabilityImprovements]] ** [[phab:project/view/831/|VisualEditor-Performance]] ** [[phab:project/view/826/|VisualEditor-Tables]] ** [[phab:project/view/2710/|VisualEditor-VisualDiffs]] * vm ** [[phab:project/view/1234/|vm-requests]] * [[phab:project/view/729/|VoteNY]] * VPS ** [[phab:project/view/3158/|VPS-project-Codesearch]] ** [[phab:project/view/819/|VPS-project-Extdist]] ** [[phab:project/view/2825/|VPS-project-icinga2]] ** [[phab:project/view/2103/|VPS-project-Phabricator]] ** [[phab:project/view/5497/|VPS-Project-wikicommunityhealth]] ** [[phab:project/view/543/|VPS-project-Wikistats]] * [[phab:project/view/5725/|vrts]] * [[phab:project/view/5602/|Vue.js]] * [[phab:project/view/4431/|Vulnerability Management]] * [[phab:project/view/2284/|WaitConditionLoop]] * [[phab:project/view/4340/|WatchTranslations]] * WDQS ** [[phab:project/view/3027/|WDQS-Optimizer]] * wdwb ** [[phab:project/view/3532/|wdwb-tech]] * [[phab:project/view/3165/|Weapon of Mass Description]] * [[phab:project/view/5933/|Web Team Visual Regression Framework]] * Web2Cit ** [[phab:project/view/5669/|Web2Cit-Community]] ** [[phab:project/view/5670/|Web2Cit-Core]] ** [[phab:project/view/5760/|Web2Cit-Editor]] ** [[phab:project/view/5929/|Web2Cit-Gadget]] ** [[phab:project/view/5810/|Web2Cit-Monitor]] ** [[phab:project/view/5668/|Web2Cit-Research]] ** [[phab:project/view/5689/|Web2Cit-Server]] * [[phab:project/view/3619/|WebPageReplay]] * [[phab:project/view/1777/|WebPageTest]] * Who ** [[phab:project/view/3836/|Who-Wrote-That]] * Wiki Loves Monuments FY 2021 ** [[phab:project/view/5708/|Wiki Loves Monuments FY 2021-2022]] * Wiki Loves Monuments FY 2022 ** [[phab:project/view/5709/|Wiki Loves Monuments FY 2022-2023]] * Wiki ** [[phab:project/view/4042/|Wiki-goes-Caribbean]] ** [[phab:project/view/545/|Wiki-Loves-Monuments-Database]] ** [[phab:project/view/550/|Wiki-Loves-Monuments-Sources]] ** [[phab:project/view/2941/|Wiki-Setup]] * [[phab:project/view/5505/|Wiki2Reveal]] * [[phab:project/view/2341/|WikiApiary]] * [[phab:project/view/385/|WikiArticleFeeds]] * [[phab:project/view/2909/|wikiba.se website]] * [[phab:project/view/17/|Wikibase (3rd party installations)]] * Wikibase ** [[phab:project/view/4930/|Wikibase - Automated Configuration Detection (WikibaseManifest)]] ** [[phab:project/view/4604/|Wikibase - Federated Properties]] * [[phab:project/view/5094/|Wikibase and Wikidata Architecture Overview]] * [[phab:project/view/5513/|Wikibase change dispatching scripts to jobs]] * [[phab:project/view/5958/|Wikibase Cloud Test]] * [[phab:project/view/5307/|Wikibase OPEN!NEXT]] * [[phab:project/view/5095/|Wikibase Pingback]] * [[phab:project/view/5771/|Wikibase Product Platform]] * [[phab:project/view/5063/|Wikibase Release Strategy]] * [[phab:project/view/5003/|Wikibase REST API Schema]] * [[phab:project/view/5755/|Wikibase Suite]] * Wikibase ** [[phab:project/view/920/|Wikibase-DataModel]] ** [[phab:project/view/923/|Wikibase-DataModel-JavaScript]] ** [[phab:project/view/922/|Wikibase-DataModel-Serialization]] ** [[phab:project/view/1335/|Wikibase-DataModel-Services]] ** [[phab:project/view/921/|Wikibase-Internal-Serialization]] ** [[phab:project/view/925/|Wikibase-JavaScript-Api]] ** [[phab:project/view/3336/|Wikibase-Lua]] ** [[phab:project/view/1202/|Wikibase-Quality-Constraints]] ** [[phab:project/view/3363/|Wikibase-registry]] ** [[phab:project/view/919/|Wikibase-Serialization-JavaScript]] * [[phab:project/view/5563/|Wikibase.cloud]] * [[phab:project/view/1816/|WikibaseMediaInfo]] * [[phab:project/view/36/|Wikibugs]] * [[phab:project/view/1641/|WikiCategoryTagCloud]] * [[phab:project/view/1608/|WikiCite]] * Wikidata ** [[phab:project/view/4817/|Wikidata - DS hike]] ** [[phab:project/view/4635/|Wikidata - Reference Treasure Hunt]] ** [[phab:project/view/5200/|Wikidata - Visualisation of Reliability Metrics]] * [[phab:project/view/5408/|Wikidata Analytics]] * [[phab:project/view/4521/|Wikidata Design System]] * [[phab:project/view/3404/|Wikidata Mobile]] * [[phab:project/view/4990/|Wikidata Query Builder]] * [[phab:project/view/2901/|Wikidata Query UI]] * [[phab:project/view/5068/|Wikidata subsets cloud & interop]] * [[phab:project/view/4242/|Wikidata Tainted References]] * Wikidata ** [[phab:project/view/4074/|Wikidata-Bridge]] ** [[phab:project/view/1278/|Wikidata-Gadgets]] ** [[phab:project/view/1158/|Wikidata-Page-Banner]] ** [[phab:project/view/2788/|Wikidata-primary-sources]] ** [[phab:project/view/891/|Wikidata-Query-Service]] ** [[phab:project/view/3620/|Wikidata-Termbox]] * [[phab:project/view/125/|Wikidata.org]] * [[phab:project/view/270/|wikidiff2]] * [[phab:project/view/3394/|Wikidocumentaries]] * [[phab:project/view/342/|WikiEditor]] * [[phab:project/view/4110/|Wikifeeds]] * [[phab:project/view/469/|WikiForum]] * [[phab:project/view/183/|WikiHiero]] * [[phab:project/view/1466/|Wikilabels]] * [[phab:project/view/5275/|WikiLambda]] * Wikilink ** [[phab:project/view/4082/|Wikilink-Tool]] * [[phab:project/view/445/|WikiLove]] * wikimaps ** [[phab:project/view/1886/|wikimaps-warper]] * [[phab:project/view/3215/|Wikimedia Australia]] * [[phab:project/view/4948/|Wikimedia Chat]] * [[phab:project/view/1016/|Wikimedia Design Style Guide]] * [[phab:project/view/5642/|Wikimedia Enterprise DevOps]] * [[phab:project/view/5520/|Wikimedia Enterprise Discussion]] * [[phab:project/view/5777/|Wikimedia Enterprise Engineering]] * [[phab:project/view/5684/|Wikimedia Enterprise External Request]] * [[phab:project/view/5579/|Wikimedia Enterprise Infrastructure v2]] * [[phab:project/view/5778/|Wikimedia Enterprise Modeling]] * [[phab:project/view/5610/|Wikimedia Enterprise QA]] * [[phab:project/view/5578/|Wikimedia Enterprise SSO]] * [[phab:project/view/5577/|Wikimedia Enterprise Uptime Monitoring]] * [[phab:project/view/5569/|Wikimedia Enterprise Web Application]] * [[phab:project/view/4729/|Wikimedia Meet]] * [[phab:project/view/4739/|Wikimedia OCR]] * [[phab:project/view/1871/|Wikimedia Resource Center]] * Wikimedia ** [[phab:project/view/4752/|Wikimedia-abusefilter-global-maintainers]] ** [[phab:project/view/5185/|Wikimedia-Affiliates-Data-Portal]] ** [[phab:project/view/382/|Wikimedia-Apache-configuration]] ** [[phab:project/view/152/|Wikimedia-Bugzilla]] ** [[phab:project/view/1024/|Wikimedia-Cdb]] ** [[phab:project/view/2479/|Wikimedia-CentralNotice-Administration]] ** [[phab:project/view/4941/|Wikimedia-Developer-Portal]] ** [[phab:project/view/447/|Wikimedia-Etherpad]] ** [[phab:project/view/188/|Wikimedia-Extension-setup]] ** [[phab:project/view/2893/|Wikimedia-FR-Tech-Projects]] ** [[phab:project/view/2892/|Wikimedia-FR-Tech-Systems]] ** [[phab:project/view/2715/|Wikimedia-Fundraising-Banners]] ** [[phab:project/view/1130/|Wikimedia-Fundraising-Campaigns]] ** [[phab:project/view/404/|Wikimedia-Fundraising-CiviCRM]] ** [[phab:project/view/1524/|Wikimedia-GitHub]] ** [[phab:project/view/815/|Wikimedia-IEG-grant-review]] ** [[phab:project/view/143/|Wikimedia-Interwiki-links]] * wikimedia ** [[phab:project/view/2751/|wikimedia-irc-libera]] * Wikimedia ** [[phab:project/view/227/|Wikimedia-IRC-RC-Server]] ** [[phab:project/view/179/|Wikimedia-Language-setup]] ** [[phab:project/view/772/|Wikimedia-Logstash]] ** [[phab:project/view/190/|Wikimedia-Mailing-lists]] ** [[phab:project/view/5193/|Wikimedia-Minify]] * wikimedia ** [[phab:project/view/2729/|wikimedia-page-library]] * Wikimedia ** [[phab:project/view/2666/|Wikimedia-Phabricator-Extensions]] ** [[phab:project/view/413/|Wikimedia-Planet]] ** [[phab:project/view/1619/|Wikimedia-Portals]] ** [[phab:project/view/165/|Wikimedia-Rdbms]] ** [[phab:project/view/178/|Wikimedia-Site-requests]] ** [[phab:project/view/5625/|Wikimedia-Small-Projects-User-Group-Projects]] ** [[phab:project/view/211/|Wikimedia-SVG-rendering]] ** [[phab:project/view/2949/|Wikimedia-Takedown-Tools]] ** [[phab:project/view/4853/|Wikimedia-Tech-Talks]] ** [[phab:project/view/2285/|Wikimedia-Timestamp]] ** [[phab:project/view/1255/|Wikimedia-Video]] ** [[phab:project/view/740/|Wikimedia-Wikimania-Scholarships]] * [[phab:project/view/536/|wikimedia.biterg.io]] * [[phab:project/view/4822/|WikimediaApiPortal]] * [[phab:project/view/4924/|WikimediaDebug]] * [[phab:project/view/3907/|WikimediaEditorTasks]] * [[phab:project/view/3496/|wikimediafoundation.org]] * [[phab:project/view/426/|WikimediaMessages]] * WikimediaUI ** [[phab:project/view/5064/|WikimediaUI-Base]] * [[phab:project/view/5220/|Wikimini.org]] * [[phab:project/view/3314/|Wikinity]] * Wikipedia ** [[phab:project/view/4393/|Wikipedia-Preview]] * [[phab:project/view/4156/|wikipedia.de]] * [[phab:project/view/4090/|WikiPEG]] * [[phab:project/view/3857/|Wikiportrait]] * WikiProject ** [[phab:project/view/3493/|WikiProject-Biodiversity]] ** [[phab:project/view/3356/|WikiProject-ShEx]] ** [[phab:project/view/1640/|WikiProject-tools]] * [[phab:project/view/5868/|WikiSEO]] * Wikispeech ** [[phab:project/view/4379/|Wikispeech-Jobrunner]] ** [[phab:project/view/4349/|Wikispeech-Speech-Data-Collector]] ** [[phab:project/view/4344/|Wikispeech-Text-to-Speech]] * [[phab:project/view/4250/|Wikispore]] * [[phab:project/view/5564/|Wikistories]] * [[phab:project/view/531/|wikitech.wikimedia.org]] * [[phab:project/view/871/|WikiTextLoggedInOut]] * [[phab:project/view/5672/|WikiWho]] * WLM ** [[phab:project/view/4325/|WLM-Italy-Finder]] ** [[phab:project/view/4327/|WLM-Italy-Finder-App]] ** [[phab:project/view/4326/|WLM-Italy-Stats]] * WLX ** [[phab:project/view/1741/|WLX-Jury]] * WM ** [[phab:project/view/668/|WM-Bot]] ** [[phab:project/view/4782/|WMCH-Cronos]] ** [[phab:project/view/4830/|WMCH-Infrastructure]] ** [[phab:project/view/4799/|WMCH-Minipedia]] ** [[phab:project/view/3712/|WMCZ-General]] ** [[phab:project/view/5305/|WMCZ-Stats]] ** [[phab:project/view/3391/|WMCZ-Tracker]] ** [[phab:project/view/4399/|WMCZ-Web]] ** [[phab:project/view/5928/|WMDE-FUN-Tech-Payment-Refactoring]] ** [[phab:project/view/1688/|WMDE-Fundraising-Tech]] ** [[phab:project/view/5559/|WMDE-GeoInfo-FocusArea]] ** [[phab:project/view/2821/|WMDE-New-Editors-Banner-Campaigns]] * wmde ** [[phab:project/view/5865/|wmde-team-b-tech]] * WMDE ** [[phab:project/view/1702/|WMDE-Tech-Communication-Mentoring-And-Events]] ** [[phab:project/view/5892/|WMDE-technical-needs-from-WMF]] ** [[phab:project/view/4529/|WMDE-Templates-FocusArea]] * wmde ** [[phab:project/view/5864/|wmde-wikidata-tech]] * [[phab:project/view/3609/|WMEE 101+]] * WMEE ** [[phab:project/view/3560/|WMEE-gen]] * WMF ** [[phab:project/view/42/|WMF-Annual-Report]] ** [[phab:project/view/151/|WMF-General-or-Unknown]] ** [[phab:project/view/811/|WMF-JobQueue]] ** [[phab:project/view/5595/|WMF-Safety-Survey]] * wmf ** [[phab:project/view/4861/|wmf-sre-laptop]] ** [[phab:project/view/4627/|wmfdata-python]] * [[phab:project/view/5611/|wmfdb]] * WMIT ** [[phab:project/view/5827/|WMIT-CiviCRM]] ** [[phab:project/view/5047/|WMIT-Infrastructure]] ** [[phab:project/view/5241/|WMIT-LimeSurvey]] * WMNO ** [[phab:project/view/3255/|WMNO-General]] ** [[phab:project/view/5459/|WMNO-Knowledge-Equity]] ** [[phab:project/view/3141/|WMNO-Sámi]] * WMSE ** [[phab:project/view/5741/|WMSE-A-Community-for-Everybody-2022]] ** [[phab:project/view/5731/|WMSE-Advocacy-2022]] ** [[phab:project/view/5745/|WMSE-Association-Involvement-2022]] ** [[phab:project/view/5734/|WMSE-Bug-Reporting-and-Translation-2022]] ** [[phab:project/view/5738/|WMSE-Community-Support-2022]] ** [[phab:project/view/5440/|WMSE-Content-partnerships-support-2021]] ** [[phab:project/view/5445/|WMSE-Content-partnerships-support-2021-Capacity-building]] ** [[phab:project/view/5442/|WMSE-Content-partnerships-support-2021-Communication]] ** [[phab:project/view/5446/|WMSE-Content-partnerships-support-2021-Fundraising]] ** [[phab:project/view/5448/|WMSE-Content-partnerships-support-2021-Helpdesk]] ** [[phab:project/view/5444/|WMSE-Content-partnerships-support-2021-IGO/INGO]] ** [[phab:project/view/5441/|WMSE-Content-partnerships-support-2021-Project-management]] ** [[phab:project/view/5443/|WMSE-Content-partnerships-support-2021-Research]] ** [[phab:project/view/5447/|WMSE-Content-partnerships-support-2021-Software-development]] ** [[phab:project/view/5613/|WMSE-Content-partnerships-support-2021-Strategic-data-uploads]] ** [[phab:project/view/5739/|WMSE-Development-Support-2022]] ** [[phab:project/view/5749/|WMSE-Exchange-of-Experiences-2022]] ** [[phab:project/view/5748/|WMSE-Experimental-partnerships-2022]] ** [[phab:project/view/5746/|WMSE-FOSS-for-the-Association-2022]] ** [[phab:project/view/5699/|WMSE-GLAM-2022]] ** [[phab:project/view/5609/|WMSE-International-copyright-2021]] ** [[phab:project/view/5728/|WMSE-Kalmar-läns-museum-2022]] ** [[phab:project/view/5732/|WMSE-Knowledge-in-Crisis-Situations-2022]] ** [[phab:project/view/5608/|WMSE-Lowering-barriers-for-WikiGap-2021]] ** [[phab:project/view/5744/|WMSE-Organisational-Development-2022]] ** [[phab:project/view/5742/|WMSE-Partnerships-for-WikiGap-2022]] ** [[phab:project/view/5730/|WMSE-Presentations-2022]] ** [[phab:project/view/3220/|WMSE-Project-leftovers]] ** [[phab:project/view/3883/|WMSE-SMHI-2019]] ** [[phab:project/view/5747/|WMSE-Supporting-the-European-Hub-2022]] ** [[phab:project/view/5737/|WMSE-Trust-Making-2022]] ** [[phab:project/view/5733/|WMSE-Visibility-Making-2022]] ** [[phab:project/view/5740/|WMSE-Wiki-Loves-2022]] ** [[phab:project/view/5107/|WMSE-Wikidata-for-authority-control-2021]] ** [[phab:project/view/5743/|WMSE-Wikipedia-for-All-of-Sweden-2022]] ** [[phab:project/view/5729/|WMSE-Wikipedia-in-Education-2022]] ** [[phab:project/view/4447/|WMSE-Wikispeech-for-AI-2020]] ** [[phab:project/view/5735/|WMSE-Wikispeech-Maintenance-and-Support-2022]] ** [[phab:project/view/5736/|WMSE-Wikispeech-Speech-Data-Collector-Tool-2022]] * [[phab:project/view/2764/|WoOgLeShades]] * [[phab:project/view/4842/|WPCleaner]] * [[phab:project/view/4979/|WPtouch]] * [[phab:project/view/3514/|WrappedString]] * [[phab:project/view/3917/|WS Export]] * [[phab:project/view/4898/|WVUI]] * [[phab:project/view/1182/|XAnalytics]] * [[phab:project/view/4987/|XMPReader]] * [[phab:project/view/803/|XTools]] * [[phab:project/view/210/|Znuny]] === Umbrella projects === * [[phab:project/view/1887/|BlueSpice]] * Cloud ** [[phab:project/view/832/|Cloud-Services]] * Google ** [[phab:project/view/2540/|Google-Summer-of-Code]] * LDAP ** [[phab:project/view/3071/|LDAP-Extensions]] * MediaWiki ** [[phab:project/view/1539/|MediaWiki-Releasing]] ** [[phab:project/view/5614/|MediaWiki-SettingsBuilder]] * [[phab:project/view/4085/|OpenRefine]] * [[phab:project/view/2206/|Outreachy]] * [[phab:project/view/5460/|Platform Engineering Code Jam]] * Projects ** [[phab:project/view/2829/|Projects-Cleanup]] * [[phab:project/view/2334/|Reading Epics]] * Recurring ** [[phab:project/view/1311/|Recurring-Donations]] * [[phab:project/view/2453/|Release Pipeline]] * [[phab:project/view/3610/|rsc assessment]] * Security ** [[phab:project/view/4420/|Security-Team-Services]] * [[phab:project/view/3789/|Shape Expressions]] * Social ** [[phab:project/view/1009/|Social-Tools]] * [[phab:project/view/3632/|StructuredDataOnCommons]] * [[phab:project/view/1696/|Teahouse]] * [[phab:project/view/5976/|The Signpost]] * [[phab:project/view/703/|Tools]] * [[phab:project/view/483/|VisualEditor]] * VPS ** [[phab:project/view/525/|VPS-Projects]] * [[phab:project/view/5081/|wbstack]] * [[phab:project/view/5593/|Web2Cit]] * Wiki ** [[phab:project/view/575/|Wiki-Loves-Monuments]] ** [[phab:project/view/3345/|Wikibase-UserGroup]] * [[phab:project/view/71/|Wikidata]] * [[phab:project/view/2292/|Wikidata Lexicographical data]] * [[phab:project/view/1663/|Wikispeech]] * WMDE ** [[phab:project/view/3133/|WMDE-Blueprint-tickets]] ** [[phab:project/view/3295/|WMDE-TechWish-Maintenance]] ** [[phab:project/view/5799/|WMDE-TechWish-Survey]] * [[phab:project/view/4636/|WMEE]] * [[phab:project/view/4034/|WMFI]] * [[phab:project/view/3128/|WMNO]] * [[phab:project/view/2480/|WMSE]] === Tags === * [[phab:project/view/171/|Accessibility]] * affects ** [[phab:project/view/5266/|affects-Daty]] ** [[phab:project/view/4381/|affects-Kiwix-and-openZIM]] ** [[phab:project/view/6000/|affects-Scribe-Keyboards]] ** [[phab:project/view/4298/|affects-translatewiki.net]] * artificial ** [[phab:project/view/2454/|artificial-intelligence]] * audits ** [[phab:project/view/1317/|audits-data-retention]] * [[phab:project/view/4716/|AWS]] * Bengali ** [[phab:project/view/2393/|Bengali-Sites]] * Beta ** [[phab:project/view/1563/|Beta-Cluster-reproducible]] ** [[phab:project/view/58/|Beta-Feature]] * Browser ** [[phab:project/view/1298/|Browser-Support-Android-Google-Chrome]] ** [[phab:project/view/350/|Browser-Support-Apple-Safari]] ** [[phab:project/view/284/|Browser-Support-Firefox]] ** [[phab:project/view/362/|Browser-Support-Google-Chrome]] ** [[phab:project/view/164/|Browser-Support-Internet-Explorer]] ** [[phab:project/view/4575/|Browser-Support-KaiOS]] ** [[phab:project/view/1433/|Browser-Support-Microsoft-Edge]] ** [[phab:project/view/233/|Browser-Support-Opera]] ** [[phab:project/view/4456/|Browser-support-print-media]] ** [[phab:project/view/1617/|Browser-Tests]] * [[phab:project/view/4922/|castor]] * Chinese ** [[phab:project/view/2409/|Chinese-Sites]] * ci ** [[phab:project/view/4177/|ci-test-error]] * Cloud ** [[phab:project/view/5638/|Cloud-Services-Origin-Alert]] ** [[phab:project/view/5639/|Cloud-Services-Origin-Team]] ** [[phab:project/view/5637/|Cloud-Services-Origin-User]] ** [[phab:project/view/5635/|Cloud-Services-Worktype-Maintenance]] ** [[phab:project/view/5634/|Cloud-Services-Worktype-Project]] ** [[phab:project/view/5636/|Cloud-Services-Worktype-Unplanned]] * Code ** [[phab:project/view/3310/|Code-Health]] ** [[phab:project/view/4622/|Code-Health-DevEd]] ** [[phab:project/view/4720/|Code-Health-DevEd-Curriculum]] ** [[phab:project/view/3670/|Code-Health-Help-Wanted]] ** [[phab:project/view/5000/|Code-Health-Objective]] ** [[phab:project/view/4168/|Code-Health-Office-Hours]] ** [[phab:project/view/3144/|Code-Stewardship-Reviews]] * Community ** [[phab:project/view/175/|Community-consensus-needed]] ** [[phab:project/view/1482/|Community-Wishlist-Survey-2015]] ** [[phab:project/view/2420/|Community-Wishlist-Survey-2016]] ** [[phab:project/view/3078/|Community-Wishlist-Survey-2017]] * [[phab:project/view/1093/|Composer]] * [[phab:project/view/4365/|ContentSecurityPolicy]] * covid ** [[phab:project/view/4648/|covid-19]] * Croatian ** [[phab:project/view/5624/|Croatian-Sites]] * [[phab:project/view/145/|Crosswiki]] * [[phab:project/view/2149/|CSS]] * Dagbani ** [[phab:project/view/5538/|Dagbani-Sites]] * Datacenter ** [[phab:project/view/3571/|Datacenter-Switchover]] * [[phab:project/view/4656/|Dependency injection]] * [[phab:project/view/157/|Design]] * [[phab:project/view/4096/|Desktop]] * [[phab:project/view/3521/|Developer Productivity]] * Developer ** [[phab:project/view/1098/|Developer-notice]] * [[phab:project/view/987/|Documentation]] * EngProd ** [[phab:project/view/4773/|EngProd-Virtual-Hackathon]] * [[phab:project/view/942/|Epic]] * Esperanto ** [[phab:project/view/1775/|Esperanto-Sites]] * [[phab:project/view/2552/|events]] * FR ** [[phab:project/view/2062/|FR-Email]] ** [[phab:project/view/1654/|FR-Fraud]] * Gender ** [[phab:project/view/3108/|Gender-Support]] * [[phab:project/view/169/|good first task]] * [[phab:project/view/81/|Graphite]] * Gujarati ** [[phab:project/view/4825/|Gujarati-Sites]] * Hindi ** [[phab:project/view/2418/|Hindi-Sites]] * [[phab:project/view/5351/|HTML5]] * [[phab:project/view/162/|HTTPS]] * Hungarian ** [[phab:project/view/5693/|Hungarian-Sites]] * [[phab:project/view/156/|I18n]] * IABot ** [[phab:project/view/6003/|IABot-Priority-2022]] ** [[phab:project/view/6004/|IABot-Priority-Eastern-Europe-Former-USSR]] * [[phab:project/view/184/|IPv6]] * IRC ** [[phab:project/view/1773/|IRC-Meetings]] * [[phab:project/view/267/|JavaScript]] * [[phab:project/view/83/|Jenkins]] * [[phab:project/view/2361/|Kubernetes]] * [[phab:project/view/4981/|Language codes]] * [[phab:project/view/982/|LDAP]] * [[phab:project/view/3827/|Logos]] * Malayalam ** [[phab:project/view/2417/|Malayalam-Sites]] * mariadb ** [[phab:project/view/4313/|mariadb-optimizer-bug]] * [[phab:project/view/2691/|Microcontribution]] * [[phab:project/view/372/|Mobile]] * [[phab:project/view/1096/|Notice]] * Pageviews ** [[phab:project/view/3905/|Pageviews-Anomaly]] * [[phab:project/view/1852/|Paper]] * Patch ** [[phab:project/view/1825/|Patch-Needs-Improvement]] * patch ** [[phab:project/view/418/|patch-welcome]] * [[phab:project/view/196/|Performance Issue]] * Performance ** [[phab:project/view/1559/|Performance-Team-publish]] * periodic ** [[phab:project/view/2807/|periodic-update]] * [[phab:project/view/3825/|PermanentlyPrivate]] * Persona ** [[phab:project/view/1803/|Persona-Active-Editor]] ** [[phab:project/view/1801/|Persona-Active-Reader]] ** [[phab:project/view/1800/|Persona-Casual-Reader]] ** [[phab:project/view/1802/|Persona-New-Editor]] ** [[phab:project/view/1804/|Persona-Power-Editor]] ** [[phab:project/view/1805/|Persona-Vandal]] * [[phab:project/view/3267/|PHP 7.2 support]] * [[phab:project/view/3494/|PHP 7.3 support]] * [[phab:project/view/4107/|PHP 7.4 support]] * [[phab:project/view/4652/|PHP 8.0 support]] * [[phab:project/view/5132/|PHP 8.1 support]] * [[phab:project/view/6053/|PHP 8.2 support]] * [[phab:project/view/4665/|Pikk plaan]] * Plural ** [[phab:project/view/3172/|Plural-Support]] * [[phab:project/view/4411/|PM]] * [[phab:project/view/2339/|PostgreSQL]] * [[phab:project/view/1205/|Privacy]] * Product ** [[phab:project/view/5001/|Product-Feature]] * [[phab:project/view/1542/|Proposal]] * [[phab:project/view/78/|Puppet]] * Python3 ** [[phab:project/view/4522/|Python3-Porting]] * Pywikibot ** [[phab:project/view/1774/|Pywikibot-Announce]] ** [[phab:project/view/97/|Pywikibot-Documentation]] ** [[phab:project/view/102/|Pywikibot-network]] ** [[phab:project/view/1260/|Pywikibot-RfCs]] ** [[phab:project/view/107/|Pywikibot-tests]] ** [[phab:project/view/110/|Pywikibot-Wikidata]] * Quality ** [[phab:project/view/4342/|Quality-and-Test-Engineering-Office-Hours]] * [[phab:project/view/914/|Regression]] * RESTBase ** [[phab:project/view/837/|RESTBase-architecture]] * [[phab:project/view/4606/|RFS]] * [[phab:project/view/1280/|RTL]] * [[phab:project/view/1618/|Ruby]] * Russian ** [[phab:project/view/2621/|Russian-Sites]] * Schema ** [[phab:project/view/161/|Schema-change]] ** [[phab:project/view/1494/|Schema-change-in-production]] * [[phab:project/view/4493/|SecTeam Discussion]] * SecTeam ** [[phab:project/view/5180/|SecTeam-Processed]] ** [[phab:project/view/5181/|SecTeam-wikimedia-project-event]] * [[phab:project/view/4573/|Security]] * [[phab:project/view/1163/|SEO]] * Serbian ** [[phab:project/view/3791/|Serbian-Sites]] * Service ** [[phab:project/view/838/|Service-Architecture]] ** [[phab:project/view/1305/|Service-deployment-requests]] * [[phab:project/view/4063/|Skipped QA]] * Slow ** [[phab:project/view/5427/|Slow-DB-Query]] * Software ** [[phab:project/view/1443/|Software-Licensing]] * Spanish ** [[phab:project/view/2564/|Spanish-Sites]] * [[phab:project/view/2085/|Spike]] * [[phab:project/view/2752/|SQLite]] * [[phab:project/view/1541/|Story]] * [[phab:project/view/1465/|Surveys]] * [[phab:project/view/1167/|Sustainability]] * [[phab:project/view/5762/|SVG]] * Sysadmin ** [[phab:project/view/1099/|Sysadmin-notice]] * Tamil ** [[phab:project/view/2416/|Tamil-Sites]] * Tech ** [[phab:project/view/3302/|Tech-Ambassadors]] ** [[phab:project/view/609/|Technical-Debt]] * Test ** [[phab:project/view/3223/|Test-Coverage]] ** [[phab:project/view/4524/|Testing-Roadblocks]] * [[phab:project/view/138/|TestMe]] * Thai ** [[phab:project/view/5950/|Thai-Sites]] * [[phab:project/view/2835/|Tor]] * Tracking ** [[phab:project/view/134/|Tracking-Neverending]] * Turkish ** [[phab:project/view/3231/|Turkish-Sites]] * Unplanned ** [[phab:project/view/1318/|Unplanned-Sprint-Work]] * Unstewarded ** [[phab:project/view/5503/|Unstewarded-production-error]] * [[phab:project/view/153/|Upstream]] * User ** [[phab:project/view/1097/|User-notice]] * UX ** [[phab:project/view/3687/|UX-Debt]] * [[phab:project/view/825/|Verified]] * [[phab:project/view/1355/|Voice & Tone]] * Vuln ** [[phab:project/view/1345/|Vuln-Authn/Session]] ** [[phab:project/view/4258/|Vuln-CachePollution]] ** [[phab:project/view/907/|Vuln-CSRF]] ** [[phab:project/view/1340/|Vuln-DirectObjectReference]] ** [[phab:project/view/1446/|Vuln-DoS]] ** [[phab:project/view/908/|Vuln-Infoleak]] ** [[phab:project/view/905/|Vuln-Inject]] ** [[phab:project/view/4260/|Vuln-InsufficientMonitoring]] ** [[phab:project/view/1344/|Vuln-Misconfiguration]] ** [[phab:project/view/1343/|Vuln-MissingAuthz]] ** [[phab:project/view/1341/|Vuln-OpenRedirect]] ** [[phab:project/view/4259/|Vuln-SerDe]] ** [[phab:project/view/1342/|Vuln-VulnComponent]] ** [[phab:project/view/906/|Vuln-XSS]] ** [[phab:project/view/4261/|Vuln-XXE]] * WCAG ** [[phab:project/view/3289/|WCAG-Level-A]] ** [[phab:project/view/3290/|WCAG-Level-AA]] ** [[phab:project/view/3291/|WCAG-Level-AAA]] * web ** [[phab:project/view/5833/|web-team-revisit-later]] * [[phab:project/view/6024/|Wikidata data quality and trust]] * Wikimedia ** [[phab:project/view/4182/|Wikimedia-database-issue]] ** [[phab:project/view/2953/|Wikimedia-extension-review-queue]] ** [[phab:project/view/2143/|Wikimedia-Incident]] ** [[phab:project/view/2670/|Wikimedia-maintenance-script-run]] ** [[phab:project/view/1055/|Wikimedia-production-error]] * WMDE ** [[phab:project/view/4433/|WMDE-Fundraising-CFR]] ** [[phab:project/view/1943/|WMDE-Fundraising-CN]] * WorkType ** [[phab:project/view/1454/|WorkType-Maintenance]] ** [[phab:project/view/1453/|WorkType-NewFunctionality]] * [[phab:project/view/836/|Zuul]] === User groups === * [[phab:project/view/4876/|Abstract Wikipedia team]] * Africa ** [[phab:project/view/2858/|Africa-Wikimedia-Developers]] * All ** [[phab:project/view/1117/|All-and-every-Wikisource]] ** [[phab:project/view/1115/|All-and-every-Wiktionary]] * Anti ** [[phab:project/view/2660/|Anti-Harassment]] * [[phab:project/view/5960/|AvoinGLAM]] * [[phab:project/view/1942/|Brickimedia]] * Campaign ** [[phab:project/view/5430/|Campaign-Tools]] * cloud ** [[phab:project/view/2773/|cloud-services-team]] * Code ** [[phab:project/view/4165/|Code-Health-Group]] ** [[phab:project/view/3621/|Code-Health-Metrics]] ** [[phab:project/view/3766/|Code-Review-Workgroup]] * [[phab:project/view/1118/|Commons]] * Community ** [[phab:project/view/3448/|Community-Relations]] ** [[phab:project/view/945/|Community-Resources]] ** [[phab:project/view/1274/|Community-Tech]] * Content ** [[phab:project/view/5846/|Content-Transform-Team]] * Data ** [[phab:project/view/5462/|Data-Engineering]] ** [[phab:project/view/5980/|Data-Engineering-Icebox]] ** [[phab:project/view/5463/|Data-Engineering-Kanban]] ** [[phab:project/view/5682/|Data-Engineering-Radar]] ** [[phab:project/view/4996/|Data-Persistence]] ** [[phab:project/view/5050/|Data-Persistence (Consultation)]] * [[phab:project/view/1060/|DBA]] * DC ** [[phab:project/view/1784/|DC-Ops]] * Design ** [[phab:project/view/4650/|Design-Innovation-Team]] ** [[phab:project/view/839/|Design-Research]] ** [[phab:project/view/5858/|Design-Systems-Team]] * Developer ** [[phab:project/view/33/|Developer-Advocacy]] * Diffusion ** [[phab:project/view/85/|Diffusion-Repository-Administrators]] * [[phab:project/view/1174/|Discovery]] ** [[phab:project/view/1850/|Discovery-Analysis]] ** [[phab:project/view/1899/|Discovery-Portal-Backlog]] ** [[phab:project/view/1849/|Discovery-Search]] * [[phab:project/view/3728/|Editing QA]] * Editing ** [[phab:project/view/2823/|Editing-team]] * [[phab:project/view/1588/|ELiSo]] * English ** [[phab:project/view/5856/|English-Arbitration-Committee]] ** [[phab:project/view/2604/|English-Wikipedia-New-Pages-Patrol]] * Front ** [[phab:project/view/1616/|Front-end-Standards-Group]] * Fundraising ** [[phab:project/view/1390/|Fundraising-Analysis]] ** [[phab:project/view/41/|Fundraising-Backlog]] * [[phab:project/view/5517/|Generated Data Platform]] * Gerrit ** [[phab:project/view/3957/|Gerrit-Privilege-Requests]] * [[phab:project/view/2086/|GLAM]] * Growth ** [[phab:project/view/1114/|Growth-Team]] * Igbo ** [[phab:project/view/5069/|Igbo-Wikimedians-User-Group]] * [[phab:project/view/31/|importbots]] * Indiana ** [[phab:project/view/5949/|Indiana-Wikimedians]] * Indic ** [[phab:project/view/5147/|Indic-MediaWiki-Developers]] ** [[phab:project/view/3748/|Indic-TechCom]] * Infrastructure ** [[phab:project/view/5387/|Infrastructure-Foundations]] * Inuka ** [[phab:project/view/4300/|Inuka-Team]] * Koninklijke ** [[phab:project/view/5086/|Koninklijke-Bibliotheek-Team-Wiki]] * Language ** [[phab:project/view/18/|Language-Team]] * Machine ** [[phab:project/view/1901/|Machine-Learning-Team]] * MediaWiki ** [[phab:project/view/1005/|MediaWiki-Farmers]] ** [[phab:project/view/3956/|MediaWiki-Gerrit-Group-Requests]] ** [[phab:project/view/1071/|MediaWiki-Stakeholders-Group]] * Moderator ** [[phab:project/view/5869/|Moderator-Tools-Team]] * [[phab:project/view/3901/|Moegirlpedia]] * [[phab:project/view/5664/|NFDI]] * Offline ** [[phab:project/view/2387/|Offline-Working-Group]] * Performance ** [[phab:project/view/1212/|Performance-Team]] * [[phab:project/view/3654/|Platform Engineering]] * [[phab:project/view/4971/|Platform Engineering Roadmap Decision Making]] * [[phab:project/view/3696/|Platform Team Workboards]] * Policy ** [[phab:project/view/1869/|Policy-Admins]] * [[phab:project/view/4425/|Privacy Engineering]] * Product ** [[phab:project/view/3313/|Product-Analytics]] ** [[phab:project/view/2726/|Product-Infrastructure-Team-Backlog]] ** [[phab:project/view/3468/|Product-QA]] * Project ** [[phab:project/view/835/|Project-Admins]] * QTE ** [[phab:project/view/5189/|QTE-TestingOverview]] ** [[phab:project/view/4403/|Quality-and-Test-Engineering-Team (QTE)]] * Readers ** [[phab:project/view/67/|Readers-Web-Backlog]] * Reading ** [[phab:project/view/1199/|Reading-Admin]] ** [[phab:project/view/2785/|Reading-Web-Third-Party-Support]] * Release ** [[phab:project/view/20/|Release-Engineering-Team]] * [[phab:project/view/45/|Research]] ** [[phab:project/view/1864/|Research-Backlog]] * [[phab:project/view/4630/|secscrum]] * Security ** [[phab:project/view/1179/|Security-Team]] * [[phab:project/view/3775/|serviceops]] ** [[phab:project/view/6002/|serviceops-collab]] ** [[phab:project/view/4114/|serviceops-radar]] * [[phab:project/view/988/|ShoutWiki]] * [[phab:project/view/5008/|Smithsonian]] * [[phab:project/view/1025/|SRE]] * [[phab:project/view/5391/|SRE Observability]] * SRE ** [[phab:project/view/4626/|SRE-OnFire]] * Stewards ** [[phab:project/view/1596/|Stewards-and-global-tools]] * Structured ** [[phab:project/view/4223/|Structured-Data-Backlog]] * tech ** [[phab:project/view/5179/|tech-decision-forum]] * The ** [[phab:project/view/1270/|The-Wikipedia-Library]] * Toolforge ** [[phab:project/view/2457/|Toolforge-standards-committee]] * [[phab:project/view/1201/|Traffic]] ** [[phab:project/view/5516/|Traffic-Icebox]] * [[phab:project/view/991/|translatewiki.net]] * [[phab:project/view/13/|Triagers]] * [[phab:project/view/5374/|Trust and Safety Tools Team Backlog]] * Trust ** [[phab:project/view/1058/|Trust-and-Safety]] ** [[phab:project/view/3104/|Trusted-Contributors]] * [[phab:project/view/3998/|Uncyclomedia]] * Wiki ** [[phab:project/view/3359/|Wiki-Loves-Love]] ** [[phab:project/view/2588/|Wiki-Project-Med]] * [[phab:project/view/4286/|WikiClubWest]] * [[phab:project/view/6016/|Wikidata Dev Team]] * Wikidata ** [[phab:project/view/3402/|Wikidata-Campsite]] ** [[phab:project/view/5417/|Wikidata-WikiProject-Music]] * [[phab:project/view/1920/|Wikifab]] * [[phab:project/view/4317/|WikiJournals]] * [[phab:project/view/4929/|Wikimedia Enterprise]] * [[phab:project/view/2836/|Wikimedia Taiwan]] * Wikimedia ** [[phab:project/view/4329/|Wikimedia-and-Libraries-User-Group]] ** [[phab:project/view/3171/|Wikimedia-Cameroon-User-Group]] ** [[phab:project/view/1043/|Wikimedia-DC]] ** [[phab:project/view/363/|Wikimedia-Fundraising]] ** [[phab:project/view/2367/|Wikimedia-Israel-Hackers]] * wikimedia ** [[phab:project/view/2744/|wikimedia-page-library-tshirt]] * Wikimedia ** [[phab:project/view/5197/|Wikimedia-Small-Projects-User-Group]] ** [[phab:project/view/2865/|Wikimedia-Small-Projects-User-Group-TechCom]] ** [[phab:project/view/2990/|Wikimedia-User-Group-Basque]] ** [[phab:project/view/2677/|Wikimedia-Venezuela]] * Wikipedia ** [[phab:project/view/489/|Wikipedia-Android-App-Backlog]] ** [[phab:project/view/782/|Wikipedia-iOS-App-Backlog]] * Wikisource ** [[phab:project/view/1334/|Wikisource-Community-User-Group]] * Wikispeech ** [[phab:project/view/1979/|Wikispeech-KTH]] ** [[phab:project/view/1980/|Wikispeech-STTS]] ** [[phab:project/view/1978/|Wikispeech-WMSE]] * Wiktionary ** [[phab:project/view/4363/|Wiktionary-fr]] * WMDE ** [[phab:project/view/1585/|WMDE-Analytics-Engineering]] ** [[phab:project/view/1944/|WMDE-Design]] ** [[phab:project/view/2276/|WMDE-FUN-Team]] ** [[phab:project/view/2323/|WMDE-TechWish]] * WMF ** [[phab:project/view/4805/|WMF-Architecture-Team]] ** [[phab:project/view/1520/|WMF-Communications]] ** [[phab:project/view/57/|WMF-Design]] ** [[phab:project/view/28/|WMF-Legal]] ** [[phab:project/view/974/|WMF-NDA-Requests]] * WMSE ** [[phab:project/view/2521/|WMSE-Communication]] * WMUA ** [[phab:project/view/1686/|WMUA-Tech]] === ACLs === * acl*access ** [[phab:project/view/1515/|acl*access-policy-approvers]] * acl*AHT ** [[phab:project/view/4323/|acl*AHT-Private_policy_admins]] * [[phab:project/view/2217/|acl*analytics]] * acl*Analytics ** [[phab:project/view/3154/|acl*Analytics-Legal_policy_admins]] * [[phab:project/view/2025/|acl*annual_report_policy_admins]] * acl*blog ** [[phab:project/view/3774/|acl*blog-admins]] * [[phab:project/view/1418/|acl*communityrelations_policy_admins]] * acl*discovery ** [[phab:project/view/2625/|acl*discovery-repository-admins]] * acl*English ** [[phab:project/view/5855/|acl*English-Arbitration-Committee_policy_admins]] * [[phab:project/view/1142/|acl*fr_policy_admins]] * [[phab:project/view/1644/|acl*fundraising_research_policy_admins]] * acl*otrs ** [[phab:project/view/2406/|acl*otrs-admins]] * [[phab:project/view/5603/|acl*performance_team]] * [[phab:project/view/1081/|acl*phabricator]] * acl*procurement ** [[phab:project/view/1586/|acl*procurement-review]] * acl*Project ** [[phab:project/view/1776/|acl*Project-Admins]] * [[phab:project/view/3764/|acl*release_security_pre_announce]] * [[phab:project/view/1615/|acl*releng]] * acl*repository ** [[phab:project/view/2624/|acl*repository-admins]] * [[phab:project/view/2112/|acl*research_collaborations_policy_admins]] * [[phab:project/view/30/|acl*security]] * [[phab:project/view/4569/|acl*security_bugwrangler]] * [[phab:project/view/4564/|acl*security_developer]] * [[phab:project/view/4568/|acl*security_documentation]] * [[phab:project/view/4571/|acl*security_legal]] * [[phab:project/view/4565/|acl*security_management]] * [[phab:project/view/4567/|acl*security_product_manager]] * [[phab:project/view/4566/|acl*security_program_manager]] * [[phab:project/view/4563/|acl*security_releng]] * [[phab:project/view/4560/|acl*security_secteam]] * [[phab:project/view/4562/|acl*security_sre]] * [[phab:project/view/4570/|acl*security_steward]] * [[phab:project/view/2356/|acl*security_team]] * [[phab:project/view/4561/|acl*security_trusa]] * [[phab:project/view/4559/|acl*security_volunteer]] * [[phab:project/view/4572/|acl*security_wmde]] * acl*sre ** [[phab:project/view/29/|acl*sre-team]] * [[phab:project/view/2849/|acl*stewards]] * [[phab:project/view/2135/|acl*support_and_safety_policy_admins]] * [[phab:project/view/3442/|acl*userdisable]] * acl*Wikimedia ** [[phab:project/view/2991/|acl*Wikimedia-User-Group-Basque_policy_admins]] * [[phab:project/view/2808/|acl*wikisp_policy_admins]] * acl*wmcs ** [[phab:project/view/4858/|acl*wmcs-team]] * acl*WMDE ** [[phab:project/view/4753/|acl*WMDE-Technical-Wishes-Private_policy_admins]] * acl*WMF ** [[phab:project/view/4457/|acl*WMF-Communications_policy_admins]] ** [[phab:project/view/1070/|acl*WMF-FR]] ** [[phab:project/view/5264/|acl*WMF-Technical-Program-Management_policy_admins]] * [[phab:project/view/2904/|acl*wmf_blog_social_team_policy_admins]] * acl*WMIT ** [[phab:project/view/5818/|acl*WMIT-Private_policy_admins]] * [[phab:project/view/2052/|acl*WMUA_policy_admins]] * [[phab:project/view/4299/|Outreachy Mentors]] * WMF ** [[phab:project/view/61/|WMF-NDA]] === Goals === * Campaign ** [[phab:project/view/5515/|Campaign-Registration]] * CAS ** [[phab:project/view/4766/|CAS-SSO]] * Community ** [[phab:project/view/5581/|Community-Wishlist-Survey-2022]] * Data ** [[phab:project/view/3730/|Data-Portability]] * Disambiguation ** [[phab:project/view/5451/|Disambiguation-Wish-2021]] * Doc collections 2022 ** [[phab:project/view/6033/|Doc collections 2022-23]] * Doc contributions 2022 ** [[phab:project/view/6034/|Doc contributions 2022-23]] * Docs Assessment and Contributing 2022 ** [[phab:project/view/6032/|Docs Assessment and Contributing 2022-23]] * git ** [[phab:project/view/4856/|git-protocol-v2]] * [[phab:project/view/2169/|Goal]] * Growth ** [[phab:project/view/5246/|Growth-Deployments]] * Key docs update 2021 ** [[phab:project/view/5409/|Key docs update 2021-22]] * [[phab:project/view/4193/|Platform Team Initiatives]] * Pywikibot ** [[phab:project/view/904/|Pywikibot-compat-to-core]] * Realtime ** [[phab:project/view/5506/|Realtime-Preview-Wish-2021]] * [[phab:project/view/3611/|security_assessment_analytics_2018]] * [[phab:project/view/4412/|security_assessment_devtools_2019]] * services ** [[phab:project/view/1233/|services-tooling]] * [[phab:project/view/2770/|Train Deployments]] * Undelete ** [[phab:project/view/5480/|Undelete-Associated-Talk-Page (2021)]] * Wiki ** [[phab:project/view/5240/|Wiki-Techstorm-2022]] ** [[phab:project/view/5657/|Wikimedia-Hackathon-2022-Organization]] * [[phab:project/view/3605/|WMEE Eesti 1000]] * [[phab:project/view/3580/|WMEE Miljon+]] === Milestones === * 1.38.0 ** [[phab:project/view/5794/|1.38.0-wmf.25; 2022-03-07]] (MW-1.38-notes) ** [[phab:project/view/5795/|1.38.0-wmf.26; 2022-03-14]] (MW-1.38-notes) * 1.39.0 ** [[phab:project/view/6028/|1.39.0-wmf.22; 2022-07-25]] (MW-1.39-notes) ** [[phab:project/view/6029/|1.39.0-wmf.23; 2022-08-01]] (MW-1.39-notes) ** [[phab:project/view/6046/|1.39.0-wmf.25; 2022-08-15]] (MW-1.39-notes) * 1.40.0 ** [[phab:project/view/6048/|1.40.0-wmf.1; 2022-08-22]] (MW-1.40-notes) ** [[phab:project/view/6049/|1.40.0-wmf.2; 2022-08-29]] (MW-1.40-notes) ** [[phab:project/view/6050/|1.40.0-wmf.3; 2022-09-05]] (MW-1.40-notes) ** [[phab:project/view/6051/|1.40.0-wmf.4; 2022-09-12]] (MW-1.40-notes) * [[phab:project/view/5716/|2022]] (Google-Summer-of-Code) * [[phab:project/view/2860/|3rd party support]] (MinervaNeue) * [[phab:project/view/4244/|Abstract Schema]] (Platform Team Initiatives) * [[phab:project/view/5151/|actions]] (MediaWiki-Interface) * [[phab:project/view/5152/|active libraries]] (MediaWiki-Interface) * [[phab:project/view/1306/|Active Tasks]] (Machine-Learning-Team) * [[phab:project/view/5557/|Administration, Settings & Policy]] (GitLab) * [[phab:project/view/6006/|AHaT Sprint 11: The Fascinator]] (Anti-Harassment) * [[phab:project/view/6038/|AHaT Sprint 12: The Dutch Cap]] (Anti-Harassment) * [[phab:project/view/5968/|AHaT Sprint 9: The Beret]] (Anti-Harassment) * [[phab:project/view/5195/|Ambassador]] (User-Urbanecm_WMF) * [[phab:project/view/2758/|Analytics]] (Reading Epics) * Android Release FY2021 ** [[phab:project/view/5420/|Android Release FY2021-22]] (Wikipedia-Android-App-Backlog) * [[phab:project/view/4321/|API Gateway]] (Platform Team Initiatives) * [[phab:project/view/4210/|API Integration Tests]] (Platform Team Initiatives) * [[phab:project/view/5554/|Auth & Access]] (GitLab) * [[phab:project/view/2613/|Authentication]] (Reading Epics) * [[phab:project/view/5059/|autocomplete search]] (MediaWiki-Interface) * [[phab:project/view/5786/|Automatic article quality assessment]] (WMSE-Development-Support-2022) * [[phab:project/view/4526/|Automatic article quality assessment]] (WMSE-Development-Support-2020) * [[phab:project/view/5315/|Automatic article quality assessment]] (WMSE-Development-Support-2021) * [[phab:project/view/5019/|Backlog]] (Product-Data-Infrastructure) * [[phab:project/view/5867/|Bad data]] (Wikimedia-database-issue) * [[phab:project/view/5543/|Banner campaign occasional editors 2021]] (WMDE-New-Editors-Banner-Campaigns) * [[phab:project/view/2121/|Beta Cluster Release]] (FileAnnotations) * [[phab:project/view/2812/|Blubber]] (Release Pipeline) * Campaign ** [[phab:project/view/5767/|Campaign-Design]] (Campaign-Tools) ** [[phab:project/view/6040/|Campaign-Tools-Sprint-17]] (Campaign-Tools) ** [[phab:project/view/4030/|Campaigns-jogging]] (SDC-Statements) * [[phab:project/view/2465/|Central Notice for Apps]] (Reading Epics) * [[phab:project/view/5555/|CI & Job Runners]] (GitLab) * [[phab:project/view/5787/|Citoid library for SVWP]] (WMSE-Development-Support-2022) * [[phab:project/view/4523/|Citoid library for SVWP]] (WMSE-Development-Support-2020) * [[phab:project/view/5316/|Citoid library for SVWP]] (WMSE-Development-Support-2021) * [[phab:project/view/4149/|Clinic Duty Team]] (Platform Team Workboards) * [[phab:project/view/2944/|Close]] (Wiki-Setup) * [[phab:project/view/5153/|collapsible elements]] (MediaWiki-Interface) * [[phab:project/view/6058/|Commons]] (Wikistories) * CommTech ** [[phab:project/view/5991/|CommTech-Sprint-29]] (Community-Tech) ** [[phab:project/view/5992/|CommTech-Sprint-30]] (Community-Tech) ** [[phab:project/view/5993/|CommTech-Sprint-31]] (Community-Tech) ** [[phab:project/view/6044/|CommTech-Sprint-32]] (Community-Tech) ** [[phab:project/view/6045/|CommTech-Sprint-33]] (Community-Tech) * [[phab:project/view/4364/|Containerise Services]] (Platform Team Initiatives) * [[phab:project/view/2942/|Create]] (Wiki-Setup) * [[phab:project/view/3450/|Current Sprint]] (Growth-Team) * [[phab:project/view/4232/|Current Work]] (Structured-Data-Backlog) * [[phab:project/view/1227/|Current work]] (Discovery-Search) * [[phab:project/view/1241/|Current work]] (Discovery-Analysis) * [[phab:project/view/5649/|Debian Stretch Deprecation]] (Cloud-VPS) * [[phab:project/view/4204/|Decoupling (CDP2)]] (Platform Team Initiatives) * [[phab:project/view/3590/|Delete / Redirect]] (Wiki-Setup) * Depicts ** [[phab:project/view/3938/|Depicts-Walking]] (SDC-Statements) * [[phab:project/view/3443/|Deployment]] (Multi-Content-Revisions) * [[phab:project/view/5981/|Deployment Autopilot 🛩️]] (Release-Engineering-Team) * [[phab:project/view/5265/|Deployment Training Requests]] (Release-Engineering-Team) * [[phab:project/view/5155/|deprecated JS libraries]] (MediaWiki-Interface) * [[phab:project/view/3473/|Deprecation process]] (Technical-Debt) * [[phab:project/view/2569/|Design]] (Wikipedia-iOS-App-Backlog) * [[phab:project/view/5199/|Design Backlog]] (Editing-team) * Design ** [[phab:project/view/5859/|Design-Systems-Sprint]] (Design-Systems-Team) * [[phab:project/view/2859/|Desktop]] (MinervaNeue) * [[phab:project/view/4814/|Discovery]] (KaiOS-Wikipedia-app) * [[phab:project/view/5160/|Dodo]] (Parsoid) * [[phab:project/view/5321/|Doing]] (Release-Engineering-Team) * [[phab:project/view/3845/|Economy]] (WMSE) * [[phab:project/view/3598/|EKM]] (WMEE Sum of all paintings) * Engagement ** [[phab:project/view/5158/|Engagement-1]] (KaiOS-Wikipedia-app) * [[phab:project/view/5053/|Engineering]] (User-Urbanecm_WMF) * [[phab:project/view/4614/|External Code Reviews]] (Platform Team Workboards) * [[phab:project/view/4681/|Failed QA]] (RW-Feature-DI-Opt-out-Toggle) * [[phab:project/view/4684/|Failed QA]] (RW-Feature-DI-Sticky-Site-Header) * [[phab:project/view/4687/|Failed QA]] (RW-Feature-DI-Collapsible-Sidebar) * [[phab:project/view/4690/|Failed QA]] (RW-Feature-DI-Language-Links) * [[phab:project/view/4693/|Failed QA]] (RW-Feature-DI-Header-and-Logo) * [[phab:project/view/4696/|Failed QA]] (RW-Feature-DI-User-Menu) * [[phab:project/view/4699/|Failed QA]] (RW-Feature-DI-Language-Switcher) * [[phab:project/view/4702/|Failed QA]] (RW-Feature-DI-TOC) * [[phab:project/view/4705/|Failed QA]] (RW-Feature-DI-Article-Tools) * [[phab:project/view/4710/|Failed QA]] (RW-Feature-DI-Sticky-Article-Header) * [[phab:project/view/4713/|Failed QA]] (RW-Feature-DI-Search-Improvements) * Feature ** [[phab:project/view/1839/|Feature-Parity]] (WMDE-Fundraising-Frontend-Release) * [[phab:project/view/4319/|Featured Feeds]] (Platform Team Initiatives) * Federation v2 ** [[phab:project/view/5512/|Federation v2 - Sprint 6]] (Wikibase - Federated Properties) * [[phab:project/view/2463/|Feed Content Language Expansion]] (Reading Epics) * [[phab:project/view/5435/|Freezer 🥶]] (wdwb-tech) * FY 2021 ** [[phab:project/view/5300/|FY 2021-2022]] (Wiki-Loves-Monuments) * FY2021 ** [[phab:project/view/4864/|FY2021-22 Kanban Board]] (Editing-team) ** [[phab:project/view/5457/|FY2021-22-Research-April-June]] (Research) ** [[phab:project/view/5650/|FY2021/2022-Q2]] (SRE-OnFire) ** [[phab:project/view/5651/|FY2021/2022-Q3]] (SRE-OnFire) ** [[phab:project/view/5652/|FY2021/2022-Q4]] (SRE-OnFire) ** [[phab:project/view/5808/|FY2021/2022-Q4]] (Infrastructure-Foundations) * FY2022/2023 ** [[phab:project/view/5945/|FY2022/2023-Q1]] (SRE Observability) ** [[phab:project/view/5946/|FY2022/2023-Q2]] (SRE Observability) ** [[phab:project/view/5947/|FY2022/2023-Q3]] (SRE Observability) * [[phab:project/view/6059/|Generator]] (Wikistories) * [[phab:project/view/5293/|Geoshapes]] (Maps) * [[phab:project/view/5347/|Gerrit 3.4]] (Gerrit) * [[phab:project/view/5896/|Gerrit 3.5]] (Gerrit) * [[phab:project/view/5897/|Gerrit 3.6]] (Gerrit) * GitLab ** [[phab:project/view/5873/|GitLab-a-thon 🦊]] (Release-Engineering-Team) * [[phab:project/view/5025/|Goals]] (Product-Data-Infrastructure) * [[phab:project/view/5789/|Google Workspace integration]] (WMSE-Organisational-Development-2022) * [[phab:project/view/3846/|Grants]] (WMSE) * [[phab:project/view/6052/|Hackathon 2022]] (Lingua Libre) * [[phab:project/view/4482/|Hardware]] (cloud-services-team) * [[phab:project/view/4655/|Hash Checking]] (Platform Team Initiatives) * [[phab:project/view/3844/|HR]] (WMSE) * [[phab:project/view/4632/|Icebox]] (Platform Engineering) * [[phab:project/view/5171/|Image Suggestion API]] (Platform Team Workboards) * [[phab:project/view/4758/|Incident Followup]] (Sustainability) * [[phab:project/view/5553/|Infrastructure]] (GitLab) * [[phab:project/view/5556/|Integrations]] (GitLab) * [[phab:project/view/3842/|IT]] (WMSE) * [[phab:project/view/4659/|Jio2]] (KaiOS-Wikipedia-app) * Jul ** [[phab:project/view/5857/|Jul-Sep 2022]] (Developer-Advocacy) ** [[phab:project/view/5898/|Jul-Sep-2022]] (CommRel-Specialists-Support) * [[phab:project/view/2727/|Kanban]] (Product-Infrastructure-Team-Backlog) * [[phab:project/view/4301/|Kanban]] (Inuka-Team) * [[phab:project/view/2774/|Kanban]] (cloud-services-team) * [[phab:project/view/4320/|Kanban]] (Product-Analytics) * [[phab:project/view/5880/|Kanban]] (Moderator-Tools-Team) * [[phab:project/view/5375/|Kanban]] (Trust and Safety Tools Team Backlog) * [[phab:project/view/4651/|Kanban Board]] (Design-Innovation-Team) * Kanbanana ** [[phab:project/view/6008/|Kanbanana-2022-23-Q1]] (Readers-Web-Backlog) * [[phab:project/view/1692/|Kartographer]] (Maps) * [[phab:project/view/1829/|Kartotherian]] (Maps) * [[phab:project/view/4810/|Language]] (KaiOS-Wikipedia-app) ** [[phab:project/view/4647/|Language-2020-Focus-Sprint]] (Language-Team) ** [[phab:project/view/5835/|Language-2022-April-June]] (Language-Team) ** [[phab:project/view/6009/|Language-2022-July-September]] (Language-Team) * [[phab:project/view/5566/|Lead Nurturing 2021 pilot 2]] (WMDE-New-Editors-Banner-Campaigns) * [[phab:project/view/2484/|Location Search]] (Reading Epics) * Machine ** [[phab:project/view/4109/|Machine-vision-depicts]] (SDC-Statements) * [[phab:project/view/2952/|Maintainer needed]] (Toolforge-standards-committee) * Map ** [[phab:project/view/1633/|Map-Styles]] (Maps) * [[phab:project/view/4527/|Maps in infoboxes]] (WMSE-Development-Support-2020) * Maps ** [[phab:project/view/2054/|Maps-data]] (Maps) * [[phab:project/view/4200/|MCR]] (Platform Team Initiatives) * [[phab:project/view/4217/|MCR Schema Migration]] (Platform Team Initiatives) * MediaSearch ** [[phab:project/view/4900/|MediaSearch-Alpha]] (SDAW-MediaSearch) ** [[phab:project/view/4901/|MediaSearch-Beta]] (SDAW-MediaSearch) ** [[phab:project/view/5187/|MediaSearch-ConceptChips]] (SDAW-MediaSearch) ** [[phab:project/view/5186/|MediaSearch-ImageRecs]] (SDAW-MediaSearch) ** [[phab:project/view/4902/|MediaSearch-ReleaseCandidate]] (SDAW-MediaSearch) ** [[phab:project/view/5014/|MediaSearch-ReleaseCandidate2]] (SDAW-MediaSearch) * MediaWiki ** [[phab:project/view/2743/|MediaWiki-MultiDC]] (Sustainability) * [[phab:project/view/4947/|mediawiki.widgets]] (MediaWiki-Interface) * [[phab:project/view/5769/|Menus 2.0]] (MediaWiki-Core-Skin-Architecture) * Metrics ** [[phab:project/view/5335/|Metrics-Platform-Epic-Roadmap]] (Metrics-Platform) ** [[phab:project/view/5336/|Metrics-Platform-MVP-Release-1]] (Metrics-Platform) * [[phab:project/view/5558/|Misc]] (GitLab) * [[phab:project/view/2467/|Mobile Web SSR and Connection Management]] (Reading Epics) * Mobile ** [[phab:project/view/4737/|Mobile-Prototype]] (Wikipedia-Preview) * [[phab:project/view/5654/|MobileFrontend (Editor)]] (MobileFrontend) * [[phab:project/view/3707/|MobileFrontend Special Pages]] (MobileFrontend) * [[phab:project/view/4195/|Modern Event Platform (TEC2)]] (Platform Team Initiatives) * Multi ** [[phab:project/view/4202/|Multi-DC (TEC1)]] (Platform Team Initiatives) * [[phab:project/view/4658/|MVP]] (KaiOS-Wikipedia-app) * [[phab:project/view/5698/|MVP]] (Wikistories) * [[phab:project/view/5144/|MW Expedition]] (Platform Team Workboards) * [[phab:project/view/4219/|MW REST API in PHP]] (Platform Team Initiatives) * [[phab:project/view/5154/|mw.notifications]] (MediaWiki-Interface) * [[phab:project/view/3601/|Narva Muuseum]] (WMEE Sum of all paintings) * [[phab:project/view/5483/|Needs Prioritization (Tech)]] (Readers-Web-Backlog) * [[phab:project/view/4549/|New Discussion 1.0]] (OWC2020) * [[phab:project/view/3678/|New Features]] (Multi-Content-Revisions) * [[phab:project/view/2464/|New Feed Content]] (Reading Epics) * [[phab:project/view/4623/|New Hook System]] (Platform Team Initiatives) * [[phab:project/view/5322/|Next]] (Release-Engineering-Team) * [[phab:project/view/4786/|Next Release]] (KaiOS-Wikipedia-app) * Oct ** [[phab:project/view/5989/|Oct-Dec 2022]] (Developer-Advocacy) ** [[phab:project/view/6036/|Oct-Dec-2022]] (CommRel-Specialists-Support) * [[phab:project/view/5478/|Okapi Wikimedia Enterprise]] (Wikimedia Enterprise) * [[phab:project/view/5631/|Onboarding 🚀]] (Release-Engineering-Team) * OOUI ** [[phab:project/view/4667/|OOUI-0.38.0]] (OOUI) ** [[phab:project/view/5677/|OOUI-0.43.0]] (OOUI) ** [[phab:project/view/5956/|OOUI-0.44.1]] (OOUI) * [[phab:project/view/4811/|Optimize]] (KaiOS-Wikipedia-app) * other ** [[phab:project/view/4255/|other-input-types-on-a-dirigible]] (SDC-Statements) * Other ** [[phab:project/view/3940/|Other-statements-running]] (SDC-Statements) * [[phab:project/view/4402/|Outreachy Interns]] (Platform Team Workboards) * Overhaul ** [[phab:project/view/4939/|Overhaul-2020]] (AbuseFilter) * [[phab:project/view/4547/|OWC2020 Replying 1.0]] (OWC2020) * [[phab:project/view/4546/|OWC2020 Replying 2.0]] (OWC2020) * [[phab:project/view/2468/|Page Previews]] (Reading Epics) * [[phab:project/view/4207/|Parsoid REST API in PHP (CDP2)]] (Platform Team Initiatives) * [[phab:project/view/4808/|Partnerships]] (The-Wikipedia-Library) * [[phab:project/view/4682/|Passed QA]] (RW-Feature-DI-Opt-out-Toggle) * [[phab:project/view/5562/|Peter's world]] (Editing-team) * phabricator ** [[phab:project/view/5278/|phabricator-next]] (Phabricator) * Phase 0 ** [[phab:project/view/5533/|Phase 0 - Parsoid-Media-Structure]] (Parsoid-Read-Views) * Phase 1 ** [[phab:project/view/5534/|Phase 1 - DiscussionTools support]] (Parsoid-Read-Views) * Phase 2 ** [[phab:project/view/5535/|Phase 2 - testwiki Main namespace support]] (Parsoid-Read-Views) * Phase 3 ** [[phab:project/view/5536/|Phase 3 - Main namespace of officewiki / mediawiki.org renders with Parsoid]] (Parsoid-Read-Views) * Phase 4 ** [[phab:project/view/5537/|Phase 4 - Parsoid generates metadata needed by core]] (Parsoid-Read-Views) * [[phab:project/view/4961/|Phase θ – Throttling]] (Abstract Wikipedia team) * [[phab:project/view/4962/|Phase ι – Documentation]] (Abstract Wikipedia team) * Phase κ – Clean ** [[phab:project/view/4963/|Phase κ – Clean-up]] (Abstract Wikipedia team) * [[phab:project/view/4964/|Phase λ – Launch]] (Abstract Wikipedia team) * [[phab:project/view/5268/|Platform Engineering Reliability]] (Platform Team Workboards) * [[phab:project/view/2462/|Platform JS CSS and HTML consolidation]] (Reading Epics) * Platform ** [[phab:project/view/4913/|Platform-Product Roadmap]] (Platform Team Workboards) * [[phab:project/view/5585/|Priority Backlog 📥]] (Release-Engineering-Team) * [[phab:project/view/5377/|Product Roadmap]] (API Platform) * [[phab:project/view/5600/|Product Roadmap]] (Generated Data Platform) * [[phab:project/view/2248/|Production release]] (FileAnnotations) * [[phab:project/view/5552/|Project Migration]] (GitLab) * [[phab:project/view/2700/|Project Setup]] (Push-Notification-Service) * [[phab:project/view/5784/|Project start bot]] (WMSE-Organisational-Development-2022) * Project ** [[phab:project/view/2875/|Project-requests]] (Cloud-VPS) * [[phab:project/view/2475/|Push Notifications]] (Reading Epics) * [[phab:project/view/3599/|Pärnu Muuseum]] (WMEE Sum of all paintings) * Quota ** [[phab:project/view/2880/|Quota-requests]] (Cloud-VPS) ** [[phab:project/view/4481/|Quota-requests]] (Data-Services) ** [[phab:project/view/4834/|Quota-requests]] (Toolforge) * [[phab:project/view/5988/|R2]] (Wikistories) * [[phab:project/view/2923/|Radar]] (Performance-Team) * [[phab:project/view/5320/|Radar]] (Release-Engineering-Team) * [[phab:project/view/3679/|Reactive]] (Multi-Content-Revisions) * [[phab:project/view/2943/|Rename]] (Wiki-Setup) * [[phab:project/view/4907/|Reply Tool Opt Out]] (OWC2020) * [[phab:project/view/3417/|Reportings]] (WMDE-New-Editors-Banner-Campaigns) * [[phab:project/view/5173/|Responsive]] (MonoBook) * [[phab:project/view/4211/|Revision Storage Schema Improvements]] (Platform Team Initiatives) * [[phab:project/view/5507/|Round 23]] (Outreachy) * [[phab:project/view/5717/|Round 24]] (Outreachy) * RW ** [[phab:project/view/2297/|RW-Design-Debt]] (Design) ** [[phab:project/view/2296/|RW-Tech-Debt]] (Technical-Debt) ** [[phab:project/view/3912/|RW-Test-Cases]] (Product-QA) * [[phab:project/view/4157/|S&F Workboard]] (Platform Team Workboards) * S1 ** [[phab:project/view/5632/|S1-2022]] (Wikimedia-Small-Projects-User-Group-Milestone) * Scap3 ** [[phab:project/view/1823/|Scap3-MediaWiki-MVP]] (Scap) * [[phab:project/view/2523/|Search]] (Phabricator) * [[phab:project/view/5323/|Seen]] (Release-Engineering-Team) * [[phab:project/view/4194/|Session Management Service (CDP2)]] (Platform Team Initiatives) * [[phab:project/view/3978/|Software install/update]] (Toolforge) * [[phab:project/view/4380/|Sprint]] (Wikispeech-Jobrunner) * [[phab:project/view/4871/|Sprint 0]] (Platform Team Sprints Board) * [[phab:project/view/6061/|Sprint 00]] (Data Pipelines) * [[phab:project/view/6056/|Sprint 02]] (Data Engineering Planning) * [[phab:project/view/4903/|Sprint 1]] (Platform Team Sprints Board) * [[phab:project/view/6060/|Sprint 11]] (Wikibase Product Platform) * [[phab:project/view/4938/|Sprint 2]] (Platform Team Sprints Board) * [[phab:project/view/4966/|Sprint 3]] (Platform Team Sprints Board) * [[phab:project/view/4986/|Sprint 4]] (Platform Team Sprints Board) * [[phab:project/view/5015/|Sprint 5]] (Platform Team Sprints Board) * Sprint 7/28 ** [[phab:project/view/5438/|Sprint 7/28-8/10 2021]] (User-jeena) * Sprint 8/18 ** [[phab:project/view/5493/|Sprint 8/18-8/31 2021]] (User-jeena) * Sprint ** [[phab:project/view/6017/|Sprint-♾]] (Wikidata Dev Team) * Statement ** [[phab:project/view/3987/|Statement-and-keyword-search-power-walking]] (SDC-Statements) * [[phab:project/view/5551/|Support]] (GitLab) * [[phab:project/view/2483/|Synchronized Reading Lists]] (Reading Epics) * [[phab:project/view/4906/|Tables]] (MediaWiki-Interface) * [[phab:project/view/3597/|TARTMUS]] (WMEE Sum of all paintings) * [[phab:project/view/3600/|Tartu Linnamuuseum]] (WMEE Sum of all paintings) * [[phab:project/view/3604/|Tartu Ülikoli kunstimuuseum]] (WMEE Sum of all paintings) * [[phab:project/view/3603/|Tartu Ülikoli muuseum]] (WMEE Sum of all paintings) * [[phab:project/view/5612/|Team A Hearth 🏰🔥]] (Wikidata-Campsite) * [[phab:project/view/3677/|Tech Debt]] (Multi-Content-Revisions) * Temporary ** [[phab:project/view/2414/|Temporary-UserRights]] (Stewards-and-global-tools) * [[phab:project/view/6022/|The Decommission Mission 💀]] (Release-Engineering-Team) * Third ** [[phab:project/view/5206/|Third-party]] (Editing-team) ** [[phab:project/view/5100/|Third-party]] (Parsoid) * [[phab:project/view/2482/|Thumbnails]] (Reading Epics) * [[phab:project/view/1830/|Tilerator]] (Maps) * [[phab:project/view/3975/|Tools to be deleted]] (Toolforge) * [[phab:project/view/4905/|Tracking]] (MobileFrontend) * [[phab:project/view/5172/|Tracking]] (Modern) * [[phab:project/view/5174/|Tracking]] (MonoBook) * [[phab:project/view/5175/|Tracking]] (CologneBlue) * [[phab:project/view/3769/|Tracking]] (Page-Previews) * [[phab:project/view/4541/|Tracking]] (Editing-team) * [[phab:project/view/3297/|Tracking]] (MinervaNeue) * [[phab:project/view/5099/|Tracking]] (Parsoid) * [[phab:project/view/2476/|Trending Edits]] (Reading Epics) * UI ** [[phab:project/view/4192/|UI-consolidation-on-a-Ferris-wheel]] (SDC-Statements) * [[phab:project/view/6/|Upstream]] (Phabricator) * [[phab:project/view/5671/|v0.0.1]] (Web2Cit-Core) * [[phab:project/view/5667/|v3.0]] (InternetArchiveBot) * [[phab:project/view/4496/|Vector (Tracking)]] (Vector) * [[phab:project/view/3602/|Võrumaa Museum]] (WMEE Sum of all paintings) * [[phab:project/view/4506/|Wiki Loves Earth 2020]] (WMSE-Wiki-Loves-2020) * [[phab:project/view/4505/|Wiki Loves Monuments 2020]] (WMSE-Wiki-Loves-2020) * [[phab:project/view/5761/|Wikibase Suite Maintenance Releases Feb 2022]] (Wikibase Suite) * [[phab:project/view/6043/|Wikibase.cloud (WB Cloud Sprint 1)]] (Wikibase.cloud) * [[phab:project/view/2472/|Wikidata Description Editing]] (Reading Epics) * [[phab:project/view/2471/|Wikidata Description Editing ORES Abuse Filter]] (Reading Epics) * WMDE ** [[phab:project/view/3114/|WMDE-Design-Workboard Doing]] (WMDE-Design) * WMF ** [[phab:project/view/4742/|WMF-deployed Build Failure]] (ci-test-error) * WMSE ** [[phab:project/view/5990/|WMSE-Nordic-Museum-2022]] (WMSE-GLAM-2022) * [[phab:project/view/2759/|Workflow Improvements]] (MediaWiki-Releasing) * [[phab:project/view/5319/|Yak Shaving 🐃🪒]] (Release-Engineering-Team) * [[phab:project/view/5819/|Zynatic]] (WMSE-Association-Involvement-2022) * [[phab:project/view/5861/|🌱 Spring Cleaning — April 2022]] (Release-Engineering-Team) === Releases === * Gadgets ** [[phab:project/view/1634/|Gadgets-2.0]] * iOS ** [[phab:project/view/5997/|iOS-app-v6.9.3]] * ios ** [[phab:project/view/5380/|ios-app-v7.0]] * MediaWiki ** [[phab:project/view/2239/|MediaWiki-backport-deployments]] * MW ** [[phab:project/view/4306/|MW-1.35-notes]] ** [[phab:project/view/4035/|MW-1.35-release]] ** [[phab:project/view/5296/|MW-1.37-notes]] ** [[phab:project/view/4928/|MW-1.37-release]] ** [[phab:project/view/5539/|MW-1.38-notes]] ** [[phab:project/view/5407/|MW-1.38-release]] ** [[phab:project/view/5796/|MW-1.39-notes]] ** [[phab:project/view/5694/|MW-1.39-release]] ** [[phab:project/view/6047/|MW-1.40-notes]] * [[phab:project/view/1333/|Release]] === Sprints === * Abstract Wikipedia Fix ** [[phab:project/view/5712/|Abstract Wikipedia Fix-It tasks]] * CommTech ** [[phab:project/view/5906/|CommTech-Hackathon-AKA-CodeJam-2022]] * Data ** [[phab:project/view/5504/|Data-Quality-Days-2021]] * Discovery ** [[phab:project/view/1235/|Discovery-Portal-Sprint]] * [[phab:project/view/1230/|Elections]] * [[phab:project/view/6019/|Fundraising Sprint Machine Unlearning]] * [[phab:project/view/4797/|itWikiCon]] ** [[phab:project/view/4798/|itWikiCon-2020]] ** [[phab:project/view/5790/|itWikiCon-2022]] * [[phab:project/view/4970/|Platform Engineering Roadmap]] * Programs ** [[phab:project/view/1786/|Programs-and-Events-Dashboard-Sprint 2]] * UI ** [[phab:project/view/1806/|UI-Standardization-Kanban]] * Wikimania ** [[phab:project/view/6030/|Wikimania-Hackathon-2022]] * Wikimedia ** [[phab:project/view/5802/|Wikimedia-Hackathon-2022]] ** [[phab:project/view/5626/|Wikimedia-Small-Projects-User-Group-Milestone]] * WMDE ** [[phab:project/view/6001/|WMDE-FUN-Sprint-2022-06-27]] ** [[phab:project/view/6025/|WMDE-FUN-Sprint-2022-07-11]] ** [[phab:project/view/6057/|WMDE-FUN-Sprint-2022-07-25]] ** [[phab:project/view/6039/|WMDE-TechWish-Sprint-2022-07-20]] ** [[phab:project/view/3106/|WMDE-UX-Workboard]] * WMF ** [[phab:project/view/6023/|WMF-Inspiration-Week-2022-ML-Collab]] === User projects === * User ** [[phab:project/view/2688/|User-Abbe98]] ** [[phab:project/view/3908/|User-abi_]] ** [[phab:project/view/5822/|User-AKlapper]] ** [[phab:project/view/2518/|User-Alicia_Fagerving_WMSE]] ** [[phab:project/view/3418/|User-Amire80]] ** [[phab:project/view/4580/|User-ANEUN]] ** [[phab:project/view/4396/|User-Apap04]] ** [[phab:project/view/2995/|User-ArielGlenn]] ** [[phab:project/view/2776/|User-aude]] ** [[phab:project/view/4464/|User-awight]] ** [[phab:project/view/2516/|User-AxelPettersson_WMSE]] ** [[phab:project/view/929/|User-bd808]] ** [[phab:project/view/5418/|User-Bongo-Cat]] ** [[phab:project/view/4463/|User-brennen]] ** [[phab:project/view/5317/|User-Carn]] ** [[phab:project/view/4196/|User-CCicaleseWMF]] ** [[phab:project/view/3734/|User-CDanis]] ** [[phab:project/view/4198/|User-Cicalese]] ** [[phab:project/view/3381/|User-Cirdan]] ** [[phab:project/view/3588/|User-Daimona]] ** [[phab:project/view/4859/|User-dancy]] ** [[phab:project/view/2384/|User-Daniel]] ** [[phab:project/view/3849/|User-DannyS712]] ** [[phab:project/view/5584/|User-dcaro]] ** [[phab:project/view/5779/|User-dduvall]] ** [[phab:project/view/2187/|User-Dereckson]] ** [[phab:project/view/4377/|User-Dyolf77]] ** [[phab:project/view/3865/|User-EBernhardson]] ** [[phab:project/view/3075/|User-Eevans]] ** [[phab:project/view/2398/|User-Elukey]] ** [[phab:project/view/5932/|User-EpicPupper]] ** [[phab:project/view/2517/|User-Eric_Luth_WMSE]] ** [[phab:project/view/4556/|User-Etonkovidova]] ** [[phab:project/view/5970/|User-EUdoh-WMF]] ** [[phab:project/view/2668/|User-fgiunchedi]] ** [[phab:project/view/3866/|User-fsero]] ** [[phab:project/view/4764/|User-gabrielchl]] ** [[phab:project/view/2895/|User-GoranSMilovanovic]] ** [[phab:project/view/1436/|User-greg]] ** [[phab:project/view/4345/|User-HannaLindgren]] ** [[phab:project/view/4003/|User-Harej]] ** [[phab:project/view/3429/|User-herron]] ** [[phab:project/view/2962/|User-Huji]] ** [[phab:project/view/2077/|User-Hydriz]] ** [[phab:project/view/5508/|User-IN]] ** [[phab:project/view/5221/|User-Inductiveload]] ** [[phab:project/view/5804/|User-ItamarWMDE]] ** [[phab:project/view/3076/|User-Jayprakash12345]] ** [[phab:project/view/4357/|User-jbond]] ** [[phab:project/view/2985/|User-Jdlrobson]] ** [[phab:project/view/2563/|User-JeanFred]] ** [[phab:project/view/5436/|User-jeena]] ** [[phab:project/view/4748/|User-Jenny_Brandt_WMSE]] ** [[phab:project/view/3091/|User-Jhernandez]] ** [[phab:project/view/3572/|User-jijiki]] ** [[phab:project/view/2271/|User-Joe]] ** [[phab:project/view/1763/|User-Johan]] ** [[phab:project/view/2542/|User-John_Cummings]] ** [[phab:project/view/2512/|User-Jopparn]] ** [[phab:project/view/4531/|User-JosefineHellrothLarssonWMSE]] ** [[phab:project/view/1724/|User-Josve05a]] ** [[phab:project/view/4925/|User-Jpita]] ** [[phab:project/view/2566/|User-JSeddon]] ** [[phab:project/view/5599/|User-Juan90264]] ** [[phab:project/view/4552/|User-kalle]] ** [[phab:project/view/2946/|User-KartikMistry]] ** [[phab:project/view/3077/|User-Kizule]] ** [[phab:project/view/4854/|User-Kormat]] ** [[phab:project/view/3735/|User-kostajh]] ** [[phab:project/view/3778/|User-kzimmerman]] ** [[phab:project/view/2451/|User-LokalProfil]] ** [[phab:project/view/5358/|User-LSobanski]] ** [[phab:project/view/1765/|User-Luke081515]] ** [[phab:project/view/3069/|User-MacFan4000]] ** [[phab:project/view/2877/|User-MarcoAurelio]] ** [[phab:project/view/4583/|User-Maria_Burehall_WMSE]] ** [[phab:project/view/3490/|User-Marostegui]] ** [[phab:project/view/2896/|User-Matthewrbowker]] ** [[phab:project/view/3378/|User-MatthiasGeisler]] ** [[phab:project/view/2079/|User-MBinder_WMF]] ** [[phab:project/view/3749/|User-Michael]] ** [[phab:project/view/3579/|User-MModell]] ** [[phab:project/view/4779/|User-MoritzMuehlenhoff]] ** [[phab:project/view/2223/|User-MuhammadShuaib]] ** [[phab:project/view/2222/|User-Nikerabbit]] ** [[phab:project/view/3861/|User-Noarave]] ** [[phab:project/view/3272/|User-Physikerwelt]] ** [[phab:project/view/4374/|User-PPham]] ** [[phab:project/view/4741/|User-QEDK]] ** [[phab:project/view/5676/|User-Raymond_Ndibe]] ** [[phab:project/view/1725/|User-Reedy]] ** [[phab:project/view/3138/|User-revi]] ** [[phab:project/view/4159/|User-RhinosF1]] ** [[phab:project/view/3508/|User-Rxy]] ** [[phab:project/view/2433/|User-Ryasmeen]] ** [[phab:project/view/5288/|User-Salgo60]] ** [[phab:project/view/5973/|User-Sandra_Fauconnier_WMSE]] ** [[phab:project/view/2515/|User-SaraMortsell]] * user ** [[phab:project/view/3979/|user-sbassett]] * User ** [[phab:project/view/2511/|User-Sebastian_Berlin-WMSE]] ** [[phab:project/view/5658/|User-Slst2020]] ** [[phab:project/view/2921/|User-Smalyshev]] ** [[phab:project/view/4833/|User-Soham]] ** [[phab:project/view/4392/|User-srishakatux]] ** [[phab:project/view/5601/|User-STei-WMF]] ** [[phab:project/view/4302/|User-SwedishMuseum]] ** [[phab:project/view/3341/|User-TArrow]] ** [[phab:project/view/2728/|User-Tgr]] ** [[phab:project/view/3770/|User-TheDJ]] ** [[phab:project/view/2539/|User-TheresNoTime]] ** [[phab:project/view/4289/|User-TheSandDoctor]] ** [[phab:project/view/3107/|User-thiemowmde]] ** [[phab:project/view/5720/|User-Tks4Fish]] ** [[phab:project/view/2196/|User-Tobi_WMDE_SW]] ** [[phab:project/view/4017/|User-Tore_Danielsson_WMSE]] ** [[phab:project/view/2098/|User-Urbanecm]] ** [[phab:project/view/4943/|User-Urbanecm_WMF]] ** [[phab:project/view/4832/|User-Vidhi-Mody]] ** [[phab:project/view/4183/|User-WDoran]] ** [[phab:project/view/2658/|User-WMDE-leszek]] ** [[phab:project/view/3525/|User-xSavitar]] ** [[phab:project/view/1938/|User-zeljkofilipin]] ** [[phab:project/view/2745/|User-Zppix]] === Miscellaneous === * Continuous ** [[phab:project/view/1208/|Continuous-Integration-Config]] * Patch ** [[phab:project/view/32/|Patch-For-Review]] * [[phab:project/view/89/|Trash]] {{/Footer}} 5b7qgv3faqgte3wu8vjymotzhonihq7 5387366 5386454 2022-07-28T22:11:34Z Crystal-bot 5243179 Bot: Updating project taxonomy wikitext text/x-wiki {{/Header}} Data as of: 22:11, 28 July 2022 (UTC) === Projects === * [[phab:project/view/5930/|2022 Wikimedia Google.org Fellowship]] * [[phab:project/view/1929/|3D]] * [[phab:project/view/3147/|3D2Commons]] * [[phab:project/view/5054/|Abstract Wikipedia UX]] * [[phab:project/view/217/|AbuseFilter]] * Accuracy ** [[phab:project/view/1994/|Accuracy-Review-of-Wikipedias]] * Acme ** [[phab:project/view/3694/|Acme-chief]] * [[phab:project/view/651/|ActiveAbstract]] * Add ** [[phab:project/view/5045/|Add-Link]] * address ** [[phab:project/view/4382/|address-knowledge-gaps]] * [[phab:project/view/3755/|Advanced Mobile Contributions]] * Advanced ** [[phab:project/view/2798/|Advanced-Search]] * [[phab:project/view/1295/|AhoCorasick]] * AHT ** [[phab:project/view/5313/|AHT-Roadmap]] * [[phab:project/view/527/|AJAXPoll]] * [[phab:project/view/11/|Analytics]] ** [[phab:project/view/655/|Analytics-Clusters]] ** [[phab:project/view/817/|Analytics-Dashiki]] ** [[phab:project/view/2886/|Analytics-Data-Quality]] ** [[phab:project/view/3711/|Analytics-Jupyter]] ** [[phab:project/view/3153/|Analytics-Legal]] ** [[phab:project/view/4824/|Analytics-Radar]] ** [[phab:project/view/206/|Analytics-Wikistats]] * [[phab:project/view/2255/|Android Design]] * Android ** [[phab:project/view/2824/|Android-app-feature-Compilations-v1]] ** [[phab:project/view/2237/|Android-app-feature-Description-Editing]] * [[phab:project/view/3826/|Anisa]] * [[phab:project/view/257/|AntiSpoof]] * [[phab:project/view/941/|Apex]] * [[phab:project/view/5376/|API Platform]] * API ** [[phab:project/view/5046/|API-Portal]] * [[phab:project/view/842/|ApiFeatureUsage]] * [[phab:project/view/4465/|Application Security Reviews]] * Arc ** [[phab:project/view/4222/|Arc-Lamp]] * Article ** [[phab:project/view/1351/|Article-Recommendation]] ** [[phab:project/view/2749/|Article-Reminder-Notifications]] * [[phab:project/view/481/|ArticleFeedbackv5]] * [[phab:project/view/1416/|ArticlePlaceholder]] * articlequality ** [[phab:project/view/1675/|articlequality-modeling]] * [[phab:project/view/1948/|ArticleRatings]] * [[phab:project/view/4724/|Articles Needing links]] * at ** [[phab:project/view/1304/|at-ease]] ** [[phab:project/view/5890/|Authentication-Experiments-2022]] * [[phab:project/view/5713/|Auto schema]] * [[phab:project/view/2294/|Automated list generation]] * [[phab:project/view/1012/|AutoWikiBrowser]] * AvoinGLAM ** [[phab:project/view/4190/|AvoinGLAM-Saami]] * [[phab:project/view/5371/|bacula]] * Bad ** [[phab:project/view/1470/|Bad-Words-Detection-System]] * [[phab:project/view/3372/|base_convert]] * Beta ** [[phab:project/view/497/|Beta-Cluster-Infrastructure]] * [[phab:project/view/741/|BetaFeatures]] * [[phab:project/view/1250/|BiblioPlus]] * [[phab:project/view/676/|BlogPage]] * [[phab:project/view/1092/|BlueSky]] * Book ** [[phab:project/view/4256/|Book-Referencing]] * Bot ** [[phab:project/view/2746/|Bot-Frameworks]] * [[phab:project/view/2258/|Bouquet]] * [[phab:project/view/5662/|CampaignEvents]] * [[phab:project/view/1976/|Cassandra]] * [[phab:project/view/1808/|CatWatch]] * CFSSL ** [[phab:project/view/5338/|CFSSL-PKI]] * [[phab:project/view/2264/|Challenge]] * [[phab:project/view/2114/|ChangeProp]] * [[phab:project/view/185/|CharInsert]] * [[phab:project/view/203/|CheckUser]] * [[phab:project/view/4398/|ChessBrowser]] * [[phab:project/view/209/|CirrusSearch]] * [[phab:project/view/172/|Cite]] ** [[phab:project/view/4050/|Cite-Unseen]] * [[phab:project/view/980/|CiteThisPage]] * [[phab:project/view/62/|Citoid]] * [[phab:project/view/5263/|Cloud Services Proposals]] * Cloud ** [[phab:project/view/474/|Cloud-VPS]] * Code ** [[phab:project/view/3672/|Code-Health-First-Responder]] ** [[phab:project/view/3779/|Code-Health-Newsletter]] * [[phab:project/view/580/|CodeEditor]] * [[phab:project/view/5587/|Codex]] * [[phab:project/view/2320/|Cognate]] * Collab ** [[phab:project/view/1922/|Collab-Notifications-Page]] ** [[phab:project/view/1691/|Collaboration-Community-Engagement]] * [[phab:project/view/329/|Collection]] * [[phab:project/view/322/|CologneBlue]] * commit ** [[phab:project/view/2163/|commit-message-validator]] * [[phab:project/view/4829/|CommonPasswords]] * [[phab:project/view/5429/|Commons Deletion Notification bot]] * Commons ** [[phab:project/view/1986/|Commons-Datasets]] ** [[phab:project/view/3166/|Commons-Mass-Description]] ** [[phab:project/view/3616/|Commons-Twitter-Bot]] * [[phab:project/view/736/|CommonsMetadata]] * CommRel ** [[phab:project/view/3456/|CommRel-Documentation]] ** [[phab:project/view/3451/|CommRel-Specialists-Support]] * Community ** [[phab:project/view/973/|Community-IdeaLab]] * community ** [[phab:project/view/2348/|community-labs-monitoring]] * Community ** [[phab:project/view/978/|Community-LearningPatterns]] * [[phab:project/view/3862/|Confirmation prompt for rollback action]] * [[phab:project/view/225/|ConfirmEdit (CAPTCHA extension)]] * [[phab:project/view/4218/|conftool]] * [[phab:project/view/776/|ContentTranslation]] * Continuous ** [[phab:project/view/401/|Continuous-Integration-Infrastructure]] * [[phab:project/view/388/|ContributionScores]] * Convenient ** [[phab:project/view/3851/|Convenient-Discussions]] * [[phab:project/view/1638/|CopyPatrol]] * [[phab:project/view/5017/|Cosmos]] * [[phab:project/view/5841/|CoverMe]] * COVID ** [[phab:project/view/4721/|COVID-19 Global Dashboard]] ** [[phab:project/view/4676/|COVID-19-Graphics]] * [[phab:project/view/5309/|CreateAPage]] * [[phab:project/view/1224/|crosswatch]] * css ** [[phab:project/view/2598/|css-sanitizer]] * CX ** [[phab:project/view/3437/|CX-analytics]] ** [[phab:project/view/4191/|CX-boost]] ** [[phab:project/view/3435/|CX-cxserver]] ** [[phab:project/view/3421/|CX-deployments]] ** [[phab:project/view/3434/|CX-mobile]] ** [[phab:project/view/3419/|CX-out-of-beta]] ** [[phab:project/view/3457/|CX-template-improvements]] ** [[phab:project/view/3420/|CX-TranslationList]] * [[phab:project/view/2669/|Cyberbot]] * [[phab:project/view/4006/|DarkMode]] * [[phab:project/view/6010/|Data Engineering Planning]] * [[phab:project/view/5616/|Data Pipelines]] * [[phab:project/view/4422/|Data Protection]] * Data ** [[phab:project/view/5697/|Data-Catalog]] ** [[phab:project/view/5996/|Data-Engineering-Operations]] ** [[phab:project/view/4997/|Data-Persistence-Backup]] ** [[phab:project/view/5006/|Data-Persistence-Misc]] ** [[phab:project/view/1393/|Data-release]] ** [[phab:project/view/2874/|Data-Services]] * database ** [[phab:project/view/5372/|database-backups]] * Datasets ** [[phab:project/view/1135/|Datasets-Archiving]] ** [[phab:project/view/189/|Datasets-General-or-Unknown]] ** [[phab:project/view/191/|Datasets-Webstatscollector]] * [[phab:project/view/123/|DataTypes]] * [[phab:project/view/122/|DataValues]] ** [[phab:project/view/924/|DataValues-JavaScript]] * [[phab:project/view/5304/|Data³]] * dbbackups ** [[phab:project/view/5291/|dbbackups-dashboard]] * decommission ** [[phab:project/view/3364/|decommission-hardware]] * Dependency ** [[phab:project/view/3502/|Dependency-Tracking]] * [[phab:project/view/349/|Deployments]] * [[phab:project/view/2259/|DeskMessMirrored]] * [[phab:project/view/4281/|Desktop Improvements]] * dev ** [[phab:project/view/4032/|dev-images]] * [[phab:project/view/5853/|DicoAdo.org]] * Diff ** [[phab:project/view/328/|Diff-blog]] * [[phab:project/view/53/|Diffusion]] * [[phab:project/view/4358/|DiscussionTools]] * [[phab:project/view/266/|DismissableSiteNotice]] * [[phab:project/view/154/|DNS]] * Docker ** [[phab:project/view/3094/|Docker-Hub-MediaWiki]] * docker ** [[phab:project/view/3161/|docker-pkg]] * Documentation ** [[phab:project/view/5093/|Documentation-Review-Board]] * [[phab:project/view/1040/|Domains]] * [[phab:project/view/3499/|donate.wikimedia.org]] * [[phab:project/view/4400/|Doxygen]] * draftquality ** [[phab:project/view/2369/|draftquality-modeling]] * drafttopic ** [[phab:project/view/3086/|drafttopic-modeling]] * DSE ** [[phab:project/view/5959/|DSE-Kubernetes-Cluster]] * Dumps ** [[phab:project/view/1519/|Dumps-Generation]] ** [[phab:project/view/1729/|Dumps-Rewrite]] * [[phab:project/view/2260/|Dusk]] * [[phab:project/view/2261/|DuskToDawn]] * DynamicPageList (third ** [[phab:project/view/246/|DynamicPageList (third-party)]] * [[phab:project/view/201/|DynamicPageList (Wikimedia)]] * [[phab:project/view/140/|EasyTimeline]] * Edit ** [[phab:project/view/2040/|Edit-Review-Improvements]] ** [[phab:project/view/2721/|Edit-Review-Improvements-Integrated-Filters]] ** [[phab:project/view/2201/|Edit-Review-Improvements-RC-Page]] ** [[phab:project/view/4796/|Editing-Team-Request]] * editquality ** [[phab:project/view/1673/|editquality-modeling]] * edittypes ** [[phab:project/view/1674/|edittypes-modeling]] * Education ** [[phab:project/view/1052/|Education-Program-Dashboard]] * [[phab:project/view/77/|Elasticsearch]] * Electron ** [[phab:project/view/2162/|Electron-PDFs]] * [[phab:project/view/5184/|envoy]] * Equity ** [[phab:project/view/5828/|Equity-Landscape]] * [[phab:project/view/3068/|Equivset]] * [[phab:project/view/4432/|ERM]] * Europeana ** [[phab:project/view/1580/|Europeana-280]] * [[phab:project/view/3543/|Event Metrics]] * Event ** [[phab:project/view/1474/|Event-Platform]] * [[phab:project/view/789/|EventStreams]] * [[phab:project/view/2783/|Example (skin)]] * [[phab:project/view/3708/|Excimer]] * Expiring ** [[phab:project/view/1995/|Expiring-Watchlist-Items]] * [[phab:project/view/336/|ExtensionDistributor]] * [[phab:project/view/2603/|ExternalArticles]] * [[phab:project/view/3780/|ExternalGuidance]] * [[phab:project/view/3673/|FactGrid]] * [[phab:project/view/810/|FanBoxes]] * [[phab:project/view/2120/|FileAnnotations]] * Fix ** [[phab:project/view/5519/|Fix-Suggester-Bot]] * [[phab:project/view/3570/|fixcopyright.wikimedia.org]] * [[phab:project/view/1496/|FormWizard]] ** [[phab:project/view/3568/|FormWizard-Gadget]] * [[phab:project/view/3501/|foundation.wikimedia.org]] * [[phab:project/view/5489/|Foundational Technology Requests]] * [[phab:project/view/3093/|Fountain]] * FR ** [[phab:project/view/1895/|FR-ActiveMQ]] ** [[phab:project/view/1602/|FR-Adyen]] ** [[phab:project/view/6035/|FR-Alerts]] ** [[phab:project/view/1600/|FR-Amazon]] ** [[phab:project/view/5239/|FR-Australia]] ** [[phab:project/view/4660/|FR-AutoTY-Email]] ** [[phab:project/view/5273/|FR-BigBundle]] ** [[phab:project/view/5754/|FR-Braintree-Integration]] ** [[phab:project/view/5829/|FR-Brazil]] ** [[phab:project/view/5236/|FR-Canada]] * Fr ** [[phab:project/view/3546/|Fr-CentralNotice-Caching]] ** [[phab:project/view/3233/|Fr-CentralNotice-Translation-Bugs]] ** [[phab:project/view/3545/|Fr-CentralNotice-translations]] * FR ** [[phab:project/view/4263/|FR-Civi-Dedupe]] ** [[phab:project/view/4037/|FR-Civi-Planned-Giving]] ** [[phab:project/view/4036/|FR-Civi-Prospect]] * Fr ** [[phab:project/view/2928/|Fr-CiviCRM-dedupe-FY2017/18]] * FR ** [[phab:project/view/5223/|FR-CiviCRM-Searchkit]] * Fr ** [[phab:project/view/4356/|Fr-cross-training]] * FR ** [[phab:project/view/1603/|FR-dlocal]] ** [[phab:project/view/5137/|FR-Docker]] * fr ** [[phab:project/view/4915/|fr-donorservices]] * Fr ** [[phab:project/view/5128/|Fr-drupal-upgrade-2021]] * fr ** [[phab:project/view/5159/|fr-email-preference-center]] * FR ** [[phab:project/view/5274/|FR-EN6C]] * Fr ** [[phab:project/view/4975/|Fr-endowment]] * FR ** [[phab:project/view/4076/|FR-event logging as primary]] ** [[phab:project/view/4075/|FR-event logging in parallel ]] ** [[phab:project/view/3692/|FR-failmail]] ** [[phab:project/view/5770/|FR-form-chooser-refactor]] * Fr ** [[phab:project/view/4264/|Fr-fortnightly]] ** [[phab:project/view/5233/|FR-France]] * FR ** [[phab:project/view/5753/|FR-Gpay-Integration]] ** [[phab:project/view/5229/|FR-India]] ** [[phab:project/view/1604/|FR-Ingenico]] * Fr ** [[phab:project/view/2894/|Fr-Ingenico-integration_2017-18]] * FR ** [[phab:project/view/5234/|FR-Ireland]] ** [[phab:project/view/5232/|FR-Italy]] ** [[phab:project/view/5230/|FR-Japan]] ** [[phab:project/view/5228/|FR-LATAM]] * fr ** [[phab:project/view/5464/|fr-matching-gifts]] * FR ** [[phab:project/view/4769/|FR-MW-Vagrant]] ** [[phab:project/view/5272/|FR-Netherlands]] ** [[phab:project/view/5238/|FR-New-Zealand]] ** [[phab:project/view/1605/|FR-OtherProcessors]] ** [[phab:project/view/5764/|FR-payments-general]] ** [[phab:project/view/1601/|FR-Paypal]] ** [[phab:project/view/1893/|FR-PayPal-ExpressCheckout]] ** [[phab:project/view/1894/|FR-PCI]] * Fr ** [[phab:project/view/4494/|Fr-planning-ahead]] * FR ** [[phab:project/view/1653/|FR-Smashpig]] ** [[phab:project/view/5231/|FR-Sweden]] ** [[phab:project/view/5384/|FR-Target-Smart]] ** [[phab:project/view/3232/|FR-Tech-Analytics]] * fr ** [[phab:project/view/4507/|fr-tech-ops-okr]] * FR ** [[phab:project/view/5235/|FR-UK]] ** [[phab:project/view/5237/|FR-US]] ** [[phab:project/view/1931/|FR-WMF-Audit]] ** [[phab:project/view/1599/|FR-Worldpay]] * [[phab:project/view/59/|freigabe3]] * [[phab:project/view/4744/|Fresh]] * [[phab:project/view/3893/|Fresnel]] * function ** [[phab:project/view/5276/|function-evaluator]] ** [[phab:project/view/5277/|function-orchestrator]] ** [[phab:project/view/5364/|function-schemata]] * fundraising ** [[phab:project/view/1091/|fundraising-tech-ops]] * [[phab:project/view/2262/|Gamepress]] * [[phab:project/view/5999/|Ganeti]] * [[phab:project/view/1391/|GapFinder]] * Gendered ** [[phab:project/view/5066/|Gendered-Categories]] * [[phab:project/view/2912/|Genealogy]] * [[phab:project/view/605/|GeoCrumbs]] * [[phab:project/view/600/|GeoData]] * [[phab:project/view/330/|Gerrit]] * [[phab:project/view/2003/|GerritBot]] * Github ** [[phab:project/view/2762/|Github-notif-bot]] * [[phab:project/view/5793/|Gitiles]] * [[phab:project/view/5057/|GitLab]] * Gitlab ** [[phab:project/view/5984/|Gitlab-Application-Security-Pipeline]] * gitlab ** [[phab:project/view/5484/|gitlab-settings]] * GitLab ** [[phab:project/view/4954/|GitLab-Test]] * GLAM ** [[phab:project/view/2087/|GLAM-Tech]] * [[phab:project/view/2690/|glam2commons]] * [[phab:project/view/315/|GlobalBlocking]] * [[phab:project/view/1949/|GlobalContribs]] * [[phab:project/view/749/|GlobalCssJs]] * [[phab:project/view/1219/|GlobalRename]] * [[phab:project/view/394/|GlobalUsage]] * [[phab:project/view/802/|GlobalUserPage]] * [[phab:project/view/4288/|GLOW]] * [[phab:project/view/2926/|Goatification]] * Google ** [[phab:project/view/4740/|Google-api-proxy]] ** [[phab:project/view/4068/|Google-Drive-to-Commons]] * [[phab:project/view/23/|GoogleLogin]] * [[phab:project/view/3695/|GraphQL]] * [[phab:project/view/943/|GraphViz]] * [[phab:project/view/866/|GreyStuff]] * [[phab:project/view/5663/|Growth community maintenance]] * [[phab:project/view/4094/|Growth Design]] * Growth ** [[phab:project/view/5971/|Growth-Positive-Reinforcement]] ** [[phab:project/view/4738/|Growth-Scaling]] ** [[phab:project/view/4780/|Growth-Structured-Tasks]] ** [[phab:project/view/5314/|Growth-Team-Filtering]] ** [[phab:project/view/4908/|Growth-Team-Leftovers]] * [[phab:project/view/3716/|GrowthExperiments]] ** [[phab:project/view/5475/|GrowthExperiments-CommunityConfiguration]] ** [[phab:project/view/3985/|GrowthExperiments-Help panel]] ** [[phab:project/view/4099/|GrowthExperiments-HelpModule]] ** [[phab:project/view/3986/|GrowthExperiments-Homepage]] ** [[phab:project/view/4100/|GrowthExperiments-HomepageDiscovery]] ** [[phab:project/view/4097/|GrowthExperiments-ImpactModule]] ** [[phab:project/view/5219/|GrowthExperiments-MentorDashboard]] ** [[phab:project/view/4098/|GrowthExperiments-Mentorship]] ** [[phab:project/view/4226/|GrowthExperiments-NewcomerTasks]] ** [[phab:project/view/4095/|GrowthExperiments-StartModule]] * [[phab:project/view/3229/|Hashtags]] * [[phab:project/view/2771/|HasSomeColours]] * [[phab:project/view/3067/|HAWelcome]] * [[phab:project/view/5722/|Header Tabs]] * [[phab:project/view/4373/|homer]] * [[phab:project/view/1822/|Horizon]] * [[phab:project/view/4892/|HtmlFormatter]] * [[phab:project/view/520/|Huggle]] * [[phab:project/view/4967/|Humaniki]] * [[phab:project/view/1746/|HyperSwitch]] * [[phab:project/view/2793/|IA Upload]] * [[phab:project/view/80/|Icinga]] * IDS ** [[phab:project/view/2407/|IDS-extension]] * Image ** [[phab:project/view/5253/|Image-Suggestion-API]] ** [[phab:project/view/5098/|Image-Suggestions]] * [[phab:project/view/243/|ImageMap]] * [[phab:project/view/2461/|ImageRating]] * [[phab:project/view/1650/|ImageTweaks]] * import ** [[phab:project/view/3503/|import-500px]] * [[phab:project/view/1431/|ImportUsers]] * Improving ** [[phab:project/view/1401/|Improving-access]] * Incident ** [[phab:project/view/4038/|Incident-Reporting-System]] * [[phab:project/view/3752/|incubator.wikimedia.org]] * Instrument ** [[phab:project/view/5018/|Instrument-ClientError]] * [[phab:project/view/3156/|InteractionTimeline]] * International ** [[phab:project/view/4045/|International-Developer-Events]] * Internet ** [[phab:project/view/1576/|Internet-Archive]] * [[phab:project/view/2160/|InternetArchiveBot]] * iOS ** [[phab:project/view/1876/|iOS-app-Bugs]] ** [[phab:project/view/1882/|iOS-app-feature-Accessibility]] ** [[phab:project/view/1883/|iOS-app-feature-Analytics]] ** [[phab:project/view/2009/|iOS-app-feature-Database]] ** [[phab:project/view/2232/|iOS-app-feature-Feed]] ** [[phab:project/view/1884/|iOS-app-feature-iPad]] ** [[phab:project/view/1900/|iOS-app-feature-Links]] ** [[phab:project/view/2234/|iOS-app-feature-Login]] ** [[phab:project/view/1924/|iOS-app-feature-Multilingual]] ** [[phab:project/view/1875/|iOS-app-feature-Namespaces]] ** [[phab:project/view/5640/|iOS-app-feature-Navigation]] ** [[phab:project/view/2010/|iOS-app-feature-Notifications]] ** [[phab:project/view/1874/|iOS-app-feature-Offline]] ** [[phab:project/view/1879/|iOS-app-feature-Performance]] ** [[phab:project/view/2008/|iOS-app-feature-Places]] ** [[phab:project/view/1877/|iOS-app-feature-Saved]] ** [[phab:project/view/5714/|iOS-app-feature-Talkpages]] ** [[phab:project/view/1881/|iOS-app-feature-TOC]] ** [[phab:project/view/1878/|iOS-app-feature-TopRead]] ** [[phab:project/view/2233/|iOS-app-feature-Widgets]] * ios ** [[phab:project/view/5726/|ios-app-feature-wikitext-editor]] * iOS ** [[phab:project/view/5830/|iOS-app-next-os-update]] * [[phab:project/view/4923/|IP Info]] * [[phab:project/view/5751/|IP Masking]] * IPA ** [[phab:project/view/5901/|IPA-Audio-Renderer-Wish-2022]] * [[phab:project/view/5805/|IPFS]] * [[phab:project/view/1553/|IPSet]] * [[phab:project/view/4624/|IPUtils]] * [[phab:project/view/3382/|Ipwatcher]] * [[phab:project/view/2122/|IRCecho]] * [[phab:project/view/5357/|ircservserv]] * [[phab:project/view/3981/|ISA]] * [[phab:project/view/5209/|Item Quality Evaluator]] * [[phab:project/view/4932/|Item Quality Scoring Improvement]] * [[phab:project/view/3249/|Jouncebot]] * jQuery ** [[phab:project/view/1119/|jQuery-Client]] * [[phab:project/view/3689/|JSDoc WMF theme]] * [[phab:project/view/1103/|JsonConfig]] * [[phab:project/view/2809/|Junta Directiva]] * KaiOS ** [[phab:project/view/4305/|KaiOS-Wikipedia-app]] * [[phab:project/view/5847/|Kanban]] * [[phab:project/view/2777/|KartoEditor]] * [[phab:project/view/3771/|Keyholder]] * Knowledge ** [[phab:project/view/4384/|Knowledge-Integrity]] * LabsDB ** [[phab:project/view/939/|LabsDB-Auditor]] * Ladies ** [[phab:project/view/2329/|Ladies-That-FOSS-Wikidata]] * Language ** [[phab:project/view/4247/|Language-analytics]] ** [[phab:project/view/5974/|Language-Diversity-Hub]] ** [[phab:project/view/4361/|Language-research]] ** [[phab:project/view/3709/|Language-strategy]] * [[phab:project/view/547/|LastModified]] * LDAP ** [[phab:project/view/1564/|LDAP-Access-Requests]] * [[phab:project/view/4/|Legalpad]] * [[phab:project/view/43/|Librarization]] * Library ** [[phab:project/view/2765/|Library-Card-Platform]] ** [[phab:project/view/3401/|Library-Card-Platform-Discovery]] * [[phab:project/view/2930/|LibUp]] * Lift ** [[phab:project/view/5020/|Lift-Wing]] * [[phab:project/view/3393/|Lingua Libre]] * Linked ** [[phab:project/view/5893/|Linked-Open-Data-Network-Program]] * [[phab:project/view/799/|LinkFilter]] * [[phab:project/view/3916/|Loading Screen]] * local ** [[phab:project/view/3942/|local-charts]] * [[phab:project/view/4000/|LogoFunctions]] * [[phab:project/view/373/|LookupUser]] * [[phab:project/view/5876/|LSC]] * [[phab:project/view/3225/|LuaSandbox]] * [[phab:project/view/4081/|MachineVision]] * [[phab:project/view/983/|Mail]] * Map ** [[phab:project/view/3607/|Map-of-monuments]] * [[phab:project/view/1127/|Maps]] * [[phab:project/view/4011/|Mask]] * [[phab:project/view/4417/|Massmailer]] * [[phab:project/view/717/|MassMessage]] * [[phab:project/view/5541/|masz]] * [[phab:project/view/2422/|Material]] * [[phab:project/view/130/|Math]] ** [[phab:project/view/4847/|Math-Chemistry-Support]] ** [[phab:project/view/4848/|Math-Macro-Proposals]] ** [[phab:project/view/4849/|Math-Non-WMF-Installations]] ** [[phab:project/view/3743/|Mathe für Nicht-Freaks]] * [[phab:project/view/796/|Mathoid]] * [[phab:project/view/737/|MathSearch]] * [[phab:project/view/4056/|Matrix]] * Measuring ** [[phab:project/view/1400/|Measuring-value-added]] * media ** [[phab:project/view/5373/|media-backups]] ** [[phab:project/view/2455/|media-reports-tool]] * [[phab:project/view/5204/|MediaUploader]] * [[phab:project/view/230/|MediaViewer]] * [[phab:project/view/1464/|MediaWiki Language Extension Bundle]] * [[phab:project/view/4835/|MediaWiki Train Development Environment]] * MediaWiki ** [[phab:project/view/200/|MediaWiki-Action-API]] ** [[phab:project/view/1037/|MediaWiki-Authentication-and-authorization]] ** [[phab:project/view/4731/|MediaWiki-Blocks]] ** [[phab:project/view/150/|MediaWiki-Categories]] ** [[phab:project/view/181/|MediaWiki-Change-tagging]] ** [[phab:project/view/1087/|MediaWiki-Codesniffer]] ** [[phab:project/view/3742/|MediaWiki-Comment-store]] ** [[phab:project/view/359/|MediaWiki-Configuration]] ** [[phab:project/view/1687/|MediaWiki-Containers]] ** [[phab:project/view/256/|MediaWiki-ContentHandler]] ** [[phab:project/view/4730/|MediaWiki-Core-Hooks]] ** [[phab:project/view/5723/|MediaWiki-Core-HTTP-Cache]] ** [[phab:project/view/269/|MediaWiki-Core-JobQueue]] ** [[phab:project/view/163/|MediaWiki-Core-Preferences]] ** [[phab:project/view/4586/|MediaWiki-Core-Profiler]] ** [[phab:project/view/3880/|MediaWiki-Core-Revision-backend]] ** [[phab:project/view/4795/|MediaWiki-Core-Skin-Architecture]] ** [[phab:project/view/174/|MediaWiki-Core-Snapshots]] ** [[phab:project/view/313/|MediaWiki-Core-Tests]] ** [[phab:project/view/1694/|MediaWiki-Debian]] ** [[phab:project/view/1129/|MediaWiki-Debug-Logger]] ** [[phab:project/view/234/|MediaWiki-DjVu]] ** [[phab:project/view/4585/|MediaWiki-Docker]] ** [[phab:project/view/132/|MediaWiki-Documentation]] ** [[phab:project/view/216/|MediaWiki-Email]] ** [[phab:project/view/137/|MediaWiki-extension-requests]] ** [[phab:project/view/564/|MediaWiki-extensions-AccessControl]] ** [[phab:project/view/887/|MediaWiki-extensions-AccountInfo]] ** [[phab:project/view/3299/|MediaWiki-extensions-AddPersonalUrls]] ** [[phab:project/view/389/|MediaWiki-extensions-AdminLinks]] ** [[phab:project/view/454/|MediaWiki-extensions-AdvancedMeta]] ** [[phab:project/view/4601/|MediaWiki-extensions-AkismetKlik]] ** [[phab:project/view/3574/|MediaWiki-extensions-Approved-Revs]] ** [[phab:project/view/3565/|MediaWiki-extensions-Arrays]] ** [[phab:project/view/2887/|MediaWiki-extensions-ArticleCreationWorkflow]] ** [[phab:project/view/4489/|MediaWiki-extensions-ArticleToCategory2]] ** [[phab:project/view/2719/|MediaWiki-extensions-Auth_remoteuser]] ** [[phab:project/view/354/|MediaWiki-extensions-AutoCreateCategoryPages]] ** [[phab:project/view/4484/|MediaWiki-extensions-AutoProxyBlock]] ** [[phab:project/view/317/|MediaWiki-extensions-Babel]] ** [[phab:project/view/4594/|MediaWiki-extensions-BibManager]] ** [[phab:project/view/4514/|MediaWiki-extensions-Blackout]] ** [[phab:project/view/3024/|MediaWiki-extensions-BlockAndNuke]] ** [[phab:project/view/806/|MediaWiki-extensions-BounceHandler]] ** [[phab:project/view/760/|MediaWiki-extensions-BreadCrumbs]] ** [[phab:project/view/706/|MediaWiki-extensions-Campaigns]] ** [[phab:project/view/787/|MediaWiki-extensions-Capiunto]] ** [[phab:project/view/1029/|MediaWiki-extensions-Cargo]] ** [[phab:project/view/236/|MediaWiki-extensions-CategoryTree]] ** [[phab:project/view/2832/|MediaWiki-extensions-CategoryWatch]] ** [[phab:project/view/167/|MediaWiki-extensions-CentralAuth]] ** [[phab:project/view/291/|MediaWiki-extensions-CentralNotice]] ** [[phab:project/view/3615/|MediaWiki-extensions-ChangeUserPasswords]] ** [[phab:project/view/5907/|MediaWiki-extensions-CiteDrawer]] ** [[phab:project/view/455/|MediaWiki-extensions-CLDR]] ** [[phab:project/view/586/|MediaWiki-extensions-CleanChanges]] ** [[phab:project/view/4588/|MediaWiki-extensions-CloseWikis]] ** [[phab:project/view/1162/|MediaWiki-extensions-CodeMirror]] ** [[phab:project/view/318/|MediaWiki-extensions-CodeReview]] ** [[phab:project/view/1778/|MediaWiki-extensions-CollaborationKit]] ** [[phab:project/view/5908/|MediaWiki-extensions-CollapsibleSections]] ** [[phab:project/view/889/|MediaWiki-extensions-CollapsibleVector]] ** [[phab:project/view/649/|MediaWiki-extensions-Commentbox]] ** [[phab:project/view/506/|MediaWiki-extensions-Comments]] ** [[phab:project/view/2820/|MediaWiki-extensions-CommentStreams]] ** [[phab:project/view/4642/|MediaWiki-extensions-CommonMessages]] ** [[phab:project/view/288/|MediaWiki-extensions-ConfirmAccount]] ** [[phab:project/view/4590/|MediaWiki-extensions-CongressLookup]] ** [[phab:project/view/405/|MediaWiki-extensions-ContactPage]] ** [[phab:project/view/253/|MediaWiki-extensions-Contributors]] ** [[phab:project/view/2240/|MediaWiki-extensions-CookieWarning]] ** [[phab:project/view/4602/|MediaWiki-extensions-CountDownClock]] ** [[phab:project/view/2827/|MediaWiki-extensions-Create-User-Page]] ** [[phab:project/view/4483/|MediaWiki-extensions-CreateRedirect]] ** [[phab:project/view/598/|MediaWiki-extensions-CreditsSource]] ** [[phab:project/view/477/|MediaWiki-extensions-CSS]] ** [[phab:project/view/2924/|MediaWiki-extensions-Dashiki]] ** [[phab:project/view/791/|MediaWiki-extensions-DataTransfer]] ** [[phab:project/view/4512/|MediaWiki-extensions-DeleteBatch]] ** [[phab:project/view/885/|MediaWiki-extensions-DeleteOwn]] ** [[phab:project/view/1549/|MediaWiki-extensions-DeletePagesForGood]] ** [[phab:project/view/4462/|MediaWiki-extensions-DisableAccount]] ** [[phab:project/view/212/|MediaWiki-extensions-Disambiguator]] ** [[phab:project/view/6041/|MediaWiki-extensions-Discourse]] ** [[phab:project/view/798/|MediaWiki-extensions-DiscussionThreading]] ** [[phab:project/view/2694/|MediaWiki-extensions-DisplayTitle]] ** [[phab:project/view/4227/|MediaWiki-extensions-DocBookExport]] ** [[phab:project/view/409/|MediaWiki-extensions-DonationInterface]] ** [[phab:project/view/395/|MediaWiki-extensions-DoubleWiki]] ** [[phab:project/view/4640/|MediaWiki-extensions-DPLforum]] ** [[phab:project/view/316/|MediaWiki-extensions-Drafts]] ** [[phab:project/view/4999/|MediaWiki-extensions-DrawioEditor]] ** [[phab:project/view/4675/|MediaWiki-extensions-DumpsOnDemand]] ** [[phab:project/view/3955/|MediaWiki-extensions-Duplicator]] ** [[phab:project/view/614/|MediaWiki-extensions-DynamicSidebar]] ** [[phab:project/view/5909/|MediaWiki-extensions-EditAccount]] ** [[phab:project/view/220/|MediaWiki-extensions-Editcount]] ** [[phab:project/view/2007/|MediaWiki-extensions-EditNotify]] ** [[phab:project/view/560/|MediaWiki-extensions-EditUser]] ** [[phab:project/view/2826/|MediaWiki-extensions-Email_Authorization]] ** [[phab:project/view/2358/|MediaWiki-extensions-EmailAuth]] ** [[phab:project/view/5910/|MediaWiki-extensions-EncryptedUploads]] ** [[phab:project/view/534/|MediaWiki-extensions-EtherpadLite]] ** [[phab:project/view/589/|MediaWiki-extensions-EventLogging]] ** [[phab:project/view/1405/|MediaWiki-extensions-Examples]] ** [[phab:project/view/494/|MediaWiki-extensions-ExternalData]] ** [[phab:project/view/5911/|MediaWiki-extensions-ExternalLinkConfirm]] ** [[phab:project/view/792/|MediaWiki-extensions-ExtraLanguageLink]] ** [[phab:project/view/4637/|MediaWiki-extensions-Farmer]] ** [[phab:project/view/514/|MediaWiki-extensions-FeaturedFeeds]] ** [[phab:project/view/296/|MediaWiki-extensions-FlaggedRevs]] ** [[phab:project/view/5912/|MediaWiki-extensions-FlickrAPI]] ** [[phab:project/view/3117/|MediaWiki-extensions-Form]] ** [[phab:project/view/622/|MediaWiki-extensions-FundraiserLandingPage]] ** [[phab:project/view/285/|MediaWiki-extensions-Gadgets]] ** [[phab:project/view/176/|MediaWiki-extensions-General]] ** [[phab:project/view/590/|MediaWiki-extensions-GettingStarted]] ** [[phab:project/view/884/|MediaWiki-extensions-Git2Pages]] ** [[phab:project/view/763/|MediaWiki-extensions-GlobalPreferences]] ** [[phab:project/view/4828/|MediaWiki-extensions-GlobalWatchlist]] ** [[phab:project/view/4228/|MediaWiki-extensions-GoogleAdSense]] ** [[phab:project/view/5913/|MediaWiki-extensions-GoogleAnalyticsMetrics]] ** [[phab:project/view/5914/|MediaWiki-extensions-GoogleCustomWikiSearch]] ** [[phab:project/view/509/|MediaWiki-extensions-GoogleNewsSitemap]] ** [[phab:project/view/1548/|MediaWiki-extensions-GPGMail]] ** [[phab:project/view/816/|MediaWiki-extensions-Graph]] ** [[phab:project/view/3902/|MediaWiki-extensions-GraphQL]] ** [[phab:project/view/5294/|MediaWiki-extensions-Gravatar]] ** [[phab:project/view/5915/|MediaWiki-extensions-GroupWhitelist]] ** [[phab:project/view/582/|MediaWiki-extensions-GuidedTour]] ** [[phab:project/view/744/|MediaWiki-extensions-GWToolset]] ** [[phab:project/view/853/|MediaWiki-extensions-Hierarchy-Builder]] ** [[phab:project/view/1320/|MediaWiki-extensions-HitCounters]] ** [[phab:project/view/2350/|MediaWiki-extensions-HostStats]] ** [[phab:project/view/1094/|MediaWiki-extensions-Html2Wiki]] ** [[phab:project/view/3763/|MediaWiki-extensions-ImageCompare]] ** [[phab:project/view/1512/|MediaWiki-extensions-ImportArticles]] ** [[phab:project/view/290/|MediaWiki-extensions-ImportFreeImages]] ** [[phab:project/view/374/|MediaWiki-extensions-IndexFunction]] ** [[phab:project/view/180/|MediaWiki-extensions-InputBox]] ** [[phab:project/view/690/|MediaWiki-extensions-Insider]] ** [[phab:project/view/443/|MediaWiki-extensions-Interlanguage]] ** [[phab:project/view/333/|MediaWiki-extensions-Interwiki]] ** [[phab:project/view/4366/|MediaWiki-extensions-InterwikiExtracts]] ** [[phab:project/view/2374/|MediaWiki-extensions-InterwikiSorting]] ** [[phab:project/view/4600/|MediaWiki-extensions-InviteSignup]] ** [[phab:project/view/1032/|MediaWiki-extensions-Josa]] ** [[phab:project/view/3242/|MediaWiki-extensions-JSBreadCrumbs]] ** [[phab:project/view/4501/|MediaWiki-extensions-JsonData]] ** [[phab:project/view/302/|MediaWiki-extensions-LabeledSectionTransclusion]] ** [[phab:project/view/371/|MediaWiki-extensions-LanguageSelector]] ** [[phab:project/view/5202/|MediaWiki-extensions-LastUserLogin]] ** [[phab:project/view/414/|MediaWiki-extensions-LdapAuthentication]] ** [[phab:project/view/4169/|MediaWiki-extensions-LDAPAuthentication2]] ** [[phab:project/view/863/|MediaWiki-extensions-LDAPAuthorization]] ** [[phab:project/view/3070/|MediaWiki-extensions-LDAPGroups]] ** [[phab:project/view/3952/|MediaWiki-extensions-LDAPProvider]] ** [[phab:project/view/3953/|MediaWiki-extensions-LDAPUserInfo]] ** [[phab:project/view/5916/|MediaWiki-extensions-LegalLogin]] ** [[phab:project/view/723/|MediaWiki-extensions-Lingo]] ** [[phab:project/view/2164/|MediaWiki-extensions-LinkedWiki]] ** [[phab:project/view/4499/|MediaWiki-extensions-LinkSuggest]] ** [[phab:project/view/5917/|MediaWiki-extensions-LinkTarget]] ** [[phab:project/view/2318/|MediaWiki-extensions-Linter]] ** [[phab:project/view/303/|MediaWiki-extensions-LiquidThreads]] ** [[phab:project/view/597/|MediaWiki-extensions-Listings]] ** [[phab:project/view/376/|MediaWiki-extensions-LocalisationUpdate]] ** [[phab:project/view/5207/|MediaWiki-extensions-LockAuthor]] ** [[phab:project/view/416/|MediaWiki-extensions-Lockdown]] ** [[phab:project/view/321/|MediaWiki-extensions-LogEntry]] ** [[phab:project/view/2419/|MediaWiki-extensions-LoginNotify]] ** [[phab:project/view/3567/|MediaWiki-extensions-Loops]] ** [[phab:project/view/4596/|MediaWiki-extensions-MagicNoCache]] ** [[phab:project/view/1424/|MediaWiki-extensions-Mailgun]] ** [[phab:project/view/451/|MediaWiki-extensions-Maintenance (by Skizzerz)]] ** [[phab:project/view/643/|MediaWiki-extensions-MaintenanceShell]] ** [[phab:project/view/640/|MediaWiki-extensions-MapSources]] ** [[phab:project/view/769/|MediaWiki-extensions-MarkAsHelpful]] ** [[phab:project/view/4486/|MediaWiki-extensions-MassEditRegex]] ** [[phab:project/view/5918/|MediaWiki-extensions-MassMessageEmail]] ** [[phab:project/view/286/|MediaWiki-extensions-MediaFunctions]] ** [[phab:project/view/4608/|MediaWiki-extensions-MediaModeration]] ** [[phab:project/view/2687/|MediaWiki-extensions-MediaWikiFarm]] ** [[phab:project/view/5919/|MediaWiki-extensions-MetaMaster]] ** [[phab:project/view/3577/|MediaWiki-extensions-MintyDocs]] ** [[phab:project/view/793/|MediaWiki-extensions-MobileApp]] ** [[phab:project/view/5145/|MediaWiki-extensions-MobileDetect]] ** [[phab:project/view/804/|MediaWiki-extensions-MolHandler]] ** [[phab:project/view/2421/|MediaWiki-extensions-MsCalendar]] ** [[phab:project/view/926/|MediaWiki-extensions-MsCatSelect]] ** [[phab:project/view/883/|MediaWiki-extensions-MsUpload]] ** [[phab:project/view/295/|MediaWiki-extensions-MultiBoilerplate]] ** [[phab:project/view/6007/|MediaWiki-extensions-MultiMail]] ** [[phab:project/view/4490/|MediaWiki-extensions-MultiMaps]] ** [[phab:project/view/5920/|MediaWiki-extensions-MyVariables]] ** [[phab:project/view/5921/|MediaWiki-extensions-NamespaceHTML]] ** [[phab:project/view/4515/|MediaWiki-extensions-NetworkAuth]] ** [[phab:project/view/319/|MediaWiki-extensions-NewestPages]] ** [[phab:project/view/4589/|MediaWiki-extensions-News]] ** [[phab:project/view/888/|MediaWiki-extensions-Newsletter]] ** [[phab:project/view/1863/|MediaWiki-extensions-NewUserActions]] ** [[phab:project/view/305/|MediaWiki-extensions-NewUserMessage]] ** [[phab:project/view/450/|MediaWiki-extensions-NewUserNotif]] ** [[phab:project/view/563/|MediaWiki-extensions-NSFileRepo]] ** [[phab:project/view/231/|MediaWiki-extensions-Nuke]] ** [[phab:project/view/554/|MediaWiki-extensions-OATHAuth]] ** [[phab:project/view/682/|MediaWiki-extensions-OAuth]] ** [[phab:project/view/1263/|MediaWiki-extensions-OAuthAuthentication]] ** [[phab:project/view/4904/|MediaWiki-extensions-OAuthRateLimiter]] ** [[phab:project/view/343/|MediaWiki-extensions-OnlineStatus]] ** [[phab:project/view/553/|MediaWiki-extensions-OnlineStatusBar]] ** [[phab:project/view/882/|MediaWiki-extensions-OnlyRecentRecentChanges]] ** [[phab:project/view/4498/|MediaWiki-extensions-OpenGraphMeta]] ** [[phab:project/view/244/|MediaWiki-extensions-OpenID]] ** [[phab:project/view/862/|MediaWiki-extensions-OpenID-Connect]] ** [[phab:project/view/4530/|MediaWiki-extensions-OpenJsCad]] ** [[phab:project/view/420/|MediaWiki-extensions-OpenStackManager]] ** [[phab:project/view/1662/|MediaWiki-extensions-ORES]] ** [[phab:project/view/2861/|MediaWiki-extensions-OrphanedTalkPages]] ** [[phab:project/view/308/|MediaWiki-extensions-Other]] ** [[phab:project/view/272/|MediaWiki-extensions-Page_Forms]] ** [[phab:project/view/1936/|MediaWiki-extensions-PageAssessments]] ** [[phab:project/view/403/|MediaWiki-extensions-PagedTiffHandler]] ** [[phab:project/view/5922/|MediaWiki-extensions-PageMagic]] ** [[phab:project/view/392/|MediaWiki-extensions-PageNotice]] ** [[phab:project/view/652/|MediaWiki-extensions-PageSchemas]] ** [[phab:project/view/4487/|MediaWiki-extensions-ParserMigration]] ** [[phab:project/view/261/|MediaWiki-extensions-Patroller]] ** [[phab:project/view/393/|MediaWiki-extensions-PdfHandler]] ** [[phab:project/view/1851/|MediaWiki-extensions-PerformanceInspector]] ** [[phab:project/view/5923/|MediaWiki-extensions-PerPageLanguage]] ** [[phab:project/view/786/|MediaWiki-extensions-Petition]] ** [[phab:project/view/4513/|MediaWiki-extensions-PGFTikZ]] ** [[phab:project/view/1159/|MediaWiki-extensions-PhpTags]] ** [[phab:project/view/861/|MediaWiki-extensions-Pluggable-Auth]] ** [[phab:project/view/232/|MediaWiki-extensions-Poem]] ** [[phab:project/view/415/|MediaWiki-extensions-Poll]] ** [[phab:project/view/5924/|MediaWiki-extensions-PopupAlerts]] ** [[phab:project/view/2796/|MediaWiki-extensions-PropertySuggester]] ** [[phab:project/view/4395/|MediaWiki-extensions-ProtectionIndicator]] ** [[phab:project/view/4643/|MediaWiki-extensions-Push]] ** [[phab:project/view/4500/|MediaWiki-extensions-PushToWatch]] ** [[phab:project/view/1984/|MediaWiki-extensions-QuickGV]] ** [[phab:project/view/5881/|MediaWiki-extensions-QuickInstantCommons]] ** [[phab:project/view/289/|MediaWiki-extensions-Quiz]] ** [[phab:project/view/248/|MediaWiki-extensions-RandomImage]] ** [[phab:project/view/4639/|MediaWiki-extensions-RandomInCategory]] ** [[phab:project/view/6042/|MediaWiki-extensions-Realnames]] ** [[phab:project/view/5782/|MediaWiki-extensions-RedirectManager]] ** [[phab:project/view/780/|MediaWiki-extensions-RefreshSpecial]] ** [[phab:project/view/595/|MediaWiki-extensions-RelatedSites]] ** [[phab:project/view/204/|MediaWiki-extensions-Renameuser]] ** [[phab:project/view/344/|MediaWiki-extensions-ReplaceText]] ** [[phab:project/view/4625/|MediaWiki-extensions-RevisionCommentSupplement]] ** [[phab:project/view/4615/|MediaWiki-extensions-RightFunctions]] ** [[phab:project/view/430/|MediaWiki-extensions-RSS]] ** [[phab:project/view/822/|MediaWiki-extensions-SandboxLink]] ** [[phab:project/view/5925/|MediaWiki-extensions-SaveSpinner]] ** [[phab:project/view/613/|MediaWiki-extensions-Score]] ** [[phab:project/view/1550/|MediaWiki-extensions-Screenplay]] ** [[phab:project/view/558/|MediaWiki-extensions-Scribunto]] ** [[phab:project/view/876/|MediaWiki-extensions-SearchExtraNS]] ** [[phab:project/view/4674/|MediaWiki-extensions-SearchStats]] ** [[phab:project/view/3366/|MediaWiki-extensions-SecureAuth]] ** [[phab:project/view/3495/|MediaWiki-extensions-SecureLinkFixer]] ** [[phab:project/view/238/|MediaWiki-extensions-SecurePoll]] ** [[phab:project/view/704/|MediaWiki-extensions-SecureSessions]] ** [[phab:project/view/260/|MediaWiki-extensions-SelectCategory]] ** [[phab:project/view/860/|MediaWiki-extensions-Semantic-Dependency]] ** [[phab:project/view/855/|MediaWiki-extensions-Semantic-Rating]] ** [[phab:project/view/4497/|MediaWiki-extensions-SemanticACL]] ** [[phab:project/view/293/|MediaWiki-extensions-SemanticDrilldown]] ** [[phab:project/view/2051/|MediaWiki-extensions-SemanticQueryInterface]] ** [[phab:project/view/2954/|MediaWiki-extensions-SendGrid]] ** [[phab:project/view/491/|MediaWiki-extensions-ShortUrl]] ** [[phab:project/view/5926/|MediaWiki-extensions-ShowMe]] ** [[phab:project/view/859/|MediaWiki-extensions-SimpleSAMLphp]] ** [[phab:project/view/4502/|MediaWiki-extensions-Site_Settings]] ** [[phab:project/view/1406/|MediaWiki-extensions-SkinPerNamespace]] ** [[phab:project/view/4616/|MediaWiki-extensions-SkinPerPage]] ** [[phab:project/view/625/|MediaWiki-extensions-SlimboxThumbs]] ** [[phab:project/view/1252/|MediaWiki-extensions-SmiteSpam]] ** [[phab:project/view/5931/|MediaWiki-extensions-SpamDiffTool]] ** [[phab:project/view/3794/|MediaWiki-extensions-SparkPost]] ** [[phab:project/view/467/|MediaWiki-extensions-SphinxSearch]] ** [[phab:project/view/4641/|MediaWiki-extensions-StalkerLog]] ** [[phab:project/view/2324/|MediaWiki-extensions-StlHandler]] ** [[phab:project/view/781/|MediaWiki-extensions-StopForumSpam]] ** [[phab:project/view/411/|MediaWiki-extensions-StringFunctionsEscaped]] ** [[phab:project/view/4587/|MediaWiki-extensions-SubPageList3]] ** [[phab:project/view/874/|MediaWiki-extensions-SubpageSortkey]] ** [[phab:project/view/4638/|MediaWiki-extensions-Sudo]] ** [[phab:project/view/660/|MediaWiki-extensions-Survey]] ** [[phab:project/view/872/|MediaWiki-extensions-SwiftMailer]] ** [[phab:project/view/4016/|MediaWiki-extensions-TEI]] ** [[phab:project/view/604/|MediaWiki-extensions-TemplateSandbox]] ** [[phab:project/view/3284/|MediaWiki-extensions-TemplateWizard]] ** [[phab:project/view/1363/|MediaWiki-extensions-TestLanguageNameGrammar]] ** [[phab:project/view/671/|MediaWiki-extensions-ThrottleOverride]] ** [[phab:project/view/3575/|MediaWiki-extensions-TinyMCE]] ** [[phab:project/view/854/|MediaWiki-extensions-Title-Icon]] ** [[phab:project/view/397/|MediaWiki-extensions-TitleKey]] ** [[phab:project/view/666/|MediaWiki-extensions-TocTree]] ** [[phab:project/view/6037/|MediaWiki-extensions-Toolhub]] ** [[phab:project/view/444/|MediaWiki-extensions-TorBlock]] ** [[phab:project/view/271/|MediaWiki-extensions-Translate]] ** [[phab:project/view/1272/|MediaWiki-extensions-TranslateSvg]] ** [[phab:project/view/551/|MediaWiki-extensions-TranslationNotifications]] ** [[phab:project/view/2138/|MediaWiki-extensions-TrustedXFF]] ** [[phab:project/view/764/|MediaWiki-extensions-TweetANew]] ** [[phab:project/view/619/|MediaWiki-extensions-TwitterCards]] ** [[phab:project/view/4598/|MediaWiki-extensions-TwitterLogin]] ** [[phab:project/view/650/|MediaWiki-extensions-TwnMainPage]] ** [[phab:project/view/4509/|MediaWiki-extensions-UIFeedback]] ** [[phab:project/view/4599/|MediaWiki-extensions-UnicodeConverter]] ** [[phab:project/view/4593/|MediaWiki-extensions-UploadBlacklist]] ** [[phab:project/view/1846/|MediaWiki-extensions-UploadsLink]] ** [[phab:project/view/809/|MediaWiki-extensions-UrlShortener]] ** [[phab:project/view/3531/|MediaWiki-extensions-UserAgreement]] ** [[phab:project/view/5208/|MediaWiki-extensions-UseResource]] ** [[phab:project/view/453/|MediaWiki-extensions-UserMerge]] ** [[phab:project/view/5927/|MediaWiki-extensions-UserProtect]] ** [[phab:project/view/3326/|MediaWiki-extensions-Variables]] ** [[phab:project/view/3576/|MediaWiki-extensions-VEForAll]] ** [[phab:project/view/3213/|MediaWiki-extensions-VersionCompare]] ** [[phab:project/view/858/|MediaWiki-extensions-VIKI]] ** [[phab:project/view/857/|MediaWiki-extensions-VikiSemanticTitle]] ** [[phab:project/view/505/|MediaWiki-extensions-VipsScaler]] ** [[phab:project/view/4488/|MediaWiki-extensions-WatchSubpages]] ** [[phab:project/view/3888/|MediaWiki-extensions-WebDAV]] ** [[phab:project/view/4266/|MediaWiki-extensions-WebToolsManager]] ** [[phab:project/view/4491/|MediaWiki-extensions-WhoIsWatching]] ** [[phab:project/view/358/|MediaWiki-extensions-Widgets]] ** [[phab:project/view/4747/|MediaWiki-extensions-WikEdDiff]] ** [[phab:project/view/114/|MediaWiki-extensions-WikibaseClient]] ** [[phab:project/view/5043/|MediaWiki-extensions-WikibaseManifest]] ** [[phab:project/view/113/|MediaWiki-extensions-WikibaseRepository]] ** [[phab:project/view/1176/|MediaWiki-extensions-WikibaseView]] ** [[phab:project/view/242/|MediaWiki-extensions-WikiLexicalData-or-OmegaWiki]] ** [[phab:project/view/4823/|MediaWiki-extensions-WikimediaApiPortalOAuth]] ** [[phab:project/view/3286/|MediaWiki-extensions-WikimediaBadges]] ** [[phab:project/view/707/|MediaWiki-extensions-WikimediaEvents]] ** [[phab:project/view/471/|MediaWiki-extensions-WikimediaIncubator]] ** [[phab:project/view/492/|MediaWiki-extensions-WikimediaMaintenance]] ** [[phab:project/view/1309/|MediaWiki-extensions-WikiShare]] ** [[phab:project/view/5370/|MediaWiki-extensions-WSOAuth]] ** [[phab:project/view/131/|MediaWiki-File-management]] ** [[phab:project/view/1498/|MediaWiki-Gallery]] ** [[phab:project/view/135/|MediaWiki-General]] ** [[phab:project/view/1525/|MediaWiki-HTML-Templating]] ** [[phab:project/view/540/|MediaWiki-HTMLForm]] ** [[phab:project/view/147/|MediaWiki-Installer]] ** [[phab:project/view/155/|MediaWiki-Interface]] ** [[phab:project/view/144/|MediaWiki-Internationalization]] ** [[phab:project/view/1685/|MediaWiki-Interwiki]] ** [[phab:project/view/223/|MediaWiki-Language-converter]] ** [[phab:project/view/5082/|MediaWiki-libs-Assert]] ** [[phab:project/view/3777/|MediaWiki-libs-HTTP]] ** [[phab:project/view/5583/|MediaWiki-libs-Metrics]] ** [[phab:project/view/4783/|MediaWiki-libs-Mime]] ** [[phab:project/view/1329/|MediaWiki-libs-ObjectCache]] * mediawiki ** [[phab:project/view/5496/|mediawiki-libs-RequestTimeout]] * MediaWiki ** [[phab:project/view/3390/|MediaWiki-libs-Services]] ** [[phab:project/view/356/|MediaWiki-Logevents]] ** [[phab:project/view/268/|MediaWiki-Maintenance-system]] ** [[phab:project/view/4728/|MediaWiki-MergeHistory]] ** [[phab:project/view/213/|MediaWiki-Page-deletion]] ** [[phab:project/view/3881/|MediaWiki-Page-derived-data]] ** [[phab:project/view/149/|MediaWiki-Page-diffs]] ** [[phab:project/view/139/|MediaWiki-Page-editing]] ** [[phab:project/view/4287/|MediaWiki-Page-history]] ** [[phab:project/view/278/|MediaWiki-Page-protection]] ** [[phab:project/view/4727/|MediaWiki-Page-rename]] ** [[phab:project/view/136/|MediaWiki-Parser]] ** [[phab:project/view/195/|MediaWiki-Patrolling]] ** [[phab:project/view/194/|MediaWiki-Recent-changes]] ** [[phab:project/view/160/|MediaWiki-Redirects]] ** [[phab:project/view/3044/|MediaWiki-Release-Tools]] ** [[phab:project/view/274/|MediaWiki-ResourceLoader]] ** [[phab:project/view/4020/|MediaWiki-REST-API]] ** [[phab:project/view/337/|MediaWiki-Revision-deletion]] ** [[phab:project/view/146/|MediaWiki-Search]] ** [[phab:project/view/3150/|MediaWiki-Shell]] ** [[phab:project/view/656/|MediaWiki-Site-system]] ** [[phab:project/view/5070/|MediaWiki-skins-Amethyst]] ** [[phab:project/view/5703/|MediaWiki-skins-Cavendish]] ** [[phab:project/view/5077/|MediaWiki-skins-Erudite]] ** [[phab:project/view/5131/|MediaWiki-skins-GuMaxDD]] ** [[phab:project/view/5134/|MediaWiki-skins-Mirage]] ** [[phab:project/view/5073/|MediaWiki-skins-p2wiki]] ** [[phab:project/view/5130/|MediaWiki-skins-Schulenburg]] ** [[phab:project/view/5072/|MediaWiki-skins-Strapping]] ** [[phab:project/view/5074/|MediaWiki-skins-Tempo]] ** [[phab:project/view/5075/|MediaWiki-skins-WebPlatform]] ** [[phab:project/view/133/|MediaWiki-Special-pages]] ** [[phab:project/view/142/|MediaWiki-Templates]] ** [[phab:project/view/4634/|MediaWiki-TrackingCategories]] ** [[phab:project/view/158/|MediaWiki-Uploading]] ** [[phab:project/view/148/|MediaWiki-User-login-and-signup]] ** [[phab:project/view/198/|MediaWiki-User-management]] ** [[phab:project/view/627/|MediaWiki-Vagrant]] ** [[phab:project/view/818/|MediaWiki-Vendor]] ** [[phab:project/view/173/|MediaWiki-Watchlist]] * [[phab:project/view/1950/|MediaWikiChat]] * Mention ** [[phab:project/view/2101/|Mention-Notification]] * Metrics ** [[phab:project/view/5324/|Metrics-Platform]] * [[phab:project/view/1023/|Metrolook]] * [[phab:project/view/2799/|MinervaNeue]] * [[phab:project/view/2390/|MiniInvite]] * [[phab:project/view/2998/|MinusX]] * [[phab:project/view/5385/|Mismatch Finder]] * [[phab:project/view/3458/|Mitmachen]] * ML ** [[phab:project/view/5244/|ML-Governance]] * Mobile ** [[phab:project/view/1323/|Mobile-Content-Service]] * [[phab:project/view/1157/|MobileFrontend]] * [[phab:project/view/5482/|MobileFrontend Content Provider]] * [[phab:project/view/396/|Modern]] * [[phab:project/view/355/|MonoBook]] * [[phab:project/view/2287/|Montage]] * [[phab:project/view/3379/|MontserratFont]] * [[phab:project/view/2696/|Monumental]] * Move ** [[phab:project/view/2671/|Move-Files-To-Commons]] * Multi ** [[phab:project/view/3112/|Multi-Content-Revisions]] * MW ** [[phab:project/view/4946/|MW-on-K8s]] * [[phab:project/view/5331/|mwcli]] * [[phab:project/view/4910/|Nagf]] * Navigation ** [[phab:project/view/2055/|Navigation-Popups-Gadget]] * [[phab:project/view/642/|NavigationTiming]] * [[phab:project/view/4609/|NearbyPages]] * [[phab:project/view/4031/|netbox]] * [[phab:project/view/950/|netops]] * [[phab:project/view/4282/|NewcomerTasks 1.0 ]] * [[phab:project/view/4283/|NewcomerTasks 1.1]] * [[phab:project/view/4284/|NewcomerTasks 1.2]] * [[phab:project/view/4285/|NewcomerTasks Future Release ]] * [[phab:project/view/2265/|NewSignupPage]] * [[phab:project/view/807/|Nimbus]] * [[phab:project/view/5986/|noc.wikimedia.org]] * Nonpublic ** [[phab:project/view/1485/|Nonpublic-Information-Access-Policy]] * [[phab:project/view/5414/|NormalizedException]] * [[phab:project/view/865/|Nostalgia]] * [[phab:project/view/182/|Notifications]] * [[phab:project/view/2734/|OABot]] * [[phab:project/view/3244/|ObjectFactory]] * [[phab:project/view/84/|observability]] * Observability ** [[phab:project/view/5394/|Observability-Alerting]] ** [[phab:project/view/5393/|Observability-Logging]] ** [[phab:project/view/5392/|Observability-Metrics]] ** [[phab:project/view/5395/|Observability-Tracing]] * [[phab:project/view/5710/|ogv.js]] * [[phab:project/view/748/|OOjs core]] * OOjs ** [[phab:project/view/2119/|OOjs-Router]] * [[phab:project/view/697/|OOUI]] * [[phab:project/view/916/|OpenBadges]] * ops ** [[phab:project/view/955/|ops-codfw]] ** [[phab:project/view/5329/|ops-drmrs]] ** [[phab:project/view/1635/|ops-eqdfw]] ** [[phab:project/view/952/|ops-eqiad]] ** [[phab:project/view/1636/|ops-eqord]] ** [[phab:project/view/3127/|ops-eqsin]] ** [[phab:project/view/951/|ops-esams]] ** [[phab:project/view/954/|ops-ulsfo]] * [[phab:project/view/5061/|Orchestrator]] * [[phab:project/view/1467/|ORES]] ** [[phab:project/view/3327/|ORES-Support-Checklist]] * Other ** [[phab:project/view/824/|Other-skins]] * Outreach ** [[phab:project/view/2537/|Outreach-Programs-Projects]] * [[phab:project/view/4178/|OWC2020]] * [[phab:project/view/1782/|Packaging]] * [[phab:project/view/2885/|Page Content Service]] * Page ** [[phab:project/view/765/|Page-Previews]] * [[phab:project/view/731/|PageImages]] * [[phab:project/view/541/|PageTriage]] * [[phab:project/view/1753/|PageViewInfo]] * Pageviews ** [[phab:project/view/1772/|Pageviews-API]] * [[phab:project/view/237/|ParserFunctions]] * [[phab:project/view/487/|Parsoid]] ** [[phab:project/view/1046/|Parsoid-Nowiki]] ** [[phab:project/view/5532/|Parsoid-Read-Views]] ** [[phab:project/view/1286/|Parsoid-Rendering]] ** [[phab:project/view/1045/|Parsoid-Robustness]] ** [[phab:project/view/488/|Parsoid-Serializer]] ** [[phab:project/view/610/|Parsoid-Tests]] ** [[phab:project/view/581/|Parsoid-Tokenizer]] * Password ** [[phab:project/view/4275/|Password-Reset-Update]] * [[phab:project/view/4058/|PasswordlessLogin]] * [[phab:project/view/1648/|PAWS]] * [[phab:project/view/4800/|Peek]] * Performance ** [[phab:project/view/4983/|Performance-Device-Lab]] * [[phab:project/view/5/|Phabricator]] * [[phab:project/view/4460/|Phabricator Antivandalism Extension]] * [[phab:project/view/5254/|phabricator maintenance bot]] * Phabricator ** [[phab:project/view/981/|Phabricator-Bot-Requests]] * [[phab:project/view/3065/|PhabTaskGraph]] * [[phab:project/view/3906/|phan]] ** [[phab:project/view/3149/|phan-taint-check-plugin]] * [[phab:project/view/4578/|Phatality]] * [[phab:project/view/5900/|PhotoSwipe]] * PHP ** [[phab:project/view/2349/|PHP-API-for-Wikisource]] * php ** [[phab:project/view/1581/|php-session-serializer]] ** [[phab:project/view/4060/|php-wmerrors]] ** [[phab:project/view/3222/|phpunit-patch-coverage]] * [[phab:project/view/880/|PictureGame]] * Pilot ** [[phab:project/view/5021/|Pilot-Flag]] * [[phab:project/view/510/|PollNY]] * [[phab:project/view/4144/|Poncho]] * [[phab:project/view/437/|PoolCounter]] * preview ** [[phab:project/view/5365/|preview-environment]] * [[phab:project/view/2830/|PrivateDomains]] * [[phab:project/view/1155/|procurement]] * Prod ** [[phab:project/view/2290/|Prod-Kubernetes]] * [[phab:project/view/5040/|Product Infrastructure Roadmap]] * [[phab:project/view/5582/|Product Roadmap]] * Product ** [[phab:project/view/3348/|Product-Design-Strategy]] ** [[phab:project/view/4982/|Product-Platform Operations]] * [[phab:project/view/645/|PronunciationRecording]] * [[phab:project/view/276/|ProofreadPage]] * [[phab:project/view/2960/|Proton]] * ProveIt ** [[phab:project/view/2317/|ProveIt-Gadget]] * puppet ** [[phab:project/view/1807/|puppet-compiler]] * [[phab:project/view/5750/|Purtle]] * Push ** [[phab:project/view/2699/|Push-Notification-Service]] * [[phab:project/view/984/|PyBal]] * [[phab:project/view/87/|Pywikibot]] ** [[phab:project/view/92/|Pywikibot-archivebot.py]] * pywikibot ** [[phab:project/view/2250/|pywikibot-bots-FLOSSbot]] * Pywikibot ** [[phab:project/view/93/|Pywikibot-category.py]] ** [[phab:project/view/755/|Pywikibot-catfiles]] ** [[phab:project/view/1484/|Pywikibot-Commons]] ** [[phab:project/view/95/|Pywikibot-cosmetic-changes.py]] ** [[phab:project/view/1247/|Pywikibot-Flow]] ** [[phab:project/view/99/|Pywikibot-i18n]] ** [[phab:project/view/100/|Pywikibot-interwiki.py]] ** [[phab:project/view/101/|Pywikibot-login.py]] ** [[phab:project/view/1246/|Pywikibot-OAuth]] ** [[phab:project/view/104/|Pywikibot-pagegenerators.py]] ** [[phab:project/view/105/|Pywikibot-redirect.py]] ** [[phab:project/view/1293/|Pywikibot-replace.py]] ** [[phab:project/view/103/|Pywikibot-Scripts]] ** [[phab:project/view/106/|Pywikibot-solve-disambiguation.py]] ** [[phab:project/view/108/|Pywikibot-textlib.py]] ** [[phab:project/view/109/|Pywikibot-weblinkchecker.py]] * QRpedia ** [[phab:project/view/728/|QRpedia-General]] * Quality ** [[phab:project/view/4725/|Quality-and-Test-Engineering-Retrospectives]] * [[phab:project/view/800/|Quarry]] ** [[phab:project/view/2572/|QuarryBot-enwiki]] * [[phab:project/view/2772/|Quibble]] * [[phab:project/view/1429/|QuickSurveys]] * [[phab:project/view/879/|QuizGame]] * [[phab:project/view/877/|RandomGameUnit]] * React ** [[phab:project/view/5048/|React-i18n]] * Reader ** [[phab:project/view/1787/|Reader-research]] ** [[phab:project/view/1538/|Readers-Community-Engagement]] * [[phab:project/view/3910/|Reading Depth]] * [[phab:project/view/2740/|Reading List Service]] * Reading ** [[phab:project/view/1682/|Reading-Web-Local-Wiki-Issues]] * Recommendation ** [[phab:project/view/2128/|Recommendation-API]] * [[phab:project/view/5458/|Reconciliation]] * [[phab:project/view/3840/|Reference Previews]] * [[phab:project/view/1956/|Refreshed]] * [[phab:project/view/345/|RegexBlock]] * [[phab:project/view/688/|RelatedArticles]] * [[phab:project/view/1276/|ReleaseTaggerBot]] * [[phab:project/view/2978/|RemexHtml]] * Reports ** [[phab:project/view/1940/|Reports-bot]] * [[phab:project/view/1292/|Research ideas]] * Research ** [[phab:project/view/1396/|Research-and-Data-VisualEditor ]] ** [[phab:project/view/2113/|Research-collaborations]] ** [[phab:project/view/1402/|Research-consulting]] ** [[phab:project/view/4383/|Research-foundational]] ** [[phab:project/view/3243/|Research-landing-page]] ** [[phab:project/view/1395/|Research-management]] ** [[phab:project/view/1394/|Research-outreach]] * [[phab:project/view/833/|RESTBase]] ** [[phab:project/view/851/|RESTBase-API]] ** [[phab:project/view/834/|RESTBase-Cassandra]] * restbase ** [[phab:project/view/4389/|restbase-mysql]] * Retro ** [[phab:project/view/4788/|Retro-Actions]] * Revision ** [[phab:project/view/1639/|Revision-Slider]] * [[phab:project/view/1677/|revscoring]] * Riksarkivet ** [[phab:project/view/5289/|Riksarkivet-NAD]] * [[phab:project/view/3395/|RunningStat]] * [[phab:project/view/1449/|Scap]] * [[phab:project/view/2283/|ScopedCallback]] * [[phab:project/view/4051/|Scribe]] * SDAW ** [[phab:project/view/4899/|SDAW-MediaSearch]] ** [[phab:project/view/5877/|SDAW-Search-Improvements]] ** [[phab:project/view/5979/|SDAW-SearchVue]] * [[phab:project/view/34/|SDC General]] * SDC ** [[phab:project/view/3936/|SDC-Statements]] * Search ** [[phab:project/view/5882/|Search-Console-access-request]] * [[phab:project/view/3915/|Section Editing (Mobile)]] * Section ** [[phab:project/view/6012/|Section-Level-Image-Suggestions]] ** [[phab:project/view/4668/|Section-Name-Diff]] ** [[phab:project/view/6013/|Section-Topics]] * [[phab:project/view/4909/|SectionTranslation]] * [[phab:project/view/4430/|Security Architecture Tooling]] * [[phab:project/view/4428/|Security Awareness]] * [[phab:project/view/4424/|Security Incident Response]] * [[phab:project/view/4423/|Security policy and procedure]] * [[phab:project/view/4466/|Security Preview]] * [[phab:project/view/4421/|Security Risk Management]] * [[phab:project/view/4427/|Security Supplier Assessments]] * [[phab:project/view/4429/|Security Team AppSec]] * Security ** [[phab:project/view/5870/|Security-API-Service]] * [[phab:project/view/976/|Sentry]] * Server ** [[phab:project/view/5629/|Server-side-upload-request]] * service ** [[phab:project/view/1062/|service-runner]] ** [[phab:project/view/1072/|service-template-node]] * [[phab:project/view/5125/|Shellbox]] * Shop ** [[phab:project/view/913/|Shop-Theme]] * [[phab:project/view/620/|ShoutWiki Calendar]] * [[phab:project/view/5310/|ShoutWikiAds]] * Show ** [[phab:project/view/5954/|Show-Recent-Block-History-for-IPs-and-Ranges-Wish-2022]] * [[phab:project/view/5773/|Similar Editors]] * [[phab:project/view/186/|SiteMatrix]] * [[phab:project/view/875/|SiteMetrics]] * Small ** [[phab:project/view/4657/|Small-Wiki-Toolkits]] * [[phab:project/view/326/|SocialProfile]] * [[phab:project/view/4418/|SonarQube Bot]] * [[phab:project/view/3476/|Soweego]] * [[phab:project/view/192/|SpamBlacklist]] * [[phab:project/view/2383/|SpamRegex]] * [[phab:project/view/5674/|Special:NewLexeme revival]] * [[phab:project/view/903/|SpellingDictionary]] * [[phab:project/view/5222/|Spicerack]] * [[phab:project/view/1928/|Splash]] * [[phab:project/view/4544/|SRE Program Management]] * SRE ** [[phab:project/view/956/|SRE-Access-Requests]] ** [[phab:project/view/76/|SRE-swift-storage]] ** [[phab:project/view/1828/|SRE-tools]] * [[phab:project/view/1364/|Stashbot]] * [[phab:project/view/3903/|Status]] * [[phab:project/view/1821/|stewardbots]] * [[phab:project/view/2134/|Striker]] * [[phab:project/view/3633/|Structured Data Engineering]] * [[phab:project/view/657/|StructuredDiscussions]] * [[phab:project/view/5633/|SuenaWiki Reloaded]] * [[phab:project/view/2340/|Suggestor]] * [[phab:project/view/5683/|Superset]] * [[phab:project/view/3542/|SVG Translate Tool]] * [[phab:project/view/277/|SyntaxHighlight]] * [[phab:project/view/4237/|Talk Pages]] * [[phab:project/view/1582/|TaxonBot]] * Tech ** [[phab:project/view/4953/|Tech-Product API Roadmap]] * [[phab:project/view/4610/|Technical blog]] * Technical ** [[phab:project/view/4654/|Technical-blog-posts]] ** [[phab:project/view/2235/|Technical-Tool-Request]] * [[phab:project/view/638/|TemplateData]] * [[phab:project/view/1932/|TemplateStyles]] * Test ** [[phab:project/view/5022/|Test-Grounds]] * [[phab:project/view/747/|TextExtracts]] * [[phab:project/view/1771/|Texvcjs]] * [[phab:project/view/5678/|Teyora]] * Thank ** [[phab:project/view/4977/|Thank-You-Page]] * [[phab:project/view/628/|Thanks]] * The ** [[phab:project/view/1690/|The-Wikipedia-Adventure]] * [[phab:project/view/1388/|Theme]] * [[phab:project/view/4426/|Threat Modeling]] * [[phab:project/view/1672/|Thumbor]] * [[phab:project/view/5851/|Thumbor Migration]] * [[phab:project/view/299/|TimedMediaHandler]] ** [[phab:project/view/1590/|TimedMediaHandler-TimedText]] ** [[phab:project/view/1591/|TimedMediaHandler-Transcode]] * [[phab:project/view/1912/|Timeless]] * [[phab:project/view/292/|TitleBlacklist]] * [[phab:project/view/2423/|tofawiki]] * Tool ** [[phab:project/view/3261/|Tool-admin]] ** [[phab:project/view/5356/|Tool-ameisenbot]] ** [[phab:project/view/1138/|Tool-anagrimes]] ** [[phab:project/view/762/|Tool-Article-request]] ** [[phab:project/view/1290/|Tool-Attribution-Generator]] ** [[phab:project/view/5166/|Tool-bodh]] ** [[phab:project/view/5355/|Tool-botmahmood]] ** [[phab:project/view/6018/|Tool-boxybot]] ** [[phab:project/view/4955/|Tool-bridgebot]] ** [[phab:project/view/4889/|Tool-commonsapi]] ** [[phab:project/view/4968/|Tool-cycling-init-bot]] ** [[phab:project/view/5401/|Tool-deploy-commands]] * tool ** [[phab:project/view/5936/|tool-docs]] * Tool ** [[phab:project/view/5350/|Tool-drift-tracker]] ** [[phab:project/view/775/|Tool-Erwin's-tools]] ** [[phab:project/view/5058/|Tool-explore-TopicContribs]] ** [[phab:project/view/4010/|Tool-extjsonuploader]] ** [[phab:project/view/2834/|Tool-fatameh]] ** [[phab:project/view/4052/|Tool-flickrdash]] ** [[phab:project/view/4972/|Tool-g8-patrol]] ** [[phab:project/view/5290/|Tool-gawa]] ** [[phab:project/view/986/|Tool-Gerrit-Patch-Uploader]] ** [[phab:project/view/4053/|Tool-global-search]] ** [[phab:project/view/766/|Tool-Global-user-contributions]] ** [[phab:project/view/5211/|Tool-image-content-filtration]] ** [[phab:project/view/5135/|Tool-infogeek244-grammabot]] ** [[phab:project/view/4059/|Tool-inteGraality]] ** [[phab:project/view/5348/|Tool-ip]] ** [[phab:project/view/5295/|Tool-itwiki]] ** [[phab:project/view/5333/|Tool-klexiboxen]] ** [[phab:project/view/5955/|Tool-kuwikibot]] ** [[phab:project/view/3999/|Tool-ldap]] ** [[phab:project/view/5342/|Tool-leksem-indonesia]] ** [[phab:project/view/708/|Tool-lists]] ** [[phab:project/view/5182/|Tool-logo-test]] ** [[phab:project/view/5330/|Tool-lokasbot]] ** [[phab:project/view/4678/|Tool-MajavahBot]] ** [[phab:project/view/750/|Tool-Matthewrbowker's-tools]] ** [[phab:project/view/4771/|Tool-mdvt]] ** [[phab:project/view/773/|Tool-meetbot]] ** [[phab:project/view/4746/|Tool-MoeData]] ** [[phab:project/view/112/|Tool-nlwikibots]] ** [[phab:project/view/5016/|Tool-openstack-browser]] ** [[phab:project/view/2045/|Tool-Pageviews]] ** [[phab:project/view/6054/|Tool-pdlarcher]] ** [[phab:project/view/2159/|Tool-Phabricator-bug-status]] ** [[phab:project/view/5049/|Tool-rangeblockfinder]] ** [[phab:project/view/5987/|Tool-rc-discord]] ** [[phab:project/view/5013/|Tool-refill]] ** [[phab:project/view/5549/|Tool-sbdjwhsh]] ** [[phab:project/view/5037/|Tool-search-filters]] ** [[phab:project/view/5138/|Tool-socks]] ** [[phab:project/view/4235/|Tool-spacemedia]] * tool ** [[phab:project/view/5673/|tool-sql-optimizer]] * Tool ** [[phab:project/view/5085/|Tool-sqlchecker]] ** [[phab:project/view/4988/|Tool-suggestbotbn]] ** [[phab:project/view/5425/|Tool-test-stats]] ** [[phab:project/view/5518/|Tool-topictagging]] ** [[phab:project/view/743/|Tool-tsreports]] ** [[phab:project/view/4956/|Tool-wiki-importer]] ** [[phab:project/view/5056/|Tool-wikiauthbot]] ** [[phab:project/view/1262/|Tool-Wikidata-Periodic-Table]] ** [[phab:project/view/1847/|Tool-wikiloves]] * tool ** [[phab:project/view/3758/|tool-ws-cat-browser]] ** [[phab:project/view/3422/|tool-wscontest]] * Tool ** [[phab:project/view/5325/|Tool-zhwpvg-article-list]] * [[phab:project/view/539/|Toolforge]] * [[phab:project/view/5596/|Toolforge Build Service]] * [[phab:project/view/5969/|Toolforge Jobs framework]] * [[phab:project/view/5196/|ToolforgeBundle]] * [[phab:project/view/3224/|Toolhub]] * tox ** [[phab:project/view/4548/|tox-wikimedia]] * [[phab:project/view/2263/|Truglass]] * Twinkle ** [[phab:project/view/5589/|Twinkle-on-Turkish-Wikipedia]] * Twitter ** [[phab:project/view/4176/|Twitter-to-Commons]] * Two ** [[phab:project/view/2277/|Two-Column-Edit-Conflict-Merge]] * UI ** [[phab:project/view/24/|UI-Standardization]] * ULS ** [[phab:project/view/1116/|ULS-CompactLinks]] * UNESCO ** [[phab:project/view/2761/|UNESCO-Wikimedian-in-Residence]] * [[phab:project/view/442/|UniversalLanguageSelector]] * [[phab:project/view/2204/|UnusedRedirects]] * [[phab:project/view/402/|UploadWizard]] * [[phab:project/view/2386/|uprightdiff]] * [[phab:project/view/4324/|urbanecmbot]] * User ** [[phab:project/view/2853/|User-Testing]] * [[phab:project/view/2268/|UserStatus]] * [[phab:project/view/1069/|utfnormal]] * Utilities ** [[phab:project/view/446/|Utilities-code-utils]] ** [[phab:project/view/753/|Utilities-grabbers]] ** [[phab:project/view/251/|Utilities-mwdumper]] ** [[phab:project/view/864/|Utilities-UnicodeJS]] * [[phab:project/view/4269/|Vabatahtlikule]] * [[phab:project/view/918/|ValueView]] * [[phab:project/view/166/|Vector]] * Video (non ** [[phab:project/view/1827/|Video (non-WMF)]] * [[phab:project/view/2141/|video2commons]] * [[phab:project/view/4054/|VideoCutTool]] * [[phab:project/view/4375/|VideoJS player]] * [[phab:project/view/3383/|VisualCategories]] * VisualEditor ** [[phab:project/view/480/|VisualEditor-ContentEditable]] ** [[phab:project/view/499/|VisualEditor-ContentLanguage]] ** [[phab:project/view/898/|VisualEditor-CopyPaste]] ** [[phab:project/view/503/|VisualEditor-DataModel]] ** [[phab:project/view/4171/|VisualEditor-Edit Cards ]] ** [[phab:project/view/486/|VisualEditor-EditingTools]] ** [[phab:project/view/612/|VisualEditor-Initialisation]] ** [[phab:project/view/899/|VisualEditor-InterfaceLanguage]] ** [[phab:project/view/1268/|VisualEditor-LanguageTool]] ** [[phab:project/view/1020/|VisualEditor-Links]] ** [[phab:project/view/1021/|VisualEditor-Media]] ** [[phab:project/view/484/|VisualEditor-MediaWiki]] ** [[phab:project/view/2301/|VisualEditor-MediaWiki-2017WikitextEditor]] ** [[phab:project/view/830/|VisualEditor-MediaWiki-Links]] ** [[phab:project/view/828/|VisualEditor-MediaWiki-Media]] ** [[phab:project/view/515/|VisualEditor-MediaWiki-Mobile]] ** [[phab:project/view/1019/|VisualEditor-MediaWiki-Plugins]] ** [[phab:project/view/827/|VisualEditor-MediaWiki-References]] ** [[phab:project/view/829/|VisualEditor-MediaWiki-Templates]] ** [[phab:project/view/4111/|VisualEditor-Mobile-UsabilityImprovements]] ** [[phab:project/view/831/|VisualEditor-Performance]] ** [[phab:project/view/826/|VisualEditor-Tables]] ** [[phab:project/view/2710/|VisualEditor-VisualDiffs]] * vm ** [[phab:project/view/1234/|vm-requests]] * [[phab:project/view/729/|VoteNY]] * VPS ** [[phab:project/view/3158/|VPS-project-Codesearch]] ** [[phab:project/view/819/|VPS-project-Extdist]] ** [[phab:project/view/2825/|VPS-project-icinga2]] ** [[phab:project/view/2103/|VPS-project-Phabricator]] ** [[phab:project/view/5497/|VPS-Project-wikicommunityhealth]] ** [[phab:project/view/543/|VPS-project-Wikistats]] * [[phab:project/view/5725/|vrts]] * [[phab:project/view/5602/|Vue.js]] * [[phab:project/view/4431/|Vulnerability Management]] * [[phab:project/view/2284/|WaitConditionLoop]] * [[phab:project/view/4340/|WatchTranslations]] * WDQS ** [[phab:project/view/3027/|WDQS-Optimizer]] * wdwb ** [[phab:project/view/3532/|wdwb-tech]] * [[phab:project/view/3165/|Weapon of Mass Description]] * [[phab:project/view/5933/|Web Team Visual Regression Framework]] * Web2Cit ** [[phab:project/view/5669/|Web2Cit-Community]] ** [[phab:project/view/5670/|Web2Cit-Core]] ** [[phab:project/view/5760/|Web2Cit-Editor]] ** [[phab:project/view/5929/|Web2Cit-Gadget]] ** [[phab:project/view/5810/|Web2Cit-Monitor]] ** [[phab:project/view/5668/|Web2Cit-Research]] ** [[phab:project/view/5689/|Web2Cit-Server]] * [[phab:project/view/3619/|WebPageReplay]] * [[phab:project/view/1777/|WebPageTest]] * Who ** [[phab:project/view/3836/|Who-Wrote-That]] * Wiki Loves Monuments FY 2021 ** [[phab:project/view/5708/|Wiki Loves Monuments FY 2021-2022]] * Wiki Loves Monuments FY 2022 ** [[phab:project/view/5709/|Wiki Loves Monuments FY 2022-2023]] * Wiki ** [[phab:project/view/4042/|Wiki-goes-Caribbean]] ** [[phab:project/view/545/|Wiki-Loves-Monuments-Database]] ** [[phab:project/view/550/|Wiki-Loves-Monuments-Sources]] ** [[phab:project/view/2941/|Wiki-Setup]] * [[phab:project/view/5505/|Wiki2Reveal]] * [[phab:project/view/2341/|WikiApiary]] * [[phab:project/view/385/|WikiArticleFeeds]] * [[phab:project/view/2909/|wikiba.se website]] * [[phab:project/view/17/|Wikibase (3rd party installations)]] * Wikibase ** [[phab:project/view/4930/|Wikibase - Automated Configuration Detection (WikibaseManifest)]] ** [[phab:project/view/4604/|Wikibase - Federated Properties]] * [[phab:project/view/5094/|Wikibase and Wikidata Architecture Overview]] * [[phab:project/view/5513/|Wikibase change dispatching scripts to jobs]] * [[phab:project/view/5958/|Wikibase Cloud Test]] * [[phab:project/view/5307/|Wikibase OPEN!NEXT]] * [[phab:project/view/5095/|Wikibase Pingback]] * [[phab:project/view/5771/|Wikibase Product Platform]] * [[phab:project/view/5063/|Wikibase Release Strategy]] * [[phab:project/view/5003/|Wikibase REST API Schema]] * [[phab:project/view/5755/|Wikibase Suite]] * Wikibase ** [[phab:project/view/920/|Wikibase-DataModel]] ** [[phab:project/view/923/|Wikibase-DataModel-JavaScript]] ** [[phab:project/view/922/|Wikibase-DataModel-Serialization]] ** [[phab:project/view/1335/|Wikibase-DataModel-Services]] ** [[phab:project/view/921/|Wikibase-Internal-Serialization]] ** [[phab:project/view/925/|Wikibase-JavaScript-Api]] ** [[phab:project/view/3336/|Wikibase-Lua]] ** [[phab:project/view/1202/|Wikibase-Quality-Constraints]] ** [[phab:project/view/3363/|Wikibase-registry]] ** [[phab:project/view/919/|Wikibase-Serialization-JavaScript]] * [[phab:project/view/5563/|Wikibase.cloud]] * [[phab:project/view/1816/|WikibaseMediaInfo]] * [[phab:project/view/36/|Wikibugs]] * [[phab:project/view/1641/|WikiCategoryTagCloud]] * [[phab:project/view/1608/|WikiCite]] * Wikidata ** [[phab:project/view/4817/|Wikidata - DS hike]] ** [[phab:project/view/4635/|Wikidata - Reference Treasure Hunt]] ** [[phab:project/view/5200/|Wikidata - Visualisation of Reliability Metrics]] * [[phab:project/view/5408/|Wikidata Analytics]] * [[phab:project/view/4521/|Wikidata Design System]] * [[phab:project/view/3404/|Wikidata Mobile]] * [[phab:project/view/4990/|Wikidata Query Builder]] * [[phab:project/view/2901/|Wikidata Query UI]] * [[phab:project/view/5068/|Wikidata subsets cloud & interop]] * [[phab:project/view/4242/|Wikidata Tainted References]] * Wikidata ** [[phab:project/view/4074/|Wikidata-Bridge]] ** [[phab:project/view/1278/|Wikidata-Gadgets]] ** [[phab:project/view/1158/|Wikidata-Page-Banner]] ** [[phab:project/view/2788/|Wikidata-primary-sources]] ** [[phab:project/view/891/|Wikidata-Query-Service]] ** [[phab:project/view/3620/|Wikidata-Termbox]] * [[phab:project/view/125/|Wikidata.org]] * [[phab:project/view/270/|wikidiff2]] * [[phab:project/view/3394/|Wikidocumentaries]] * [[phab:project/view/342/|WikiEditor]] * [[phab:project/view/4110/|Wikifeeds]] * [[phab:project/view/469/|WikiForum]] * [[phab:project/view/183/|WikiHiero]] * [[phab:project/view/1466/|Wikilabels]] * [[phab:project/view/5275/|WikiLambda]] * Wikilink ** [[phab:project/view/4082/|Wikilink-Tool]] * [[phab:project/view/445/|WikiLove]] * wikimaps ** [[phab:project/view/1886/|wikimaps-warper]] * [[phab:project/view/3215/|Wikimedia Australia]] * [[phab:project/view/4948/|Wikimedia Chat]] * [[phab:project/view/1016/|Wikimedia Design Style Guide]] * [[phab:project/view/5642/|Wikimedia Enterprise DevOps]] * [[phab:project/view/5520/|Wikimedia Enterprise Discussion]] * [[phab:project/view/5777/|Wikimedia Enterprise Engineering]] * [[phab:project/view/5684/|Wikimedia Enterprise External Request]] * [[phab:project/view/5579/|Wikimedia Enterprise Infrastructure v2]] * [[phab:project/view/5778/|Wikimedia Enterprise Modeling]] * [[phab:project/view/5610/|Wikimedia Enterprise QA]] * [[phab:project/view/5578/|Wikimedia Enterprise SSO]] * [[phab:project/view/5577/|Wikimedia Enterprise Uptime Monitoring]] * [[phab:project/view/5569/|Wikimedia Enterprise Web Application]] * [[phab:project/view/4729/|Wikimedia Meet]] * [[phab:project/view/4739/|Wikimedia OCR]] * [[phab:project/view/1871/|Wikimedia Resource Center]] * Wikimedia ** [[phab:project/view/4752/|Wikimedia-abusefilter-global-maintainers]] ** [[phab:project/view/5185/|Wikimedia-Affiliates-Data-Portal]] ** [[phab:project/view/382/|Wikimedia-Apache-configuration]] ** [[phab:project/view/152/|Wikimedia-Bugzilla]] ** [[phab:project/view/1024/|Wikimedia-Cdb]] ** [[phab:project/view/2479/|Wikimedia-CentralNotice-Administration]] ** [[phab:project/view/4941/|Wikimedia-Developer-Portal]] ** [[phab:project/view/447/|Wikimedia-Etherpad]] ** [[phab:project/view/188/|Wikimedia-Extension-setup]] ** [[phab:project/view/2893/|Wikimedia-FR-Tech-Projects]] ** [[phab:project/view/2892/|Wikimedia-FR-Tech-Systems]] ** [[phab:project/view/2715/|Wikimedia-Fundraising-Banners]] ** [[phab:project/view/1130/|Wikimedia-Fundraising-Campaigns]] ** [[phab:project/view/404/|Wikimedia-Fundraising-CiviCRM]] ** [[phab:project/view/1524/|Wikimedia-GitHub]] ** [[phab:project/view/815/|Wikimedia-IEG-grant-review]] ** [[phab:project/view/143/|Wikimedia-Interwiki-links]] * wikimedia ** [[phab:project/view/2751/|wikimedia-irc-libera]] * Wikimedia ** [[phab:project/view/227/|Wikimedia-IRC-RC-Server]] ** [[phab:project/view/179/|Wikimedia-Language-setup]] ** [[phab:project/view/772/|Wikimedia-Logstash]] ** [[phab:project/view/190/|Wikimedia-Mailing-lists]] ** [[phab:project/view/5193/|Wikimedia-Minify]] * wikimedia ** [[phab:project/view/2729/|wikimedia-page-library]] * Wikimedia ** [[phab:project/view/2666/|Wikimedia-Phabricator-Extensions]] ** [[phab:project/view/413/|Wikimedia-Planet]] ** [[phab:project/view/1619/|Wikimedia-Portals]] ** [[phab:project/view/165/|Wikimedia-Rdbms]] ** [[phab:project/view/178/|Wikimedia-Site-requests]] ** [[phab:project/view/5625/|Wikimedia-Small-Projects-User-Group-Projects]] ** [[phab:project/view/211/|Wikimedia-SVG-rendering]] ** [[phab:project/view/2949/|Wikimedia-Takedown-Tools]] ** [[phab:project/view/4853/|Wikimedia-Tech-Talks]] ** [[phab:project/view/2285/|Wikimedia-Timestamp]] ** [[phab:project/view/1255/|Wikimedia-Video]] ** [[phab:project/view/740/|Wikimedia-Wikimania-Scholarships]] * [[phab:project/view/536/|wikimedia.biterg.io]] * [[phab:project/view/4822/|WikimediaApiPortal]] * [[phab:project/view/4924/|WikimediaDebug]] * [[phab:project/view/3907/|WikimediaEditorTasks]] * [[phab:project/view/3496/|wikimediafoundation.org]] * [[phab:project/view/426/|WikimediaMessages]] * WikimediaUI ** [[phab:project/view/5064/|WikimediaUI-Base]] * [[phab:project/view/5220/|Wikimini.org]] * [[phab:project/view/3314/|Wikinity]] * Wikipedia ** [[phab:project/view/4393/|Wikipedia-Preview]] * [[phab:project/view/4156/|wikipedia.de]] * [[phab:project/view/4090/|WikiPEG]] * [[phab:project/view/3857/|Wikiportrait]] * WikiProject ** [[phab:project/view/3493/|WikiProject-Biodiversity]] ** [[phab:project/view/3356/|WikiProject-ShEx]] ** [[phab:project/view/1640/|WikiProject-tools]] * [[phab:project/view/5868/|WikiSEO]] * Wikispeech ** [[phab:project/view/4379/|Wikispeech-Jobrunner]] ** [[phab:project/view/4349/|Wikispeech-Speech-Data-Collector]] ** [[phab:project/view/4344/|Wikispeech-Text-to-Speech]] * [[phab:project/view/4250/|Wikispore]] * [[phab:project/view/5564/|Wikistories]] * [[phab:project/view/531/|wikitech.wikimedia.org]] * [[phab:project/view/871/|WikiTextLoggedInOut]] * [[phab:project/view/5672/|WikiWho]] * WLM ** [[phab:project/view/4325/|WLM-Italy-Finder]] ** [[phab:project/view/4327/|WLM-Italy-Finder-App]] ** [[phab:project/view/4326/|WLM-Italy-Stats]] * WLX ** [[phab:project/view/1741/|WLX-Jury]] * WM ** [[phab:project/view/668/|WM-Bot]] ** [[phab:project/view/4782/|WMCH-Cronos]] ** [[phab:project/view/4830/|WMCH-Infrastructure]] ** [[phab:project/view/4799/|WMCH-Minipedia]] ** [[phab:project/view/3712/|WMCZ-General]] ** [[phab:project/view/5305/|WMCZ-Stats]] ** [[phab:project/view/3391/|WMCZ-Tracker]] ** [[phab:project/view/4399/|WMCZ-Web]] ** [[phab:project/view/5928/|WMDE-FUN-Tech-Payment-Refactoring]] ** [[phab:project/view/1688/|WMDE-Fundraising-Tech]] ** [[phab:project/view/5559/|WMDE-GeoInfo-FocusArea]] ** [[phab:project/view/2821/|WMDE-New-Editors-Banner-Campaigns]] * wmde ** [[phab:project/view/5865/|wmde-team-b-tech]] * WMDE ** [[phab:project/view/1702/|WMDE-Tech-Communication-Mentoring-And-Events]] ** [[phab:project/view/5892/|WMDE-technical-needs-from-WMF]] ** [[phab:project/view/4529/|WMDE-Templates-FocusArea]] * wmde ** [[phab:project/view/5864/|wmde-wikidata-tech]] * [[phab:project/view/3609/|WMEE 101+]] * WMEE ** [[phab:project/view/3560/|WMEE-gen]] * WMF ** [[phab:project/view/42/|WMF-Annual-Report]] ** [[phab:project/view/151/|WMF-General-or-Unknown]] ** [[phab:project/view/811/|WMF-JobQueue]] ** [[phab:project/view/5595/|WMF-Safety-Survey]] * wmf ** [[phab:project/view/4861/|wmf-sre-laptop]] ** [[phab:project/view/4627/|wmfdata-python]] * [[phab:project/view/5611/|wmfdb]] * WMIT ** [[phab:project/view/5827/|WMIT-CiviCRM]] ** [[phab:project/view/5047/|WMIT-Infrastructure]] ** [[phab:project/view/5241/|WMIT-LimeSurvey]] * WMNO ** [[phab:project/view/3255/|WMNO-General]] ** [[phab:project/view/5459/|WMNO-Knowledge-Equity]] ** [[phab:project/view/3141/|WMNO-Sámi]] * WMSE ** [[phab:project/view/5741/|WMSE-A-Community-for-Everybody-2022]] ** [[phab:project/view/5731/|WMSE-Advocacy-2022]] ** [[phab:project/view/5745/|WMSE-Association-Involvement-2022]] ** [[phab:project/view/5734/|WMSE-Bug-Reporting-and-Translation-2022]] ** [[phab:project/view/5738/|WMSE-Community-Support-2022]] ** [[phab:project/view/5440/|WMSE-Content-partnerships-support-2021]] ** [[phab:project/view/5445/|WMSE-Content-partnerships-support-2021-Capacity-building]] ** [[phab:project/view/5442/|WMSE-Content-partnerships-support-2021-Communication]] ** [[phab:project/view/5446/|WMSE-Content-partnerships-support-2021-Fundraising]] ** [[phab:project/view/5448/|WMSE-Content-partnerships-support-2021-Helpdesk]] ** [[phab:project/view/5444/|WMSE-Content-partnerships-support-2021-IGO/INGO]] ** [[phab:project/view/5441/|WMSE-Content-partnerships-support-2021-Project-management]] ** [[phab:project/view/5443/|WMSE-Content-partnerships-support-2021-Research]] ** [[phab:project/view/5447/|WMSE-Content-partnerships-support-2021-Software-development]] ** [[phab:project/view/5613/|WMSE-Content-partnerships-support-2021-Strategic-data-uploads]] ** [[phab:project/view/5739/|WMSE-Development-Support-2022]] ** [[phab:project/view/5749/|WMSE-Exchange-of-Experiences-2022]] ** [[phab:project/view/5748/|WMSE-Experimental-partnerships-2022]] ** [[phab:project/view/5746/|WMSE-FOSS-for-the-Association-2022]] ** [[phab:project/view/5699/|WMSE-GLAM-2022]] ** [[phab:project/view/5609/|WMSE-International-copyright-2021]] ** [[phab:project/view/5728/|WMSE-Kalmar-läns-museum-2022]] ** [[phab:project/view/5732/|WMSE-Knowledge-in-Crisis-Situations-2022]] ** [[phab:project/view/5608/|WMSE-Lowering-barriers-for-WikiGap-2021]] ** [[phab:project/view/5744/|WMSE-Organisational-Development-2022]] ** [[phab:project/view/5742/|WMSE-Partnerships-for-WikiGap-2022]] ** [[phab:project/view/5730/|WMSE-Presentations-2022]] ** [[phab:project/view/3220/|WMSE-Project-leftovers]] ** [[phab:project/view/3883/|WMSE-SMHI-2019]] ** [[phab:project/view/5747/|WMSE-Supporting-the-European-Hub-2022]] ** [[phab:project/view/5737/|WMSE-Trust-Making-2022]] ** [[phab:project/view/5733/|WMSE-Visibility-Making-2022]] ** [[phab:project/view/5740/|WMSE-Wiki-Loves-2022]] ** [[phab:project/view/5107/|WMSE-Wikidata-for-authority-control-2021]] ** [[phab:project/view/5743/|WMSE-Wikipedia-for-All-of-Sweden-2022]] ** [[phab:project/view/5729/|WMSE-Wikipedia-in-Education-2022]] ** [[phab:project/view/4447/|WMSE-Wikispeech-for-AI-2020]] ** [[phab:project/view/5735/|WMSE-Wikispeech-Maintenance-and-Support-2022]] ** [[phab:project/view/5736/|WMSE-Wikispeech-Speech-Data-Collector-Tool-2022]] * [[phab:project/view/2764/|WoOgLeShades]] * [[phab:project/view/4842/|WPCleaner]] * [[phab:project/view/4979/|WPtouch]] * [[phab:project/view/3514/|WrappedString]] * [[phab:project/view/3917/|WS Export]] * [[phab:project/view/4898/|WVUI]] * [[phab:project/view/1182/|XAnalytics]] * [[phab:project/view/4987/|XMPReader]] * [[phab:project/view/803/|XTools]] * [[phab:project/view/210/|Znuny]] === Umbrella projects === * [[phab:project/view/1887/|BlueSpice]] * Cloud ** [[phab:project/view/832/|Cloud-Services]] * Google ** [[phab:project/view/2540/|Google-Summer-of-Code]] * LDAP ** [[phab:project/view/3071/|LDAP-Extensions]] * MediaWiki ** [[phab:project/view/1539/|MediaWiki-Releasing]] ** [[phab:project/view/5614/|MediaWiki-SettingsBuilder]] * [[phab:project/view/4085/|OpenRefine]] * [[phab:project/view/2206/|Outreachy]] * [[phab:project/view/5460/|Platform Engineering Code Jam]] * Projects ** [[phab:project/view/2829/|Projects-Cleanup]] * [[phab:project/view/2334/|Reading Epics]] * Recurring ** [[phab:project/view/1311/|Recurring-Donations]] * [[phab:project/view/2453/|Release Pipeline]] * [[phab:project/view/3610/|rsc assessment]] * Security ** [[phab:project/view/4420/|Security-Team-Services]] * [[phab:project/view/3789/|Shape Expressions]] * Social ** [[phab:project/view/1009/|Social-Tools]] * [[phab:project/view/3632/|StructuredDataOnCommons]] * [[phab:project/view/1696/|Teahouse]] * [[phab:project/view/5976/|The Signpost]] * [[phab:project/view/703/|Tools]] * [[phab:project/view/483/|VisualEditor]] * VPS ** [[phab:project/view/525/|VPS-Projects]] * [[phab:project/view/5081/|wbstack]] * [[phab:project/view/5593/|Web2Cit]] * Wiki ** [[phab:project/view/575/|Wiki-Loves-Monuments]] ** [[phab:project/view/3345/|Wikibase-UserGroup]] * [[phab:project/view/71/|Wikidata]] * [[phab:project/view/2292/|Wikidata Lexicographical data]] * [[phab:project/view/1663/|Wikispeech]] * WMDE ** [[phab:project/view/3133/|WMDE-Blueprint-tickets]] ** [[phab:project/view/3295/|WMDE-TechWish-Maintenance]] ** [[phab:project/view/5799/|WMDE-TechWish-Survey]] * [[phab:project/view/4636/|WMEE]] * [[phab:project/view/4034/|WMFI]] * [[phab:project/view/3128/|WMNO]] * [[phab:project/view/2480/|WMSE]] === Tags === * [[phab:project/view/171/|Accessibility]] * affects ** [[phab:project/view/5266/|affects-Daty]] ** [[phab:project/view/4381/|affects-Kiwix-and-openZIM]] ** [[phab:project/view/6000/|affects-Scribe-Keyboards]] ** [[phab:project/view/4298/|affects-translatewiki.net]] * artificial ** [[phab:project/view/2454/|artificial-intelligence]] * audits ** [[phab:project/view/1317/|audits-data-retention]] * [[phab:project/view/4716/|AWS]] * Bengali ** [[phab:project/view/2393/|Bengali-Sites]] * Beta ** [[phab:project/view/1563/|Beta-Cluster-reproducible]] ** [[phab:project/view/58/|Beta-Feature]] * Browser ** [[phab:project/view/1298/|Browser-Support-Android-Google-Chrome]] ** [[phab:project/view/350/|Browser-Support-Apple-Safari]] ** [[phab:project/view/284/|Browser-Support-Firefox]] ** [[phab:project/view/362/|Browser-Support-Google-Chrome]] ** [[phab:project/view/164/|Browser-Support-Internet-Explorer]] ** [[phab:project/view/4575/|Browser-Support-KaiOS]] ** [[phab:project/view/1433/|Browser-Support-Microsoft-Edge]] ** [[phab:project/view/233/|Browser-Support-Opera]] ** [[phab:project/view/4456/|Browser-support-print-media]] ** [[phab:project/view/1617/|Browser-Tests]] * [[phab:project/view/4922/|castor]] * Chinese ** [[phab:project/view/2409/|Chinese-Sites]] * ci ** [[phab:project/view/4177/|ci-test-error]] * Cloud ** [[phab:project/view/5638/|Cloud-Services-Origin-Alert]] ** [[phab:project/view/5639/|Cloud-Services-Origin-Team]] ** [[phab:project/view/5637/|Cloud-Services-Origin-User]] ** [[phab:project/view/5635/|Cloud-Services-Worktype-Maintenance]] ** [[phab:project/view/5634/|Cloud-Services-Worktype-Project]] ** [[phab:project/view/5636/|Cloud-Services-Worktype-Unplanned]] * Code ** [[phab:project/view/3310/|Code-Health]] ** [[phab:project/view/4622/|Code-Health-DevEd]] ** [[phab:project/view/4720/|Code-Health-DevEd-Curriculum]] ** [[phab:project/view/3670/|Code-Health-Help-Wanted]] ** [[phab:project/view/5000/|Code-Health-Objective]] ** [[phab:project/view/4168/|Code-Health-Office-Hours]] ** [[phab:project/view/3144/|Code-Stewardship-Reviews]] * Community ** [[phab:project/view/175/|Community-consensus-needed]] ** [[phab:project/view/1482/|Community-Wishlist-Survey-2015]] ** [[phab:project/view/2420/|Community-Wishlist-Survey-2016]] ** [[phab:project/view/3078/|Community-Wishlist-Survey-2017]] * [[phab:project/view/1093/|Composer]] * [[phab:project/view/4365/|ContentSecurityPolicy]] * covid ** [[phab:project/view/4648/|covid-19]] * Croatian ** [[phab:project/view/5624/|Croatian-Sites]] * [[phab:project/view/145/|Crosswiki]] * [[phab:project/view/2149/|CSS]] * Dagbani ** [[phab:project/view/5538/|Dagbani-Sites]] * Datacenter ** [[phab:project/view/3571/|Datacenter-Switchover]] * [[phab:project/view/4656/|Dependency injection]] * [[phab:project/view/157/|Design]] * [[phab:project/view/4096/|Desktop]] * [[phab:project/view/3521/|Developer Productivity]] * Developer ** [[phab:project/view/1098/|Developer-notice]] * [[phab:project/view/987/|Documentation]] * EngProd ** [[phab:project/view/4773/|EngProd-Virtual-Hackathon]] * [[phab:project/view/942/|Epic]] * Esperanto ** [[phab:project/view/1775/|Esperanto-Sites]] * [[phab:project/view/2552/|events]] * FR ** [[phab:project/view/2062/|FR-Email]] ** [[phab:project/view/1654/|FR-Fraud]] * Gender ** [[phab:project/view/3108/|Gender-Support]] * [[phab:project/view/169/|good first task]] * [[phab:project/view/81/|Graphite]] * Gujarati ** [[phab:project/view/4825/|Gujarati-Sites]] * Hindi ** [[phab:project/view/2418/|Hindi-Sites]] * [[phab:project/view/5351/|HTML5]] * [[phab:project/view/162/|HTTPS]] * Hungarian ** [[phab:project/view/5693/|Hungarian-Sites]] * [[phab:project/view/156/|I18n]] * IABot ** [[phab:project/view/6003/|IABot-Priority-2022]] ** [[phab:project/view/6004/|IABot-Priority-Eastern-Europe-Former-USSR]] * [[phab:project/view/184/|IPv6]] * IRC ** [[phab:project/view/1773/|IRC-Meetings]] * [[phab:project/view/267/|JavaScript]] * [[phab:project/view/83/|Jenkins]] * [[phab:project/view/2361/|Kubernetes]] * [[phab:project/view/4981/|Language codes]] * [[phab:project/view/982/|LDAP]] * [[phab:project/view/3827/|Logos]] * Malayalam ** [[phab:project/view/2417/|Malayalam-Sites]] * mariadb ** [[phab:project/view/4313/|mariadb-optimizer-bug]] * [[phab:project/view/2691/|Microcontribution]] * [[phab:project/view/372/|Mobile]] * [[phab:project/view/1096/|Notice]] * Pageviews ** [[phab:project/view/3905/|Pageviews-Anomaly]] * [[phab:project/view/1852/|Paper]] * Patch ** [[phab:project/view/1825/|Patch-Needs-Improvement]] * patch ** [[phab:project/view/418/|patch-welcome]] * [[phab:project/view/196/|Performance Issue]] * Performance ** [[phab:project/view/1559/|Performance-Team-publish]] * periodic ** [[phab:project/view/2807/|periodic-update]] * [[phab:project/view/3825/|PermanentlyPrivate]] * Persona ** [[phab:project/view/1803/|Persona-Active-Editor]] ** [[phab:project/view/1801/|Persona-Active-Reader]] ** [[phab:project/view/1800/|Persona-Casual-Reader]] ** [[phab:project/view/1802/|Persona-New-Editor]] ** [[phab:project/view/1804/|Persona-Power-Editor]] ** [[phab:project/view/1805/|Persona-Vandal]] * [[phab:project/view/3267/|PHP 7.2 support]] * [[phab:project/view/3494/|PHP 7.3 support]] * [[phab:project/view/4107/|PHP 7.4 support]] * [[phab:project/view/4652/|PHP 8.0 support]] * [[phab:project/view/5132/|PHP 8.1 support]] * [[phab:project/view/6053/|PHP 8.2 support]] * [[phab:project/view/4665/|Pikk plaan]] * Plural ** [[phab:project/view/3172/|Plural-Support]] * [[phab:project/view/4411/|PM]] * [[phab:project/view/2339/|PostgreSQL]] * [[phab:project/view/1205/|Privacy]] * Product ** [[phab:project/view/5001/|Product-Feature]] * [[phab:project/view/1542/|Proposal]] * [[phab:project/view/78/|Puppet]] * Python3 ** [[phab:project/view/4522/|Python3-Porting]] * Pywikibot ** [[phab:project/view/1774/|Pywikibot-Announce]] ** [[phab:project/view/97/|Pywikibot-Documentation]] ** [[phab:project/view/102/|Pywikibot-network]] ** [[phab:project/view/1260/|Pywikibot-RfCs]] ** [[phab:project/view/107/|Pywikibot-tests]] ** [[phab:project/view/110/|Pywikibot-Wikidata]] * Quality ** [[phab:project/view/4342/|Quality-and-Test-Engineering-Office-Hours]] * [[phab:project/view/914/|Regression]] * RESTBase ** [[phab:project/view/837/|RESTBase-architecture]] * [[phab:project/view/4606/|RFS]] * [[phab:project/view/1280/|RTL]] * [[phab:project/view/1618/|Ruby]] * Russian ** [[phab:project/view/2621/|Russian-Sites]] * Schema ** [[phab:project/view/161/|Schema-change]] ** [[phab:project/view/1494/|Schema-change-in-production]] * [[phab:project/view/4493/|SecTeam Discussion]] * SecTeam ** [[phab:project/view/5180/|SecTeam-Processed]] ** [[phab:project/view/5181/|SecTeam-wikimedia-project-event]] * [[phab:project/view/4573/|Security]] * [[phab:project/view/1163/|SEO]] * Serbian ** [[phab:project/view/3791/|Serbian-Sites]] * Service ** [[phab:project/view/838/|Service-Architecture]] ** [[phab:project/view/1305/|Service-deployment-requests]] * [[phab:project/view/4063/|Skipped QA]] * Slow ** [[phab:project/view/5427/|Slow-DB-Query]] * Software ** [[phab:project/view/1443/|Software-Licensing]] * Spanish ** [[phab:project/view/2564/|Spanish-Sites]] * [[phab:project/view/2085/|Spike]] * [[phab:project/view/2752/|SQLite]] * [[phab:project/view/1541/|Story]] * [[phab:project/view/1465/|Surveys]] * [[phab:project/view/1167/|Sustainability]] * [[phab:project/view/5762/|SVG]] * Sysadmin ** [[phab:project/view/1099/|Sysadmin-notice]] * Tamil ** [[phab:project/view/2416/|Tamil-Sites]] * Tech ** [[phab:project/view/3302/|Tech-Ambassadors]] ** [[phab:project/view/609/|Technical-Debt]] * Test ** [[phab:project/view/3223/|Test-Coverage]] ** [[phab:project/view/4524/|Testing-Roadblocks]] * [[phab:project/view/138/|TestMe]] * Thai ** [[phab:project/view/5950/|Thai-Sites]] * [[phab:project/view/2835/|Tor]] * Tracking ** [[phab:project/view/134/|Tracking-Neverending]] * Turkish ** [[phab:project/view/3231/|Turkish-Sites]] * Unplanned ** [[phab:project/view/1318/|Unplanned-Sprint-Work]] * Unstewarded ** [[phab:project/view/5503/|Unstewarded-production-error]] * [[phab:project/view/153/|Upstream]] * User ** [[phab:project/view/1097/|User-notice]] * UX ** [[phab:project/view/3687/|UX-Debt]] * [[phab:project/view/825/|Verified]] * [[phab:project/view/1355/|Voice & Tone]] * Vuln ** [[phab:project/view/1345/|Vuln-Authn/Session]] ** [[phab:project/view/4258/|Vuln-CachePollution]] ** [[phab:project/view/907/|Vuln-CSRF]] ** [[phab:project/view/1340/|Vuln-DirectObjectReference]] ** [[phab:project/view/1446/|Vuln-DoS]] ** [[phab:project/view/908/|Vuln-Infoleak]] ** [[phab:project/view/905/|Vuln-Inject]] ** [[phab:project/view/4260/|Vuln-InsufficientMonitoring]] ** [[phab:project/view/1344/|Vuln-Misconfiguration]] ** [[phab:project/view/1343/|Vuln-MissingAuthz]] ** [[phab:project/view/1341/|Vuln-OpenRedirect]] ** [[phab:project/view/4259/|Vuln-SerDe]] ** [[phab:project/view/1342/|Vuln-VulnComponent]] ** [[phab:project/view/906/|Vuln-XSS]] ** [[phab:project/view/4261/|Vuln-XXE]] * WCAG ** [[phab:project/view/3289/|WCAG-Level-A]] ** [[phab:project/view/3290/|WCAG-Level-AA]] ** [[phab:project/view/3291/|WCAG-Level-AAA]] * web ** [[phab:project/view/5833/|web-team-revisit-later]] * [[phab:project/view/6024/|Wikidata data quality and trust]] * Wikimedia ** [[phab:project/view/4182/|Wikimedia-database-issue]] ** [[phab:project/view/2953/|Wikimedia-extension-review-queue]] ** [[phab:project/view/2143/|Wikimedia-Incident]] ** [[phab:project/view/2670/|Wikimedia-maintenance-script-run]] ** [[phab:project/view/1055/|Wikimedia-production-error]] * WMDE ** [[phab:project/view/4433/|WMDE-Fundraising-CFR]] ** [[phab:project/view/1943/|WMDE-Fundraising-CN]] * WorkType ** [[phab:project/view/1454/|WorkType-Maintenance]] ** [[phab:project/view/1453/|WorkType-NewFunctionality]] * [[phab:project/view/836/|Zuul]] === User groups === * [[phab:project/view/4876/|Abstract Wikipedia team]] * Africa ** [[phab:project/view/2858/|Africa-Wikimedia-Developers]] * All ** [[phab:project/view/1117/|All-and-every-Wikisource]] ** [[phab:project/view/1115/|All-and-every-Wiktionary]] * Anti ** [[phab:project/view/2660/|Anti-Harassment]] * [[phab:project/view/5960/|AvoinGLAM]] * [[phab:project/view/1942/|Brickimedia]] * Campaign ** [[phab:project/view/5430/|Campaign-Tools]] * cloud ** [[phab:project/view/2773/|cloud-services-team]] * Code ** [[phab:project/view/4165/|Code-Health-Group]] ** [[phab:project/view/3621/|Code-Health-Metrics]] ** [[phab:project/view/3766/|Code-Review-Workgroup]] * [[phab:project/view/1118/|Commons]] * Community ** [[phab:project/view/3448/|Community-Relations]] ** [[phab:project/view/945/|Community-Resources]] ** [[phab:project/view/1274/|Community-Tech]] * Content ** [[phab:project/view/5846/|Content-Transform-Team]] * Data ** [[phab:project/view/5462/|Data-Engineering]] ** [[phab:project/view/5980/|Data-Engineering-Icebox]] ** [[phab:project/view/5463/|Data-Engineering-Kanban]] ** [[phab:project/view/5682/|Data-Engineering-Radar]] ** [[phab:project/view/4996/|Data-Persistence]] ** [[phab:project/view/5050/|Data-Persistence (Consultation)]] * [[phab:project/view/1060/|DBA]] * DC ** [[phab:project/view/1784/|DC-Ops]] * Design ** [[phab:project/view/4650/|Design-Innovation-Team]] ** [[phab:project/view/839/|Design-Research]] ** [[phab:project/view/5858/|Design-Systems-Team]] * Developer ** [[phab:project/view/33/|Developer-Advocacy]] * Diffusion ** [[phab:project/view/85/|Diffusion-Repository-Administrators]] * [[phab:project/view/1174/|Discovery]] ** [[phab:project/view/1850/|Discovery-Analysis]] ** [[phab:project/view/1899/|Discovery-Portal-Backlog]] ** [[phab:project/view/1849/|Discovery-Search]] * [[phab:project/view/3728/|Editing QA]] * Editing ** [[phab:project/view/2823/|Editing-team]] * [[phab:project/view/1588/|ELiSo]] * English ** [[phab:project/view/5856/|English-Arbitration-Committee]] ** [[phab:project/view/2604/|English-Wikipedia-New-Pages-Patrol]] * Front ** [[phab:project/view/1616/|Front-end-Standards-Group]] * Fundraising ** [[phab:project/view/1390/|Fundraising-Analysis]] ** [[phab:project/view/41/|Fundraising-Backlog]] * [[phab:project/view/5517/|Generated Data Platform]] * Gerrit ** [[phab:project/view/3957/|Gerrit-Privilege-Requests]] * [[phab:project/view/2086/|GLAM]] * Growth ** [[phab:project/view/1114/|Growth-Team]] * Igbo ** [[phab:project/view/5069/|Igbo-Wikimedians-User-Group]] * [[phab:project/view/31/|importbots]] * Indiana ** [[phab:project/view/5949/|Indiana-Wikimedians]] * Indic ** [[phab:project/view/5147/|Indic-MediaWiki-Developers]] ** [[phab:project/view/3748/|Indic-TechCom]] * Infrastructure ** [[phab:project/view/5387/|Infrastructure-Foundations]] * Inuka ** [[phab:project/view/4300/|Inuka-Team]] * Koninklijke ** [[phab:project/view/5086/|Koninklijke-Bibliotheek-Team-Wiki]] * Language ** [[phab:project/view/18/|Language-Team]] * Machine ** [[phab:project/view/1901/|Machine-Learning-Team]] * MediaWiki ** [[phab:project/view/1005/|MediaWiki-Farmers]] ** [[phab:project/view/3956/|MediaWiki-Gerrit-Group-Requests]] ** [[phab:project/view/1071/|MediaWiki-Stakeholders-Group]] * Moderator ** [[phab:project/view/5869/|Moderator-Tools-Team]] * [[phab:project/view/3901/|Moegirlpedia]] * [[phab:project/view/5664/|NFDI]] * Offline ** [[phab:project/view/2387/|Offline-Working-Group]] * Performance ** [[phab:project/view/1212/|Performance-Team]] * [[phab:project/view/3654/|Platform Engineering]] * [[phab:project/view/4971/|Platform Engineering Roadmap Decision Making]] * [[phab:project/view/3696/|Platform Team Workboards]] * Policy ** [[phab:project/view/1869/|Policy-Admins]] * [[phab:project/view/4425/|Privacy Engineering]] * Product ** [[phab:project/view/3313/|Product-Analytics]] ** [[phab:project/view/2726/|Product-Infrastructure-Team-Backlog]] ** [[phab:project/view/3468/|Product-QA]] * Project ** [[phab:project/view/835/|Project-Admins]] * QTE ** [[phab:project/view/5189/|QTE-TestingOverview]] ** [[phab:project/view/4403/|Quality-and-Test-Engineering-Team (QTE)]] * Readers ** [[phab:project/view/67/|Readers-Web-Backlog]] * Reading ** [[phab:project/view/1199/|Reading-Admin]] ** [[phab:project/view/2785/|Reading-Web-Third-Party-Support]] * Release ** [[phab:project/view/20/|Release-Engineering-Team]] * [[phab:project/view/45/|Research]] ** [[phab:project/view/1864/|Research-Backlog]] * [[phab:project/view/4630/|secscrum]] * Security ** [[phab:project/view/1179/|Security-Team]] * [[phab:project/view/3775/|serviceops]] ** [[phab:project/view/6002/|serviceops-collab]] ** [[phab:project/view/4114/|serviceops-radar]] * [[phab:project/view/988/|ShoutWiki]] * [[phab:project/view/5008/|Smithsonian]] * [[phab:project/view/1025/|SRE]] * [[phab:project/view/5391/|SRE Observability]] * SRE ** [[phab:project/view/4626/|SRE-OnFire]] * Stewards ** [[phab:project/view/1596/|Stewards-and-global-tools]] * Structured ** [[phab:project/view/4223/|Structured-Data-Backlog]] * tech ** [[phab:project/view/5179/|tech-decision-forum]] * The ** [[phab:project/view/1270/|The-Wikipedia-Library]] * Toolforge ** [[phab:project/view/2457/|Toolforge-standards-committee]] * [[phab:project/view/1201/|Traffic]] ** [[phab:project/view/5516/|Traffic-Icebox]] * [[phab:project/view/991/|translatewiki.net]] * [[phab:project/view/13/|Triagers]] * [[phab:project/view/5374/|Trust and Safety Tools Team Backlog]] * Trust ** [[phab:project/view/1058/|Trust-and-Safety]] ** [[phab:project/view/3104/|Trusted-Contributors]] * [[phab:project/view/3998/|Uncyclomedia]] * Wiki ** [[phab:project/view/3359/|Wiki-Loves-Love]] ** [[phab:project/view/2588/|Wiki-Project-Med]] * [[phab:project/view/4286/|WikiClubWest]] * [[phab:project/view/6016/|Wikidata Dev Team]] * Wikidata ** [[phab:project/view/3402/|Wikidata-Campsite]] ** [[phab:project/view/5417/|Wikidata-WikiProject-Music]] * [[phab:project/view/1920/|Wikifab]] * [[phab:project/view/4317/|WikiJournals]] * [[phab:project/view/4929/|Wikimedia Enterprise]] * [[phab:project/view/2836/|Wikimedia Taiwan]] * Wikimedia ** [[phab:project/view/4329/|Wikimedia-and-Libraries-User-Group]] ** [[phab:project/view/3171/|Wikimedia-Cameroon-User-Group]] ** [[phab:project/view/1043/|Wikimedia-DC]] ** [[phab:project/view/363/|Wikimedia-Fundraising]] ** [[phab:project/view/2367/|Wikimedia-Israel-Hackers]] * wikimedia ** [[phab:project/view/2744/|wikimedia-page-library-tshirt]] * Wikimedia ** [[phab:project/view/5197/|Wikimedia-Small-Projects-User-Group]] ** [[phab:project/view/2865/|Wikimedia-Small-Projects-User-Group-TechCom]] ** [[phab:project/view/2990/|Wikimedia-User-Group-Basque]] ** [[phab:project/view/2677/|Wikimedia-Venezuela]] * Wikipedia ** [[phab:project/view/489/|Wikipedia-Android-App-Backlog]] ** [[phab:project/view/782/|Wikipedia-iOS-App-Backlog]] * Wikisource ** [[phab:project/view/1334/|Wikisource-Community-User-Group]] * Wikispeech ** [[phab:project/view/1979/|Wikispeech-KTH]] ** [[phab:project/view/1980/|Wikispeech-STTS]] ** [[phab:project/view/1978/|Wikispeech-WMSE]] * Wiktionary ** [[phab:project/view/4363/|Wiktionary-fr]] * WMDE ** [[phab:project/view/1585/|WMDE-Analytics-Engineering]] ** [[phab:project/view/1944/|WMDE-Design]] ** [[phab:project/view/2276/|WMDE-FUN-Team]] ** [[phab:project/view/2323/|WMDE-TechWish]] * WMF ** [[phab:project/view/4805/|WMF-Architecture-Team]] ** [[phab:project/view/1520/|WMF-Communications]] ** [[phab:project/view/57/|WMF-Design]] ** [[phab:project/view/28/|WMF-Legal]] ** [[phab:project/view/974/|WMF-NDA-Requests]] * WMSE ** [[phab:project/view/2521/|WMSE-Communication]] * WMUA ** [[phab:project/view/1686/|WMUA-Tech]] === ACLs === * acl*access ** [[phab:project/view/1515/|acl*access-policy-approvers]] * acl*AHT ** [[phab:project/view/4323/|acl*AHT-Private_policy_admins]] * [[phab:project/view/2217/|acl*analytics]] * acl*Analytics ** [[phab:project/view/3154/|acl*Analytics-Legal_policy_admins]] * [[phab:project/view/2025/|acl*annual_report_policy_admins]] * acl*blog ** [[phab:project/view/3774/|acl*blog-admins]] * [[phab:project/view/1418/|acl*communityrelations_policy_admins]] * acl*discovery ** [[phab:project/view/2625/|acl*discovery-repository-admins]] * acl*English ** [[phab:project/view/5855/|acl*English-Arbitration-Committee_policy_admins]] * [[phab:project/view/1142/|acl*fr_policy_admins]] * [[phab:project/view/1644/|acl*fundraising_research_policy_admins]] * acl*otrs ** [[phab:project/view/2406/|acl*otrs-admins]] * [[phab:project/view/5603/|acl*performance_team]] * [[phab:project/view/1081/|acl*phabricator]] * acl*procurement ** [[phab:project/view/1586/|acl*procurement-review]] * acl*Project ** [[phab:project/view/1776/|acl*Project-Admins]] * [[phab:project/view/3764/|acl*release_security_pre_announce]] * [[phab:project/view/1615/|acl*releng]] * acl*repository ** [[phab:project/view/2624/|acl*repository-admins]] * [[phab:project/view/2112/|acl*research_collaborations_policy_admins]] * [[phab:project/view/30/|acl*security]] * [[phab:project/view/4569/|acl*security_bugwrangler]] * [[phab:project/view/4564/|acl*security_developer]] * [[phab:project/view/4568/|acl*security_documentation]] * [[phab:project/view/4571/|acl*security_legal]] * [[phab:project/view/4565/|acl*security_management]] * [[phab:project/view/4567/|acl*security_product_manager]] * [[phab:project/view/4566/|acl*security_program_manager]] * [[phab:project/view/4563/|acl*security_releng]] * [[phab:project/view/4560/|acl*security_secteam]] * [[phab:project/view/4562/|acl*security_sre]] * [[phab:project/view/4570/|acl*security_steward]] * [[phab:project/view/2356/|acl*security_team]] * [[phab:project/view/4561/|acl*security_trusa]] * [[phab:project/view/4559/|acl*security_volunteer]] * [[phab:project/view/4572/|acl*security_wmde]] * acl*sre ** [[phab:project/view/29/|acl*sre-team]] * [[phab:project/view/2849/|acl*stewards]] * [[phab:project/view/2135/|acl*support_and_safety_policy_admins]] * [[phab:project/view/3442/|acl*userdisable]] * acl*Wikimedia ** [[phab:project/view/2991/|acl*Wikimedia-User-Group-Basque_policy_admins]] * [[phab:project/view/2808/|acl*wikisp_policy_admins]] * acl*wmcs ** [[phab:project/view/4858/|acl*wmcs-team]] * acl*WMDE ** [[phab:project/view/4753/|acl*WMDE-Technical-Wishes-Private_policy_admins]] * acl*WMF ** [[phab:project/view/4457/|acl*WMF-Communications_policy_admins]] ** [[phab:project/view/1070/|acl*WMF-FR]] ** [[phab:project/view/5264/|acl*WMF-Technical-Program-Management_policy_admins]] * [[phab:project/view/2904/|acl*wmf_blog_social_team_policy_admins]] * acl*WMIT ** [[phab:project/view/5818/|acl*WMIT-Private_policy_admins]] * [[phab:project/view/2052/|acl*WMUA_policy_admins]] * [[phab:project/view/4299/|Outreachy Mentors]] * WMF ** [[phab:project/view/61/|WMF-NDA]] === Goals === * Campaign ** [[phab:project/view/5515/|Campaign-Registration]] * CAS ** [[phab:project/view/4766/|CAS-SSO]] * Community ** [[phab:project/view/5581/|Community-Wishlist-Survey-2022]] * Data ** [[phab:project/view/3730/|Data-Portability]] * Disambiguation ** [[phab:project/view/5451/|Disambiguation-Wish-2021]] * Doc collections 2022 ** [[phab:project/view/6033/|Doc collections 2022-23]] * Doc contributions 2022 ** [[phab:project/view/6034/|Doc contributions 2022-23]] * Docs Assessment and Contributing 2022 ** [[phab:project/view/6032/|Docs Assessment and Contributing 2022-23]] * git ** [[phab:project/view/4856/|git-protocol-v2]] * [[phab:project/view/2169/|Goal]] * Growth ** [[phab:project/view/5246/|Growth-Deployments]] * Key docs update 2021 ** [[phab:project/view/5409/|Key docs update 2021-22]] * [[phab:project/view/4193/|Platform Team Initiatives]] * Pywikibot ** [[phab:project/view/904/|Pywikibot-compat-to-core]] * Realtime ** [[phab:project/view/5506/|Realtime-Preview-Wish-2021]] * [[phab:project/view/3611/|security_assessment_analytics_2018]] * [[phab:project/view/4412/|security_assessment_devtools_2019]] * services ** [[phab:project/view/1233/|services-tooling]] * [[phab:project/view/2770/|Train Deployments]] * Undelete ** [[phab:project/view/5480/|Undelete-Associated-Talk-Page (2021)]] * Wiki ** [[phab:project/view/5240/|Wiki-Techstorm-2022]] ** [[phab:project/view/5657/|Wikimedia-Hackathon-2022-Organization]] * [[phab:project/view/3605/|WMEE Eesti 1000]] * [[phab:project/view/3580/|WMEE Miljon+]] === Milestones === * 1.38.0 ** [[phab:project/view/5794/|1.38.0-wmf.25; 2022-03-07]] (MW-1.38-notes) ** [[phab:project/view/5795/|1.38.0-wmf.26; 2022-03-14]] (MW-1.38-notes) * 1.39.0 ** [[phab:project/view/6028/|1.39.0-wmf.22; 2022-07-25]] (MW-1.39-notes) ** [[phab:project/view/6029/|1.39.0-wmf.23; 2022-08-01]] (MW-1.39-notes) ** [[phab:project/view/6046/|1.39.0-wmf.25; 2022-08-15]] (MW-1.39-notes) ** [[phab:project/view/6062/|1.39.0-wmf.26; 2022-08-22]] (MW-1.39-notes) ** [[phab:project/view/6063/|1.39.0-wmf.27; 2022-08-29]] (MW-1.39-notes) ** [[phab:project/view/6064/|1.39.0-wmf.28; 2022-09-05]] (MW-1.39-notes) * 1.40.0 ** [[phab:project/view/6048/|1.40.0-wmf.1; 2022-09-12]] (MW-1.40-notes) ** [[phab:project/view/6049/|1.40.0-wmf.2; 2022-09-19]] (MW-1.40-notes) ** [[phab:project/view/6050/|1.40.0-wmf.3; 2022-09-26]] (MW-1.40-notes) ** [[phab:project/view/6051/|1.40.0-wmf.4; 2022-10-03]] (MW-1.40-notes) * [[phab:project/view/5716/|2022]] (Google-Summer-of-Code) * [[phab:project/view/2860/|3rd party support]] (MinervaNeue) * [[phab:project/view/4244/|Abstract Schema]] (Platform Team Initiatives) * [[phab:project/view/5151/|actions]] (MediaWiki-Interface) * [[phab:project/view/5152/|active libraries]] (MediaWiki-Interface) * [[phab:project/view/1306/|Active Tasks]] (Machine-Learning-Team) * [[phab:project/view/5557/|Administration, Settings & Policy]] (GitLab) * [[phab:project/view/6006/|AHaT Sprint 11: The Fascinator]] (Anti-Harassment) * [[phab:project/view/6038/|AHaT Sprint 12: The Dutch Cap]] (Anti-Harassment) * [[phab:project/view/5968/|AHaT Sprint 9: The Beret]] (Anti-Harassment) * [[phab:project/view/5195/|Ambassador]] (User-Urbanecm_WMF) * [[phab:project/view/2758/|Analytics]] (Reading Epics) * Android Release FY2021 ** [[phab:project/view/5420/|Android Release FY2021-22]] (Wikipedia-Android-App-Backlog) * [[phab:project/view/4321/|API Gateway]] (Platform Team Initiatives) * [[phab:project/view/4210/|API Integration Tests]] (Platform Team Initiatives) * [[phab:project/view/5554/|Auth & Access]] (GitLab) * [[phab:project/view/2613/|Authentication]] (Reading Epics) * [[phab:project/view/5059/|autocomplete search]] (MediaWiki-Interface) * [[phab:project/view/5786/|Automatic article quality assessment]] (WMSE-Development-Support-2022) * [[phab:project/view/4526/|Automatic article quality assessment]] (WMSE-Development-Support-2020) * [[phab:project/view/5315/|Automatic article quality assessment]] (WMSE-Development-Support-2021) * [[phab:project/view/5019/|Backlog]] (Product-Data-Infrastructure) * [[phab:project/view/5867/|Bad data]] (Wikimedia-database-issue) * [[phab:project/view/5543/|Banner campaign occasional editors 2021]] (WMDE-New-Editors-Banner-Campaigns) * [[phab:project/view/2121/|Beta Cluster Release]] (FileAnnotations) * [[phab:project/view/2812/|Blubber]] (Release Pipeline) * Campaign ** [[phab:project/view/5767/|Campaign-Design]] (Campaign-Tools) ** [[phab:project/view/6040/|Campaign-Tools-Sprint-17]] (Campaign-Tools) ** [[phab:project/view/4030/|Campaigns-jogging]] (SDC-Statements) * [[phab:project/view/2465/|Central Notice for Apps]] (Reading Epics) * [[phab:project/view/5555/|CI & Job Runners]] (GitLab) * [[phab:project/view/5787/|Citoid library for SVWP]] (WMSE-Development-Support-2022) * [[phab:project/view/4523/|Citoid library for SVWP]] (WMSE-Development-Support-2020) * [[phab:project/view/5316/|Citoid library for SVWP]] (WMSE-Development-Support-2021) * [[phab:project/view/4149/|Clinic Duty Team]] (Platform Team Workboards) * [[phab:project/view/2944/|Close]] (Wiki-Setup) * [[phab:project/view/5153/|collapsible elements]] (MediaWiki-Interface) * [[phab:project/view/6058/|Commons]] (Wikistories) * CommTech ** [[phab:project/view/5991/|CommTech-Sprint-29]] (Community-Tech) ** [[phab:project/view/5992/|CommTech-Sprint-30]] (Community-Tech) ** [[phab:project/view/5993/|CommTech-Sprint-31]] (Community-Tech) ** [[phab:project/view/6044/|CommTech-Sprint-32]] (Community-Tech) ** [[phab:project/view/6045/|CommTech-Sprint-33]] (Community-Tech) * [[phab:project/view/4364/|Containerise Services]] (Platform Team Initiatives) * [[phab:project/view/2942/|Create]] (Wiki-Setup) * [[phab:project/view/3450/|Current Sprint]] (Growth-Team) * [[phab:project/view/4232/|Current Work]] (Structured-Data-Backlog) * [[phab:project/view/1227/|Current work]] (Discovery-Search) * [[phab:project/view/1241/|Current work]] (Discovery-Analysis) * [[phab:project/view/5649/|Debian Stretch Deprecation]] (Cloud-VPS) * [[phab:project/view/4204/|Decoupling (CDP2)]] (Platform Team Initiatives) * [[phab:project/view/3590/|Delete / Redirect]] (Wiki-Setup) * Depicts ** [[phab:project/view/3938/|Depicts-Walking]] (SDC-Statements) * [[phab:project/view/3443/|Deployment]] (Multi-Content-Revisions) * [[phab:project/view/5981/|Deployment Autopilot 🛩️]] (Release-Engineering-Team) * [[phab:project/view/5265/|Deployment Training Requests]] (Release-Engineering-Team) * [[phab:project/view/5155/|deprecated JS libraries]] (MediaWiki-Interface) * [[phab:project/view/3473/|Deprecation process]] (Technical-Debt) * [[phab:project/view/2569/|Design]] (Wikipedia-iOS-App-Backlog) * [[phab:project/view/5199/|Design Backlog]] (Editing-team) * Design ** [[phab:project/view/5859/|Design-Systems-Sprint]] (Design-Systems-Team) * [[phab:project/view/2859/|Desktop]] (MinervaNeue) * [[phab:project/view/4814/|Discovery]] (KaiOS-Wikipedia-app) * [[phab:project/view/5160/|Dodo]] (Parsoid) * [[phab:project/view/5321/|Doing]] (Release-Engineering-Team) * [[phab:project/view/3845/|Economy]] (WMSE) * [[phab:project/view/3598/|EKM]] (WMEE Sum of all paintings) * Engagement ** [[phab:project/view/5158/|Engagement-1]] (KaiOS-Wikipedia-app) * [[phab:project/view/5053/|Engineering]] (User-Urbanecm_WMF) * [[phab:project/view/4614/|External Code Reviews]] (Platform Team Workboards) * [[phab:project/view/4681/|Failed QA]] (RW-Feature-DI-Opt-out-Toggle) * [[phab:project/view/4684/|Failed QA]] (RW-Feature-DI-Sticky-Site-Header) * [[phab:project/view/4687/|Failed QA]] (RW-Feature-DI-Collapsible-Sidebar) * [[phab:project/view/4690/|Failed QA]] (RW-Feature-DI-Language-Links) * [[phab:project/view/4693/|Failed QA]] (RW-Feature-DI-Header-and-Logo) * [[phab:project/view/4696/|Failed QA]] (RW-Feature-DI-User-Menu) * [[phab:project/view/4699/|Failed QA]] (RW-Feature-DI-Language-Switcher) * [[phab:project/view/4702/|Failed QA]] (RW-Feature-DI-TOC) * [[phab:project/view/4705/|Failed QA]] (RW-Feature-DI-Article-Tools) * [[phab:project/view/4710/|Failed QA]] (RW-Feature-DI-Sticky-Article-Header) * [[phab:project/view/4713/|Failed QA]] (RW-Feature-DI-Search-Improvements) * Feature ** [[phab:project/view/1839/|Feature-Parity]] (WMDE-Fundraising-Frontend-Release) * [[phab:project/view/4319/|Featured Feeds]] (Platform Team Initiatives) * Federation v2 ** [[phab:project/view/5512/|Federation v2 - Sprint 6]] (Wikibase - Federated Properties) * [[phab:project/view/2463/|Feed Content Language Expansion]] (Reading Epics) * [[phab:project/view/5435/|Freezer 🥶]] (wdwb-tech) * FY 2021 ** [[phab:project/view/5300/|FY 2021-2022]] (Wiki-Loves-Monuments) * FY2021 ** [[phab:project/view/4864/|FY2021-22 Kanban Board]] (Editing-team) ** [[phab:project/view/5457/|FY2021-22-Research-April-June]] (Research) ** [[phab:project/view/5650/|FY2021/2022-Q2]] (SRE-OnFire) ** [[phab:project/view/5651/|FY2021/2022-Q3]] (SRE-OnFire) ** [[phab:project/view/5652/|FY2021/2022-Q4]] (SRE-OnFire) ** [[phab:project/view/5808/|FY2021/2022-Q4]] (Infrastructure-Foundations) * FY2022/2023 ** [[phab:project/view/5945/|FY2022/2023-Q1]] (SRE Observability) ** [[phab:project/view/5946/|FY2022/2023-Q2]] (SRE Observability) ** [[phab:project/view/5947/|FY2022/2023-Q3]] (SRE Observability) * [[phab:project/view/6059/|Generator]] (Wikistories) * [[phab:project/view/5293/|Geoshapes]] (Maps) * [[phab:project/view/5347/|Gerrit 3.4]] (Gerrit) * [[phab:project/view/5896/|Gerrit 3.5]] (Gerrit) * [[phab:project/view/5897/|Gerrit 3.6]] (Gerrit) * GitLab ** [[phab:project/view/5873/|GitLab-a-thon 🦊]] (Release-Engineering-Team) * [[phab:project/view/5025/|Goals]] (Product-Data-Infrastructure) * [[phab:project/view/5789/|Google Workspace integration]] (WMSE-Organisational-Development-2022) * [[phab:project/view/3846/|Grants]] (WMSE) * [[phab:project/view/6052/|Hackathon 2022]] (Lingua Libre) * [[phab:project/view/4482/|Hardware]] (cloud-services-team) * [[phab:project/view/4655/|Hash Checking]] (Platform Team Initiatives) * [[phab:project/view/3844/|HR]] (WMSE) * [[phab:project/view/4632/|Icebox]] (Platform Engineering) * [[phab:project/view/5171/|Image Suggestion API]] (Platform Team Workboards) * [[phab:project/view/4758/|Incident Followup]] (Sustainability) * [[phab:project/view/5553/|Infrastructure]] (GitLab) * [[phab:project/view/5556/|Integrations]] (GitLab) * [[phab:project/view/3842/|IT]] (WMSE) * [[phab:project/view/4659/|Jio2]] (KaiOS-Wikipedia-app) * Jul ** [[phab:project/view/5857/|Jul-Sep 2022]] (Developer-Advocacy) ** [[phab:project/view/5898/|Jul-Sep-2022]] (CommRel-Specialists-Support) * [[phab:project/view/2727/|Kanban]] (Product-Infrastructure-Team-Backlog) * [[phab:project/view/4301/|Kanban]] (Inuka-Team) * [[phab:project/view/2774/|Kanban]] (cloud-services-team) * [[phab:project/view/4320/|Kanban]] (Product-Analytics) * [[phab:project/view/5880/|Kanban]] (Moderator-Tools-Team) * [[phab:project/view/5375/|Kanban]] (Trust and Safety Tools Team Backlog) * [[phab:project/view/4651/|Kanban Board]] (Design-Innovation-Team) * Kanbanana ** [[phab:project/view/6008/|Kanbanana-2022-23-Q1]] (Readers-Web-Backlog) * [[phab:project/view/1692/|Kartographer]] (Maps) * [[phab:project/view/1829/|Kartotherian]] (Maps) * [[phab:project/view/4810/|Language]] (KaiOS-Wikipedia-app) ** [[phab:project/view/4647/|Language-2020-Focus-Sprint]] (Language-Team) ** [[phab:project/view/5835/|Language-2022-April-June]] (Language-Team) ** [[phab:project/view/6009/|Language-2022-July-September]] (Language-Team) * [[phab:project/view/5566/|Lead Nurturing 2021 pilot 2]] (WMDE-New-Editors-Banner-Campaigns) * [[phab:project/view/2484/|Location Search]] (Reading Epics) * Machine ** [[phab:project/view/4109/|Machine-vision-depicts]] (SDC-Statements) * [[phab:project/view/2952/|Maintainer needed]] (Toolforge-standards-committee) * Map ** [[phab:project/view/1633/|Map-Styles]] (Maps) * [[phab:project/view/4527/|Maps in infoboxes]] (WMSE-Development-Support-2020) * Maps ** [[phab:project/view/2054/|Maps-data]] (Maps) * [[phab:project/view/4200/|MCR]] (Platform Team Initiatives) * [[phab:project/view/4217/|MCR Schema Migration]] (Platform Team Initiatives) * MediaSearch ** [[phab:project/view/4900/|MediaSearch-Alpha]] (SDAW-MediaSearch) ** [[phab:project/view/4901/|MediaSearch-Beta]] (SDAW-MediaSearch) ** [[phab:project/view/5187/|MediaSearch-ConceptChips]] (SDAW-MediaSearch) ** [[phab:project/view/5186/|MediaSearch-ImageRecs]] (SDAW-MediaSearch) ** [[phab:project/view/4902/|MediaSearch-ReleaseCandidate]] (SDAW-MediaSearch) ** [[phab:project/view/5014/|MediaSearch-ReleaseCandidate2]] (SDAW-MediaSearch) * MediaWiki ** [[phab:project/view/2743/|MediaWiki-MultiDC]] (Sustainability) * [[phab:project/view/4947/|mediawiki.widgets]] (MediaWiki-Interface) * [[phab:project/view/5769/|Menus 2.0]] (MediaWiki-Core-Skin-Architecture) * Metrics ** [[phab:project/view/5335/|Metrics-Platform-Epic-Roadmap]] (Metrics-Platform) ** [[phab:project/view/5336/|Metrics-Platform-MVP-Release-1]] (Metrics-Platform) * [[phab:project/view/5558/|Misc]] (GitLab) * [[phab:project/view/2467/|Mobile Web SSR and Connection Management]] (Reading Epics) * Mobile ** [[phab:project/view/4737/|Mobile-Prototype]] (Wikipedia-Preview) * [[phab:project/view/5654/|MobileFrontend (Editor)]] (MobileFrontend) * [[phab:project/view/3707/|MobileFrontend Special Pages]] (MobileFrontend) * [[phab:project/view/4195/|Modern Event Platform (TEC2)]] (Platform Team Initiatives) * Multi ** [[phab:project/view/4202/|Multi-DC (TEC1)]] (Platform Team Initiatives) * [[phab:project/view/4658/|MVP]] (KaiOS-Wikipedia-app) * [[phab:project/view/5698/|MVP]] (Wikistories) * [[phab:project/view/5144/|MW Expedition]] (Platform Team Workboards) * [[phab:project/view/4219/|MW REST API in PHP]] (Platform Team Initiatives) * [[phab:project/view/5154/|mw.notifications]] (MediaWiki-Interface) * [[phab:project/view/3601/|Narva Muuseum]] (WMEE Sum of all paintings) * [[phab:project/view/5483/|Needs Prioritization (Tech)]] (Readers-Web-Backlog) * [[phab:project/view/4549/|New Discussion 1.0]] (OWC2020) * [[phab:project/view/3678/|New Features]] (Multi-Content-Revisions) * [[phab:project/view/2464/|New Feed Content]] (Reading Epics) * [[phab:project/view/4623/|New Hook System]] (Platform Team Initiatives) * [[phab:project/view/5322/|Next]] (Release-Engineering-Team) * [[phab:project/view/4786/|Next Release]] (KaiOS-Wikipedia-app) * Oct ** [[phab:project/view/5989/|Oct-Dec 2022]] (Developer-Advocacy) ** [[phab:project/view/6036/|Oct-Dec-2022]] (CommRel-Specialists-Support) * [[phab:project/view/5478/|Okapi Wikimedia Enterprise]] (Wikimedia Enterprise) * [[phab:project/view/5631/|Onboarding 🚀]] (Release-Engineering-Team) * OOUI ** [[phab:project/view/4667/|OOUI-0.38.0]] (OOUI) ** [[phab:project/view/5677/|OOUI-0.43.0]] (OOUI) ** [[phab:project/view/5956/|OOUI-0.44.1]] (OOUI) * [[phab:project/view/4811/|Optimize]] (KaiOS-Wikipedia-app) * other ** [[phab:project/view/4255/|other-input-types-on-a-dirigible]] (SDC-Statements) * Other ** [[phab:project/view/3940/|Other-statements-running]] (SDC-Statements) * [[phab:project/view/4402/|Outreachy Interns]] (Platform Team Workboards) * Overhaul ** [[phab:project/view/4939/|Overhaul-2020]] (AbuseFilter) * [[phab:project/view/4547/|OWC2020 Replying 1.0]] (OWC2020) * [[phab:project/view/4546/|OWC2020 Replying 2.0]] (OWC2020) * [[phab:project/view/2468/|Page Previews]] (Reading Epics) * [[phab:project/view/4207/|Parsoid REST API in PHP (CDP2)]] (Platform Team Initiatives) * [[phab:project/view/4808/|Partnerships]] (The-Wikipedia-Library) * [[phab:project/view/4682/|Passed QA]] (RW-Feature-DI-Opt-out-Toggle) * [[phab:project/view/4685/|Passed QA]] (RW-Feature-DI-Sticky-Site-Header) * [[phab:project/view/4688/|Passed QA]] (RW-Feature-DI-Collapsible-Sidebar) * [[phab:project/view/4691/|Passed QA]] (RW-Feature-DI-Language-Links) * [[phab:project/view/4694/|Passed QA]] (RW-Feature-DI-Header-and-Logo) * [[phab:project/view/4697/|Passed QA]] (RW-Feature-DI-User-Menu) * [[phab:project/view/4700/|Passed QA]] (RW-Feature-DI-Language-Switcher) * [[phab:project/view/4703/|Passed QA]] (RW-Feature-DI-TOC) * [[phab:project/view/4706/|Passed QA]] (RW-Feature-DI-Article-Tools) * [[phab:project/view/4711/|Passed QA]] (RW-Feature-DI-Sticky-Article-Header) * [[phab:project/view/4714/|Passed QA]] (RW-Feature-DI-Search-Improvements) * [[phab:project/view/5562/|Peter's world]] (Editing-team) * phabricator ** [[phab:project/view/5278/|phabricator-next]] (Phabricator) * Phase 0 ** [[phab:project/view/5533/|Phase 0 - Parsoid-Media-Structure]] (Parsoid-Read-Views) * Phase 1 ** [[phab:project/view/5534/|Phase 1 - DiscussionTools support]] (Parsoid-Read-Views) * Phase 2 ** [[phab:project/view/5535/|Phase 2 - testwiki Main namespace support]] (Parsoid-Read-Views) * Phase 3 ** [[phab:project/view/5536/|Phase 3 - Main namespace of officewiki / mediawiki.org renders with Parsoid]] (Parsoid-Read-Views) * Phase 4 ** [[phab:project/view/5537/|Phase 4 - Parsoid generates metadata needed by core]] (Parsoid-Read-Views) * [[phab:project/view/4961/|Phase θ – Throttling]] (Abstract Wikipedia team) * [[phab:project/view/4962/|Phase ι – Documentation]] (Abstract Wikipedia team) * Phase κ – Clean ** [[phab:project/view/4963/|Phase κ – Clean-up]] (Abstract Wikipedia team) * [[phab:project/view/4964/|Phase λ – Launch]] (Abstract Wikipedia team) * [[phab:project/view/5268/|Platform Engineering Reliability]] (Platform Team Workboards) * [[phab:project/view/2462/|Platform JS CSS and HTML consolidation]] (Reading Epics) * Platform ** [[phab:project/view/4913/|Platform-Product Roadmap]] (Platform Team Workboards) * [[phab:project/view/5585/|Priority Backlog 📥]] (Release-Engineering-Team) * [[phab:project/view/5377/|Product Roadmap]] (API Platform) * [[phab:project/view/5600/|Product Roadmap]] (Generated Data Platform) * [[phab:project/view/2248/|Production release]] (FileAnnotations) * [[phab:project/view/5552/|Project Migration]] (GitLab) * [[phab:project/view/2700/|Project Setup]] (Push-Notification-Service) * [[phab:project/view/5784/|Project start bot]] (WMSE-Organisational-Development-2022) * Project ** [[phab:project/view/2875/|Project-requests]] (Cloud-VPS) * [[phab:project/view/2475/|Push Notifications]] (Reading Epics) * [[phab:project/view/3599/|Pärnu Muuseum]] (WMEE Sum of all paintings) * Quota ** [[phab:project/view/2880/|Quota-requests]] (Cloud-VPS) ** [[phab:project/view/4481/|Quota-requests]] (Data-Services) ** [[phab:project/view/4834/|Quota-requests]] (Toolforge) * [[phab:project/view/5988/|R2]] (Wikistories) * [[phab:project/view/2923/|Radar]] (Performance-Team) * [[phab:project/view/5320/|Radar]] (Release-Engineering-Team) * [[phab:project/view/3679/|Reactive]] (Multi-Content-Revisions) * [[phab:project/view/2943/|Rename]] (Wiki-Setup) * [[phab:project/view/4907/|Reply Tool Opt Out]] (OWC2020) * [[phab:project/view/3417/|Reportings]] (WMDE-New-Editors-Banner-Campaigns) * [[phab:project/view/5173/|Responsive]] (MonoBook) * [[phab:project/view/4211/|Revision Storage Schema Improvements]] (Platform Team Initiatives) * [[phab:project/view/5507/|Round 23]] (Outreachy) * [[phab:project/view/5717/|Round 24]] (Outreachy) * RW ** [[phab:project/view/2297/|RW-Design-Debt]] (Design) ** [[phab:project/view/2296/|RW-Tech-Debt]] (Technical-Debt) ** [[phab:project/view/3912/|RW-Test-Cases]] (Product-QA) * [[phab:project/view/4157/|S&F Workboard]] (Platform Team Workboards) * S1 ** [[phab:project/view/5632/|S1-2022]] (Wikimedia-Small-Projects-User-Group-Milestone) * Scap3 ** [[phab:project/view/1823/|Scap3-MediaWiki-MVP]] (Scap) * [[phab:project/view/2523/|Search]] (Phabricator) * [[phab:project/view/5323/|Seen]] (Release-Engineering-Team) * [[phab:project/view/4194/|Session Management Service (CDP2)]] (Platform Team Initiatives) * [[phab:project/view/3978/|Software install/update]] (Toolforge) * [[phab:project/view/4380/|Sprint]] (Wikispeech-Jobrunner) * [[phab:project/view/4871/|Sprint 0]] (Platform Team Sprints Board) * [[phab:project/view/6061/|Sprint 00]] (Data Pipelines) * [[phab:project/view/6056/|Sprint 02]] (Data Engineering Planning) * [[phab:project/view/4903/|Sprint 1]] (Platform Team Sprints Board) * [[phab:project/view/6060/|Sprint 11]] (Wikibase Product Platform) * [[phab:project/view/4938/|Sprint 2]] (Platform Team Sprints Board) * [[phab:project/view/4966/|Sprint 3]] (Platform Team Sprints Board) * [[phab:project/view/4986/|Sprint 4]] (Platform Team Sprints Board) * [[phab:project/view/5015/|Sprint 5]] (Platform Team Sprints Board) * Sprint 7/28 ** [[phab:project/view/5438/|Sprint 7/28-8/10 2021]] (User-jeena) * Sprint 8/18 ** [[phab:project/view/5493/|Sprint 8/18-8/31 2021]] (User-jeena) * Sprint ** [[phab:project/view/6017/|Sprint-♾]] (Wikidata Dev Team) * Statement ** [[phab:project/view/3987/|Statement-and-keyword-search-power-walking]] (SDC-Statements) * [[phab:project/view/5551/|Support]] (GitLab) * [[phab:project/view/2483/|Synchronized Reading Lists]] (Reading Epics) * [[phab:project/view/4906/|Tables]] (MediaWiki-Interface) * [[phab:project/view/3597/|TARTMUS]] (WMEE Sum of all paintings) * [[phab:project/view/3600/|Tartu Linnamuuseum]] (WMEE Sum of all paintings) * [[phab:project/view/3604/|Tartu Ülikoli kunstimuuseum]] (WMEE Sum of all paintings) * [[phab:project/view/3603/|Tartu Ülikoli muuseum]] (WMEE Sum of all paintings) * [[phab:project/view/5612/|Team A Hearth 🏰🔥]] (Wikidata-Campsite) * [[phab:project/view/3677/|Tech Debt]] (Multi-Content-Revisions) * Temporary ** [[phab:project/view/2414/|Temporary-UserRights]] (Stewards-and-global-tools) * [[phab:project/view/6022/|The Decommission Mission 💀]] (Release-Engineering-Team) * Third ** [[phab:project/view/5206/|Third-party]] (Editing-team) ** [[phab:project/view/5100/|Third-party]] (Parsoid) * [[phab:project/view/2482/|Thumbnails]] (Reading Epics) * [[phab:project/view/1830/|Tilerator]] (Maps) * [[phab:project/view/3975/|Tools to be deleted]] (Toolforge) * [[phab:project/view/4905/|Tracking]] (MobileFrontend) * [[phab:project/view/5172/|Tracking]] (Modern) * [[phab:project/view/5174/|Tracking]] (MonoBook) * [[phab:project/view/5175/|Tracking]] (CologneBlue) * [[phab:project/view/3769/|Tracking]] (Page-Previews) * [[phab:project/view/4541/|Tracking]] (Editing-team) * [[phab:project/view/3297/|Tracking]] (MinervaNeue) * [[phab:project/view/5099/|Tracking]] (Parsoid) * [[phab:project/view/2476/|Trending Edits]] (Reading Epics) * UI ** [[phab:project/view/4192/|UI-consolidation-on-a-Ferris-wheel]] (SDC-Statements) * [[phab:project/view/6/|Upstream]] (Phabricator) * [[phab:project/view/5671/|v0.0.1]] (Web2Cit-Core) * [[phab:project/view/5667/|v3.0]] (InternetArchiveBot) * [[phab:project/view/4496/|Vector (Tracking)]] (Vector) * [[phab:project/view/3602/|Võrumaa Museum]] (WMEE Sum of all paintings) * [[phab:project/view/4506/|Wiki Loves Earth 2020]] (WMSE-Wiki-Loves-2020) * [[phab:project/view/4505/|Wiki Loves Monuments 2020]] (WMSE-Wiki-Loves-2020) * [[phab:project/view/5761/|Wikibase Suite Maintenance Releases Feb 2022]] (Wikibase Suite) * [[phab:project/view/6043/|Wikibase.cloud (WB Cloud Sprint 1)]] (Wikibase.cloud) * [[phab:project/view/2472/|Wikidata Description Editing]] (Reading Epics) * [[phab:project/view/2471/|Wikidata Description Editing ORES Abuse Filter]] (Reading Epics) * WMDE ** [[phab:project/view/3114/|WMDE-Design-Workboard Doing]] (WMDE-Design) * WMF ** [[phab:project/view/4742/|WMF-deployed Build Failure]] (ci-test-error) * WMSE ** [[phab:project/view/5990/|WMSE-Nordic-Museum-2022]] (WMSE-GLAM-2022) * [[phab:project/view/2759/|Workflow Improvements]] (MediaWiki-Releasing) * [[phab:project/view/5319/|Yak Shaving 🐃🪒]] (Release-Engineering-Team) * [[phab:project/view/5819/|Zynatic]] (WMSE-Association-Involvement-2022) * [[phab:project/view/5861/|🌱 Spring Cleaning — April 2022]] (Release-Engineering-Team) === Releases === * Gadgets ** [[phab:project/view/1634/|Gadgets-2.0]] * iOS ** [[phab:project/view/5997/|iOS-app-v6.9.3]] * ios ** [[phab:project/view/5380/|ios-app-v7.0]] * MediaWiki ** [[phab:project/view/2239/|MediaWiki-backport-deployments]] * MW ** [[phab:project/view/4306/|MW-1.35-notes]] ** [[phab:project/view/4035/|MW-1.35-release]] ** [[phab:project/view/5296/|MW-1.37-notes]] ** [[phab:project/view/4928/|MW-1.37-release]] ** [[phab:project/view/5539/|MW-1.38-notes]] ** [[phab:project/view/5407/|MW-1.38-release]] ** [[phab:project/view/5796/|MW-1.39-notes]] ** [[phab:project/view/5694/|MW-1.39-release]] ** [[phab:project/view/6047/|MW-1.40-notes]] * [[phab:project/view/1333/|Release]] === Sprints === * Abstract Wikipedia Fix ** [[phab:project/view/5712/|Abstract Wikipedia Fix-It tasks]] * CommTech ** [[phab:project/view/5906/|CommTech-Hackathon-AKA-CodeJam-2022]] * Data ** [[phab:project/view/5504/|Data-Quality-Days-2021]] * Discovery ** [[phab:project/view/1235/|Discovery-Portal-Sprint]] * [[phab:project/view/1230/|Elections]] * [[phab:project/view/6019/|Fundraising Sprint Machine Unlearning]] * [[phab:project/view/4797/|itWikiCon]] ** [[phab:project/view/4798/|itWikiCon-2020]] ** [[phab:project/view/5790/|itWikiCon-2022]] * [[phab:project/view/4970/|Platform Engineering Roadmap]] * Programs ** [[phab:project/view/1786/|Programs-and-Events-Dashboard-Sprint 2]] * UI ** [[phab:project/view/1806/|UI-Standardization-Kanban]] * Wikimania ** [[phab:project/view/6030/|Wikimania-Hackathon-2022]] * Wikimedia ** [[phab:project/view/5802/|Wikimedia-Hackathon-2022]] ** [[phab:project/view/5626/|Wikimedia-Small-Projects-User-Group-Milestone]] * WMDE ** [[phab:project/view/6001/|WMDE-FUN-Sprint-2022-06-27]] ** [[phab:project/view/6025/|WMDE-FUN-Sprint-2022-07-11]] ** [[phab:project/view/6057/|WMDE-FUN-Sprint-2022-07-25]] ** [[phab:project/view/6039/|WMDE-TechWish-Sprint-2022-07-20]] ** [[phab:project/view/3106/|WMDE-UX-Workboard]] * WMF ** [[phab:project/view/6023/|WMF-Inspiration-Week-2022-ML-Collab]] === User projects === * User ** [[phab:project/view/2688/|User-Abbe98]] ** [[phab:project/view/3908/|User-abi_]] ** [[phab:project/view/5822/|User-AKlapper]] ** [[phab:project/view/2518/|User-Alicia_Fagerving_WMSE]] ** [[phab:project/view/3418/|User-Amire80]] ** [[phab:project/view/4580/|User-ANEUN]] ** [[phab:project/view/4396/|User-Apap04]] ** [[phab:project/view/2995/|User-ArielGlenn]] ** [[phab:project/view/2776/|User-aude]] ** [[phab:project/view/4464/|User-awight]] ** [[phab:project/view/2516/|User-AxelPettersson_WMSE]] ** [[phab:project/view/929/|User-bd808]] ** [[phab:project/view/5418/|User-Bongo-Cat]] ** [[phab:project/view/4463/|User-brennen]] ** [[phab:project/view/5317/|User-Carn]] ** [[phab:project/view/4196/|User-CCicaleseWMF]] ** [[phab:project/view/3734/|User-CDanis]] ** [[phab:project/view/4198/|User-Cicalese]] ** [[phab:project/view/3381/|User-Cirdan]] ** [[phab:project/view/3588/|User-Daimona]] ** [[phab:project/view/4859/|User-dancy]] ** [[phab:project/view/2384/|User-Daniel]] ** [[phab:project/view/3849/|User-DannyS712]] ** [[phab:project/view/5584/|User-dcaro]] ** [[phab:project/view/5779/|User-dduvall]] ** [[phab:project/view/2187/|User-Dereckson]] ** [[phab:project/view/4377/|User-Dyolf77]] ** [[phab:project/view/3865/|User-EBernhardson]] ** [[phab:project/view/3075/|User-Eevans]] ** [[phab:project/view/2398/|User-Elukey]] ** [[phab:project/view/5932/|User-EpicPupper]] ** [[phab:project/view/2517/|User-Eric_Luth_WMSE]] ** [[phab:project/view/4556/|User-Etonkovidova]] ** [[phab:project/view/5970/|User-EUdoh-WMF]] ** [[phab:project/view/2668/|User-fgiunchedi]] ** [[phab:project/view/3866/|User-fsero]] ** [[phab:project/view/4764/|User-gabrielchl]] ** [[phab:project/view/2895/|User-GoranSMilovanovic]] ** [[phab:project/view/1436/|User-greg]] ** [[phab:project/view/4345/|User-HannaLindgren]] ** [[phab:project/view/4003/|User-Harej]] ** [[phab:project/view/3429/|User-herron]] ** [[phab:project/view/2962/|User-Huji]] ** [[phab:project/view/2077/|User-Hydriz]] ** [[phab:project/view/5508/|User-IN]] ** [[phab:project/view/5221/|User-Inductiveload]] ** [[phab:project/view/5804/|User-ItamarWMDE]] ** [[phab:project/view/3076/|User-Jayprakash12345]] ** [[phab:project/view/4357/|User-jbond]] ** [[phab:project/view/2985/|User-Jdlrobson]] ** [[phab:project/view/2563/|User-JeanFred]] ** [[phab:project/view/5436/|User-jeena]] ** [[phab:project/view/4748/|User-Jenny_Brandt_WMSE]] ** [[phab:project/view/3091/|User-Jhernandez]] ** [[phab:project/view/3572/|User-jijiki]] ** [[phab:project/view/2271/|User-Joe]] ** [[phab:project/view/1763/|User-Johan]] ** [[phab:project/view/2542/|User-John_Cummings]] ** [[phab:project/view/2512/|User-Jopparn]] ** [[phab:project/view/4531/|User-JosefineHellrothLarssonWMSE]] ** [[phab:project/view/1724/|User-Josve05a]] ** [[phab:project/view/4925/|User-Jpita]] ** [[phab:project/view/2566/|User-JSeddon]] ** [[phab:project/view/5599/|User-Juan90264]] ** [[phab:project/view/4552/|User-kalle]] ** [[phab:project/view/2946/|User-KartikMistry]] ** [[phab:project/view/3077/|User-Kizule]] ** [[phab:project/view/4854/|User-Kormat]] ** [[phab:project/view/3735/|User-kostajh]] ** [[phab:project/view/3778/|User-kzimmerman]] ** [[phab:project/view/2451/|User-LokalProfil]] ** [[phab:project/view/5358/|User-LSobanski]] ** [[phab:project/view/1765/|User-Luke081515]] ** [[phab:project/view/3069/|User-MacFan4000]] ** [[phab:project/view/2877/|User-MarcoAurelio]] ** [[phab:project/view/4583/|User-Maria_Burehall_WMSE]] ** [[phab:project/view/3490/|User-Marostegui]] ** [[phab:project/view/2896/|User-Matthewrbowker]] ** [[phab:project/view/3378/|User-MatthiasGeisler]] ** [[phab:project/view/2079/|User-MBinder_WMF]] ** [[phab:project/view/3749/|User-Michael]] ** [[phab:project/view/3579/|User-MModell]] ** [[phab:project/view/4779/|User-MoritzMuehlenhoff]] ** [[phab:project/view/2223/|User-MuhammadShuaib]] ** [[phab:project/view/2222/|User-Nikerabbit]] ** [[phab:project/view/3861/|User-Noarave]] ** [[phab:project/view/3272/|User-Physikerwelt]] ** [[phab:project/view/4374/|User-PPham]] ** [[phab:project/view/4741/|User-QEDK]] ** [[phab:project/view/5676/|User-Raymond_Ndibe]] ** [[phab:project/view/1725/|User-Reedy]] ** [[phab:project/view/3138/|User-revi]] ** [[phab:project/view/4159/|User-RhinosF1]] ** [[phab:project/view/3508/|User-Rxy]] ** [[phab:project/view/2433/|User-Ryasmeen]] ** [[phab:project/view/5288/|User-Salgo60]] ** [[phab:project/view/5973/|User-Sandra_Fauconnier_WMSE]] ** [[phab:project/view/2515/|User-SaraMortsell]] * user ** [[phab:project/view/3979/|user-sbassett]] * User ** [[phab:project/view/2511/|User-Sebastian_Berlin-WMSE]] ** [[phab:project/view/5658/|User-Slst2020]] ** [[phab:project/view/2921/|User-Smalyshev]] ** [[phab:project/view/4833/|User-Soham]] ** [[phab:project/view/4392/|User-srishakatux]] ** [[phab:project/view/5601/|User-STei-WMF]] ** [[phab:project/view/4302/|User-SwedishMuseum]] ** [[phab:project/view/3341/|User-TArrow]] ** [[phab:project/view/2728/|User-Tgr]] ** [[phab:project/view/3770/|User-TheDJ]] ** [[phab:project/view/2539/|User-TheresNoTime]] ** [[phab:project/view/4289/|User-TheSandDoctor]] ** [[phab:project/view/3107/|User-thiemowmde]] ** [[phab:project/view/5720/|User-Tks4Fish]] ** [[phab:project/view/2196/|User-Tobi_WMDE_SW]] ** [[phab:project/view/4017/|User-Tore_Danielsson_WMSE]] ** [[phab:project/view/2098/|User-Urbanecm]] ** [[phab:project/view/4943/|User-Urbanecm_WMF]] ** [[phab:project/view/4832/|User-Vidhi-Mody]] ** [[phab:project/view/4183/|User-WDoran]] ** [[phab:project/view/2658/|User-WMDE-leszek]] ** [[phab:project/view/3525/|User-xSavitar]] ** [[phab:project/view/1938/|User-zeljkofilipin]] ** [[phab:project/view/2745/|User-Zppix]] === Miscellaneous === * Continuous ** [[phab:project/view/1208/|Continuous-Integration-Config]] * Patch ** [[phab:project/view/32/|Patch-For-Review]] * [[phab:project/view/89/|Trash]] {{/Footer}} g6xr9l2yms3qorf41nigwrsdywpqcur Manual:Installation guide/ar 100 346960 5386634 5381070 2022-07-28T17:14:21Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ar]] 6sw4wvx33swqgcs9huatpqpyaqpia20 5386693 5386634 2022-07-28T17:26:42Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/ar]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Extension talk:Cargo 103 356188 5386717 5357096 2022-07-28T18:17:52Z MusikAnimal 422134 /* Debugging why Cargo data is not storing */ Reply wikitext text/x-wiki {{Cargo navigation}} {{Archive box| * [[Extension talk:Cargo/Archive January to May 2015|January to May 2015]] * [[Extension talk:Cargo/Archive June to October 2015|June to October 2015]] * [[Extension talk:Cargo/Archive November to December 2015|November to December 2015]] * [[Extension talk:Cargo/Archive January to March 2016|January to March 2016]] * [[Extension talk:Cargo/Archive April to June 2016|April to June 2016]] * [[Extension talk:Cargo/Archive July to October 2016|July to October 2016]] * [[Extension talk:Cargo/Archive November to December 2016|November to December 2016]] * [[Extension talk:Cargo/Archive January to February 2017|January to February 2017]] * [[Extension talk:Cargo/Archive March to July 2017|March to July 2017]] * [[Extension talk:Cargo/Archive August to September 2017|August to September 2017]] * [[Extension talk:Cargo/Archive October to December 2017|October to December 2017]] * [[Extension talk:Cargo/Archive January to February 2018|January to February 2018]] * [[Extension talk:Cargo/Archive March to May 2018|March to May 2018]] * [[Extension talk:Cargo/Archive June to July 2018|June to July 2018]] * [[Extension talk:Cargo/Archive August to September 2018|August to September 2018]] * [[Extension talk:Cargo/Archive October to December 2018|October to December 2018]] * [[Extension talk:Cargo/Archive January 2019|January 2019]] * [[Extension talk:Cargo/Archive February to March 2019|February to March 2019]] * [[Extension talk:Cargo/Archive April to July 2019|April to July 2019]] * [[Extension talk:Cargo/Archive August to October 2019|August to October 2019]] * [[Extension talk:Cargo/Archive November to December 2019|November to December 2019]] * [[Extension talk:Cargo/Archive January to February 2020|January to February 2020]] * [[Extension talk:Cargo/Archive March to April 2020|March to April 2020]] * [[Extension talk:Cargo/Archive May to July 2020|May to July 2020]] * [[Extension talk:Cargo/Archive August to December 2020|August to December 2020]] * [[Extension talk:Cargo/Archive January to April 2021|January to April 2021]] * [[Extension talk:Cargo/Archive May to June 2021|May to June 2021]] * [[Extension talk:Cargo/Archive July to October 2021|July to October 2021]] * [[Extension talk:Cargo/Archive November to December 2021|November to December 2021]] * [[Extension talk:Cargo/Archive January to May 2022|January to May 2022]] }} == Display Format Table without Sortable == I would like to display the results of the query in a table, but not allow for that table to be sorted. Format=Table appears to force sorting on. How can I work around this? [[Special:Contributions/2601:C2:8201:6940:0:0:0:42E2|2601:C2:8201:6940:0:0:0:42E2]] 19:20, 16 June 2022 (UTC) :Well, the table will always be sorted on ''something''. If you want it to ''look'' unsorted, you could always add an "order by=" with some random field that's not in the table, like "order by=_pageID". (Though _pageID will reflect the order in which the pages were created, so maybe that's not ideal either - you could instead do something like "order by=_pageID % 100".) [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 20:04, 16 June 2022 (UTC) ::You could use format=template to create a table from scratch. ::Maybe you could use css to hide the arrow icons. ::Maybe you could use JavaScript to get rid of the class that makes the table sortable. [[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 20:11, 16 June 2022 (UTC) :::Oh... maybe I misunderstood the question. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 20:15, 16 June 2022 (UTC) ::::Thank you for the reply. Currently, I am using the workaround of hiding the sorting arrows via css changes. Jonathan3's suggestion to remove the headerSort class via javascript is viable, but I would like to avoid bloating my wiki's common.js with changes like this. [[Special:Contributions/2601:C2:8201:6940:0:0:0:42E2|2601:C2:8201:6940:0:0:0:42E2]] 01:28, 17 June 2022 (UTC) :::::Why do you want to disable sorting, if I may ask? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 02:04, 17 June 2022 (UTC) == table format in lua == Hello how to draw a conclusion in a table <code>local args = { where = 'categories HOLDS "..."', limit = '100', orderBy = '_pageName', format = table }</code> <code>format = table</code> doesn't work, bottom doesn't show (View (previous 50|next 50) (20|50|100|250|500)) Thanks! --Oleksii [[Special:Contributions/212.80.62.177|212.80.62.177]] 10:54, 20 June 2022 (UTC) :There is no way to add that specific footer to the end of query results - for the "table" format or otherwise - in Cargo, as far as I know; that interface is really meant for the bottom of special pages. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:07, 20 June 2022 (UTC) == Do not have permission to recreate Cargo data == Hello, I have installed Cargo extension in bluespice free. I have a sysops role. When I try to create a cargo table using ?action=recreatedata I get a permission error "You do not have permission to recreate Cargo data, for the following reason: You are not allowed to execute the action you have requested." What have I to do to get it working ? [[User:Vn596174|Vn596174]] ([[User talk:Vn596174|talk]]) 11:45, 22 June 2022 (UTC) :That's odd - are you sure you're part of the "sysop" group"? And what version of Cargo are you running? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:59, 23 June 2022 (UTC) :I have the same problem. To work around it il did the following: :- deactive all bluespice extensions in settings.d, keeping only mediawiki ones :<?php :return; // Disabled. :- create cargo tables :- active all bluespice extensions :<?php ://return; // Disabled. :Now you can add data to cargo tables but still not use recreate data :I think this is caused by the way BS uses permissions (see BlueSpicePermissionManager [[Extension:PermissionManager/en|Extension:PermissionManager - MediaWiki]]) [[Special:Contributions/2001:861:4745:7590:9D8B:EFCB:F425:7B79|2001:861:4745:7590:9D8B:EFCB:F425:7B79]] 13:39, 16 July 2022 (UTC) == cargoRecreateData throws error after upgrade to MW1.38.1 == Hello, after upgrading to MW 1.38.1, one of my tables is throwing this error for every page when doing cargoRecreateData: <code>PHP Notice:  Undefined index: Image in /var/www/mediawiki-1.38.1/extensions/Cargo/includes/parserfunctions/CargoStore.php on line 472</code> 'Image' is one of the fields and is set to NULL in every entry. There are other fields within the same table that are set to NULL but those are not giving any problem. Thank you very much for your support [[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 08:20, 1 July 2022 (UTC) :This may be a silly question, but does the Cargo table actually contain an "Image" field? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:59, 1 July 2022 (UTC) :: Hello Yaron, yes, it does contain an "Image" field--[[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 07:58, 4 July 2022 (UTC) :::Yes, indeed... what does the line for "Image" look like in the #cargo_declare call? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 01:16, 5 July 2022 (UTC) :::: Hello, the #cargo_declare looks like this:<code>{{#cargo_declare:_table=Documents|Requires_editing=Boolean (hidden)|Type=String|Project=Page|Activity=Page|Topic=List (,) of String|Scope=List (,) of String|Authors=List (,) of Page (hidden)|Tool=Page (hidden)|Contact=Page (hidden)|Attachments=List (,) of String (hidden)|Image=File|Meeting_time=Datetime (hidden)|Meeting_location=String (hidden)|Meeting_participants_CE=List (,) of Page (hidden)|Meeting_participants_CQ=List (,) of Page (hidden)|Meeting_participants_companies=List (,) of Page (hidden)|Meeting_document_date=Date (hidden)|Car_review=Page (hidden)}}</code> :::: Thanks!--[[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 07:49, 5 July 2022 (UTC)<br> [[File:Screenshot Documents table fields.png|thumb]] :::::Thanks for that listing. You discovered a bug in the handling of "File" fields - sorry about that. I and someone else just checked in [https://phabricator.wikimedia.org/rECRG2e8c4020ed4c1c695d9368ea4efcb3f81e8c704a a fix] for it, so if you get the latest Cargo code, those PHP notices should go away. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 03:07, 6 July 2022 (UTC) :::::: Great, thanks. --[[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 07:44, 6 July 2022 (UTC) :::::: Also, there was another error being thrown, which is still present:<br> <code>Recreating data for Cargo table Activities in 5 seconds... hit [Ctrl]-C to escape.</code><br> <code>Deleting and recreating table...</code><br> <code>Handling template that adds to this table: Activity</code><br> <code>PHP Deprecated: Use of Title::$mDbkeyform was deprecated in MediaWiki 1.37. [Called from CargoRecreateData::recreateAllDataForTable in /var/www/mediawiki-1.38.1/extensions/Cargo/maintenance/cargoRecreateData.php at line 153] in /var/www/mediawiki-1.38.1/includes/debug/MWDebug.php on line 377</code> :Thanks for letting me know about that - this, too, is fixed now, I believe. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 16:53, 6 July 2022 (UTC) :: I confirm it's fixed. Thanks Yaron. --[[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 09:06, 7 July 2022 (UTC) == Create Class error message "This appears to be a cross-site request forgery - Save cancelled" == What does this error message mean? I had completed defining all the fields for a table, went to save it and got that message. Before entering it all again and hoping for the best, I would prefer to know what I might have done wrong. I had previously deleted the table and was recreating it with less and altered fields, and was following the same process as for an earlier table that did save successfully. I love the Build Class feature, it is a pity there is no Modify Class as well as manually editing templates to add or edit fields is a painstaking task, hence I have found it easier to start again if there is not much in the table yet. I am using Mediawiki 1.36.2 and Cargo 3.1. Thanks, Robert :I'm guessing/hoping that it's a one-time thing, and if you try it again it'll work fine. That said, if you want to be able to modify the class with a form, check out the [[Extension:Page Schemas|Page Schemas]] extension. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:56, 8 July 2022 (UTC) == Cargo_query error == Hello, Running php update.php after installing the Cargo extension, I have created a cargo table using the following template Template:MSStandard <pre> <noinclude> {{#template_params:MSSReference|MSSTitle|MSSAbstract|MSSPublicationDate|MSSEdition|MSSStatus|MSSType|Language}} {{#cargo_declare:_table=MSStandard|MSSReference=String|MSSTitle=String|MSSAbstract=Text (size=3500)|MSSPublicationDate=String|MSSEdition=String|MSSStatus=String (allowed values=WD,CD,DIS,FDIS,IS)|MSSType=string (allowed values=MSS-A,MSS-B)|Language=String (allowed values=English,Français)}}</noinclude><includeonly>{{#cargo_store:_table=MSStandard}} {{#template_display:_format=standard}} [[Category:MSStandard]] </includeonly> </pre> When I add a page using the template everything is OK, the page is created and the cargo table is populated. Every time I add a cargo query to the page there is an error message <pre> A database query error has occurred. This may indicate a bug in the software. [efdb63d66f6075643dec9f82] /index.php/MSStandard-0010 Wikimedia\Rdbms\DBQueryError from line 1700 of C:\laragon\www\BS412Cargo\includes\libs\rdbms\database\Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading? {{DISPLAYTITLE:{{#cargo_query:table=MSStandard | fields=MSSTitle | where=_pageID = {{PAGEID}} AND Language = {{#switch: {{int:lang}}|fr="Français"|en="English"}}|no html}} }} Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY `cargo_MSStandard`.`_pageID`,`MSSTitle` LIMIT 100' at line 1 (localhost:3306) Function: CargoSQLQuery::run Query: SELECT `cargo_MSStandard`.`_pageID` AS `cargo_backlink_page_id_MSStandard`,`MSSTitle` AS `MSSTitle` FROM `cargo_MSStandard` WHERE _pageID = 7 AND Language = ORDER BY `cargo_MSStandard`.`_pageID`,`MSSTitle` LIMIT 100 Backtrace: </pre> With Special:CargoQuery the problem occurs if the "Where" field is completed. Filling "Table" and "Fields" gives the expected results One more point, looking at cargo_backlinks there is no data. All ohter cargo tables have data Thanks for your support [[Special:Contributions/2001:861:4745:7590:4027:16E4:389A:2D1F|2001:861:4745:7590:4027:16E4:389A:2D1F]] 11:20, 14 July 2022 (UTC) :I'm guessing that the issue there is that <code><nowiki>{{int:lang}}</nowiki></code> is, for whatever reason, returning a value that's neither "en" nor "fr", and thus messing up the query. I would try replacing this part of the query: <pre>{{#switch: {{int:lang}}|fr="Français"|en="English"}}</pre> :...with this: <pre>'{{#switch: {{int:lang}}|fr=Français|en=English}}'</pre> :Hopefully that will at least prevent the query from crashing. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:26, 14 July 2022 (UTC) ::There is no more database error. Many thanks Yaron [[Special:Contributions/2001:861:4745:7590:2973:A2FE:A833:3E34|2001:861:4745:7590:2973:A2FE:A833:3E34]] 16:35, 14 July 2022 (UTC) == Debugging why Cargo data is not storing == This is using Cargo v3.2. The example page is https://spcodex.wiki/wiki/Haenim. Under the "Releases" section, we use [https://spcodex.wiki/wiki/Template:Release Template:Release] (see source if needed). When I made [https://spcodex.wiki/w/index.php?title=Haenim&diff=74207&oldid=69755 this edit], which doesn't even touch the Releases section, Cargo removed the row from the [https://spcodex.wiki/wiki/Special:CargoTables/releases releases table] (see [https://spcodex.wiki/w/index.php?title=Special%3ACargoQuery&tables=releases&fields=&where=_pageName%3D%22Haenim%22&join_on=&group_by=&having=&order_by%5B0%5D=&order_by_options%5B0%5D=ASC&limit=&offset=0&format= query]). I can't for the life of me figure out why this is. Given I don't have sysadmin access, are there are debugging tips to figure out what's going on? This may have been effected by the MediaWiki 1.38 upgrade on Miraheze. There's at least one other page ([https://spcodex.wiki/wiki/The_End_Is_the_Beginning_Is_the_End The End Is the Beginning Is the End]) that seems to have the same problem. In both cases, other Cargo data (such as the infobox which stores into the <code>songs</code> table) is saving without issue. Thanks for any help you can provide. <span style="font-family:sans-serif">&mdash; <span style="font-weight:bold">[[User:MusikAnimal|<span style="color:black; font-style:italic">MusikAnimal</span>]] <sup>[[User talk:MusikAnimal|<span style="color:green">talk</span>]]</sup></span></span> 21:45, 18 July 2022 (UTC) :That's strange. Normally, I would say calling cargoRecreateData.php from the command line is the best way to see what problems are coming up, but it sounds like you don't have command-line access. If that's the case, then maybe the best approach is to find a call to the "Release" template that does store correctly, and make incremental changes to the non-working one to match the working one, until you find the difference that makes it work/not work. Hopefully that won't take too long. Please let me know if you do! [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 02:23, 19 July 2022 (UTC) ::Well I know it doesn't save if something doesn't pass validations (say you didn't provide a required field). In this case though, there have been no changes to Template:Release, or the wikitext that uses it. That's what had me thinking it had something to do with the MediaWiki upgrade and/or Cargo (which I assume was upgraded in tandem). ::Anyway, I've already compared this use of Template:Release with others that are still working and don't see any obvious reasons the one doesn't work. I will reach out to the sysadmins and see if they can run the script for me. Speaking of which, is it possible to use cargoRecreateData.php and store into a replacement table (keeping the normal one still there for querying), just like you can in the UI? Thanks, <span style="font-family:sans-serif">&mdash; <span style="font-weight:bold">[[User:MusikAnimal|<span style="color:black; font-style:italic">MusikAnimal</span>]] <sup>[[User talk:MusikAnimal|<span style="color:green">talk</span>]]</sup></span></span> 03:51, 19 July 2022 (UTC) :::Yes - just use the "--replacement" flag. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:14, 19 July 2022 (UTC) ::::@[[User:Yaron Koren|Yaron Koren]] Finally got a sysadmin to the run the script, and they said it worked without any errors. The table was fully regenerated, restoring rows that were previously missing. So I'm afraid what's going on is a bit of a mystery... I tested re-saving some of those effected pages and sure enough, it still removes the row from the db. ::::Miraheze staff did mention there were lots of these warnings generated by the script: <code>Notice: Undefined index: wgCargoLegacyNullLuaFieldsAsEmptyString in /srv/mediawiki/w/extensions/Cargo/includes/CargoLuaLibrary.php on line 94</code> ::::That doesn't seem related, but I'm sharing it just in case. ::::My question for you is, does action=recreatedata not do the same thing as the cargoRecreateData.php maintenance script? I've noticed that when I use the UI (action=recreatedata), data regeneration is very slow and often does not finish at all. I have to go through each page that's still missing and do a null edit, then it will appear in the replacement table. I'm guessing this is an issue with the job queue? It may be specific to Miraheze. But at any rate, I'm a real bind here as my wiki is vulnerable to having data be removed slowly over time, anytime someone edits one of the effected pages :( ::::Assuming I were to have sysadmin access, what's the best way to debug what's happening with those page saves and it removing rows from the db? If it helps, I maintain this wasn't an issue some months ago, likely aligned with the MediaWiki/Cargo upgrade to REL1_38. <span style="font-family:sans-serif">&mdash; <span style="font-weight:bold">[[User:MusikAnimal|<span style="color:black; font-style:italic">MusikAnimal</span>]] <sup>[[User talk:MusikAnimal|<span style="color:green">talk</span>]]</sup></span></span> 18:17, 28 July 2022 (UTC) d4mqc3684gokzkeaf8pnrujtmh2k7kw 5387222 5386717 2022-07-28T21:23:09Z Yaron Koren 15560 /* Debugging why Cargo data is not storing */ Reply wikitext text/x-wiki {{Cargo navigation}} {{Archive box| * [[Extension talk:Cargo/Archive January to May 2015|January to May 2015]] * [[Extension talk:Cargo/Archive June to October 2015|June to October 2015]] * [[Extension talk:Cargo/Archive November to December 2015|November to December 2015]] * [[Extension talk:Cargo/Archive January to March 2016|January to March 2016]] * [[Extension talk:Cargo/Archive April to June 2016|April to June 2016]] * [[Extension talk:Cargo/Archive July to October 2016|July to October 2016]] * [[Extension talk:Cargo/Archive November to December 2016|November to December 2016]] * [[Extension talk:Cargo/Archive January to February 2017|January to February 2017]] * [[Extension talk:Cargo/Archive March to July 2017|March to July 2017]] * [[Extension talk:Cargo/Archive August to September 2017|August to September 2017]] * [[Extension talk:Cargo/Archive October to December 2017|October to December 2017]] * [[Extension talk:Cargo/Archive January to February 2018|January to February 2018]] * [[Extension talk:Cargo/Archive March to May 2018|March to May 2018]] * [[Extension talk:Cargo/Archive June to July 2018|June to July 2018]] * [[Extension talk:Cargo/Archive August to September 2018|August to September 2018]] * [[Extension talk:Cargo/Archive October to December 2018|October to December 2018]] * [[Extension talk:Cargo/Archive January 2019|January 2019]] * [[Extension talk:Cargo/Archive February to March 2019|February to March 2019]] * [[Extension talk:Cargo/Archive April to July 2019|April to July 2019]] * [[Extension talk:Cargo/Archive August to October 2019|August to October 2019]] * [[Extension talk:Cargo/Archive November to December 2019|November to December 2019]] * [[Extension talk:Cargo/Archive January to February 2020|January to February 2020]] * [[Extension talk:Cargo/Archive March to April 2020|March to April 2020]] * [[Extension talk:Cargo/Archive May to July 2020|May to July 2020]] * [[Extension talk:Cargo/Archive August to December 2020|August to December 2020]] * [[Extension talk:Cargo/Archive January to April 2021|January to April 2021]] * [[Extension talk:Cargo/Archive May to June 2021|May to June 2021]] * [[Extension talk:Cargo/Archive July to October 2021|July to October 2021]] * [[Extension talk:Cargo/Archive November to December 2021|November to December 2021]] * [[Extension talk:Cargo/Archive January to May 2022|January to May 2022]] }} == Display Format Table without Sortable == I would like to display the results of the query in a table, but not allow for that table to be sorted. Format=Table appears to force sorting on. How can I work around this? [[Special:Contributions/2601:C2:8201:6940:0:0:0:42E2|2601:C2:8201:6940:0:0:0:42E2]] 19:20, 16 June 2022 (UTC) :Well, the table will always be sorted on ''something''. If you want it to ''look'' unsorted, you could always add an "order by=" with some random field that's not in the table, like "order by=_pageID". (Though _pageID will reflect the order in which the pages were created, so maybe that's not ideal either - you could instead do something like "order by=_pageID % 100".) [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 20:04, 16 June 2022 (UTC) ::You could use format=template to create a table from scratch. ::Maybe you could use css to hide the arrow icons. ::Maybe you could use JavaScript to get rid of the class that makes the table sortable. [[User:Jonathan3|Jonathan3]] ([[User talk:Jonathan3|talk]]) 20:11, 16 June 2022 (UTC) :::Oh... maybe I misunderstood the question. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 20:15, 16 June 2022 (UTC) ::::Thank you for the reply. Currently, I am using the workaround of hiding the sorting arrows via css changes. Jonathan3's suggestion to remove the headerSort class via javascript is viable, but I would like to avoid bloating my wiki's common.js with changes like this. [[Special:Contributions/2601:C2:8201:6940:0:0:0:42E2|2601:C2:8201:6940:0:0:0:42E2]] 01:28, 17 June 2022 (UTC) :::::Why do you want to disable sorting, if I may ask? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 02:04, 17 June 2022 (UTC) == table format in lua == Hello how to draw a conclusion in a table <code>local args = { where = 'categories HOLDS "..."', limit = '100', orderBy = '_pageName', format = table }</code> <code>format = table</code> doesn't work, bottom doesn't show (View (previous 50|next 50) (20|50|100|250|500)) Thanks! --Oleksii [[Special:Contributions/212.80.62.177|212.80.62.177]] 10:54, 20 June 2022 (UTC) :There is no way to add that specific footer to the end of query results - for the "table" format or otherwise - in Cargo, as far as I know; that interface is really meant for the bottom of special pages. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 14:07, 20 June 2022 (UTC) == Do not have permission to recreate Cargo data == Hello, I have installed Cargo extension in bluespice free. I have a sysops role. When I try to create a cargo table using ?action=recreatedata I get a permission error "You do not have permission to recreate Cargo data, for the following reason: You are not allowed to execute the action you have requested." What have I to do to get it working ? [[User:Vn596174|Vn596174]] ([[User talk:Vn596174|talk]]) 11:45, 22 June 2022 (UTC) :That's odd - are you sure you're part of the "sysop" group"? And what version of Cargo are you running? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:59, 23 June 2022 (UTC) :I have the same problem. To work around it il did the following: :- deactive all bluespice extensions in settings.d, keeping only mediawiki ones :<?php :return; // Disabled. :- create cargo tables :- active all bluespice extensions :<?php ://return; // Disabled. :Now you can add data to cargo tables but still not use recreate data :I think this is caused by the way BS uses permissions (see BlueSpicePermissionManager [[Extension:PermissionManager/en|Extension:PermissionManager - MediaWiki]]) [[Special:Contributions/2001:861:4745:7590:9D8B:EFCB:F425:7B79|2001:861:4745:7590:9D8B:EFCB:F425:7B79]] 13:39, 16 July 2022 (UTC) == cargoRecreateData throws error after upgrade to MW1.38.1 == Hello, after upgrading to MW 1.38.1, one of my tables is throwing this error for every page when doing cargoRecreateData: <code>PHP Notice:  Undefined index: Image in /var/www/mediawiki-1.38.1/extensions/Cargo/includes/parserfunctions/CargoStore.php on line 472</code> 'Image' is one of the fields and is set to NULL in every entry. There are other fields within the same table that are set to NULL but those are not giving any problem. Thank you very much for your support [[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 08:20, 1 July 2022 (UTC) :This may be a silly question, but does the Cargo table actually contain an "Image" field? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:59, 1 July 2022 (UTC) :: Hello Yaron, yes, it does contain an "Image" field--[[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 07:58, 4 July 2022 (UTC) :::Yes, indeed... what does the line for "Image" look like in the #cargo_declare call? [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 01:16, 5 July 2022 (UTC) :::: Hello, the #cargo_declare looks like this:<code>{{#cargo_declare:_table=Documents|Requires_editing=Boolean (hidden)|Type=String|Project=Page|Activity=Page|Topic=List (,) of String|Scope=List (,) of String|Authors=List (,) of Page (hidden)|Tool=Page (hidden)|Contact=Page (hidden)|Attachments=List (,) of String (hidden)|Image=File|Meeting_time=Datetime (hidden)|Meeting_location=String (hidden)|Meeting_participants_CE=List (,) of Page (hidden)|Meeting_participants_CQ=List (,) of Page (hidden)|Meeting_participants_companies=List (,) of Page (hidden)|Meeting_document_date=Date (hidden)|Car_review=Page (hidden)}}</code> :::: Thanks!--[[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 07:49, 5 July 2022 (UTC)<br> [[File:Screenshot Documents table fields.png|thumb]] :::::Thanks for that listing. You discovered a bug in the handling of "File" fields - sorry about that. I and someone else just checked in [https://phabricator.wikimedia.org/rECRG2e8c4020ed4c1c695d9368ea4efcb3f81e8c704a a fix] for it, so if you get the latest Cargo code, those PHP notices should go away. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 03:07, 6 July 2022 (UTC) :::::: Great, thanks. --[[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 07:44, 6 July 2022 (UTC) :::::: Also, there was another error being thrown, which is still present:<br> <code>Recreating data for Cargo table Activities in 5 seconds... hit [Ctrl]-C to escape.</code><br> <code>Deleting and recreating table...</code><br> <code>Handling template that adds to this table: Activity</code><br> <code>PHP Deprecated: Use of Title::$mDbkeyform was deprecated in MediaWiki 1.37. [Called from CargoRecreateData::recreateAllDataForTable in /var/www/mediawiki-1.38.1/extensions/Cargo/maintenance/cargoRecreateData.php at line 153] in /var/www/mediawiki-1.38.1/includes/debug/MWDebug.php on line 377</code> :Thanks for letting me know about that - this, too, is fixed now, I believe. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 16:53, 6 July 2022 (UTC) :: I confirm it's fixed. Thanks Yaron. --[[User:Carloposo|Carloposo]] ([[User talk:Carloposo|talk]]) 09:06, 7 July 2022 (UTC) == Create Class error message "This appears to be a cross-site request forgery - Save cancelled" == What does this error message mean? I had completed defining all the fields for a table, went to save it and got that message. Before entering it all again and hoping for the best, I would prefer to know what I might have done wrong. I had previously deleted the table and was recreating it with less and altered fields, and was following the same process as for an earlier table that did save successfully. I love the Build Class feature, it is a pity there is no Modify Class as well as manually editing templates to add or edit fields is a painstaking task, hence I have found it easier to start again if there is not much in the table yet. I am using Mediawiki 1.36.2 and Cargo 3.1. Thanks, Robert :I'm guessing/hoping that it's a one-time thing, and if you try it again it'll work fine. That said, if you want to be able to modify the class with a form, check out the [[Extension:Page Schemas|Page Schemas]] extension. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:56, 8 July 2022 (UTC) == Cargo_query error == Hello, Running php update.php after installing the Cargo extension, I have created a cargo table using the following template Template:MSStandard <pre> <noinclude> {{#template_params:MSSReference|MSSTitle|MSSAbstract|MSSPublicationDate|MSSEdition|MSSStatus|MSSType|Language}} {{#cargo_declare:_table=MSStandard|MSSReference=String|MSSTitle=String|MSSAbstract=Text (size=3500)|MSSPublicationDate=String|MSSEdition=String|MSSStatus=String (allowed values=WD,CD,DIS,FDIS,IS)|MSSType=string (allowed values=MSS-A,MSS-B)|Language=String (allowed values=English,Français)}}</noinclude><includeonly>{{#cargo_store:_table=MSStandard}} {{#template_display:_format=standard}} [[Category:MSStandard]] </includeonly> </pre> When I add a page using the template everything is OK, the page is created and the cargo table is populated. Every time I add a cargo query to the page there is an error message <pre> A database query error has occurred. This may indicate a bug in the software. [efdb63d66f6075643dec9f82] /index.php/MSStandard-0010 Wikimedia\Rdbms\DBQueryError from line 1700 of C:\laragon\www\BS412Cargo\includes\libs\rdbms\database\Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading? {{DISPLAYTITLE:{{#cargo_query:table=MSStandard | fields=MSSTitle | where=_pageID = {{PAGEID}} AND Language = {{#switch: {{int:lang}}|fr="Français"|en="English"}}|no html}} }} Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY `cargo_MSStandard`.`_pageID`,`MSSTitle` LIMIT 100' at line 1 (localhost:3306) Function: CargoSQLQuery::run Query: SELECT `cargo_MSStandard`.`_pageID` AS `cargo_backlink_page_id_MSStandard`,`MSSTitle` AS `MSSTitle` FROM `cargo_MSStandard` WHERE _pageID = 7 AND Language = ORDER BY `cargo_MSStandard`.`_pageID`,`MSSTitle` LIMIT 100 Backtrace: </pre> With Special:CargoQuery the problem occurs if the "Where" field is completed. Filling "Table" and "Fields" gives the expected results One more point, looking at cargo_backlinks there is no data. All ohter cargo tables have data Thanks for your support [[Special:Contributions/2001:861:4745:7590:4027:16E4:389A:2D1F|2001:861:4745:7590:4027:16E4:389A:2D1F]] 11:20, 14 July 2022 (UTC) :I'm guessing that the issue there is that <code><nowiki>{{int:lang}}</nowiki></code> is, for whatever reason, returning a value that's neither "en" nor "fr", and thus messing up the query. I would try replacing this part of the query: <pre>{{#switch: {{int:lang}}|fr="Français"|en="English"}}</pre> :...with this: <pre>'{{#switch: {{int:lang}}|fr=Français|en=English}}'</pre> :Hopefully that will at least prevent the query from crashing. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:26, 14 July 2022 (UTC) ::There is no more database error. Many thanks Yaron [[Special:Contributions/2001:861:4745:7590:2973:A2FE:A833:3E34|2001:861:4745:7590:2973:A2FE:A833:3E34]] 16:35, 14 July 2022 (UTC) == Debugging why Cargo data is not storing == This is using Cargo v3.2. The example page is https://spcodex.wiki/wiki/Haenim. Under the "Releases" section, we use [https://spcodex.wiki/wiki/Template:Release Template:Release] (see source if needed). When I made [https://spcodex.wiki/w/index.php?title=Haenim&diff=74207&oldid=69755 this edit], which doesn't even touch the Releases section, Cargo removed the row from the [https://spcodex.wiki/wiki/Special:CargoTables/releases releases table] (see [https://spcodex.wiki/w/index.php?title=Special%3ACargoQuery&tables=releases&fields=&where=_pageName%3D%22Haenim%22&join_on=&group_by=&having=&order_by%5B0%5D=&order_by_options%5B0%5D=ASC&limit=&offset=0&format= query]). I can't for the life of me figure out why this is. Given I don't have sysadmin access, are there are debugging tips to figure out what's going on? This may have been effected by the MediaWiki 1.38 upgrade on Miraheze. There's at least one other page ([https://spcodex.wiki/wiki/The_End_Is_the_Beginning_Is_the_End The End Is the Beginning Is the End]) that seems to have the same problem. In both cases, other Cargo data (such as the infobox which stores into the <code>songs</code> table) is saving without issue. Thanks for any help you can provide. <span style="font-family:sans-serif">&mdash; <span style="font-weight:bold">[[User:MusikAnimal|<span style="color:black; font-style:italic">MusikAnimal</span>]] <sup>[[User talk:MusikAnimal|<span style="color:green">talk</span>]]</sup></span></span> 21:45, 18 July 2022 (UTC) :That's strange. Normally, I would say calling cargoRecreateData.php from the command line is the best way to see what problems are coming up, but it sounds like you don't have command-line access. If that's the case, then maybe the best approach is to find a call to the "Release" template that does store correctly, and make incremental changes to the non-working one to match the working one, until you find the difference that makes it work/not work. Hopefully that won't take too long. Please let me know if you do! [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 02:23, 19 July 2022 (UTC) ::Well I know it doesn't save if something doesn't pass validations (say you didn't provide a required field). In this case though, there have been no changes to Template:Release, or the wikitext that uses it. That's what had me thinking it had something to do with the MediaWiki upgrade and/or Cargo (which I assume was upgraded in tandem). ::Anyway, I've already compared this use of Template:Release with others that are still working and don't see any obvious reasons the one doesn't work. I will reach out to the sysadmins and see if they can run the script for me. Speaking of which, is it possible to use cargoRecreateData.php and store into a replacement table (keeping the normal one still there for querying), just like you can in the UI? Thanks, <span style="font-family:sans-serif">&mdash; <span style="font-weight:bold">[[User:MusikAnimal|<span style="color:black; font-style:italic">MusikAnimal</span>]] <sup>[[User talk:MusikAnimal|<span style="color:green">talk</span>]]</sup></span></span> 03:51, 19 July 2022 (UTC) :::Yes - just use the "--replacement" flag. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 13:14, 19 July 2022 (UTC) ::::@[[User:Yaron Koren|Yaron Koren]] Finally got a sysadmin to the run the script, and they said it worked without any errors. The table was fully regenerated, restoring rows that were previously missing. So I'm afraid what's going on is a bit of a mystery... I tested re-saving some of those effected pages and sure enough, it still removes the row from the db. ::::Miraheze staff did mention there were lots of these warnings generated by the script: <code>Notice: Undefined index: wgCargoLegacyNullLuaFieldsAsEmptyString in /srv/mediawiki/w/extensions/Cargo/includes/CargoLuaLibrary.php on line 94</code> ::::That doesn't seem related, but I'm sharing it just in case. ::::My question for you is, does action=recreatedata not do the same thing as the cargoRecreateData.php maintenance script? I've noticed that when I use the UI (action=recreatedata), data regeneration is very slow and often does not finish at all. I have to go through each page that's still missing and do a null edit, then it will appear in the replacement table. I'm guessing this is an issue with the job queue? It may be specific to Miraheze. But at any rate, I'm a real bind here as my wiki is vulnerable to having data be removed slowly over time, anytime someone edits one of the effected pages :( ::::Assuming I were to have sysadmin access, what's the best way to debug what's happening with those page saves and it removing rows from the db? If it helps, I maintain this wasn't an issue some months ago, likely aligned with the MediaWiki/Cargo upgrade to REL1_38. <span style="font-family:sans-serif">&mdash; <span style="font-weight:bold">[[User:MusikAnimal|<span style="color:black; font-style:italic">MusikAnimal</span>]] <sup>[[User talk:MusikAnimal|<span style="color:green">talk</span>]]</sup></span></span> 18:17, 28 July 2022 (UTC) :::::Thanks for letting me know about that PHP warning - it's indeed unrelated, but it was good to know about. I just checked in a fix for it. In your case, there are three things: cargoRecreateData.php, action=recreatedata, and individual page saves - and it sounds like the last two are failing. It does sound like there's a problem with the job queue running very slowly. But I still recommend that approach of taking a non-working page, and modifying it until its data gets saved correctly, to try to figure out what is causing the problem. I can't think of another solution at the moment. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 21:23, 28 July 2022 (UTC) 45bug9d6hu0k5pg1dp1e0lpj67zsvwp Manual:Installation guide/nl 100 356570 5386660 5383880 2022-07-28T17:14:32Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/nl]] 2mhvcsww3br1wqxh9j28bevxhadj4f9 5386679 5386660 2022-07-28T17:17:37Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/nl]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Magic words/ru 100 358957 5386697 5340905 2022-07-28T17:39:20Z Артём 13327 17625157 wikitext text/x-wiki <languages/> {{ExtensionTypes}} [[File:MediaWiki-extensions-icon.svg|125px|alt=Расширения MediaWiki|right]] {{notice|1=Ищете '''список волшебных слов''' и переменных? Смотрите '''{{ll|Help:Magic words}}'''.}} '''Волшебные слова''' — это техника для соединения разнообразных текстовых цепочек к одному ID которое ассоциируется с этой функцией. И [[Special:MyLanguage/Manual:Variables|переменные]], и [[Special:MyLanguage/Manual:Parser functions|функции парсера]] используют данную технику. Весь текст, прикрепленный к данному ID, будет заменен на возвращаемое значение функции. Сопоставление текстовых строк и идентификатора сохраняется в переменной <code>$magicWords</code> в файле, который можно загрузить с помощью {{ll|Manual:$wgExtensionMessagesFiles|$wgExtensionMessagesFiles[]}}. Стандартные волшебные слова реализованы в {{ll|Manual:CoreParserFunctions.php|CoreParserFunctions.php}}. == Как работают волшебные слова == Всякий раз, когда MediaWiki находит текст между двойными скобками (<code><nowiki>{{</nowiki>XXX ...}}</code>), необходимо решить, является ли XXX [[Special:MyLanguage/Manual:Variables|переменной]], [[Special:MyLanguage/Manual:Parser functions|функцией парсера]] или [[Special:MyLanguage/Help:Templates|шаблоном]]. Чтобы сделать это, задается несколько вопросов: #<span class="mw-translate-fuzzy">'''Есть ли связанное ID волшебного слова?''' В качестве первого шага разбора разметки в виде <code><nowiki>{{XXX...}}</nowiki></code>, MediaWiki пытается перевести ''XXX'' в ID волшебного слова. Таблица переводов определяется в $magicWords.</span> #*<span class="mw-translate-fuzzy">Если нет связанного с ''XXX'' ID волшебного слова, предполагается, что ''XXX'' — это [[Special:MyLanguage/Help:Templates|шаблон]].</span> #:<br/> #'''Переменная ли это?''' <em>Если найдено</em> ID волшебного слова, MediaWiki далее проверяет есть ли у него какие-либо параметры. #*Если параметры не найдены, MediaWiki проверяет, объявлен ли идентификатор волшебного слова как идентификатор переменной. Чтобы проверить это, он получает список обслуживающих волшебных слов, вызывая <code>MagicWord::getVariableIDs()</code>. Этот метод получает свой список идентификаторов переменных из жестко закодированного списка идентификаторов переменных (см.{{ll|Help:Variables}}) и из списка идентификаторов пользовательских переменных, предоставляемых всеми функциями, прикрепленными к ловушке {{ll|Manual:Hooks/MagicWordwgVariableIDs|MagicWordwgVariableIDs}}. #**Если ID волшебного слова было классифицировано как переменная, хуки MediaWiki будут вызывать функции, связанные с именем события {{ll|Manual:Hooks/ParserGetVariableValueSwitch|ParserGetVariableValueSwitch}}, пока не будет найдена та, которая распознает волшебное слово и сможет вернуть его значение. #:<br/> #'''Функция парсера ли это?''' Если нет каких-либо параметров или если ID волшебного слова не найдено в списке переменных ID волшебных слов, тогда MediaWiki подразумевает что это волшебное слово [[Special:MyLanguage/Manual:Parser functions|функция парсера]] или [[Special:MyLanguage/Help:Templates|шаблон]]. Если ID волшебного слова найдено в списке функций парсера, который объявляется с помощью вызова <code>$wgParser->setFunctionHook($magicWordId, $renderingFunctionName)</code>, то рассматривается как функция парсера и отображается с помощью функции под именем <code>$renderingFunctionName</code>. Иначе предполагается что это шаблон. {{note|1= <div lang="en" dir="ltr" class="mw-content-ltr"> By convention: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">The magic words called variables are capitalised, case-sensitive and do not have space characters.</span> * Parserfunctions are prefixed with a hash sign (<nowiki>{{#</nowiki>), are case insensitive and do not include space characters. <div lang="en" dir="ltr" class="mw-content-ltr"> This is however a convention and one not consistently applied (for historic reasons). </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Variables do not have space characters, but some translations of variables in other languages DO have spaces</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Variables generally are capitalised and case-sensitive, but some parser functions also use this convention.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Some parser functions start with a hash sign, but some do not.</span> Where possible you should follow the conventions when defining or translating magic words. Magic words are higher in priority than templates, so any magic word defined, will block the usage of that defined name as a template. Following the conventions avoids adding more and more potential collisions. }} == Определение волшебных слов == Чтобы волшебные слова творили своё волшебство, мы должны определить две вещи: * соответствие вики-текста с идентификатором волшебного слова * соответствие идентификатора волшебного слова и какой-то php-функции, которая интерпретирует волшебное слово. === Проведение соответствия вики-текста с идентификатором волшебного слова === Переменная $magicWords используется для ассоциации всех идентификаторов магических слов с языково-зависимым массивом, который описывает все текстовые строки, которые связаны с идентификатором волшебного слова. Важно: Это только настраивает отображение интернационализации (i18n), но вам всё равно нужно написать другой код, чтобы MediaWiki использовал волшебное слово для чего угодно. Also, make sure that you initialize <code>$magicWords</code> as an empty array before adding language-specific values or you will get errors when trying to load the magic word and will need to rebuild your localization cache before it will work. Первый элемент этого массива это целочисленный флаг, указывающий, является ли волшебное чувствительным к регистру. Остальные элементы это список текста, который должен быть связан с ID волшебного слова. Если флаг чувствительности к регистру равен 0, то любые варианты регистра в имени будут совпадать. Если флаг чувствительности к регистру равен 1, то только точные совпадения по регистру будут ассоциированы с ID волшебного слова. Таким образом формат выглядит как <code>$magicWords['en'] = [ 'InternalName' => [ 0, 'NameUserTypes', 'AdditionalAliasUserCanType' ] ];</code> Такая ассоциация создается переменной $magicWords , в файле, зарегистрированном с помощью {{ll|Manual:$wgExtensionMessagesFiles|$wgExtensionMessagesFiles[]}}. В приведенном ниже примере установка MediaWiki на испанском языке будет связывать идентификатор волшебного слова 'MAG_CUSTOM' с «personalizado», «custom», «PERSONALIZADO», «CUSTOM» и всеми другими вариантами регистра. В англоязычной MediaWiki только «custom» в различных комбинациях регистров будет отображаться в 'MAG_CUSTOM': Файл <code>Example.i18n.magic.php</code>: <syntaxhighlight lang="php"> <?php $magicWords = []; $magicWords['en'] = [ 'MAG_CUSTOM' => [ 0, 'custom' ], ]; $magicWords['es'] = [ 'MAG_CUSTOM' => [ 0, 'personalizado' ], ]; </syntaxhighlight> В части файла extension.json: <syntaxhighlight lang="json"> "ExtensionMessagesFiles": { "ExampleMagic": "Example.i18n.magic.php" } </syntaxhighlight> Обратите внимание, что "ExampleMagic" отличается от ключа, который вы бы использовали для простого файла интернационализации (обычно это просто название расширения, то есть "Example"). "Magic" было добавлено ​​намеренно, чтобы одно не перезаписывало другое. ==== Во встроенном PHP ==== Вы можете связать волшебные слова прямо в PHP, а не через файл i18n. Это полезно при определении связок(хуков) в <code>LocalSettings.php</code>. <syntaxhighlight lang="php"> MediaWiki\MediaWikiServices::getInstance()->getContentLanguage()->mMagicExtensions['wikicodeToHtml'] = ['MAG_CUSTOM', 'custom']; </syntaxhighlight> === Ассоциация ID волшебного слова с PHP-функцией === Механизм ассоциации ID волшебного слова с функцией рендеринга зависит от того, будет ли волшебное слово использоваться как [[Special:MyLanguage/Manual:Parser functions|функция парсера]] или как [[Special:MyLanguage/Manual:Variables|переменная]]. Для получения более подробной информации смотрите: * {{ll|Manual:Parser functions}} * {{ll|Manual:Variables}} === Регистрация волшебных слов === В MediaWiki отсутствует явное требование регистрации ID волшебных слов. Достаточно зарегистрировать функцию парсера или переменные, которые их используют. === Локализация === :''Для справки смотрите [[Special:MyLanguage/Help:Magic words#Localisation|Справка:Волшебные слова#Локализация]].'' Вы можете прочитать больше об определении и использовании волшебных слов для локализации на [[Special:MyLanguage/Manual:Messages API|Manual:Messages API]], [[Special:MyLanguage/Manual:Language#Namespaces|Manual:Language#Namespaces]]; [[Special:MyLanguage/Help:System_message#Avoid_.7B.7BSITENAME.7D.7D_in_messages|<nowiki>Avoid {{SITENAME}} in messages</nowiki>]]. ==Переключатели поведения (волшебные слова с двойным подчеркиванием)== <span class="mw-translate-fuzzy">Переключатели поведения это особый тип волшебных слов. Их можно узнать по двойному подчеркиванию (вместо двойных скобок). Например, <code><nowiki>__NOTOC__</nowiki></code>.</span> Пример: <code><nowiki>__NOTOC__</nowiki></code> Эти волшебные слова обычно не выводят какой-либо контент, а вместо этого изменяют поведение страницы и/или устанавливают свойство страницы. Эти волшебные слова перечислены в {{phpi|MagicWordFactory::mDoubleUnderscoreIDs}}, а также в [[Special:MyLanguage/Help:Magic words#Behavior switches|Справка:волшебные слова#Переключатели поведения]]. Эффекты наиболее стандартных сценариев переключений описаны в {{phpi|Parser::handleDoubleUnderscore()}}. Если конкретный эффект не определен, волшебное слово просто установит свойство страницы в таблице page_props. === Поведение настраиваемого переключателя === Для применения поведения настраиваемого переключателя. <syntaxhighlight lang="php"> // __CUSTOM__ behavior switch in LocalSettings.php $wgHooks['GetDoubleUnderscoreIDs'][] = function ( &$ids ) { $ids[] = 'custom'; MediaWiki\MediaWikiServices::getInstance()->getContentLanguage()->mMagicExtensions['custom'] = ['custom', 'custom']; }; $wgHooks['ParserAfterParse'][] = function ( Parser $parser, &$text, StripState $stripState ) { if(isset($parser->mDoubleUnderscores['custom'])) { // Do behavior switching here ... } }; </syntaxhighlight> == Посмотрите также == *{{ll|Help:Magic words}} - Список таких переменных как <nowiki>{{PAGENAME}}</nowiki> и <nowiki>{{SERVER}}</nowiki> [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:Magic words{{#translation:}}|{{PAGENAME}}]] 0dyft5rsbpfuil0gzd41s01z4eyy1uw 5386699 5386697 2022-07-28T17:39:57Z Артём 13327 17625157 wikitext text/x-wiki <languages/> {{ExtensionTypes}} [[File:MediaWiki-extensions-icon.svg|125px|alt=Расширения MediaWiki|right]] {{notice|1=Ищете '''список волшебных слов''' и переменных? Смотрите '''{{ll|Help:Magic words}}'''.}} '''Волшебные слова''' — это техника для соединения разнообразных текстовых цепочек к одному ID которое ассоциируется с этой функцией. И [[Special:MyLanguage/Manual:Variables|переменные]], и [[Special:MyLanguage/Manual:Parser functions|функции парсера]] используют данную технику. Весь текст, прикрепленный к данному ID, будет заменен на возвращаемое значение функции. Сопоставление текстовых строк и идентификатора сохраняется в переменной <code>$magicWords</code> в файле, который можно загрузить с помощью {{ll|Manual:$wgExtensionMessagesFiles|$wgExtensionMessagesFiles[]}}. Стандартные волшебные слова реализованы в {{ll|Manual:CoreParserFunctions.php|CoreParserFunctions.php}}. == Как работают волшебные слова == Всякий раз, когда MediaWiki находит текст между двойными скобками (<code><nowiki>{{</nowiki>XXX ...}}</code>), необходимо решить, является ли XXX [[Special:MyLanguage/Manual:Variables|переменной]], [[Special:MyLanguage/Manual:Parser functions|функцией парсера]] или [[Special:MyLanguage/Help:Templates|шаблоном]]. Чтобы сделать это, задается несколько вопросов: #'''Есть ли связанное ID волшебного слова?''' В качестве первого шага разбора разметки в виде <code><nowiki>{{XXX...}}</nowiki></code>, MediaWiki пытается перевести ''XXX'' в ID волшебного слова. Таблица переводов определяется в $magicWords. #*<span class="mw-translate-fuzzy">Если нет связанного с ''XXX'' ID волшебного слова, предполагается, что ''XXX'' — это [[Special:MyLanguage/Help:Templates|шаблон]].</span> #:<br/> #'''Переменная ли это?''' <em>Если найдено</em> ID волшебного слова, MediaWiki далее проверяет есть ли у него какие-либо параметры. #*Если параметры не найдены, MediaWiki проверяет, объявлен ли идентификатор волшебного слова как идентификатор переменной. Чтобы проверить это, он получает список обслуживающих волшебных слов, вызывая <code>MagicWord::getVariableIDs()</code>. Этот метод получает свой список идентификаторов переменных из жестко закодированного списка идентификаторов переменных (см.{{ll|Help:Variables}}) и из списка идентификаторов пользовательских переменных, предоставляемых всеми функциями, прикрепленными к ловушке {{ll|Manual:Hooks/MagicWordwgVariableIDs|MagicWordwgVariableIDs}}. #**Если ID волшебного слова было классифицировано как переменная, хуки MediaWiki будут вызывать функции, связанные с именем события {{ll|Manual:Hooks/ParserGetVariableValueSwitch|ParserGetVariableValueSwitch}}, пока не будет найдена та, которая распознает волшебное слово и сможет вернуть его значение. #:<br/> #'''Функция парсера ли это?''' Если нет каких-либо параметров или если ID волшебного слова не найдено в списке переменных ID волшебных слов, тогда MediaWiki подразумевает что это волшебное слово [[Special:MyLanguage/Manual:Parser functions|функция парсера]] или [[Special:MyLanguage/Help:Templates|шаблон]]. Если ID волшебного слова найдено в списке функций парсера, который объявляется с помощью вызова <code>$wgParser->setFunctionHook($magicWordId, $renderingFunctionName)</code>, то рассматривается как функция парсера и отображается с помощью функции под именем <code>$renderingFunctionName</code>. Иначе предполагается что это шаблон. {{note|1= <div lang="en" dir="ltr" class="mw-content-ltr"> By convention: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">The magic words called variables are capitalised, case-sensitive and do not have space characters.</span> * Parserfunctions are prefixed with a hash sign (<nowiki>{{#</nowiki>), are case insensitive and do not include space characters. <div lang="en" dir="ltr" class="mw-content-ltr"> This is however a convention and one not consistently applied (for historic reasons). </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Variables do not have space characters, but some translations of variables in other languages DO have spaces</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Variables generally are capitalised and case-sensitive, but some parser functions also use this convention.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Some parser functions start with a hash sign, but some do not.</span> Where possible you should follow the conventions when defining or translating magic words. Magic words are higher in priority than templates, so any magic word defined, will block the usage of that defined name as a template. Following the conventions avoids adding more and more potential collisions. }} == Определение волшебных слов == Чтобы волшебные слова творили своё волшебство, мы должны определить две вещи: * соответствие вики-текста с идентификатором волшебного слова * соответствие идентификатора волшебного слова и какой-то php-функции, которая интерпретирует волшебное слово. === Проведение соответствия вики-текста с идентификатором волшебного слова === Переменная $magicWords используется для ассоциации всех идентификаторов магических слов с языково-зависимым массивом, который описывает все текстовые строки, которые связаны с идентификатором волшебного слова. Важно: Это только настраивает отображение интернационализации (i18n), но вам всё равно нужно написать другой код, чтобы MediaWiki использовал волшебное слово для чего угодно. Also, make sure that you initialize <code>$magicWords</code> as an empty array before adding language-specific values or you will get errors when trying to load the magic word and will need to rebuild your localization cache before it will work. Первый элемент этого массива это целочисленный флаг, указывающий, является ли волшебное чувствительным к регистру. Остальные элементы это список текста, который должен быть связан с ID волшебного слова. Если флаг чувствительности к регистру равен 0, то любые варианты регистра в имени будут совпадать. Если флаг чувствительности к регистру равен 1, то только точные совпадения по регистру будут ассоциированы с ID волшебного слова. Таким образом формат выглядит как <code>$magicWords['en'] = [ 'InternalName' => [ 0, 'NameUserTypes', 'AdditionalAliasUserCanType' ] ];</code> Такая ассоциация создается переменной $magicWords , в файле, зарегистрированном с помощью {{ll|Manual:$wgExtensionMessagesFiles|$wgExtensionMessagesFiles[]}}. В приведенном ниже примере установка MediaWiki на испанском языке будет связывать идентификатор волшебного слова 'MAG_CUSTOM' с «personalizado», «custom», «PERSONALIZADO», «CUSTOM» и всеми другими вариантами регистра. В англоязычной MediaWiki только «custom» в различных комбинациях регистров будет отображаться в 'MAG_CUSTOM': Файл <code>Example.i18n.magic.php</code>: <syntaxhighlight lang="php"> <?php $magicWords = []; $magicWords['en'] = [ 'MAG_CUSTOM' => [ 0, 'custom' ], ]; $magicWords['es'] = [ 'MAG_CUSTOM' => [ 0, 'personalizado' ], ]; </syntaxhighlight> В части файла extension.json: <syntaxhighlight lang="json"> "ExtensionMessagesFiles": { "ExampleMagic": "Example.i18n.magic.php" } </syntaxhighlight> Обратите внимание, что "ExampleMagic" отличается от ключа, который вы бы использовали для простого файла интернационализации (обычно это просто название расширения, то есть "Example"). "Magic" было добавлено ​​намеренно, чтобы одно не перезаписывало другое. ==== Во встроенном PHP ==== Вы можете связать волшебные слова прямо в PHP, а не через файл i18n. Это полезно при определении связок(хуков) в <code>LocalSettings.php</code>. <syntaxhighlight lang="php"> MediaWiki\MediaWikiServices::getInstance()->getContentLanguage()->mMagicExtensions['wikicodeToHtml'] = ['MAG_CUSTOM', 'custom']; </syntaxhighlight> === Ассоциация ID волшебного слова с PHP-функцией === Механизм ассоциации ID волшебного слова с функцией рендеринга зависит от того, будет ли волшебное слово использоваться как [[Special:MyLanguage/Manual:Parser functions|функция парсера]] или как [[Special:MyLanguage/Manual:Variables|переменная]]. Для получения более подробной информации смотрите: * {{ll|Manual:Parser functions}} * {{ll|Manual:Variables}} === Регистрация волшебных слов === В MediaWiki отсутствует явное требование регистрации ID волшебных слов. Достаточно зарегистрировать функцию парсера или переменные, которые их используют. === Локализация === :''Для справки смотрите [[Special:MyLanguage/Help:Magic words#Localisation|Справка:Волшебные слова#Локализация]].'' Вы можете прочитать больше об определении и использовании волшебных слов для локализации на [[Special:MyLanguage/Manual:Messages API|Manual:Messages API]], [[Special:MyLanguage/Manual:Language#Namespaces|Manual:Language#Namespaces]]; [[Special:MyLanguage/Help:System_message#Avoid_.7B.7BSITENAME.7D.7D_in_messages|<nowiki>Avoid {{SITENAME}} in messages</nowiki>]]. ==Переключатели поведения (волшебные слова с двойным подчеркиванием)== <span class="mw-translate-fuzzy">Переключатели поведения это особый тип волшебных слов. Их можно узнать по двойному подчеркиванию (вместо двойных скобок). Например, <code><nowiki>__NOTOC__</nowiki></code>.</span> Пример: <code><nowiki>__NOTOC__</nowiki></code> Эти волшебные слова обычно не выводят какой-либо контент, а вместо этого изменяют поведение страницы и/или устанавливают свойство страницы. Эти волшебные слова перечислены в {{phpi|MagicWordFactory::mDoubleUnderscoreIDs}}, а также в [[Special:MyLanguage/Help:Magic words#Behavior switches|Справка:волшебные слова#Переключатели поведения]]. Эффекты наиболее стандартных сценариев переключений описаны в {{phpi|Parser::handleDoubleUnderscore()}}. Если конкретный эффект не определен, волшебное слово просто установит свойство страницы в таблице page_props. === Поведение настраиваемого переключателя === Для применения поведения настраиваемого переключателя. <syntaxhighlight lang="php"> // __CUSTOM__ behavior switch in LocalSettings.php $wgHooks['GetDoubleUnderscoreIDs'][] = function ( &$ids ) { $ids[] = 'custom'; MediaWiki\MediaWikiServices::getInstance()->getContentLanguage()->mMagicExtensions['custom'] = ['custom', 'custom']; }; $wgHooks['ParserAfterParse'][] = function ( Parser $parser, &$text, StripState $stripState ) { if(isset($parser->mDoubleUnderscores['custom'])) { // Do behavior switching here ... } }; </syntaxhighlight> == Посмотрите также == *{{ll|Help:Magic words}} - Список таких переменных как <nowiki>{{PAGENAME}}</nowiki> и <nowiki>{{SERVER}}</nowiki> [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:Magic words{{#translation:}}|{{PAGENAME}}]] h9r4pvwmryy5jyk2rubtai6061idl7q 5386701 5386699 2022-07-28T17:40:27Z Артём 13327 17625157 wikitext text/x-wiki <languages/> {{ExtensionTypes}} [[File:MediaWiki-extensions-icon.svg|125px|alt=Расширения MediaWiki|right]] {{notice|1=Ищете '''список волшебных слов''' и переменных? Смотрите '''{{ll|Help:Magic words}}'''.}} '''Волшебные слова''' — это техника для соединения разнообразных текстовых цепочек к одному ID которое ассоциируется с этой функцией. И [[Special:MyLanguage/Manual:Variables|переменные]], и [[Special:MyLanguage/Manual:Parser functions|функции парсера]] используют данную технику. Весь текст, прикрепленный к данному ID, будет заменен на возвращаемое значение функции. Сопоставление текстовых строк и идентификатора сохраняется в переменной <code>$magicWords</code> в файле, который можно загрузить с помощью {{ll|Manual:$wgExtensionMessagesFiles|$wgExtensionMessagesFiles[]}}. Стандартные волшебные слова реализованы в {{ll|Manual:CoreParserFunctions.php|CoreParserFunctions.php}}. == Как работают волшебные слова == Всякий раз, когда MediaWiki находит текст между двойными скобками (<code><nowiki>{{</nowiki>XXX ...}}</code>), необходимо решить, является ли XXX [[Special:MyLanguage/Manual:Variables|переменной]], [[Special:MyLanguage/Manual:Parser functions|функцией парсера]] или [[Special:MyLanguage/Help:Templates|шаблоном]]. Чтобы сделать это, задается несколько вопросов: #'''Есть ли связанное ID волшебного слова?''' В качестве первого шага разбора разметки в виде <code><nowiki>{{XXX...}}</nowiki></code>, MediaWiki пытается перевести ''XXX'' в ID волшебного слова. Таблица переводов определяется в $magicWords. #*Если нет связанного с ''XXX'' ID волшебного слова, предполагается, что ''XXX'' — это [[Special:MyLanguage/Help:Templates|шаблон]]. #:<br/> #'''Переменная ли это?''' <em>Если найдено</em> ID волшебного слова, MediaWiki далее проверяет есть ли у него какие-либо параметры. #*Если параметры не найдены, MediaWiki проверяет, объявлен ли идентификатор волшебного слова как идентификатор переменной. Чтобы проверить это, он получает список обслуживающих волшебных слов, вызывая <code>MagicWord::getVariableIDs()</code>. Этот метод получает свой список идентификаторов переменных из жестко закодированного списка идентификаторов переменных (см.{{ll|Help:Variables}}) и из списка идентификаторов пользовательских переменных, предоставляемых всеми функциями, прикрепленными к ловушке {{ll|Manual:Hooks/MagicWordwgVariableIDs|MagicWordwgVariableIDs}}. #**Если ID волшебного слова было классифицировано как переменная, хуки MediaWiki будут вызывать функции, связанные с именем события {{ll|Manual:Hooks/ParserGetVariableValueSwitch|ParserGetVariableValueSwitch}}, пока не будет найдена та, которая распознает волшебное слово и сможет вернуть его значение. #:<br/> #'''Функция парсера ли это?''' Если нет каких-либо параметров или если ID волшебного слова не найдено в списке переменных ID волшебных слов, тогда MediaWiki подразумевает что это волшебное слово [[Special:MyLanguage/Manual:Parser functions|функция парсера]] или [[Special:MyLanguage/Help:Templates|шаблон]]. Если ID волшебного слова найдено в списке функций парсера, который объявляется с помощью вызова <code>$wgParser->setFunctionHook($magicWordId, $renderingFunctionName)</code>, то рассматривается как функция парсера и отображается с помощью функции под именем <code>$renderingFunctionName</code>. Иначе предполагается что это шаблон. {{note|1= <div lang="en" dir="ltr" class="mw-content-ltr"> By convention: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">The magic words called variables are capitalised, case-sensitive and do not have space characters.</span> * Parserfunctions are prefixed with a hash sign (<nowiki>{{#</nowiki>), are case insensitive and do not include space characters. <div lang="en" dir="ltr" class="mw-content-ltr"> This is however a convention and one not consistently applied (for historic reasons). </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Variables do not have space characters, but some translations of variables in other languages DO have spaces</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Variables generally are capitalised and case-sensitive, but some parser functions also use this convention.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Some parser functions start with a hash sign, but some do not.</span> Where possible you should follow the conventions when defining or translating magic words. Magic words are higher in priority than templates, so any magic word defined, will block the usage of that defined name as a template. Following the conventions avoids adding more and more potential collisions. }} == Определение волшебных слов == Чтобы волшебные слова творили своё волшебство, мы должны определить две вещи: * соответствие вики-текста с идентификатором волшебного слова * соответствие идентификатора волшебного слова и какой-то php-функции, которая интерпретирует волшебное слово. === Проведение соответствия вики-текста с идентификатором волшебного слова === Переменная $magicWords используется для ассоциации всех идентификаторов магических слов с языково-зависимым массивом, который описывает все текстовые строки, которые связаны с идентификатором волшебного слова. Важно: Это только настраивает отображение интернационализации (i18n), но вам всё равно нужно написать другой код, чтобы MediaWiki использовал волшебное слово для чего угодно. Also, make sure that you initialize <code>$magicWords</code> as an empty array before adding language-specific values or you will get errors when trying to load the magic word and will need to rebuild your localization cache before it will work. Первый элемент этого массива это целочисленный флаг, указывающий, является ли волшебное чувствительным к регистру. Остальные элементы это список текста, который должен быть связан с ID волшебного слова. Если флаг чувствительности к регистру равен 0, то любые варианты регистра в имени будут совпадать. Если флаг чувствительности к регистру равен 1, то только точные совпадения по регистру будут ассоциированы с ID волшебного слова. Таким образом формат выглядит как <code>$magicWords['en'] = [ 'InternalName' => [ 0, 'NameUserTypes', 'AdditionalAliasUserCanType' ] ];</code> Такая ассоциация создается переменной $magicWords , в файле, зарегистрированном с помощью {{ll|Manual:$wgExtensionMessagesFiles|$wgExtensionMessagesFiles[]}}. В приведенном ниже примере установка MediaWiki на испанском языке будет связывать идентификатор волшебного слова 'MAG_CUSTOM' с «personalizado», «custom», «PERSONALIZADO», «CUSTOM» и всеми другими вариантами регистра. В англоязычной MediaWiki только «custom» в различных комбинациях регистров будет отображаться в 'MAG_CUSTOM': Файл <code>Example.i18n.magic.php</code>: <syntaxhighlight lang="php"> <?php $magicWords = []; $magicWords['en'] = [ 'MAG_CUSTOM' => [ 0, 'custom' ], ]; $magicWords['es'] = [ 'MAG_CUSTOM' => [ 0, 'personalizado' ], ]; </syntaxhighlight> В части файла extension.json: <syntaxhighlight lang="json"> "ExtensionMessagesFiles": { "ExampleMagic": "Example.i18n.magic.php" } </syntaxhighlight> Обратите внимание, что "ExampleMagic" отличается от ключа, который вы бы использовали для простого файла интернационализации (обычно это просто название расширения, то есть "Example"). "Magic" было добавлено ​​намеренно, чтобы одно не перезаписывало другое. ==== Во встроенном PHP ==== Вы можете связать волшебные слова прямо в PHP, а не через файл i18n. Это полезно при определении связок(хуков) в <code>LocalSettings.php</code>. <syntaxhighlight lang="php"> MediaWiki\MediaWikiServices::getInstance()->getContentLanguage()->mMagicExtensions['wikicodeToHtml'] = ['MAG_CUSTOM', 'custom']; </syntaxhighlight> === Ассоциация ID волшебного слова с PHP-функцией === Механизм ассоциации ID волшебного слова с функцией рендеринга зависит от того, будет ли волшебное слово использоваться как [[Special:MyLanguage/Manual:Parser functions|функция парсера]] или как [[Special:MyLanguage/Manual:Variables|переменная]]. Для получения более подробной информации смотрите: * {{ll|Manual:Parser functions}} * {{ll|Manual:Variables}} === Регистрация волшебных слов === В MediaWiki отсутствует явное требование регистрации ID волшебных слов. Достаточно зарегистрировать функцию парсера или переменные, которые их используют. === Локализация === :''Для справки смотрите [[Special:MyLanguage/Help:Magic words#Localisation|Справка:Волшебные слова#Локализация]].'' Вы можете прочитать больше об определении и использовании волшебных слов для локализации на [[Special:MyLanguage/Manual:Messages API|Manual:Messages API]], [[Special:MyLanguage/Manual:Language#Namespaces|Manual:Language#Namespaces]]; [[Special:MyLanguage/Help:System_message#Avoid_.7B.7BSITENAME.7D.7D_in_messages|<nowiki>Avoid {{SITENAME}} in messages</nowiki>]]. ==Переключатели поведения (волшебные слова с двойным подчеркиванием)== <span class="mw-translate-fuzzy">Переключатели поведения это особый тип волшебных слов. Их можно узнать по двойному подчеркиванию (вместо двойных скобок). Например, <code><nowiki>__NOTOC__</nowiki></code>.</span> Пример: <code><nowiki>__NOTOC__</nowiki></code> Эти волшебные слова обычно не выводят какой-либо контент, а вместо этого изменяют поведение страницы и/или устанавливают свойство страницы. Эти волшебные слова перечислены в {{phpi|MagicWordFactory::mDoubleUnderscoreIDs}}, а также в [[Special:MyLanguage/Help:Magic words#Behavior switches|Справка:волшебные слова#Переключатели поведения]]. Эффекты наиболее стандартных сценариев переключений описаны в {{phpi|Parser::handleDoubleUnderscore()}}. Если конкретный эффект не определен, волшебное слово просто установит свойство страницы в таблице page_props. === Поведение настраиваемого переключателя === Для применения поведения настраиваемого переключателя. <syntaxhighlight lang="php"> // __CUSTOM__ behavior switch in LocalSettings.php $wgHooks['GetDoubleUnderscoreIDs'][] = function ( &$ids ) { $ids[] = 'custom'; MediaWiki\MediaWikiServices::getInstance()->getContentLanguage()->mMagicExtensions['custom'] = ['custom', 'custom']; }; $wgHooks['ParserAfterParse'][] = function ( Parser $parser, &$text, StripState $stripState ) { if(isset($parser->mDoubleUnderscores['custom'])) { // Do behavior switching here ... } }; </syntaxhighlight> == Посмотрите также == *{{ll|Help:Magic words}} - Список таких переменных как <nowiki>{{PAGENAME}}</nowiki> и <nowiki>{{SERVER}}</nowiki> [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:Magic words{{#translation:}}|{{PAGENAME}}]] i5n99uakwjtqhyeelzx5lk4fgeycepd Manual:Installation guide/th 100 363447 5386670 5381109 2022-07-28T17:14:37Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/th]] avls25auwf4c5eawzlx2u7m8y4ehd95 5386695 5386670 2022-07-28T17:30:49Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/th]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Installation guide/sv 100 363459 5386668 5381106 2022-07-28T17:14:36Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/sv]] 6ygndy3khxczu516p8ywc2msv9xo5v0 Extension:Cargo/de 102 364567 5387030 5364149 2022-07-28T19:53:39Z ThisCarthing 17456337 wikitext text/x-wiki <languages/> {{Cargo navigation}} {{Extension |status = stable |type1 = special |type2 = api |type3 = parser function |newhook1 = CargoSetFormatClasses |newhook2 = CargoBeforeStoreData |newhook3 = CargoDisplayExportData |newhook4 = CargoTablesSetAllowedActions |newhook5 = CargoTablesSetActionLinks |username = Yaron Koren |author = [[User:Yaron Koren|Yaron Koren]] <yaron57@gmail.com> |description = Eine Erweiterung, die das Speichern und Abfragen von in enthaltenen Daten ermöglicht. |image = Cargo logo.png |imagesize = 120px |version = 3.2 |update = {{ym|2022|4}} |compatibility policy = master |mediawiki = 1.32+ |download = Siehe {{ll|Extension:Cargo/Download and installation}} |changelog = |example = [http://discoursedb.org/wiki/Main_Page Eine Seite mit verschiedenen Anrufen auf #cargo_query] |namespace = |tags = |bugzilla = Cargo |translate = ext-cargo |table1 = cargo_tables |table2 = cargo_pages }} '''Cargo''' ist eine Erweiterung von MediaWiki, die eine einfache Möglichkeit bietet, die in den Aufrufen von Vorlagen, wie z.B. Infoboxen, enthaltenen Daten zu speichern und abzufragen. Es ist vom Konzept her ähnlich wie die Erweiterung {{ll|Extension:Semantic MediaWiki|nsp=0}}, bietet aber eine Reihe von Vorteilen, einschließlich der einfachen Installation und Nutzung. Cargo speichert alle seine Daten in Datenbanktabellen, die entweder in der MediaWiki-eigenen Datenbank (Standard) oder in einer separaten Datenbank abgelegt werden können. In den meisten Fällen werden die Daten jeder gespeicherten Vorlage in einer einzigen DB-Tabelle gespeichert, mit einer Spalte für jeden relevanten Vorlagenparameter. Es gibt einige wenige Ausnahmen: Die Handhabung von Vorlagenfeldern, die Arrays/Wertelisten enthalten, und von Feldern, die geographische Koordinaten enthalten, ist aufgrund der schlechten nativen Handhabung dieser Datentypen in den meisten DB-Systemen komplexer. Und mehrere Vorlagen können so eingestellt werden, dass alle ihre Daten in einer DB-Tabelle speichern. Die Erweiterung definiert eine Reihe von Parser-Funktionen; diese drei sind die wichtigsten: * <code>#cargo_declare</code> - innerhalb des {{tag|noinclude|open}}-Teils einer Vorlage platziert; sie definiert das Schema für eine Tabelle. * <code>#cargo_store</code> - Speichert eine Zeile in einer Cargo-Tabelle. Normalerweise innerhalb des {{tag|includeonly|open}}-Teils einer Vorlage platziert. * <code>#cargo_query</code> - SQL ähnliche Abfrage über eine oder mehrere Cargo-Tabellen. Die anderen definierten Parser-Funktionen sind: * <code>#cargo_attach</code> - <span lang="en" dir="ltr" class="mw-content-ltr">defines a template as adding rows to a table declared elsewhere.</span> * <code>#cargo_compound_query</code> - Zeigt die Ergebnisse mehrerer Abfragen an einer Stelle an. * <code>#cargo_display_map</code> - Zeigt eine Karte mit einem einzelnen Punkt an. * <code>#recurring_event</code> - druckt die Daten für eine wiederkehrende Veranstaltung aus; zur Verwendung durch #cargo_store. Cargo definiert auch verschiedene Schnittstellen, um diese gespeicherten Daten einzusehen und zu durchsuchen. <span class="mw-translate-fuzzy">Cargo wurde getestet und funktioniert mit den Datenbanksystemen MySQL, PostgreSQL und SQL Server.</span> <span class="mw-translate-fuzzy">Theoretisch unterstützt es auch SQLite und Oracle, aber es wurde mit diesen Systemen nicht getestet, es funktioniert da möglicherweise nicht perfekt.</span> Diese Version der Cargo-Erweiterung erfordert MediaWiki 1.32+. Klicken Sie sich durch die Seiten in der Navigationsleiste oben, um mehr über Cargo zu erfahren, wie es funktioniert, wie man es benutzt und wie man es installiert. == Siehe auch == * {{ll|Manual:Managing data in MediaWiki}} – Ein Überblick und Vergleich * {{ll|Extension:DynamicPageList|DynamicPageList}} – Erlaubt, Daten aus Seiten zu extrahieren * {{ll|Extension:Semantic MediaWiki|Semantic MediaWiki}} – Erlaubt Speichern und Abfragen von in Seiten enthaltenen Daten * {{ll|Extension:WikiDB|WikiDB}} – Stellt Datenbank-Features zur Verfügung, ähnelt semantischen Eigenschaften * {{ll|Extension:Wikibase|Wikibase}} – Ermöglicht die Darstellung und Manipulation strukturierter Daten als Teil des [[meta:Wikidata|Wikidata-Projektes]]. {{Used by|canasta=1|fandom=1|miraheze=1|mywikis=1}} [[Category:Data extraction extensions{{#translation:}}]] [[Category:Database extensions{{#translation:}}]] [[Category:Table extensions{{#translation:}}]] [[Category:Calendar extensions{{#translation:}}]] [[Category:Map extensions{{#translation:}}]] [[Category:Google Maps extensions{{#translation:}}]] [[Category:OpenLayers extensions{{#translation:}}]] [[Category:Leaflet extensions{{#translation:}}]] [[Category:Graphical Timelines{{#translation:}}]] [[Category:Graph extensions{{#translation:}}]] [[Category:Math extensions{{#translation:}}]] [[Category:Search extensions{{#translation:}}]] tj6f4v5yxlhg0cbq5tnjelk683pbn9r 5387032 5387030 2022-07-28T19:54:04Z ThisCarthing 17456337 wikitext text/x-wiki <languages/> {{Cargo navigation}} {{Extension |status = stable |type1 = special |type2 = api |type3 = parser function |newhook1 = CargoSetFormatClasses |newhook2 = CargoBeforeStoreData |newhook3 = CargoDisplayExportData |newhook4 = CargoTablesSetAllowedActions |newhook5 = CargoTablesSetActionLinks |username = Yaron Koren |author = [[User:Yaron Koren|Yaron Koren]] <yaron57@gmail.com> |description = Eine Erweiterung, die das Speichern und Abfragen von in enthaltenen Daten ermöglicht. |image = Cargo logo.png |imagesize = 120px |version = 3.2 |update = {{ym|2022|4}} |compatibility policy = master |mediawiki = 1.32+ |download = Siehe {{ll|Extension:Cargo/Download and installation}} |changelog = |example = [http://discoursedb.org/wiki/Main_Page Eine Seite mit verschiedenen Anrufen auf #cargo_query] |namespace = |tags = |bugzilla = Cargo |translate = ext-cargo |table1 = cargo_tables |table2 = cargo_pages }} '''Cargo''' ist eine Erweiterung von MediaWiki, die eine einfache Möglichkeit bietet, die in den Aufrufen von Vorlagen, wie z.B. Infoboxen, enthaltenen Daten zu speichern und abzufragen. Es ist vom Konzept her ähnlich wie die Erweiterung {{ll|Extension:Semantic MediaWiki|nsp=0}}, bietet aber eine Reihe von Vorteilen, einschließlich der einfachen Installation und Nutzung. Cargo speichert alle seine Daten in Datenbanktabellen, die entweder in der MediaWiki-eigenen Datenbank (Standard) oder in einer separaten Datenbank abgelegt werden können. In den meisten Fällen werden die Daten jeder gespeicherten Vorlage in einer einzigen DB-Tabelle gespeichert, mit einer Spalte für jeden relevanten Vorlagenparameter. Es gibt einige wenige Ausnahmen: Die Handhabung von Vorlagenfeldern, die Arrays/Wertelisten enthalten, und von Feldern, die geographische Koordinaten enthalten, ist aufgrund der schlechten nativen Handhabung dieser Datentypen in den meisten DB-Systemen komplexer. Und mehrere Vorlagen können so eingestellt werden, dass alle ihre Daten in einer DB-Tabelle speichern. Die Erweiterung definiert eine Reihe von Parser-Funktionen; diese drei sind die wichtigsten: * <code>#cargo_declare</code> - innerhalb des {{tag|noinclude|open}}-Teils einer Vorlage platziert; sie definiert das Schema für eine Tabelle. * <code>#cargo_store</code> - Speichert eine Zeile in einer Cargo-Tabelle. Normalerweise innerhalb des {{tag|includeonly|open}}-Teils einer Vorlage platziert. * <code>#cargo_query</code> - SQL ähnliche Abfrage über eine oder mehrere Cargo-Tabellen. Die anderen definierten Parser-Funktionen sind: * <code>#cargo_attach</code> - <span lang="en" dir="ltr" class="mw-content-ltr">defines a template as adding rows to a table declared elsewhere.</span> * <code>#cargo_compound_query</code> - Zeigt die Ergebnisse mehrerer Abfragen an einer Stelle an. * <code>#cargo_display_map</code> - Zeigt eine Karte mit einem einzelnen Punkt an. * <code>#recurring_event</code> - druckt die Daten für eine wiederkehrende Veranstaltung aus; zur Verwendung durch #cargo_store. Cargo definiert auch verschiedene Schnittstellen, um diese gespeicherten Daten einzusehen und zu durchsuchen. Cargo wurde getestet und funktioniert mit den Datenbanksystemen MySQL und PostgreSQL. <span class="mw-translate-fuzzy">Theoretisch unterstützt es auch SQLite und Oracle, aber es wurde mit diesen Systemen nicht getestet, es funktioniert da möglicherweise nicht perfekt.</span> Diese Version der Cargo-Erweiterung erfordert MediaWiki 1.32+. Klicken Sie sich durch die Seiten in der Navigationsleiste oben, um mehr über Cargo zu erfahren, wie es funktioniert, wie man es benutzt und wie man es installiert. == Siehe auch == * {{ll|Manual:Managing data in MediaWiki}} – Ein Überblick und Vergleich * {{ll|Extension:DynamicPageList|DynamicPageList}} – Erlaubt, Daten aus Seiten zu extrahieren * {{ll|Extension:Semantic MediaWiki|Semantic MediaWiki}} – Erlaubt Speichern und Abfragen von in Seiten enthaltenen Daten * {{ll|Extension:WikiDB|WikiDB}} – Stellt Datenbank-Features zur Verfügung, ähnelt semantischen Eigenschaften * {{ll|Extension:Wikibase|Wikibase}} – Ermöglicht die Darstellung und Manipulation strukturierter Daten als Teil des [[meta:Wikidata|Wikidata-Projektes]]. {{Used by|canasta=1|fandom=1|miraheze=1|mywikis=1}} [[Category:Data extraction extensions{{#translation:}}]] [[Category:Database extensions{{#translation:}}]] [[Category:Table extensions{{#translation:}}]] [[Category:Calendar extensions{{#translation:}}]] [[Category:Map extensions{{#translation:}}]] [[Category:Google Maps extensions{{#translation:}}]] [[Category:OpenLayers extensions{{#translation:}}]] [[Category:Leaflet extensions{{#translation:}}]] [[Category:Graphical Timelines{{#translation:}}]] [[Category:Graph extensions{{#translation:}}]] [[Category:Math extensions{{#translation:}}]] [[Category:Search extensions{{#translation:}}]] pmoofe1tol64flmg35eu17rfc0cuiy4 5387034 5387032 2022-07-28T19:55:31Z ThisCarthing 17456337 wikitext text/x-wiki <languages/> {{Cargo navigation}} {{Extension |status = stable |type1 = special |type2 = api |type3 = parser function |newhook1 = CargoSetFormatClasses |newhook2 = CargoBeforeStoreData |newhook3 = CargoDisplayExportData |newhook4 = CargoTablesSetAllowedActions |newhook5 = CargoTablesSetActionLinks |username = Yaron Koren |author = [[User:Yaron Koren|Yaron Koren]] <yaron57@gmail.com> |description = Eine Erweiterung, die das Speichern und Abfragen von in enthaltenen Daten ermöglicht. |image = Cargo logo.png |imagesize = 120px |version = 3.2 |update = {{ym|2022|4}} |compatibility policy = master |mediawiki = 1.32+ |download = Siehe {{ll|Extension:Cargo/Download and installation}} |changelog = |example = [http://discoursedb.org/wiki/Main_Page Eine Seite mit verschiedenen Anrufen auf #cargo_query] |namespace = |tags = |bugzilla = Cargo |translate = ext-cargo |table1 = cargo_tables |table2 = cargo_pages }} '''Cargo''' ist eine Erweiterung von MediaWiki, die eine einfache Möglichkeit bietet, die in den Aufrufen von Vorlagen, wie z.B. Infoboxen, enthaltenen Daten zu speichern und abzufragen. Es ist vom Konzept her ähnlich wie die Erweiterung {{ll|Extension:Semantic MediaWiki|nsp=0}}, bietet aber eine Reihe von Vorteilen, einschließlich der einfachen Installation und Nutzung. Cargo speichert alle seine Daten in Datenbanktabellen, die entweder in der MediaWiki-eigenen Datenbank (Standard) oder in einer separaten Datenbank abgelegt werden können. In den meisten Fällen werden die Daten jeder gespeicherten Vorlage in einer einzigen DB-Tabelle gespeichert, mit einer Spalte für jeden relevanten Vorlagenparameter. Es gibt einige wenige Ausnahmen: Die Handhabung von Vorlagenfeldern, die Arrays/Wertelisten enthalten, und von Feldern, die geographische Koordinaten enthalten, ist aufgrund der schlechten nativen Handhabung dieser Datentypen in den meisten DB-Systemen komplexer. Und mehrere Vorlagen können so eingestellt werden, dass alle ihre Daten in einer DB-Tabelle speichern. Die Erweiterung definiert eine Reihe von Parser-Funktionen; diese drei sind die wichtigsten: * <code>#cargo_declare</code> - innerhalb des {{tag|noinclude|open}}-Teils einer Vorlage platziert; sie definiert das Schema für eine Tabelle. * <code>#cargo_store</code> - Speichert eine Zeile in einer Cargo-Tabelle. Normalerweise innerhalb des {{tag|includeonly|open}}-Teils einer Vorlage platziert. * <code>#cargo_query</code> - SQL ähnliche Abfrage über eine oder mehrere Cargo-Tabellen. Die anderen definierten Parser-Funktionen sind: * <code>#cargo_attach</code> - <span lang="en" dir="ltr" class="mw-content-ltr">defines a template as adding rows to a table declared elsewhere.</span> * <code>#cargo_compound_query</code> - Zeigt die Ergebnisse mehrerer Abfragen an einer Stelle an. * <code>#cargo_display_map</code> - Zeigt eine Karte mit einem einzelnen Punkt an. * <code>#recurring_event</code> - druckt die Daten für eine wiederkehrende Veranstaltung aus; zur Verwendung durch #cargo_store. Cargo definiert auch verschiedene Schnittstellen, um diese gespeicherten Daten einzusehen und zu durchsuchen. Cargo wurde getestet und funktioniert mit den Datenbanksystemen MySQL und PostgreSQL. Theoretisch unterstützt es auch SQLite, aber es wurde mit SQLite nicht gut getestet und es funktioniert möglicherweise nicht. Diese Version der Cargo-Erweiterung erfordert MediaWiki 1.32+. Klicken Sie sich durch die Seiten in der Navigationsleiste oben, um mehr über Cargo zu erfahren, wie es funktioniert, wie man es benutzt und wie man es installiert. == Siehe auch == * {{ll|Manual:Managing data in MediaWiki}} – Ein Überblick und Vergleich * {{ll|Extension:DynamicPageList|DynamicPageList}} – Erlaubt, Daten aus Seiten zu extrahieren * {{ll|Extension:Semantic MediaWiki|Semantic MediaWiki}} – Erlaubt Speichern und Abfragen von in Seiten enthaltenen Daten * {{ll|Extension:WikiDB|WikiDB}} – Stellt Datenbank-Features zur Verfügung, ähnelt semantischen Eigenschaften * {{ll|Extension:Wikibase|Wikibase}} – Ermöglicht die Darstellung und Manipulation strukturierter Daten als Teil des [[meta:Wikidata|Wikidata-Projektes]]. {{Used by|canasta=1|fandom=1|miraheze=1|mywikis=1}} [[Category:Data extraction extensions{{#translation:}}]] [[Category:Database extensions{{#translation:}}]] [[Category:Table extensions{{#translation:}}]] [[Category:Calendar extensions{{#translation:}}]] [[Category:Map extensions{{#translation:}}]] [[Category:Google Maps extensions{{#translation:}}]] [[Category:OpenLayers extensions{{#translation:}}]] [[Category:Leaflet extensions{{#translation:}}]] [[Category:Graphical Timelines{{#translation:}}]] [[Category:Graph extensions{{#translation:}}]] [[Category:Math extensions{{#translation:}}]] [[Category:Search extensions{{#translation:}}]] q68fufhegodw3eq71c0v08dg9m3ijv6 Help:Transclusion/it 12 364670 5387767 5329734 2022-07-29T08:36:09Z GpieroMW 17587484 Created page with "=== Uso di base ===" wikitext text/x-wiki <languages /> {{PD Help Page}} '''Transclusion''' è un temine generico di MediaWiki che indica l'inclusione di un oggetto in una pagina utilizzando il simbolo delle doppie parentesi graffe "<nowiki>{{}}</nowiki>". Questi possono essere oggetti come [[Special:MyLanguage/Help:Templates|template]], pagine in altri namespace, [[Special:MyLanguage/Help:Magic words|parole magiche]], output per [[Special:MyLanguage/Help:Parser function|funzioni parser]], alcune [[Special:MyLanguage/Help:Special pages|Pagine speciali]], [[Special:MyLanguage/Manual:Interwiki|pagine interwiki]] e altri. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Target page syntax== </div> === Uso di base === <div lang="en" dir="ltr" class="mw-content-ltr"> To transclude a page, include both the namespace and the page name (separated with a colon) within the double-brace: </div> <pre><nowiki>{{Help:Transclusion}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> When transcluding a '''[[Special:MyLanguage/Help:Templates|template]]''', you may omit the namespace and colon: </div> <pre><nowiki>{{infobox}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> When transcluding an article in the '''Main namespace''', you may omit the namespace: </div> <pre><nowiki>{{:Transclusion}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> When transcluding a '''subpage''' of the target page, you may use the subpage name by itself: </div> <pre><nowiki>{{/doc}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Parameters=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Transcluded templates and {{ll|special pages}} may accept parameters: </div> <pre><nowiki>{{note|inline|This is a note.}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Source page syntax== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Three tags ({{tag|[[#%3Cnoinclude%3E|noinclude]]|o}}, {{tag|[[#%3Cincludeonly%3E|includeonly]]|o}}, and {{tag|[[#%3Conlyinclude%3E|onlyinclude]]|o}}) control which content appears in the target page. </div> <dl> <dt>{{anchor|&lt;noinclude&gt;|.3Cnoinclude.3E}} {{tag|noinclude|o}}</dt> <dd> <div lang="en" dir="ltr" class="mw-content-ltr"> Content within the {{tag|noinclude}} tags is excluded from transclusion on the target page. This content still appears on the source page. </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Source page wikitext</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the source page</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the target page</span> |- | <syntaxhighlight inline lang="html">Hello <noinclude>world</noinclude></syntaxhighlight> | Hello world | Hello |} </dd> <dt>{{anchor|&lt;includeonly&gt;|.3Cincludeonly.3E}} {{tag|includeonly|o}}</dt> <dd> <div lang="en" dir="ltr" class="mw-content-ltr"> Content within the {{tag|includeonly}} tags is transcluded on the target page, but does not appear on the source page. </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Source page wikitext</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the source page</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the target page</span> |- | <syntaxhighlight lang=html inline>Hello <includeonly>world</includeonly></syntaxhighlight> | Hello | Hello world |} </dd> <dt>{{anchor|&lt;onlyinclude&gt;|.3Conlyinclude.3E}} {{tag|onlyinclude|o}}</dt> <dd> <div lang="en" dir="ltr" class="mw-content-ltr"> Content within the {{tag|onlyinclude}} tags is transcluded on the target page, and also appears on the source page. </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Source page wikitext</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the source page</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the target page</span> |- | <syntaxhighlight lang=html inline>Hello <onlyinclude>world</onlyinclude></syntaxhighlight> | Hello world | world |} </dd> </dl> <div lang="en" dir="ltr" class="mw-content-ltr"> ==See also== </div> * {{ll|Transclusion}} - <span lang="en" dir="ltr" class="mw-content-ltr">A more in-depth explanation</span> [[Category:Help{{#translation:}}|{{PAGENAME}}]] nv0u3ytyc3pi5pp5gkl55v940fhjr4u 5387769 5387767 2022-07-29T08:36:54Z GpieroMW 17587484 Created page with "==Sintassi della pagina di destinazione==" wikitext text/x-wiki <languages /> {{PD Help Page}} '''Transclusion''' è un temine generico di MediaWiki che indica l'inclusione di un oggetto in una pagina utilizzando il simbolo delle doppie parentesi graffe "<nowiki>{{}}</nowiki>". Questi possono essere oggetti come [[Special:MyLanguage/Help:Templates|template]], pagine in altri namespace, [[Special:MyLanguage/Help:Magic words|parole magiche]], output per [[Special:MyLanguage/Help:Parser function|funzioni parser]], alcune [[Special:MyLanguage/Help:Special pages|Pagine speciali]], [[Special:MyLanguage/Manual:Interwiki|pagine interwiki]] e altri. ==Sintassi della pagina di destinazione== === Uso di base === <div lang="en" dir="ltr" class="mw-content-ltr"> To transclude a page, include both the namespace and the page name (separated with a colon) within the double-brace: </div> <pre><nowiki>{{Help:Transclusion}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> When transcluding a '''[[Special:MyLanguage/Help:Templates|template]]''', you may omit the namespace and colon: </div> <pre><nowiki>{{infobox}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> When transcluding an article in the '''Main namespace''', you may omit the namespace: </div> <pre><nowiki>{{:Transclusion}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> When transcluding a '''subpage''' of the target page, you may use the subpage name by itself: </div> <pre><nowiki>{{/doc}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Parameters=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Transcluded templates and {{ll|special pages}} may accept parameters: </div> <pre><nowiki>{{note|inline|This is a note.}}</nowiki></pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Source page syntax== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Three tags ({{tag|[[#%3Cnoinclude%3E|noinclude]]|o}}, {{tag|[[#%3Cincludeonly%3E|includeonly]]|o}}, and {{tag|[[#%3Conlyinclude%3E|onlyinclude]]|o}}) control which content appears in the target page. </div> <dl> <dt>{{anchor|&lt;noinclude&gt;|.3Cnoinclude.3E}} {{tag|noinclude|o}}</dt> <dd> <div lang="en" dir="ltr" class="mw-content-ltr"> Content within the {{tag|noinclude}} tags is excluded from transclusion on the target page. This content still appears on the source page. </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Source page wikitext</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the source page</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the target page</span> |- | <syntaxhighlight inline lang="html">Hello <noinclude>world</noinclude></syntaxhighlight> | Hello world | Hello |} </dd> <dt>{{anchor|&lt;includeonly&gt;|.3Cincludeonly.3E}} {{tag|includeonly|o}}</dt> <dd> <div lang="en" dir="ltr" class="mw-content-ltr"> Content within the {{tag|includeonly}} tags is transcluded on the target page, but does not appear on the source page. </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Source page wikitext</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the source page</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the target page</span> |- | <syntaxhighlight lang=html inline>Hello <includeonly>world</includeonly></syntaxhighlight> | Hello | Hello world |} </dd> <dt>{{anchor|&lt;onlyinclude&gt;|.3Conlyinclude.3E}} {{tag|onlyinclude|o}}</dt> <dd> <div lang="en" dir="ltr" class="mw-content-ltr"> Content within the {{tag|onlyinclude}} tags is transcluded on the target page, and also appears on the source page. </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Source page wikitext</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the source page</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">What appears on the target page</span> |- | <syntaxhighlight lang=html inline>Hello <onlyinclude>world</onlyinclude></syntaxhighlight> | Hello world | world |} </dd> </dl> <div lang="en" dir="ltr" class="mw-content-ltr"> ==See also== </div> * {{ll|Transclusion}} - <span lang="en" dir="ltr" class="mw-content-ltr">A more in-depth explanation</span> [[Category:Help{{#translation:}}|{{PAGENAME}}]] snzdkupndek93ewwbyw93sas6h3byti Template:InstallationNav/ar 10 427590 5387185 5384772 2022-07-28T21:17:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=تخصيص}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] jj27ttrjuozaxwkpfwqpv94jqw0elp8 Universal Language Selector/FAQ/de 0 429731 5386731 4665444 2022-07-28T18:50:14Z ThisCarthing 17456337 wikitext text/x-wiki <languages /> == Was ist der Universal Language Selector? == Der Universal Language Selector ist eine Erweiterung von MediaWiki, die es Nutzern erlaubt, Spracheinstellungen und Konfigurationen nach ihren Vorlieben zu verändern. Er verwendet die ''jQuery'' Bibliotheken des Projektes ''Milkshake''. == Welche Spracheinstellungen kann ich mithilfe von ULS anpassen? == Der Universal Language Selector bietet die folgenden Funktionen in Wikimedia Wikis: # Auswahl der Anzeigesprache für angemeldete Benutzer. # WebFonts (Schriftarten) # Eingabemethoden {{anchor|language-territory|How_does_Universal_Language_Selector_determine_which_languages_I_may_understand}} == Wie ermittelt der Universal Language Selector, welche Sprachen ich vermutlich verstehe? == ULS befragt einen Dienstleister, der dein Herkunftland anhand deiner IP-Adresse bestimmt. Diese Information ist nicht immer korrekt. Ausgehend von deiner Länderkennzahl werden dir die dort am häufigsten gesprochenen Sprachen vorgeschlagen. Die "gebräuchlichen Sprachen" innerhalb eines Landes sind ebenfalls schwer zu ergründen. Deshalb stammen diese Informationen aus den [[Milkshake]]-Bibliotheken. Wir zielen darauf, diese mit anderen interessierten Software Projekten über Wikimedia hinaus gemeinsam zu pflegen. Hauptsächlich kommen die Daten jedoch von Unicode (mehr dazu [[translatewiki:CLDR|hier]]) und können in deren [http://www.unicode.org/cldr/charts/latest/supplemental/territory_language_information.html Territory-Language Information|Informationstabelle] eingesehen werden. Wenn du Verbesserungsvorschläge hast, was die dir vom ULS vorgeschlagene Sprachauswahl betrifft, sieh erst nach, ob die Unicode-Infotabelle auf dem besten Stand ist. Falls es dort ebenfalls Verbesserungsbedarf gibt, klicke in der Zeile deines Landes/deiner Sprache auf "add new" und schlage Änderungen vor. Die Unicode-Mitarbeiter sind sehr hilfsbereit und es ist keine Registrierung erforderlich. Bedenke die [http://cldr.unicode.org/index/cldr-spec/definitions CLDR Definitionen] und denke daran, verlässliche Quellen für die vorgeschlagenen Daten anzuführen, wie zum Beispiel ein Amt für Statistik oder eine wissenschaftliche Studie (für Daten zur Lese-/Schreibfähigkeit) oder nationale/lokale Gesetze (um nachzuweisen, dass eine Sprache auch als Amtssprache geläufig ist). {{notice|1=<span lang="en" dir="ltr" class="mw-content-ltr">We're currently taking care of the [http://unicode.org/cldr/trac/ticket/9680 top 3 languages of each country of Europe] but you can also do a more detailed work for a single country, see for instance:</span> {{bug|T64346}}, {{bug|T141650}}, [[phabricator:T142070#2552959|bug T142070]]}} == Wo ist der Universal Language Selector verfügbar? == Momentan ist geplant, den Universal Language Selector so bald wie möglich auf allen Wikimedia Wikis zugänglich zu machen. Details können [[UniversalLanguageSelector/Deployment/Planning|hier]] eingesehen werden. {{anchor|How can I use Universal Language Selector}} == Wie kann ich den Universal Language Selector verwenden? == In Projekten mit mehreren Sprachausgaben (Wikipedia, Wikibooks, Wikiversity, Wiktionary, Wikiquote, Wikivoyage, Wikinews, Wikisource) ist der Universal Language Selector als Zahnradsymbol im Menübereich für Sprachenlinks zu finden. In Wikimedia Projekten ohne Mehrsprachigkeit (z. B. Wikimedia Commons, Meta-Wiki, Wikispecies und dieses Wiki mediawiki.org), befindet sich der ULS als Symbol in der persönlichen Werkzeugleiste oben auf jeder Seite. Klicke auf das Symbol, führe Veränderungen durch und bestätige sie um sie dauerhaft beizubehalten. Ein kleines Tastatur-Symbol wird überall dort erscheinen, wo Texteingaben möglich sind. Wähle es aus um die Einstellungen zu verändern. Lies dir "[[Universal_Language_Selector/Testing#Location_for_the_Selector|Location for the Selector]]"durch um mehr über die Ortsauswahl zu erfahren. == Wie kann ich die Anzeigesprache verändern? == [[File:Using Wikipedia across multiple languages.webm|thumb|Dieses englischsprachige Video zeigt den Ort des Bedienfeldes.]] Die Anzeigesprache der MediaWiki-Interfacemeldungen kann mithilfe des Bedienfeldes für Spracheinstellungen im ULS verändert werden. Auf Wikimediaprojekten steht diese Funktion ausschließlich angemeldeten Nutzern zur Verfügung. Nach der Anmeldung kannst du das Bedienfeld zur Spracheinstellung öffnen (in der Seitenleiste oder oben) und zum Sprachenreiter der Anzeigeeinstellungen navigieren. Für eine schnelle Auswahl wird der ULS eine Liste möglicher Sprachen anzeigen, die auf deinem Standort (IP) basiert. Zur Auswahl klickst du auf die Sprache deiner Wahl. Wenn die Sprache, nach der du suchst, nicht im Bedienfeld verfügbar ist, klicke auf den '...'-Button, um die längere Sprachenliste zu öffnen und wähle die gesuchte Sprache aus. Ein kleines Pop-Up (die technisch Bezeichnung ist "undo popover" oder "tipsy") wird erscheinen, wenn das ULS die Sprache im Vergleich zu Deinen bisherigen Einstellungen ändert, damit Du es schnell wieder ändern kannst. In manchen Fällen wird stattdessen ein Tooltip angezeigt. == Muss ich angemeldet sein, um die Anzeigesprache zu ändern? == Ja. Die Anzeigesprache kann nur von angemeldeten Nutzern verändert werden. == Wenn ich die Anzeigesprache ändere, verändert das auch die Sprache des Inhalts auf der Seite, die ich mir gerade ansehe? == Nein. Der ULS verändert nicht die Sprache des jeweiligen Seiteninhalts. Er kann verwendet werden, um nur die [[interface language|Sprache der Schnittstelle (Interface)]] von MediaWiki zu verändern (die in diesem FAQ manchmal "Anzeigesprache" genannt wird). In Fällen, in denen die Erweiterung {{ll|Extension:Translate|nsp=0}} installiert wurde, kann diese dahingehend konfiguriert werden, den Benutzer zu bestehenden Übersetzungen der Seite zu schicken, wenn das ULS die Sprache der Schnittstelle verändert hat. == Ich sehe Kästchen im Text wenn ich meine Sprache auswähle == Wir nennen diese Boxen "Tofu". Sie tauchen auf, wenn in der gewählten Sprache kein Zeichensatz zur Verfügung steht. Du kannst einen lokalen Zeichensatz of deinem Rechner installieren um das Problem zu beheben. Um ein ähnliches Problem in Zukunft zu verhindern, würden wir aber gerne sicherstellen, dass sich in unserer Schriftarten-Bibliothek Zeichensätze für deine Sprache befinden. Bitte informiere uns daher, vorzugsweise über https://phabricator.wikimedia.org. == Kann ich den Zeichensatz der Sprache verändern? == Schriftarten einer Sprache können vom Nutzer über den "Schriftarten"-Reiter innerhalb der Anzeigeeinstellungen verändert werden. Anonyme Nutzer können den Zeichensatz nur für die aktive Sprache verändern. Angemeldete Nutzer können die Zeichensätze aller Sprachen verändern. == Wie verläuft die Entscheidung für einen voreingestellten Zeichensatz einer Sprache oder eines Skripts? == Ein voreingestellter Zeichensatz wird eingerichtet, wenn eine Sprache oder ein Skript eine problematische Support-Geschichte auf einer großen Bandbreite von Desktop-Computern und anderen Geräten aufweist. Obwohl die meisten modernen Betriebssysteme Möglichkeiten bereithalten, Sprachen oder Skripte gut zu unterstützen, erfordert dies möglicherweise ein vorheriges Handeln des Nutzers. So wird beispielsweise die Installation einer Software oder eine Änderung der Betriebssystemeinstellungen erfordert. Unsere Erfahrung zeigt, dass viele Nutzer dies nicht tun und aufgeben, daher wollen wir einen schnellen und automatischen Weg zur Lesbarkeit der Texte möglich machen. Der Universal Language Selector stellt nur frei lizensierte Zeichensätze zur Verfügung. Wir wählen voreingestellte Schriftarten einerseits aufgrund der Popularität des Zeichensatzes aus (z.B. ein voreingestellter Zeichensatz für ein Skript in Linux-Vertrieben, welche in Portalen der entsprechenden Sprache häufig verwendet werden u.s.w.) und andererseits aufgrund der Eingaben unserer potentiellen Nutzer. Wenn der voreingestellte Zeichensatz Fehler aufweist, die Nutzer am Gebrauch hindern, werden wir versuchen, einen anderen Zeichensatz zu verwenden (falls verfügbar). Hierfür wird in Phabricator ein gültiger Problembericht benötigt. {{anchor|What if the default font chosen is not the best one for the language? Can this be changed?}} == Was passiert, wenn die gewählte Voreinstellung nicht der beste Zeichensatz für die jeweilige Sprache ist? Kann das geändert werden? == Mit dem Universal Language Selector durchgeführte Aktionen beinhalten jetzt das sog. "[[Special:MyLanguage/Extension:EventLogging|Event Logging]]", siehe auch "[[Extension:UniversalLanguageSelector/EventLogging queries|Statistiken und Daten]]". Dies erlaubt den Entwicklern eine Analyse des Nutzerverhaltens und der vorgenommenen Einstellungsveränderungen. Basierend auf dem Nutzerverhalten und anderen Messungen können dann Änderungen durchgeführt werden. Das bedeutet, dass das Eingabewerkzeug und die Zeichensatzunterstützung in WMF-Werkzeugen im EventLogging-System integriert sein müssen. Jede Veränderung der voreingestellten Eingabemethode oder an Zeichensätzen muss von den [[Extension:UniversalLanguageSelector/EventLogging queries|Nutzerstatistiken]] unterstützt werden. Am Beispiel von Zeichensatz A und Zeichensatz B für eine Sprache S: Wenn Satz B häufiger genutzt wird als Satz A, sollte Zeichensatz B zur Standardeinstellung für diese Sprache gemacht werden. Wenn der Systemsatz bei einer Sprache meist präferiert wird, sollte in der Voreinstellung der Internet-Zeichensatz deaktiviert werden. Nach dem gleichen Prinzip funktioniert auch die Einstellung der Eingabemethoden. == Kann ich die von ULS für meine Sprache gewählte Voreinstellung (Zeichensatz) deaktivieren? == Die Voreinstellung kann [[#How can I use Universal Language Selector|in den Einstellungen]] deaktiviert werden. Wenn die Sprache von A-Nutzern und -Betriebssystemen gut unterstützt wird, können die vom System bereitgestellten Einstellungen bzgl. Zeichensatz und Eingabemethoden zur Standardeinstellung werden. Gute Unterstützung bedeutet, dass Browser und Betriebssysteme für die entsprechende Sprache einen fehlerfreien Zeichensatz und eine makellose Eingabemethode als Standardeinstellung zur Verfügung stellen (gebündelt mit OS, ohne spezielle Installationsschritte zu erfordern). == Es scheint keinen Zeichensatz für meine Sprache zu geben. Wie kann ich einen neuen Zeichensatz für ULS anfragen? == Du kannst eine Fehlermeldung auf [https://phabricator.wikimedia.org Phabricator] einreichen, in der du um das Hinzufügen eines Zeichensatzes für deine Sprache bittest. Es wird erwartet, dass du darüber hinaus Vorschläge über mögliche Zeichensätze machst und uns mitteilst, wo sie zu finden sind. Wir empfehlen außerdem, von anderen Mitgliedern deiner Sprachgemeinschaft einen Konsens über die Einbeziehung eines neuen Zeichensatzes einzuholen. == Welche Informationen werden benötigt um einen neuen Zeichensatz in den ULS zu integrieren? == # Den Namen des Zeichensatzes # Die URL der Quelle/des Fundortes # Eine Lizenz für den Zeichensatz, die eine freie Nutzung, Distribution und Veränderung gestattet. Diese Informationen können in Phabricator angeführt werden, wenn um die Aufnahme eines Zeichensatzes gebeten wird. == Ich würde gerne in einer anderen Sprache schreiben. Wie kann ich die Einstellungen dahingehend verändern? == # In der Seitenleiste: Du kannst im Bereich "Eingabeeinstellungen" im Bedienfeld der Spracheinstellungen eine der Sprachen auswählen, die auf den Buttons oder im "Sprachauswahl"-Popup gezeigt werden. # Im Tastatur-Menü: Die Sprachen sind in einer Liste aufgeführt, aus der ausgewählt werden kann. == Ich habe eine Sprache gewählt, kann aber immer noch nicht in dieser Sprache schreiben. Warum? == Wenn du eine Sprache auswählst, wird dir eine Liste mit Eingabemethoden gezeigt. Wenn im ULS für diese Sprache keine Eingabemethoden existieren, wird die lokale Tastatur deines Computers zur Eingabe verwendet. Wenn in keiner der beiden Optionen Eingabemethoden verfügbar sind, ist es nicht möglich, in der gewählten Sprache zu schreiben. == Ich würde gerne die Tastatur für die gewählte Sprache verändern. Wie geht das? == Die Eingabemethoden-/Tastatur-Optionen für eine Sprache im ULS werden sowohl im Bedienfeld der Spracheinstellungen als auch im Tastaturmenü eines Texteingabefeldes als Liste dargestellt. Für jede Sprache ist eine Tastatur voreingestellt. Um eine andere Tastatur zu verwenden, kannst du aus dieser Liste auswählen. == Ich habe eine Tastatur an meinem Computer und möchte nicht die Tastatur des ULS verwenden. Kann ich die ULS-Tastatur vollständig abschalten? == Die ULS-Eingabemethoden können auf zwei Arten deaktiviert werden: # In der Seitenleiste: Klicke auf den "{{int|jquery-ime-disable-text}}"-Button in der "Eingabemethoden"-Option der Spracheinstellungen # Im Tastaturmenü: Klicke auf den "{{int|jquery-ime-disable-text}}"-Button im Tastaturmenü, dass durch klicken auf das Tastatur-Symbol eines Texteingabefeldes (z.B. das Suchfeld) erscheint == Kann ich die ULS-Tastatur für eine einzelne Sprache abschalten, ohne sie vollständig zu deaktivieren? == Ja. Dafür wähle bitte "Native Tastatur verwenden" im Drop-Down-Menü, das in der Liste der verfügbaren Tastaturen in dieser Sprache aufgeführt wird. == Wie wird die Reihenfolge der Eingabemethoden entschieden? == [[File:Key theme - Global South, WMF Metrics Meeting February 2015.pdf|page=18|thumb|Beispielhafter Graph zur Darstellung der Eingabemethoden]] Dies wird für jede Sprache einzeln ausgewertet. Vorzugsweise ist es zuerst einmal die nützlichste und am häufigsten gebrauchte für die jeweilige Sprache, gemäß der Rücksprache mit potentiellen Nutzern. Wenn die Standard-Eingabemethode durch einen Fehler nicht nutzbar sein sollte, wird sie als präferierte oder voreingestellte Eingabemethode deaktiviert. Hierfür wird in Phabricator ein gültiger, aussagekräftiger Fehlerbericht erfordert. Bis der Fehler behoben ist, rückt die nächste verfügbare Eingabemethode an die Spitze der Liste. == Was passiert, wenn die Standard-Eingabemethode nicht die bestmögliche in der Sprache ist? Kann dies verändert werden? == Jede Änderung in den Standardeinstellungen für Eingabemethoden oder Zeichensätze muss durch die [[Extension:UniversalLanguageSelector/EventLogging queries|Nutzungsstatistik]] unterstützt werden. [[#What if the default font chosen is not the best one for the language? Can this be changed?|Hierzu wurde weiter oben schon eine ähnliche Frage gestellt.]] == Kann ich alle Veränderungen in den Spracheinstellungen von meiner Nutzerseite aus vornehmen? == Ja. Um die Spracheinstellungen zu konfigurieren, gehe zu deiner Nutzerseite und klicke unter dem "{{int|prefs-personal}}"-Reiter im "{{int|prefs-i18n}}"-Abschnitt auf "{{int|ext-uls-language-settings-preferences-link}}". {{anchor|Why can anonymous users not use Universal Language Selector to change their interface language}} == Warum können anonyme Nutzer den ULS nicht zum verändern ihrer Schnittstellensprache verwenden? == Diese Option ist auf Wikimedia Wikis deaktiviert, weil die Struktur des Wikimedia Cache dies momentan nicht unterstützt. In Zukunft wollen wir es allerdings möglich machen. Es gibt noch keine Zeitschiene hierfür. <span lang="en" dir="ltr" class="mw-content-ltr">See [[:phab:T134592|Allow setting the UI to a language other than English for anonymous users]] in Phabricator.</span> == Wie kann ich den Universal Language Selector deaktivieren? == Nur Teile des Funktionsangebotes können deaktiviert werden. Eingabemethoden können vollständig ausgeschaltet werden, indem auf das Tastatur-Symbol geklickt und "Eingabewerkzeuge deaktivieren" gewählt wird. Eingabemethoden können pro Eingabeelement ausgeschaltet werden, indem dort <code>class="noime"</code> angefügt wird. Web-Zeichensätze können nur über die Sprache [[#How can I use Universal Language Selector|in den Einstellungen]] deaktiviert werden. == Kann ich die Schnittstelle des Universal Language Selector in meine Sprache übersetzen? == Ja! Du kannst dies auf [[translatewiki:|translatewiki.net]] tun. Vervollständige die Übersetzung der folgenden zwei Meldungsgruppen, sobald du als Übersetzer registriert bist: * [[translatewiki:Special:Translate/ext-universallanguageselector|MediaWiki-Erweiterung]] * <s>[[translatewiki:Special:Translate/ext-jquery-uls|jQuery Plugin]]</s> Existiert nicht mehr. == Wo kann ich ein Problem melden? == Bitte [[Special:MyLanguage/How to report a bug|melde Probleme und Vorschläge in Phabricator]]. Bitte stelle sicher, dass dein Bericht so detailliert wie möglich ist. == What fonts are included? == <span lang="en" dir="ltr" class="mw-content-ltr">An up-to-date list is in the {{git file|action=tree|project=mediawiki/extensions/UniversalLanguageSelector|branch=HEAD|file=data/fontrepo/fonts|text=fonts directory}} of Wikimedia’s Git repository (each folder has metadata in the file font.ini). Here is the list, as of 2013-11-22 (v1.4.0-Snapshot):</span> <!-- this should be expanded with information about font version, language & Unicode block support in each. --> {| style="border-collapse:collapse; border-bottom:3px double #ccc; " |- style="border-bottom:1px solid #ccc; text-align:left; " ! <span lang="en" dir="ltr" class="mw-content-ltr">Font</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">CSS font-family name</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">For languages (* denotes default font)</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Additional support</span> |- style="border-bottom:1px solid #ccc; " | AbyssinicaSIL 1.200[http://scripts.sil.org/AbyssinicaSIL] | AbyssinicaSIL | Amharic (am*), Tigrinya (ti*), Ge‘ez (gez*), Tigre (tig*) | Ethiopic/Ge‘ez script (Ethi) |- style="border-bottom:1px solid #ccc; " | Akkadian 2.56[http://users.teilar.gr/~g1951d/] | Akkadian | Akkadian (akk*), Sumerian (sux*) | |- style="border-bottom:1px solid #ccc; " | Alef 1.0[http://alef.hagilda.com/] | Alef, 'Alef Bold' | Hebrew (he), Yiddish (yi), Old Hebrew (hbo) | |- style="border-bottom:1px solid #ccc; " | amiri 1.0.2[http://amirifont.org] | Amiri, 'Amiri Bold', 'Amiri Italic', 'Amiri Bold Italic' | Arabic (ar), Standard Arabic (arb), Persian (fa) | |- style="border-bottom:1px solid #ccc; " | AnjaliOldLipi .0.730[https://sites.google.com/site/cibu/anjalioldlipi-font] | AnjaliOldLipi | Malayalam (ml) | Malayalam script (Mlym) |- style="border-bottom:1px solid #ccc; " | Autonym v 20131118[https://github.com/santhoshtr/AutonymFont/] | Autonym | multiple languages (mul) | |- style="border-bottom:1px solid #ccc; " | CharisSIL 4.011[http://scripts.sil.org/CharisSIL] | CharisSIL | Min Dong (cdo), Min Nan (nan) | Latin script (Latn) |- style="border-bottom:1px solid #ccc; " | DoulosSIL 4.112[http://scripts.sil.org/DoulosSIL] | 'Doulos Sil' | Min Nan (nan) | |- style="border-bottom:1px solid #ccc; " | EastSyriacAdiabene 1.21[http://www.bethmardutho.org/index.php/resources/fonts.html] | 'East Syriac Adiabene' | Syriac (syc), Imperial Aramaic (arc) | |- style="border-bottom:1px solid #ccc; " | EstrangeloEdessa 1.21[http://www.bethmardutho.org/index.php/resources/fonts.html] | 'Estrangelo Edessa' | Syriac (syc*), Imperial Aramaic (arc*) | |- style="border-bottom:1px solid #ccc; " | FreeFontThana 1.0[http://www.gnu.org/software/freefont] | FreeFont-Thaana, 'FreeFont-Thaana Bold] | Maldivian (dv*) | |- style="border-bottom:1px solid #ccc; " | GentiumPlus 1.510[http://scripts.sil.org/gentium] | GentiumPlus, 'GentiumPlus Italic' | Greek (grc) | Greek script (Grek), Latin (Latn), Cyrillic (Cyrl), IPA (und-fonipa) |- style="border-bottom:1px solid #ccc; " | Gubbi 1.3[https://github.com/aravindavk/Gubbi/] | Gubbi | Kannada (kn), Tulu (tcy) | |- style="border-bottom:1px solid #ccc; " | Hanuman 1.0[http://www.google.com/fonts/specimen/Hanuman] | Hanuman, 'Hanuman Bold' | Khmer (km) | |- style="border-bottom:1px solid #ccc; " | IranianSans 1.0[http://fedoraproject.org/wiki/Iranian_fonts] | 'Iranian Sans' | Persian (fa) | Arabic script (Arab) |- style="border-bottom:1px solid #ccc; " | Jomolhari 0.003[https://sites.google.com/site/chrisfynn2/home/fonts/jomolhari] | Jomolhari | Tibetan (bo*, bod*), Dzongkha (dz*), Sino-Tibetan (adx*), Dolpo (dre*), goe*, Humla (hut*), Nubri (kte*), Khams Tibetan (khg*), Khamba (kbg*), Lhomi (lhm*), Ladakhi (lbj*), Lowa (loy*), Lunanakha (luk*), Layakha (lya*), Mukha-Dora (muk*), Walungge (ola*), Old Tibetan (otb*), Tichurong (tcn*), Thudam (thw*), Tseku (tsk*), Classical Tibetan (xct*), Zangskari (zau*) | |- style="border-bottom:1px solid #ccc; " | Junicode 2013-01-17[http://junicode.sourceforge.net/] | Junicode, 'Junicode Italic', 'Junicode Bold', 'Junicode Bold Italic' | Old English (ang) | |- style="border-bottom:1px solid #ccc; " | KhmerOS 1.10[http://www.khmeros.info/drupal612/en/fonts] | KhmerOS | Khmer (km) | |- style="border-bottom:1px solid #ccc; " | KhmerOSbattambang 1.10[http://www.khmeros.info/drupal612/en/fonts] | KhmerOSbattambang | Khmer (km*) | Khmer script (Khmr) |- style="border-bottom:1px solid #ccc; " | LinuxLibertine 5.3.0[http://linuxlibertine.org] | 'Linux Libertine', 'Linux Libertine Bold', 'Linux Libertine Italic', 'Linux Libertine Bold Italic' | – | |- style="border-bottom:1px solid #ccc; " | lklug 0.6[http://www.lug.lk/fonts/lklug] | lklug | Sinhalese (si) | |- style="border-bottom:1px solid #ccc; " | LohitAssamese 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Assamese' | Assamese (as) | Bengali (bn), Bishnupriya Manipuri (bpy) in Assamese script |- style="border-bottom:1px solid #ccc; " | LohitBengali (default) 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Bengali' | Bengali (bn), Bishnupriya Manipuri (bpy) | Assamese (as) in Bengali script (Beng) |- style="border-bottom:1px solid #ccc; " | LohitDevanagari 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Devanagari' | Bhojpuri (bh*, bho*), Hindi (hi*), Konkani (kok*), Goan Konkani (gom*), Maithili (mai*), Sanskrit (sa*) | Marathi (mr), Ahirani (ahr) in Devanagari script (Deva) |- style="border-bottom:1px solid #ccc; " | LohitGujarati 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Gujarati' | Gujarati (gu*) | Gujarati script (Gujr) |- style="border-bottom:1px solid #ccc; " | LohitKannada 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Kannada' | Kannada (kn*), Tulu (tcy*) | Kannada script (Knda) |- style="border-bottom:1px solid #ccc; " | LohitMarathi 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Marathi' | Ahirani (ahr*), Marathi (mr*) | |- style="border-bottom:1px solid #ccc; " | LohitNepali 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Nepali' | Nepali (ne*) | |- style="border-bottom:1px solid #ccc; " | LohitOriya 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Oriya' | Oriya (or*) | Oriya script (Orya) |- style="border-bottom:1px solid #ccc; " | LohitPunjabi 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Punjabi' | Punjabi (pa*) | Gurmukhi script (Guru) |- style="border-bottom:1px solid #ccc; " | LohitTamil 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Tamil' | Tamil (ta) | Tamil script (Taml) |- style="border-bottom:1px solid #ccc; " | LohitTamilClassical 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Tamil Classical' | Tamil (ta) | Tamil script (Taml) |- style="border-bottom:1px solid #ccc; " | LohitTelugu 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Telugu' | Telugu (te*) | Telugu script (Telu) |- style="border-bottom:1px solid #ccc; " | madan 2[http://www.mpp.org.np] | Madan | Nepali (ne) | Hindi (hi), Marathi (mr), Maithili (mai), Bhojpuri (bh, bho), Goan Konkani (gom), Ahirani (ahr) in Devanagari script (Deva) |- style="border-bottom:1px solid #ccc; " | Meera 6.0[https://savannah.nongnu.org/projects/smc] | Meera | Malayalam (ml) | Malayalam script (Mlym) |- style="border-bottom:1px solid #ccc; " | MiriamCLM 0.130[http://culmus.sourceforge.net/] | 'Miriam CLM' | Hebrew (he) | Hebrew script (Hebr) |- style="border-bottom:1px solid #ccc; " | Myanmar3 3.0[http://code.google.com/p/myanmar3source/] | Myanmar3 | Burmese (my) | Myanmar (Burmese) script (Mymr) |- style="border-bottom:1px solid #ccc; " | NafeesWeb 1.2[http://www.crulp.org/nafeesWebNaskh.html] | NafeesWeb | Urdu (ur) | |- style="border-bottom:1px solid #ccc; " | Nazli 0.4[http://persian-computing.org/] | Nazli | Persian (fa) | |- style="border-bottom:1px solid #ccc; " | Nokora 1.10[http://www.google.com/fonts/specimen/Nokora] | 'Nokora Regular', 'Nokora Bold' | Khmer (km) | |- style="border-bottom:1px solid #ccc; " | NuosuSIL 2.1.1[http://scripts.sil.org/SILYI_home] | 'Nuosu SIL' | Sichuan Yi (ii*) | |- style="border-bottom:1px solid #ccc; " | OpenDyslexic 2.1.0+git060dc841[https://github.com/antijingoist/open-dyslexic] | OpenDyslexic, 'OpenDyslexic Bold', 'OpenDyslexic Italic', 'OpenDyslexic BoldItalic' | Afrikaans (af), [unknown] (bk), Catalan (ca), Welsh (cy), Danish (da), German (de), English (en), Spanish (es), Estonian (et), Finnish (fi), Faroese (fo), French (fr), West Frisian (fy), Irish (ga), Scottish Gaelic (gd), Galician (gl), Hungarian (hu), Indonesian (id), Icelandic (is), Italian (it), Luxembourgish (lb), Limburgish (li), Māori (mi), Malay (ms), Norwegian Bokmål (nb), Dutch (nl), Occitan (oc), Polish (pl), Portuguese (pt), Albanian (sq), Swedish (sv), Swahili (sw), Tagalog (tl), Turkish (tr), Walloon (wa) | |- style="border-bottom:1px solid #ccc; " | OskiEast 2.200[http://www.languagegeek.com/font/fontdownload.html#AlgonAndInu] | OskiEast, 'OskiEast Bold', 'OskiEast Italic', 'OskiEast Bold Italic' | Cree (cr*), Inuktitut (iu) | |- style="border-bottom:1px solid #ccc; " | Padauk 2.8[http://scripts.sil.org/Padauk] | Padauk | Burmese (my) | Myanmar (Burmese) script (Mymr) |- style="border-bottom:1px solid #ccc; " | Pagul 1.0[http://sourceforge.net/projects/pagul/] | Pagul | Saurashtra (saz*) | Saurashtra script (Saur) |- style="border-bottom:1px solid #ccc; " | Pangururan 1.0.5[http://evertype.com/fonts/batak/] | Pangururan | Batak Toba (bbc), Batak btk | |- style="border-bottom:1px solid #ccc; " | Phetsarath 1.01[http://phetsarath.gov.la] | Phetsarath, Phetsarath-Bold | Lao (lo*) | |- style="border-bottom:1px solid #ccc; " | Saab 0.91[http://guca.sourceforge.net/typography/fonts/saab/] | Saab | Punjabi (pa) | Gurmukhi script (Guru) |- style="border-bottom:1px solid #ccc; " | saweri 2[https://sites.google.com/site/niariot87/] | Saweri | Buginese (bug*), Makassar (mak*) | |- style="border-bottom:1px solid #ccc; " | SertoUrhoy 1.20[http://www.bethmardutho.org/index.php/resources/fonts.html] | SertoUrhoy | Syriac (syc), Imperial Aramaic (arc) | |- style="border-bottom:1px solid #ccc; " | Shapour 001.000[https://github.com/behaafarid/shapour_font] | Shapour | Pahlavi Middle Persian (pal*) | |- style="border-bottom:1px solid #ccc; " | SiyamRupali 1.070[https://github.com/potasiyam/Siyam-Rupali] | 'Siyam Rupali' | Bengali (bn*), Bishnupriya Manipuri (bpy*) | |- style="border-bottom:1px solid #ccc; " | Suwannaphum 2.00[http://www.google.com/fonts/specimen/Suwannaphum] | Suwannaphum | Khmer (km) | |- style="border-bottom:1px solid #ccc; " | TaameyFrankCLM 0.110[http://culmus.sourceforge.net/] | 'Taamey Frank CLM' | Old Hebrew (hbo*), Hebrew (he) | Hebrew script (Hebr) |- style="border-bottom:1px solid #ccc; " | TharLon 1.003[http://code.google.com/p/tharlon-font/] | TharLon | Burmese (my*) | |- style="border-bottom:1px solid #ccc; " | Thendral 1.0[https://github.com/thamizha/tamil-fonts] | Thendral | Tamil (ta) | Tamil script (Taml) |- style="border-bottom:1px solid #ccc; " | Thenee 1.0[https://github.com/thamizha/tamil-fonts] | Thenee | Tamil (ta) | Tamil script (Taml) |- style="border-bottom:1px solid #ccc; " | TuladhaJejeg 2.0.1[https://sites.google.com/site/jawaunicode/] | 'Tuladha Jejeg' | Javanese (jv), Javanese in Javanese script (jv-Java*) | |- style="border-bottom:1px solid #ccc; " | UnifrakturMaguntia 2012-10-19[http://unifraktur.sourceforge.net/maguntia.html] | UnifrakturMaguntia | – | Latin fraktur script (Latf) |- style="border-bottom:1px solid #ccc; " | utkal 0.13[http://oriya.sarovar.org/user_download.html] | Utkal | Oriya (or) | Oriya script (Orya) |- style="border-bottom:1px solid #ccc; " | Xerxes 1.301[http://persian.ir/images/7/70/Xerxes.ttf] | Xerxes | Old Persian (peo*) | |} == Gibt es Messungen und Statistiken zu Nutzung und Einfluss? == Ja. Wir haben einige [[Language_tools/Impact_Measurement_and_Metrics#Metrics_for_Universal_Language_Selector|Messungen zum Universal Language Selector]] durchgeführt und sammeln nun Daten mit [[Special:MyLanguage/Extension:EventLogging|EventLogging]] zu einer Vielzahl von mit ULS ausgeführten Handlungen. Mehr dazu unter "[[Special:MyLanguage/Extension:UniversalLanguageSelector/EventLogging queries|Befragungen/Statistik zur ULS Nutzung]]" und einigen dort verlinkten Datensätzen. [[Category:Universal Language Selector{{#translation:}}]] sdn7n35aa5ngyuznr6pi22e8ygghzqt 5386733 5386731 2022-07-28T18:50:28Z ThisCarthing 17456337 Created page with "Schriftart" wikitext text/x-wiki <languages /> == Was ist der Universal Language Selector? == Der Universal Language Selector ist eine Erweiterung von MediaWiki, die es Nutzern erlaubt, Spracheinstellungen und Konfigurationen nach ihren Vorlieben zu verändern. Er verwendet die ''jQuery'' Bibliotheken des Projektes ''Milkshake''. == Welche Spracheinstellungen kann ich mithilfe von ULS anpassen? == Der Universal Language Selector bietet die folgenden Funktionen in Wikimedia Wikis: # Auswahl der Anzeigesprache für angemeldete Benutzer. # WebFonts (Schriftarten) # Eingabemethoden {{anchor|language-territory|How_does_Universal_Language_Selector_determine_which_languages_I_may_understand}} == Wie ermittelt der Universal Language Selector, welche Sprachen ich vermutlich verstehe? == ULS befragt einen Dienstleister, der dein Herkunftland anhand deiner IP-Adresse bestimmt. Diese Information ist nicht immer korrekt. Ausgehend von deiner Länderkennzahl werden dir die dort am häufigsten gesprochenen Sprachen vorgeschlagen. Die "gebräuchlichen Sprachen" innerhalb eines Landes sind ebenfalls schwer zu ergründen. Deshalb stammen diese Informationen aus den [[Milkshake]]-Bibliotheken. Wir zielen darauf, diese mit anderen interessierten Software Projekten über Wikimedia hinaus gemeinsam zu pflegen. Hauptsächlich kommen die Daten jedoch von Unicode (mehr dazu [[translatewiki:CLDR|hier]]) und können in deren [http://www.unicode.org/cldr/charts/latest/supplemental/territory_language_information.html Territory-Language Information|Informationstabelle] eingesehen werden. Wenn du Verbesserungsvorschläge hast, was die dir vom ULS vorgeschlagene Sprachauswahl betrifft, sieh erst nach, ob die Unicode-Infotabelle auf dem besten Stand ist. Falls es dort ebenfalls Verbesserungsbedarf gibt, klicke in der Zeile deines Landes/deiner Sprache auf "add new" und schlage Änderungen vor. Die Unicode-Mitarbeiter sind sehr hilfsbereit und es ist keine Registrierung erforderlich. Bedenke die [http://cldr.unicode.org/index/cldr-spec/definitions CLDR Definitionen] und denke daran, verlässliche Quellen für die vorgeschlagenen Daten anzuführen, wie zum Beispiel ein Amt für Statistik oder eine wissenschaftliche Studie (für Daten zur Lese-/Schreibfähigkeit) oder nationale/lokale Gesetze (um nachzuweisen, dass eine Sprache auch als Amtssprache geläufig ist). {{notice|1=<span lang="en" dir="ltr" class="mw-content-ltr">We're currently taking care of the [http://unicode.org/cldr/trac/ticket/9680 top 3 languages of each country of Europe] but you can also do a more detailed work for a single country, see for instance:</span> {{bug|T64346}}, {{bug|T141650}}, [[phabricator:T142070#2552959|bug T142070]]}} == Wo ist der Universal Language Selector verfügbar? == Momentan ist geplant, den Universal Language Selector so bald wie möglich auf allen Wikimedia Wikis zugänglich zu machen. Details können [[UniversalLanguageSelector/Deployment/Planning|hier]] eingesehen werden. {{anchor|How can I use Universal Language Selector}} == Wie kann ich den Universal Language Selector verwenden? == In Projekten mit mehreren Sprachausgaben (Wikipedia, Wikibooks, Wikiversity, Wiktionary, Wikiquote, Wikivoyage, Wikinews, Wikisource) ist der Universal Language Selector als Zahnradsymbol im Menübereich für Sprachenlinks zu finden. In Wikimedia Projekten ohne Mehrsprachigkeit (z. B. Wikimedia Commons, Meta-Wiki, Wikispecies und dieses Wiki mediawiki.org), befindet sich der ULS als Symbol in der persönlichen Werkzeugleiste oben auf jeder Seite. Klicke auf das Symbol, führe Veränderungen durch und bestätige sie um sie dauerhaft beizubehalten. Ein kleines Tastatur-Symbol wird überall dort erscheinen, wo Texteingaben möglich sind. Wähle es aus um die Einstellungen zu verändern. Lies dir "[[Universal_Language_Selector/Testing#Location_for_the_Selector|Location for the Selector]]"durch um mehr über die Ortsauswahl zu erfahren. == Wie kann ich die Anzeigesprache verändern? == [[File:Using Wikipedia across multiple languages.webm|thumb|Dieses englischsprachige Video zeigt den Ort des Bedienfeldes.]] Die Anzeigesprache der MediaWiki-Interfacemeldungen kann mithilfe des Bedienfeldes für Spracheinstellungen im ULS verändert werden. Auf Wikimediaprojekten steht diese Funktion ausschließlich angemeldeten Nutzern zur Verfügung. Nach der Anmeldung kannst du das Bedienfeld zur Spracheinstellung öffnen (in der Seitenleiste oder oben) und zum Sprachenreiter der Anzeigeeinstellungen navigieren. Für eine schnelle Auswahl wird der ULS eine Liste möglicher Sprachen anzeigen, die auf deinem Standort (IP) basiert. Zur Auswahl klickst du auf die Sprache deiner Wahl. Wenn die Sprache, nach der du suchst, nicht im Bedienfeld verfügbar ist, klicke auf den '...'-Button, um die längere Sprachenliste zu öffnen und wähle die gesuchte Sprache aus. Ein kleines Pop-Up (die technisch Bezeichnung ist "undo popover" oder "tipsy") wird erscheinen, wenn das ULS die Sprache im Vergleich zu Deinen bisherigen Einstellungen ändert, damit Du es schnell wieder ändern kannst. In manchen Fällen wird stattdessen ein Tooltip angezeigt. == Muss ich angemeldet sein, um die Anzeigesprache zu ändern? == Ja. Die Anzeigesprache kann nur von angemeldeten Nutzern verändert werden. == Wenn ich die Anzeigesprache ändere, verändert das auch die Sprache des Inhalts auf der Seite, die ich mir gerade ansehe? == Nein. Der ULS verändert nicht die Sprache des jeweiligen Seiteninhalts. Er kann verwendet werden, um nur die [[interface language|Sprache der Schnittstelle (Interface)]] von MediaWiki zu verändern (die in diesem FAQ manchmal "Anzeigesprache" genannt wird). In Fällen, in denen die Erweiterung {{ll|Extension:Translate|nsp=0}} installiert wurde, kann diese dahingehend konfiguriert werden, den Benutzer zu bestehenden Übersetzungen der Seite zu schicken, wenn das ULS die Sprache der Schnittstelle verändert hat. == Ich sehe Kästchen im Text wenn ich meine Sprache auswähle == Wir nennen diese Boxen "Tofu". Sie tauchen auf, wenn in der gewählten Sprache kein Zeichensatz zur Verfügung steht. Du kannst einen lokalen Zeichensatz of deinem Rechner installieren um das Problem zu beheben. Um ein ähnliches Problem in Zukunft zu verhindern, würden wir aber gerne sicherstellen, dass sich in unserer Schriftarten-Bibliothek Zeichensätze für deine Sprache befinden. Bitte informiere uns daher, vorzugsweise über https://phabricator.wikimedia.org. == Kann ich den Zeichensatz der Sprache verändern? == Schriftarten einer Sprache können vom Nutzer über den "Schriftarten"-Reiter innerhalb der Anzeigeeinstellungen verändert werden. Anonyme Nutzer können den Zeichensatz nur für die aktive Sprache verändern. Angemeldete Nutzer können die Zeichensätze aller Sprachen verändern. == Wie verläuft die Entscheidung für einen voreingestellten Zeichensatz einer Sprache oder eines Skripts? == Ein voreingestellter Zeichensatz wird eingerichtet, wenn eine Sprache oder ein Skript eine problematische Support-Geschichte auf einer großen Bandbreite von Desktop-Computern und anderen Geräten aufweist. Obwohl die meisten modernen Betriebssysteme Möglichkeiten bereithalten, Sprachen oder Skripte gut zu unterstützen, erfordert dies möglicherweise ein vorheriges Handeln des Nutzers. So wird beispielsweise die Installation einer Software oder eine Änderung der Betriebssystemeinstellungen erfordert. Unsere Erfahrung zeigt, dass viele Nutzer dies nicht tun und aufgeben, daher wollen wir einen schnellen und automatischen Weg zur Lesbarkeit der Texte möglich machen. Der Universal Language Selector stellt nur frei lizensierte Zeichensätze zur Verfügung. Wir wählen voreingestellte Schriftarten einerseits aufgrund der Popularität des Zeichensatzes aus (z.B. ein voreingestellter Zeichensatz für ein Skript in Linux-Vertrieben, welche in Portalen der entsprechenden Sprache häufig verwendet werden u.s.w.) und andererseits aufgrund der Eingaben unserer potentiellen Nutzer. Wenn der voreingestellte Zeichensatz Fehler aufweist, die Nutzer am Gebrauch hindern, werden wir versuchen, einen anderen Zeichensatz zu verwenden (falls verfügbar). Hierfür wird in Phabricator ein gültiger Problembericht benötigt. {{anchor|What if the default font chosen is not the best one for the language? Can this be changed?}} == Was passiert, wenn die gewählte Voreinstellung nicht der beste Zeichensatz für die jeweilige Sprache ist? Kann das geändert werden? == Mit dem Universal Language Selector durchgeführte Aktionen beinhalten jetzt das sog. "[[Special:MyLanguage/Extension:EventLogging|Event Logging]]", siehe auch "[[Extension:UniversalLanguageSelector/EventLogging queries|Statistiken und Daten]]". Dies erlaubt den Entwicklern eine Analyse des Nutzerverhaltens und der vorgenommenen Einstellungsveränderungen. Basierend auf dem Nutzerverhalten und anderen Messungen können dann Änderungen durchgeführt werden. Das bedeutet, dass das Eingabewerkzeug und die Zeichensatzunterstützung in WMF-Werkzeugen im EventLogging-System integriert sein müssen. Jede Veränderung der voreingestellten Eingabemethode oder an Zeichensätzen muss von den [[Extension:UniversalLanguageSelector/EventLogging queries|Nutzerstatistiken]] unterstützt werden. Am Beispiel von Zeichensatz A und Zeichensatz B für eine Sprache S: Wenn Satz B häufiger genutzt wird als Satz A, sollte Zeichensatz B zur Standardeinstellung für diese Sprache gemacht werden. Wenn der Systemsatz bei einer Sprache meist präferiert wird, sollte in der Voreinstellung der Internet-Zeichensatz deaktiviert werden. Nach dem gleichen Prinzip funktioniert auch die Einstellung der Eingabemethoden. == Kann ich die von ULS für meine Sprache gewählte Voreinstellung (Zeichensatz) deaktivieren? == Die Voreinstellung kann [[#How can I use Universal Language Selector|in den Einstellungen]] deaktiviert werden. Wenn die Sprache von A-Nutzern und -Betriebssystemen gut unterstützt wird, können die vom System bereitgestellten Einstellungen bzgl. Zeichensatz und Eingabemethoden zur Standardeinstellung werden. Gute Unterstützung bedeutet, dass Browser und Betriebssysteme für die entsprechende Sprache einen fehlerfreien Zeichensatz und eine makellose Eingabemethode als Standardeinstellung zur Verfügung stellen (gebündelt mit OS, ohne spezielle Installationsschritte zu erfordern). == Es scheint keinen Zeichensatz für meine Sprache zu geben. Wie kann ich einen neuen Zeichensatz für ULS anfragen? == Du kannst eine Fehlermeldung auf [https://phabricator.wikimedia.org Phabricator] einreichen, in der du um das Hinzufügen eines Zeichensatzes für deine Sprache bittest. Es wird erwartet, dass du darüber hinaus Vorschläge über mögliche Zeichensätze machst und uns mitteilst, wo sie zu finden sind. Wir empfehlen außerdem, von anderen Mitgliedern deiner Sprachgemeinschaft einen Konsens über die Einbeziehung eines neuen Zeichensatzes einzuholen. == Welche Informationen werden benötigt um einen neuen Zeichensatz in den ULS zu integrieren? == # Den Namen des Zeichensatzes # Die URL der Quelle/des Fundortes # Eine Lizenz für den Zeichensatz, die eine freie Nutzung, Distribution und Veränderung gestattet. Diese Informationen können in Phabricator angeführt werden, wenn um die Aufnahme eines Zeichensatzes gebeten wird. == Ich würde gerne in einer anderen Sprache schreiben. Wie kann ich die Einstellungen dahingehend verändern? == # In der Seitenleiste: Du kannst im Bereich "Eingabeeinstellungen" im Bedienfeld der Spracheinstellungen eine der Sprachen auswählen, die auf den Buttons oder im "Sprachauswahl"-Popup gezeigt werden. # Im Tastatur-Menü: Die Sprachen sind in einer Liste aufgeführt, aus der ausgewählt werden kann. == Ich habe eine Sprache gewählt, kann aber immer noch nicht in dieser Sprache schreiben. Warum? == Wenn du eine Sprache auswählst, wird dir eine Liste mit Eingabemethoden gezeigt. Wenn im ULS für diese Sprache keine Eingabemethoden existieren, wird die lokale Tastatur deines Computers zur Eingabe verwendet. Wenn in keiner der beiden Optionen Eingabemethoden verfügbar sind, ist es nicht möglich, in der gewählten Sprache zu schreiben. == Ich würde gerne die Tastatur für die gewählte Sprache verändern. Wie geht das? == Die Eingabemethoden-/Tastatur-Optionen für eine Sprache im ULS werden sowohl im Bedienfeld der Spracheinstellungen als auch im Tastaturmenü eines Texteingabefeldes als Liste dargestellt. Für jede Sprache ist eine Tastatur voreingestellt. Um eine andere Tastatur zu verwenden, kannst du aus dieser Liste auswählen. == Ich habe eine Tastatur an meinem Computer und möchte nicht die Tastatur des ULS verwenden. Kann ich die ULS-Tastatur vollständig abschalten? == Die ULS-Eingabemethoden können auf zwei Arten deaktiviert werden: # In der Seitenleiste: Klicke auf den "{{int|jquery-ime-disable-text}}"-Button in der "Eingabemethoden"-Option der Spracheinstellungen # Im Tastaturmenü: Klicke auf den "{{int|jquery-ime-disable-text}}"-Button im Tastaturmenü, dass durch klicken auf das Tastatur-Symbol eines Texteingabefeldes (z.B. das Suchfeld) erscheint == Kann ich die ULS-Tastatur für eine einzelne Sprache abschalten, ohne sie vollständig zu deaktivieren? == Ja. Dafür wähle bitte "Native Tastatur verwenden" im Drop-Down-Menü, das in der Liste der verfügbaren Tastaturen in dieser Sprache aufgeführt wird. == Wie wird die Reihenfolge der Eingabemethoden entschieden? == [[File:Key theme - Global South, WMF Metrics Meeting February 2015.pdf|page=18|thumb|Beispielhafter Graph zur Darstellung der Eingabemethoden]] Dies wird für jede Sprache einzeln ausgewertet. Vorzugsweise ist es zuerst einmal die nützlichste und am häufigsten gebrauchte für die jeweilige Sprache, gemäß der Rücksprache mit potentiellen Nutzern. Wenn die Standard-Eingabemethode durch einen Fehler nicht nutzbar sein sollte, wird sie als präferierte oder voreingestellte Eingabemethode deaktiviert. Hierfür wird in Phabricator ein gültiger, aussagekräftiger Fehlerbericht erfordert. Bis der Fehler behoben ist, rückt die nächste verfügbare Eingabemethode an die Spitze der Liste. == Was passiert, wenn die Standard-Eingabemethode nicht die bestmögliche in der Sprache ist? Kann dies verändert werden? == Jede Änderung in den Standardeinstellungen für Eingabemethoden oder Zeichensätze muss durch die [[Extension:UniversalLanguageSelector/EventLogging queries|Nutzungsstatistik]] unterstützt werden. [[#What if the default font chosen is not the best one for the language? Can this be changed?|Hierzu wurde weiter oben schon eine ähnliche Frage gestellt.]] == Kann ich alle Veränderungen in den Spracheinstellungen von meiner Nutzerseite aus vornehmen? == Ja. Um die Spracheinstellungen zu konfigurieren, gehe zu deiner Nutzerseite und klicke unter dem "{{int|prefs-personal}}"-Reiter im "{{int|prefs-i18n}}"-Abschnitt auf "{{int|ext-uls-language-settings-preferences-link}}". {{anchor|Why can anonymous users not use Universal Language Selector to change their interface language}} == Warum können anonyme Nutzer den ULS nicht zum verändern ihrer Schnittstellensprache verwenden? == Diese Option ist auf Wikimedia Wikis deaktiviert, weil die Struktur des Wikimedia Cache dies momentan nicht unterstützt. In Zukunft wollen wir es allerdings möglich machen. Es gibt noch keine Zeitschiene hierfür. <span lang="en" dir="ltr" class="mw-content-ltr">See [[:phab:T134592|Allow setting the UI to a language other than English for anonymous users]] in Phabricator.</span> == Wie kann ich den Universal Language Selector deaktivieren? == Nur Teile des Funktionsangebotes können deaktiviert werden. Eingabemethoden können vollständig ausgeschaltet werden, indem auf das Tastatur-Symbol geklickt und "Eingabewerkzeuge deaktivieren" gewählt wird. Eingabemethoden können pro Eingabeelement ausgeschaltet werden, indem dort <code>class="noime"</code> angefügt wird. Web-Zeichensätze können nur über die Sprache [[#How can I use Universal Language Selector|in den Einstellungen]] deaktiviert werden. == Kann ich die Schnittstelle des Universal Language Selector in meine Sprache übersetzen? == Ja! Du kannst dies auf [[translatewiki:|translatewiki.net]] tun. Vervollständige die Übersetzung der folgenden zwei Meldungsgruppen, sobald du als Übersetzer registriert bist: * [[translatewiki:Special:Translate/ext-universallanguageselector|MediaWiki-Erweiterung]] * <s>[[translatewiki:Special:Translate/ext-jquery-uls|jQuery Plugin]]</s> Existiert nicht mehr. == Wo kann ich ein Problem melden? == Bitte [[Special:MyLanguage/How to report a bug|melde Probleme und Vorschläge in Phabricator]]. Bitte stelle sicher, dass dein Bericht so detailliert wie möglich ist. == What fonts are included? == <span lang="en" dir="ltr" class="mw-content-ltr">An up-to-date list is in the {{git file|action=tree|project=mediawiki/extensions/UniversalLanguageSelector|branch=HEAD|file=data/fontrepo/fonts|text=fonts directory}} of Wikimedia’s Git repository (each folder has metadata in the file font.ini). Here is the list, as of 2013-11-22 (v1.4.0-Snapshot):</span> <!-- this should be expanded with information about font version, language & Unicode block support in each. --> {| style="border-collapse:collapse; border-bottom:3px double #ccc; " |- style="border-bottom:1px solid #ccc; text-align:left; " ! Schriftart ! <span lang="en" dir="ltr" class="mw-content-ltr">CSS font-family name</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">For languages (* denotes default font)</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Additional support</span> |- style="border-bottom:1px solid #ccc; " | AbyssinicaSIL 1.200[http://scripts.sil.org/AbyssinicaSIL] | AbyssinicaSIL | Amharic (am*), Tigrinya (ti*), Ge‘ez (gez*), Tigre (tig*) | Ethiopic/Ge‘ez script (Ethi) |- style="border-bottom:1px solid #ccc; " | Akkadian 2.56[http://users.teilar.gr/~g1951d/] | Akkadian | Akkadian (akk*), Sumerian (sux*) | |- style="border-bottom:1px solid #ccc; " | Alef 1.0[http://alef.hagilda.com/] | Alef, 'Alef Bold' | Hebrew (he), Yiddish (yi), Old Hebrew (hbo) | |- style="border-bottom:1px solid #ccc; " | amiri 1.0.2[http://amirifont.org] | Amiri, 'Amiri Bold', 'Amiri Italic', 'Amiri Bold Italic' | Arabic (ar), Standard Arabic (arb), Persian (fa) | |- style="border-bottom:1px solid #ccc; " | AnjaliOldLipi .0.730[https://sites.google.com/site/cibu/anjalioldlipi-font] | AnjaliOldLipi | Malayalam (ml) | Malayalam script (Mlym) |- style="border-bottom:1px solid #ccc; " | Autonym v 20131118[https://github.com/santhoshtr/AutonymFont/] | Autonym | multiple languages (mul) | |- style="border-bottom:1px solid #ccc; " | CharisSIL 4.011[http://scripts.sil.org/CharisSIL] | CharisSIL | Min Dong (cdo), Min Nan (nan) | Latin script (Latn) |- style="border-bottom:1px solid #ccc; " | DoulosSIL 4.112[http://scripts.sil.org/DoulosSIL] | 'Doulos Sil' | Min Nan (nan) | |- style="border-bottom:1px solid #ccc; " | EastSyriacAdiabene 1.21[http://www.bethmardutho.org/index.php/resources/fonts.html] | 'East Syriac Adiabene' | Syriac (syc), Imperial Aramaic (arc) | |- style="border-bottom:1px solid #ccc; " | EstrangeloEdessa 1.21[http://www.bethmardutho.org/index.php/resources/fonts.html] | 'Estrangelo Edessa' | Syriac (syc*), Imperial Aramaic (arc*) | |- style="border-bottom:1px solid #ccc; " | FreeFontThana 1.0[http://www.gnu.org/software/freefont] | FreeFont-Thaana, 'FreeFont-Thaana Bold] | Maldivian (dv*) | |- style="border-bottom:1px solid #ccc; " | GentiumPlus 1.510[http://scripts.sil.org/gentium] | GentiumPlus, 'GentiumPlus Italic' | Greek (grc) | Greek script (Grek), Latin (Latn), Cyrillic (Cyrl), IPA (und-fonipa) |- style="border-bottom:1px solid #ccc; " | Gubbi 1.3[https://github.com/aravindavk/Gubbi/] | Gubbi | Kannada (kn), Tulu (tcy) | |- style="border-bottom:1px solid #ccc; " | Hanuman 1.0[http://www.google.com/fonts/specimen/Hanuman] | Hanuman, 'Hanuman Bold' | Khmer (km) | |- style="border-bottom:1px solid #ccc; " | IranianSans 1.0[http://fedoraproject.org/wiki/Iranian_fonts] | 'Iranian Sans' | Persian (fa) | Arabic script (Arab) |- style="border-bottom:1px solid #ccc; " | Jomolhari 0.003[https://sites.google.com/site/chrisfynn2/home/fonts/jomolhari] | Jomolhari | Tibetan (bo*, bod*), Dzongkha (dz*), Sino-Tibetan (adx*), Dolpo (dre*), goe*, Humla (hut*), Nubri (kte*), Khams Tibetan (khg*), Khamba (kbg*), Lhomi (lhm*), Ladakhi (lbj*), Lowa (loy*), Lunanakha (luk*), Layakha (lya*), Mukha-Dora (muk*), Walungge (ola*), Old Tibetan (otb*), Tichurong (tcn*), Thudam (thw*), Tseku (tsk*), Classical Tibetan (xct*), Zangskari (zau*) | |- style="border-bottom:1px solid #ccc; " | Junicode 2013-01-17[http://junicode.sourceforge.net/] | Junicode, 'Junicode Italic', 'Junicode Bold', 'Junicode Bold Italic' | Old English (ang) | |- style="border-bottom:1px solid #ccc; " | KhmerOS 1.10[http://www.khmeros.info/drupal612/en/fonts] | KhmerOS | Khmer (km) | |- style="border-bottom:1px solid #ccc; " | KhmerOSbattambang 1.10[http://www.khmeros.info/drupal612/en/fonts] | KhmerOSbattambang | Khmer (km*) | Khmer script (Khmr) |- style="border-bottom:1px solid #ccc; " | LinuxLibertine 5.3.0[http://linuxlibertine.org] | 'Linux Libertine', 'Linux Libertine Bold', 'Linux Libertine Italic', 'Linux Libertine Bold Italic' | – | |- style="border-bottom:1px solid #ccc; " | lklug 0.6[http://www.lug.lk/fonts/lklug] | lklug | Sinhalese (si) | |- style="border-bottom:1px solid #ccc; " | LohitAssamese 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Assamese' | Assamese (as) | Bengali (bn), Bishnupriya Manipuri (bpy) in Assamese script |- style="border-bottom:1px solid #ccc; " | LohitBengali (default) 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Bengali' | Bengali (bn), Bishnupriya Manipuri (bpy) | Assamese (as) in Bengali script (Beng) |- style="border-bottom:1px solid #ccc; " | LohitDevanagari 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Devanagari' | Bhojpuri (bh*, bho*), Hindi (hi*), Konkani (kok*), Goan Konkani (gom*), Maithili (mai*), Sanskrit (sa*) | Marathi (mr), Ahirani (ahr) in Devanagari script (Deva) |- style="border-bottom:1px solid #ccc; " | LohitGujarati 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Gujarati' | Gujarati (gu*) | Gujarati script (Gujr) |- style="border-bottom:1px solid #ccc; " | LohitKannada 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Kannada' | Kannada (kn*), Tulu (tcy*) | Kannada script (Knda) |- style="border-bottom:1px solid #ccc; " | LohitMarathi 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Marathi' | Ahirani (ahr*), Marathi (mr*) | |- style="border-bottom:1px solid #ccc; " | LohitNepali 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Nepali' | Nepali (ne*) | |- style="border-bottom:1px solid #ccc; " | LohitOriya 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Oriya' | Oriya (or*) | Oriya script (Orya) |- style="border-bottom:1px solid #ccc; " | LohitPunjabi 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Punjabi' | Punjabi (pa*) | Gurmukhi script (Guru) |- style="border-bottom:1px solid #ccc; " | LohitTamil 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Tamil' | Tamil (ta) | Tamil script (Taml) |- style="border-bottom:1px solid #ccc; " | LohitTamilClassical 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Tamil Classical' | Tamil (ta) | Tamil script (Taml) |- style="border-bottom:1px solid #ccc; " | LohitTelugu 2.5.3[https://fedorahosted.org/lohit/] | 'Lohit Telugu' | Telugu (te*) | Telugu script (Telu) |- style="border-bottom:1px solid #ccc; " | madan 2[http://www.mpp.org.np] | Madan | Nepali (ne) | Hindi (hi), Marathi (mr), Maithili (mai), Bhojpuri (bh, bho), Goan Konkani (gom), Ahirani (ahr) in Devanagari script (Deva) |- style="border-bottom:1px solid #ccc; " | Meera 6.0[https://savannah.nongnu.org/projects/smc] | Meera | Malayalam (ml) | Malayalam script (Mlym) |- style="border-bottom:1px solid #ccc; " | MiriamCLM 0.130[http://culmus.sourceforge.net/] | 'Miriam CLM' | Hebrew (he) | Hebrew script (Hebr) |- style="border-bottom:1px solid #ccc; " | Myanmar3 3.0[http://code.google.com/p/myanmar3source/] | Myanmar3 | Burmese (my) | Myanmar (Burmese) script (Mymr) |- style="border-bottom:1px solid #ccc; " | NafeesWeb 1.2[http://www.crulp.org/nafeesWebNaskh.html] | NafeesWeb | Urdu (ur) | |- style="border-bottom:1px solid #ccc; " | Nazli 0.4[http://persian-computing.org/] | Nazli | Persian (fa) | |- style="border-bottom:1px solid #ccc; " | Nokora 1.10[http://www.google.com/fonts/specimen/Nokora] | 'Nokora Regular', 'Nokora Bold' | Khmer (km) | |- style="border-bottom:1px solid #ccc; " | NuosuSIL 2.1.1[http://scripts.sil.org/SILYI_home] | 'Nuosu SIL' | Sichuan Yi (ii*) | |- style="border-bottom:1px solid #ccc; " | OpenDyslexic 2.1.0+git060dc841[https://github.com/antijingoist/open-dyslexic] | OpenDyslexic, 'OpenDyslexic Bold', 'OpenDyslexic Italic', 'OpenDyslexic BoldItalic' | Afrikaans (af), [unknown] (bk), Catalan (ca), Welsh (cy), Danish (da), German (de), English (en), Spanish (es), Estonian (et), Finnish (fi), Faroese (fo), French (fr), West Frisian (fy), Irish (ga), Scottish Gaelic (gd), Galician (gl), Hungarian (hu), Indonesian (id), Icelandic (is), Italian (it), Luxembourgish (lb), Limburgish (li), Māori (mi), Malay (ms), Norwegian Bokmål (nb), Dutch (nl), Occitan (oc), Polish (pl), Portuguese (pt), Albanian (sq), Swedish (sv), Swahili (sw), Tagalog (tl), Turkish (tr), Walloon (wa) | |- style="border-bottom:1px solid #ccc; " | OskiEast 2.200[http://www.languagegeek.com/font/fontdownload.html#AlgonAndInu] | OskiEast, 'OskiEast Bold', 'OskiEast Italic', 'OskiEast Bold Italic' | Cree (cr*), Inuktitut (iu) | |- style="border-bottom:1px solid #ccc; " | Padauk 2.8[http://scripts.sil.org/Padauk] | Padauk | Burmese (my) | Myanmar (Burmese) script (Mymr) |- style="border-bottom:1px solid #ccc; " | Pagul 1.0[http://sourceforge.net/projects/pagul/] | Pagul | Saurashtra (saz*) | Saurashtra script (Saur) |- style="border-bottom:1px solid #ccc; " | Pangururan 1.0.5[http://evertype.com/fonts/batak/] | Pangururan | Batak Toba (bbc), Batak btk | |- style="border-bottom:1px solid #ccc; " | Phetsarath 1.01[http://phetsarath.gov.la] | Phetsarath, Phetsarath-Bold | Lao (lo*) | |- style="border-bottom:1px solid #ccc; " | Saab 0.91[http://guca.sourceforge.net/typography/fonts/saab/] | Saab | Punjabi (pa) | Gurmukhi script (Guru) |- style="border-bottom:1px solid #ccc; " | saweri 2[https://sites.google.com/site/niariot87/] | Saweri | Buginese (bug*), Makassar (mak*) | |- style="border-bottom:1px solid #ccc; " | SertoUrhoy 1.20[http://www.bethmardutho.org/index.php/resources/fonts.html] | SertoUrhoy | Syriac (syc), Imperial Aramaic (arc) | |- style="border-bottom:1px solid #ccc; " | Shapour 001.000[https://github.com/behaafarid/shapour_font] | Shapour | Pahlavi Middle Persian (pal*) | |- style="border-bottom:1px solid #ccc; " | SiyamRupali 1.070[https://github.com/potasiyam/Siyam-Rupali] | 'Siyam Rupali' | Bengali (bn*), Bishnupriya Manipuri (bpy*) | |- style="border-bottom:1px solid #ccc; " | Suwannaphum 2.00[http://www.google.com/fonts/specimen/Suwannaphum] | Suwannaphum | Khmer (km) | |- style="border-bottom:1px solid #ccc; " | TaameyFrankCLM 0.110[http://culmus.sourceforge.net/] | 'Taamey Frank CLM' | Old Hebrew (hbo*), Hebrew (he) | Hebrew script (Hebr) |- style="border-bottom:1px solid #ccc; " | TharLon 1.003[http://code.google.com/p/tharlon-font/] | TharLon | Burmese (my*) | |- style="border-bottom:1px solid #ccc; " | Thendral 1.0[https://github.com/thamizha/tamil-fonts] | Thendral | Tamil (ta) | Tamil script (Taml) |- style="border-bottom:1px solid #ccc; " | Thenee 1.0[https://github.com/thamizha/tamil-fonts] | Thenee | Tamil (ta) | Tamil script (Taml) |- style="border-bottom:1px solid #ccc; " | TuladhaJejeg 2.0.1[https://sites.google.com/site/jawaunicode/] | 'Tuladha Jejeg' | Javanese (jv), Javanese in Javanese script (jv-Java*) | |- style="border-bottom:1px solid #ccc; " | UnifrakturMaguntia 2012-10-19[http://unifraktur.sourceforge.net/maguntia.html] | UnifrakturMaguntia | – | Latin fraktur script (Latf) |- style="border-bottom:1px solid #ccc; " | utkal 0.13[http://oriya.sarovar.org/user_download.html] | Utkal | Oriya (or) | Oriya script (Orya) |- style="border-bottom:1px solid #ccc; " | Xerxes 1.301[http://persian.ir/images/7/70/Xerxes.ttf] | Xerxes | Old Persian (peo*) | |} == Gibt es Messungen und Statistiken zu Nutzung und Einfluss? == Ja. Wir haben einige [[Language_tools/Impact_Measurement_and_Metrics#Metrics_for_Universal_Language_Selector|Messungen zum Universal Language Selector]] durchgeführt und sammeln nun Daten mit [[Special:MyLanguage/Extension:EventLogging|EventLogging]] zu einer Vielzahl von mit ULS ausgeführten Handlungen. Mehr dazu unter "[[Special:MyLanguage/Extension:UniversalLanguageSelector/EventLogging queries|Befragungen/Statistik zur ULS Nutzung]]" und einigen dort verlinkten Datensätzen. [[Category:Universal Language Selector{{#translation:}}]] o0xj9p84cmvnrjvpqexktpmakvrn58h Help:Templates/cs 12 442499 5386378 5242999 2022-07-28T13:26:05Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla, nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre><span lang="en" dir="ltr" class="mw-content-ltr">{{Thankyou|1=adding “=”|2=Me}}</span></pre> zobrazí se {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáz pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} <span lang="en" dir="ltr" class="mw-content-ltr">Often default values are used to specify alternate names of parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, the template will first look for a parameter named "a".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] rpfyz5c01jobvz92h173v2j5q9z12qa 5386381 5386378 2022-07-28T13:28:52Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre><span lang="en" dir="ltr" class="mw-content-ltr">{{Thankyou|1=adding “=”|2=Me}}</span></pre> zobrazí se {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáz pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} <span lang="en" dir="ltr" class="mw-content-ltr">Often default values are used to specify alternate names of parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, the template will first look for a parameter named "a".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] lypqrev7k2v8w9pijces9uyx8w5gojp 5386391 5386381 2022-07-28T13:40:56Z ENeRZet 17359278 Created page with "{{Thankyou|1=přidání "="|2=Tonda}}" wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáz pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} <span lang="en" dir="ltr" class="mw-content-ltr">Often default values are used to specify alternate names of parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, the template will first look for a parameter named "a".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] 0auu1gyekt0dbzp7c3qp54q1f1pp3h8 5386393 5386391 2022-07-28T13:41:05Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáz pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} <span lang="en" dir="ltr" class="mw-content-ltr">Often default values are used to specify alternate names of parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, the template will first look for a parameter named "a".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] qzrjtavcj4tijgp7jd0jkyexrp8fu9b 5386404 5386393 2022-07-28T13:47:24Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=co nezobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáz pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} <span lang="en" dir="ltr" class="mw-content-ltr">Often default values are used to specify alternate names of parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, the template will first look for a parameter named "a".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] 2wpxk1wo3ct9h6a18x2dqzcliujwsiy 5386406 5386404 2022-07-28T13:47:49Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáz pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} <span lang="en" dir="ltr" class="mw-content-ltr">Often default values are used to specify alternate names of parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, the template will first look for a parameter named "a".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] fjeu79cvmye4d7h6tr5wn3xz9dc0p0m 5386410 5386406 2022-07-28T13:50:02Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} <span lang="en" dir="ltr" class="mw-content-ltr">Often default values are used to specify alternate names of parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, the template will first look for a parameter named "a".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] ah4s93trlhcr7bsyvw6gvxhir54io0a 5386413 5386410 2022-07-28T13:51:35Z ENeRZet 17359278 Created page with "K určení alternativních názvů parametrů se často používají výchozí hodnoty." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, the template will first look for a parameter named "a".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] a98jaavxvczjsgdhli60cq64qhaf399 5386415 5386413 2022-07-28T13:52:11Z ENeRZet 17359278 Created page with "Pokud máte například $1, šablona nejprve vyhledá parametr s názvem "$2"." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". <span lang="en" dir="ltr" class="mw-content-ltr">If it is not set, it will use the parameter named "b".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] s6w1l3zzu2m6ebacex5motn05m8kw10 5386417 5386415 2022-07-28T13:52:26Z ENeRZet 17359278 Created page with "Pokud není nastaven, použije parametr s názvem "$1"." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". <span lang="en" dir="ltr" class="mw-content-ltr">If neither "a" nor "b" is set, it will output nothing.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] lippak3gu19vlts2kfb65yrrexzmlh4 5386419 5386417 2022-07-28T13:53:01Z ENeRZet 17359278 Created page with "Pokud není nastaveno ani "$1" ani "$2", nevypíše se nic." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. <div lang="en" dir="ltr" class="mw-content-ltr"> === Evaluation === </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] p6gdaq2rijo314lrzgjngn4gvf7u7sr 5386421 5386419 2022-07-28T13:54:01Z ENeRZet 17359278 Created page with "=== Hodnocení ===" wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is an advanced topic which you can skip unless you need it.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] dljqmvpgor02udeqduq0b9a3gmzigpw 5386423 5386421 2022-07-28T13:54:34Z ENeRZet 17359278 Created page with "Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} <span lang="en" dir="ltr" class="mw-content-ltr">Generally speaking, template parameters are substituted into the template after tokenization, but as is.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] q0zea8ghqzoszw23wids7gz9q4e33kj 5386425 5386423 2022-07-28T13:56:52Z ENeRZet 17359278 Created page with "Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. <span lang="en" dir="ltr" class="mw-content-ltr">They are not evaluated until they are used.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] au1hc9tb1v9vobdwdpw7qrmx0oz3jel 5386427 5386425 2022-07-28T13:57:14Z ENeRZet 17359278 Created page with "Nejsou hodnoceny, dokud nejsou použity." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. Nejsou hodnoceny, dokud nejsou použity. <span lang="en" dir="ltr" class="mw-content-ltr">This has a few consequences.</span> First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] ns32570hvr908ngylqy3cwbhcvbyxt4 5386429 5386427 2022-07-28T13:57:36Z ENeRZet 17359278 Created page with "To má několik důsledků." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. Nejsou hodnoceny, dokud nejsou použity. To má několik důsledků. First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. <span lang="en" dir="ltr" class="mw-content-ltr">You can still use templates to control the name of a parameter or template, but you cannot split a template call amongst multiple templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] swni242pimgnpyemube5tjqq1eb74s5 5386431 5386429 2022-07-28T13:58:04Z ENeRZet 17359278 Created page with "K ovládání názvu parametru nebo šablony můžete stále používat šablony, ale nemůžete rozdělit volání šablony mezi více šablon." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. Nejsou hodnoceny, dokud nejsou použity. To má několik důsledků. First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. K ovládání názvu parametru nebo šablony můžete stále používat šablony, ale nemůžete rozdělit volání šablony mezi více šablon. <span lang="en" dir="ltr" class="mw-content-ltr">The second consequence of this is dead-code elimination.</span> If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] tm8b95xcjuq7w5jknhbhoq6vgf8bxz1 5386433 5386431 2022-07-28T13:58:44Z ENeRZet 17359278 Created page with "Druhým důsledkem je odstranění mrtvého kódu." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. Nejsou hodnoceny, dokud nejsou použity. To má několik důsledků. First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. K ovládání názvu parametru nebo šablony můžete stále používat šablony, ale nemůžete rozdělit volání šablony mezi více šablon. Druhým důsledkem je odstranění mrtvého kódu. If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. <span lang="en" dir="ltr" class="mw-content-ltr">Many but not all parser functions, parser tags and trancluded special pages are not directly included like templates but instead are replaced by a "strip marker".</span> <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] c8s2xi04z3f5khjoyooy3bnaizblmz2 5386435 5386433 2022-07-28T13:59:35Z ENeRZet 17359278 Created page with "Mnoho, ale ne všechny funkce analyzátoru, značky analyzátoru a transkludované speciální stránky nejsou přímo zahrnuty jako šablony, ale místo toho jsou nahrazeny "strip marker"." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. Nejsou hodnoceny, dokud nejsou použity. To má několik důsledků. First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. K ovládání názvu parametru nebo šablony můžete stále používat šablony, ale nemůžete rozdělit volání šablony mezi více šablon. Druhým důsledkem je odstranění mrtvého kódu. If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. Mnoho, ale ne všechny funkce analyzátoru, značky analyzátoru a transkludované speciální stránky nejsou přímo zahrnuty jako šablony, ale místo toho jsou nahrazeny "strip marker". <span lang="en" dir="ltr" class="mw-content-ltr">This means you cannot manipulate the results with parser functions like padleft: or similar functions from extensions, as they see the strip marker instead of the result of the parser function.</span> === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] 7xp2ck59nk8heqyddlgqqicsb7mkrkz 5386438 5386435 2022-07-28T14:03:01Z ENeRZet 17359278 Created page with "To znamená, že nemůžete manipulovat s výsledky pomocí funkcí analyzátoru, jako je $1 nebo podobných funkcí z rozšíření, protože místo výsledku funkce analyzátoru vidí značku stripu." wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. Nejsou hodnoceny, dokud nejsou použity. To má několik důsledků. First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. K ovládání názvu parametru nebo šablony můžete stále používat šablony, ale nemůžete rozdělit volání šablony mezi více šablon. Druhým důsledkem je odstranění mrtvého kódu. If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. Mnoho, ale ne všechny funkce analyzátoru, značky analyzátoru a transkludované speciální stránky nejsou přímo zahrnuty jako šablony, ale místo toho jsou nahrazeny "strip marker". To znamená, že nemůžete manipulovat s výsledky pomocí funkcí analyzátoru, jako je padleft: nebo podobných funkcí z rozšíření, protože místo výsledku funkce analyzátoru vidí značku stripu. === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] owphsx1vfa4mi0v5evwz3atde61gmjw 5386440 5386438 2022-07-28T14:03:21Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} Máte-li standardní texty, které chcete zařadit na několika stránkách, je funkce šablon ideálním nástrojem. Na rozdíl od rozšíření a mediálních souborů zde není žádné centrální úložiště šablon. Šablony mohou být nově napsány nebo pro uložení již provedené duplicitní práce exportovány z jiné wiki např. Wikipedie a poté importovány do cílové wiki. == Vytvoření == Šablony jsou standardní wiki stránky, jejichž obsah je navržen tak, aby byl '''[[Special:MyLanguage/Transclusion|transkludován]]''' (vložen) do jiných stránek. Šablony se řídí konvencí, že název má předponu "<code>Template:</code>" a přiřazuje jej k tomuto [[Special:MyLanguage/Help:Namespaces|jmennému prostoru]]. Kromě toho je můžete [[Special:MyLanguage/Help:Starting a new page|vytvořit jako kteroukoli jinou wiki stránku]]. Nejjednodušší použití šablon je následující. Pokud vytvoříte stránku s názvem "Template:Welcome" s obsahem: Ahoj! Vítejte na wiki. vytvořili jste svou první šablonu! Pokud zadáte kód: <nowiki>{{Welcome}}</nowiki> na jakékoli jiné stránce se místo se zobrazí místo <code><nowiki>{{Welcome}}</nowiki></code> zobrazí text "Ahoj! Vítejte na wiki.". Obsah šablony je "přenesen" na tuto stránku, tj. je na stránce integrován. Kód <code><nowiki>{{Welcome}}</nowiki> </code> můžete vložit na kterékoli místo jakékoli stránky, na které chcete někoho přivítat. Předpokládejme, že se používá na 100 stránkách. Pokud změníte obsah šablony na: Ahoj! Vítejte na této skvělé wiki. znovu na kterékoli ze 100 stránek, kde byla šablona použita, uvidíte již nový text místo původního. Tímto způsobem jste změnili obsah 100 stránek, aniž byste je upravovali, protože na tyto stránky je přenesena šablona. Toto je základní princip. Existuje několik dalších funkcí transluze, které obohacují tento mechanismus a činí šablony velmi užitečnými. == Použití == Šablony lze použít na jiných stránkách těmito způsoby: * <code><nowiki>{{Name}}</nowiki></code> - jak je popsáno výše, bude tento odkaz dynamicky nahrazen aktuálním obsahem <nowiki>[[Template:Name]]</nowiki> v okamžiku '''načtení''' stránky s odkazem na šablonu. Odkaz zůstane ve zdroji stránky nezměněn. * <code><nowiki>{{subst:Name}}</nowiki></code> - při použití tohoto odkazu šablony bude jednou provždy nahrazen obsahem <nowiki>[[Template:Name]]</nowiki> v době, kdy je stránka s odkazem '''uložena''': Kopie obsahu <nowiki>[[Template:Name]]</nowiki> bude ''nahrazena'' odkazem na šablonu. Obsah je pak součástí stránky a může být upravován normálně, odděleně od originálu. ''Poznámka'': Pozdější změny na stránce zdrojové šablony nebudou přeneseny na stránku s odkazem na šablonu. * <code><nowiki>{{safesubst:Name}}</nowiki></code> - toto bylo zavedeno s cílem umožnit nahrazení, které nepřerušuje transkluzi (zahrnutí stejného obsahu do více dokumentů, aniž by bylo nutné tyto dokumenty upravovat samostatně), viz [[w:Help:Substitution#The safesubst: modifier]]. * <code><nowiki>{{msgnw:Name}}</nowiki></code> - obsahuje šablonu ve formě, která ji zobrazuje jako nezpracovanou wiki syntaxi (způsobem {{tag|nowiki|open}}), když je načtena stránka, která ji obsahuje. Ve skutečnosti lze běžnou wiki stránku použít také jako šablonu, jednoduše zadáním jmenného prostoru, ve kterém se nachází, takže: * <code><nowiki>{{Template:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Pagename]]</nowiki></code> * <code><nowiki>{{Talk:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Talk:Pagename]]</nowiki></code> * <code><nowiki>{{:Pagename}}</nowiki></code> zahrnuje <code><nowiki>[[Pagename]]</nowiki></code> ** <code><nowiki>{{subst::Pagename}}</nowiki></code> se nahrazuje obsahem<code><nowiki>[[Pagename]]</nowiki></code> Pokud takový jmenný prostor neexistuje, považuje se celý název za šablonu: * <code><nowiki>{{Foo:Bar}}</nowiki></code> zahrnuje <code><nowiki>[[Template:Foo:Bar]]</nowiki></code> {{anchor|Parameters}} == Parametry == Pro obohacení mechanismu transkluze umožňuje MediaWiki předat parametry šabloně, když je transkludována. Parametry umožňují šabloně vytvářet různý obsah nebo mít různé chování. Předpokládejme, že chcete vložit malou poděkovací poznámku na [[Special:MyLanguage/Help:Talk pages|diskusní stránku]] dalších uživatelů, například: {{Thankyou|vaše úsilí|Tonda}} Jako první parametr šablony bude uvedeno zač je děkováno (v tomto případě "vaše úsilí") a jako druhý jméno děkujícího (např. "Tonda"). Vaším cílem je, aby kterýkoli uživatel mohl tímto způsobem za něco poděkovat jinému uživateli, kupř. v rámci diskuze. Šablonu, například s názvem {{ll|Template:Thankyou}}, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. I když bude vypadat každé poděkování podobně, jeho obsah (tj. důvod a podpis) se bude lišit vždy, pokud ji použije k poděkování někdo jiný, někomu jinému, za něco jiného. A to je obsah, který se bude předávat přes parametry. Zapomeňme pro tuto chvíli na ostatní prvky, které ovlivňují podobu rámečku a umístění obrázku. Z hlediska obsahu šablony, je rozhodující následující obsah: <syntaxhighlight lang=moin> '''Díky...''' za {{{1}}}. Zdraví {{{2}}} </syntaxhighlight> Všimněte si použití <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>{{{2}}}</nowiki></code>. Tak se do šablony vloží parametry předané při použití šablony. Identifikátory parametrů jsou uzavřeny do '''ztrojených''' složených závorek: <code><nowiki>{{{ }}}</nowiki></code>. To zajistí, že se nebudou interpretovat jako názvy šablony. Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" (<code>|</code>). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. {{anchor|Anonymous parameters}} === Nepojmenované, poziční parametry === Pokud parametry předané šabloně nepojmenujete, bude rozhodující jejich pořadí: <nowiki>{{Thankyou|vaše úsilí|Tonda}}</nowiki> V tomto případě se šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předají dva poziční parametry <code><nowiki>{{{1}}}=vaše úsilí</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>: {{Thankyou|vaše úsilí|Tonda}} Pořadí, ve kterém jsou parametry uvedeny, je pro jejich zpracování důležité. Podívejme se, jak bude vypadat výsledek zpracování, pokud uvedeme tyto parametry v obráceném pořadí: <nowiki>{{Thankyou|Tonda|vaše úsilí}}</nowiki> a tohle je výsledek: {{Thankyou|Tonda|vaše úsilí}} {{note|1=Podle pozice se zpracovávají pouze nepojmenované parametry. Pokud použijete při pojmenování číslo pozice (např. <code><nowiki>{{{1}}}</nowiki></code> atd.) nemusí šablona fungovat správně. Žádné parametry identifikované jménem, jak je uvedeno níže, nebudou pro šablonu přístupné pomocí pořadových čísel.}} {{note|1=Pozor také na znak "rovnítka" <code>=</code>. Pokud se objeví v hodnotě pozičního parametru, může být předchozí textová hodnota tohoto parametru chybně interpretována jako identifikátor [[#Named parameters|pojmenovaného parametru]] (což vysvětlujeme níže). Stává se to poměrně často, pokud chcete jako poziční parametr šablony použít externí link nebo parametrizovaný HTML element (viz {{task|T16235}}). Vyhnete se mu, pokud místo pozičních parametrů použijete parametry pojmenované, resp. očíslované.}} === Číslované parametry === Předávané parametry lze identifikovat podle čísla už při jejich předání: <nowiki>{{Thankyou|2=Tonda|1=tvé přátelství}}</nowiki> Tentokrát jsou šabloně <code><nowiki>{{Thankyou}}</nowiki></code> předané dva očíslované parametry <code><nowiki>{{{1}}}=tvé přátelství</nowiki></code> a <code><nowiki>{{{2}}}=Tonda</nowiki></code>. A přestože byly v šabloně uvedené v obráceném pořadí,jsou zpracované takto: {{Thankyou|2=Tonda|1=tvé přátelství}} {{note|1=To se hodí, obzvláště pokud by mohl některý z parametrů obsahovat znak "=".}} ;Příklad: <pre>{{Thankyou|1=přidání "="|2=Tonda}}</pre> zobrazí se: {{Thankyou|1=přidání "="|2=Tonda}} {{warning|1=Pokud ale použijete k identifikaci některého parametru číslo, tak byste měli uvést identifikátor i u těch ostatních.}} {{anchor|Named parameters}} === Pojmenované parametry === Místo čísel můžete použít jako identifikátory i textové řetězce. V tomto případě by se obsah šablony změnil na: <pre><nowiki>'''Díky...''' za {{{reason}}}. Zdraví {{{signature}}}</nowiki></pre> V šabloně nyní místo čísla použijeme pro první parametr <code><nowiki>{{{reason}}}</nowiki></code> a pro druhý <code><nowiki>{{{signature}}}</nowiki></code>: <nowiki>{{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}}</nowiki> V tomto případě šablona <code><nowiki>{{Thankyou}}</nowiki></code> převezme parametry <code><nowiki>{{{{reason}}}=to že jsi tím, kým jsi </nowiki></code> a <code><nowiki>{{{signature}}}}=Tonda</nowiki></code> a vytvoří: {{Thankyou|signature=Tonda|reason=to že jsi tím, kým jsi}} Pojmenované parametry rozlišují velká a malá písmena, takže: <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> zobrazí: {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. === Výchozí hodnoty === Pokud převedete šablonu, která očekává parametry, ale neposkytnete jejich argumenty, tímto způsobem: <nowiki>{{Thankyou}}</nowiki> v příkladu s číslovanými parametry, uvedeném výše, získáte následující: {{Thankyou}} Vzhledem k tomu, že nebyly předány žádné argumenty, představuje šablona samotné parametry namísto jejich příslušných hodnot. V těchto případech může být užitečné definovat '' výchozí '' hodnoty pro parametry, tj. hodnoty, které budou použity, pokud nebude předána žádná hodnota. Například pokud se obsah šablony změní na: <syntaxhighlight lang=moin> '''Děkuji...''' za {{{reason|všechno}}}. kdo, {{{signature|Já}}} </syntaxhighlight> pak <code><nowiki>{{reason|všechno}}</nowiki></code> definuje, že pokud není poskytnut žádný argument pro parametr <code>{{{reason}}}</code>, pak bude použita hodnota <code>všechno</code>. Podobně <code><nowiki>{{{signature|Já}}}</nowiki></code>, výchozí parametr <code> {{{signature}}}</code> má hodnotu <code>Já</code>. Výsledkem opětovného převedení šablony bez předání argumentu je následující: <!-- strictly speaking, this example is false, because the template call was changed to obtain the desired effect - but the effect is the same if the template is defined as described --> {{Thankyou|reason=všechno|signature=Já}} K určení alternativních názvů parametrů se často používají výchozí hodnoty. Pokud máte například <code><nowiki>{{{a|{{{b|}}} }}}</nowiki></code>, šablona nejprve vyhledá parametr s názvem "a". Pokud není nastaven, použije parametr s názvem "b". Pokud není nastaveno ani "a" ani "b", nevypíše se nic. === Hodnocení === {{Note|1=Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete.}} Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. Nejsou hodnoceny, dokud nejsou použity. To má několik důsledků. First of all, if you have a <code>Template:Start</code> containing <code><nowiki>{{mytemplate</nowiki></code>, and a <code>Template:End</code> containing <code><nowiki>|foo=bar}}</nowiki></code>, and put <code><nowiki>{{start}}{{end}}</nowiki></code> on a page, ''mytemplate'' isn't transcluded, because tokens like "|" cannot be added by a template and keep their special meaning in templates. K ovládání názvu parametru nebo šablony můžete stále používat šablony, ale nemůžete rozdělit volání šablony mezi více šablon. Druhým důsledkem je odstranění mrtvého kódu. If you make a template call like <code>{{foo|{{DISPLAYTITLE:Bar}} }}</code>, and Template:Foo does not contain <nowiki>{{{1}}}</nowiki>, then the displaytitle is not used, since it is only evaluated when needed, and it there is no parameter to substitute it into, so it is never evaluated. This usually comes into play when using [[Extension:ParserFunctions]], and can be especially noticed when used in combination with the <code><nowiki>int:</nowiki></code> magic word that varies by user language. Template calls starting with the magic word <code>subst:</code> or <code>safesubst:</code> are evaluated in a separate first pass that only happens at save time, along with <nowiki>~~~~</nowiki> and links using the [[pipe trick]]. If they cannot be evaluated during the first pass, subst: calls are ignored, and safesubst: are treated as if a normal template. Mnoho, ale ne všechny funkce analyzátoru, značky analyzátoru a transkludované speciální stránky nejsou přímo zahrnuty jako šablony, ale místo toho jsou nahrazeny "značkou stripu". To znamená, že nemůžete manipulovat s výsledky pomocí funkcí analyzátoru, jako je padleft: nebo podobných funkcí z rozšíření, protože místo výsledku funkce analyzátoru vidí značku stripu. === Rekurze v šablonách === Zahrnutí šablony samo o sobě nespustí MediaWiki do nekonečné rekurze (určitá procedura nebo funkce je znovu volána dříve, než je dokončeno její předchozí volání). MediaWiki zastaví rekurzi tučným názvem šablony. Pokud je například obsah Template:Aaaa <code>a <nowiki>{{Aaaa}}</nowiki> z</code>, zobrazí se "a a <span class="error">Template loop detected: '''Template:Aaaa'''</span> z z". <!-- NOTE TO TRANSLATORS: I don't edit much in this space. If my contribution exceeds the allowable translation burden, feel free to toss this into the talk page instead. My own feeling is that in any realm of computer science, self-recursion should never be documented as inherently evil, but for pragmatism. MaxEnt on 18 December 2021 --> ====Forbidden idiom==== This safeguard precludes a potentially useful template idiom where a template self-normalizes its own calling arguments. In this forbidden example <code>template:d</code> can either be called <code><nowiki>{{d|20200311}}</nowiki></code> or <code><nowiki>{{d|y=2020|m=3|d=11}}</nowiki></code>. If called in the first manner, it recurses into itself with the second argument structure (obtained using string parser functions), which then follows a unified processing path. :<code><nowiki>{{#if:{{{1|}}}|{{d|y={{#sub:{{{1}}}|0|4}}|m={{#sub:{{{1}}}|4|2}}|d={{#sub:{{{1}}}|6|2}}}}|<!-- processing path with arguments y,m,d regardless of original call pattern -->}}</nowiki></code> If <code>template:d</code> is modified to recurse into <code>template:d/2</code> and <code>template:d/2</code> is an ''identical manual copy'' of <code>template:d</code> this idiom works fine as the self-recursion safeguard operates dynamically and not statically. A feasible way for the MediaWiki software to loosen the self-recursion rule would be to require that each recursive call have a distinct argument count from all previous active calls, at most once recursing with the argument count non-decreasing. That would provide a strong guarantee against infinite self-recursion while enabling useful idioms such as the one described here in a flexible manner. If the processing path is of low complexity, a simple solution using only one template is to handle each calling convention on a separate if/else branch, duplicating the logic of the processing path within each case. If the processing path is more complex, each call-structure case can delegate to an implementation template with a unified call structure which provides the final template behaviour. === Tables in parameters === Since the syntax for wikitables involves pipes in single braces ({ }) and using the [[w:Help:Pipe trick|pipe trick]] will not work in transclusion parameters, one will have to create a table as a separate page and transclude it from there.<ref> [https://en.wikipedia.org/wiki/Draft:Enzo_Enzo?action=edit&section=5 Look at the invisible comment] </ref> == Zahrnutí kontrolní šablony == Ve výchozím nastavení je obsah šablony zobrazen jako celek. A to jak při přímém prohlížení, tak při zahrnutí na jinou stránku. Můžete však určit, pomocí značek {{tag|noinclude|open}}, {{tag|includeonly|open}} a {{tag|onlyinclude|open}}, které části šablony se budou zobrazovat a zahrnovat. Všechno mezi {{tag|noinclude|open}} a {{tag|noinclude|close}} bude vidět pouze tehdy, když se stránka šablony prohlíží přímo, ale ne, když je zahrnuta do jiné stránky. To je užitečné, pokud chcete do šablony zahrnout text nebo kód, který nechcete šířit na žádné stránky, které jej obsahují, jako například: * [[Special:MyLanguage/Help:Categories|Odkazy]] při kategorizaci samotné šablony. * [[Special:MyLanguage/Help:Links#Interlanguage links|Mezijazyčné odkazy]] na podobné šablony v jiných jazycích. * Vysvětlující text k použití šablony. Podobně bude cokoli mezi {{tag|includeonly|open}} a {{tag|includeonly|close}} zpracováno a zobrazeno pouze při zahrnutí stránky, ale ne při přímém prohlížení stránky šablony. To je užitečné v situacích, jako například: * [[Special:MyLanguage/Help:Categories|Kategorizace]] stránek obsahujících šablonu. ''Poznámka:'' Při změně kategorií použitých šablonou tímto způsobem nemusí být kategorizace stránek, které tuto šablonu obsahují, aktualizována okamžitě, ale až za nějaký čas: Zpracovává ji {{ll|Manual:Job queue|fronta úloh}}. Chcete-li vynutit změnu kategorizace konkrétní stránky, otevřete ji pro úpravy a uložte ji beze změn. * Zajištění, že kód šablony nebude spuštěn při prohlížení samotné stránky šablony. Obvykle je to proto, že očekává parametry a provedení bez parametrů má nežádoucí výsledek. Všechno mimo {{tag|noinclude|open}} a {{tag|includeonly|open}} je zpracováno a zobrazeno normálně. To znamená, když se stránka šablony prohlíží přímo nebo když je šablona zahrnuta na jiné stránce. Důraz je kladen na to, co je uvnitř těchto dvou značek. Všechno mimo {{tag|onlyinclude|open}} tagy je při převodu vyřazeno. Dokonce i sekce označené pouze includeonly (včetně) jsou při převodu zahozeny, pokud nejsou označeny jako onlyinclude (zahrnout pouze). Důraz je kladen na to, co je mimo tuto značku. Je také možné vnoření těchto značek. Tři značky pro částečný přechod umožňují všechny možné kombinace toho, co je zpracováno a vykresleno. Roli plní i komentáře. == Organizování šablon == Aby byly šablony efektivní, uživatelé je musí jednoduše najít a zjistit, jak je správně používat. Uživatelé je mohou najít: # Klikněte na '''{{int|specialpages}}''' > '''{{int|allpages}}''' # V seznamu '''{{int|namespace}}''' zvolte '''Template''' a klikněte na '''{{int|allpagessubmit}}'''. Chcete-li poskytnout informace o způsobu použití, připojte na stránku šablony takovýto příklad: <pre><nowiki> <noinclude> == Použití == Uživatelé vítejte: {{Thankyou|reason=tvůj důvod|signature=tvůj podpis}} </noinclude> </nowiki></pre> Redaktor potom podobnou stránku vytvoří tak, že příklad jednoduše zkopíruje. == Propojení na šablonu == Stránku šablony lze propojit s jakoukoli jinou stránkou wiki. Například odkaz [[Template:Navbar]] je generován pomocí wikicode <code><nowiki>[[Template:Navbar]]</nowiki></code>. Na mnoha wikinách [[Template:Tl]] lze použít k vytvoření odkazu na šablonu formátovanou způsobem, který ukazuje wikicode "double curly-braces" nezbytný k převedení šablony bez skutečného provedení převodu. Například kód <code><nowiki>{{tl|Navbar}}</nowiki></code> může být použit k vytvoření odkazu {{tl|Navbar}}. Tento způsob se běžně používá v dokumentaci šablon, na stránkách nápovědy a na diskusních stránkách při odkazování na šablony. Stejného efektu lze dosáhnout použitím <code><nowiki>{{[[Template:Navbar|Navbar]]}}</nowiki></code>, ale použití {{tl|tl}} vyžaduje o dost méně psaní. Na jakékoli dané wiki šablona Tl, pokud existuje, může nebo nemusí vykreslit text v prvku "kód" nebo jako typ monospace. Pokud ne (jako na této wiki), může tak učinit jiná podobně pojmenovaná šablona. Viz například část [[Template:Tl#See also|"Viz také" naší dokumentace Template:Tl]]. == Kopírování z jedné wiki do druhé == Šablony často vyžadují [[m:Special:MyLanguage/Help:Cascading_style_sheets|CSS]] nebo jiné šablony, takže uživatelé mají často potíže s kopírováním šablon z jedné wiki do druhé. Následující kroky by měly fungovat pro většinu šablon. === MediaWiki code === Pokud máte nová importní práva (konkrétně importupload): # Přejděte na [[Special:Export]] na původní wiki a stáhněte soubor .xml s úplnou historií všech potřebných šablon, takto: #* Do textového pole zadejte název šablony, např. "emplate:Welcome". Zvláštní pozornost věnujte malým a velkým písmenům a zvláštním znakům - pokud není název šablony přesně správný, může dojít k exportu, ale soubor XML nebude mít očekávaná data. #* Zaškrtněte políčko "{{int|export-templates}}". #* zaškrtněte políčko "{{int|exportcuronly}}". #* Klikněte na "{{int|export-submit}}". # Na nové wiki přejděte na [[Special:Import]] a nahrajte soubor .xml. Pokud nemáte nová importní práva na novou wiki: # Přejděte na šablonu, kterou chcete zkopírovat z původní wiki. Přejděte na stránku úprav a zkopírujte celý wikitext # Na nové wiki přejděte na stránku se stejným názvem jaký má kopírovaná šablona. Stiskněte vytvořit a upravit a vložte wikitext, který jste zkopírovali. V souhrnu úprav každé šablony vytvořte odkaz na původní stránku pro přiřazení. # V původní wiki v editačním okně pod editačním polem sledujte seznam "Templates used on this page" (šablony použité na této stránce). Pro každou uvedenou šablonu postupujte podle těchto pokynů. Totéž udělejte pro jakoukoli šablonu používanou kteroukoli z těchto šablon atd. Tím se zkopíruje celý nezbytný kód a bude stačit pro některé šablony. Všimněte si, že se exportují pouze prvky stránky analyzované při vykreslování stránky, takže například podstránky dokumentace nejsou exportovány jako součást tohoto procesu. Pokud to nefunguje, zkontrolujte také červené odkazy uvedené v části "Pages transcluded onto the current version of this page:" (stránky přenesené na aktuální verzi této stránky) pod editačním polem. Pokud nějaké existují, opakujte výše uvedené kroky i pro ně a také zkopírujte kód do modulů. Po úspěšném importu šablony a všech souvisejících šablon z druhé wiki šablonu upravte tak, aby vyhovovala vaší wiki. Chcete-li například změnit logo, odeberte nadbytečné kategorie nebo červené odkazy. === Rozšíření === Přípona často používaná v šablonách je ParserFunctions. Navštivte stránku {{ll|Help:Extension:ParserFunctions|nsp=0}} a zkontrolujte, zda se ve zkopírovaných šablonách nepoužívají některé ze zde uvedených funkcí. Pokud ano, musíte nainstalovat rozšíření {{ll|Extension:ParserFunctions|nsp=0}}. K jeho instalaci budete potřebovat systémový administrátorský přístup k serveru vaší instalace MediaWiki. Další závislost, kterou lze použít v šablonách, zejména na Wikipedii, je [[w:Lua (programming language)|Lua (programovací jazyk)]]. Dobré je mít '''<code><nowiki>{{#invoke: }}</nowiki></code>''' v kódu šablony. V případě, že se používá, musíte nainstalovat rozšíření {{ll|Extension:Scribunto|nsp=0}}. I zde je vyžadován přístup správce systému. Na této stránce naleznete další pokyny k instalaci a používání rozšíření. === CSS a kód JavaScript === Kromě kódu MediaWiki mnoho šablon využívá CSS a některé spoléhají na plné fungování JavaScriptu. Pokud se zkopírované šablony nebudou chovat podle očekávání, může zde být příčina. Chcete-li zkopírovat požadované CSS a JavaScript na svou wiki, obvykle budete potřebovat administrátorská oprávnění, protože budete upravovat systémové zprávy ve jmenném prostoru "MediaWiki:". # Vyhledejte v textu šablony použití tříd CSS (text jako <code>class="foobar"</code>). Pokud se tyto třídy objeví v "MediaWiki:Common.css" nebo "MediaWiki:Monobook.css" na původní wiki, zkopírujte tyto třídy do "MediaWiki:Common.css" na nové wiki a zkontrolujte, zda je šablona v pořádku. # Jestliže zkopírovaná šablona stále nefunguje podle očekávání, zkontrolujte, zda se na původní wiki nachází kód "MediaWiki:Common.js" nebo "MediaWiki:Monobook.js". Pokud ano, můžete jej zkusit zkopírovat na "MediaWiki:Common.js" na nové wiki. Obvykle je vhodné kopírovat kód pouze z důvěryhodných zdrojů a nejprve procházet kód, identifikovat a vybrat části, které jsou relevantní. Můžete najít komentáře, které mohou sloužit jako vodítka pro identifikaci funkčnosti každé části. == Související stránky == * [[w:Help:Table|w:Help:Table]] - nejjednodušší návod k použití. * {{ll|Help:TemplateData}} * {{ll|Help:External searches}} – příklad zvláštního použití šablony * {{ll|Help:Magic words}} – fantastické věci, které najdete v některých šablonách * {{ll|Help:Extension:ParserFunctions}} – další ozdobné ovládací funkce, jako je #if a #switch * {{ll|Help:Parser functions in templates}} – návod k používání funkcí syntaktického analyzátoru v šablonách * [[m:Special:MyLanguage/Help:Template|m:Nápověda:Šablona]] — obsahuje mnohem důkladnější příručku o tom, jak přesně šablony fungují * [[m:Special:MyLanguage/Help:Advanced templates|m:Nápověda:Pokročilé šablony]] — popisuje ještě pokročilejší techniky, jako jsou dynamická volání šablon a názvy proměnných parametrů * [[m:Special:MyLanguage/Help:Embed page|m:Nápověda:Vložit stránku]] — vkládání stránek ze [[Special:MyLanguage/Help:Namespaces|jmenných prostorů]] jiných než <code>Template:</code>. * {{ll|Manual:Importing Wikipedia infoboxes tutorial}} * {{ll|Help:ExpandTemplates}} * {{ll|Extension:PageTemplates}} * {{ll|Manual:Creating pages with preloaded text}} – Using templates as the starting text of a page == Externí odkazy == * [https://template.miraheze.org/wiki/Miraheze_Template_Wiki Úložiště šablon Miraheze] - Šablony MediaWiki určené ke všeobecnému použití. [[Category:Help{{#translation:}}|Templates]] [[Category:Template{{#translation:}}]] [[Category:MediaWiki for site admins{{#translation:}}]] i686sj2yxuywj85kv7t2oybc2zap2u0 Translations:Manual:Installation guide/11/ja 1198 453715 5387285 4699643 2022-07-28T21:56:07Z Baris6161TURK 17188421 wikitext text/x-wiki 画像のサムネイル作成には追加のプログラムが必要です。$1 (ビジュアルエディタに必要) とその他のサービスがそれぞれに必要とするものです。 0xqpvvahd7drt77i6f26kg7un3hm95g Manual:Installation guide/scn 100 501310 5386667 5381107 2022-07-28T17:14:36Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/scn]] i9f0quh6dabzgbak0reh4bxwo5t33ac 5386685 5386667 2022-07-28T17:23:03Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/scn]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Installation/scn 0 501348 5387797 1907066 2022-07-29T09:24:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Template:InstallationNav/as 10 510880 5387187 5384771 2022-07-28T21:17:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Wikitext standard/en 0 521632 5387868 3797117 2022-07-29T10:33:04Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Historical|1=Most of the text found on this page was written from 2003-2006. See {{ll|Wikitext}} for the latest status on wikitext standardization efforts.}} A single '''[[Special:MyLanguage/wikitext|wikitext]] standard''' is of great importance for the long-term stability of the MediaWiki software. We need to describe and formalize a [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] version of the Wikitext language, based on what is used currently. In other words this work should not (for right now) involve incorporating improvements or changes to the Wikitext language. Releases must be stable and predictable so that other software developers can work to the same markup syntax, and know for sure that they will not be facing random or arbitrary changes for some fixed time period, like a year. This suggests there may be [[Special:MyLanguage/wikitext 2005|wikitext 2005]], [[Special:MyLanguage/wikitext 2006|wikitext 2006]] and so on. [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] was tracking which mediawiki sites are doing what best. Wikipedia won't always be the furthest ahead on an issue, nor should its needs necessarily always trump others in the mediawiki software design effort. For instance [[meta:Wikitravel|Wikitravel]] may do better on geography and [[meta:Spacetime DTD|map]] issues. The first useful map and underlying data standards like an [[meta:Ecoregion DTD|ecoregion DTD]] and [[meta:Spacetime DTD|spacetime DTD]] may be easier to work on there, where these are more central issues. Other subtasks like a [[meta:Person DTD|person DTD]] may become WikiProjects undertaken by a disciplined group of scholars who know, or want to know, everything about documenting people. ==Tasks== #Write a [[Special:MyLanguage/markup spec|markup spec]] #Write an efficient [[Special:MyLanguage/Alternative parsers|Wikitext to HTML converter]], to replace the current PHP code. #Write a set of unit tests to validate the correctness of a Wikitext to HTML converter. ===XML-Related Tasks=== #Write a [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]] that can serve as a canonical translation of Wikitext <=> XML, for further processing by XML tools. ''Or use [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. #Write a Wikitext to XML converter. #* Evaluate [http://www.tldp.org/wt2db/ wt2db]. #* Or use [http://schematics.sourceforge.net WebBot], A PLT Scheme package that acts as a Bot on MediaWiki and contains the parser to convert WikiText to the [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. ==Publishing the Standard== A clear standard can be published and supported by other wikis, like MoinMoinWiki ([[:en:Python_programming_language|python]]-based) and tikiwiki (see [http://tikiwiki.sourceforge.net sourceforge]), which are very popular, and more extensible than mediawiki, which has serious structural problems Even if mediawiki can keep up with those other packages, text import/export has to be one of our priorities, given the objectives of this project to become a central GNU FDL repository of trusted text for use all over the place. The [[meta:Wikimedia|Wikimedia]] activities shouldn't be in any way trapped or tied to MediaWiki, if drastically better software emerges from tikiwiki or the Python world. And it will, eventually. ===Long Term Plans === #when things settle down, say [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], then: #create a consortium of all users, developers of various types of software, including [[meta:IRC/Channels|chat]] and [[Special:MyLanguage/email|email]] based systems that incorporate features like [[Special:MyLanguage/Trillian Instant Lookup|Trillian Instant Lookup]] - not all users of Wikipedia use a web browser #agree on a [[meta:Simple ideology of Wikitax|simple ideology of Wikitax]] to make it easy for content generated elsewhere to quickly become wiki pages #develop a unified base boot like KnoppixTiki that supports the new standard so it can be used for any kind of data storage like in a PIM #stabilize and publish something like [[Special:MyLanguage/wikitext 2008|wikitext 2008]] as a real RFC #aim for [[Special:MyLanguage/wikitext 2009|wikitext 2009]] or [[Special:MyLanguage/wikitext 2010|wikitext 2010]] to be an ITU standard See also: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] r7vvfdjyk3yorally0ztg0anbyviijj Manual:Installing third-party tools/en 100 523538 5387820 5377078 2022-07-29T09:28:47Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/en]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/en]] ep2omt629u3b99k59akhk57r2ef2gew Manual:Installing MediaWiki/en 100 547013 5387491 5384964 2022-07-28T22:45:18Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} This page covers all steps to manually install and configure MediaWiki. MediaWiki can be difficult to install if you do not have any experience with Apache (web server software), PHP and MySQL/MariaDB (database). The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]]. The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. {{Note|If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].}} == Check the installation requirements == Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. == Download the MediaWiki software == Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. == Extract the MediaWiki software == The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format. You need to uncompress this archive file before use. You can uncompress the file locally (and then upload via FTP to the server) or directly on your server. On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). On Linux and Mac OS X, you can uncompress the file using the command: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup. On Linux systems, the command would be using [[w:chown|chown]] as the following: <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==Upload files to your web server== If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. Upload the files to your web server's web directory either by: # directly copying the unzipped folder or # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). # by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager'' If your upload tool has a "change file names to lowercase" option, then you must disable this. If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive. By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}. The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system. In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>. In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>. Rename the uploaded folder to whatever you would like to have in the URL. If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>. {{Note|1=Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].}} {{anchor|Create a database}} == Set up the database == MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. SQLite, MariaDB/MySQL, and PostgreSQL are supported databases. If you're unsure which database to choose, use MariaDB. After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory. For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed. If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. See the corresponding documentation of your hosting provider. Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you. The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account. If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].}} ===PostgreSQL=== If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form. Often, this is the database user named <code>postgres</code>. The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. createuser -S -D -R -P -E wikiuser (then enter the database password) createdb -O wikiuser my_wiki or as superuser (default postgres) execute the following commands at the database prompt: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. {{anchor|Run the installation script}} == Run the installation script == Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. ==Further configuration== * {{ll|Manual:System administration#Configuration}} - Additional configuration * {{ll|Manual:Administrators}} - Wiki administration == Keep up to date! == Once installed, make sure you stay up to date with releases, and keep your server secure! {{Clickable button 2|Subscribe to the MediaWiki release announcements mailing list.|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} == Appendices == {{anchor|Alternatives to manual installation|Alternative to manual installation}} === Alternatives to manual installation === Instead of manually installing MediaWiki, alternative options might be easier: * [[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]] * [[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]] :{{Note|1=Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.}} See also the {{ll|comparison of distribution options}}. === System-specific instructions === The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. However, by and large these per-system docs are less maintained and might not always be up to date. First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation. {{anchor|Wiki families (multiple wikis)}} === Running multiple wikis === Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. {{anchor|Installing an existing wiki}} === Importing an existing wiki database === Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. == See also == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 8fwp0sqkw4uu48bzvu1p9ug04vw8v84 Translations:Manual:Installing MediaWiki/33/ja 1198 555293 5387231 2042546 2022-07-28T21:28:06Z Shirayuki 472859 update wikitext text/x-wiki == データベースをセットアップする == f8qkba08521fx7jnrvn8xs53iorheas Help:TemplateData/cs 12 561698 5386186 5386177 2022-07-28T12:00:26Z ENeRZet 17359278 Created page with "Hodnota $1 je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[$2|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In VisualEditor and the 2017 wikitext editor, <code>"date"</code> has no visible effect. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In the 2010 wikitext editor with TemplateWizard, <code>"date"</code> makes the parameter input box about a third shorter and adds a dropdown calendar, allowing the user to choose a date input. It also displays the grey example text in the input box "YYYY-MM-DD". If an input does not conform to this standard, the box glows red, however the editor will always output a date conforming to the standard (if numbers are entered) or nothing (if only text or nothing is entered). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''With other parameters''' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In the 2010 wikitext editor with TemplateWizard, <code>"date"</code> overrides the effects of <code>"[[#Autovalue|autovalue]]"</code>; the value of <code>"autovalue"</code> will not be automatically placed in the input box if the parameter type is <code>"date"</code>. </div> |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, když uživatel klepne odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> g0ncjx9e70gj01sorghcxhtwj6hqtdq 5386188 5386186 2022-07-28T12:00:32Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' <div lang="en" dir="ltr" class="mw-content-ltr"> * In VisualEditor and the 2017 wikitext editor, <code>"date"</code> has no visible effect. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In the 2010 wikitext editor with TemplateWizard, <code>"date"</code> makes the parameter input box about a third shorter and adds a dropdown calendar, allowing the user to choose a date input. It also displays the grey example text in the input box "YYYY-MM-DD". If an input does not conform to this standard, the box glows red, however the editor will always output a date conforming to the standard (if numbers are entered) or nothing (if only text or nothing is entered). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''With other parameters''' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In the 2010 wikitext editor with TemplateWizard, <code>"date"</code> overrides the effects of <code>"[[#Autovalue|autovalue]]"</code>; the value of <code>"autovalue"</code> will not be automatically placed in the input box if the parameter type is <code>"date"</code>. </div> |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, když uživatel klepne odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> qkl3nybuhza5uzuq7lx5k31xhoyh478 5386191 5386188 2022-07-28T12:00:49Z ENeRZet 17359278 Created page with "* V aplikaci VisualEditor a editoru wikitext 2017 nemá $1 žádný viditelný efekt." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. <div lang="en" dir="ltr" class="mw-content-ltr"> * In the 2010 wikitext editor with TemplateWizard, <code>"date"</code> makes the parameter input box about a third shorter and adds a dropdown calendar, allowing the user to choose a date input. It also displays the grey example text in the input box "YYYY-MM-DD". If an input does not conform to this standard, the box glows red, however the editor will always output a date conforming to the standard (if numbers are entered) or nothing (if only text or nothing is entered). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''With other parameters''' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In the 2010 wikitext editor with TemplateWizard, <code>"date"</code> overrides the effects of <code>"[[#Autovalue|autovalue]]"</code>; the value of <code>"autovalue"</code> will not be automatically placed in the input box if the parameter type is <code>"date"</code>. </div> |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, když uživatel klepne odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 80n8i87ehe0uucn0zqouz8ezeob2bgt 5386196 5386191 2022-07-28T12:01:42Z ENeRZet 17359278 Created page with "* Ve wikitextovém editoru pro rok 2010 s TemplateWizard $1 zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic)." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). <div lang="en" dir="ltr" class="mw-content-ltr"> '''With other parameters''' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In the 2010 wikitext editor with TemplateWizard, <code>"date"</code> overrides the effects of <code>"[[#Autovalue|autovalue]]"</code>; the value of <code>"autovalue"</code> will not be automatically placed in the input box if the parameter type is <code>"date"</code>. </div> |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, když uživatel klepne odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 1ykcm3oogjmarjbngcps148h2tuo2by 5386198 5386196 2022-07-28T12:01:52Z ENeRZet 17359278 Created page with "'''S jinými parametry'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' <div lang="en" dir="ltr" class="mw-content-ltr"> * In the 2010 wikitext editor with TemplateWizard, <code>"date"</code> overrides the effects of <code>"[[#Autovalue|autovalue]]"</code>; the value of <code>"autovalue"</code> will not be automatically placed in the input box if the parameter type is <code>"date"</code>. </div> |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, když uživatel klepne odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 4fkt0hsom9q3stbnkfkac8th0y73yzw 5386200 5386198 2022-07-28T12:01:59Z ENeRZet 17359278 Created page with "* V editoru wikitext 2010 s TemplateWizard, $1 přepíše efekty $2. Hodnota $3 nebude automaticky vložena do vstupního pole, pokud je typ parametru $4." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, když uživatel klepne odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> b7at1gpqrr3pg533ub918y7xz87z1y2 5386202 5386200 2022-07-28T12:04:25Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, když uživatel klepne odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> awv6xf0texmldpkgpxnnbgve3j35emw 5386206 5386202 2022-07-28T12:09:36Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> lqb0ubu1ri4btjz5jan7metkt0zz2qu 5386208 5386206 2022-07-28T12:09:49Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 7xt1r7m0yllbh7ppikgm0ohcy8dk09i 5386211 5386208 2022-07-28T12:10:28Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> qrieg7pk3agjz3k33wrxa6ko6229hyh 5386213 5386211 2022-07-28T12:11:19Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> dii9s8qbd90msbwjxi1svou5vxtxf9w 5386215 5386213 2022-07-28T12:11:37Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> pcuzgftjzm8jfwc0kznf7hc3nnxlct1 5386217 5386215 2022-07-28T12:12:40Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 5qb7j0y7dejaszc6810nu6rfyos1wyk 5386219 5386217 2022-07-28T12:13:03Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> cln4fsyiopzu1c67jhqvmwgq66wub4w 5386221 5386219 2022-07-28T12:13:13Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. <span lang="en" dir="ltr" class="mw-content-ltr">The file names do not contain the "File:" namespace prefix.</span> Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> kcpbndqaizqdumzbiga48qirayjjbec 5386223 5386221 2022-07-28T12:14:08Z ENeRZet 17359278 Created page with "Názvy souborů neobsahují předponu jmenného prostoru "$1"." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki, nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> tg2izlbfz3wj5h37vl567qf4hmh0q5w 5386225 5386223 2022-07-28T12:15:17Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> az26ne1zvmk66s8k9emlf8kk48hzx36 5386227 5386225 2022-07-28T12:16:51Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 4sd0spe57lj56mfemivdfjstzvrnhss 5386229 5386227 2022-07-28T12:17:35Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné než šablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> l41hs1yl3g17yimn50o2luoz3l7wnwr 5386231 5386229 2022-07-28T12:20:08Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 8xzrb8eroyjxn3fzlba4d3dhjb68to3 5386233 5386231 2022-07-28T12:20:41Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditor a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 6w1zwu4hf2hh4vu076zh90s9jyjge9m 5386235 5386233 2022-07-28T12:21:02Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> f32f4tj3se75y2ozh9sxk42f4ms7rm7 5386237 5386235 2022-07-28T12:21:30Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> rchy9jlrv32czqsx2b1chyd9cjzviir 5386239 5386237 2022-07-28T12:21:38Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. <div lang="en" dir="ltr" class="mw-content-ltr"> '''Effects''' </div> * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> oi052uvvuf0g9gtzs743izuxzvkdz09 5386243 5386239 2022-07-28T12:23:21Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> ouqjnhst3ka3bhoieu9iph2urmdf8ba 5386245 5386243 2022-07-28T12:23:31Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znakech a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> i1ny3xrlba5d0ytstldwxz3ohbel2n9 5386247 5386245 2022-07-28T12:25:57Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti řetězce formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 66wm7uj3r2wf3jj8fk4c2gvwc746rwg 5386250 5386247 2022-07-28T12:29:52Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak dojde k neplatnosti formátového řetězce. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 3pdwh2p5l3e4jgw5dwtdo9dxeeh0eb1 5386252 5386250 2022-07-28T12:30:15Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formátování řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> ct7yi03t1n5s3u23ymydms4adm23rji 5386254 5386252 2022-07-28T12:31:00Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Vložené formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> kyyf8pcek3okmu3vfy19mcbbv8j4rfe 5386256 5386254 2022-07-28T12:31:40Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inlin formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 96bsynulb53ikcgi8ctl6tqdlf59otu 5386258 5386256 2022-07-28T12:31:49Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Před názvem parametru není mezera, každá šablona na vlastním řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 1eh52wbg55go9iukq43k7krgz8r7jhb 5386260 5386258 2022-07-28T12:32:51Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislitka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> a5dsiu13bey67hewfvh4a54fdg9oek0 5386262 5386260 2022-07-28T12:33:59Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, potrubí vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 7g2svgeqgeyfrcmdwezf8i6tvrzvusz 5386264 5386262 2022-07-28T12:34:22Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate níže a přidat do šablony nová data TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> ahsdbc8az8efohqwkzmydgzfxu21t23 5386266 5386264 2022-07-28T12:35:06Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Bad JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> idur3434txxkwwn5hl36drrhbl5lze2 5386268 5386266 2022-07-28T12:35:44Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). <span lang="en" dir="ltr" class="mw-content-ltr">These errors can be difficult to detect and come in too many forms to list.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 7rg6tcd77ta4kyza80jgimx8p7vb4qs 5386270 5386268 2022-07-28T12:37:29Z ENeRZet 17359278 Created page with "Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. <span lang="en" dir="ltr" class="mw-content-ltr">The best way to avoid them is to edit template data exclusively with the TemplateData editor; the best way to detect them once they've occurred is to use an external JSON validator, such as [[#jsonlint|JSONLint]], which will highlight errors and aid in fixing them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 4pxbflcef2yedd4hku7xtjtzvzy293b 5386272 5386270 2022-07-28T12:38:14Z ENeRZet 17359278 Created page with "Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například $1, který zvýrazní chyby a pomůže je opravit." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. <span lang="en" dir="ltr" class="mw-content-ltr">The 2010 wikitext editor does not check for invalid JSON thanks to an old, unfixed bug ({{phab|T128029}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> r7dnrn0x896g6x3uv3ojsmo2mf9sker 5386274 5386272 2022-07-28T12:38:42Z ENeRZet 17359278 Created page with "Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ($1)." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). <span lang="en" dir="ltr" class="mw-content-ltr">Pages that contain invalid JSON may throw alarming "{{int|internalerror}}" messages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> nbr58iry5nzz6zj5i3y2mlr7trwcima 5386276 5386274 2022-07-28T12:39:17Z ENeRZet 17359278 Created page with "Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "$1"." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". <span lang="en" dir="ltr" class="mw-content-ltr">To fix these errors, your best bet is to use a JSON validator (see above).</span> {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> f36yxi35jvi33f44nyoa8mwigjng6bv 5386278 5386276 2022-07-28T12:39:41Z ENeRZet 17359278 Created page with "Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše)." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete parametr v <code>"[[#Params|params]]"</code>, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 1f1x8lotlr24o4k0h3sfvd1cc3gvekg 5386280 5386278 2022-07-28T12:41:45Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který chybí. To odkazuje na jeho pořadí v sekvenci, ale to je o jeden méně než jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 3z0zvz9kpj5p77uw90j0ezn1irryx3r 5386282 5386280 2022-07-28T12:43:16Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- This parameter is not stated in "paramOrder", but it should be. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> oxio8neaql4uuts7myvo3poasq2cgzp 5386284 5386282 2022-07-28T12:43:47Z ENeRZet 17359278 Created page with "Tento parametr není uveden v $1, ale měl by být." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Error: Required property "paramOrder[2]" not found. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 89qvawqhebsbic49grs6dm7z4dr1gj6 5386287 5386284 2022-07-28T12:44:31Z ENeRZet 17359278 Created page with "Chyba: Požadovaná vlastnost "$1" nebyla nalezena." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> gkvg7pk2xrthkw9806e3k5101zaxwmm 5386289 5386287 2022-07-28T12:45:17Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete parametr v <code>"[[#ParamOrder|paramOrder]]"</code>, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 9ekvm1m5prkc0kyshflu8f6dq3zra3s 5386291 5386289 2022-07-28T12:45:54Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na parametr v <code>"paramOrder"</code>, který by tam neměl být. To odkazuje na jeho pořadí v sekvenci, ale to je o jedno méně než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole; 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 1isojxy956mqbktp6skje1rfinyi41b 5386293 5386291 2022-07-28T12:46:19Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- This parameter is not stated in "params", but it should be. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> d85v7rxrmh9u1ebedi61ggvg30gb9ml 5386295 5386293 2022-07-28T12:46:28Z ENeRZet 17359278 Created page with "Tento parametr není uveden v $1, ale měl by být." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Error: Invalid value for property "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> s82zx5szhjk3bb3aznsexgks2g83pnp 5386297 5386295 2022-07-28T12:47:06Z ENeRZet 17359278 Created page with "Chyba: Neplatná hodnota vlastnosti "$1"." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Alternativně můžete odebrat objekt <code>"paramOrder"</code> a tuto chybu odstranit. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> f0a6lvi0nd5f9znff6ve6zjixr7t05i 5386299 5386297 2022-07-28T12:47:28Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> e2cf9oh53u26l39us3mmc0r7j1av4gd 5386301 5386299 2022-07-28T12:48:03Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- These quotation marks shouldn't be here. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> skz9uiwylaa4efajp4x1q8jyju1af7f 5386303 5386301 2022-07-28T12:49:07Z ENeRZet 17359278 Created page with "Tyto uvozovky by zde neměly být." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Error : Property "format" is expected to be "inline", "block", or a valid format string. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 97xwvaaekna99q9ejh15he5yi1k68ee 5386305 5386303 2022-07-28T12:50:20Z ENeRZet 17359278 Created page with "Chyba: Předpokládá se, že vlastnost "$1" bude "$2", "$3" nebo platný formátovací řetězec." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky; viz část [[#Custom formats|#Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> qqurq07zi3uj6v23w9345b7v4t5vq2x 5386307 5386305 2022-07-28T12:50:56Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Alternativně můžete odstranit tuto chybu pomocí parametru <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 6ndbcd8wwtejj69qylccmlhognvqnr0 5386309 5386307 2022-07-28T12:51:37Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === <span lang="en" dir="ltr" class="mw-content-ltr">This error occurs if you state a parameter that does not exist in TemplateData.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 0k9lysj8ps8q4unhltpg766eks4vszd 5386311 5386309 2022-07-28T12:52:32Z ENeRZet 17359278 Created page with "K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. <span lang="en" dir="ltr" class="mw-content-ltr">This is probably due to spelling mistakes.</span> <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> cb4gl9npezd1dix9a8xomjlebw6agzx 5386313 5386311 2022-07-28T12:52:58Z ENeRZet 17359278 Created page with "To je pravděpodobně způsobeno pravopisnými chybami." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- spelling mistake "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> dv5mfxr17lv6nl6mwlncr672x2orogn 5386315 5386313 2022-07-28T12:53:21Z ENeRZet 17359278 Created page with "pravopisná chyba" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami, nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 6suofupqjmyc4xvlyj8ev8o7tn3cjpr 5386317 5386315 2022-07-28T12:53:39Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- incorrectly placed parameter "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> kd259nsxsz9xze7bya803l1btzb57z0 5386319 5386317 2022-07-28T12:54:45Z ENeRZet 17359278 Created page with "špatně umístěný parametr" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." omylem. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> q6wqsz78q17pamyhlb98rw6t7l9qlt0 5386321 5386319 2022-07-28T12:55:46Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." v chybě. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, make sure you don't state any parameters that don't exist for a TemplateData object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 6mw7wz4qh0k3fpcagzy18pc1nbtyk85 5386323 5386321 2022-07-28T12:56:22Z ENeRZet 17359278 Created page with "Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." v chybě. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou správně umístěny. Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují. <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> iv4459okoznj9uq1ewo1f1urxrfc9ny 5386325 5386323 2022-07-28T12:56:39Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." v chybě. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou umístěny správně. Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují. <span lang="en" dir="ltr" class="mw-content-ltr">You can check which parameters exist for an object in the section [[#TemplateData parameters|#TemplateData parameters]].</span> === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> iiflogf1ciwtlc1i9c96vy3ip7lm355 5386327 5386325 2022-07-28T12:57:18Z ENeRZet 17359278 Created page with "V sekci [[$1|Parametry TemplateData]] můžete zkontrolovat, které parametry pro objekt existují." wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." v chybě. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou umístěny správně. Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují. V sekci [[#TemplateData parameters|Parametry TemplateData]] můžete zkontrolovat, které parametry pro objekt existují. === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedia]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> 70wnqkzihrroetgxt6kz09w8oapvsku 5386329 5386327 2022-07-28T13:03:33Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." v chybě. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou umístěny správně. Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují. V sekci [[#TemplateData parameters|Parametry TemplateData]] můžete zkontrolovat, které parametry pro objekt existují. === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedie]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který čte zdrojovou šablonu wikicodu a snaží se najít všechny použité parametry a vydá dokument kostry s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> ho6g9wgs1fzxz134jjzbbpll6d0ks39 5386332 5386329 2022-07-28T13:15:05Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." v chybě. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou umístěny správně. Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují. V sekci [[#TemplateData parameters|Parametry TemplateData]] můžete zkontrolovat, které parametry pro objekt existují. === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedie]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který načte zdrojový wikikód šablony, pokusí se najít všechny použité parametry a vytvoří kostru dokumentu s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * S [[w:de:Template:TemplateData|dewiki template TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> bf4vepwtagws22zg7hydmog6w6s06os 5386334 5386332 2022-07-28T13:17:58Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." v chybě. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou umístěny správně. Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují. V sekci [[#TemplateData parameters|Parametry TemplateData]] můžete zkontrolovat, které parametry pro objekt existují. === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedie]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který načte zdrojový wikikód šablony, pokusí se najít všechny použité parametry a vytvoří kostru dokumentu s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * V [[w:de:Template:TemplateData|šabloně dewiki TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * <span lang="en" dir="ltr" class="mw-content-ltr">https://query.wikidata.org/ and [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]]</span> ek5l5bea5inu1e9yzw2lwsu9scxwvid 5386336 5386334 2022-07-28T13:18:15Z ENeRZet 17359278 Created page with "$1 a [[$2|Query Helper]]" wikitext text/x-wiki <languages/> {{PD Help Page}} {{anchor|What is TemplateData?}} '''{{ll|Extension:TemplateData|TemplateData}}''' je rozšíření, které ukládá informace a parametry spojené s [[Special:MyLanguage/Help:Templates|šablonou wikitextu]] a zpřístupňuje je editačnímu rozhraní, které je může načíst a prezentovat v editoru šablon – to vše pomáhá uživatelům přidávat a upravovat šablony na stránky. Od dubna 2019 je funkce TemplateData součástí výchozího uživatelského prostředí pro všechny uživatele na všech wiki Wikimedie, pokud přidávají šablonu, včetně neregistrovaných uživatelů. Jak výchozí zdrojové, tak vizuální editory jej určitým způsobem zahrnují, stejně jako mnoho skriptů, nástrojů a gadgetů. Pokud máte vlastní wiki, budete muset nainstalovat {{ll|Extension:TemplateData}}. Přidání TemplateData do šablony pro použití tohoto rozšíření v podstatě spočívá ve vložení malého, jednoduchého bloku kódu [[w:JSON|JSON]] (vysvětleno níže) na stránku dokumentace šablony. Můžete to udělat ručně nebo pomocí editoru TemplateData, grafického uživatelského rozhraní, ke kterému máte přístup na stránkách šablony "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na wiki s nainstalovaným rozšířením TemplateData. JSON obsahuje seznam parametrů šablony a informace o těchto parametrech a o šabloně jako celku (podrobnosti viz níže). Šablony, které obsahují TemplateData, zobrazí tyto informace v uživatelském rozhraní, pokud uživatel přidá šablonu. V některých případech se změní chování editoru, když jej použijete k úpravě nebo vložení dané šablony. Což uživatelům výrazně usnadní provádění kroků potřebných k přidání dané šablony. == Historie == TemplateData byl původně vyvinut na začátku roku 2013 s ohledem na {{ll|VisualEditor}}, což bylo v té době ve fázi testování MediaWiki. VisualEditor je hlavní vizuální editační rozhraní pro wiki Wikimedie a TemplateData mu umožnilo mít užitečnější rozhraní při přidávání šablon. To bylo [[Special:MyLanguage/VisualEditor/Portal/TemplateData|okamžitě]] oficiálně podporováno VisualEditorem. Vzhledem k tomu, že VisualEditor byl rozšířen na různé hlavní wiki Wikimedie jako výchozí funkce od roku 2013 do roku 2016. TemplateData se také stala jejich součástí. V prosinci 2016 bylo rozhraní VisualEditor zpřístupněno pro úpravy zdrojového kódu jako funkce beta. Bylo nazýváno {{ll|2017 wikitext editor}}. To poprvé přineslo funkce TemplateData do úpravy zdroje. V březnu 2018 společnost [[User:Samwilson|Sam Wilson]] vyvinula rozšíření {{ll|Extension:TemplateWizard|nsp=0}}, rozšíření editoru GUI pro výchozí zdrojový editor Wikimedia, {{ll|WikiEditor}} (jinak známý jako editor wikitext 2010), jehož cílem je usnadnit proces přidávání šablon pomocí informací z TemplateData. V [[w:Wikipedia:Wikipedia Signpost/2019-04-30/Technology report|dubnu 2019]] byl TemplateWizard nastaven jako výchozí součást editoru wikitext 2010 na všech wiki Wikimedie. To znamenalo, že TemplateData se stala výchozí součástí vizuálního editoru i zdrojového editoru na wiki Wikimedie. == Přidání nebo úprava TemplateData == Chcete-li přidat nebo upravit TemplateData, nejprve přejděte na stránku šablony, která se nachází v "/Template:''Templatename''". {{anchor|Prior checks}} === Kontrola aktuálního stavu === Před přidáním nebo úpravou TemplateData zkontrolujte, zda má šablona '''podstránku dokumentace'''. Poté zkontrolujte, zda šablona '''již obsahuje TemplateData''' a pokud ano, zda se nachází na stránce šablony nebo na podstránce dokumentace. {{Note|1=Nezapomeňte zkontrolovat, zda existuje podstránka. Pokud přidáte TemplateData na hlavní stránku šablony, zatímco existuje podstránka s TemplateData, TemplateData na hlavní stránce přepíše data na podstránce.|2=warn}} ==== Dokumentace podstránek ==== Existují dva hlavní způsoby, jak šablony na většině wiki Wikimedie ukládají své poznámky k použití a další data, která by neměla být zahrnuta do samotné šablony, jako jsou kategorie, ve kterých by šablona měla být obsažena: * Velká většina šablon uchovává poznámky k použití a další data, která nepatří na samotnou stránku šablony, na podstránce dokumentace: "/Template:''Templatename''/doc". Na stránkách, jako je tato, šablona {{((}}{{ll|Template:Documentation|Documentation}}{{))}} [[Special:MyLanguage/Help:Transclusion|přenese]] veškerý obsah stránky /doc na stránku šablony, přičemž zdrojový kód šablony bude mnohem čistší. ** Na šablonách s podstránkami dokumentace budou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" následovat odkazy jako [zobrazit], [upravit], [historie] a [vyčistit]. * Několik stránek šablony si zachovalo tyto informace na hlavní stránce šablony. Na těchto stránkách to můžete najít tak, že mezi značkami {{tag|noinclude|open}} vyhledáte výskyt <code>{{Documentation|content=</code>. Různé wiki mohou toto vše prezentovat různě. Zřídkakdy mohou hlavní stránky šablon trvale obsahovat dokumentaci, i když jste zkontrolovali vše výše uvedené. Zde uživatel přidá vlastní název stránky /doc mezi "<code><nowiki>{{Documentation|</nowiki></code>" a "<code><nowiki>|content=</nowiki></code>" a poté přidá obsah za "<code><nowiki>|content=</nowiki></code>". Můžete se také podívat na upozornění v dolní části stránky podobné tomuto: "Výše uvedená dokumentace je převzata ze šablony:''Templatename''/doc". ==== Šablony bez podstránek dokumentace ==== Pokud šablona nemá podstránku dokumentace, vytvořte ji a přesuňte tam dokumentaci šablony (nebo její zástupný symbol). Poté můžete přidat TemplateData na podstránku dokumentace. ===== Vytvoření podstránky a přesun dokumentace ===== {{Note|1=Na mnoha wiki Wikimedie můžete vytvořit stránku pouze v případě, že jste tam byli registrovaným uživatelem několik dní a provedli jste minimální počet úprav.|2=info}} Chcete-li vytvořit podstránku dokumentace, klikněte na "{{int|vector-view-edit}}"/"{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony; vyhledejte značky {{tag|noinclude|open}} a jejich obsah (obvykle dole). Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= == Usage == Information about usage. == More example headings == More example contents [[Category:Example category]] [[Category:Example category 2]] }} </noinclude></syntaxhighlight> Můžete také zjistit, že již obsahuje TemplateData. Pokud ano, bude to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation|content= ... <templatedata> { "description": "", "params": { "1": { "label": "Example parameter", "description": "Example parameter description", "type": "string" } } } </templatedata> </noinclude></syntaxhighlight> Vyberte vše po "<code><nowiki>|content=</nowiki></code>" a před "{{tag|noinclude|close}}" a vystřihněte to do schránky nebo uložte do dočasného dokumentu. Smažte "<code><nowiki>|content=</nowiki></code>" a ponechte pouze následující: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} </noinclude></syntaxhighlight> Uložte stránku šablony. Chcete-li nyní vytvořit novou podstránku, podívejte se do adresního řádku prohlížeče a na konec adresy URL přidejte /doc. Stiskněte {{Key press|Enter}} a vyberte možnost vytvoření nové stránky. Pokud má tato wiki šablonu oznámení {{((}}{{ll|Template:Documentation_subpage|Documentation subpage}}{{))}}, přidejte ji na začátek nové stránky. Můžete také chtít přidat (pokud to daná wiki podporuje) další šablony, jako je odkaz {{((}}{{ll|Template:Purge_button|Purge button}}{{))}} nebo {{((}}{{ll|Template:Purge|Purge}}{{))}}. Další informace naleznete na stránce s [[m:Special:MyLanguage/Help:Template documentation|dokumentací k šablonám]]. Vložte text, který jste vystřihli nebo uložili do předchozího textu (pod šablonu oznámení, pokud existuje). Zabalte všechny kategorie do značek {{tag|includeonly|open}} tak, aby se vztahovaly pouze na hlavní stránku šablony: <syntaxhighlight lang="xml"> <includeonly> [[Category:Example category]] [[Category:Example category 2]] </includeonly> </syntaxhighlight> Mnoho wiki má šablonu <code><nowiki>{{Sandbox other}}</nowiki></code>. Tuto šablonu zde použijte, pokud je pravděpodobné, že šablona, kterou upravujete, existuje ve verzi izolovaného prostoru (umístěná v "Template:''Templatename''/sandbox"), aby se zabránilo použití kategorií na stránce izolovaného prostoru: <syntaxhighlight lang="xml"> <includeonly>{{sandbox other|| [[Category:Example category]] [[Category:Example category 2]] }}</includeonly> </syntaxhighlight> Nakonec stránku publikujte. Nyní můžete přidávat a upravovat TemplateData na podstránce dokumentace pomocí pokynů popsaných v odstavci [[#Methods|Metody]]. ===== Přidání a úprava TemplateData na hlavní stránce šablony ===== Pokud nemůžete vytvořit stránku /doc, můžete přidat a upravit TemplateData na hlavní stránce šablony podle pokynů v odstavci [[#Methods|Metody]]. Pokud má šablona podstránku dokumentace, zkontrolujte na hlavní stránce i na podstránce dokumentace přítomnost TemplateData (značka {{tag|templatedata|open}} následovaná polem ve složených závorkách: <code>{}</code>). Alternativně může tuto kontrolu provést za vás rozšíření TemplateData. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na kterékoli stránce. Pokud šablona již obsahuje TemplateData na kterékoli stránce, uvidíte v horní části stránky žluté upozornění, které říká: : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''/doc}}'' nebo : ''{{int|templatedata-exists-on-related-page|2=Šablona:'''Název šablony'''}}'' '''Pokud šablona obsahuje TemplateData na své podstránce dokumentace''' Pokud má šablona na své podstránce dokumentace TemplateData, je to stránka, kterou byste měli upravit. Můžete to udělat kliknutím na "[edit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" nahoře. Chcete-li přidat nebo upravit TemplateData, postupujte podle pokynů v [[#Methods|Metodách]]. '''Pokud má šablona na hlavní stránce TemplateData''' Pokud má šablona na hlavní stránce TemplateData, máte opět dvě možnosti: * Můžete se buď přesunout na jeho podstránku dokumentace. Toto je preferovaná možnost. * Nebo jej můžete upravit na hlavní stránce šablony. '''Přesun TemplateData na podstránku dokumentace''' Chcete-li to provést, klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na hlavní stránce šablony a vyhledejte značky {{tag|templatedata|open}}, které jsou součástí značek {{tag|noinclude|open}}. Mělo by to vypadat nějak takto: <syntaxhighlight lang="xml"> <noinclude> {{Documentation}} <templatedata> { "description": "", "params": { "1": { "label": "Příklad parametru", "description": "Příklad popisu parametru", "type": "string" } } } </templatedata> </noinclude> </syntaxhighlight> Z kódu vyjměte pouze značky {{tag|templatedata|open}} a jejich obsah a poté stránku uložte. Dále upravte podstránku dokumentace kliknutím na "[upravit]" umístěnou za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobně). Zadejte nadpis, například "TemplateData", a pod něj vložte TemplateData. Nyní můžete upravovat TemplateData na základě pokynů v [[#Methods|Metodách]]. '''Úprava dat šablony na hlavní stránce šablony''' Pokud si nepřejete přesunout data TemplateData na stránku /doc, můžete je upravit na hlavní stránce šablony. Viz [[#Methods|Metody]], jak upravit TemplateData. '''Pokud šablona ještě nemá TemplateData, ale má podstránku dokumentu''' Pokud šablona ještě nemá TemplateData, měli byste ji přidat na podstránku dokumentace. Udělejte to kliknutím na "[upravit]" umístěným za nadpisem "[[File:Test Template Info-Icon - Version (2).svg|50px]] '''Dokumentace šablony'''" (nebo podobným), nebo, pokud jste již na stránce /doc, kliknutím na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}} " nahoře. Zadejte nadpis, například "TemplateData", a poté je přidejte pod tento nadpis. Sekce [[#Methods|Metody]] vysvětluje, jak přidat TemplateData. {{anchor|Methods}} === Metody === {{anchor|TemplateData editor}} ==== Metoda editoru TemplateData ==== Toto je jednoduchý způsob, jak přidat nebo upravit TemplateData, doporučený pro méně zkušené uživatele. Editor TemplateData je grafické uživatelské rozhraní pro přidávání a úpravy TemplateData. Je součástí rozšíření TemplateData, které je dostupné na jakékoli stránce šablony (nebo podstránce dokumentace) kliknutím na "{{int|vector-view-edit}}" nebo na "{{int|visualeditor-ca-editsource}}". Po kliknutí na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" se nad oblastí úprav a názvem stránky zobrazí tlačítko "{{int|templatedata-editbutton}}". {{Clear}} [[{{lm|Manage template documentation button for TemplateData 2014|png|_}}|453px]] Kliknutím na toto tlačítko se dostanete do '''Editoru TemplateData'''. Pokud stránka, na které jste, již obsahuje TemplateData, automaticky se zde zobrazí. {{Clear}} [[{{lm|TemplateData GUI editor new|png|_}}|alt=Snímek obrazovky editačního nástroje TemplateData|600px|Nástroj pro úpravy TemplateData na stránce, která dosud neobsahuje TemplateData.]] Funkce ve výše uvedeném okně: * Horní položka volí jazyk textu rozhraní. Umožňuje zadávat textový obsah ve více jazycích, který se zobrazuje uživatelům na základě jejich nastavení v Předvolbách, '''není založen na jazyku wiki'''. Různé wiki mají zcela odlišné databáze šablon. Pokud neexistuje žádný jazyk TemplateData, rozhraní nabídne uživatelům pouze vlastní jazyk wiki, ale uživatelé mohou kliknout na "{{int|templatedata-modal-button-add-language}}" a přidat další vstupy. Kód jazyka je zobrazen v závorkách vedle parametrů, na které může být použit, jako jsou popisy a štítky. * Další položkou je popis šablony. Toto je popis šablony jako celku. Zobrazuje se uživatelům na mnoha místech v editorech šablon při přidávání šablony. Tento parametr a jeho účinky jsou popsány [[#Description|zde]]. * Třetí položka řídí formátování wikitextu šablony. Tento parametr určuje, jak bude wikitext rozvržen, když uživatel klikne na "{{int|templatedata-modal-button-apply}}", dva hlavní typy jsou <code>"inline"</code> (na jednom řádku) a <code>"block"</code> (na nových řádcích). Tento parametr a jeho účinky jsou popsány [[#Format|zde]]. : Pokud uživatel zvolí "{{int|templatedata-modal-format-custom}}", může zadat wikitext pod "{{int|templatedata-modal-title-templateformatstring}}" podle pravidel uvedených [[#Custom formats|zde]], aby vytvořil vlastní rozvržení pro šablonu, když uživatel klikne na "{{int|templatedata-modal-button-apply}}". * Čtvrtá položka konfiguruje parametry šablony. Pokud již byly parametry v TemplateData definovány, tato oblast je zobrazí v seznamu. Pokud zdrojový kód šablony specifikuje parametry, pro které neexistují TemplateData, můžete vidět tlačítko označené "{{int|templatedata-modal-table-param-importoption|2}}". Editor extrahuje tyto návrhy ze zdrojového kódu šablony vyhledáním <code><nowiki>{{{parametername}}}</nowiki></code> nebo <code><nowiki>{{{parametername|}}}</nowiki></code>. Kliknutím na "{{int|templatedata-modal-table-param-importoption|2}}" přidáte tyto parametry pomocí jejich názvů, jak je definováno ve zdrojovém kódu. Nahoře se také objeví zelené upozornění, například "{{int|Templatedata-modal-notice-import-numparams|2|''názvy parametrů''}}". * Ve spodní části okna vidíte tlačítko "{{int|templatedata-modal-button-addparam}}". To vám umožní ručně přidat parametr s vlastním názvem. Pokračujte dalším krokem kliknutím na některý z parametrů v seznamu. To vám umožní upravit informace o tomto parametru. [[{{lm|TemplateData GUI editor with two parameters|png|_}}|alt=Snímek obrazovky editoru TemplateData zobrazující přidávaný další parametr|600px]] Všechny tyto funkce a jejich účinky jsou popsány v části [[#Within a parameter's name|O názvu parametru]]. {{note|1=<div> * Editor TemplateData vám nedovolí změnit parametr "[[#Parameter name|{{int|Templatedata-modal-table-param-name}}]]" na prázdný. Parametry v TemplateData, které nějakým způsobem získávají prázdné řetězce jako názvy, nezpůsobí problémy v editoru wikitextu 2010 s TemplateWizard, ale ani VisualEditor ani editor wikitextu 2017 je vůbec nezobrazí. Toto je v editoru TemplateData jediné povinné pole. * Kliknutím na "{{int|templatedata-modal-button-delparam}}" smažete parametr a všechny jeho informace z TemplateData. Nemůžete je v TemplateData načíst nebo vrátit zpět, pokud poté nekliknete na "X". Jakékoli změny provedené po kliknutí na "{{int|templatedata-modal-button-apply}}" můžete vrátit zpět kliknutím na {{Key press|Ctrl|Z}}. * Ukončení editoru TemplateData po provedení změn vás vyzve k potvrzení, že chcete změny zrušit.</div> }} Po dokončení klikněte na "{{int|templatedata-modal-button-delparam}}". Tím se automaticky vloží TemplateData na konec stránky před značku {{tag|noinclude|close}}. Nebo, pokud již existuje, bude aktualizován o nové informace, aniž by se změnila jeho poloha. Text TemplateData bude také vybrán, když kliknete na "{{int|templatedata-modal-button-delparam}}". Editor TemplateData vytvoří parametr <code>"paramOrder"</code> ve spodní části TemplateData (nebo jej, pokud již existuje, aktualizuje). <code>"paramOrder"</code> obsahuje aktuální parametry TemplateData v pořadí, v jakém byly zobrazeny editorem TemplateData. <code>"paramOrder"</code> můžete změnit přetažením parametrů nahoru a dolů v editoru TemplateData pomocí tří vodorovných pruhů vlevo. <code>"paramOrder"</code> a jeho účinky jsou popsány [[#ParamOrder|zde]]. Poté klikněte na "{{int|templatedata-modal-button-saveparam}}" pro uložení revize stránky. ==== Ruční metoda ==== TemplateData můžete také přidat nebo upravit ručně. Struktura TemplateData je založena na standardu [[w:JSON|JSON]], ale nemusíte se učit JSON, abyste se zjistili, jak umístit TemplateData. TemplateData se řídí několika velmi jednoduchými pravidly a přijímá pouze několik desítek možných předdefinovaných parametrů a hodnot, obvykle ve formátu <code><nowiki>"parameter": "value"</nowiki></code>. '''Ruční přidávání TemplateData''' Na zřetel: * Pokud přidáváte TemplateData na podstránku dokumentace šablony ('''doporučeno'''), můžete je přidat kamkoli na stránku. Zkontrolujte, zda má Wikipedie ve vašem jazyce preferované umístění. Například na anglické Wikipedii jsou TemplateData obvykle v dolní části stránky s dokumentací. Na německé Wikipedii je obvykle nahoře. * Pokud přidáváte TemplateData na hlavní stránku šablony ('''nedoporučuje se'''; viz [[#Prior checks|Předchozí kontroly]]), musíte je umístit mezi tagy {{tag|noinclude}}. Klikněte na "{{int|vector-view-edit}}" nebo "{{int|visualeditor-ca-editsource}}" na příslušné stránce, poté se přesuňte na místo na stránce, kam chcete přidat TemplateData, a napište nadpis: "TemplateData". Mnoho wiki má šablonu {{tl|TemplateData header}}, která přidává krátké upozornění týkající se TemplateData. Pokud vaše wiki ano, přidejte ji za nadpis. Chcete-li začít přidávat TemplateData, zadejte otevírací a uzavírací značku {{tag|templatedata|open}} a pár složených závorek na nové řádky s prázdným řádkem: <syntaxhighlight lang="html"> <templatedata> { } </templatedata></syntaxhighlight> Dále přidejte odsazení na prázdný řádek mezi dvě složené závorky a začněte přidávat parametry. Podrobnosti o parametrech lze nalézt na [[#TemplateData parameters|Parametry TemplateData]]. Většina je volitelná. Některé jsou důrazně doporučeny. Parametry mohou být v libovolném pořadí, ale následuje pořadí, které nejlépe odpovídá dokumentaci TemplateData a usnadňuje editorům použití obsahu: <syntaxhighlight lang="html"> <templatedata> { "description": "", "format": "", "params": { "parameter1": { "aliases": ["",""] "label": "", "description": "", "type": "" } }, "paramOrder": [ "" ] } </templatedata></syntaxhighlight> Ujistěte se, že parametry, například v objektu <code>"params"</code>, zůstávají uvnitř tohoto objektu. Jinak při pokusu o uložení spustíte chybu "[[#Unexpected property|{{int|templatedata-invalid-unknown|''správně pojmenovat''}}]](properlyname)". {{anchor|Example}} '''Příklad''' Zde je několik příkladů TemplateData pro hypotetickou šablonu čištění. Taková šablona by zobrazila upozornění a zařadila stránku do kategorie s datem na základě zadaného měsíce a roku. Oznámení může také obsahovat odkaz na sekci diskusní stránky. TemplateData by vypadala nějak takto: <syntaxhighlight lang="javascript"> <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "date": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "reason": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "talk": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "date", "reason", "talk" ] } </templatedata> </syntaxhighlight> Odpovídající dokumentace TemplateData by se zobrazila takto: <templatedata> { "description": "Použijte tuto šablonu k označení, že článek potřebuje vyčistit.", "format": "inline", "params": { "datum": { "label": "Měsíc a rok", "description": "Měsíc a rok, kdy byla šablona přidána", "type": "string", "autovalue": "{{SUBST:CURRENTMONTHNAME}} {{SUBST:CURRENTYEAR}}", "example": "Leden 2013", "suggested": true }, "důvod": { "aliases": ["1"], "label": "Důvod", "description": "Důvod, proč článek potřebuje vyčistit", "type": "string" }, "diskuse": { "aliases": ["sekce diskuse"], "label": "Sekce diskusní stránky", "description": "Část diskusní stránky obsahující příslušnou diskusi", "type": "string" } }, "paramOrder": [ "datum", "důvod", "diskuse" ] } </templatedata> {{anchor|TemplateData parameters|Description and parameters}} == Parametry TemplateData == Všechny dostupné parametry TemplateData jsou uvedeny níže s popisem a s příkladem. Jsou také podrobněji uvedeny na stránce [[Special:MyLanguage/Extension:TemplateData#Format|Rozšíření:TemplateData#Format]]. {{note|1=<nowiki/> * Tyto informace jsou aktuální od listopadu 2021 a mohou se změnit, pokud jsou přidány nové parametry nebo rozhraní pro úpravy šablon získají aktualizace, které podporují stávající parametry nebo zacházejí s určitými parametry odlišně. * Wiki označení nebude fungovat v popisech ani na štítcích. Jsou to čistě prosté textové řetězce. * Nové řádky ("<code>\n</code>") v popisech, štítcích, příkladech nebo výchozích nastaveních se nezobrazí v žádném z hlavních editorů (TemplateWizard, VisualEditor nebo editor wikitextu 2017), i když se zobrazují v automaticky generované dokumentaci TemplateData. Ve vstupních formulářích jsou někde nahrazeny prázdným řetězcem a jinde mezerou. }} {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|description|Description|Template description}} |- ! description | Parametr <code>"description"</code> popisuje, co šablona dělá. Je volitelný, ale velice doporučený. '''Výsledky''' Na stránce dokumentace šablon se popis zobrazí jako prostý text pod podnadpisem "Data šablony pro [název šablony]". Ve všech hlavních editorech ({{ll|VisualEditor}}, {{ll|2017 wikitext editor}} a {{ll|Extension:WikiEditor|nsp=0}} s [[Special:MyLanguage/Help:Extension:TemplateWizard|TemplateWizard]]) se popis zobrazuje ve dvou hlavních případech: * pod názvem šablony v každém návrhu vyhledávání, když uživatel hledá šablonu * pod názvem šablony v editoru šablon, zatímco přidává hodnoty do parametrů v šabloně. V editoru wikitextu VisualEditor a 2017 bude popis zkrácen na přibližně 50 znaků pod každým návrhem vyhledávání, za ním následují "...", ale celý popis se zobrazí v hlavním okně editoru šablon. Oba jsou zobrazeny šedým textem. V hlavním okně editoru šablon jsou popisy delší než čtyři řádky (asi 540 znaků) vybaveny samostatným posuvníkem a jsou zobrazeny černým textem. '''Pokud není uvedeno''' Pokud parametr popisu neexistuje nebo není zadán, zobrazí se text "{{int|templatedata-doc-desc-empty}}" (no description) v dokumentaci TemplateData pod podtitulem "Data šablony pro [název šablony]" (template data for [template name]). Dodatek: * V aplikaci VisualEditoru a editoru wikitext 2017 se bude chovat stejně jako šablona, která nemá TemplateData. Místo popisu se zobrazí následující text: ::<code>{{int|quotation-marks|2="Šablona:''Název šablony''" zatím nemá popis, ale na stránce šablony mohou být nějaké informace.}}</code> * V editoru wikitext 2010 s TemplateWizard se zobrazí následující text, kde by byl popis (kromě návrhů vyhledávání): :<code>{{int|quotation-marks|{{int|templatewizard-no-description}}}}</code> :To se liší od dvou standardních popisů zástupných symbolů v případech, kdy TemplateData neexistují: :*<code>{{int|quotation-marks|2=Kvůli chybějícím TemplateData byly parametry pro tuto šablonu vygenerovány automaticky. Uvědomte si prosím, že nemusí být přesné.}}</code> :*<code>{{int|quotation-marks|2=Pro tuto šablonu nebylo možné určit žádné parametry kvůli absenci dokumentace TemplateData. Šablonu můžete vložit bez parametrů.}}</code> | <syntaxhighlight lang="javascript"> "description": "Šablona pro propojení na kategorii commons", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|format|Format}} |- ! format | Parametr <code>"format"</code> popisuje, jak by měl být rozložen wikitext šablony. To lze nastavit na standardní formáty <code>"inline"</code> a <code>"block"</code>. Uživatel také může zadat sadu wikitextových symbolů pro vytvoření vlastního formátu. Tyto symboly a některé příklady jsou uvedeny v sekci [[#Custom formats|Vlastní formáty]]. Tento parametr není vyžadován, ale doporučuje se. Výchozí chování, když tento parametr neexistuje, je in-line formátování a v dokumentaci TemplateData pod nadpisem tabulky se nezobrazí žádné odpovídající upozornění. '''Výsledky''' '''Inline:''' Pokud je parametr nastaven na <code>"inline"</code>, zobrazí šablona odpovídající upozornění o preferenci v dokumentaci TemplateData pod nadpisem tabulky "{{int|templatedata-modal-title-templateparams}}" (template parameters): :<code><nowiki>{{int|quotation-marks|[<translate>circles and pipes icon</translate>] {{int|templatedata-doc-format-inline}}}}</nowiki></code> Když je šablona vložena, rozloží svůj wikitext na jediný řádek bez mezer mezi prvky. Například: :<code><nowiki>{{Foo|bar=baz|qux=quux}}</nowiki></code> '''Blok:''' Pokud je parametr nastaven na <code>"block"</code>, šablona zobrazí v dokumentaci TemplateData následující upřednostňující oznámení: :<code><nowiki>{{int|quotation-marks|[<translate>stacked blocks and pipes icon</translate>] [[int|templatedata-doc-format-block}}}}</nowiki></code> Když je šablona vložena, rozdělí své parametry každý na nový řádek s mezerami mezi jednotlivými prvky. Například: <pre>{{Foo | bar = baz | qux = quux }}</pre> '''Vlastní formátování:''' Alternativně, pokud je parametr nastaven na vlastní řetězec wikitextu, podle pravidel uvedených v sekci [[#Custom formats|Vlastní formáty]], šablona zobrazí následující upozornění na předvolby v dokumentaci TemplateData: :<code><nowiki>"[<translate>cogwheel icon</translate>] {{int|templatedata-doc-format-custom}}"</nowiki></code> Po vložení šablona rozloží svůj wikitext podle daného wikitextu. | <syntaxhighlight lang="javascript"> "format": "inline" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|params|Params|Multiple parameters}} |- ! params | Objekt <code>"params"</code> obsahuje informace pro každý parametr šablony. Je vyžadován a jeho parametry si můžete prohlédnout v sekci [[#Within params|Parametry]]. Měl by obsahovat [[#Parameter name|název]] každého parametru, za nímž následuje sada sub-parametrů TemplateData uvedených v sekci [[#Within a parameter's name|Název parametru]]. Pokud existuje více parametrů, umístěte čárku ''mezi'' každý parametr objektu, ale žádný nepřidávejte za poslední složenou závorku (viz příklad). | <syntaxhighlight lang="javascript"> "params": { "parameter1": { ... // informace o parametrech }, // čárka zde "parameter2": { ... // informace o parametrech }, // a zde "parameter3": { ... // informace o parametrech } // ale tady ne } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|paramOrder|ParamOrder|Paramorder}} |- ! paramOrder | <code>"paramOrder"</code> je volitelný objekt, který po přidání do editoru šablon způsobí, že se parametry šablony zobrazí v určitém pořadí. '''Jak jej používat''' Přidejte parametr <code>"paramOrder"</code>, za ním dvojtečku, mezeru a otevřenou hranatou závorku a poté zadejte název každého z parametrů šablony v uvozovkách (<code>"</code>) v požadovaném pořadí, oddělený čárkami. Ukončete uzavřenou hranatou závorkou (vytvoření pole). Parametry nemusí být na nových řádcích (mohou být zapsány jako <code>"paramOrder": ["param1","param2","param3"]</code>), ale jejich umístění na nové řádky často pomáhá čitelnosti. Doporučujeme umístit <code>"paramOrder"</code> za <code>"params"</code>, jako to dělá editor TemplateData. Nezobrazuje se v dokumentaci TemplateData, ale jednoduše vynucuje pořadí parametrů. Budoucí editor si možná bude přát rychle prohlédnout detaily parametrů a upravit je, spíše než procházet kolem <code>"paramOrder"</code>, zvláště pokud existuje mnoho parametrů. Pokud se rozhodnete umístit paramOrder někam vedle konce TemplateData, ukončete jej čárkou. Musíte zahrnout každý parametr uvedený v TemplateData. Jinak se zobrazí chyba "[[#Required property|{{int|templatedata-invalid-missing|''správně pojmenovat''}}]] (properlyname)". '''Pokud není specifikováno''' Bez <code>"paramOrder"</code> se parametry šablony zobrazí v pořadí, v jakém je deklaruje zdrojový kód šablony. Pokud zdrojový kód obsahuje objekty uvnitř objektů, budou na prvním místě parametry ve vnějších objektech, následované vnitřními objekty. '''S jinými parametry''' V editoru wikitextu 2010 s TemplateWizard: * S <code>"[[#Required|required]]"</code> (požadované) parametry vždy zobrazí nahoře, bez ohledu na pořadí v <code>"paramOrder"</code>. * Parametry <code>"[[#Suggested|suggested]]"</code> (doporučené) se vždy zobrazí jako druhé, nad těmi <code>"optional"</code>. * <code>"[[#Deprecated|deprecated]]"</code> (zastaralé) parametry se v tomto editoru vůbec nezobrazí; viz popis <code>"deprecated"</code> pro více informací. * <code>"paramOrder"</code> bude vynucovat své pořadí pouze v těchto kategoriích (tj. všechny <code>"required"</code> parametry budou v pořadí specifikovaném <code>"paramOrder"</code> a všechny <code>"suggested"</code> parametry budou také, ale všechny <code>"suggested"</code> parametry se objeví pod všemi <code>"required"</code> parametry). V aplikaci VisualEditor a editoru wikitext 2017 vynucuje <code>"paramOrder"</code> své pořadí bez ohledu na stav všech parametrů. | <syntaxhighlight lang="javascript"> "paramOrder": [ "date", "reason", "talk" ] </syntaxhighlight> |- |} {{anchor|Within params}} === V rámci parametrů === {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 75%;"| Popis ! style="width: 20%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter name}} |- ! ''{{int|templatedata-modal-placeholder-paramkey}}'' | Jedinou položkou první úrovně objektu <code>params</code> je název parametru šablony. Například ve zdrojovém kódu šablony <code><nowiki>{{{date}}}</nowiki></code> označuje parametr a měl by být přidán pod <code>"params"</code> s názvem <code>"date"</code>. Můžete také vidět parametry s názvem <code><nowiki>{{{1}}}</nowiki></code> nebo jiné číslo (jehož název TemplateData by měl být například <code>"1"</code>). Tyto parametry se chovají tak, že když uživatel vloží šablonu, může vynechat název parametru a znaménko rovná se (tj. <code><nowiki>|value|</nowiki></code> místo <code><nowiki>|parametername=value|</nowiki></code>). Pokud existuje více nepojmenovaných parametrů, číslo identifikuje, na který [[Special:MyLanguage/Help:Templates#Anonymous parameters|nepojmenovaný parametr]] se odkazuje. Například v: :<code><nowiki>{{example template|value1|value2}}</nowiki></code> <code><nowiki>value1</nowiki></code> je hodnota parametru <code><nowiki>{{{1}}}</nowiki></code> a <code><nowiki>value2</nowiki></code> je hodnota parametru <code><nowiki>{{{2}}}</nowiki></code>. Nezapomeňte odpovídajícím způsobem popsat parametry TemplateData. Poznámka: Uživatel může přesto vynutit použití <code><nowiki>{{{2}}}</nowiki></code> bez <code><nowiki>{{{1}}}</nowiki></code> jednoduše vložením parametru s názvem "<code>2</code>" do editoru šablony nebo zadáním "<code><nowiki>|2=</nowiki></code>" do wikitextu. Nakonec si všimněte, že <code>"aliases"</code> vytváří alternativy k názvu parametru, které lze zaměnit a <code>"label"</code> nahrazuje název parametru '''v uživatelském rozhraní''' zadaným štítkem (pro situace, kdy název parametru není čitelný člověkem nebo není snadno pochopitelný). '''Jak jej používat''' Každý z těchto objektů "{{int|templatedata-modal-placeholder-paramkey}}" (parametr name) by měl obsahovat všechny informace o parametru ve formě více TemplateData parametrů. Jsou uvedeny v následující části [[#Within a parameter's name|O názvu parametrů]]. | <syntaxhighlight lang="javascript"> "1": { // název parametru ... // informace o parametru najdete zde } </syntaxhighlight> |- |} {{anchor|Within_a_parameter's_name}} ==== O názvu parametru ==== {| class="wikitable" ! style="width: 5%;"| Parametr ! style="width: 70%;"| Popis ! style="width: 25%;"| Příklad |- style="visibility:collapse" | colspan="3" | {{anchor|aliases|Aliases|Parameter aliases}} |- ! aliases | Volitelný parametr <code>"aliases"</code> umožňuje, aby parametr šablony měl více jmen. Můžete jej zkontrolovat tak, že přejdete do zdrojového kódu šablony a hledáte: :<code><nowiki>{{{parameter1|{{{parameter2}}}}}}</nowiki></code> nebo :<code><nowiki>{{{parameter1|{{{parameter2|}}}}}}</nowiki></code> To znamená, že pokud uživatel vloží některý z těchto parametrů s hodnotou, provede stejnou funkci. To doslova znamená "Hodnota parameter1. Pokud parametr1 neexistuje nebo nemá hodnotu, hodnota parameter2." V druhém případě to také znamená: "Pokud parameter2 neexistuje nebo nemá hodnotu, tak žádná hodnota". Chcete-li vložit parametr <code>"aliases"</code>, přidejte text <code>"aliases"</code> následovaný dvojtečkou, mezerou a otevřenou hranatou závorkou a poté zadejte název každého z aliasů parametru do uvozovek oddělený čárkami. Zakončete uzavřenou hranatou závorkou, čímž vytvoříte pole. | <syntaxhighlight lang="javascript"> "aliases": ["1", "talk", "talksection"], </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|inherits|Inherits|Similar parameters}} |- ! inherits | <code>"inherits"</code> je volitelný parametr, kdy by měl parametr zdědit všechna TemplateData jiného parametru. To pak může být potlačeno libovolnými parametry zadanými pro dědičný parametr. Chcete-li použít tento parametr, zadejte <code>"inherits" :</code> následovaný názvem jiného parametru šablony, například <code>"talk"</code> nebo <code>"1"</code>. Poté můžete podle potřeby zadat další konkrétní nastavení parametru, například <code>"label" : "A different label"</code>. První parametr zdědí všechny vlastnosti druhého parametru s výjimkou tohoto. | <syntaxhighlight lang="javascript"> "params": { "téma1": { "label": "Téma", "description": "Téma zmíněné na této disambiguační (nejednoznačné) stránce", "type": "string" }, "téma2": { "inherits": "téma1" }, "téma3": { "inherits": "téma1", "label" : "A different label" } } </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|label|Label}} |- ! label | Parametr <code>"label"</code> je pro člověka čitelný název parametru, který se zobrazí v editoru šablon. Štítek se vždy zobrazuje místo nezpracovaného názvu parametru, včetně případů, kdy je ve wikitextu použit alias. Tento parametr je sice volitelný, ale velmi se doporučuje. | <syntaxhighlight lang="javascript"> "label": "Měsíc a rok", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|Parameter description}} |- ! description | <code>"description"</code> je zde popisem parametru, nikoli šablony jako celku. Tento popis se zobrazí pod názvem parametru (dlouhé popisy budou zkráceny tlačítkem pro případné rozšíření). Je volitelný, ale velice doporučený. | <syntaxhighlight lang="javascript"> "description": "Měsíc a rok, kdy byla šablona vložena", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|type|Type}} |- ! type | Viz část [[#Type parameter|Parametr typu]]. | |- style="visibility:collapse" | colspan="3" | {{anchor|default|Default}} |- ! default | Některé parametry šablony mají výchozí hodnotu. Hodnota se použije, pokud není přepsána uživatelem. Položka <code>"default"</code> je volitelná položka. Je pouze dokumentační. Je určena ke sdělování této výchozí hodnoty uživateli. Hodnota se nemusí shodovat se skutečným výchozím nastavením (pokud existuje) a nemá '''žádný funkční účinek'''. (Neplést s <code>"autovalue"</code>, což '''je''' funkční parametr, který vyplňuje pole pro uživatele.) '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor 2017 a 2010 wikitext editor s TemplateWizard) se <code>"default"</code> text zobrazí jako šedý text ve vstupním poli jakéhokoli otevřeného parametru, pokud je prázdný, ve formátu <code>"Default: ''default text''"</code>. Kromě toho se zobrazí jako obyčejný černý text v [[#Parameter description|popisu parametru]] (když uživatel umístí kurzor myši na symbol "i"). V aplikaci VisualEditor a editoru wikitext 2017 to bude pod popisem parametru: "Pole je [[#Required|povinné]]" nebo "Pole je [[#Deprecated|zastaralé]]", pokud je uvedeno (editor wikitext 2010 tento text nezobrazuje), a nad "[[#Example|viz příklad]]", pokud je zadán (<code>"example"</code> se nezobrazí v popisu parametru v editoru wikitext 2010). V editoru wikitext 2010 s TemplateWizard se <code>"default"</code> text zobrazí hned za popisem parametru na stejném řádku za mezerou. Zobrazuje se ve stejném formátu jako ostatní editory (<code>"Default: ''default text''"</code>). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), je-li zadáno <code>"default"</code>, hodnota <code>"example"</code> se ve vstupním poli nezobrazí. | <syntaxhighlight lang="javascript"> "default": "Category:CommonsRoot", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|autovalue|Autovalue|Auto value}} |- ! autovalue | Parametru lze přiřadit <code>"autovalue"</code>. When a user adds the template to a page, this value will automatically appear in the input box. Například mnoho šablon čištění vyžaduje přidání data nastavením <code>"autovalue"</code> pro parametr <code>date</code> šablony na <code><nowiki>{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}</nowiki></code> se automaticky vyplní měsíc a rok, kdy byla šablona přidána. Tuto hodnotu může uživatel přepsat v editoru šablon. '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard), <code>"autovalue"</code> přepíše viditelné efekty <code>"url"</code> ve VisualEditoru a wikitext editoru 2017. Další informace viz [[#Type|popis pro <code>"type"</code>]]. | <syntaxhighlight lang="javascript"> "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}" </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|example|Example}} |- ! example | Parametr <code>"example"</code> je volitelný a pouze dokumentační. Jeho hodnota obsahuje příklad, který pomáhá uživateli šablony pochopit správný způsob vyplnění parametru (neplést s <code>"suggested"</code>; další informace naleznete v tomto záznamu). '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard). Tato vlastnost je zobrazena pod popisem parametru (a pod <code>"default"</code> textem, pokud je zadán). '''S dalšími parametry''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) se <code>"example"</code> (příklad) nezobrazí ve vstupním poli, pokud je zadán "default" (výchozí). | <syntaxhighlight lang="javascript"> "example": "January 2013", </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|required|Required}} |- ! required | Parametr <code>"required"</code> (povinné) lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Určuje, zda je vyplnění daného parametru pro šablonu povinné. '''Výsledky''' Tento stav má několik efektů v aplikaci VisualEditor a v {{ll|2017 wikitext editor}}: *zobrazí parametr automaticky, když uživatel vloží šablonu; *ve vstupním poli vpravo je zobrazena černá hvězdička; *pod popisem parametru se zobrazí šedý text s kurzívou "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; *pokud uživatel klepne pryč bez zadání hodnoty, způsobí, že vstupní pole svítí červeně; *pokud se uživatel pokusí vložit šablonu bez hodnoty do požadovaného parametru, zobrazí výzvu a zeptá se, zda si je jistý. Pokud toto potvrdí, vloží parametr s prázdnou hodnotou. Nezabrání ve vkládání šablony a nebude mít za následek viditelnou chybu samu o sobě (i když šablony nelze naprogramovat tak, aby zobrazovaly chybu, pokud není vyplněn požadovaný parametr). V {{ll|Extension:WikiEditor|nsp=0}} na stránce {{ll|Help:Extension:TemplateWizard|nsp=0}}, stejně jako v ostatních editorech se zobrazuje, při vložení šablony uživatelem, parametr automaticky, ale parametr nelze odstranit pomocí tohoto ani žádného jiného editoru. V popisu parametru také nezobrazuje "{{int|Visualeditor-dialog-transclusion-required-parameter-description}}"; spíše uvádí parametr na straně v části "{{int|templatewizard-parameters-required}}". Kromě toho se obvykle chová stejně jako v ostatních editorech, kromě toho, že se v řádku zobrazí, že vstup neodpovídá očekávanému formátu. '''S dalšími parametry''' V aplikaci VisualEditoru a editoru wikitext 2017 stav <code>"deprecated"</code> nepřepíše funkčnost tohoto parametru, ale ve wikitextovém editoru 2010 s TemplateWizardem ano. Další informace naleznete v popisu "<code>"deprecated"</code>" (zastaralé). | <syntaxhighlight lang="javascript"> "required": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggested|Suggested}} |- ! suggested | Parametr <code>"suggested"</code> lze nastavit na <code>true</code> nebo <code>false</code>. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Použijte <code>"suggested"</code> pro parametry, které nejsou povinné, ale důrazně doporučujeme uživatelům šablony poskytnout. Při vyplňování tohoto parametru se uživateli zobrazí tento návrh. '''Výsledky''' V aplikaci VisualEditor a {{ll|2017 wikitext editor}} způsobí, že se parametr automaticky zobrazí, když uživatel vloží šablonu. Pokud má parametr nastavenou automatickou hodnotu, bude tato také automaticky ve vstupním poli parametru. Nemá žádný další účinek a nezobrazuje žádný další text ani varování. V {{ll|Extension:WikiEditor|nsp=0}} s TemplateWizard neumisťuje parametr do šablony automaticky, ale místo toho způsobí, že bude uveden na straně v části "{{int|templatewizard-parameters-suggested}}". Uživatel pak může kliknout na "+" vedle parametru a přidat jej do šablony. '''S dalšími parametry''' Stav <code>"required"</code> (požadovaný) přepíše funkčnost tohoto stavu ve všech hlavních editorech (VisualEditor, editor wikitext 2017 a editor wikitext 2010). Také přepíše zobrazený stav <code>"suggested"</code> (doporučený) v dokumentaci TemplateData (zobrazí se <code>"required"</code> (povinný), pokud jsou <code>"required"</code> i "suggested" <code>true</code>). | <syntaxhighlight lang="javascript"> "suggested": true </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|deprecated|Deprecated}} |- ! deprecated | Nakonec je zde zastaralé <code>"deprecated"</code>, které může být nastaveno na <code>true</code>, <code>false</code> nebo řetězec popisující, co by uživatelé měli místo toho dělat. Pokud není specifikováno, je výchozí hodnota <code>false</code>. Toto je stav pro parametry, které by se již neměly používat, ale prozatím existují. Může to být proto, že použití šablony se přesouvá z jedné sady parametrů do druhé. '''Výsledky''' Účinek tohoto parametru v aplikaci VisualEditor a editoru wikitext 2017 je, že po vložení parametru se vedle štítku parametru zobrazí šedý vykřičník a pod informačním popisem parametru je šedou kurzívou zobrazen text "{{int|Visualeditor-dialog-transclusion-deprecated-parameter-description|''důvod ukončení podpory''}}". Nemá to vliv na funkčnost nebo použitelnost parametru ani nezobrazuje žádná další varování. Přestože může řetězec trvat, od ledna 2020 žádný z hlavních editorů (VisualEditor, editor wikitext 2017 nebo editor wikitext 2010) nezobrazí uživatelům obsah tohoto řetězce. Zadání řetězce má stejný účinek jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard nastavení této hodnoty jako <code>true</code> neumožňuje přidání nebo zobrazení parametru. '''S dalšími parametry''' Pokud nastavíte jak toto, tak <code>"suggested"</code> (navrhované) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako <code>"deprecated"</code> (zastaralé), ale v VisualEditor a editoru wikitext 2017 budou obě funkce zachovány. Parametr se automaticky zobrazí, když uživatel vloží šablonu, ale bude mít varování <code>"deprecated"</code> (zastaralá). Pokud nastavíte toto i <code>"required"</code> (povinné) jako <code>true</code>, stav parametru se v dokumentaci TemplateData zobrazí jako "deprecated" (zastaralé), ale ve VisualEditor a editoru wikitext 2017 bude mít stejnou funkcionalitu jako pouze <code>"required"</code> (vyžadováno). Parametr se automaticky zobrazí, když uživatel vloží šablonu a bude mít zobrazeno varování "deprecated" (požadovaná). To samé platí, pokud nastavíte <code>"deprecated"</code> (zastaralé), <code>"suggested"</code> (navrhované) a <code>"required"</code> (povinné) jako <code>true</code>. V editoru wikitext 2010 s TemplateWizard, <code>"deprecated"</code> (zastaralý) přepíše parametry <code>"required"</code> (povinné) a <code>"suggested"</code> (navrhované). |<syntaxhighlight lang="javascript"> "deprecated": "Místo toho použijte 'publicationDate'." </syntaxhighlight> |- style="visibility:collapse" | colspan="3" | {{anchor|suggestedvalues}} |- ! suggested values (navrhované hodnoty) | Vlastnost parametru <code>suggestedvalues</code> vám umožňuje definovat seznam hodnot parametrů, které se mají zobrazit uživatelům VisualEditoru v rozevíracím seznamu pro snadný výběr. To lze provést buď přímo v JSON nebo pomocí editoru TemplateData (bez nutnosti kódování). Můžete přidat navrhované hodnoty, které se mají zobrazit ve VisualEditoru pro parametry, jejichž typ je nastaven na jednu z následujících možností ([[Special:MyLanguage/Extension:TemplateData#Param object|reference]]): * content * line * string * number * unknown * unbalanced wikitext Jiné typy (file, page, template, user, date, boolean, URL) nejsou aktuálně podporovány, protože již mají speciální funkce ve VisualEditoru, jako je automatické dokončování, které by narušovalo rozevírací nabídku pro navrhované hodnoty ve VisualEditoru. '''Úpravy TemplateData jako JSON ve WikiTextu''' Chcete-li přidat navrhované hodnoty k libovolnému typu parametru, přidejte do parametru v JSON novou vlastnost "suggestedvalues". Atribut “suggestedvalues” musí být seznam řetězců. '''Úpravy TemplateData pomocí editoru TemplateData''' # Klikněte na "{{int|templatedata-editbutton}}". # Klikněte na název parametru, ke kterému chcete navrhované hodnoty přidat. # Pokud to ještě není provedeno, nastavte typ parametru na jeden z následujících: content, line, string, number, unknown, unbalanced wikitext. Objeví se nové vstupní pole "{{int|templatedata-modal-table-param-suggestedvalues}}". Pokud je parametr již nastaven na jeden z těchto typů, vstupní pole by již mělo být viditelné. # Zadejte navrhované hodnoty, včetně mezer a speciálních znaků, a stisknutím klávesy Enter přidejte hodnotu (hodnoty) do seznamu. '''Effects''' Jakmile budou hodnoty přidány do TemplateData, VisualEditor je zobrazí v rozbalovacím seznamu (rozbalovací seznam, do kterého mohou uživatelé také zadat vlastní hodnotu) pro typy parametrů uvedené výše. Uživatel vybere požadovanou hodnotu kliknutím na ni. Pokud je seznam hodnot dlouhý – například seznam států země – může uživatel do pole začít psát, načež bude seznam filtrován tak, aby zobrazoval pouze hodnoty obsahující zadaný text. Pro změnu zadané hodnoty musí uživatel pole jednoduše vymazat a znovu se zobrazí celý rozevírací seznam. Pokud uživatel potřebuje hodnotu, která není uvedena v seznamu (například "zpráva v láhvi"), může ji zadat ručně. |<syntaxhighlight lang="javascript"> "suggestedvalues": [ "Časopis", "Kniha", "Noviny", "Magazín" ] </syntaxhighlight> |- |} Poznámka: Pokud <code>"required"</code>, <code>"suggested"</code> ani <code>"deprecated"</code> nemají parametr nastavený jako <code>true</code>, jejich stav se v dokumentaci TemplateData zobrazí jako <code>"optional"</code>. Až budete hotovi, stiskněte "{{int|templatedata-modal-button-saveparam}}". Pokud jste udělali chyby, nedovolí vám to uložit (což je rušivé, ale znamená to, že nemůžete nic pokazit). Pokud narazíte na chyby, vysvětlete na [[Special:MyLanguage/VisualEditor/Feedback|stránce zpětné vazby]], co jste se snažili udělat, a my vám rádi pomůžeme. Všimněte si, že pokud zneužíváte hackovací šablonu k dynamickému generování TemplateData, nelze ji před uložením zkontrolovat na chyby. Všimněte si, že každá položka informací je uzavřena v uvozovkách (s výjimkou <code>true</code> a <code>false</code>) a je oddělena od dalšího bitu čárkou (pokud není poslední). {{anchor|Type parameter}} ==== Zadejte parametr ==== Parametr <code>"type"</code> má signalizovat editoru šablon povahu hodnoty parametru. V některých případech byly editory šablon naprogramovány tak, aby upravovaly uživatelské rozhraní pro určitý parametr podle hodnoty TemplateData, například tak, aby uživateli umožňoval zadávat pouze platné hodnoty, které odpovídají zadanému typu. Tento parametr nemá žádný funkční vliv na parametr šablony nebo jeho hodnotu. Pouze řídí, jak editor šablony vidí a zachází s parametrem v režimu úprav. '''Jak jej používat''' Používá se přidáním parametru <code>"type"</code>, za kterým následuje dvojtečka a mezera a poté se do uvozovek přidá jakákoli z hodnot uvedených v tabulce níže. Příklad: <syntaxhighlight lang="javascript"> "type": "string", </syntaxhighlight> '''Výsledky''' Od února 2020 má pouze 5 ze 13 hodnot typu viditelné výsledky ve VisualEditoru a editoru wikitextu 2017, zatímco 8 má viditelné výsledky v TemplateWizard. Účinky určitých hodnot se pravděpodobně změní, protože editory šablon získávají aktualizace, které je podporují. Jedno takové úsilí pro VisualEditor a editor wikitextu 2017 je sledováno v úkolu Phabricator [[phab:T55613|T55613]]. Podobná snaha přimět TemplateWizard, aby podporoval booleovskou hodnotu, je sledována v [[phab:T200664|T200664]]. Aktuálně známé účinky jsou následující. {| class="wikitable" |+ {{Anchor|Type parameter table}} ! style="width: 10%;"| Hodnota ! style="width: 90%;"| Popis |- style="visibility:collapse" | colspan="3" | {{anchor|unknown|Unknown}} |- ! unknown | Hodnota <code>"unknown"</code> je výchozí hodnotou typu, pokud není nastaven žádný typ. Lze ji také nastavit ručně zadáním <code>"type": "unknown"</code>. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"unknown"</code> žádné viditelné účinky ve srovnání se šablonou bez TemplateData. |- style="visibility:collapse" | colspan="3" | {{anchor|number|Number}} |- ! number | Hodnota <code>"number"</code> je určena pro číselné hodnoty, včetně záporných hodnot a desetinných míst. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"number"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> způsobí, že se ve vstupním poli na obou stranách zobrazí tlačítko "+" a "-", kterým lze zvýšit nebo snížit číselnou hodnotu ve vstupním poli a uživatel může zadávat čísla pouze do pole. Tlačítka mohou také snížit počet na záporný. '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"number"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"number"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|string|String}} |- ! string | Hodnota <code>"string"</code> je určena pro jakýkoli řetězec základního textu. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard) nemá <code>"string"</code> žádný viditelný efekt ve srovnání s <code>"unknown"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|line|Line}} |- ! line | Hodnota <code>"line"</code> je určena pro obsah, který má zůstat na jednom řádku. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 <code>"line"</code> brání vstupnímu poli parametru povolit nové řádky, které jsou obvykle v těchto editorech možné. * V editoru wikitext 2010 s TemplateWizard nemá <code>"line"</code> žádný viditelný efekt (vstupní pole ve výchozím nastavení neumožňuje v tomto editoru nové řádky). |- style="visibility:collapse" | colspan="3" | {{anchor|boolean|Boolean}} |- ! boolean | Hodnota 1 $ je určena pro hodnotu, která je buď pravdivá, nepravdivá nebo neznámá. To je v [[Special:MyLanguage/Extension:TemplateData#Param object|příručce]] zamýšleno tak, aby bylo reprezentováno "1", "0" nebo prázdnou hodnotou. '''Výsledky''' Od února 2020 žádný z hlavních editorů Wikimedia (VisualEditor, editor wikitextu 2017 nebo editor wikitextu 2010 s TemplateWizard) tuto hodnotu nevyužívá. Nemá žádné viditelné účinky. Ve VisualEditoru se objeví zaškrtávací políčko <code>autovalue:0</code>, které lze zapnout a vypnout. |- style="visibility:collapse" | colspan="3" | {{anchor|date|Date}} |- ! date | Hodnota <code>"date"</code> je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[Special:MyLanguage/Extension:TemplateData#Param object|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. '''Výsledky''' * V aplikaci VisualEditor a editoru wikitext 2017 nemá <code>"date"</code> žádný viditelný efekt. * Ve wikitextovém editoru pro rok 2010 s TemplateWizard <code>"date"</code> zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). '''S jinými parametry''' * V editoru wikitext 2010 s TemplateWizard, <code>"date"</code> přepíše efekty <code>"[[#Autovalue|autovalue]]"</code>. Hodnota <code>"autovalue"</code> nebude automaticky vložena do vstupního pole, pokud je typ parametru <code>"date"</code>. |- style="visibility:collapse" | colspan="3" | {{anchor|url|Url|URL}} |- ! url | Hodnota <code>"url"</code> je určena pro adresu URL, včetně internetového protokolu (např. "https://" nebo "//"). '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 <code>"url"</code> způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "https://", "ftp://" nebo "//"), za kterým následuje nějaký text. Tento druhý efekt je podobný jako u nastavení "<code>[[#Required|required]]</code>" (požadováno), ale uživatele nevaruje, pokud se pokusí vložit šablonu bez platné adresy URL. Vyskytuje se také s jakémkoli nastavením stavu (například "<code>[[#Suggested|suggested]]"</code>" nebo "<code>[[#Deprecated|deprecated]]</code>"). * V editoru wikitext 2010 s TemplateWizard nemá <code>"url"</code> žádný viditelný efekt. '''S dalšími parametry''' * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše <code>"autovalue"</code> viditelné efekty <code>"url"</code>. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-page-name|Wiki-page-name}} |- ! {{nowrap|wiki-page-name}} | Hodnota <code>"wiki-page-name"</code> je určena pro název stránky na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, editor wikitextu 2017 a editor wikitextu 2010 s TemplateWizard), <code>"wiki-page-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam stránek na wiki, například články na Wikipedii, které lze vybrat. Při hledání lze také definovat jmenný prostor. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiné stránky. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-file-name|Wiki-file-name}} |- ! {{nowrap|wiki-file-name}} | Hodnota <code>"wiki-file-name"</code> je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"wiki-file-name"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard <code>"wiki-file-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam souborů hostovaných lokálně i na Wikimedia Commons, které lze vybrat. Názvy souborů neobsahují předponu jmenného prostoru "File:". Rozbalovací nabídka také zobrazuje miniatury souborů. Nemá žádný další viditelný efekt a nebrání tomu, aby byl soubor vložen. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-template-name|Wiki-template-name}} |- ! {{nowrap|wiki-template-name}} | Hodnota <code>"wiki-template-name"</code> je určena pro název šablony. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a wikitext editor 2010 s TemplateWizard) <code>"wiki-template-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam šablon, které lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. |- style="visibility:collapse" | colspan="3" | {{anchor|wiki-user-name|Wiki-user-name}} |- ! {{nowrap|wiki-user-name}} | Hodnota <code>"wiki-user-name"</code> je určena pro uživatelské jméno na wiki. '''Výsledky''' Ve všech hlavních editorech (VisualEditor, 2017 wikitext editor a 2010 wikitext editor s TemplateWizard) <code>"wiki-user-name"</code> způsobí, že vstupní pole parametrů zobrazí rozbalovací nabídku návrhů obsahující seznam skutečných uživatelských jmen, která lze vybrat. V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. Nemá žádný další viditelný efekt a nezabraňuje zadávání jiného uživatele. |- style="visibility:collapse" | colspan="3" | {{anchor|content|Content}} |- ! content | Hodnota <code>"content"</code> je určena pro wikitext obsahu stránky, například pro odkazy, obrázky nebo formátování textu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"content"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"content"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |- style="visibility:collapse" | colspan="3" | {{anchor|unbalanced-wikitext|Unbalanced-wikitext}} |- ! {{nowrap|unbalanced-wikitext}} | Hodnota <code>"unbalanced-wikitext"</code> je určena pro wikitext, který nemůže stát samostatně, tj. Postrádá otevírací nebo uzavírací značku nebo odkazuje na jiné části wikitextu. '''Výsledky''' * V aplikaci VisualEditoru a editoru wikitext 2017 nemá <code>"unbalanced-wikitext"</code> žádný viditelný efekt. * V editoru wikitext 2010 s TemplateWizard, <code>"unbalanced-wikitext"</code> dělá vstupní pole parametrů o jeden řádek vyšší a umožňuje nové řádky, které běžná vstupní pole v editoru wikitext 2010 nedělají. |} {{anchor|Custom formats}} === Vlastní formáty === Při úpravě hodnoty <code>"format"</code> vytvoříte vlastní formáty zadáním sady symbolů wikitextu pomocí některých předdefinovaných pravidel. * <code><nowiki>{{</nowiki></code> - začátek šablony * <code><nowiki>_</nowiki></code> - obsah (např. řetězec, celé číslo nebo parametr). Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například <code><nowiki>_______</nowiki></code>. Není-li této délky dosaženo, vyplní zbývající znaky mezerami. To lze použít k zarovnání všech znamének rovná se na konkrétní pozici za parametr (pokud se použije s <code>\n</code> pro nové řádky). * <code><nowiki>|</nowiki></code> - potrubí, trubka, svislá čára, svislítko (odděluje parametry) * <code><nowiki>=</nowiki></code> - znaménko rovná se (předchází hodnotě parametru) * <code>\n</code> nebo stisknutí klávesy Enter - nový řádek (ve vstupním poli se zobrazí jako <code>↵</code>) * <code><nowiki> </nowiki></code> - mezera (lze použít s <code>\n</code> k odsazení nových řádků) * <code><nowiki>}}</nowiki></code> - konec šablony Wikitext by měl splňovat minimálně <code><nowiki>{{_|_=_}}</nowiki></code>, jinak bude neplatný formátovací řetězec. {| class="wikitable" |+ Příklady formátů, které můžete použít ! style="width:25%" | Úkol ! Formát řetězce ! Výstup |- | Inline formátování | <code style="white-space: pre-wrap;"><nowiki>{{_|_=_}}</nowiki></code> <br/> <code>inline</code> | <pre>{{Foo|bar=baz|qux=quux}}{{Bar}}</pre> |- | Blokové formátování | <code style="white-space: pre-wrap;"><nowiki>{{_\n| _ = _\n}}</nowiki></code> <br/> <code>block</code> | <pre>{{Foo | bar = baz | qux = quux }}{{Bar}}</pre> |- | Žádná mezera před názvem parametru, každá šablona na samostatném řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_\n|_ = _\n}}\n</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }} {{Bar}}</pre> |- | Odsazení každého parametru | <code style="white-space: pre-wrap;"><nowiki>{{_\n |_ = _\n}}</nowiki></code> | <pre>{{Foo |bar = baz |qux = quux }}{{Bar}}</pre> |- | Zarovnání všech názvů parametrů s danou délkou | <code style="white-space: pre-wrap;"><nowiki>{{_\n|_______________ = _\n}}\n</nowiki></code> || <pre>{{Foo |bar = baz |qux = quux |veryverylongparameter = bat }} {{Bar}}</pre> |- | Znaky svislítka na konci předchozího řádku | <code style="white-space: pre-wrap;"><nowiki>{{_|\n _______________ = _}}</nowiki></code> | <pre>{{Foo| bar = baz| qux = quux}}{{Bar}}</pre> |- | Vložený styl s více mezerami musí být na začátku řádku | <code style="white-space: pre-wrap;"><nowiki>\n{{_ | _ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar }}</pre> |- | Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu | <code style="white-space: pre-wrap;"><nowiki>\n{{_ |\n _______________ = _}}</nowiki></code> | <pre>{{Foo | bar = baz | qux = quux}} {{Bar}}</pre> |} {{anchor|Blank boilerplate}} === Prázdná předloha === Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "params": { "1": { "label": "", "description": "", "type": "" }, "2": { "label": "", "description": "", "type": "" } } } </templatedata> </syntaxhighlight> == Chyby == === {{int|templatedata-invalid-parse}} / Špatný formát JSON === K těmto chybám dochází při ukládání TemplateData, obvykle ručně upravovaných, s neplatným kódem JSON (duplicitní klíče/parametry, koncové nebo chybějící čárky atd.) ve VisualEditoru nebo v editoru wikitextu 2017. "{{int|templatedata-invalid-parse}}" se objeví ve VisualEditoru a editoru wikitextu 2017. Při úpravách v editoru GUI TemplateData se zobrazí "Bad JSON format" (špatný formát JSON). Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například [[#jsonlint|JSONLint]], který zvýrazní chyby a pomůže je opravit. Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ({{phab|T128029}}). Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "{{int|internalerror}}". Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). {{anchor|Required property}} === Požadovaná vlastnost "paramOrder(''number'')" nebyla nalezena. === K této chybě dochází, pokud uvedete v <code>"[[#Params|params]]"</code> parametr, který není uveden v <code>"[[#ParamOrder|paramOrder]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "reason": { ... }, "talk": { ... // <-- Tento parametr není uveden v "paramOrder", ale měl by být. } }, "paramOrder": [ "date", "reason" ] // Chyba: Požadovaná vlastnost "paramOrder[2]" nebyla nalezena. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"params"</code> jsou uvedeny v <code>"paramOrder"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Neplatná hodnota pro vlastnost "paramOrder(''number'')". === K této chybě dochází, pokud uvedete v <code>"[[#ParamOrder|paramOrder]]"</code> parametr, který není uveden v <code>"[[#Params|params]]"</code>. Číslo v hranatých závorkách odkazuje na chybějící parametr v <code>"paramOrder"</code>. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože <code>"paramOrder"</code> je pole. 0 je první, 1 je druhý atd. <syntaxhighlight lang="javascript"> "params": { "date": { ... }, "talk": { ... } }, "paramOrder": [ "date", "reason", // <-- Tento parametr není uveden v "params", ale měl by být. "talk" ] // Chyba: Neplatná hodnota vlastnosti "paramOrder[1]". </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že všechny parametry uvedené v <code>"paramOrder"</code> jsou uvedeny v <code>"params"</code>. Případně můžete tuto chybu odstranit odebráním objektu <code>"paramOrder"</code>. === Očekává se, že vlastnost "params.''parametername''.required" bude typu "boolean". === K této chybě dochází, pokud uvozovky umístíte kolem hodnoty buď <code>"[[#Required|required]]"</code> nebo <code>"[[#Suggested|suggested]]"</code>. <syntaxhighlight lang="javascript"> "suggested": "true" // <-- Tyto uvozovky by zde neměly být. </syntaxhighlight> Toto jsou booleovské hodnoty, nikoli řetězce, proto nevyžadují žádné uvozovky. Chcete-li to vyřešit, odeberte uvozovky kolem hodnot <code>true</code> nebo <code>false</code> pro tyto parametry. === Očekává se, že "format" vlastnosti bude ... === Pokud parametr <code>"[[#Format|format]]"</code> existuje, ale jeho hodnota není <code>"inline"</code>, <code>"block"</code> nebo platný řetězec formátu, zobrazí se chybová zpráva: "{{int|Templatedata-invalid-format|format}}". <syntaxhighlight lang="javascript"> "format": "notinline" // Chyba: Předpokládá se, že vlastnost "format" bude "inline", "block" nebo platný formátovací řetězec. </syntaxhighlight> Chcete-li to vyřešit, ujistěte se, že hodnota po <code>"format": </code> se rovná <code>"inline"</code> nebo <code>"block"</code> a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně <code><nowiki>{{_|_=_}}</nowiki></code> a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[#Custom formats|Vlastní formáty]] pro syntaxi vlastních formátů. Případně můžete tuto chybu odstranit odebráním objektu <code>"format"</code>. {{anchor|Unexpected property}} === Neočekávaná vlastnost "''parametername''". === K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. To je pravděpodobně způsobeno pravopisnými chybami. <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "params": { "1": { "label": "", "descriptino": "", // <-- pravopisná chyba "type": "" } } } </templatedata> </syntaxhighlight> Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. Například byste mohli napsat parametr <code>"[[#Label|label]]"</code> pod kořenový objekt TemplateData namísto uvnitř <code>"[[#Params|params]]"</code>: <syntaxhighlight lang="javascript"> <templatedata> { "description": "", "format": "inline", "label": "", // <-- špatně umístěný parametr "params": { "1": { // ↓ it should be in here "description": "", "type": "" } } } </templatedata> </syntaxhighlight> Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř <code>"params"</code>, uvidíte jeho název za "params.''parametername''." v chybě. Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou umístěny správně. Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují. V sekci [[#TemplateData parameters|Parametry TemplateData]] můžete zkontrolovat, které parametry pro objekt existují. === Požadovaná vlastnost "params" nebyla nalezena. === K této chybě dochází, pokud v TemplateData není žádný objekt <code>"[[#Params|params]]"</code>. Toto je nezbytný objekt, protože obsahuje všechny podrobnosti o každém parametru, takže tuto chybu opravte, ujistěte se, že je přidána a že nedochází k pravopisným chybám. Viz [[#Params|část výše]] o tom, jak přidat parametr <code>"params"</code>. {{anchor|Limitations and questions}} === Omezení a zpětná vazba === * '''Chybějící funkce''' – TemplateData je příkladem nástroje, který byl zpřístupněn s několika funkcemi, v naději, že by uživatelé pomohli řídit vývoj funkcí, které požadovali. Pokud chcete požádat o nové funkce pro TemplateData, dejte nám prosím vědět na [https://phabricator.wikimedia.org/maniphest/task/edit/form/102/?projects=MediaWiki-extensions-TemplateData]. * '''Prodlevy při zobrazování v šablonách''' – Po přidání TemplateData do šablony by měla být metadata viditelná okamžitě, jakmile se šablona otevře ve vizuálním editoru. Je však možné, že to bude trvat několik hodin, než se metadata zobrazí. Aktualizace můžete vynutit provedením nulové úpravy samotné stránky šablony (nikoli podstránky dokumentace). Chcete-li provést nulovou úpravu, otevřete stránku šablony pro úpravy a stránku uložte bez jakékoli změny a bez přidání souhrnu úprav. * '''Aktuální problémy''' – Seznam aktuálních chyb a požadavků na funkce je k dispozici [[phabricator:maniphest/query/qXa9bowMj3nX/#R|v nástroji pro sledování chyb Wikimedie]]. {{anchor|Other tools}} == Další nástroje == ; {{ll|Help:Extension:TemplateWizard}}: Dialogové okno panelu nástrojů pro zadávání wikitextů šablony pomocí formuláře vytvořeného z TemplateData. ; [http://tools.wikimedia.pl/~mlazowik/templatedata/ TemplateData Wizard]: Nástroj, který generuje TemplateData prostřednictvím interaktivního rozhraní. ; [[w:User:Salix alba/TDSkell|Skeleton TemplateData generator]]: Nástroj, který načte zdrojový wikikód šablony, pokusí se najít všechny použité parametry a vytvoří kostru dokumentu s uvedenými parametry. ; {{anchor|jsonlint}}[https://jsonlint.com/ JSONLint]: Nástroj, který vám umožní ověřit ručně napsaný JSON, který pomůže najít chyby v syntaxi. * [{{fullurl:Special:PagesWithProp|propname=templatedata&propname-other=}} Seznam všech šablon s TemplateData] na této wiki * V [[w:de:Template:TemplateData|šabloně dewiki TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data * https://query.wikidata.org/ a [[d:Wikidata:SPARQL query service/Query Helper|Query Helper]] b5kfwxst0fsnnyna23ew0mf47xq7jl4 Extension:Highlight Links in Category 102 567009 5386718 5345441 2022-07-28T18:25:32Z RheingoldRiver 4061934 update wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} <translate> <!--T:1--> '''Highlight Links in Category''' is an extension that adds a CSS class to links pointing to members of a category. <!--T:2--> For reporting an issue or a bug, please use [<tvar name=url>https://phabricator.miraheze.org</tvar> Miraheze Phabricator]. ==Installation== <!--T:3--> </translate> {{ExtensionInstall|HighlightLinksInCategory|registration=required}} <translate> ==Configuration parameters== <!--T:4--> </translate> ; $wgHighlightLinksInCategory : <translate><!--T:5--> This global is an array that configures which categories get an added CSS class. The keys are the Category names, which must include underscores instead of spaces. Do not include the Category: namespace. The value for each key is the CSS class you would like to add to that category. For example:</translate> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} <translate> <!--T:6--> If you want add more than one class, separate the class names with spaces, like </translate> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} <translate> <!--T:7--> You can add as many of these as you want, but from a UX perspective it's probably not awesome to add 500 different style links. </translate> <translate><!--T:8--> If <tvar name=1>$wgHighlightLinksInCategory</tvar> is not set or empty, this extension will do nothing.</translate> <translate><!--T:26--> If you're running a wiki farm and need to turn it off on some wikis, set <tvar name=1><syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight></tvar>; using <tvar name=2>{{phpi|false}}</tvar> could lead to incorrect behavior.</translate> <translate> ==Styling== <!--T:9--> <!--T:10--> Simply add the styles you need for these links to MediaWiki:Common.css on your wiki. For example: </translate> {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} <translate> <!--T:11--> If you want one category to override another, you'll have to specify it with CSS. </translate> {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} <translate> <!--T:12--> Or alternatively, you could have defined the original <code>a.templates</code> rule as <code>a.templates:not(.disambig)</code> instead. <!--T:13--> There's also the link icon approach: </translate> {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} <translate> ==User Toggles== <!--T:14--> <!--T:15--> An easy way to set up toggling this highlighting on or off is to make a [[Extension:Gadgets|Gadget]] with CSS in it. Yes, this is a personalization extension that outsources the personalization part to other extensions; I can still sleep at night. ==How this works== <!--T:16--> </translate> <translate><!--T:17--> Right after MediaWiki determines which linked pages exist (to make redlinks), it runs the <code>GetLinkColours</code> hook (see LinkHolderArray.php).</translate> <translate><!--T:23--> As we have a list of all of the page ids which are linked on that page, we can run one database query to see which of these links are in the set of categories we want to highlight.</translate> <translate><!--T:24--> Because the query only happens on an index of the <code>categorylinks</code> table, it's reasonably fast.</translate> <translate><!--T:25--> Then CSS classes are assigned based on the result, using the configuration values the user sets in <code>$wgHighlightLinksInCategory</code>.</translate> <translate> <!--T:18--> Explaining how CSS works is outside the scope of this document. ==Known issues== <!--T:19--> <!--T:20--> * CSS styles are not added in Flow, because it doesn't appear to call the GetLinkColors hook there. ==See also== <!--T:21--> <!--T:22--> * [[:Category:LinkEnd extensions]] - which customize links in other ways </translate> {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] irsr14g7sr1f65y079nfrwnicyfk864 Template:InstallationNav/hu 10 568271 5387200 5384787 2022-07-28T21:17:30Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=Testreszabás}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] kqnsrzk2frt7uwcoj1sqknmzg1pcuen Manual:Installing third-party tools/pl 100 596604 5387825 5377084 2022-07-29T09:29:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/pl]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/pl]] b6zf9uu302z9prb61dalq114ribkgg6 Translations:Manual:Installation guide/11/it 1198 604534 5387286 5293817 2022-07-28T21:56:18Z Baris6161TURK 17188421 wikitext text/x-wiki Anteprima dell'immagine richiede programmi aggiuntivi. $1 (richiesto da VisualEditor) e altri servizi hanno i propri requisiti. j0lr6mtktvzrdc733nlohncx9rtdin8 Manual:Installation guide/bg 100 618722 5386636 5381072 2022-07-28T17:14:22Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/bg]] e2a2on5tcbdbrr76dkt1sl4d9bdwacp 5386687 5386636 2022-07-28T17:24:19Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/bg]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Translations:Manual:Installation guide/11/pl 1198 622325 5387287 4700850 2022-07-28T21:56:29Z Baris6161TURK 17188421 wikitext text/x-wiki Tworzenie miniaturek wymaga dodatkowych programów. $1 (wymagany przez VisualEditor) i inne usługi mają własne wymagania. jpvr7ktn8ksazqr1lrd6neufbp89lqi MediaWiki Language Extension Bundle/releases 0 622963 5387697 5230241 2022-07-29T05:52:04Z KartikMistry 550774 2022.07 release notes. wikitext text/x-wiki ==== Latest release ==== ===== 2022.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.07.tar.bz2 * sha256sum: 3e8f48643403946fdb55f3ff086ed1e702c0367f3282c9dc78eb6785964c0809 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/JTU47XWODZPN6HGTEKO7MVI7YDHZ5LLS/ Announcement] * [https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2022.04 Release notes] * Compatible with '''MediaWiki 1.37.2''' or later and requires '''PHP 7.3.19''' or above. ====== LocalisationUpdate ====== * LocalisationUpdate extension is removed from MediaWiki Language Extension Bundle. Please [https://lists.wikimedia.org/hyperkitty/list/mediawiki-l@lists.wikimedia.org/message/BCDH3PUKWYGF5AZFCJI6ZPACHCQA6IT7/ read the announcement]. ====== Translate ====== * Support for MediaWiki 1.36 has been dropped. * Avoid recreation of translation pages on bulk deletion of pages, for example when using the Nuke extension. ({{phab|T291724}}, {{gerrit|799383}}) * Fix "Impossible to mark pages for translation using the mobile site". ({{phab|T311631}}, {{gerrit|809970}}) ===== 2022.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.04.tar.bz2 * sha256sum: a5ef23339730ec80422d60c31ece1fb696397f6be90fbe9fbf703cc9ddbf5527 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/JTU47XWODZPN6HGTEKO7MVI7YDHZ5LLS/ Announcement] * [https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2022.04 Release notes] * Compatible with '''MediaWiki >= 1.36.4 < 1.37''' or '''MediaWiki >= 1.37.2''' and requires '''PHP 7.3.19''' or above. ====== LocalisationUpdate ====== * We're planning to sunset the LocalisationUpdate extension from version 2022.07. Please [https://lists.wikimedia.org/hyperkitty/list/mediawiki-l@lists.wikimedia.org/message/BCDH3PUKWYGF5AZFCJI6ZPACHCQA6IT7/ read the announcement]. ====== Translate ====== * If you are using [[Help:Extension:Translate/Translation memories|translation memory]] with ElasticSearch backend, we recommend rebuilding the translation memory index. This can be done by running <code>php <path_to_mediawiki_core>/extensions/Translate/scripts/ttmserver-export.php</code> ==== Previous releases ==== ===== 2022.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.01.tar.bz2 * sha256sum: 0cb434980b399f7bac42a92c9f171b6c9041cb998e3b2b0fcf16daf58c43fe61 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] *[https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/BA34V5I7OIAZRLA2RDWCKXYT4Q4AF4Q2/ Announcement] * [https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2022.01 Release notes] * Compatible with '''MediaWiki 1.36''' or above and requires '''PHP 7.3.19''' or above. ====== Translate ====== * Breaking change: Remove backward compatibility for MW <= 1.35 ({{phab|T298788}}, {{gerrit|752166}}) ====== UniversalLanguageSelector ====== * Remove backward compatibility for MW <= 1.35 ===== 2021.12 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.12.tar.bz2 * sha256sum: 61c9c7a700c9f98c6b3c59adf2f0fc7d1919fc87e0c3584308d313536dd81f37 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.12.tar.bz2.sha256sum <nowiki>[1]</nowiki>] *[https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/57KMSHMFOAUOI3ZI2SVMUSVK6ZCHHU4C/ Announcement and Release Notes] * Compatible with '''MediaWiki 1.35.3''' or above and requires '''PHP 7.3.19''' or above. ====== Translate ====== * Fix broken SpecialMovePage on MediaWiki 1.35 ([[phab:T294605|Phab:T296450]]) ---- ===== 2021.11 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.11.tar.bz2 *sha256sum: 07e697bfed3ef153c421a760221e93f0e3fef70a8db54defd59c4608b4d56352 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.11.tar.bz2.sha256sum <nowiki>[1]</nowiki>] *[https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/ANOIEJQ5GMBCRYDHTRFTZVX32H44IXGD/ Announcement and Release Notes] * Compatible with '''MediaWiki 1.35.3''' or above and requires '''PHP 7.3.19''' or above. ====== Translate ====== * Fix compatibility with MediaWiki <= 1.37 when VisualEditor is installed. ([[phab:T294605|Phab:T294605]]) ---- ===== 2021.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.10.tar.bz2 * sha256sum: ce923b2a661e3a97ec8f0add9eb9369637e02cbb70a47b80a1e50f3e8c0001d6 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/7BIYSQZ5XXKC23ATRLJXGWZ356XVHVCV/ Announcement and Release Notes] * Compatible with '''MediaWiki 1.35.3''' or above and requires '''PHP 7.3.19''' or above. ====== Translate ====== * '''SECURITY''': Allow revdel-related actions in translatable pages ([[gerrit:c/mediawiki/extensions/Translate/+/725385|Gerrit]]) * '''BREAKING CHANGES''' ** Export script: remove <code>--hours</code> ([[gerrit:c/mediawiki/extensions/Translate/+/705677|Gerrit]]) ** Remove translation aids customization (Hook: <code>TranslateTranslationAids</code>) ([[gerrit:c/mediawiki/extensions/Translate/+/715939|Gerrit]]) ** Remove <code>$wgTranslateDelayedMessageIndexRebuild</code> ([[gerrit:c/mediawiki/extensions/Translate/+/719062|Gerrit]]) ** Remove <code>getConfiguration</code> and <code>getFFS</code> from MessageGroup ([[gerrit:c/mediawiki/extensions/Translate/+/715946|Gerrit]]) ** Group configuration: Rename validator keymatch option to include ([[gerrit:c/mediawiki/extensions/Translate/+/730035|Gerrit]]) ====== UniversalLanguageSelector ====== * '''SECURITY''': Language name search: Avoid searching for very long search keys ([[gerrit:c/mediawiki/extensions/UniversalLanguageSelector/+/732274|Gerrit]], [[phab:T293749|Phabricator]]) * Improve support for the new Vector Skin. * Remove configuration <code>ULSEnableAnon</code> ([[gerrit:c/mediawiki/extensions/UniversalLanguageSelector/+/707229|Gerrit]]) * Add support for multiple ULS buttons ([[gerrit:c/mediawiki/extensions/UniversalLanguageSelector/+/719325|Gerrit]]) ---- ===== 2021.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.07.tar.bz2 * sha256sum: f7cd8113c095375be51464429dff04c8fa5bb88bc22ba3d780bf5698668e52c5 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/7YEY5ICH43CFY5OOWEIS3XYHMZYGS343/ Announcement and Release Notes] * Compatible with MediaWiki 1.35 or above and requires PHP 7.2 or above. ====== Translate ====== * '''SECURITY''': Enhance validation and logging for AggregateGroups API deletions ({{phab|T282932}}) * '''BREAKING CHANGES''' ** Translate extension now requires MediaWiki 1.35 or above. ** Remove TranslateMessageGroupPathVariables hook ({{gerrit|701678}}) ** Remove Validator and LegacyValidatorAdapter ({{gerrit|685438}}) '''Configuration variable changes''' To address voice and tone issues in the Translate extension ({{phab|T277965}}) the following configuration variable names have been renamed: * <code>TranslateBlacklist</code> → <code>TranslateDisabledTargetLanguages</code> * <code>TranslateAuthorBlacklist</code> → <code>TranslateAuthorExclusionList</code> * <code>TranslateCheckBlacklist</code> → <code>TranslateValidationExclusionFile</code> ''The old variables will be supported for MLEB 2021.07 release but removed in the MLEB 2021.10 release.'' If you have defined [[Help:Extension:Translate/Group_configuration|message groups]] defined with <code>LANGUAGE</code> attributes, <code>whitelist/blacklist</code> have been changed to <code>include/exclude</code> ====== UniversalLanguageSelector ====== * '''BREAKING CHANGE''': UniversalLanguageSelector extension now requires MediaWiki 1.35 or above. * MODERN VECTOR: ** Position language menu below language button. ({{phab|T276248}}) ** Fix "ULS settings window can’t be opened with the preferences link on new Vector". ({{phab|T282956}}) ---- ===== 2021.06 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.06.tar.bz2 * sha256sum: 09e16a44f09103637ebd97a69bc96a8ad657cf6748ec7f859532be7270dc40fb [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.06.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/JAXSTQBGQVBMUUZ5JMUZMSIFTZV47LZC/ Announcement and Release Notes] * Compatible with MediaWiki 1.34 or above and requires PHP 7.2 or above. * Bug fix release. ====== Translate ====== * Fix metadata handling for translatable page moves and deletions. ({{Phab|T282905}}) * Restore suggested languages to compact languages button. ({{Phab|T282037}}) ---- ===== 2021.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.04.tar.bz2 * sha256sum: 652b7838b4c87fba80ca46ebd15a106bf3fd4e9cc202417de6ee3ad33d2a8048 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2021-April/001207.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.34 and above and requires PHP 7.2 or above. ====== Translate ====== * Consider translated optional messages towards meeting the export threshold ({{Phab|T159122}}) * Do not lock pages indefinitely during translatable page moves ({{Gerrit|661125}}) * Limit pages that can be moved from the UI to 500 by default. ({{Phab|T277431}}) ** This can be modified by updating the configuration: <code>$wgTranslatePageMoveLimit</code> * Namespace for classes under the <code>src/</code> folder has been changed to: <code>MediaWiki\Extension\Translate</code> instead of: <code>MediaWiki\Extensions\Translate</code>. <code>class_alias</code> has been used to ensure existing functionality and cached data does not break. The alias will be removed in the next MLEB release. ====== UniversalLanguageSelector ====== * Ensure ULS supports modern Vector ({{Phab|T273232}},{{Phab|T273928}}) ---- ===== 2021.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.01.tar.bz2 * sha256sum: 4360572704369e5c1f02ab9df831dd0a6258cbcbae28c61c3c4a551347000b00 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2021-January/001204.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.34 and above and requires PHP 7.2 or above. ====== Translate ====== * Add script to find unsynchronized definitions ({{Gerrit|655860}}) * Various improvements to the transaction export.php script * Add a script to find and delete equal translations ({{Gerrit|652543}}) * GoogleTranslateWebService: Add Chinese codes to code map ({{Gerrit|649652}}) * Convert Special:ManageMessageGroups to OOUI ({{Gerrit|647670}}) * Insertables have been moved to the src/TranslatorInterface/Insertable folder ({{Gerrit|644460}}) * Stop hiding page heading on pages other than Special:Translate ({{Gerrit|644514}}) * Drop non-array based configuration support for Insertables ({{Gerrit|644464}}) ====== UniversalLanguageSelector ====== * Remove FCFontFinder ({{Gerrit|641189}}) * Bump group loader cache version to re-trigger re-caching of groups ({{Gerrit|644843}}) * Remove Gettext post processing support from export.php script ({{Gerrit|641385}}) * Improve handling of opening links to new tab/window for compact language links ({{Gerrit|639474}}) * Allow skins to register their own button and disable compact language links ({{Phabricator|T264824}}) <includeonly>[[MediaWiki_Language_Extension_Bundle/releases|Show all releases]].</includeonly><noinclude> ---- ===== 2020.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.10.tar.bz2 * sha256sum: 8a0b0282e3a1ef88b231f8c1fd8c922052eba6e0b55b75f87de940632f3730e1 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2020-October/001201.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.34 and above and requires PHP 7.2 or above. * The Translate extension now requires MediaWiki 1.34 or above. * Update the language selector on the Special:PageTranslation ({{Gerrit|616762}}) * Do not list all pages on marking a page for translation ({{Gerrit|621034}}) * Add API to fetch translation statistics ({{Gerrit|623169}}) * Replace PHPlot with Chart.js on Special:TranslationStats ({{Phabricator|T134634}}) * Fix mandatory deletion of sub pages when deleting translatable pages ({{Gerrit|636871}}) * Rename MessageValidator namespace to Validation ({{Gerrit|616069}}) * Legacy editor: remove various translation helpers, custom buttons * Make Language stats appear better on mobile screens and make the header sticky ({{Gerrit|631979}}) * Tag untranslated translations units with lang and dir attributes ({{Phabricator|T254484}}) * Add magic word: <code><nowiki>{{TRANSLATIONLANGUAGE}}</nowiki></code> for translatable pages ({{Phabricator|T254486}}) * Avoid showing bdi tags on Special:Translate ({{Phabricator|T117852}}) * Add [[Help:Extension:Translate/Developer_guide|Developer guide]] for Translate ({{Phabricator|T256873}}) * Fix "Translation page does not contain the latest translations/last translation" ({{Phabricator|T255334}}) * Fix "This namespace is reserved for content page translations" when trying to translate a recently created translation unit" ({{Phabricator|T221119}}) * ULS now defines unsupported skins ({{Phabricator|T237036}}, {{Phabricator|T235712}}) * Remove configuration variables: <code>ULSCompactLinksForNewAccounts</code> and <code>ULSCompactLinksEnableAnon</code> ({{Gerrit|632721}}) ---- ===== 2020.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.07.tar.bz2 * sha256sum: 7334f6c0f4e00a451d976c81024c955061cffc3466d8a03fd223733992d0a2d5 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2020-July/001200.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.33 and above and requires PHP 7.2 or above. * Update to cldr 37. * Fixes to moving and deletion of translatable pages. ([[phab:T168591|Phab:T168591]]) * Display a help message when editing a translatable page source. ([[phab:T192052|Phab:T192052]]) * Translations are now published instead of saved, for consistency with rest of MediaWiki. ([[phab:T131132|Phab:T131132]]) ---- ===== 2020.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.04.tar.bz2 * sha256sum: 97dbf8846c62cbafa43b7b5f359c3fb55039846277ebb55dd7b00e42d356d709 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2020-April/001193.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.33 and above and requires PHP 7.2 or above. * Remove PHP based entry point for Translate extension. Use <code>wfLoadExtension( 'Translate' );</code> to load the Translate extension. * Test and add support for PHP 7.4. Now all versions of PHP 7.2 and above are supported. * '''SECURITY FIX''': Translate: HTML from messages was not escaped in Special:ManageMessageGroups. If you do not use this page (e.g. only use translatable wiki pages) you are not affected. ([[phab:T242115|Phab:T242115]]) ---- ===== 2020.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.01.tar.bz2 * sha256sum: 94c6bb79e6b3bc55b8ca629165256a96da8dbd196999da09ba45a7e11cc7c194 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2020-January/001191.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.33 and above and requires PHP 7.2 or above. * Updated to cldr 36. * Prevent duplicate translation unit error from showing twice. ([[phab:T236153|Phab:T236153]]) * Add secondary check before displaying tpt-unknown-page error. ([[phab:T221119|Phab:T221119]]) * Display an error message if translation aids fail to load. ([[phab:T221119|Phab:T221119]]) * Improve message group selector performance reducing Translate API request time. ([[phab:T236904|Phab:T236904]]) * Update setlang to display confirmation dialog to change language. ([[phab:T63115|Phab:T63115]]) ---- ===== 2019.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.10.tar.bz2 * sha256sum: b7d6afdb365c7333829ab5b4e286c2f28e3a5f6f48d1584c1f43439e74a60de6 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2019-October/001188.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.32 and above and requires PHP 7.1.0 or above. * PHP entry point has been deprecated. To load the Translate extension, please use the following, <pre>wfLoadExtension( 'Translate' );</pre> * Removed deprecated and unmaintained SolrTTMServer. Recommendation is to migrate to ElasticSearch. ([https://phabricator.wikimedia.orgT87985 Phab:T87985]) * Dropped support for HHVM. ---- ===== 2019.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.07.tar.bz2 * sha256sum: 84cb6de241f62c7e5e9853d74390c4ffbf55cf35aab930c36f9ec5733a351130 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2019-July/001186.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.32 and above and requires PHP 7.0.0 or above. * Update to cldr 35.1 ([https://phabricator.wikimedia.org/T220906 T220906]). * Translate and UniversalLanguageSelector now requires MediaWiki >= 1.32.0. Please upgrade! * Added a new MessageValidator framework to improve translation validation. ([https://phabricator.wikimedia.org/T204568 T204568]) ([[Help:Extension:Translate/Validators|See documentation]]). * Fixed invalid more warnings label shown during message translation ([https://phabricator.wikimedia.org/T220789 T220789]) * Added several African keyboards in UniversalLanguageSelector. ---- ===== 2019.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.04.tar.bz2 * sha256sum: 5fbbd39acd1cc0e1edbd542a390daf1992d1526134ceb69248cdb4dced58f3a9 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2019-April/001180.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.31, 1.32 and above and requires PHP 7.0.0 or above. * PHP entry point has been removed for CleanChanges and cldr. Warning will be displayed for deprecated PHP entry point. (T140007) * Fixed fatal error on PageContentLanguage hook subscriber (T214358) * Fixed broken Special:PageMigration (T217727) * Added support for newer versions of the Elastica extension while maintaining backward compatibility for older version REL 1.31 (T218100) * Added multiple new keyboard layouts in UniversalLanguageSelector. ---- ===== 2019.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.01.tar.bz2 * sha256sum: 39f2e946e360ac868744dc8e6f62cb5723447415bd11bcbb4911eb0f3674360c [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2019-January/001177.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.31, 1.32 and above and requires PHP 5.5.9 or above. * $wgTranslateCC is deprecated now. It should be replaced by TranslatePostInitGroups hook. (T212836) * Added proofreading to (Language|MessageGroup)Stats. The statistics table also has updated styling. (T41279) * Skipping messages Special:Translate's page mode no longer sometimes marks the translation proofread. (T206748) * Translatable subpages are no longer moved when moving parent. (T114592) * Message group stats updating was broken in multiple ways. (T134252, T208521) * Added multiple new keyboard layouts in UniversalLanguageSelector. ---- ===== 2018.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.10.tar.bz2 * sha256sum: c0a65956d4f8e49ba1b401372636b9575a5c17fbf2501fa14ff1c265dd778862 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2018-October/001175.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.30, 1.31 and above and requires PHP 5.5.9 or above. * Updated cldr to version 34.0 * LocalisationUpdates and UniversalLanguageSelector has removed PHP entry point. Please update your configuration! * Fixed an error in Translate that prevented Special:PageMigration from working. * UniversalLanguageSelector now supports UI language change when Global Preferences are present. (T198206) * UniversalLanguageSelector dropped support for discontinued freegeoip.net. ---- ===== 2018.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.07.tar.bz2 * sha256sum: 36aa80c78be6dcfb533f96dc25afdabd2fd4716452c1b5a6f2bc982def1af7bc [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2018-July/001168.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.30, 1.31 and above and requires PHP 5.5.9 or above. * Updated cldr to version 33. * Special:SupportedLanguages: List of authors is now sorted by the number of contributions. * Message keys coming from external files are now handled with more care and less likely to produce invalid or inaccessible pages. ([[phab:T193023|T193023]]) * refresh-translatable-pages.php script can now use JobQueue, which is more efficient on wikis with thousands of translatable pages. ([[phab:T195347|T195347]]) * Custom languages defined in $wgExtraLanguages now always appear in Special:Translate and Special:SearchTranslations. ([[phab:T112889|T112889]]) ---- ===== 2018.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.04.tar.bz2 * sha256sum: e8b4da822b2dcc7906e444a65e8924d8505c028c8636cdfe8d38059dc9ef1d1c [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2018-April/001164.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.29, 1.30 and above and requires PHP 5.5.9 or above. * Fixed compatibility with MediaWiki 1.29 release. * Added the 'translate' right to the 'editpage' grant. This will allow OAuth apps to translate. * Translation variables can now span multiple lines. * AndroidXml file format now includes authors. * Fixed Ctrl-Clicking in Compact Language Links. ([[phab:T189582|T189582]]) * ULS trigger and settings are more keyboard accessible now. ([[phab:T52793|T52793]]) * Language search results are not grouped by region. ---- ===== 2018.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.01.tar.bz2 * sha256sum: a6d90633cf16dbf48c0481d1e073130717d98b9540c0d1b80059bb34946c6749 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2018-January/001155.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.29, 1.30 and above and requires PHP 5.5.9 or above. * Translation filter is now part of the new recent changes interface if the new interface is available. * Almost all legacy non-TUX code has been removed from Translate. * Removed non-default webfonts for some languages in UniversalLanguageSelector. * User interface and search improvements in UniversalLanguageSelector. ---- ===== 2017.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.10.tar.bz2 * sha256sum: 75eefff3bbf50f1f84232f45ab169d2eedea5f7a18994f85b43237f2145403b1 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2017-October/001151.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.28, 1.29 and above and requires PHP 5.5.9 or above. * Translate, Universal Language Selector and Babel received style updates. * Search for languages in Universal Language Selector was improved. * Translate extension received multiple compatibility fixes. ---- ===== 2017.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.07.tar.bz2 * sha256sum: c050c326bfa56d326fece072bed5e4be3e3ad3289b0a449313a2e7dbc4514c55 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2017-July/001132.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.27, 1.28 or above and requires PHP 5.5.9 or above. * Translate extension no longer bundles spyc library. If you need support for parsing and generating YAML files, and you don't have phpyaml extensions installed (HHVM provides it in PHP compatibility mode), then you can install spyc using composer update. * Information about the languages that the user knows in Babel is now cached to improve performance. * It is now possible to load Babel information from a Babel box on a global user page. * Compact Language Links the ability to show languages that logged-in users specified in the Babel box. * Several new IMEs are added and improved in UniveralLanguageSelector. ---- ===== 2017.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.04.tar.bz2 * sha256sum: 4207398d7ed3ea9c793f35f88e75f29672b33aee4d0baf01afc869517c629c65 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2017-April/001120.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.27, 1.28 or above and requires PHP 5.5.9 or above. * CLDR updated to version 31. * Support for Elastic5, Multi-DC for TTMServices, freezing writes added in Translate. * Import of the new translations in Special:ImportTranslations is fixed now. * Several new IMEs are added in UniveralLanguageSelector. ---- ===== 2017.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.01.tar.bz2 * sha256sum: 89f4a029f33ea9f9225c8379367bc526fa63353845a2873290ba82560fb314c9 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2017-January/001099.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.27, 1.28 or above and requires PHP 5.5.9 or above. * Several improvements in Translate editor, MessageTable and Special:TranslationStats * SpecialPage(Preparation|Migration) are moved to tag. * jquery.i18n library is removed from UniveralLanguageSelector, which is now available in MediaWiki core since 1.26 release. ---- ===== 2016.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.10.tar.bz2 * sha256sum: f82ac16b1a71433d68066c684c2e67379d3c435d1938044a9f0f0582cb6549b3 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2016-October/001089.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.26, 1.27 or above and requires PHP 5.5.9 or above. * Easy way to access wikitext editor from Special:Translate. T48955 * Special:Translate now works with MobileFrontend. T102922 * Special:Translate now works better in mobile devices. T146134 * WebAPI module to query user's babel languages. * The style of ULS's dialogs have been updated and polished to be more streamlined (for real this time, was incorrectly claimed to be included in 2016.08). ---- ===== 2016.08 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.08.tar.bz2 * sha256sum: aba09ead5f2c646e5960ce2aecc36866ee092079f51598d0aab461c7655410da [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.08.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2016-August/001084.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.26, 1.27 or above and requires PHP 5.5.9 or above. * Translate extension now requires Elastica extension for ElasticSearch support. Wikimedia search plugin needs to be installed for ElasticSearch 2.x series. * Special:Translate now has a summary field. * Special:Translate is much more robust thanks to improved error handling and to many small bugs having been fixed. * Page translation is much more robust. * The sandbox feature of Translate extension requires MediaWiki 1.27 or newer. * Translate's export functionality is now on separate special page called Special:ExportTranslations * The style of ULS's dialogs have been updated and polished to be more streamlined. * The default geoip service for Universal Language Selector is changed because the old service is discontinued. * Major update on webfont formats: woff2 format added, eot and svg formats dropped. ---- ===== 2016.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.04.tar.bz2 * sha256sum: 113439ad94b1a75ab8616f41c4d120e12c1fa8c3888933ec136783bfbdc9bc70 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2016-April/001061.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.25, 1.26 or above and requires PHP 5.5.9 or above. * Babel and LocalisationUpdate ** Extensions now uses extension registration. * CLDR: ** Updated to CLDR 29 release. * Translate: ** Message group selector now works in Internet Explorer and Edge browsers. ** [[phabricator:T48716|A bug was fixed that sometimes caused translation pages not to update changes to the source page after marking it for translation]]. After upgrading it is recommended to run scripts/refresh-translatable-pages.php to ensure no pages contain outdated content. * UniversalLanguageSelector: ** Fixed issues related to the tooltip shown for language settings that sometimes caused JavaScript errors. ** Input methods now work with VisualEditor. ---- ===== 2016.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.01.tar.bz2 * sha256sum: 7a46bb96f852aa42f728c68e4e21558878c8cba703ce9f8f6c2316af7bbe03e3 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2016-January/001047.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.25.x and 1.26.x. * CLDR: ** cldr is converted to extension registration. Please update your LocalSettings.php! * Translate: ** Old custom tokens were deprecated in favor of using regular "csrf" (previously known as "edit") token. If you are using Translate WebAPIs you might need to migrate. ** Special:Translations no longer shows PHP notices for pages with invalid language codes * UniversalLanguageSelector: ** ULS now uses extension registration and thus requires MediaWiki 1.25 or later. ** Input methods should now work inside Visual Editor. ** Various fixes in fonts and input methods. ---- ===== 2015.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.10.tar.bz2 * sha256sum: 482595d35ab02fdc40c6ae54d2cf21aa22360f7021d498c054624ccdbf721237 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-October/001029.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.24.x and 1.25.x. * CLDR: ** Updated to CLDR 28. * Translate: ** MediaWiki 1.23 is no longer supported. Extension is no longer automatically loaded when installed via composer. ** If local TTMServer translation memory is marked as public, it will <s>not</s> '''now''' automatically take advantage of TranslationWebServices query parallelization. * UniversalLanguageSelector: ** MediaWiki 1.23 is no longer supported. Extension is no longer automatically loaded when installed via composer. ** Language change is now done in two phase: first changed with API, then page is reloaded. The 'setlang' URL parameter is no longer used, although it still works. Due to the change, language switching might take a slightly longer than previously. ---- ===== 2015.08 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.08.tar.bz2 * sha256sum: 21cb43509d1e6da3cadc7e594866215d430e110aea5d04857e5cffd2a69db031 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.08.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-August/001009.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x, 1.24.x and 1.25.x. * Translate: ** Special:SearchTranslations has acquired lots of new features, such as cross language search. To take advantage of all the new features, you need to reindex the index with "php scripts/ttmserver-export.php --reindex". You also need to update ruflin/elastica to 2.2.0 or later, or recent version of CirrusSearch which bundles it. * UniversalLanguageSelector: ** ULS will use jQuery.i18n from MediaWiki core if available. ** Updated the default geoiplookup URL. ** ULS supports extension registration now. ** New Input Methods and fonts are added. ---- ===== 2015.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.04.tar.bz2 * sha256sum: 0aaae92b987130068b9fc03595428286d96541a947cbd137147ae7c0f50d9241 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-April/000985.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * Babel: ** Restore compatibility with MediaWiki 1.24 and older version. * CLDR: ** Update to CLDR 27.0.1 * Translate: ** Styled search result navigation buttons in Special:SearchTranslations ** Fixed Special:PagePreparation, now works better and has autocompletion * UniversalLanguageSelector: ** Show the Common language section only if the list is long enough. ** Make ULS IME working in Content Translation. ---- ===== 2015.03 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.03.tar.bz2 * sha256sum: 938444aecd01df92d340e69b0f1c341de7085269bf5e6bbb28b82f41e816cc6d [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.03.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-March/000979.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * LocalisationUpdate: ** A bug that prevented extension and skin i18n files to be updated is fixed now. * Translate: ** Improvements in the message group selector. * UniversalLanguageSelector: ** Fixed issues related to the tooltip for ULS cog (trigger icon at the sidebar interlanguage position). ---- ===== 2015.02 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.02.tar.bz2 * sha256sum: 536cf86e7080d8293a02cb59f99d96328c7009c8239e818556b28b77b02ff88d [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.02.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-February/000976.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * Translate: ** Improvements in Special:PagePreparation. ** Performance improvements by removing unneeded queries. * UniversalLanguageSelector: ** Restore compatibility with IE8. If you still have any issue, please report it! ---- ===== 2015.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.01.tar.bz2 * sha256sum: 7a53ed826ae14ffe279fc4231cc47d367f668723a5843ad62c13a8f17d339744 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-January/000967.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * LocalisationUpdate: ** Added support for updating skins. * Translate: ** Added Content Translation Machine Translation backend support. ** Message group configurations are now optionally validated. ** Make 'fuzzy' as a default action for changes in source language in Special:ManageMessageGroups. * UniversalLanguageSelector: ** This version has compatibility issues with Internet Explorer 8. Support will be restored in the next MLEB release. ---- ===== 2014.12 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.12.tar.bz2 * sha256sum: 5a0e00d27e2a81b896de4015a8f0933f24ea3409e554b0ba7f2e3c27ec27430f [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.12.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-December/000959.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * Translate: ** Due to MediaWiki core plural rule changes, Translate extension contains interface translations which are not compatible with any released version of MediaWiki. If you are using Translate in the affected languages, (See https://blog.wikimedia.org/2014/11/04/updates-in-mediawiki-internationalization-reflect-changes-from-cldr/ for more details and list of affected languages) you might want to consider using MLEB 2014.09 instead. The issue manifests as incorrect plural forms used in the interface for certain numbers. ** T76184: Improvements in ElasticSearch TTM. Query results are now more reliable and consistent. * UniversalLanguageSelector: ** As a part of refactoring ULS design, world map from ULS has been removed. You can track progress of task at https://phabricator.wikimedia.org/T85519 ---- ===== 2014.11 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.11.tar.bz2 * sha256sum: 39b397a05561f743962cfb499f59a58219338607ea13ebfcc7a8806105e7dedc [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.11.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-November/000947.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * CLDR: ** Fixed some time displays if CLDR had only partial localisation of time units. * Translate: ** Translate WebAPI documentation is now localized. Only works in MediaWiki 1.24 and newer. ** If you are using the '''Solr backend '''for the translation memory or the translation search, please let us know. If there are no users for the Solr backend, we will deprecate and later remove it in favor of the better maintained ElasticSearch backend. * UniversalLanguageSelector: ** ULS WebAPI documentation is now localized. Only works in MediaWiki 1.24 and newer. ** T67516: Removed font-size for ULS language selection panel buttons, which caused tiny font sizes on the Monobook skin. ** Small compatibility fix when both ULS and VisualEditor are in use. ** About 20 new languages are now supported in the language selector and a couple language names were changes. ** Added support for WOFF2 webfont format. Note that there are no WOFF2 webfonts in the font repository yet due to pending issues in WOFF2 font generation. ---- ===== 2014.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.10.tar.bz2 * sha256sum: 49707823ec19d9eed1c21c37550a3b0a2c81ff83855aea2706287a5169e90468 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-October/000936.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.22.x and 1.23.x. * CleanChanges: Added support for ULS in language filter selector. * Translate: * New feature: Remove any page from translation with two clicks from Special:PageTranslation. Previously, translate tags had to be removed manually first. * Special:PageTranslation also has prettier warning and error notifications. * The user group translate-proofr is no longer created by default. If you were using it, you can add it back with following code in your LocalSettings.php: $wgGroupPermissions['translate-proofr']['translate-messagereview'] = true; $wgAddGroups['translate-proofr'] = array( 'translate-proofr' ); * Removed $wgTranslatePageMigration (enabled by default), $wgTranslateUseTux (no longer in use) and translate-proofr group (needs sysadmin action if in use). ---- ===== 2014.09 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.09.tar.bz2 * sha256sum: 9cfdc7d4fc87b4cd6f8d1d2e1593b8cd064b7a9a2773c1a6a554304949a609ec [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.09.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-September/000920.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.22.x and 1.23.x. * CLDR is updated to 26. * Translate: * Regression fixed: Translate's compatibility with MediaWiki 1.22 has been restored. * Regression fixed: Fix translation ratios in translatable page language selector. * Special:MyLanguage is now in core. For backwards compatibility, translations of Special:MyLanguage aliases were moved to a separate file (Bug 69461). * $wgTranslatePageTranslationULS now works as intended on all translation pages by removing the language code from the page name. ---- ===== 2014.08 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.08.tar.bz2 * sha256sum: f4663910facd2b34d4afb1af930f66adad22b2746f9395f7706f07751e633857 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.08.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-August/000911.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.22.x and 1.23.x. * Added Comic Neue font. It is available for English and other languages using the latin alphabet. * Translate ** Breaking change: Dropped support for MediaWiki 1.21 (2014.05 is the latest version of MLEB as a whole which supports 1.21) ** Avoid losing translators' edits: improved handling of expired sessions ({{bug|69314}}). ** Restore progress icon for the current translation page (regression from MLEB 2014.07). ---- ===== 2014.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.07.tar.bz2 * sha256sum: 8af5c001db9375bf8dfd16495c7a88fc8dc9b4fe281b1048f6bea6c490bc4a9d [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-July/000902.html Announcement and Release Notes] * Compatible with MediaWiki: 1.22.x and 1.23.x. * Updated to CLDR 25 and fixed rebuild script. * Display source language for the pages in Special:Translate * Fixed ElasticSearchTTMServer to not return matches for single word messages only. * Stopped using deprecated jquery.json module, this will make ULS slightly smaller. * Added Ludic (lud) transliteration and Tibetian (bo) EWTS layouts. ---- ===== 2014.06 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.06.tar.bz2 * sha256sum: 02721b25e8c8fe06889b825a1c03fc4c1b1e4268d1e56169815983b5e87e8932 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.06.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-June/000893.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.22.x and 1.23.x. ** Translate: New feature, Special:PageMigration page has been added and feedback is welcome! ** Translate: Email notifications are no longer sent upon translation review. ** Translate: Regression fix: Message checker live updates is working again with this release. ---- ===== 2014.05 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.05.tar.bz2 * sha256sum: f53030ce7e6e0619f9a075877bc85423c0a28f46ffb296dbed5733502683b9b3 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.05.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-May/000881.html Announcement and Release Notes] * Compatible with MediaWiki: 1.21.10 and 1.22.7. * Translate: When a user is promoted from translator sandbox, it is treated as account creation. Promoted users can now receive NewUserMessage. * CLDR: The fallback logic should not merge the time units from languages in fallback chain. It should use time units from a fallback language only when time units are not defined. * Always display assistant languages in compact language list when defined by user in Translate extension. * Added 'Hussaini Nastaleeq' font for Urdu. ---- ===== 2014.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.04.tar.bz2 * sha256sum: f20631d2629e0cf80df8ca022e6eec4d6d784e0cd39799f9fd46f338f4a7381a [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-April/000866.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.9 and 1.22.6. ** LocalisationUpdate now updates messages for older MediaWiki versions. ** Set JSON message format as default for MediaWiki extensions. ** Allow overriding the header styles from typography refresh. ** Added Batak input method. ---- ===== 2014.03 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.03.tar.bz2 * sha256sum: f3a253e05f6b7c4f451882a1a78a138a1dcaecd2777237d0c2b8af7c3ecced70 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.03.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-March/000838.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.7 and 1.22.4. ** LocalisationUpdate is rewritten for JSON file format support for extensions. This is compatible with MediaWiki 1.19 and above. ** ULS adds compact language links as new BetaFeature. ---- ===== 2014.02 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.02.tar.bz2 * sha256sum: 5c5636332b38a7ce9ac12fac74f0402afdc592aa58795b51dc4747877db340da [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.02.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-February/000808.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.5 and 1.22.2. ** Added AppleFFS module for iOS/Mac OS X Localizable.strings files ** Detect tofu before applying any default fonts. See: https://www.mediawiki.org/wiki/Universal_Language_Selector/WebFonts#How_webfonts_are_applied.3F for technical documentation about how tofu detection works in ULS. ** ULS is now much lighter for the browser thanks to many changes (see full Release Notes) ---- ===== 2014.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.01.tar.bz2 * sha256sum: 2dc673ba0bbc43a3d69237c15600171e85d3c56d9ff520e5bdb3eda0f2fdc74a [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-January/000803.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.5 and 1.22.2. ** Refactoring and performance improvements in ULS. ** Regression fixes introduced in previous MLEB release in Translate. ** Initial plural support for Android file format. ---- ===== 2013.12 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.12.tar.bz2 * sha256sum: 2ef19e31d685dd0d6e50088ec8bbb1cd3e74c694096dfa333efb61dcfee9c3c0 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.12.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-December/000791.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.3 and 1.22.0. ** Refactoring and performance improvements in Translate Sandbox and TUX. ** Added support to MediaWiki localisation format from PHP files to JSON files. ** Language selector now opens an order of magnitude faster. ** Initial support for webfonts in MobileFrontend. ---- ===== 2013.11 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.11.tar.bz2 * sha256sum: 926bdcb6aa9cc405dc54275a60fd1d13836ee0f36a1e9c1329f4f7eed94354ce [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.11.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-November/000772.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.20.7 and 1.21.2. ** Lots of cleanup, refactoring and performance improvements: ** The ResourceLoader modules for ULS were redone. They are now lazy-loaded to improve the initial page loading time. To use features provided by ULS, such as styles, ULS data utils functions, and others, you must load the features separately in your extensions. See https://www.mediawiki.org/wiki/Universal_Language_Selector/Developing_with_ULS for more details. ** Cleanup, refactoring and performance improvements in Translate extension. ---- ===== 2013.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.10.tar.bz2 * sha256sum: 04b1a1db293439553c225765a41add5f0bcd3ad4dce7f89e1f098276470e96c4 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-October/000762.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.20.7 and 1.21.2. ** Use the Autonym font for language autonyms in the Language Search box and Interlanguage links. ** Introducing of the TranslationStash feature. It's the place where sandboxed users can store their translations before they are given full translator rights. ---- ===== 2013.09 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.09.tar.bz2 * sha256sum: 2ac55639aeb43a6f3d198a87e10111f673eae1115225de072be73a1fa2052ab2 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.09.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-September/000751.html Announcement and Release Notes] ** Compatible with MediaWiki 1.20.7 and MediaWiki 1.21.2. ** The latest development efforts are about fixing known bugs and improving performance. ** Added initial support for insertables. This will be helpful in typing and copy-paste of syntax like $1 and plural especially on tablets (bug 38350). More about this feature at: http://laxstrom.name/blag/2013/09/18/insertables-in-translate-extension-make-translating-easier/ ** CLDR is updated to version 24. ---- ===== 2013.08 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.08.tar.bz2 * sha256sum: 21b3abf3a8e19d0c746d41d246e4bc8883d0f5e179d894e1720500031c621f2c [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.08.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-August/000732.html Announcement and Release Notes] ** The latest development efforts are about fixing known bugs, improving performance and adding fonts. ** EventLogging support has been added to ULS. ** Several bugs were fixed in the Translate extension. ---- ===== 2013.07 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.07.tar.bz2 * sha256sum: ca381ea1bc1f10c56df28353f91a25129c604ff11938b424833925e8716e2ff3 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-July/000725.html Announcement and Release Notes] ** The ULS is stabilizing. The latest development efforts are about fixing known bugs, improving performance, and adding fonts. ** Several bugs were fixed in the Translate extension. ** Support for Yandex Translate API v1.5 was added to Translate. ---- ===== 2013.06 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.06.tar.bz2 * sha256sum: 6df32382ddec91ab61e3e74f2ede6c043220d5c1252ee3baf8efd1d6403b4d82 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.06.tar.bz2.sha256sum] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-June/000719.html Announcement and Release Notes] ** The "interlanguage" mode in ULS, which shows the ULS trigger as a cog icon in the interlanguage links area, is now considered stable. It can be enabled by setting $wgULSPosition to 'interlanguage'. ** Several bugs were fixed in the Translate extension. ** Support for currency was added to the CLDR extension. ---- ===== 2013.05 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.05.tar.bz2 * sha256sum: 9aea5b1dac2b38e44284373c849241fc694c78caff1d3ca3b4e6e72d66f2ab12 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.05.tar.bz2.sha256sum] *[http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-May/000699.html Announcement and Release Notes] ** The [[wmfblog:2013/03/25/redesigning-the-translation-experience-an-overview/|new translation interface]], known as Translate UX, is considered stable. Several bugs were fixed. ** Some design changes were introduced to the Universal Language Selector. Work continued on the "interlanguage" mode, which shows the ULS trigger as a cog icon in the interlanguage links area. It can be enabled, but is still experimental. A known issue is [[:bugzilla:48898|bug 48898]] - the "Apply settings" button doesn't close the Input settings panel after enabling or disabling the settings. The settings are saved, but the button doesn't work correctly. ** CLDR was updated to version 23.1. ---- ===== 2013.04 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.04.tar.bz2 * sha256sum: bd6aca60101308f429d90d421e35093328e7a05ea74d35c05a98474ab648dec4 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.04.tar.bz2.sha256sum] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-April/000677.html Announcement and Release Notes] ** The [[wmfblog:2013/03/25/redesigning-the-translation-experience-an-overview/|new translation interface]], known as Translate UX, is being improved. In particular, several bugs affecting Microsoft Internet Explorer users were fixed. ** The ''UniversalLanguageSelector'' extension is compatible with MediaWiki 1.20.4. It is not compatible with previous versions of MediaWiki. ---- ===== 2013.03 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.03.tar.bz2 * sha256sum: be4c6b5f80e27396555dc09cef0cec92c78cca9eeef796a230da281734738810 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.03.tar.bz2.sha256sum] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-March/000631.html Announcement and Release Notes] ** '''The [[wmfblog:2013/03/25/redesigning-the-translation-experience-an-overview/|new translation interface]], known as Translate UX, is now the default.''' It can be disabled by setting $wgTranslateUseTux to <code>false</code> in LocalSettings.php. **The [[:File:Translate_manual_-_Page_example_-_15._Translate_fuzzied.png|diff feature]] on all old outdated translations is [[bugzilla:46562|temporarily broken]] until all such old "fuzzy" messages are updated. ** '''The ''UniversalLanguageSelector'' extension is updated to the latest version'''. It is compatible with MediaWiki 1.20.3. It is not compatible with previous versions of MediaWiki. ---- ===== 2013.02 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.02.tar.bz2 * sha256sum: 7fece850483e2b74539f69b461501d26487290293ae93b40cd31d6e96f90d112 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.02.tar.bz2.sha256sum] * [http://permalink.gmane.org/gmane.org.wikimedia.mediawiki.i18n/640 Announcement and Release Notes] * '''UniversalLanguageSelector is rolled back to the 2012.12 version''' for compatibility with MediaWiki 1.20 because of a [[gerrit:44001|known issue]] where, with UniversalLanguageSelector enabled, preferences are not saved for logged-in users. Wait for 1.20.3 or [https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=snapshot;h=refs/heads/REL1_20;sf=tgz use only with the last revision of the 1.20 branch]. ---- ===== 2013.01 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.01.tar.bz2 * sha256sum: 55adb8b1a5197570fe76501454a66d2f1581bd6854e4091e2b56545a6d072d0b [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.01.tar.bz2.sha256sum] * [http://comments.gmane.org/gmane.org.wikimedia.mediawiki.i18n/618 Announcement and Release Notes] * '''Compatible only with MediaWiki 1.21alpha'''. 1.20.2 has a [[gerrit:44001|known issue]] where, with UniversalLanguageSelector enabled, preferences are not saved for logged-in users; wait for 1.20.3 or [https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=snapshot;h=refs/heads/REL1_20;sf=tgz use only with the last revision of the 1.20 branch]. ---- ===== 2012.12 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2012.12.tar.bz2 * sha256sum: d27fdbbcdd73795914c6f6a8bdddedc3cea06c1ce968b9420f28028fda191a92 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2012.12.tar.bz2.sha256sum] * [http://comments.gmane.org/gmane.org.wikimedia.mediawiki.i18n/599 Announcement and Release Notes] * Compatible with MediaWiki 1.20 and 1.21alpha ---- ===== 2012.11 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2012.11.tar.bz2 * sha256sum: 924e95b8d5b1c9cef17f72ffe141b06df310ca2cbe013816b5fb69b09732763a [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2012.11.tar.bz2.sha256sum] * [http://comments.gmane.org/gmane.org.wikimedia.mediawiki.i18n/592 Announcement and Release Notes] * Compatible with MediaWiki 1.20 and 1.21alpha </noinclude> 0zp0dbttf5545asphx966xg5cr80a84 5387701 5387697 2022-07-29T05:58:39Z KartikMistry 550774 Updated announcement link. wikitext text/x-wiki ==== Latest release ==== ===== 2022.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.07.tar.bz2 * sha256sum: 3e8f48643403946fdb55f3ff086ed1e702c0367f3282c9dc78eb6785964c0809 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/YIJPCGOWIQL76PKOS24INSWH3ZJDQO34/ Announcement] * [https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2022.04 Release notes] * Compatible with '''MediaWiki 1.37.2''' or later and requires '''PHP 7.3.19''' or above. ====== LocalisationUpdate ====== * LocalisationUpdate extension is removed from MediaWiki Language Extension Bundle. Please [https://lists.wikimedia.org/hyperkitty/list/mediawiki-l@lists.wikimedia.org/message/BCDH3PUKWYGF5AZFCJI6ZPACHCQA6IT7/ read the announcement]. ====== Translate ====== * Support for MediaWiki 1.36 has been dropped. * Avoid recreation of translation pages on bulk deletion of pages, for example when using the Nuke extension. ({{phab|T291724}}, {{gerrit|799383}}) * Fix "Impossible to mark pages for translation using the mobile site". ({{phab|T311631}}, {{gerrit|809970}}) ===== 2022.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.04.tar.bz2 * sha256sum: a5ef23339730ec80422d60c31ece1fb696397f6be90fbe9fbf703cc9ddbf5527 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/JTU47XWODZPN6HGTEKO7MVI7YDHZ5LLS/ Announcement] * [https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2022.04 Release notes] * Compatible with '''MediaWiki >= 1.36.4 < 1.37''' or '''MediaWiki >= 1.37.2''' and requires '''PHP 7.3.19''' or above. ====== LocalisationUpdate ====== * We're planning to sunset the LocalisationUpdate extension from version 2022.07. Please [https://lists.wikimedia.org/hyperkitty/list/mediawiki-l@lists.wikimedia.org/message/BCDH3PUKWYGF5AZFCJI6ZPACHCQA6IT7/ read the announcement]. ====== Translate ====== * If you are using [[Help:Extension:Translate/Translation memories|translation memory]] with ElasticSearch backend, we recommend rebuilding the translation memory index. This can be done by running <code>php <path_to_mediawiki_core>/extensions/Translate/scripts/ttmserver-export.php</code> ==== Previous releases ==== ===== 2022.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.01.tar.bz2 * sha256sum: 0cb434980b399f7bac42a92c9f171b6c9041cb998e3b2b0fcf16daf58c43fe61 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] *[https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/BA34V5I7OIAZRLA2RDWCKXYT4Q4AF4Q2/ Announcement] * [https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2022.01 Release notes] * Compatible with '''MediaWiki 1.36''' or above and requires '''PHP 7.3.19''' or above. ====== Translate ====== * Breaking change: Remove backward compatibility for MW <= 1.35 ({{phab|T298788}}, {{gerrit|752166}}) ====== UniversalLanguageSelector ====== * Remove backward compatibility for MW <= 1.35 ===== 2021.12 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.12.tar.bz2 * sha256sum: 61c9c7a700c9f98c6b3c59adf2f0fc7d1919fc87e0c3584308d313536dd81f37 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.12.tar.bz2.sha256sum <nowiki>[1]</nowiki>] *[https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/57KMSHMFOAUOI3ZI2SVMUSVK6ZCHHU4C/ Announcement and Release Notes] * Compatible with '''MediaWiki 1.35.3''' or above and requires '''PHP 7.3.19''' or above. ====== Translate ====== * Fix broken SpecialMovePage on MediaWiki 1.35 ([[phab:T294605|Phab:T296450]]) ---- ===== 2021.11 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.11.tar.bz2 *sha256sum: 07e697bfed3ef153c421a760221e93f0e3fef70a8db54defd59c4608b4d56352 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.11.tar.bz2.sha256sum <nowiki>[1]</nowiki>] *[https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/ANOIEJQ5GMBCRYDHTRFTZVX32H44IXGD/ Announcement and Release Notes] * Compatible with '''MediaWiki 1.35.3''' or above and requires '''PHP 7.3.19''' or above. ====== Translate ====== * Fix compatibility with MediaWiki <= 1.37 when VisualEditor is installed. ([[phab:T294605|Phab:T294605]]) ---- ===== 2021.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.10.tar.bz2 * sha256sum: ce923b2a661e3a97ec8f0add9eb9369637e02cbb70a47b80a1e50f3e8c0001d6 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/7BIYSQZ5XXKC23ATRLJXGWZ356XVHVCV/ Announcement and Release Notes] * Compatible with '''MediaWiki 1.35.3''' or above and requires '''PHP 7.3.19''' or above. ====== Translate ====== * '''SECURITY''': Allow revdel-related actions in translatable pages ([[gerrit:c/mediawiki/extensions/Translate/+/725385|Gerrit]]) * '''BREAKING CHANGES''' ** Export script: remove <code>--hours</code> ([[gerrit:c/mediawiki/extensions/Translate/+/705677|Gerrit]]) ** Remove translation aids customization (Hook: <code>TranslateTranslationAids</code>) ([[gerrit:c/mediawiki/extensions/Translate/+/715939|Gerrit]]) ** Remove <code>$wgTranslateDelayedMessageIndexRebuild</code> ([[gerrit:c/mediawiki/extensions/Translate/+/719062|Gerrit]]) ** Remove <code>getConfiguration</code> and <code>getFFS</code> from MessageGroup ([[gerrit:c/mediawiki/extensions/Translate/+/715946|Gerrit]]) ** Group configuration: Rename validator keymatch option to include ([[gerrit:c/mediawiki/extensions/Translate/+/730035|Gerrit]]) ====== UniversalLanguageSelector ====== * '''SECURITY''': Language name search: Avoid searching for very long search keys ([[gerrit:c/mediawiki/extensions/UniversalLanguageSelector/+/732274|Gerrit]], [[phab:T293749|Phabricator]]) * Improve support for the new Vector Skin. * Remove configuration <code>ULSEnableAnon</code> ([[gerrit:c/mediawiki/extensions/UniversalLanguageSelector/+/707229|Gerrit]]) * Add support for multiple ULS buttons ([[gerrit:c/mediawiki/extensions/UniversalLanguageSelector/+/719325|Gerrit]]) ---- ===== 2021.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.07.tar.bz2 * sha256sum: f7cd8113c095375be51464429dff04c8fa5bb88bc22ba3d780bf5698668e52c5 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/7YEY5ICH43CFY5OOWEIS3XYHMZYGS343/ Announcement and Release Notes] * Compatible with MediaWiki 1.35 or above and requires PHP 7.2 or above. ====== Translate ====== * '''SECURITY''': Enhance validation and logging for AggregateGroups API deletions ({{phab|T282932}}) * '''BREAKING CHANGES''' ** Translate extension now requires MediaWiki 1.35 or above. ** Remove TranslateMessageGroupPathVariables hook ({{gerrit|701678}}) ** Remove Validator and LegacyValidatorAdapter ({{gerrit|685438}}) '''Configuration variable changes''' To address voice and tone issues in the Translate extension ({{phab|T277965}}) the following configuration variable names have been renamed: * <code>TranslateBlacklist</code> → <code>TranslateDisabledTargetLanguages</code> * <code>TranslateAuthorBlacklist</code> → <code>TranslateAuthorExclusionList</code> * <code>TranslateCheckBlacklist</code> → <code>TranslateValidationExclusionFile</code> ''The old variables will be supported for MLEB 2021.07 release but removed in the MLEB 2021.10 release.'' If you have defined [[Help:Extension:Translate/Group_configuration|message groups]] defined with <code>LANGUAGE</code> attributes, <code>whitelist/blacklist</code> have been changed to <code>include/exclude</code> ====== UniversalLanguageSelector ====== * '''BREAKING CHANGE''': UniversalLanguageSelector extension now requires MediaWiki 1.35 or above. * MODERN VECTOR: ** Position language menu below language button. ({{phab|T276248}}) ** Fix "ULS settings window can’t be opened with the preferences link on new Vector". ({{phab|T282956}}) ---- ===== 2021.06 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.06.tar.bz2 * sha256sum: 09e16a44f09103637ebd97a69bc96a8ad657cf6748ec7f859532be7270dc40fb [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.06.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.org/thread/JAXSTQBGQVBMUUZ5JMUZMSIFTZV47LZC/ Announcement and Release Notes] * Compatible with MediaWiki 1.34 or above and requires PHP 7.2 or above. * Bug fix release. ====== Translate ====== * Fix metadata handling for translatable page moves and deletions. ({{Phab|T282905}}) * Restore suggested languages to compact languages button. ({{Phab|T282037}}) ---- ===== 2021.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.04.tar.bz2 * sha256sum: 652b7838b4c87fba80ca46ebd15a106bf3fd4e9cc202417de6ee3ad33d2a8048 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2021-April/001207.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.34 and above and requires PHP 7.2 or above. ====== Translate ====== * Consider translated optional messages towards meeting the export threshold ({{Phab|T159122}}) * Do not lock pages indefinitely during translatable page moves ({{Gerrit|661125}}) * Limit pages that can be moved from the UI to 500 by default. ({{Phab|T277431}}) ** This can be modified by updating the configuration: <code>$wgTranslatePageMoveLimit</code> * Namespace for classes under the <code>src/</code> folder has been changed to: <code>MediaWiki\Extension\Translate</code> instead of: <code>MediaWiki\Extensions\Translate</code>. <code>class_alias</code> has been used to ensure existing functionality and cached data does not break. The alias will be removed in the next MLEB release. ====== UniversalLanguageSelector ====== * Ensure ULS supports modern Vector ({{Phab|T273232}},{{Phab|T273928}}) ---- ===== 2021.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.01.tar.bz2 * sha256sum: 4360572704369e5c1f02ab9df831dd0a6258cbcbae28c61c3c4a551347000b00 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2021-January/001204.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.34 and above and requires PHP 7.2 or above. ====== Translate ====== * Add script to find unsynchronized definitions ({{Gerrit|655860}}) * Various improvements to the transaction export.php script * Add a script to find and delete equal translations ({{Gerrit|652543}}) * GoogleTranslateWebService: Add Chinese codes to code map ({{Gerrit|649652}}) * Convert Special:ManageMessageGroups to OOUI ({{Gerrit|647670}}) * Insertables have been moved to the src/TranslatorInterface/Insertable folder ({{Gerrit|644460}}) * Stop hiding page heading on pages other than Special:Translate ({{Gerrit|644514}}) * Drop non-array based configuration support for Insertables ({{Gerrit|644464}}) ====== UniversalLanguageSelector ====== * Remove FCFontFinder ({{Gerrit|641189}}) * Bump group loader cache version to re-trigger re-caching of groups ({{Gerrit|644843}}) * Remove Gettext post processing support from export.php script ({{Gerrit|641385}}) * Improve handling of opening links to new tab/window for compact language links ({{Gerrit|639474}}) * Allow skins to register their own button and disable compact language links ({{Phabricator|T264824}}) <includeonly>[[MediaWiki_Language_Extension_Bundle/releases|Show all releases]].</includeonly><noinclude> ---- ===== 2020.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.10.tar.bz2 * sha256sum: 8a0b0282e3a1ef88b231f8c1fd8c922052eba6e0b55b75f87de940632f3730e1 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2020-October/001201.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.34 and above and requires PHP 7.2 or above. * The Translate extension now requires MediaWiki 1.34 or above. * Update the language selector on the Special:PageTranslation ({{Gerrit|616762}}) * Do not list all pages on marking a page for translation ({{Gerrit|621034}}) * Add API to fetch translation statistics ({{Gerrit|623169}}) * Replace PHPlot with Chart.js on Special:TranslationStats ({{Phabricator|T134634}}) * Fix mandatory deletion of sub pages when deleting translatable pages ({{Gerrit|636871}}) * Rename MessageValidator namespace to Validation ({{Gerrit|616069}}) * Legacy editor: remove various translation helpers, custom buttons * Make Language stats appear better on mobile screens and make the header sticky ({{Gerrit|631979}}) * Tag untranslated translations units with lang and dir attributes ({{Phabricator|T254484}}) * Add magic word: <code><nowiki>{{TRANSLATIONLANGUAGE}}</nowiki></code> for translatable pages ({{Phabricator|T254486}}) * Avoid showing bdi tags on Special:Translate ({{Phabricator|T117852}}) * Add [[Help:Extension:Translate/Developer_guide|Developer guide]] for Translate ({{Phabricator|T256873}}) * Fix "Translation page does not contain the latest translations/last translation" ({{Phabricator|T255334}}) * Fix "This namespace is reserved for content page translations" when trying to translate a recently created translation unit" ({{Phabricator|T221119}}) * ULS now defines unsupported skins ({{Phabricator|T237036}}, {{Phabricator|T235712}}) * Remove configuration variables: <code>ULSCompactLinksForNewAccounts</code> and <code>ULSCompactLinksEnableAnon</code> ({{Gerrit|632721}}) ---- ===== 2020.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.07.tar.bz2 * sha256sum: 7334f6c0f4e00a451d976c81024c955061cffc3466d8a03fd223733992d0a2d5 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2020-July/001200.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.33 and above and requires PHP 7.2 or above. * Update to cldr 37. * Fixes to moving and deletion of translatable pages. ([[phab:T168591|Phab:T168591]]) * Display a help message when editing a translatable page source. ([[phab:T192052|Phab:T192052]]) * Translations are now published instead of saved, for consistency with rest of MediaWiki. ([[phab:T131132|Phab:T131132]]) ---- ===== 2020.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.04.tar.bz2 * sha256sum: 97dbf8846c62cbafa43b7b5f359c3fb55039846277ebb55dd7b00e42d356d709 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2020-April/001193.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.33 and above and requires PHP 7.2 or above. * Remove PHP based entry point for Translate extension. Use <code>wfLoadExtension( 'Translate' );</code> to load the Translate extension. * Test and add support for PHP 7.4. Now all versions of PHP 7.2 and above are supported. * '''SECURITY FIX''': Translate: HTML from messages was not escaped in Special:ManageMessageGroups. If you do not use this page (e.g. only use translatable wiki pages) you are not affected. ([[phab:T242115|Phab:T242115]]) ---- ===== 2020.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.01.tar.bz2 * sha256sum: 94c6bb79e6b3bc55b8ca629165256a96da8dbd196999da09ba45a7e11cc7c194 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2020.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2020-January/001191.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.33 and above and requires PHP 7.2 or above. * Updated to cldr 36. * Prevent duplicate translation unit error from showing twice. ([[phab:T236153|Phab:T236153]]) * Add secondary check before displaying tpt-unknown-page error. ([[phab:T221119|Phab:T221119]]) * Display an error message if translation aids fail to load. ([[phab:T221119|Phab:T221119]]) * Improve message group selector performance reducing Translate API request time. ([[phab:T236904|Phab:T236904]]) * Update setlang to display confirmation dialog to change language. ([[phab:T63115|Phab:T63115]]) ---- ===== 2019.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.10.tar.bz2 * sha256sum: b7d6afdb365c7333829ab5b4e286c2f28e3a5f6f48d1584c1f43439e74a60de6 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2019-October/001188.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.32 and above and requires PHP 7.1.0 or above. * PHP entry point has been deprecated. To load the Translate extension, please use the following, <pre>wfLoadExtension( 'Translate' );</pre> * Removed deprecated and unmaintained SolrTTMServer. Recommendation is to migrate to ElasticSearch. ([https://phabricator.wikimedia.orgT87985 Phab:T87985]) * Dropped support for HHVM. ---- ===== 2019.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.07.tar.bz2 * sha256sum: 84cb6de241f62c7e5e9853d74390c4ffbf55cf35aab930c36f9ec5733a351130 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2019-July/001186.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.32 and above and requires PHP 7.0.0 or above. * Update to cldr 35.1 ([https://phabricator.wikimedia.org/T220906 T220906]). * Translate and UniversalLanguageSelector now requires MediaWiki >= 1.32.0. Please upgrade! * Added a new MessageValidator framework to improve translation validation. ([https://phabricator.wikimedia.org/T204568 T204568]) ([[Help:Extension:Translate/Validators|See documentation]]). * Fixed invalid more warnings label shown during message translation ([https://phabricator.wikimedia.org/T220789 T220789]) * Added several African keyboards in UniversalLanguageSelector. ---- ===== 2019.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.04.tar.bz2 * sha256sum: 5fbbd39acd1cc0e1edbd542a390daf1992d1526134ceb69248cdb4dced58f3a9 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2019-April/001180.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.31, 1.32 and above and requires PHP 7.0.0 or above. * PHP entry point has been removed for CleanChanges and cldr. Warning will be displayed for deprecated PHP entry point. (T140007) * Fixed fatal error on PageContentLanguage hook subscriber (T214358) * Fixed broken Special:PageMigration (T217727) * Added support for newer versions of the Elastica extension while maintaining backward compatibility for older version REL 1.31 (T218100) * Added multiple new keyboard layouts in UniversalLanguageSelector. ---- ===== 2019.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.01.tar.bz2 * sha256sum: 39f2e946e360ac868744dc8e6f62cb5723447415bd11bcbb4911eb0f3674360c [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2019-January/001177.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.31, 1.32 and above and requires PHP 5.5.9 or above. * $wgTranslateCC is deprecated now. It should be replaced by TranslatePostInitGroups hook. (T212836) * Added proofreading to (Language|MessageGroup)Stats. The statistics table also has updated styling. (T41279) * Skipping messages Special:Translate's page mode no longer sometimes marks the translation proofread. (T206748) * Translatable subpages are no longer moved when moving parent. (T114592) * Message group stats updating was broken in multiple ways. (T134252, T208521) * Added multiple new keyboard layouts in UniversalLanguageSelector. ---- ===== 2018.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.10.tar.bz2 * sha256sum: c0a65956d4f8e49ba1b401372636b9575a5c17fbf2501fa14ff1c265dd778862 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2018-October/001175.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.30, 1.31 and above and requires PHP 5.5.9 or above. * Updated cldr to version 34.0 * LocalisationUpdates and UniversalLanguageSelector has removed PHP entry point. Please update your configuration! * Fixed an error in Translate that prevented Special:PageMigration from working. * UniversalLanguageSelector now supports UI language change when Global Preferences are present. (T198206) * UniversalLanguageSelector dropped support for discontinued freegeoip.net. ---- ===== 2018.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.07.tar.bz2 * sha256sum: 36aa80c78be6dcfb533f96dc25afdabd2fd4716452c1b5a6f2bc982def1af7bc [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2018-July/001168.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.30, 1.31 and above and requires PHP 5.5.9 or above. * Updated cldr to version 33. * Special:SupportedLanguages: List of authors is now sorted by the number of contributions. * Message keys coming from external files are now handled with more care and less likely to produce invalid or inaccessible pages. ([[phab:T193023|T193023]]) * refresh-translatable-pages.php script can now use JobQueue, which is more efficient on wikis with thousands of translatable pages. ([[phab:T195347|T195347]]) * Custom languages defined in $wgExtraLanguages now always appear in Special:Translate and Special:SearchTranslations. ([[phab:T112889|T112889]]) ---- ===== 2018.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.04.tar.bz2 * sha256sum: e8b4da822b2dcc7906e444a65e8924d8505c028c8636cdfe8d38059dc9ef1d1c [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2018-April/001164.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.29, 1.30 and above and requires PHP 5.5.9 or above. * Fixed compatibility with MediaWiki 1.29 release. * Added the 'translate' right to the 'editpage' grant. This will allow OAuth apps to translate. * Translation variables can now span multiple lines. * AndroidXml file format now includes authors. * Fixed Ctrl-Clicking in Compact Language Links. ([[phab:T189582|T189582]]) * ULS trigger and settings are more keyboard accessible now. ([[phab:T52793|T52793]]) * Language search results are not grouped by region. ---- ===== 2018.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.01.tar.bz2 * sha256sum: a6d90633cf16dbf48c0481d1e073130717d98b9540c0d1b80059bb34946c6749 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2018-January/001155.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.29, 1.30 and above and requires PHP 5.5.9 or above. * Translation filter is now part of the new recent changes interface if the new interface is available. * Almost all legacy non-TUX code has been removed from Translate. * Removed non-default webfonts for some languages in UniversalLanguageSelector. * User interface and search improvements in UniversalLanguageSelector. ---- ===== 2017.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.10.tar.bz2 * sha256sum: 75eefff3bbf50f1f84232f45ab169d2eedea5f7a18994f85b43237f2145403b1 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2017-October/001151.html|Announcement and Release Notes]] * Compatible with MediaWiki 1.28, 1.29 and above and requires PHP 5.5.9 or above. * Translate, Universal Language Selector and Babel received style updates. * Search for languages in Universal Language Selector was improved. * Translate extension received multiple compatibility fixes. ---- ===== 2017.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.07.tar.bz2 * sha256sum: c050c326bfa56d326fece072bed5e4be3e3ad3289b0a449313a2e7dbc4514c55 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2017-July/001132.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.27, 1.28 or above and requires PHP 5.5.9 or above. * Translate extension no longer bundles spyc library. If you need support for parsing and generating YAML files, and you don't have phpyaml extensions installed (HHVM provides it in PHP compatibility mode), then you can install spyc using composer update. * Information about the languages that the user knows in Babel is now cached to improve performance. * It is now possible to load Babel information from a Babel box on a global user page. * Compact Language Links the ability to show languages that logged-in users specified in the Babel box. * Several new IMEs are added and improved in UniveralLanguageSelector. ---- ===== 2017.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.04.tar.bz2 * sha256sum: 4207398d7ed3ea9c793f35f88e75f29672b33aee4d0baf01afc869517c629c65 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2017-April/001120.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.27, 1.28 or above and requires PHP 5.5.9 or above. * CLDR updated to version 31. * Support for Elastic5, Multi-DC for TTMServices, freezing writes added in Translate. * Import of the new translations in Special:ImportTranslations is fixed now. * Several new IMEs are added in UniveralLanguageSelector. ---- ===== 2017.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.01.tar.bz2 * sha256sum: 89f4a029f33ea9f9225c8379367bc526fa63353845a2873290ba82560fb314c9 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2017-January/001099.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.27, 1.28 or above and requires PHP 5.5.9 or above. * Several improvements in Translate editor, MessageTable and Special:TranslationStats * SpecialPage(Preparation|Migration) are moved to tag. * jquery.i18n library is removed from UniveralLanguageSelector, which is now available in MediaWiki core since 1.26 release. ---- ===== 2016.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.10.tar.bz2 * sha256sum: f82ac16b1a71433d68066c684c2e67379d3c435d1938044a9f0f0582cb6549b3 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2016-October/001089.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.26, 1.27 or above and requires PHP 5.5.9 or above. * Easy way to access wikitext editor from Special:Translate. T48955 * Special:Translate now works with MobileFrontend. T102922 * Special:Translate now works better in mobile devices. T146134 * WebAPI module to query user's babel languages. * The style of ULS's dialogs have been updated and polished to be more streamlined (for real this time, was incorrectly claimed to be included in 2016.08). ---- ===== 2016.08 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.08.tar.bz2 * sha256sum: aba09ead5f2c646e5960ce2aecc36866ee092079f51598d0aab461c7655410da [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.08.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2016-August/001084.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.26, 1.27 or above and requires PHP 5.5.9 or above. * Translate extension now requires Elastica extension for ElasticSearch support. Wikimedia search plugin needs to be installed for ElasticSearch 2.x series. * Special:Translate now has a summary field. * Special:Translate is much more robust thanks to improved error handling and to many small bugs having been fixed. * Page translation is much more robust. * The sandbox feature of Translate extension requires MediaWiki 1.27 or newer. * Translate's export functionality is now on separate special page called Special:ExportTranslations * The style of ULS's dialogs have been updated and polished to be more streamlined. * The default geoip service for Universal Language Selector is changed because the old service is discontinued. * Major update on webfont formats: woff2 format added, eot and svg formats dropped. ---- ===== 2016.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.04.tar.bz2 * sha256sum: 113439ad94b1a75ab8616f41c4d120e12c1fa8c3888933ec136783bfbdc9bc70 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2016-April/001061.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.25, 1.26 or above and requires PHP 5.5.9 or above. * Babel and LocalisationUpdate ** Extensions now uses extension registration. * CLDR: ** Updated to CLDR 29 release. * Translate: ** Message group selector now works in Internet Explorer and Edge browsers. ** [[phabricator:T48716|A bug was fixed that sometimes caused translation pages not to update changes to the source page after marking it for translation]]. After upgrading it is recommended to run scripts/refresh-translatable-pages.php to ensure no pages contain outdated content. * UniversalLanguageSelector: ** Fixed issues related to the tooltip shown for language settings that sometimes caused JavaScript errors. ** Input methods now work with VisualEditor. ---- ===== 2016.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.01.tar.bz2 * sha256sum: 7a46bb96f852aa42f728c68e4e21558878c8cba703ce9f8f6c2316af7bbe03e3 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2016-January/001047.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.25.x and 1.26.x. * CLDR: ** cldr is converted to extension registration. Please update your LocalSettings.php! * Translate: ** Old custom tokens were deprecated in favor of using regular "csrf" (previously known as "edit") token. If you are using Translate WebAPIs you might need to migrate. ** Special:Translations no longer shows PHP notices for pages with invalid language codes * UniversalLanguageSelector: ** ULS now uses extension registration and thus requires MediaWiki 1.25 or later. ** Input methods should now work inside Visual Editor. ** Various fixes in fonts and input methods. ---- ===== 2015.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.10.tar.bz2 * sha256sum: 482595d35ab02fdc40c6ae54d2cf21aa22360f7021d498c054624ccdbf721237 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-October/001029.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.24.x and 1.25.x. * CLDR: ** Updated to CLDR 28. * Translate: ** MediaWiki 1.23 is no longer supported. Extension is no longer automatically loaded when installed via composer. ** If local TTMServer translation memory is marked as public, it will <s>not</s> '''now''' automatically take advantage of TranslationWebServices query parallelization. * UniversalLanguageSelector: ** MediaWiki 1.23 is no longer supported. Extension is no longer automatically loaded when installed via composer. ** Language change is now done in two phase: first changed with API, then page is reloaded. The 'setlang' URL parameter is no longer used, although it still works. Due to the change, language switching might take a slightly longer than previously. ---- ===== 2015.08 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.08.tar.bz2 * sha256sum: 21cb43509d1e6da3cadc7e594866215d430e110aea5d04857e5cffd2a69db031 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.08.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-August/001009.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x, 1.24.x and 1.25.x. * Translate: ** Special:SearchTranslations has acquired lots of new features, such as cross language search. To take advantage of all the new features, you need to reindex the index with "php scripts/ttmserver-export.php --reindex". You also need to update ruflin/elastica to 2.2.0 or later, or recent version of CirrusSearch which bundles it. * UniversalLanguageSelector: ** ULS will use jQuery.i18n from MediaWiki core if available. ** Updated the default geoiplookup URL. ** ULS supports extension registration now. ** New Input Methods and fonts are added. ---- ===== 2015.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.04.tar.bz2 * sha256sum: 0aaae92b987130068b9fc03595428286d96541a947cbd137147ae7c0f50d9241 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-April/000985.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * Babel: ** Restore compatibility with MediaWiki 1.24 and older version. * CLDR: ** Update to CLDR 27.0.1 * Translate: ** Styled search result navigation buttons in Special:SearchTranslations ** Fixed Special:PagePreparation, now works better and has autocompletion * UniversalLanguageSelector: ** Show the Common language section only if the list is long enough. ** Make ULS IME working in Content Translation. ---- ===== 2015.03 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.03.tar.bz2 * sha256sum: 938444aecd01df92d340e69b0f1c341de7085269bf5e6bbb28b82f41e816cc6d [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.03.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-March/000979.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * LocalisationUpdate: ** A bug that prevented extension and skin i18n files to be updated is fixed now. * Translate: ** Improvements in the message group selector. * UniversalLanguageSelector: ** Fixed issues related to the tooltip for ULS cog (trigger icon at the sidebar interlanguage position). ---- ===== 2015.02 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.02.tar.bz2 * sha256sum: 536cf86e7080d8293a02cb59f99d96328c7009c8239e818556b28b77b02ff88d [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.02.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-February/000976.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * Translate: ** Improvements in Special:PagePreparation. ** Performance improvements by removing unneeded queries. * UniversalLanguageSelector: ** Restore compatibility with IE8. If you still have any issue, please report it! ---- ===== 2015.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.01.tar.bz2 * sha256sum: 7a53ed826ae14ffe279fc4231cc47d367f668723a5843ad62c13a8f17d339744 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2015-January/000967.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * LocalisationUpdate: ** Added support for updating skins. * Translate: ** Added Content Translation Machine Translation backend support. ** Message group configurations are now optionally validated. ** Make 'fuzzy' as a default action for changes in source language in Special:ManageMessageGroups. * UniversalLanguageSelector: ** This version has compatibility issues with Internet Explorer 8. Support will be restored in the next MLEB release. ---- ===== 2014.12 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.12.tar.bz2 * sha256sum: 5a0e00d27e2a81b896de4015a8f0933f24ea3409e554b0ba7f2e3c27ec27430f [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.12.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-December/000959.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * Translate: ** Due to MediaWiki core plural rule changes, Translate extension contains interface translations which are not compatible with any released version of MediaWiki. If you are using Translate in the affected languages, (See https://blog.wikimedia.org/2014/11/04/updates-in-mediawiki-internationalization-reflect-changes-from-cldr/ for more details and list of affected languages) you might want to consider using MLEB 2014.09 instead. The issue manifests as incorrect plural forms used in the interface for certain numbers. ** T76184: Improvements in ElasticSearch TTM. Query results are now more reliable and consistent. * UniversalLanguageSelector: ** As a part of refactoring ULS design, world map from ULS has been removed. You can track progress of task at https://phabricator.wikimedia.org/T85519 ---- ===== 2014.11 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.11.tar.bz2 * sha256sum: 39b397a05561f743962cfb499f59a58219338607ea13ebfcc7a8806105e7dedc [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.11.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-November/000947.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.23.x and 1.24.x. * CLDR: ** Fixed some time displays if CLDR had only partial localisation of time units. * Translate: ** Translate WebAPI documentation is now localized. Only works in MediaWiki 1.24 and newer. ** If you are using the '''Solr backend '''for the translation memory or the translation search, please let us know. If there are no users for the Solr backend, we will deprecate and later remove it in favor of the better maintained ElasticSearch backend. * UniversalLanguageSelector: ** ULS WebAPI documentation is now localized. Only works in MediaWiki 1.24 and newer. ** T67516: Removed font-size for ULS language selection panel buttons, which caused tiny font sizes on the Monobook skin. ** Small compatibility fix when both ULS and VisualEditor are in use. ** About 20 new languages are now supported in the language selector and a couple language names were changes. ** Added support for WOFF2 webfont format. Note that there are no WOFF2 webfonts in the font repository yet due to pending issues in WOFF2 font generation. ---- ===== 2014.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.10.tar.bz2 * sha256sum: 49707823ec19d9eed1c21c37550a3b0a2c81ff83855aea2706287a5169e90468 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-October/000936.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.22.x and 1.23.x. * CleanChanges: Added support for ULS in language filter selector. * Translate: * New feature: Remove any page from translation with two clicks from Special:PageTranslation. Previously, translate tags had to be removed manually first. * Special:PageTranslation also has prettier warning and error notifications. * The user group translate-proofr is no longer created by default. If you were using it, you can add it back with following code in your LocalSettings.php: $wgGroupPermissions['translate-proofr']['translate-messagereview'] = true; $wgAddGroups['translate-proofr'] = array( 'translate-proofr' ); * Removed $wgTranslatePageMigration (enabled by default), $wgTranslateUseTux (no longer in use) and translate-proofr group (needs sysadmin action if in use). ---- ===== 2014.09 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.09.tar.bz2 * sha256sum: 9cfdc7d4fc87b4cd6f8d1d2e1593b8cd064b7a9a2773c1a6a554304949a609ec [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.09.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-September/000920.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.22.x and 1.23.x. * CLDR is updated to 26. * Translate: * Regression fixed: Translate's compatibility with MediaWiki 1.22 has been restored. * Regression fixed: Fix translation ratios in translatable page language selector. * Special:MyLanguage is now in core. For backwards compatibility, translations of Special:MyLanguage aliases were moved to a separate file (Bug 69461). * $wgTranslatePageTranslationULS now works as intended on all translation pages by removing the language code from the page name. ---- ===== 2014.08 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.08.tar.bz2 * sha256sum: f4663910facd2b34d4afb1af930f66adad22b2746f9395f7706f07751e633857 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.08.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [[mailarchive:mediawiki-i18n/2014-August/000911.html|Announcement and Release Notes]] * Compatible with MediaWiki: 1.22.x and 1.23.x. * Added Comic Neue font. It is available for English and other languages using the latin alphabet. * Translate ** Breaking change: Dropped support for MediaWiki 1.21 (2014.05 is the latest version of MLEB as a whole which supports 1.21) ** Avoid losing translators' edits: improved handling of expired sessions ({{bug|69314}}). ** Restore progress icon for the current translation page (regression from MLEB 2014.07). ---- ===== 2014.07 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.07.tar.bz2 * sha256sum: 8af5c001db9375bf8dfd16495c7a88fc8dc9b4fe281b1048f6bea6c490bc4a9d [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-July/000902.html Announcement and Release Notes] * Compatible with MediaWiki: 1.22.x and 1.23.x. * Updated to CLDR 25 and fixed rebuild script. * Display source language for the pages in Special:Translate * Fixed ElasticSearchTTMServer to not return matches for single word messages only. * Stopped using deprecated jquery.json module, this will make ULS slightly smaller. * Added Ludic (lud) transliteration and Tibetian (bo) EWTS layouts. ---- ===== 2014.06 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.06.tar.bz2 * sha256sum: 02721b25e8c8fe06889b825a1c03fc4c1b1e4268d1e56169815983b5e87e8932 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.06.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-June/000893.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.22.x and 1.23.x. ** Translate: New feature, Special:PageMigration page has been added and feedback is welcome! ** Translate: Email notifications are no longer sent upon translation review. ** Translate: Regression fix: Message checker live updates is working again with this release. ---- ===== 2014.05 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.05.tar.bz2 * sha256sum: f53030ce7e6e0619f9a075877bc85423c0a28f46ffb296dbed5733502683b9b3 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.05.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-May/000881.html Announcement and Release Notes] * Compatible with MediaWiki: 1.21.10 and 1.22.7. * Translate: When a user is promoted from translator sandbox, it is treated as account creation. Promoted users can now receive NewUserMessage. * CLDR: The fallback logic should not merge the time units from languages in fallback chain. It should use time units from a fallback language only when time units are not defined. * Always display assistant languages in compact language list when defined by user in Translate extension. * Added 'Hussaini Nastaleeq' font for Urdu. ---- ===== 2014.04 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.04.tar.bz2 * sha256sum: f20631d2629e0cf80df8ca022e6eec4d6d784e0cd39799f9fd46f338f4a7381a [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.04.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-April/000866.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.9 and 1.22.6. ** LocalisationUpdate now updates messages for older MediaWiki versions. ** Set JSON message format as default for MediaWiki extensions. ** Allow overriding the header styles from typography refresh. ** Added Batak input method. ---- ===== 2014.03 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.03.tar.bz2 * sha256sum: f3a253e05f6b7c4f451882a1a78a138a1dcaecd2777237d0c2b8af7c3ecced70 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.03.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-March/000838.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.7 and 1.22.4. ** LocalisationUpdate is rewritten for JSON file format support for extensions. This is compatible with MediaWiki 1.19 and above. ** ULS adds compact language links as new BetaFeature. ---- ===== 2014.02 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.02.tar.bz2 * sha256sum: 5c5636332b38a7ce9ac12fac74f0402afdc592aa58795b51dc4747877db340da [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.02.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-February/000808.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.5 and 1.22.2. ** Added AppleFFS module for iOS/Mac OS X Localizable.strings files ** Detect tofu before applying any default fonts. See: https://www.mediawiki.org/wiki/Universal_Language_Selector/WebFonts#How_webfonts_are_applied.3F for technical documentation about how tofu detection works in ULS. ** ULS is now much lighter for the browser thanks to many changes (see full Release Notes) ---- ===== 2014.01 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.01.tar.bz2 * sha256sum: 2dc673ba0bbc43a3d69237c15600171e85d3c56d9ff520e5bdb3eda0f2fdc74a [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.01.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2014-January/000803.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.5 and 1.22.2. ** Refactoring and performance improvements in ULS. ** Regression fixes introduced in previous MLEB release in Translate. ** Initial plural support for Android file format. ---- ===== 2013.12 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.12.tar.bz2 * sha256sum: 2ef19e31d685dd0d6e50088ec8bbb1cd3e74c694096dfa333efb61dcfee9c3c0 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.12.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-December/000791.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.21.3 and 1.22.0. ** Refactoring and performance improvements in Translate Sandbox and TUX. ** Added support to MediaWiki localisation format from PHP files to JSON files. ** Language selector now opens an order of magnitude faster. ** Initial support for webfonts in MobileFrontend. ---- ===== 2013.11 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.11.tar.bz2 * sha256sum: 926bdcb6aa9cc405dc54275a60fd1d13836ee0f36a1e9c1329f4f7eed94354ce [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.11.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-November/000772.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.20.7 and 1.21.2. ** Lots of cleanup, refactoring and performance improvements: ** The ResourceLoader modules for ULS were redone. They are now lazy-loaded to improve the initial page loading time. To use features provided by ULS, such as styles, ULS data utils functions, and others, you must load the features separately in your extensions. See https://www.mediawiki.org/wiki/Universal_Language_Selector/Developing_with_ULS for more details. ** Cleanup, refactoring and performance improvements in Translate extension. ---- ===== 2013.10 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.10.tar.bz2 * sha256sum: 04b1a1db293439553c225765a41add5f0bcd3ad4dce7f89e1f098276470e96c4 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.10.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-October/000762.html Announcement and Release Notes] ** Compatible with MediaWiki: 1.20.7 and 1.21.2. ** Use the Autonym font for language autonyms in the Language Search box and Interlanguage links. ** Introducing of the TranslationStash feature. It's the place where sandboxed users can store their translations before they are given full translator rights. ---- ===== 2013.09 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.09.tar.bz2 * sha256sum: 2ac55639aeb43a6f3d198a87e10111f673eae1115225de072be73a1fa2052ab2 [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.09.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-September/000751.html Announcement and Release Notes] ** Compatible with MediaWiki 1.20.7 and MediaWiki 1.21.2. ** The latest development efforts are about fixing known bugs and improving performance. ** Added initial support for insertables. This will be helpful in typing and copy-paste of syntax like $1 and plural especially on tablets (bug 38350). More about this feature at: http://laxstrom.name/blag/2013/09/18/insertables-in-translate-extension-make-translating-easier/ ** CLDR is updated to version 24. ---- ===== 2013.08 ===== * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.08.tar.bz2 * sha256sum: 21b3abf3a8e19d0c746d41d246e4bc8883d0f5e179d894e1720500031c621f2c [https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.08.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-August/000732.html Announcement and Release Notes] ** The latest development efforts are about fixing known bugs, improving performance and adding fonts. ** EventLogging support has been added to ULS. ** Several bugs were fixed in the Translate extension. ---- ===== 2013.07 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.07.tar.bz2 * sha256sum: ca381ea1bc1f10c56df28353f91a25129c604ff11938b424833925e8716e2ff3 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.07.tar.bz2.sha256sum <nowiki>[1]</nowiki>] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-July/000725.html Announcement and Release Notes] ** The ULS is stabilizing. The latest development efforts are about fixing known bugs, improving performance, and adding fonts. ** Several bugs were fixed in the Translate extension. ** Support for Yandex Translate API v1.5 was added to Translate. ---- ===== 2013.06 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.06.tar.bz2 * sha256sum: 6df32382ddec91ab61e3e74f2ede6c043220d5c1252ee3baf8efd1d6403b4d82 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.06.tar.bz2.sha256sum] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-June/000719.html Announcement and Release Notes] ** The "interlanguage" mode in ULS, which shows the ULS trigger as a cog icon in the interlanguage links area, is now considered stable. It can be enabled by setting $wgULSPosition to 'interlanguage'. ** Several bugs were fixed in the Translate extension. ** Support for currency was added to the CLDR extension. ---- ===== 2013.05 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.05.tar.bz2 * sha256sum: 9aea5b1dac2b38e44284373c849241fc694c78caff1d3ca3b4e6e72d66f2ab12 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.05.tar.bz2.sha256sum] *[http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-May/000699.html Announcement and Release Notes] ** The [[wmfblog:2013/03/25/redesigning-the-translation-experience-an-overview/|new translation interface]], known as Translate UX, is considered stable. Several bugs were fixed. ** Some design changes were introduced to the Universal Language Selector. Work continued on the "interlanguage" mode, which shows the ULS trigger as a cog icon in the interlanguage links area. It can be enabled, but is still experimental. A known issue is [[:bugzilla:48898|bug 48898]] - the "Apply settings" button doesn't close the Input settings panel after enabling or disabling the settings. The settings are saved, but the button doesn't work correctly. ** CLDR was updated to version 23.1. ---- ===== 2013.04 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.04.tar.bz2 * sha256sum: bd6aca60101308f429d90d421e35093328e7a05ea74d35c05a98474ab648dec4 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.04.tar.bz2.sha256sum] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-April/000677.html Announcement and Release Notes] ** The [[wmfblog:2013/03/25/redesigning-the-translation-experience-an-overview/|new translation interface]], known as Translate UX, is being improved. In particular, several bugs affecting Microsoft Internet Explorer users were fixed. ** The ''UniversalLanguageSelector'' extension is compatible with MediaWiki 1.20.4. It is not compatible with previous versions of MediaWiki. ---- ===== 2013.03 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.03.tar.bz2 * sha256sum: be4c6b5f80e27396555dc09cef0cec92c78cca9eeef796a230da281734738810 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.03.tar.bz2.sha256sum] * [http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-March/000631.html Announcement and Release Notes] ** '''The [[wmfblog:2013/03/25/redesigning-the-translation-experience-an-overview/|new translation interface]], known as Translate UX, is now the default.''' It can be disabled by setting $wgTranslateUseTux to <code>false</code> in LocalSettings.php. **The [[:File:Translate_manual_-_Page_example_-_15._Translate_fuzzied.png|diff feature]] on all old outdated translations is [[bugzilla:46562|temporarily broken]] until all such old "fuzzy" messages are updated. ** '''The ''UniversalLanguageSelector'' extension is updated to the latest version'''. It is compatible with MediaWiki 1.20.3. It is not compatible with previous versions of MediaWiki. ---- ===== 2013.02 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.02.tar.bz2 * sha256sum: 7fece850483e2b74539f69b461501d26487290293ae93b40cd31d6e96f90d112 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.02.tar.bz2.sha256sum] * [http://permalink.gmane.org/gmane.org.wikimedia.mediawiki.i18n/640 Announcement and Release Notes] * '''UniversalLanguageSelector is rolled back to the 2012.12 version''' for compatibility with MediaWiki 1.20 because of a [[gerrit:44001|known issue]] where, with UniversalLanguageSelector enabled, preferences are not saved for logged-in users. Wait for 1.20.3 or [https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=snapshot;h=refs/heads/REL1_20;sf=tgz use only with the last revision of the 1.20 branch]. ---- ===== 2013.01 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.01.tar.bz2 * sha256sum: 55adb8b1a5197570fe76501454a66d2f1581bd6854e4091e2b56545a6d072d0b [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.01.tar.bz2.sha256sum] * [http://comments.gmane.org/gmane.org.wikimedia.mediawiki.i18n/618 Announcement and Release Notes] * '''Compatible only with MediaWiki 1.21alpha'''. 1.20.2 has a [[gerrit:44001|known issue]] where, with UniversalLanguageSelector enabled, preferences are not saved for logged-in users; wait for 1.20.3 or [https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=snapshot;h=refs/heads/REL1_20;sf=tgz use only with the last revision of the 1.20 branch]. ---- ===== 2012.12 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2012.12.tar.bz2 * sha256sum: d27fdbbcdd73795914c6f6a8bdddedc3cea06c1ce968b9420f28028fda191a92 [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2012.12.tar.bz2.sha256sum] * [http://comments.gmane.org/gmane.org.wikimedia.mediawiki.i18n/599 Announcement and Release Notes] * Compatible with MediaWiki 1.20 and 1.21alpha ---- ===== 2012.11 ===== * Download: http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2012.11.tar.bz2 * sha256sum: 924e95b8d5b1c9cef17f72ffe141b06df310ca2cbe013816b5fb69b09732763a [http://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2012.11.tar.bz2.sha256sum] * [http://comments.gmane.org/gmane.org.wikimedia.mediawiki.i18n/592 Announcement and Release Notes] * Compatible with MediaWiki 1.20 and 1.21alpha </noinclude> jpwdhjhyqsooyoxcmyv03st5pptrhe2 Template:Bundled 10 642445 5387158 5082537 2022-07-28T21:08:41Z 156.196.138.115 Replaced content with "<noinclude> <languages/> </noinclude}}]] </noinclude>" wikitext text/x-wiki <noinclude> <languages/> </noinclude}}]] </noinclude> 5i8owv2ezt9pu03wzeddjamyvqhr5ju 5387159 5387158 2022-07-28T21:09:01Z 156.196.138.115 wikitext text/x-wiki MediaWiki 7s5xorark1ez4r32vwpguyqzy6nuhj6 5387253 5387159 2022-07-28T21:34:47Z Shirayuki 472859 Reverted edits by [[Special:Contribs/156.196.138.115|156.196.138.115]] ([[User talk:156.196.138.115|talk]]) to last version by Tacsipacsi wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{note |1={{#ifeq:{{{type|}}}|skin |<translate><!--T:14--> This skin [[<tvar name=mwversion>Special:MyLanguage/MediaWiki {{{1|{{MW stable branch number}}}}}#Bundled extensions</tvar>|comes with MediaWiki <tvar name=mwversion2>{{{1|{{MW stable branch number}}}}}</tvar>]] and above.</translate> |<translate><!--T:1--> This {{<tvar name=1>#if:{{{type|}}}|{{{type}}}</tvar>|extension}} [[<tvar name=mwversion>Special:MyLanguage/MediaWiki {{{1|{{MW stable branch number}}}}}#Bundled extensions</tvar>|comes with MediaWiki <tvar name=mwversion2>{{{1|{{MW stable branch number}}}}}</tvar>]] and above.</translate> }} <!-- --><translate><!--T:3--> Thus you do not have to download it again.</translate> <!-- --><translate><!--T:4--> However, you still need to follow the other instructions provided.</translate> }}<includeonly>{{#if:{{{nocat|}}}||[[Category:{{{type|extension}}}s bundled with MediaWiki {{#if:{{{1|}}}|{{{1}}}|{{MW stable branch number}}}}{{#translation:}}]]}}</includeonly><!-- --><noinclude> {{Documentation|content= <translate> == Usage == <!--T:2--> </translate> {{Bundled/doc}} <translate> == Maintenance == <!--T:7--> </translate> * [https://www.mediawiki.org/w/index.php?title=Special:Search&limit=500&offset=0&ns102=1&ns106=1&search=Extension%3A+insource%3Abundled+insource%3A%2F%5C%7B%5C%7B%28TNT%5C%7C%29%3F%5BBb%5Dundled%5C%7C%2F+-intitle%3A%22%2Fen%22+inlanguage%3Aen&advancedSearch-current=%7B%22options%22%3A%7B%22inlanguage%22%3A%22en%22%7D%2C%22namespaces%22%3A%5B%22102%22%2C%22106%22%5D%7D <translate><!--T:8--> Extension/skin pages using this template</translate>] * [https://www.mediawiki.org/w/index.php?search=Extension%3A+insource%3Abundled+insource%3A%2F%5C%7B%5C%7B%28TNT%5C%7C%29%3F%5BBb%5Dundled%5C%7D%5C%7D%2F+-intitle%3A%22%2Fen%22+inlanguage%3Aen&title=Special:Search&profile=advanced&fulltext=1&advancedSearch-current=%7B%22options%22%3A%7B%22inlanguage%22%3A%22en%22%7D%2C%22namespaces%22%3A%5B%22102%22%2C%22106%22%5D%7D&ns102=1&ns106=1 <translate><!--T:9--> Extension/skin pages using this template with no version specified</translate>] * [https://phabricator.wikimedia.org/diffusion/MREL/browse/master/make-release/settings.yaml <translate><!--T:10--> Extensions/skins that are currently bundled</translate>] <translate> == Examples == <!--T:5--> </translate> * <code><nowiki>{{Bundled}}</nowiki></code> {{Bundled|nocat=1}} * <code><nowiki>{{Bundled|1.21}}</nowiki></code> {{Bundled|1.21|nocat=1}} * <code><nowiki>{{Bundled|1.18|type=skin}}</nowiki></code> {{Bundled|1.18|type=skin|nocat=1}} <translate> == See also == <!--T:6--> </translate> * {{ll|Category:Extensions bundled with MediaWiki}} }} [[Category:Extension templates{{#translation:}}]] </noinclude> pilegpnwllarub8kl4ch3a6jvuh65p9 Translations:Universal Language Selector/FAQ/92/de 1198 650276 5386730 2344579 2022-07-28T18:50:13Z ThisCarthing 17456337 wikitext text/x-wiki In Fällen, in denen die Erweiterung $1 installiert wurde, kann diese dahingehend konfiguriert werden, den Benutzer zu bestehenden Übersetzungen der Seite zu schicken, wenn das ULS die Sprache der Schnittstelle verändert hat. 56sxjc824l0pnyrrwfnuz60omyyxj8z Translations:Manual:Installing MediaWiki/3/ja 1198 653701 5387217 2360208 2022-07-28T21:20:04Z Shirayuki 472859 update wikitext text/x-wiki MediaWiki は、Apache (Web サーバー ソフトウェア)、PHP、MySQL/MariaDB (データベース) の経験がない場合、インストールが困難な場合があります。 iow7nljj6y2yfva0eidzdp3pfvg1vj1 Template:Empty section 10 654137 5387607 3859827 2022-07-29T03:27:02Z Ilovemydoodle2 17636692 standardized/clearer wording wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch:<translate></translate> | = {{notice|1=<translate><!--T:1--> This section is empty.</translate> <translate><!--T:2--> You can help MediaWiki.org by expanding it.</translate>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> 94jhgmsvi7z4j9y9xqtm36e9ee83twn Manual:Pywikibot/Compat/articlenos.py/zh 100 662120 5387561 4182269 2022-07-29T03:01:48Z GuGuMur 17451226 Created page with "文件<code>'''articlenos.py'''</code>是一个用于展示在[[特殊:最近更改]]页面中正在创建的新文章的序号的脚本" wikitext text/x-wiki <languages/> {{Pywikibot/Compat}} 文件<code>'''articlenos.py'''</code>是一个用于展示在[[特殊:最近更改]]页面中正在创建的新文章的序号的脚本 <span lang="en" dir="ltr" class="mw-content-ltr">The script doesn't make any edits, no bot account needed.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The script requires the Python IRC library http://python-irclib.sourceforge.net/</span>}} [[Category:Pywikibot compat scripts{{#translation:}}|articlenos]] 1cn0n3musz7uoxuygr16pna9lvljx6e 5387563 5387561 2022-07-29T03:02:20Z GuGuMur 17451226 wikitext text/x-wiki <languages/> {{Pywikibot/Compat}} 文件<code>'''articlenos.py'''</code>是一个用于展示在[[特殊:最近更改]]页面中正在创建的新文章的序号的脚本。 <span lang="en" dir="ltr" class="mw-content-ltr">The script doesn't make any edits, no bot account needed.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The script requires the Python IRC library http://python-irclib.sourceforge.net/</span>}} [[Category:Pywikibot compat scripts{{#translation:}}|articlenos]] kndeqdny8uqnugt3nrbo8n2tfi6dfia 5387565 5387563 2022-07-29T03:02:56Z GuGuMur 17451226 Created page with "使用这个脚本不需要进行任何编辑行为,亦不需要任何[[Project:Bots|bot账户]]。" wikitext text/x-wiki <languages/> {{Pywikibot/Compat}} 文件<code>'''articlenos.py'''</code>是一个用于展示在[[特殊:最近更改]]页面中正在创建的新文章的序号的脚本。 使用这个脚本不需要进行任何编辑行为,亦不需要任何[[Project:Bots|bot账户]]。 {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The script requires the Python IRC library http://python-irclib.sourceforge.net/</span>}} [[Category:Pywikibot compat scripts{{#translation:}}|articlenos]] ow5zp6k0rlmd4e8geypvkyzofkh56h0 5387567 5387565 2022-07-29T03:03:32Z GuGuMur 17451226 Created page with "该脚本需要 Python IRC 库 $url" wikitext text/x-wiki <languages/> {{Pywikibot/Compat}} 文件<code>'''articlenos.py'''</code>是一个用于展示在[[特殊:最近更改]]页面中正在创建的新文章的序号的脚本。 使用这个脚本不需要进行任何编辑行为,亦不需要任何[[Project:Bots|bot账户]]。 {{Note|1=该脚本需要 Python IRC 库 http://python-irclib.sourceforge.net/}} [[Category:Pywikibot compat scripts{{#translation:}}|articlenos]] 8v7iy9su325z3d9dhrhqdu8uvrfeukr Manual:Installation guide/bn 100 662874 5386637 5381074 2022-07-28T17:14:22Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/bn]] lfmfm0a4cu3ore13kyigy8t3tx4048h 5386694 5386637 2022-07-28T17:30:14Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/bn]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Translations:Manual:Installing MediaWiki/19/ja 1198 663471 5387223 5350513 2022-07-28T21:25:32Z Shirayuki 472859 update wikitext text/x-wiki まだ、ウェブ サーバーにファイルをアップロードしていない場合は、今すぐアップロードしてください。(ウェブ サーバー ソフトウェアが $2 でローカルに動作していてまだコピーしていない場合は、今すぐコピーしてください。) iv21tnm9optedxu9a164rmgjiugbcp4 Translations:Manual:Installing MediaWiki/24/ja 1198 663476 5387225 4623243 2022-07-28T21:27:04Z Shirayuki 472859 update wikitext text/x-wiki Apache HTTPD Web サーバーを使用する場合、$conf ファイルの $3 ディレクティブで正しいディレクトリを指定します。 8exw7s4ekmnb47te4lbf4nocnnb7eko Translations:Manual:Installing MediaWiki/28/ja 1198 663487 5387227 5350543 2022-07-28T21:27:28Z Shirayuki 472859 update wikitext text/x-wiki あなたのウェブ サーバーが例えば $1 で動作している場合、ディレクトリ名を $2 に変更すればあなたのウィキは $index でアクセスできることになります。 jawv6h0po88okjz16c133z9vlnj9nh3 Translations:Manual:Installing MediaWiki/34/ja 1198 663493 5387235 5350569 2022-07-28T21:30:45Z Shirayuki 472859 update wikitext text/x-wiki 既にデータベース サーバーがあり、「root」(admin) ユーザーのパスワードを知っている場合は、下の [[$1|#Run the installation script]] の節まで読み飛ばしてください。 dp4litopdgjhq8spbi7u8jbtacdnzp9 Translations:Manual:Installing MediaWiki/36/ja 1198 663509 5387237 5350571 2022-07-28T21:31:42Z Shirayuki 472859 update wikitext text/x-wiki root ユーザーのパスワードを知らない場合、例えば[[$1|ホスティング サーバー]]にある場合、次の節で MediaWiki インストール スクリプトを実行する前に新しいデータベースを作成する必要があります。 a1gmc87zdvumjfxozshxaekp5pj2jys Translations:Manual:Installing MediaWiki/37/ja 1198 663510 5387239 5381347 2022-07-28T21:32:04Z Shirayuki 472859 update wikitext text/x-wiki データベースは、SQLite、MariaDB/MySQL、PostgreSQL に対応しています。 7qddtwxoujc9lxxncls8o20uyxre9h9 Translations:Manual:Installing MediaWiki/89/ja 1198 663519 5387245 2920586 2022-07-28T21:33:04Z Shirayuki 472859 update wikitext text/x-wiki MediaWiki リリース告知メーリングリストに登録する。 lpj0evqg0okbvuxr0b40nj0hsl0z3dm Translations:Manual:Installing MediaWiki/46/ja 1198 663521 5387233 2403777 2022-07-28T21:29:25Z Shirayuki 472859 update wikitext text/x-wiki MediaWiki の[[$1|インストール スクリプト]]はデータベース名とデータベース ユーザ名を尋ねるため、MediaWiki はウィキの内容を保存できます。 aecqfxsy1shw4iac3ofvun9otdbknwg Translations:Manual:Installing MediaWiki/75/ja 1198 663551 5387241 2403861 2022-07-28T21:32:23Z Shirayuki 472859 update wikitext text/x-wiki 多くの場合、このデータベース ユーザーのユーザー名は $1 です。 cw9ke3bhy359j1qgix0n52sva8zn4sl Template:Archive box/doc 10 666079 5387511 3064995 2022-07-28T23:19:23Z 50.44.36.47 MEMZAT10 {pp1.0} wikitext text/x-wiki {{Documentation subpage}} <!-- Categories go at the bottom of this page and interwikis go in Wikidata. --> == Usage == {| class="wikitable" |- ! code !! result |- | <pre>{{Archive box| * [[/Archive 1]] * [[/Archive 2]]}}</pre> || {{Archive box| * [[/Archive 1]] * [[/Archive 2]]}} |- | <code><nowiki>{{Archive box| [[/Archiv 1]] · [[/Archiv 2]]}}</nowiki></code> || {{Archive box| [[/Archiv 1]] · [[/Archiv 2]]}} |} <includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox|| <!-- Categories go here and interwikis go in Wikidata. --> }}</includeonly> This is a documentation subpage for Template:Archive box. It contains usage information, categories and other content that is not part of the original Template pag [[Special:Contributions/50.44.36.47|50.44.36.47]][[Special:MyLanguage/[[QRS]] T:1<tvar name=1>MEMZAT10</tvar> dtqx0r8dbfdsehil7w6c67dtc7z098g 5387746 5387511 2022-07-29T08:12:45Z P858snake 31302 Reverted edits by [[Special:Contribs/50.44.36.47|50.44.36.47]] ([[User talk:50.44.36.47|talk]]) to last version by Vermont wikitext text/x-wiki {{Documentation subpage}} <!-- Categories go at the bottom of this page and interwikis go in Wikidata. --> == Usage == {| class="wikitable" |- ! code !! result |- | <pre>{{Archive box| * [[/Archive 1]] * [[/Archive 2]]}}</pre> || {{Archive box| * [[/Archive 1]] * [[/Archive 2]]}} |- | <code><nowiki>{{Archive box| [[/Archiv 1]] · [[/Archiv 2]]}}</nowiki></code> || {{Archive box| [[/Archiv 1]] · [[/Archiv 2]]}} |} <includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox|| <!-- Categories go here and interwikis go in Wikidata. --> }}</includeonly> 6dfb1iglx7mi7q7fol8at1v7qtan143 Manual:Installing third-party tools/fr 100 673835 5387822 5377083 2022-07-29T09:29:07Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/fr]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/fr]] ezkxxg8g5rvukcyd6rc5fyrnipfeb8r Manual:Combating spam/en 100 688356 5387476 5200688 2022-07-28T22:40:17Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Like all current dynamic web sites, wikis are a common target for spammers wishing to promote products or websites. MediaWiki offers a number of features designed to [[Special:MyLanguage/Manual:Combating vandalism|combat vandalism in general]]. On this page we deal specifically with [[m:Wiki spam|wiki spam]], which is often automated. == Overview == Common tools used to combat wiki spam typically fall into these categories: * Requiring log in and/or a CAPTCHA on certain operations, such as edits, adding external links, or new user creation * Blocking edits from known blacklisted IP addresses or IPs running open proxies * Blocking edits which add specific unwanted keywords or external links * Blocking specific username and page title patterns commonly used by spambots * Blocking edits by new or anonymous users to specific often-targeted pages * Whitelisting known-good editors (such as admins, regular contributors) while placing restrictions on new or anonymous users * Cleanup scripts or bulk deletion ({{ll|Extension:Nuke}}) of existing posts from recently-banned spambots Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. Note that many of these features are not activated by default. If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes! By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities. It helps to raise the bar a little. You should also note however, that none of these solutions can be considered completely spam-proof. Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice. ==Quickest solutions to try first== Fighting spam should not be too hard. If you want to quickly and drastically reduce spam, try these few steps first. * Install the [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] extension to block known spammer IPs. * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. ==Antispam setup basics== {{anchor|CAPTCHA}} ===CAPTCHA=== One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines. The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including * all edits * edits adding new, unrecognized external links * user registration The extension ships with a default test, but this is a reference implementation, and is not intended for production use. Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total). The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently. ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective. It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired. One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution. You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.<ref> For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology] </ref> Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations." For this reason it should be combined with other mechanisms. ===rel="nofollow"=== Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. ==Antispam routine: tailored measures== Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. {{anchor|Individual page protection}} ===Individual page protection=== Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages. Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === Abuse filter === {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on. It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam. The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks. Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. ===SpamBlacklist=== The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. === Open proxies === Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public. Most such blocks are performed manually, when noticing the abuse. It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension. Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. ==Hardcore measures== The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. === $wgSpamRegex === MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable. You can use this to block additional snippets of text or markup associated with common spam attacks. Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to. Users are presented with an explanatory message, indicating which part of their edit text is not allowed. {{ll|Extension:SpamRegex}} allows editing of this variable on-wiki. <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'. The '/i' at the end makes the search case insensitive. It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers. === Apache configuration changes === In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam. These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file). ==== Filtering by user agent ==== When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> ==== Preventing blocked spammers from consuming resources ==== A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead: <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> ===IP address blacklists=== Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]]. These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors. It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. ==== CPU usage and overload ==== Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. ==== DNSBL ==== You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency. For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers: <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. ==== Bad Behavior and Project HoneyPot ==== Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans.[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. ==== $wgProxyList ==== {{Warning|1=This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.}} You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> You then set in your LocalSettings.php: <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… ==== Honeypots, DNS BLs and HTTP BLs ==== 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist. Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked: <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> The DNS blacklist operates as follows: * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit. Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits. This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected. While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package. The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options. Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array. Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress). As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries. Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known. A relatively small number of spambots appear to be behind a large percentage of the overall problem. Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted. One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites. This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. ==== But what's this about honeypots? ==== Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots. Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites. The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service. Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms. See [[w:Honeypot_(computing)|Honeypot (computing)]]. Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. ==== More lists of proxy and spambot IPs ==== Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse. It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use. See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists. Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms. Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable. To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot): # Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set: <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # Add the following text in [[MediaWiki:Blockiptext]] to display: "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary. Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors. == If spam has won the battle == You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again. See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]]. See ''External links'' for other tools without MediaWiki support. == Other ideas == This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. ==See also== *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === Extensions === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} ==== Bundled in the installer ==== The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === Settings === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} === External links === * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] 9khhoedd771bfuar62v7itki63rgngk Manual:Combating spam/ko 100 689632 5387477 5295593 2022-07-28T22:40:19Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} <span lang="en" dir="ltr" class="mw-content-ltr">Like all current dynamic web sites, wikis are a common target for spammers wishing to promote products or websites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki offers a number of features designed to [[Special:MyLanguage/Manual:Combating vandalism|combat vandalism in general]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">On this page we deal specifically with [[m:Wiki spam|wiki spam]], which is often automated.</span> == 개요 == <div lang="en" dir="ltr" class="mw-content-ltr"> Common tools used to combat wiki spam typically fall into these categories: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Requiring log in and/or a CAPTCHA on certain operations, such as edits, adding external links, or new user creation </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits from known blacklisted IP addresses or IPs running open proxies </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits which add specific unwanted keywords or external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking specific username and page title patterns commonly used by spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits by new or anonymous users to specific often-targeted pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Whitelisting known-good editors (such as admins, regular contributors) while placing restrictions on new or anonymous users </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Cleanup scripts or bulk deletion ({{ll|Extension:Nuke}}) of existing posts from recently-banned spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Note that many of these features are not activated by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</span> <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It helps to raise the bar a little.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Quickest solutions to try first== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Fighting spam should not be too hard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to quickly and drastically reduce spam, try these few steps first.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install the [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] extension to block known spammer IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam setup basics== </div> {{anchor|CAPTCHA}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===CAPTCHA=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> * 모든 편집 <div lang="en" dir="ltr" class="mw-content-ltr"> * edits adding new, unrecognized external links </div> * 사용자 계정 <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Individual page protection=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === 편집 필터 === <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Open proxies === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Apache configuration changes === </div> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Other ideas == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> ==같이 보기== *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === 확장 기능 === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === 설정 === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External links === </div> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] mzx8e93vq0g9z3ei1spo38meje59q4w Wikimedia Product/en 0 696121 5387572 5358190 2022-07-29T03:25:40Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1='''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Contributors</span>]] * [[Readers|<span style="color:#2aa198">Readers</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Across Product == * [[Special:MyLanguage/Product Principles|Product Principles]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (formerly: [[Special:MyLanguage/Technical Collaboration Guidance|Technical Collaboration Guidance]]) * [[Special:MyLanguage/Design/Statement of purpose|Design Statement of Purpose]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|Data and research information for products]] * [[Special:MyLanguage/Wikimedia Research/Showcase|Monthly Research Showcases]] === Programs === * [[m:Special:MyLanguage/Communications/Audience research|Audience Research]] * [[m:Special:MyLanguage/Community health initiative|Community Health Initiative]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|New Editor Experiences]] (2017–2018) * [[m:Special:MyLanguage/New Readers|New Readers]] — on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing. (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|Structured Data on Commons]] === Project Pages === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|Annual Plan goal: New Content]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|Advanced Mobile Contributions]] * [[Special:MyLanguage/Android editing features|Android Editing Features]] * [[Special:MyLanguage/Content translation/V2|Content Translation, V2]] * [[Special:MyLanguage/Growth/Growth team updates|Growth]] * [[Special:MyLanguage/Language tools|Improve Translate Extension and Translate Wiki process]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|iOS Editing]] * [[Special:MyLanguage/VisualEditor on mobile|Visual based mobile editing]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''Annual Plan goal: Better Use of Data''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|Better use of Data]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|Data collection: Instrumentation]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|Report stewardship]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''Annual Plan goal: Community Wishlist''']] * [[m:Special:MyLanguage/Community Tech#Projects|Wishlist]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|Support for smaller user groups]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|Tech tools for program and event organizers]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''Annual Plan goal: Anti-Harassment Tools''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|Reporting system]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''Annual Plan goal: Wikidata''']] '''Other:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 Annual Pan goal: Platform Evolution CDP] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|Invest in the MobileFrontend & MinervaNeue frontend architecture]] ** [[Special:MyLanguage/Parsing/Parser Unification|Parser unification]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|TemplateStyles]] * [[m:Special:MyLanguage/Movement Organizers|Movement Organizers Study]] (2019) == Metrics == The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health. [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|The monthly report on key metrics tracking the overall health of the Wikimedia movement.]] == Product teams == A Product team covers a set of features developed according to specific user flows and needs. === Contributors === We build collaborative, inclusive tools for creating and editing free knowledge. * Phabricator task boards: [[phab:tag/contributors-team/|#Contributors-Team]] (rarely used) * Page: [[Special:MyLanguage/Contributors|Contributors]] * Teams: ====== Anti-Harassment Tools ====== * Phabricator task board: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Page: [[Special:MyLanguage/Anti-Harassment Tools|Anti-Harassment Tools]] ====== Community Tech ====== * [[phab:project/board/1274/|Phabricator board]] * Page: [[m:Special:MyLanguage/Community Tech|Community Tech]] ====== Editing ====== * Phabricator task boards: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Page: [[Special:MyLanguage/Editing team|Editing team]] ====== Growth ====== * Phabricator task board: [[phab:project/board/1114/|#Growth-Team]] * Page: [[Special:MyLanguage/Growth|Growth]] ====== Language ====== * Phabricator task board: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Page: [[Special:MyLanguage/Wikimedia Language engineering|Wikimedia Language engineering]] === Readers === We build exceptional learning and reading experiences for the sum of all knowledge. * Page: [[Special:MyLanguage/Readers|Readers]] * Phabricator task board: [https://phabricator.wikimedia.org/tag/reading/ #reading] * Teams: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|Parsing]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|Product Infrastructure]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|Web]] ====== * [[Reading/Component responsibility|Reading code responsibility]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|Monthly page views, May 2013–January 2019. File:Wikimedia pageviews year-over-year comparison (since May 2013).png|Total page views in year-over-year comparison, May 2013–February 2019. File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|Desktop page views in year-over-year comparison, May 2013–February 2019. File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|Mobile page views in year-over-year comparison, May 2013–February 2019. </gallery> === Technical Program Management === We are dedicated to guiding delivery processes and facilitating team health through good practices. Page: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|Technical Program Management]] Lead: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === Product Design === We make sharing of all human knowledge easy and joyful. For everyone. Page: [[Special:MyLanguage/Design#Product Design|Product Design]] Director: [[User:MNovotny_(WMF)|Margeigh Novotny]] === Product Analytics === We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics. Page: [[Special:MyLanguage/Product Analytics|Product Analytics]] Lead: Kate Zimmerman === Product Design Strategy === <!--''[intro text here]''--> Page: [[Special:MyLanguage/Design#Design Strategy|Product Design Strategy]] Lead: Margeigh Novotny === Wikidata === Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]]. * Page: [[d:Wikidata:Main Page|Wikidata]] * Lead: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Phabricator bugs & tasks board: [[phab:project/profile/71/|#wikidata]] * Discussion List: wikidata@lists.wikimedia.org {|class="wikitable" |+ Wikidata Team Goals |- !scope="row"| WMDE Fiscal Year 2017 | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q1: January–March 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q2: April–June] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q3: July–September] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q4: October–December] |- !scope="row"| WMDE Fiscal Year 2016 | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q1: January–March 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q2: April–June] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q3: July–September] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q4: October–December] |} == Goals == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: July–September 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: October–December 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: January–March 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: April–June 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: July–September 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: October–December 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: January–March 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: April–June 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: July–September 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: October–December 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: January–March 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: April–June 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: July–September 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: October–December 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: January–March 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: April–June 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: July–September 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: October–December 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: January–March 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: April–June 2016]] |} == Annual Roadmap == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|Annual Plan for Product 2018–2019]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|Annual Plan for Product 2017–2018]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|Annual Plan for Product 2016–2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|2016 Product Summary]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|2015 Product & Technology Review]] [[Category:WMF Projects{{#translation:}}]] n3m6z32y7qjuw7nw6b7kgigqwvz2jew Wikimedia Product/ru 0 696123 5387592 5358208 2022-07-29T03:26:00Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1='''Группа развития сайтов Викимедиа''' (''Wikimedia Audiences'') — [[foundationsite:role/staff-contractors/|штатные сотрудники Фонда Викимедиа]], создающие, улучшающие и поддерживающие функционал [[m:Special:MyLanguage/Wikimedia projects|сайтов Викимедиа]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Участники</span>]] * [[Readers|<span style="color:#2aa198">Читатели</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Across Product == * [[Special:MyLanguage/Product Principles|Принципы продукта]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|Руководство по техническому сотрудничеству]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — продолжающееся исследование, которое фокусируется на понимании потенциальных читателей Викимедиа в странах, где доступ к Интернету быстро растет. (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * Страница: [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * Команда: ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Страница: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * Страница: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Страница: [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * Страница: [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Страница: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * Страница: [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * Команда: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === Wikidata === Wikidata - бесплатная и открытая база знаний, которую могут читать и редактировать как люди, так и машины. Этот проект поддерживается отделом разработки программного обеспечения и разработки [[WMDE Engineering|Wikimedia в Германии]]. * Страница: [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 1 квартал: январь-март 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 2 квартал: апрель-июнь] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf 3 квартал: июль-сентябрь] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf 4 квартал: октябрь-декабрь] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p 1 квартал: январь-март 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p 2 квартал: апрель-июнь] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p 3 квартал: июль-сентябрь] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p 4 квартал: октябрь-декабрь] |} == Цели == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|1 квартал: июль-сентябрь 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|2 квартал: октябрь-декабрь 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|3 квартал: январь-март 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|4 квартал: апрель-июнь 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|1 квартал: июль-сентябрь 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|2 квартал: октябрь-декабрь 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|3 квартал: январь-март 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|4 квартал: апрель-июнь 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|1 квартал: июль-сентябрь 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|2 квартал: октябрь-декабрь 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|3 квартал: январь-март 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|4 квартал: апрель-июнь 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|1 квартал: июль-сентябрь 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|2 квартал: октябрь-декабрь 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|3 квартал: январь-март 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|4 квартал: апрель-июнь 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|1 квартал: июль-сентябрь 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|2 квартал: октябрь-декабрь 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|3 квартал: январь-март 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|4 квартал: апрель-июнь 2016]] |} == Ежегодная дорожная карта == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|Годовой план на продукт 2018-2019 гг.]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|Годовой план на продукт 2017-2018 гг.]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|Годовой план на продукт 2016-2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|Сводка продуктов 2016 года]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|Обзор продуктов и технологий за 2015 год]] [[Category:WMF Projects{{#translation:}}]] 4izm7nrnvf99isegdai8sriqk8mxtg6 Template:InstallationNav/tr 10 697545 5387211 5384798 2022-07-28T21:17:35Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Wikimedia Product/fr 0 708519 5387577 5358196 2022-07-29T03:25:47Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=Le personnel du '''Produit Wikimédia''' [[foundationsite:role/staff-contractors/|employé par la Fondation Wikimédia]] construit, améliore et gère les fonctionnalités des [[m:Special:MyLanguage/Wikimedia projects|sites Wikimédia]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Contributeurs</span>]] * [[Readers|<span style="color:#2aa198">Lecteurs</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Au sujet du produit == * [[Special:MyLanguage/Product Principles|Principes du produit]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (initialement : [[Special:MyLanguage/Technical Collaboration Guidance|Guide de collaboration technique]]) * [[Special:MyLanguage/Design/Statement of purpose|Déclaration de conception]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|Données et informations de recherche des produits]] * [[Special:MyLanguage/Wikimedia Research/Showcase|Vitrines des recherches mensuelles]] === Programmes === * [[m:Special:MyLanguage/Communications/Audience research|Recherche sur l’audience]] * [[m:Special:MyLanguage/Community health initiative|Initiative de santé communautaire]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|Expériences des nouveaux contributeurs]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Nouveaux lecteurs]] — recherche en cours, qui vise à comprendre les lecteurs potentiels de Wikimédia dans les pays où l’accès à Internet est en forte croissance. (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|Données structurées sur Commons]] === Pages du projet === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|Objectif du plan annuel : nouveaux contenus]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|Contributions avancées pour les mobiles]] * [[Special:MyLanguage/Android editing features|Fonctionnalités de rédaction sur Android]] * [[Special:MyLanguage/Content translation/V2|Traduction de contenu, V2]] * [[Special:MyLanguage/Growth/Growth team updates|Croissance]] * [[Special:MyLanguage/Language tools|Amélioration de l’extension de traduction et du processus de traduction wiki]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|Rédaction sur iOS]] * [[Special:MyLanguage/VisualEditor on mobile|Rédaction visuelle sur mobile]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''Objectif du plan annuel : meilleure utilisation des données''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|Meilleure utilisation des données]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|Collecte des données : instrumentation]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|Intendance des rapports]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''Objectif du plan annuel : liste de souhaits de la Communauté''']] * [[m:Special:MyLanguage/Community Tech#Projects|Liste de souhaits]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|Soutien des groupes d’utilisateurs plus réduits]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|Outils techniques pour les organisateurs de programme ou d’événement]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''Objectif du plan annuel : outils anti-harcèlement''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|Système de signalement]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''Objectif du plan annuel : Wikidata''']] '''Autre :''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 Objectif du plan annuel : ''CDP'' d’évolution de la plateforme] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|Investir dans l’architecture des interfaces MobileFrontEnd et MinervaNeue]] ** [[Special:MyLanguage/Parsing/Parser Unification|Unification de l’analyseur syntaxique]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|Feuilles de styles des modèles ''(TemplateStyles)'']] * [[m:Special:MyLanguage/Movement Organizers|Étude des organisateurs du Mouvement]] (2019) == Mesures == L’outil de [[Special:MyLanguage/Product Analytics|Mesures analytiques du produit]] suit un ensemble de mesures clés conçues pour donner une image globale de la santé du mouvement. [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|Rapport sur les métriques clés, suivant la santé générale du mouvement Wikimédia.]] == Équipes du produit == Une équipe Produit couvre un ensemble de fonctions développées selon les flux et besoins spécifiques des utilisateurs. === Contributeurs === Nous construisons des outils collaboratifs et inclusifs pour créer et améliorer la connaissance libre. * Tableaux des tâches Phabricator : [[phab:tag/contributors-team/|#Contributors-Team]] (rarement utilisé) * Page : [[Special:MyLanguage/Contributors|Contributeurs]] * Équipes : ====== Outils anti-harcèlement ====== * Tableau des tâches sur Phabricator : [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Page : [[Special:MyLanguage/Anti-Harassment Tools|Outils anti-harcèlement]] ====== Technologies communautaires ====== * [[phab:project/board/1274/|Tableau de bord phabricator]] * Page : [[m:Special:MyLanguage/Community Tech|Technologies communautaires]] ====== Rédaction des pages ====== * Tableaux des tâches sur Phabricator : [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Page : [[Special:MyLanguage/Editing team|Équipe d'édition]] ====== Croissance ====== * Tableau des tâches sur Phabricator : [[phab:project/board/1114/|#Growth-Team]] * Page : [[Special:MyLanguage/Growth|Croissance]] ====== Langue ====== * Tableau des tâches sur Phabricator : [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Page : [[Special:MyLanguage/Wikimedia Language engineering|Ingénierie des langues de Wikimédia]] === Lecteurs === Nous bâtissons des expériences exceptionnelles d’apprentissage et de lecture de tout le savoir. * Page : [[Special:MyLanguage/Readers|Lecteurs]] * Tableau des tâches sur Phabricator : [https://phabricator.wikimedia.org/tag/reading/ #reading] * Équipes : ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|Analyse syntaxique]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|Infrastructure de produit]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|Web]] ====== * [[Reading/Component responsibility|Responsabilité du code de lecture]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|Pages vues chaque mois, de mai 2013 à janvier 2019. File:Wikimedia pageviews year-over-year comparison (since May 2013).png|Comparaison d’une année à l’autre du nombre total de pages vues, de mai 2013 à février 2018. File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|Comparaison d’une année à l’autre des pages vues sur ordinateur de bureau, de mai 2013 à février 2019. File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|Comparaison d’une année à l’autre des pages vues sur mobile, de mai 2013 à février 2019. </gallery> === Gestion du programme technique === Nous nous consacrons à guider les processus de livraison et à faciliter le maintien en bonne santé de l’équipe par l'application de bonnes pratiques. Page : [[Special:MyLanguage/Wikimedia Product/Technical Program Management|Gestion du programme technique]] Direction : [[m:User:Ggellerman (WMF)|Grace Gellerman]] === Conception de produit === Nous rendons facile et agréable le partage de tout le savoir humain. Pour tout le monde. Page : [[Special:MyLanguage/Design#Product Design|Conception de produit]] Directeur: [[User:MNovotny_(WMF)|Margeigh Novotny]] === Mesures analytiques du produit === Nous faisons des recommandations basées sur les résultats des analyses, nous militons pour des pratiques éthiques concernant les données, et nous éduquons sur des sujets relatifs aux données et aux statistiques. Page : [[Special:MyLanguage/Product Analytics|Mesures analytiques du produit]] Direction : Kate Zimmerman === Stratégie de conception du produit === <!--''[texte d’intro ici]''--> Page : [[Special:MyLanguage/Design#Design Strategy|Stratégie de conception du produit]] Direction : Margeigh Novotny === Wikidata === Wikidata est une base de connaissance libre et ouverte qui peut être consultée et modifiée à la fois par des humains et par des programmes. Ce projet est maintenu par le département Développement logiciel et d’ingénierie de [[WMDE Engineering|Wikimédia Allemagne]]. * Page : [[d:Wikidata:Main Page|Wikidata]] * Direction : [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Tableau des tâches et des anomalies sur Phabricator : [[phab:project/profile/71/|#wikidata]] * Liste de discussion : wikidata@lists.wikimedia.org {|class="wikitable" |+ Objectifs de l’équipe Wikidata |- !scope="row"| Année fiscale WMDE 2017 | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q1 : janvier–mars 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q2 : avril–juin] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q3 : juillet–septembre] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q4 : octobre–décembre] |- !scope="row"| Année fiscale WMDE 2016 | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q1 : janvier–mars 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q2 : avril–juin] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q3 : juillet–septembre] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q4 : octobre–décembre] |} == Objectifs == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1 : juillet–septembre 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2 : octobre–décembre 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3 : janvier–mars 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4 : avril–juin 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1 : juillet–septembre 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2 : octobre–décembre 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3 : janvier–mars 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4 : avril–juin 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1 : juillet–septembre 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2 : octobre–décembre 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3 : janvier–mars 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4 : avril–juin 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1 : juillet–septembre 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2 : octobre–décembre 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3 : janvier–mars 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4 : avril–juin 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1 : juillet–septembre 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2 : octobre–décembre 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3 : janvier–mars 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4 : avril–juin 2016]] |} == Plan de route annuel == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|Plan annuel du produit pour 2018–2019]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|Plan annuel du produit pour 2017–2018]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|Plan annuel du produit pour 2016–2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|Résumé du produit en 2016]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|Revue des produits et technologies en 2015]] [[Category:WMF Projects{{#translation:}}]] 1i9i9fvrnpup2urybtmmfjulcb706iy Translations:Manual:Installing MediaWiki/Page display title/tr 1198 710624 5387339 5361315 2022-07-28T22:04:51Z Baris6161TURK 17188421 wikitext text/x-wiki Manual:MediaWiki kurma 1153ci9a5jwl3gigssa84qohfc5ltbr Manual:Installing MediaWiki/tr 100 710625 5387302 5384980 2022-07-28T22:02:04Z Baris6161TURK 17188421 Created page with "Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. <span class="mw-translate-fuzzy">Apache, PHP ve MySQL/MariaDB kullanma tecrübesi olmayan sıradan bir bilgisayar kullancısına MediaWiki kurulumu zor gelebilir.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 19duowsz587f67v5434gqw3pmrm1uoo 5387304 5387302 2022-07-28T22:02:15Z Baris6161TURK 17188421 wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 41rx77kn78b26xjl0nimcyi47pcdm2c 5387308 5387304 2022-07-28T22:02:29Z Baris6161TURK 17188421 Created page with "Aşağıdaki [[$1|Ekler]] bölümü [[$2|el kuruluma daha kolay alternatifler]] sunar." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations.</span> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] s4zik7evtc40mwrocvv9n1b94jul23m 5387311 5387308 2022-07-28T22:02:36Z Baris6161TURK 17188421 Created page with "Aşağıdaki [[$1|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 7t44dljetoixs3bq6w1673p5p6jfsif 5387314 5387311 2022-07-28T22:02:47Z Baris6161TURK 17188421 Created page with "MediaWiki'yi zaten çalıştırıyorsanız, [[$1|Yükseltme kılavuzuna]] bakın." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] qmpcmwzoegiqsyvur38lkvhayp84fdw 5387317 5387314 2022-07-28T22:02:52Z Baris6161TURK 17188421 Created page with "== Kurulum gereksinimlerini kontrol edin ==" wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] tg9x6bqhtbgk72k43kwy9ox6cijx3ay 5387320 5387317 2022-07-28T22:02:59Z Baris6161TURK 17188421 Created page with "Sisteminizin [[$1|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 30yuzazcbw65ezztl0ih8904mjg50bf 5387322 5387320 2022-07-28T22:03:22Z Baris6161TURK 17188421 Created page with "Yüklemeyi planladığınız MediaWiki sürümünün $1 sayfasını da kontrol ettiğinizden emin olun." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] doxb4dzh2014rcvri5zabphxb78smgp 5387325 5387322 2022-07-28T22:03:30Z Baris6161TURK 17188421 Created page with "== MediaWiki yazılımını indirin ==" wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. == MediaWiki yazılımını indirin == <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] pevkyw8lwpqwjlhxo0a8k8mukk8f5ao 5387328 5387325 2022-07-28T22:03:38Z Baris6161TURK 17188421 Created page with "MediaWiki tar dosyasını [[$1|resmi indirme sayfasından]] indirin." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. == MediaWiki yazılımını indirin == MediaWiki tar dosyasını [[Special:MyLanguage/Download|resmi indirme sayfasından]] indirin. <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] oa8vcuaza8mg48cn2guiwjw641r7bvl 5387330 5387328 2022-07-28T22:03:49Z Baris6161TURK 17188421 Created page with "Genel olarak, bir üretim ortamı kullanıyorsanız, $1 olan en son kararlı sürümü çalıştırmak istersiniz." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. == MediaWiki yazılımını indirin == MediaWiki tar dosyasını [[Special:MyLanguage/Download|resmi indirme sayfasından]] indirin. Genel olarak, bir üretim ortamı kullanıyorsanız, MediaWiki {{MW stable release number}} olan en son kararlı sürümü çalıştırmak istersiniz. <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] ol7aqf6sov1fohnyv37vtvutobit5rc 5387332 5387330 2022-07-28T22:03:55Z Baris6161TURK 17188421 Created page with "== MediaWiki yazılımını çıkarın ==" wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. == MediaWiki yazılımını indirin == MediaWiki tar dosyasını [[Special:MyLanguage/Download|resmi indirme sayfasından]] indirin. Genel olarak, bir üretim ortamı kullanıyorsanız, MediaWiki {{MW stable release number}} olan en son kararlı sürümü çalıştırmak istersiniz. == MediaWiki yazılımını çıkarın == <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] rt18aedwxoxz989wtole1hm1dn6w1ta 5387334 5387332 2022-07-28T22:04:02Z Baris6161TURK 17188421 Created page with "İndirilen dosya $2 veya $1 dosya biçimindedir." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. == MediaWiki yazılımını indirin == MediaWiki tar dosyasını [[Special:MyLanguage/Download|resmi indirme sayfasından]] indirin. Genel olarak, bir üretim ortamı kullanıyorsanız, MediaWiki {{MW stable release number}} olan en son kararlı sürümü çalıştırmak istersiniz. == MediaWiki yazılımını çıkarın == İndirilen dosya <code>.zip</code> veya <code>.tar.gz</code> dosya biçimindedir. <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] prmkktrwh5n6yf3i2k8v5jj3c878p5x 5387336 5387334 2022-07-28T22:04:09Z Baris6161TURK 17188421 Created page with "Kullanmadan önce bu arşiv dosyasını açmanız gerekir." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. == MediaWiki yazılımını indirin == MediaWiki tar dosyasını [[Special:MyLanguage/Download|resmi indirme sayfasından]] indirin. Genel olarak, bir üretim ortamı kullanıyorsanız, MediaWiki {{MW stable release number}} olan en son kararlı sürümü çalıştırmak istersiniz. == MediaWiki yazılımını çıkarın == İndirilen dosya <code>.zip</code> veya <code>.tar.gz</code> dosya biçimindedir. Kullanmadan önce bu arşiv dosyasını açmanız gerekir. <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] bm5sfk6suqspa16gdetoy3tfadvso5p 5387338 5387336 2022-07-28T22:04:17Z Baris6161TURK 17188421 Created page with "Dosyayı yerel olarak açabilir (ve ardından FTP yoluyla sunucuya yükleyebilirsiniz) veya doğrudan sunucunuzdan açabilirsiniz." wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. == MediaWiki yazılımını indirin == MediaWiki tar dosyasını [[Special:MyLanguage/Download|resmi indirme sayfasından]] indirin. Genel olarak, bir üretim ortamı kullanıyorsanız, MediaWiki {{MW stable release number}} olan en son kararlı sürümü çalıştırmak istersiniz. == MediaWiki yazılımını çıkarın == İndirilen dosya <code>.zip</code> veya <code>.tar.gz</code> dosya biçimindedir. Kullanmadan önce bu arşiv dosyasını açmanız gerekir. Dosyayı yerel olarak açabilir (ve ardından FTP yoluyla sunucuya yükleyebilirsiniz) veya doğrudan sunucunuzdan açabilirsiniz. <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Wiki families (multiple wikis)}} {{anchor|Installing an existing wiki}} {{anchor|Appendices}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">See also the {{ll|comparison of distribution options}}.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] swnspsf9w4oljxkebz65ffsq6sqd02o 5387507 5387338 2022-07-28T22:45:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. Aşağıdaki [[#Appendices|Ekler]] bölümü [[#Alternatives to manual installation|el kuruluma daha kolay alternatifler]] sunar. Aşağıdaki [[#Appendices|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. {{Note|MediaWiki'yi zaten çalıştırıyorsanız, [[Special:MyLanguage/Manual:Upgrading|Yükseltme kılavuzuna]] bakın.}} == Kurulum gereksinimlerini kontrol edin == Sisteminizin [[Special:MyLanguage/Manual:Installation requirements|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. Yüklemeyi planladığınız MediaWiki sürümünün {{ll|Release notes}} sayfasını da kontrol ettiğinizden emin olun. == MediaWiki yazılımını indirin == MediaWiki tar dosyasını [[Special:MyLanguage/Download|resmi indirme sayfasından]] indirin. Genel olarak, bir üretim ortamı kullanıyorsanız, MediaWiki {{MW stable release number}} olan en son kararlı sürümü çalıştırmak istersiniz. == MediaWiki yazılımını çıkarın == İndirilen dosya <code>.zip</code> veya <code>.tar.gz</code> dosya biçimindedir. Kullanmadan önce bu arşiv dosyasını açmanız gerekir. Dosyayı yerel olarak açabilir (ve ardından FTP yoluyla sunucuya yükleyebilirsiniz) veya doğrudan sunucunuzdan açabilirsiniz. <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] ibdibemqs7k7gc0nbzsc8haxj81zjdi Translations:Manual:Installing MediaWiki/3/tr 1198 710628 5387303 2545792 2022-07-28T22:02:14Z Baris6161TURK 17188421 wikitext text/x-wiki Apache (web sunucusu yazılımı), PHP ve MySQL/MariaDB (veritabanı) ile herhangi bir deneyiminiz yoksa MediaWiki'yi kurmak zor olabilir. p8ek814m3h35t8fzi8xfq6ug3t2c02a Translations:Manual:Installation guide/11/tr 1198 710636 5387288 5361309 2022-07-28T21:56:41Z Baris6161TURK 17188421 wikitext text/x-wiki Küçük resmi ek programlar gerektirir. $1 (Görsel Düzenleyici için gerekli) ve diğer hizmetlerin kendi gereksinimleri vardır. 5apu5mdov199h2l6ezwm0lh4gdwt58m Extension:Highlight Links in Category/en 102 716042 5387150 5345725 2022-07-28T21:07:57Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} '''Highlight Links in Category''' is an extension that adds a CSS class to links pointing to members of a category. For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator]. ==Installation== {{ExtensionInstall|HighlightLinksInCategory|registration=required}} ==Configuration parameters== ; $wgHighlightLinksInCategory : This global is an array that configures which categories get an added CSS class. The keys are the Category names, which must include underscores instead of spaces. Do not include the Category: namespace. The value for each key is the CSS class you would like to add to that category. For example: {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} If you want add more than one class, separate the class names with spaces, like {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} You can add as many of these as you want, but from a UX perspective it's probably not awesome to add 500 different style links. If $wgHighlightLinksInCategory is not set or empty, this extension will do nothing. If you're running a wiki farm and need to turn it off on some wikis, set <syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight>; using {{phpi|false}} could lead to incorrect behavior. ==Styling== Simply add the styles you need for these links to MediaWiki:Common.css on your wiki. For example: {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} If you want one category to override another, you'll have to specify it with CSS. {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} Or alternatively, you could have defined the original <code>a.templates</code> rule as <code>a.templates:not(.disambig)</code> instead. There's also the link icon approach: {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} ==User Toggles== An easy way to set up toggling this highlighting on or off is to make a [[Extension:Gadgets|Gadget]] with CSS in it. Yes, this is a personalization extension that outsources the personalization part to other extensions; I can still sleep at night. ==How this works== Right after MediaWiki determines which linked pages exist (to make redlinks), it runs the <code>GetLinkColours</code> hook (see LinkHolderArray.php). As we have a list of all of the page ids which are linked on that page, we can run one database query to see which of these links are in the set of categories we want to highlight. Because the query only happens on an index of the <code>categorylinks</code> table, it's reasonably fast. Then CSS classes are assigned based on the result, using the configuration values the user sets in <code>$wgHighlightLinksInCategory</code>. Explaining how CSS works is outside the scope of this document. ==Known issues== * CSS styles are not added in Flow, because it doesn't appear to call the GetLinkColors hook there. ==See also== * [[:Category:LinkEnd extensions]] - which customize links in other ways {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] n7n3kzehfe1kwh18a8dxfbrv4qsrbpo Manual:Combating spam/zh 100 726643 5387482 5255688 2022-07-28T22:40:21Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} 和现代所有动态网站一样,wiki类网站也是被垃圾内容骚扰的目标之一。 MediaWiki提供了很多功能来防止[[Special:MyLanguage/Manual:Combating vandalism|垃圾信息]]。 本页面用于提供防止您的网站受到[[m:Wiki spam|垃圾信息]]骚扰的方式 == 概述 == 用于打击垃圾信息的常用工具通常分为以下几类: * 在某些操作上需要登录和/或验证码,例如编辑、添加外部链接或创建新用户 * 阻止来自已知黑名单IP地址或运行开放代理的IP的编辑 * 阻止添加特定不需要的关键字或外部链接的编辑 * 阻止垃圾邮件通常使用的特定用户名和页面标题模式 * 阻止新用户或匿名用户对特定的经常定位的页面进行编辑 * 将已知良好的编辑者(例如管理员,常规贡献者)列入白名单,同时对新用户或匿名用户施加限制 <div lang="en" dir="ltr" class="mw-content-ltr"> * Cleanup scripts or bulk deletion ({{ll|Extension:Nuke}}) of existing posts from recently-banned spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> 请注意,默认情况下不会激活其中许多功能。 如果您在服务器/主机上运行MediaWiki安装,那么您是唯一可以进行必要配置更改的人员! <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> 它有助于提高标准一点点。 但是,您还应注意,这些解决方案都不能被视为完全防垃圾邮件。 <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> ==首先尝试最快速的解决方案== 打击垃圾并不是非常困难。 如果要快速,大幅度地减少垃圾,请先尝试这几个步骤。 * 安装[[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]]扩展以阻止已知的垃圾邮件制造者IP。 * 安装和设置基本的反垃圾扩展(已经附带于[[Special:MyLanguage/Download|最新版本]]),于特定的{{ll|Extension:ConfirmEdit}}。 * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|配置 QuestyCaptcha]] 和[[Special:MyLanguage/Extension:ConfirmEdit#Configuration|默认设置]]。 <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> 如果您仍然遇到问题,请阅读本页的其余部分以获取更多解决方案,并在[[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] 上发布以获取帮助。 ==反垃圾基础设置== {{anchor|CAPTCHA}} ===验证码=== 反自动提交的一种较为常见的方法是使用[[w:zh:验证码|验证码]],这个系统试图通过要求用户解决简单问题来区分人与自动提交系统。 <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> * 所有编辑 编辑添加新的,无法识别的外部链接 * 用户注册 <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. ==反垃圾案例:定制规则== <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} ===个别页眉的保护=== <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === 滥用过滤器 === <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> === 开放代理 === <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> 从1.22版开始,{{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}}可用于使封禁更加有效。 <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> === Apache配置更改 === <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> ===IP地址黑名单=== <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> ==== DNSBL ==== <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> == 其他主意 == <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> ==参见== *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === 扩展 === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === 设置 === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} === 外部链接 === * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] adm89agtnbp8z9psxez46ce0ctbwjpg Extension:Highlight Links in Category/tr 102 727683 5387157 5345732 2022-07-28T21:08:01Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} '''Highlight Links in Category''', bir kategorinin üyelerine işaret eden bağlantılara CSS sınıfı ekleyen bir uzantıdır. Bir sorunu veya hatayı bildirmek için lütfen [https://phabricator.miraheze.org Miraheze Phabricator] kullanın. == Kurulum == {{ExtensionInstall|HighlightLinksInCategory|registration=required}} == Yapılandırma parametreleri == ; $wgHighlightLinksInCategory : Bu küresel hangi kategorilerin ek bir CSS sınıfı alacağını yapılandıran bir dizidir. Anahtarlar, boşluk yerine alt çizgi içermesi gereken Kategori adlarıdır. Kategori: ad alanını dahil etmeyin. Her anahtarın değeri, o kategoriye eklemek istediğiniz CSS sınıfıdır. Örneğin: {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} Birden fazla sınıf eklemek istiyorsanız, sınıf adlarını boşluklarla ayırın, şunun gibi {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} Bunlardan istediğiniz kadar ekleyebilirsiniz, ancak kullanıcı deneyimi açısından 500 farklı stil bağlantısı eklemek muhtemelen harika değildir. $wgHighlightLinksInCategory ayarlanmamış veya boş ise, bu uzantı hiçbir şey yapmaz. <span lang="en" dir="ltr" class="mw-content-ltr">If you're running a wiki farm and need to turn it off on some wikis, set <syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight>; using {{phpi|false}} could lead to incorrect behavior.</span> == Stil == MediaWiki:Common.css vikinizde bağlantılar için ihtiyacınız olan stilleri ekleyin. Örneğin: {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} Bir kategorinin diğerini geçersiz kılmasını istiyorsanız, bunu CSS ile belirtmeniz gerekir. {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} Veya alternatif olarak, orijinal <code>a.templates</code> kuralını bunun yerine <code>a.templates:not(.disambig)</code> olarak tanımlayabilirsiniz. Bağlantı simgesi yaklaşımı da var: {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} == Kullanıcı geçişleri == Bu vurgulamayı açıp kapatmanın kolay bir yolu, içinde CSS olan bir [[Extension:Gadgets|küçük araç]] oluşturmaktır. Evet, bu, kişiselleştirme bölümünü diğer uzantılara aktaran bir kişiselleştirme uzantısıdır; Hala geceleri uyuyabilirim. == Bu nasıl çalışır == MediaWiki hangi bağlantılı sayfaların var olduğunu belirledikten hemen sonra (kırmızı bağlantı yapmak için), <code>GetLinkColours</code> kancasını çalıştırır (LinkHolderArray.php bakın). O sayfada bağlantılı tüm sayfa kimliklerinin bir listesine sahip olduğumuz için, bu bağlantılardan hangilerinin vurgulamak istediğimiz kategoriler kümesinde olduğunu görmek için bir veritabanı sorgusu çalıştırabiliriz. Sorgu yalnızca <code>categorylinks</code> tablosunun bir dizininde gerçekleştiğinden, oldukça hızlıdır. Ardından, sonuca göre, kullanıcının <code>$wgHighlightLinksInCategory</code> içinde ayarladığı yapılandırma değerleri kullanılarak CSS sınıfları atanır. CSS'nin nasıl çalıştığını açıklamak bu belgenin kapsamı dışındadır. == Bilinen sorunlar == * CSS stilleri Flow'a eklenmez, çünkü orada GetLinkColors kancasını çağırmıyor gibi görünüyor. == Ayrıca bakınız == * [[:Category:LinkEnd extensions]] - bağlantıları başka şekillerde özelleştiren {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] sfwto8pjsq8lzi68ooiput5h1v7elgy User:Msnhinet8 2 729682 5387886 2887843 2022-07-29T10:37:50Z Ilovemydoodle2 17636692 Corrected typo on user page - if you prefer it the way it was before, please revert this edit and specify that you do not want your user page edited under any circumstances. Thank you. wikitext text/x-wiki *嗨! *I am from taiwan. q9q0leq4vqbnfnzw1j37s4ax0yqzc8z 5387893 5387886 2022-07-29T10:39:34Z Ilovemydoodle2 17636692 Undo revision 5387886 by [[Special:Contributions/Ilovemydoodle2|Ilovemydoodle2]] ([[User talk:Ilovemydoodle2|talk]]), oops, globally banned user wikitext text/x-wiki *嗨! *I from to taiwan. 4jme3sgmds64rgrynky5brmr4eaq136 Wikimedia Product/ja 0 729948 5387582 5358199 2022-07-29T03:25:52Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1='''ウィキメディアの製品''' (Wikimedia Product) の担当者は[[foundationsite:role/staff-contractors/|ウィキメディア財団に雇用されており]]、[[m:Special:MyLanguage/Wikimedia projects|ウィキメディアのサイト]]の機能の作成、改善と管理を受け持っています。{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">貢献者</span>]] * [[Readers|<span style="color:#2aa198">閲覧者</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == 全ての製品が対象 == * [[Special:MyLanguage/Product Principles|製品の原則]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (旧称: [[Special:MyLanguage/Technical Collaboration Guidance|技術協力の指針]]) * [[Special:MyLanguage/Design/Statement of purpose|デザイン 目的の声明]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|製品に関するデータと研究情報]] * [[Special:MyLanguage/Wikimedia Research/Showcase|今月の研究紹介]] === プログラム === * [[m:Special:MyLanguage/Communications/Audience research|観衆調査]] * [[m:Special:MyLanguage/Community health initiative|コミュニティ健全化の提案]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|編集初学者の経験]] (2017–2018) * [[m:Special:MyLanguage/New Readers|新しい読者]] — インターネット人口が急速に増えている国々でウィキメディアの読者となりうる層を対象に、現在進めている研究。 (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|コモンズの保存情報の構造化]] === プロジェクトのページ === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|年次目標:新規コンテンツ]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|モバイル版の高度な貢献]] * [[Special:MyLanguage/Android editing features|Android版編集機能]] * [[Special:MyLanguage/Content translation/V2|コンテンツ翻訳拡張機能/バージョン2]] * [[Special:MyLanguage/Growth/Growth team updates|Growth]] * [[Special:MyLanguage/Language tools|翻訳拡張機能とウィキの翻訳過程の改善]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|iOS版編集きのうAndroid版の項目名と統一]] * [[Special:MyLanguage/VisualEditor on mobile|ビジュアル主体のモバイル編集]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''年次目標:データ活用''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|データの効率的な適用]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|データ収集:仕組みづくり]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|スチュワードへのレポート]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''年次目標:コミュニティの要望''']] * [[m:Special:MyLanguage/Community Tech#Projects|コミュニティの要望]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|小規模利用者グループの支援]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|プログラムとイベント主催者向け技術ツール]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''年次目標:嫌がらせ対策ツール''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|通報システム]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''年次目標:Wikidata''']] '''その他:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 年次目標:プラットフォーム革新CDP] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|MobileFrontend & MinervaNeue フロントエンド構築に投資]] ** [[Special:MyLanguage/Parsing/Parser Unification|パーサーの統合]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|TemplateStyles]] * [[m:Special:MyLanguage/Movement Organizers|運動の主催者調査]] (2019) == 評価指標 == [[Special:MyLanguage/Product Analytics|製品評価]]は、鍵となる指標一式を追跡して運動の健全性を高度に分析する。 [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|鍵となる指標の月次レポートはウィキメディア運動全般の健全性を追跡。]] == 製品チーム == 製品チームは特定の利用者フローとニーズに対応する一連の機能を担当します。 === 貢献者 === フリーな知識を創り出し編集するため、協力し合えてわけへだてのないツールを開発中です。 * Phabricator タスクボード: [[phab:tag/contributors-team/|#Contributors-Team]] (ほとんど使わない) * ページ: [[Special:MyLanguage/Contributors|貢献者]] * チーム: ====== 嫌がらせ対策ツール ====== * Phabricator タスクボード: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * ページ: [[Special:MyLanguage/Anti-Harassment Tools|嫌がらせ対策ツール]] ====== コミュニティ技術 ====== * [[phab:project/board/1274/|Phabricator ボード]] * ページ: [[m:Special:MyLanguage/Community Tech|コミュニティーテック]] ====== 編集 ====== * Phabricator タスクボード: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * ページ: [[Special:MyLanguage/Editing team|編集チーム]] ====== 成長 ====== * Phabricator タスクボード: [[phab:project/board/1114/|#Growth-Team]] * ページ: [[Special:MyLanguage/Growth|Growth]] ====== 言語 ====== * Phabricator タスクボード: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * ページ: [[Special:MyLanguage/Wikimedia Language engineering|ウィキメディア言語技術]] === 閲覧者 === すべての知識の合計について、学習と閲覧のすばらしい経験を作ります。 * ページ: [[Special:MyLanguage/Readers|読者]] * Phabricator タスクボード:upd [https://phabricator.wikimedia.org/tag/reading/ #reading] * チーム: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|パーサ処理]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|製品インフラ]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|ウェブ]] ====== * [[Reading/Component responsibility|閲覧者のコード分担]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|2013年5月–2019年1月期の月間閲覧数。 File:Wikimedia pageviews year-over-year comparison (since May 2013).png|2013年5月-2019年2月期の累積閲覧数の比較 。<!-- ([https://commons.wikimedia.org/wiki/File:Wikimedia_desktop_pageviews_year-over-year_comparison_(since_May_2013).png#/media/File:Wikimedia_desktop_pageviews_year-over-year_comparison_(since_May_2013).png デスクトップ]と[https://commons.wikimedia.org/wiki/File:Wikimedia_mobile_pageviews_year-over-year_comparison_(since_May_2013).png#/media/File:Wikimedia_mobile_pageviews_year-over-year_comparison_(since_May_2013).png モバイル]でそれぞれ統計。) --> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|デスクトップ版の2013年5月-2019年2月期の累積閲覧数の比較。 File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|モバイル版の2013年5月-2019年2月期の累積閲覧数の比較。 </gallery> === 技術プログラム管理 === 最善手法に従い、配布プロセスを指導してチームの健全性促進に努力します。 ページ: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|技術プログラム管理]] リーダー: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === 製品設計 === 人類のあらゆる知識の共有を簡単に楽しく。すべての人のために。 ページ: [[Special:MyLanguage/Design#Product Design|製品設計]] 部長: [[User:MNovotny_(WMF)|Margeigh Novotny]] === 製品分析 === 分析結果に基づいた勧告をまとめ、倫理的なデータ実践を提唱して、またデータと統計をめぐる主題を教育します。 ページ: [[Special:MyLanguage/Product Analytics|製品分析]] リーダー: Kate Zimmerman === 製品設計の戦略 === <!--''[ここに案内文を記入]''--> ページ: [[Special:MyLanguage/Design#Design Strategy|製品設計の戦略]] リーダー: Margeigh Novotny === ウィキデータ === ウィキデータは無料で公開の知識ベースで人間とコンピュータのどちらも閲覧と編集ができます。このプロジェクトの推進役は[[WMDE Engineering|ウィキメディアのドイツ支部]] (WMDE) ソフトウェア開発部門と技術部門です。 * ページ: [[d:Wikidata:Main Page|Wikidata]] * リーダー: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Phabricator バグ、タスクボード: [[phab:project/profile/71/|#wikidata]] * 議論の一覧: wikidata@lists.wikimedia.org {|class="wikitable" |+ ウィキデータチームの達成目標 |- !scope="row"| WMドイツ支部2017予算年度 | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q3: 2017年1月-3月] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q4: 4月-6月] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q1: 7月–9月] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q2: 10月-12月] |- !scope="row"| WMドイツ支部2016予算年度 | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q3: 2016年1月-3月] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q4: 4月-6月] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q1: 7月–9月] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q2: 10月-12月] |} == 目標 == {|class="wikitable" |- !scope="row"| 2019年-2020年 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: 2019年7月-9月]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2 (第2四半期): 2019年10月-12月]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3 (第3四半期): 2020年1月-3月]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4 (第4四半期): 2020年4月-6月]]--> |- !scope="row"| 2018年–2019年 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: 2018年7月–9月]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: 2018年10月–12月]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: 2019年1月–3月]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: 2019年4月–6月]] |- !scope="row"| 2017年–2018年 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: 2017年7月–9月]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: 2017年10月–12月]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: 2018年1月–3月]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: 2018年4月–6月]] |- !scope="row"| 2016年–2017年 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: 2016年7月-9月]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: 2016年10月-12月]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: 2017年1月-3月]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: 2017年4月-6月]] |- !scope="row"| 2015年–2016年 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1 (第1四半期): 2015年7月-9月]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2 (第2四半期): 2015年10月-12月]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3 (第3四半期): 2016年1月-3月]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4 (第4四半期): 2016年4月-6月]] |} == 年間ロードマップ == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|製品の年次計画 2018-2019年]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|製品の年次計画 2017-2018年]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|製品の年次計画 2016-2017年]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|2016年 製品の概要]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|2015年製品&技術評価]] [[Category:WMF Projects{{#translation:}}]] tephqdoazpjayb5ati1xt4xjwflvqc6 Wikimedia Product/zh 0 734542 5387602 5358220 2022-07-29T03:26:10Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1='''维基媒体产品'''职员[[foundationsite:role/staff-contractors/|由维基媒体基金会雇佣]],构建、改进并维护[[m:Special:MyLanguage/Wikimedia projects|维基媒体网站]]的功能。{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">贡献者</span>]] * [[Readers|<span style="color:#2aa198">读者</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == 跨产品 == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|技术协调指导]]) * [[Special:MyLanguage/Design/Statement of purpose|设计的目的声明]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|用于产品的数据和研究信息]] * [[Special:MyLanguage/Wikimedia Research/Showcase|每月研究典範]] === 计划 === * [[m:Special:MyLanguage/Communications/Audience research|受眾研究]] * [[m:Special:MyLanguage/Community health initiative|社群健康倡议]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|新读者]] — 正在进行的研究,重点是了解在互联网访问迅速增长的国家中潜在的维基媒体读者。 (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|共享资源上的结构化数据]] === 项目页面 === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|iOS Editing]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == 产品团队 == <span class="mw-translate-fuzzy">受众团队涵盖根据特定用户流程和需求开发的一系列功能。</span> === 贡献者 === 我们构建了用于创建和编辑免费知识的协作、包容性工具。 * Phabricator任务面板: [[phab:tag/contributors-team/|#Contributors-Team]] (很少用) * 页面: [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * 团队: ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * Phabricator面板: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * 页面: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|Phabricator任务面板:]] * 页面: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== 编辑 ====== * Phabricator任务面板: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * 页面: [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * Phabricator任务面板: [[phab:project/board/1114/|#Growth-Team]] * 页面: [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== 语言 ====== * Phabricator任务面板: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * 页面: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === 读者 === 我们为所有知识的总和建立了卓越的学习和阅读体验。 * 页面: [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * Phabricator任务面板: [https://phabricator.wikimedia.org/tag/reading/ #reading] * 团队: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|安卓]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|苹果]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === 技术项目管理 === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> 页面: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|技术项目管理]] 主导: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === 工具定义 === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === 维基数据 === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * 页面: [[d:Wikidata:Main Page|Wikidata]] * 领导: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Phabricator臭蟲與任務板: [[phab:project/profile/71/|#wikidata]] * 讨论列表: wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == 目标 == {|class="wikitable" |- !scope="row"| 2019~2020年 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|第一季度:2019年7月~9月]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|第二季度:2019年10月~12月]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|第三季度:2020年1月~3月]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|第四季度:2020年4月~6月]]--> |- !scope="row"| 2018~2019年 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|第一季度:2018年7月~9月]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|第二季度:2018年10月~12月]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|第三季度:2019年1月~3月]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|第四季度:2019年4月~6月]] |- !scope="row"| 2017~2018年 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|第一季度:2017年7月~9月]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|第二季度:2017年10月~12月]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|第三季度:2018年1月~3月]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|第四季度:2018年4月~6月]] |- !scope="row"| 2016~2017年 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|第一季度:2016年7月~9月]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|第二季度:2016年10月~12月]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|第三季度:2017年1月~3月]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|第四季度:2017年4月~6月]] |- !scope="row"| 2015~2016年 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|第一季度:2015年7月~9月]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|第二季度:2015年10月~12月]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|第三季度:2016年1月~3月]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|第四季度:2016年4月~6月]] |} == 年度路线图 == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|年度产品计划2018~2019]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|年度产品计划2017~2018]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|年度产品计划2016~2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|2016年产品摘要]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|2015年产品与技术复核]] [[Category:WMF Projects{{#translation:}}]] qvij8d5r5wwf87qyfh0jw3ibsol2um9 Translations:Manual:Combating spam/110/en 1198 744781 5387468 2650101 2022-07-28T22:40:06Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki Several extensions, particularly the $1 extension, blocks a range of open proxies. jqblem17a1e2p8p5tqwrbvdk6qav5zh Wikimedia Product/ml 0 749253 5387584 5358203 2022-07-29T03:25:54Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">സംഭാവന ചെയ്യുന്നവർ</span>]] * [[Readers|<span style="color:#2aa198">വായനക്കാർ</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === പരിപാടികൾ === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|പുതിയ വായനക്കാർ]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === സംഭാവന ചെയ്യുന്നവർ === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == ലക്ഷ്യങ്ങൾ == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span class="mw-translate-fuzzy">Q1:ജൂലൈ - സെപ്റ്റംബർ 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span class="mw-translate-fuzzy">Q1:ജൂലൈ - സെപ്റ്റംബർ 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span class="mw-translate-fuzzy">Q1:ജൂലൈ - സെപ്റ്റംബർ 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] na095hecl83hvs1s040gigjum2dfvmb Wikimedia Product/sd 0 757198 5387591 5358212 2022-07-29T03:26:00Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">ڀاڱيدار</span>]] * [[Readers|<span style="color:#2aa198">پڙھندڙ</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === سٽاءُ === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|نوان پڙھندڙ]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === ڀاڱيدار === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == هدف == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2017–2018</span> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2016–2017</span> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] tj924yiy08yuj7fgrz2x8hplq92k57h Wikimedia Product/ar 0 757337 5387569 5358186 2022-07-29T03:25:37Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=ينهض موظفو '''تقنية ويكيميديا''' [[:foundation:Staff and contractors|الذين عينتهم مؤسسة ويكيميديا]] بأعمال تشييد البنية التحتية [[m:Special:MyLanguage/Wikimedia projects|لمشاريع ويكيميديا]] وتحسينها وصيانتها.{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">مساهمون</span>]] * [[Readers|<span style="color:#2aa198">القارى</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === البرامج === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|القراء الجدد]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === صفحات المشروع === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|النمو]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|التعديل من نظام IOS]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|اِستخدام أفضل للبيانات]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''أخرى:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === مساهمون === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * الصفحة: [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * الفرق: ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * الصفحة: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * الصفحة: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== التحرير ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * الصفحة: [[Special:MyLanguage/Editing team|فريق التحرير]] ====== النمو ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * الصفحة: [[Special:MyLanguage/Growth|النمو]] ====== اللغة ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * الصفحة: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === القارى === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * الصفحة: [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * الفرق: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|أندرويد]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|البنية التحتية للقراءة]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|القراءات الشهرية للصفحة ، ماي 2013 - جانفي 2019 File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> الصفحة: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === تصميم المنتج === نحن نعمل على نشر المعرفة الإنسانية لتكون سهلة و ممتعة بالنسبة للجميع الصفحة: [[Special:MyLanguage/Design#Product Design|تصميم المنتج]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> الصفحة: [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> الصفحة: [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === ويكي بيانات === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * الصفحة: [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 جانفي-مارس 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 أفريل-جوان] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf جويلية-سبتمبر] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf أكتوبر-ديسمبر] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p جانفي-مارس 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p أفريل-جوان] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p جويلية-سبتمبر] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p أكتوبر-ديسمبر] |} == الأهداف == {|class="wikitable" |- !scope="row"| 2020-2019 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|يوليو-سبتمبر 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|أكتوبر-ديسمبر 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|يناير-مارس 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|أبريل-يونيو 2020]]--> |- !scope="row"| 2019-2018 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|يوليو-سبتمبر 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|أكتوبر-ديسمبر 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|يناير-مارس 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|أبريل-يونيو 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|يوليو-سبتمبر 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|أكتوبر-ديسمبر 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|يناير-مارس 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|أبريل-يونيو 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|يوليو-سبتمبر 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|أكتوبر-ديسمبر 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|يناير-مارس 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|أبريل-يونيو 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|يوليو-سبتمبر 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|أكتوبر-ديسمبر 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|يناير-مارس 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|أبريل-يوليو 2016]] |} == خريطة الطريق السنوية == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|الخطة السنوية لمُنتجات عامي 2018-2019]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|الخطة السنوية لمُنتجات عامي 2017-2018]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|الخطة السنوية لمُنتجات عامي 2016-2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|مُلخص المُنتج 2016]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|مُراجعة المُنتج والتقنية]] [[Category:WMF Projects{{#translation:}}]] 7npxtmuurgixa4pmnbwm127yeb34z5w Wikimedia Product/hi 0 761302 5387579 5358195 2022-07-29T03:25:48Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=[[foundationsite:role/staff-contractors/|विकिमीडिया संस्थान द्वारा कार्यरत]] '''विकिमीडिया उत्पाद''' स्टाफ [[m:Special:MyLanguage/Wikimedia projects|विकिमीडिया साइटों]] की सुविधाओं को विकसित करते हैं, सुधारते हैं और अनुरक्षित करते हैं।{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">योगदानकर्ताएँ</span>]] * [[Readers|<span style="color:#2aa198">पाठक</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == उत्पाद के दौरान == * [[Special:MyLanguage/Product Principles|उत्पाद के सिद्धांत]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (पूर्व: [[Special:MyLanguage/Technical Collaboration Guidance|तकनीकी सहयोग मार्गदर्शन]]) * [[Special:MyLanguage/Design/Statement of purpose|डिज़ाइन का उद्देश्य कथन]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|उत्पादों के लिए डेटा और अनुसंधान जानकारी]] * [[Special:MyLanguage/Wikimedia Research/Showcase|मासिक अनुसंधान प्रदर्शन]] === कार्यक्रम === * [[m:Special:MyLanguage/Communications/Audience research|दर्शक अनुसंधान]] * [[m:Special:MyLanguage/Community health initiative|सामुदायिक स्वास्थ्य पहल]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|नए सम्पादक के अनुभव]] (2017–2018) * [[m:Special:MyLanguage/New Readers|नए पाठक]] — चल रहे शोध जो उन देशों में संभावित विकीमीडिया पाठकों को समझने पर केंद्रित हैं जहाँ इंटरनेट तक पहुंच तेजी से बढ़ रही है। (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|कॉमन्स पर संरचित डेटा]] === परियोजना पृष्ठ === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|वार्षिक योजना लक्ष्य: नया कंटेंट]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|आधुनिक मोबाइल योगदान]] * [[Special:MyLanguage/Android editing features|एंड्रॉइड संपादन सुविधाएँ]] * [[Special:MyLanguage/Content translation/V2|सामग्री अनुवाद, V2]] * [[Special:MyLanguage/Growth/Growth team updates|विकास]] * [[Special:MyLanguage/Language tools|Translate एक्सटेंशन और Translate Wiki प्रक्रिया को सुधारना]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|iOS संपादन]] * [[Special:MyLanguage/VisualEditor on mobile|विसुअल-आधारित मोबाइल संपादन]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''वार्षिक योजना लक्ष्य: डेटा का बेहतर इस्तेमाल''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|डेटा का बेहतर उपयोग]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|डेटा संग्रह: उपकरण]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|स्टीवार्डशिप की रिपोर्ट करना]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''वार्षिक योजना लक्ष्य: सामुदायिक इच्छा-सूची''']] * [[m:Special:MyLanguage/Community Tech#Projects|इच्छा-सूची]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|छोटे सदस्य-समूहों के लिए समर्थन]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|कार्यक्रम और प्रतिस्पर्धा के आयोजकों के लिए तकनीकी उपकरण]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''वार्षिक योजना लक्ष्य: गैर-उत्पीड़न उपकरण''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|रिपोर्ट करने के लिए प्रक्रिया]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''वार्षिक योजना लक्ष्य: विकिडेटा''']] '''अन्य:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 वार्षिक योजना लक्ष्य: प्लैटफॉर्म विकास CDP] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|MobileFrontend और MinervaNeue के फ्रंट-एंड संरचना पर नज़र डालना]] ** [[Special:MyLanguage/Parsing/Parser Unification|पार्सर एकीकरण]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|TemplateStyles]] * [[m:Special:MyLanguage/Movement Organizers|आंदोलन आयोजकों के बारे में]] (2019) == मेट्रिक्स == The [[Special:MyLanguage/Product Analytics|उत्पाद आँकड़ों]] के ट्रैक नए मेट्रिक्स स्थापित करते हैं जिनकी मदद से आंदोलन की प्रगति के बारे में जाना जा सकता है। [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span class="mw-translate-fuzzy">मेट्रिक्स का $1 रिपोर्ट विकिमीडिया आंदोलन के औसत प्रगति का पता लगाता है।</span>]] == उत्पाद दल == एक दर्शक दल विशिष्ट उपयोगकर्ता प्रवाह और आवश्यकताओं के अनुसार विकसित सुविधाओं का एक समूह पर काम करता है। === योगदानकर्ताएँ === हम मुफ्त ज्ञान बनाने और संपादित करने के लिए सहयोगी, समावेशी उपकरण बनाते हैं। * Phabricator टास्क बोर्ड्स: [[phab:tag/contributors-team/|#Contributors-Team]] (अक्सर उपयुक्त नहीं) * पृष्ठ: [[Special:MyLanguage/Contributors|योगदानकर्ताएँ]] * दल: ====== गैर-उत्पीड़न उपकरण ====== * Phabricator टास्क बोर्ड: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * पृष्ठ: [[Special:MyLanguage/Anti-Harassment Tools|गैर-उत्पीड़न उपकरण]] ====== सामुदायिक तकनीकी ====== * [[phab:project/board/1274/|<span class="mw-translate-fuzzy">Phabricator टास्क बोर्ड:</span>]] * पृष्ठ: [[m:Special:MyLanguage/Community Tech|सामुदायिक तकनीकी]] ====== संपादन ====== * Phabricator टास्क बोर्ड्स: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * पृष्ठ: [[Special:MyLanguage/Editing team|संपादन दल]] ====== विकास ====== * Phabricator टास्क बोर्ड: [[phab:project/board/1114/|#Growth-Team]] * पृष्ठ: [[Special:MyLanguage/Growth|विकास]] ====== भाषा ====== * Phabricator टास्क बोर्ड: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * पृष्ठ: [[Special:MyLanguage/Wikimedia Language engineering|विकिमीडिया भाषा अभियांत्रिकी]] === पाठक === हम सभी ज्ञान के लिए विशेष सीखने और पठन का अनुभव तैयार करते हैं। * पृष्ठ: [[Special:MyLanguage/Readers|पाठक]] * Phabricator टास्क बोर्ड: [https://phabricator.wikimedia.org/tag/reading/ #reading] * दल: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|एंड्रॉइड]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|पार्सिंग]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|उत्पाद अर्थव्यवस्था]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|वेब पर पढ़ना]] ====== * [[Reading/Component responsibility|कोड पठन दायित्व]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|मासिक पृष्ठ दृश्य, मई २०१३-जनवरी २०१९। File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === तकनीकी कार्यक्रम प्रबंधन === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> पृष्ठ: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] प्रमुख: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === उत्पाद डिज़ाइन === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> पृष्ठ: [[Special:MyLanguage/Design#Product Design|उत्पाद डिज़ाइन]] निर्देशक: [[User:MNovotny_(WMF)|Margeigh Novotny]] === उत्पाद के आँकड़ें === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> पृष्ठ: [[Special:MyLanguage/Product Analytics|उत्पाद के आँकड़ें]] प्रमुख: Kate Zimmerman === उत्पाद डिज़ाइन नीति === <!--''[यहाँ पर पारिचायिक टेक्स्ट]''--> पृष्ठ: [[Special:MyLanguage/Design#Design Strategy|उत्पाद डिज़ाइन नीति]] प्रमुख: Margeigh Novotny === विकिडेटा === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * पृष्ठ: [[d:Wikidata:Main Page|Wikidata]] * प्रमुख: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Phabricator त्रुटियाँ और कार्य बोर्ड: [[phab:project/profile/71/|#wikidata]] * चर्चा सूची: wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == लक्ष्य == {|class="wikitable" |- !scope="row"| २०१९-२०२० | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q१: जुलाई–सितम्बर २०१९]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q२: अक्टूबर–दिसम्बर २०१९]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q३: जनवरी–मार्च २०२०]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q४: अप्रैल–जून २०२०]]--> |- !scope="row"| २०१८–१९ | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q१: जुलाई–सितम्बर २०१८]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q२: अक्टूबर–दिसम्बर २०१८]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q३: जनवरी–मार्च २०१९]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q४: अप्रैल–जून २०१९]] |- !scope="row"| २०१७–१८ | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q१: जुलाई–सितम्बर २०१७]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q२: अक्टूबर–दिसम्बर २०१७]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q३: जनवरी–मार्च २०१८]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q४: अप्रैल–जून २०१८]] |- !scope="row"| २०१६–१७ | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q१: जुलाई–सितम्बर २०१६]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q२: अक्टूबर–दिसम्बर २०१६]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q३: जनवरी–मार्च २०१७]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q४: अप्रैल–जून २०१७]] |- !scope="row"| २०१५–१६ | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q१: जुलाई–सितम्बर २०१५]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q२: अक्टूबर–दिसम्बर २०१५]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q३: जनवरी–मार्च २०१६]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q४: अप्रैल–जून २०१६]] |} == वार्षिक रोडमैप == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|उत्पाद के लिए वार्षिक योजना २०१८-१९]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|उत्पाद के लिए वार्षिक योजना २०१७–१८]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|उत्पाद के लिए वार्षिक योजना २०१६–१७]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|२०१६ उत्पाद सारांश]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|२०१५ उत्पाद प्रौद्योगिकी समीक्षा]] [[Category:WMF Projects{{#translation:}}]] huwnzhw8xc0qip6cevmhpgnadp4xqu1 Wikimedia Product/pt-br 0 764715 5387590 5358209 2022-07-29T03:26:00Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1='''Produto da Wikimedia''' é mantido pela [[foundationsite:role/staff-contractors/|equipe da Wikimedia Foundation]]. Para construir, melhorar e, manter as características de [[m:Special:MyLanguage/Wikimedia projects|Sites da Wikimedia]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Colaboradores</span>]] * [[Readers|<span style="color:#2aa198">Leitores</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Através do produto == * [[Special:MyLanguage/Product Principles|Princípios do produto]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|Diretriz de colaboração técnica]]) * [[Special:MyLanguage/Design/Statement of purpose|Design Declaração de Propósito]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|Dados e informações de pesquisa para produtos]] * [[Special:MyLanguage/Wikimedia Research/Showcase|Vitrines de pesquisa mensal]] === Programas === * [[m:Special:MyLanguage/Communications/Audience research|Pesquisa de público]] * [[m:Special:MyLanguage/Community health initiative|Iniciativa de saúde comunitária]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|Novas Experiências de Editor]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Novos leitores]] — pesquisa contínua que se concentra na compreensão de potenciais leitores da Wikimedia em países onde o acesso à Internet está crescendo rapidamente. (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|Dados estruturados em Commons]] === Páginas do Projeto === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|Objetivo do plano anual: novo conteúdo]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|Contribuições Móveis Avançadas]] * [[Special:MyLanguage/Android editing features|Recursos de Edição do Android]] * [[Special:MyLanguage/Content translation/V2|Tradutor de conteúdo, V2]] * [[Special:MyLanguage/Growth/Growth team updates|Crescimento]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) == Metricas == <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == Equipes de produto == <span class="mw-translate-fuzzy">Uma equipe do público-alvo abrange um conjunto de recursos desenvolvidos de acordo com os fluxos e necessidades específicos do usuário.</span> === Colaboradores === Nós construímos ferramentas colaborativas e inclusivas para criar e editar o conhecimento livre. * Placas de tarefas do Phabricator: [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * Página: [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * Equipe: ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * Placa Phabricator: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Página: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === Leitores === Nós construímos experiências excepcionais de aprendizagem e leitura para a soma de todos os conhecimentos. * Página: [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * Painel de tarefas do Phabricator: [https://phabricator.wikimedia.org/tag/reading/ #reading] * Equipes: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|Responsabilidade pelo código de leitura]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === Wikidata === Wikidata é uma base de conhecimento livre e aberta que pode ser lida e editada por humanos e máquinas. Este projeto é mantido pelo departamento de Desenvolvimento de Software e Engenharia da [[WMDE Engineering | Wikimedia Deutschland]]. * Página: [[d:Wikidata:Main Page|Wikidata]] * Líder: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Phabricator bugs e placa de tarefas: [[phab:project/profile/71/|#wikidata]] * Lista de discussão: wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Objetivos == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: Julho a setembro de 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: Outubro a dezembro de 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: Janeiro a março de 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: Abril a junho de 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: Julho a setembro de 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: Outubro a dezembro de 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: Janeiro a março de 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: De abril a junho de 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: Julho a setembro de 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: De outubro a dezembro de 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: Janeiro a março de 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: abril - junho de 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: Julho a setembro de 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: Outubro a dezembro de 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: Janeiro a março de 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: Abril a junho de 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: Julho a setembro de 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: Outubro a dezembro de 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: Janeiro a março de 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: Abril a junho de 2016]] |} == Roteiro Anual == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|Plano anual para o produto 2018-2019]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|Plano anual para o produto 2017–2018]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|Plano anual para o produto 2016-2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|Resumo do produto 2016]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|Análise de produto e tecnologia 2015]] [[Category:WMF Projects{{#translation:}}]] 2t6ncyu6f7utf9cq7h0tcaxyizuzwnh Manual:Installing MediaWiki/hu 100 765082 5387498 5385512 2022-07-28T22:45:22Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} Ez a lap leírja a MediaWiki manuális telepítéséhez és konfigurálásához szükséges lépéseket. A MediaWiki telepítése nehézséget okozhat, ha nincs tapasztalatod Apache-vel (webszerver-szoftver), PHP-val és MySQL-lel/MariaDB-vel (adatbázis). <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == A MediaWiki letöltése == <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> A letölthető állományok <code>.tar.gz</code> vagy <code>.zip</code> formátumú archívumok, vagyis használat előtt ki kell őket csomagolni. <nowiki /> <span class="mw-translate-fuzzy">Ez történhet helyben (később FTP-n feltöltéssel) vagy egyből a webszerveren.</span> Ezt Windowson például a [https://www.7-zip.org/ 7-Zip] (ingyenes), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] vagy [https://www.izarc.org/ IZArc] (ingyenes) programokkal lehet megtenni. Linuxon és Mac OS X-en a beépített untar módszerrel lehet őket kibontani: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == Fájlok feltöltése a szerveredre == <div class="mw-translate-fuzzy"> Ha még nem töltötted fel a fájlokat a webszerverre, tedd meg most. </div> Erre az alábbi módokon van lehetőséged: # a tömörített állomány felmásolásával <div class="mw-translate-fuzzy"> # FTP-klienssel (például [https://filezilla-project.org/ FileZilla], Windowson, Linuxon és OSX-en is, nyílt forrású; vagy OSX-en [https://cyberduck.io/ Cyberduck]) </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> Ha a szoftverben van „feltöltött állományok neveinek kisbetűsre változtatása” opció, kapcsold ki. <span class="mw-translate-fuzzy">Ha installáltad az Apache-t, a telepítési útvonalat a <code>httpd.conf</code> állomány tárolja (ez a [$docroot DocumentRoot] könyvtárban van; valószínűleg $1 vagy {{$2|apache-könyvtár}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Megjegyzés: Ez az Ubuntu 14.04-ben az Apache 2.4.7-tel megváltozott; az alapértelmezett útvonal az <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Adatbázis létrehozása == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Ha az adatbázis nem a webszerverrel azonos domainen fut, az alábbiak szerint meg kell adnod a pontos helyet (az alábbi esetben mediawiki.example.com): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span class="mw-translate-fuzzy">UNIX-on és Linuxon a MySQL- és MariaDB-naplóbejegyzések egy fájlban tárolódnak, amely tartalmazza az adatbázishoz használt jelszót is.</span> Ha ez zavar, a parancsok futása után [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file a MySQL dokumentációját] követve töröld és tiltsd le a <code>.mysql_history</code> fájlt.}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (majd írd be a jelszót) createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} == A telepítőszkript futtatása == Következő lépéskét nyisd meg a MediaWiki-telepítésed index.php lapját egy böngészőben: kövesd a {{ll|Manual:Config script}} utasításait. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Maradj naprakész! == Miután kész vagy a telepítéssel, kövesd a legújabb kiadásokat, és ügyelj adatbázisod biztonságára! {{Clickable button 2|<span class="mw-translate-fuzzy">[[$maillist|Iratkozz fel a kiadásokat bejelentő levelezési listára.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=A root felhasználónak megjegyezhető jelszót válassz.}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Lásd még == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] kjfrkrn665df5jtfohiihrn1hv5rp9e Product Analytics 0 776256 5387485 5358132 2022-07-28T22:44:15Z MKampurath (WMF) 17517352 Added June 2022 Wikimedia Movement metrics wikitext text/x-wiki == About Us == {{tocright}} [[File:June 2022 Wikimedia movement metrics.pdf|alt=Monthly report on key Product metrics|thumb|300x300px|Monthly report on key Product metrics]] Nurturing data-informed decision-making in [[Wikimedia Product|Product]] since 2018-02-01. === Our [[Product Analytics/Mission and Values|Mission & Values]] === We deliver '''quantitatively-based user insights to inform decision-making''' in support of Wikimedia’s strategic direction toward [[m:Strategy/Wikimedia_movement/2018-20|service and equity]]. ''We strive to provide guidance, insights, and data that are:''<br> '''Ethical • Trusted • Impactful • Accessible • Inclusive • Inspired''' === What We Do === Product Analytics contributes to the Wikimedia Movement through our work with [[Wikimedia_Product|Product]] teams and departments across the Foundation. Our responsibilities include: *Empowering others to make data-informed decisions through education and self-service analytics tools *Helping set and track goals that are achievable and measurable *Ensuring that Wikimedia products collect useful, high quality data without harming user privacy *Extracting insights through ad-hoc analyses and machine learning projects *Building dashboards and reports for tracking success and health metrics *Designing and analyzing experiments (A/B tests) *Developing tools and software for working with data, in collaboration with [[wikitech:Data Engineering|Data Engineering]] and [[Wikimedia_Product|Product]] teams. *Addressing data-related issues in collaboration with teams like [[wikitech:Data Engineering|Data Engineering]], [[Wikimedia Security Team|Security]], and [[meta:Legal|Legal]] == Who is on the team == ''Listed alphabetically by first name within each section'' === Leadership === *[[metawiki:User:KZimmerman_(WMF)|Kate Zimmerman]], Director of Data Science *[[:meta:User:MPopov (WMF)|Mikhail Popov]], Data Science Manager === Team Members === *Connie Chen, Sr. Data Scientist *Irene Florez, Data Scientist III *Jennifer Wang, Staff Data Scientist *[[User:Mayakp.wiki|Maya Kampurath]], Sr. Analyst *[[meta:User:MNeisler (WMF)|Megan Neisler]], Sr. Data Scientist *[[:meta:User:MWang (WMF)|Morten Warncke-Wang]], Staff Data Scientist *[[meta:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]], Sr. Data Scientist *[[meta:User:SNowick (WMF)|Shay Nowick]], Sr. Data Scientist == Product Team Support == Each analyst is a [[Product Analytics/Working with Product Analytics|point person]] for a team, project, or program. Our goals are to maintain context and domain knowledge while also allowing for flexibility in analyst work assignments. ''For more information about how we work with Product teams, see '''[[Product Analytics/Working with Product Analytics|Working with Product Analytics]]'''.'' {| class="wikitable" !Analyst !FY21-22 Point person for… |- |Connie |[[Wikimedia Search Platform|Search Platform]] & [[Structured data across Wikimedia|Structured Data]] |- |Irene |[[meta:Campaigns/Foundation Campaigns Team|Campaigns]] & Data as a Service |- |Jennifer |[[metawiki:Community_health_initiative#Anti-Harassment_Tools|Anti-Harassment Tools]] & [[Readers/Web/Team|Web]] |- |Maya |[[wikitech:Metrics Platform|Metrics Platform]] & Data as a Service |- |Megan |[[Editing team|Editing]] & [[Wikimedia Language engineering|Language]] |- |Morten |[[Growth]] & Newcomer Experience |- |Neil |[[Inuka_team|Inuka]] & Trust & Safety Engineering |- |Shay |[[Wikimedia Apps/Team/Android|Android]] & [[Wikimedia Apps/Team/iOS|iOS]] |} Teams that do not currently have an assigned point person are encouraged to '''[[phab:project/profile/3313/|submit requests through Phabricator]]'''. Depending on the team's capacity and organizational needs, we may also accept requests from others in the Wikimedia Foundation. The team reserves "10 percent time" to work on professional development. == How to get help with data or analysis == === Submitting Requests === If you'd like to request data, analysis, or advice, create a task in '''[[phab:project/profile/3313/|Phabricator]]''' or send an email to '''product-analytics@wikimedia.org'''. Requests are reviewed by Product Analytics and inform the direction and priorities of data projects. A team member will follow up about whether we’ll be able to work on your request. Some questions may be suited to consultation hours; see [[Product Analytics/Consultation Hours|Product Analytics Consultation Hours]] for more information and a link to book appointments. Provide the following information to help us prioritize and respond to your request appropriately: * '''Name for main point of contact and contact preference''' ::''We use Phabricator to track our work and provide progress updates. Please let us know if you would like us to follow up by other methods (e.g. email).'' * '''What teams or departments is this for?''' ::''This helps us understand who will be using the analysis.'' * '''What are your goals? How will you use this data or analysis?''' ::''This helps us understand the context and priority. What decisions do you need data to inform? Will you take different actions depending on the direction of the data? Do you want to share data publicly? Do you want to include data in a narrative or message (e.g. for PR, audience engagement, or fundraising)?'' * '''What are the details of your request? Include relevant timelines or deadlines''' ::''Is there a date after which the analysis will no longer be useful? Please provide any timeline/relevant deadlines, requested formats, examples, links to documentation, or other information that would help us understand your request.'' * '''Is this request urgent or time sensitive?''' ::''We try to reply to “Urgent” requests immediately and “Time sensitive” requests by the end of the workday. All other requests will be prioritized during our weekly triage.'' '''Note:''' We use [[phab:project/profile/3313/|Phabricator]] to track our work, and by default tickets are publicly visible. '''If any part of your request is sensitive and should be kept confidential, let us know.''' === Consultation Hours === Analysts host weekly [[Product Analytics/Consultation Hours|consultation hours (details)]]. Click [https://calendar.google.com/calendar/selfsched?sstoken=UUxHUVRSLTdXNUd1fGRlZmF1bHR8ZTMyNDQzMTI2MjQ2Y2U3NDg3ODExZTc0MWQ4MmI4ZTk here to view the calendar] or schedule an appointment. === Data FAQs === ''See [[metawiki:Research:FAQ|meta:Research:FAQ]]'' == How to contact us == * Contact information for team members are available on their user pages (linked above). * Group mailing list: product-analytics{{@}}wikimedia.org == Further information == === Data references and reports === *[[Product Analytics/Comparison datasets|Comparison datasets]] *[[Wikimedia Product/Data dictionary|Data Dictionary]] (documents data sources, such as those available in Superset and Turnilo) *[[Wikimedia Product/Data glossary|Data Glossary]] (definitions for core metrics) *[[Product Analytics/Data Products|Data Products]] (various deliverables such as reports, analyses, and datasets) *[[Product Analytics/Movement metrics|Movement metrics]] *[[gerrit:plugins/gitiles/analytics/wmf-product/jobs/+/refs/heads/master|ETL jobs]] === Guidelines and best practices === *[[wikitech:Analytics/Data access guidelines|Data access guidelines]] *[[Product Analytics/Query Style Guide|Query style guide]] *[[Product Analytics/Reporting Guidelines|Reporting Guidelines]] *[[Product Analytics/Dashboarding Guidelines|Dashboarding Guidelines]] === Documentation for tools we use === *[[Phabricator]] (managing requests and tracking work) *[[wikitech:Analytics/Systems/Superset|Superset]] (WMF internal dashboards and reports) **[[Product Analytics/Superset Access|Obtaining access to Superset/Turnilo]], with explanation of LDAP/Developer Account terminology *[[wikitech:Analytics/Systems/Turnilo-Pivot|Turnilo]] (WMF internal tool for pivoting and exploring data) *[[wikitech:Event_Platform|Event Platform]] (Various event stream distribution and processing systems we employ at WMF) *[[wikitech:Analytics/Systems/Matomo|Matomo/Piwik]] (JavaScript tracking client used for wikimediafoundation.org and other smaller-scale sites) *[[wikitech:Google_Search_Console_access|Google Search Console access]] === Team references === *[[Product Analytics/Mission and Values|Product Analytics Mission and Values]] *[[Product Analytics/Team norms|Product Analytics Team norms]] *[[Product Analytics/Working with Product Analytics|Working with Product Analytics]] *[[Product Analytics/Chore Wheel|Chore Wheel]] *[[phab:project/board/3313/|Phabricator board]] *[[Product Analytics/Onboarding|Onboarding notes for new team members]] *[[Product Analytics/Offboarding|Offboarding]] *[[Product Analytics/Contingency Carousel|Contingency Carousel]] *[[Product Analytics/Fun|Fun]] [[Category:Wikimedia Foundation teams internals]] b24kdxcy6zte710ub73jrdki8dn6xez Template:InstallationNav/fa 10 785306 5387196 5384783 2022-07-28T21:17:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Translations:HHVM/5/en 1198 785968 5387447 4224350 2022-07-28T22:32:03Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki HHVM is a new way for websites to run [[$1|MediaWiki]] (written in [[w:PHP|PHP]]). 1gjtws180gd46lm4jbs3rrysvts25b5 HHVM/en 0 785989 5387449 5240444 2022-07-28T22:32:05Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = Support in MediaWiki for HHVM (HipHop Virtual Machine) and deployment to the Wikimedia cluster | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :See [[Special:MyLanguage/HHVM/About|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work. {{note|1=In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref> After discussion<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See {{phabricator|T176209}} and {{phabricator|T192166}}.}} '''[[w:HHVM|HHVM]]''' is a PHP interpreter tool (concretely a virtual machine that compiles PHP bytecode to native instructions at runtime) that was deployed on Wikimedia servers in 2014, decreasing the loading time for: any page you view while logged in, and for saving pages that you've edited whether you are logged in or not. == Roadmap == HHVM is a new way for websites to run [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (written in [[w:PHP|PHP]]). It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT). HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users. This page is about Wikimedia-sponsored work on HipHop support in MediaWiki, and its deployment to Wikimedia production wikis. Historically, the HipHop compiler was a project by Facebook which involved compiling PHP code into C++ for purposes of speeding up the language. Facebook has since abandoned this project, and now their development efforts are focused on HHVM itself instead. Here is the general plan for deploying HHVM to the production cluster in 2014: * Deployment to Beta Cluster (currently ongoing work, in parallel with other work) {{done}} * Week of July 21: deployment to a few job runners in production {{done}} * Deploy to test.wikipedia.org application server {{done}} * Deploy Varnish module allowing partial deployment to a fraction of application servers{{Done}} * Limited deployment to small number of application servers {{Done}} * Ramp up deployment to more application servers until most servers use HHVM{{done}} * Deploy to remainder of services{{done}} === HHVM work === Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. == Rationale == It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.<ref> [http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar'' </ref><ref> [http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic. </ref> As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular. Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.<ref> "[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower." </ref> Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission. Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> in a solution: [http://hhvm.com HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages. We're quite confident that this will result in big performance improvements on our sites as well. == What does HipHop do for our end users? == MediaWiki is written in PHP, a language that is [[w:Interpreter (computing)|interpreted]] at run-time. The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed. These caches only serve users that are not logged in.<ref> By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page. This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you. </ref> Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include: *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. == How does our development work on HipHop affect MediaWiki developers? == In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend. This will be on a totally opt-in basis which can be disabled at any time. This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases. It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend. For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to. However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so. == See also == * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Setting up HHVM in {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presenting at @Scale about migrating to HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM in production: what that means for Wikimedia developers] == References and footnotes == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] 0h3aldk3q1f3qptu70yfjarm1pwkzid Translations:Manual:Magic words/5/ru 1198 790625 5386696 4313251 2022-07-28T17:39:19Z Артём 13327 17625157 wikitext text/x-wiki Всякий раз, когда MediaWiki находит текст между двойными скобками ($4), необходимо решить, является ли XXX [[$1|переменной]], [[$2|функцией парсера]] или [[$3|шаблоном]]. Чтобы сделать это, задается несколько вопросов: gwnxx1rqr8d15ckhczh1omng7ns3v59 Translations:Manual:Magic words/6/ru 1198 790626 5386698 2803263 2022-07-28T17:39:56Z Артём 13327 17625157 wikitext text/x-wiki '''Есть ли связанное ID волшебного слова?''' В качестве первого шага разбора разметки в виде $1, MediaWiki пытается перевести ''$2'' в ID волшебного слова. Таблица переводов определяется в $magicWords. guedwe6kdr77gx71ucky6e1hc1zuaxl Translations:Manual:Magic words/7/ru 1198 790627 5386700 4313253 2022-07-28T17:40:26Z Артём 13327 17625157 wikitext text/x-wiki Если нет связанного с ''$2'' ID волшебного слова, предполагается, что ''$2'' — это [[$1|шаблон]]. ptyrn9lv59vfe0bptem3ioo0wla5t0g HHVM/pl 0 799773 5387454 5240448 2022-07-28T22:32:09Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = <span lang="en" dir="ltr" class="mw-content-ltr">Support in MediaWiki for HHVM (HipHop Virtual Machine) and deployment to the Wikimedia cluster</span> | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/HHVM/About|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref> After discussion<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See {{phabricator|T176209}} and {{phabricator|T192166}}.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">'''[[w:HHVM|HHVM]]''' is a PHP interpreter tool (concretely a virtual machine that compiles PHP bytecode to native instructions at runtime) that was deployed on Wikimedia servers in 2014, decreasing the loading time for: any page you view while logged in, and for saving pages that you've edited whether you are logged in or not.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Roadmap == </div> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM is a new way for websites to run [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (written in [[w:PHP|PHP]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT).</span> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This page is about Wikimedia-sponsored work on HipHop support in MediaWiki, and its deployment to Wikimedia production wikis. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Historically, the HipHop compiler was a project by Facebook which involved compiling PHP code into C++ for purposes of speeding up the language. Facebook has since abandoned this project, and now their development efforts are focused on HHVM itself instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is the general plan for deploying HHVM to the production cluster in 2014: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Deployment to Beta Cluster (currently ongoing work, in parallel with other work) {{done}} * Week of July 21: deployment to a few job runners in production {{done}} * Deploy to test.wikipedia.org application server {{done}} * Deploy Varnish module allowing partial deployment to a fraction of application servers{{Done}} * Limited deployment to small number of application servers {{Done}} * Ramp up deployment to more application servers until most servers use HHVM{{done}} * Deploy to remainder of services{{done}} </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === HHVM work === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Rationale == </div> <span lang="en" dir="ltr" class="mw-content-ltr">It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> in a solution: [http://hhvm.com HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're quite confident that this will result in big performance improvements on our sites as well.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == What does HipHop do for our end users? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is written in PHP, a language that is [[w:Interpreter (computing)|interpreted]] at run-time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These caches only serve users that are not logged in.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does our development work on HipHop affect MediaWiki developers? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will be on a totally opt-in basis which can be disabled at any time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.</span> == Zobacz też == <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Setting up HHVM in {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presenting at @Scale about migrating to HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM in production: what that means for Wikimedia developers] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == References and footnotes == </div> <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] 8kk3ejvlv89wltt9ght08ooorhl9t7b HHVM/zh 0 800024 5387457 5240451 2022-07-28T22:32:12Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = 支持MediaWiki for HHVM(HipHop虚拟机)并部署到维基媒体集群 | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/HHVM/About|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work.</span> {{note|1=从2017年九月,脸书宣布HHVM未来不再提供PHP兼容性。<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref>经过讨论,<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] 在 ''wikitech-l''</ref>维基媒体基金会决定迁移维基媒体基金会服务器至PHP 7。HHVM支持已经从MediaWiki中移除。参见{{phabricator|T176209}}和{{phabricator|T192166}}。}} <span lang="en" dir="ltr" class="mw-content-ltr">'''[[w:HHVM|HHVM]]''' is a PHP interpreter tool (concretely a virtual machine that compiles PHP bytecode to native instructions at runtime) that was deployed on Wikimedia servers in 2014, decreasing the loading time for: any page you view while logged in, and for saving pages that you've edited whether you are logged in or not.</span> == 路线图 == <span class="mw-translate-fuzzy">HHVM是一种新的让网站运行[[special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]](用PHP编写)的方式。</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT).</span> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This page is about Wikimedia-sponsored work on HipHop support in MediaWiki, and its deployment to Wikimedia production wikis. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Historically, the HipHop compiler was a project by Facebook which involved compiling PHP code into C++ for purposes of speeding up the language. Facebook has since abandoned this project, and now their development efforts are focused on HHVM itself instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is the general plan for deploying HHVM to the production cluster in 2014: </div> * 部署到Beta群集(当前正在进行的工作,与其他工作并行){{done}} * Week of July 21: deployment to a few job runners in production {{done}} * Deploy to test.wikipedia.org application server {{done}} * Deploy Varnish module allowing partial deployment to a fraction of application servers{{Done}} * Limited deployment to small number of application servers {{Done}} * Ramp up deployment to more application servers until most servers use HHVM{{done}} * Deploy to remainder of services{{done}} === HHVM工作 === Phabricator: [[phabricator:project/board/79/|打开任务]], [[phabricator:project/board/79/query/all/|全部任务]]. == 原理 == <span lang="en" dir="ltr" class="mw-content-ltr">It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> in a solution: [http://hhvm.com HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're quite confident that this will result in big performance improvements on our sites as well.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == What does HipHop do for our end users? == </div> MediaWiki使用PHP编写,这昰种运行时[[w:Interpreter (computing)|解释]]的语言。 <span lang="en" dir="ltr" class="mw-content-ltr">The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These caches only serve users that are not logged in.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does our development work on HipHop affect MediaWiki developers? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will be on a totally opt-in basis which can be disabled at any time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.</span> == 参见 == <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Setting up HHVM in {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presenting at @Scale about migrating to HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM in production: what that means for Wikimedia developers] </div> ==参考和注释== <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] tqfdzqi55r0gysm3x09hz3zi7bkosoi Manual:Installing MediaWiki/pt 100 800314 5387503 5384978 2022-07-28T22:45:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">O MediaWiki pode ser difícil de instalar para o utilizador médio, que não tenha experiência com o Apache, PHP e MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Transferir o ''software'' MediaWiki == <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">Os ficheiros transferidos estão no formato <code>.tar.gz</code>, por isso terão de ser descomprimidos antes de serem utilizados.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span class="mw-translate-fuzzy">Isto pode ser efetuado localmente (e depois enviados via FTP) ou diretamente no seu servidor.</span> Isto é normalmente efetuado com ''software'', tais como [https://www.7-zip.org/ 7-Zip] (grátis), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] ou [https://www.izarc.org/ IZArc] (grátis) no Windows. No Linux e no Mac OS X, pode descomprimir o ficheiro utilizando este comando: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == Enviar ficheiros para o seu servidor == <div class="mw-translate-fuzzy"> Se ainda não enviou os ficheiros para o seu servidor da Web, faça-o agora. </div> Envie os ficheiros para a diretoria da Web do seu servidor da Web: # diretamente, copiando a pasta descomprimida <div class="mw-translate-fuzzy"> # utilizando um cliente FTP, tal como o [https://filezilla-project.org/ FileZilla] (''Software'' de Código Aberto, Windows, OSX e Linux) ou [https://cyberduck.io/ Cyberduck] (OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> Se a sua ferramenta de envio tem uma opção "alterar os nomes dos ficheiros para minúsculas", tem de desativar isto. <span class="mw-translate-fuzzy">Se instalou o Apache, a diretoria correta é especificada no seu ficheiro <code>httpd.conf</code> (é a diretiva [$docroot DocumentRoot], tipicamente <code>/var/www/</code> ou <code><apache-folder>/htdocs</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Nota: isto mudou no Ubuntu 14.04 com Apache 2.4.7, em que o ficheiro de configuração primário para as configurações e diretórios do servidor Apache é <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Altere o nome da pasta que carregou, para aquilo que pretende ter no URL. <span class="mw-translate-fuzzy">Se o seu servidor da Internet está a ser executado como <code>http://localhost</code>, por exemplo, alterar o nome para <code>/w/</code> significa que pretende aceder à sua wiki em <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span class="mw-translate-fuzzy">'''''Não lhe chame <code>/wiki/</code> se pretende usá-lo como um [[Special:MyLanguage/Manual:Short URL|URL curto]]'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Criar uma base de dados == </div> <div class="mw-translate-fuzzy"> O MediaWiki irá pedir-lhe o nome da base de dados e do utilizador, e tentará criá-los se estes ainda não existirem. </div> <div class="mw-translate-fuzzy"> Se já tem um servidor de base de dados e sabe a palavra-passe do utilizador ''root'' da mesma, o ficheiro de comandos da instalação do MediaWiki pode criar uma nova base de dados nova por si. </div> <div class="mw-translate-fuzzy"> Se não sabe a palavra-passe do utilizador root, como será o caso se estiver a usar um servidor alojado, por exemplo, terá de criar uma base de dados nova agora. </div> <span class="mw-translate-fuzzy">Neste momento, tem de usar SQLite, MariaDB/MySQL ou PostgreSQL para armazenar o conteúdo da sua wiki.</span> <span class="mw-translate-fuzzy">Se não tiver a certeza sobre qual a base de dados escolher, utilize MariaDB, pois é a melhor suportada pelo MediaWiki.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">Na página de instalação, terá de escolher um nome para a base de dados (que pode ser um qualquer) e para o diretório da base de dados SQLite.</span> Para o diretório da base de dados, o ficheiro de instalação tentará usar um subdiretório fora da raiz do documento e criá-lo se necessário. Se este diretório não for seguro (por exemplo, se puder ser lido através da Internet), mude-o manualmente para evitar que seja acessível por qualquer pessoa na Internet. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Consulte a respetiva documentação.</span> <span class="mw-translate-fuzzy">Em alternativa, entre em contacto com o seu fornecedor de alojamento e peça-lhes que criem uma conta para si.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Se a sua base de dados não estiver a ser executada no mesmo servidor físico onde está o seu servidor da Internet, terá de fornecer o nome do servidor físico do seu servidor da Internet &mdash; mediawiki.example.com no exemplo abaixo &mdash; como se segue: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span class="mw-translate-fuzzy">As bases de dados MySQL e MariaDB, em UNIX e em Linux, registam num ficheiro todas as consultas recebidas, incluindo a palavra-passe usada para a conta do utilizador.</span> <span class="mw-translate-fuzzy">Se isto o preocupa, apague o ficheiro <code>.mysql_history</code> depois de executar estes comandos.</span>}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Se está a usar o PostgreSQL, ou alguém terá de criar uma base de dados e um utilizador para si, ou então forneça simplesmente o nome de um utilizador do PostgreSQL com privilégios de «superutilizador» no formulário de configuração.</span> <span class="mw-translate-fuzzy">Normalmente, este utilizador da base de dados tem o nome '''postgres'''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (depois insira a palavra-passe) createdb -O wikiuser my_wiki ou como superutilizador (que, por omissão, é postgres) execute os seguintes comandos na linha de comandos da base de dados: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> Tenha em atenção a [[phab:tag/postgreSQL|lista de problemas conhecidos ao executar o MediaWiki com o PostgreSQL]]. {{anchor|Run the installation script}} == Executar o ficheiro de instalação ==<!-- Atenção: Se alterar esta âncora, altere também as hiperligações para ela em: * Translations:Manual:Installing MediaWiki/35/pt --> <div class="mw-translate-fuzzy"> Depois de completar todos os passos acima, pode finalizar a instalação através de um navegador da Internet, acedendo ao URL index.php no seu navegador — verifique as instruções mencionadas em {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> == Passos adicionais == </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Mantenha a instalação atualizada! == Terminada a instalação, mantenha-a atualizada e mantenha o seu servidor seguro! {{Clickable button 2|<span class="mw-translate-fuzzy">[[$maillist|Subscreva a nossa lista de divulgação de novas versões.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Ver também == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] aetpa01olzz2zi3j0igg0zjqn1x8kjn Translations:Manual:Installation guide/11/pt 1198 801406 5387289 4700856 2022-07-28T21:57:09Z Baris6161TURK 17188421 wikitext text/x-wiki A miniaturização de imagens e o $texvc requerem programas adicionais. O $1 (requerido pelo VisualEditor) e outros serviços têm os seus requisitos próprios. i5mha3pcjqi4euem1orfesjt5zshnmd Wikimedia Product/ko 0 802071 5387581 5358201 2022-07-29T03:25:51Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=[[foundationsite:role/staff-contractors/|위키미디어 재단이 고용한]] '''위키미디어 제품''' 직원은 [[m:Special:MyLanguage/Wikimedia projects|위키미디어 사이트들]]의 기능들을 만들고 개선하고 정비합니다.{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">기여자</span>]] * [[Readers|<span style="color:#2aa198">독자</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == 제품에 대해 == * [[Special:MyLanguage/Product Principles|제품 원칙]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === 프로그램 === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|새 사용자 경험]] (2017–2018) * [[m:Special:MyLanguage/New Readers|새 독자]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|공용의 구조화된 데이터]] === 프로젝트 문서 === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|연간 계획 목표: 새 콘텐츠]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|고급 모바일 편집]] * [[Special:MyLanguage/Android editing features|안드로이드 편집 기능]] * [[Special:MyLanguage/Content translation/V2|내용 번역 V2]] * [[Special:MyLanguage/Growth/Growth team updates|성장]] * [[Special:MyLanguage/Language tools|번역 확장기능 및 번역 위키 과정 개선]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|iOS 편집]] * [[Special:MyLanguage/VisualEditor on mobile|시각 기반 모바일 편집]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === 기여자 === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * 팀: ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * 파브리케이터 작업 게시판: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === 위키데이터 === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * 파브리케이터 버그 및 작업 게시판: [[phab:project/profile/71/|#wikidata]] * 토론 목록: wikidata@lists.wikimedia.org {|class="wikitable" |+ 위키데이터 팀 목표 |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q1: 2017년 1월–3월] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q2: 4월-6월] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q3: 7월-9월] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q4: 10월-12월] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q1: 2016년 1월–3월] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q2: 4월-6월] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q3: 7월-9월] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q4: 10월-12월] |} == 목표 == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: 2019년 7월-9월]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: 2019년 10월-12월]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: 2020년 1월-3월]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: 2020년 4월-6월]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: 2018년 7월-9월]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: 2018년 10월-12월]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: 2019년 1월-3월]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: 2019년 4월-6월]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: 2017년 7월-9월]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: 2017년 10월–12월]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: 2018년 1월–3월]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: 2018년 4월-6월]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: 2016년 7월-9월]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: 2016년 10월–12월]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: 2017년 1월–3월]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: 2017년 4월-6월]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: 2015년 7월-9월]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: 2015년 10월–12월]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: 2016년 1월–3월]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: 2016년 4월-6월]] |} == 연간 로드맵 == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|2018-2019 연간 제품 계획]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|2017-2018 연간 제품 계획]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|2016-2017 연간 제품 계획]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|2016 제품 종합]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|2015 제품 & 기술 리뷰]] [[Category:WMF Projects{{#translation:}}]] ogwggsxxj5xd7qhfpf9j18c04d6w1z2 HHVM/ko 0 802351 5387452 5240446 2022-07-28T22:32:08Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = <span lang="en" dir="ltr" class="mw-content-ltr">Support in MediaWiki for HHVM (HipHop Virtual Machine) and deployment to the Wikimedia cluster</span> | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/HHVM/About|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref> After discussion<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See {{phabricator|T176209}} and {{phabricator|T192166}}.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">'''[[w:HHVM|HHVM]]''' is a PHP interpreter tool (concretely a virtual machine that compiles PHP bytecode to native instructions at runtime) that was deployed on Wikimedia servers in 2014, decreasing the loading time for: any page you view while logged in, and for saving pages that you've edited whether you are logged in or not.</span> == 로드맵 == <span lang="en" dir="ltr" class="mw-content-ltr">HHVM is a new way for websites to run [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (written in [[w:PHP|PHP]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT).</span> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This page is about Wikimedia-sponsored work on HipHop support in MediaWiki, and its deployment to Wikimedia production wikis. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Historically, the HipHop compiler was a project by Facebook which involved compiling PHP code into C++ for purposes of speeding up the language. Facebook has since abandoned this project, and now their development efforts are focused on HHVM itself instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is the general plan for deploying HHVM to the production cluster in 2014: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Deployment to Beta Cluster (currently ongoing work, in parallel with other work) {{done}} * Week of July 21: deployment to a few job runners in production {{done}} * Deploy to test.wikipedia.org application server {{done}} * Deploy Varnish module allowing partial deployment to a fraction of application servers{{Done}} * Limited deployment to small number of application servers {{Done}} * Ramp up deployment to more application servers until most servers use HHVM{{done}} * Deploy to remainder of services{{done}} </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === HHVM work === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Rationale == </div> <span lang="en" dir="ltr" class="mw-content-ltr">It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> in a solution: [http://hhvm.com HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're quite confident that this will result in big performance improvements on our sites as well.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == What does HipHop do for our end users? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is written in PHP, a language that is [[w:Interpreter (computing)|interpreted]] at run-time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These caches only serve users that are not logged in.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does our development work on HipHop affect MediaWiki developers? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will be on a totally opt-in basis which can be disabled at any time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.</span> == 같이 보기 == <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Setting up HHVM in {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presenting at @Scale about migrating to HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM in production: what that means for Wikimedia developers] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == References and footnotes == </div> <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] t2gsze47djipy33p9sphhdkoa6dd72u Anti-Harassment Tools 0 805537 5386248 5359494 2022-07-28T12:27:49Z TChan (WMF) 4257429 Updated team section to add second tech lead wikitext text/x-wiki {{Wikimedia engineering project information | name = Anti-Harassment Tools | description = | start = January 2017 | group = [[Contributors]] | team = [[User:TChan (WMF)|Thalia Chan]], [[m:User:DWalden (WMF)|Dom Walden]], [[User:STei (WMF)| Sandister Tei]], [[m:User:ARamirez (WMF)|Aida Ramirez]] | Phabricator = Anti-Harassment | EPM = [[User:NKohli (WMF)|Niharika Kohli]] (product) | updates = | progress = | perennial = yes | projectpage = meta:Community health initiative | backlog = [https://phabricator.wikimedia.org/project/board/2660/ On Phabricator] | display = {{{display|}}} }} The '''Anti-Harassment Tools''' team is a Wikimedia Foundation team that does technical work in support of the [[meta:Community health initiative|Community health initiative]]. {{Clear}} == Team == <gallery mode="packed"> File:Kohli, Niharika June 2019.jpg|[[User:NKohli (WMF)|Niharika Kohli]]<br />Product Manager File:Wikimedia Foundation office camera shy 250px.png|[[User:TChan (WMF)|Thalia Chan]]<br />Staff Software Engineer, Tech Lead File:Wikimedia Foundation office camera shy 250px.png|[[User:STran (WMF)|Tran Tran]]<br />Staff Software Engineer, Tech Lead File:Wikimedia Foundation office camera shy 250px.png|[[User:AGueyte (WMF)|Anaïs Gueyte]]<br />Senior Software Engineer File:Lo Claudia Dec 2018.jpg|[[User:CLo (WMF)|Claudia Lo]]<br />Design Researcher File:Saxena, Prateek 2014.jpg|[[User:PSaxena (WMF)|Prateek Saxena]]<br/>UX Designer File:Wikimedia Foundation office camera shy 250px.png|[[m:User:DWalden (WMF)|Dom Walden]]<br />Test Engineer File:ARamirez at The Getty.jpg|[[m:User:ARamirez (WMF)|Aida A. Ramirez]]<br />Lead Technical Program Manager File:Jay Cano Profile.jpg|[[m:User:JCNunez (WMF)|Juan "Jay" Cano]]<br />Engineering Manager File:Wikimedia Foundation office camera shy 250px.png|[[User:TThoabala (WMF)|Tšepo Thoabala]]<br />Senior Software Engineer File:Wikimedia Foundation office camera shy 250px.png|[[User:JWang (WMF)|Jennifer Wang]]<br /> Staff Data Scientist File:Sandister Tei Wikimedian of the year 2020.jpg|[[User:STei (WMF)| Sandister Tei]]<br/> Community Relations Specialist </gallery> == Projects == See [[meta:Community health initiative#Anti-Harassment Tools|Community health initiative#Anti-Harassment Tools]] for information on our projects. Notable projects include: * [[Anti-Harassment_Tools/SecurePoll_Improvements|SecurePoll improvements]] * [[meta:Community health initiative/Blocking tools and improvements|Blocking tools and improvements]] ** [[meta:Community health initiative/Per-user page, namespace, and upload blocking|Partial blocks]] * [[meta:Community health initiative/User reporting system|User reporting system]] * [[meta:Community health initiative/Interaction Timeline|Interaction Timeline]] * [[meta:Community health initiative/User Mute features|User mute features]] * [[meta:IP Editing: Privacy Enhancement and Abuse Mitigation|IP Editing: Privacy Enhancement and Abuse Mitigation]] (in collaboration with the [[Core Platform Team]]) ** [[meta:IP_Editing:_Privacy_Enhancement_and_Abuse_Mitigation/IP_Info_feature|IP Info feature]] * For a timeline of our major releases, see [[Anti-Harassment_Tools/Release Timeline|here]] == Helpful links == * [https://phabricator.wikimedia.org/project/board/2660/ Phabricator workboard] * [[meta:Community health initiative|Community health initiative]] (now defunct) * [[meta:Anti Harassment Program|Anti-Harassment Program]] * [[Anti-Harassment_Tools/New_Extensions|Guide for creating new extensions]] * [[Anti-Harassment Tools/Volunteer interaction guide|Guide for technical contributors on how to work with the team]] * [[Anti-Harassment Tools/Requests|Internal Requests Outside of Annual Planning]] {{Collapse top|Subpages list}} {{List subpages|2=Main}} {{Collapse bottom}} efwh6dz6jn7apbaasal1732xjc3lmgm Wikimedia Product/pl 0 808769 5387588 5358206 2022-07-29T03:25:58Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Edytorzy</span>]] * [[Readers|<span style="color:#2aa198">Czytelnicy</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === Programy === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Nowi Czytelnicy]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === Strony Projektu === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|System raportowania]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''Inne:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] (rzadko używane) * Strona: [[Special:MyLanguage/Contributors|Edytorzy]] * Zespoły: ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Strona: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * Strona: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== Edytowanie ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Strona: [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * Strona: [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== Język ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Strona: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === Czytelnicy === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * Strona: [[Special:MyLanguage/Readers|Czytelnicy]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * Zespoły: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|Sieć]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> Strona: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> Strona: [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] Dyrektor: [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> Strona: [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--''[tekst do intra tutaj]''--> Strona: [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === Wikidane === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * Strona: [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * Lista dyskusyjna: wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q1: styczeń-marzec 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q2: kwiecień-czerwiec] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q3: lipiec-wrzesień] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q4: październik-grudzień] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q1: styczeń-marzec 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q2: kwiecień-czerwiec] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q3: lipiec-wrzesień] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q4: październik-grudzień] |} == Cele == {|class="wikitable" |- !scope="row"| 2019-2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: lipiec-wrzesień 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: październik-grudzień 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: styczeń-marzec 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: kwiecień-czerwiec 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: lipiec-wrzesień 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: październik-grudzień 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: styczeń-marzec 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: kwiecień-czerwiec 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: lipiec-wrzesień 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: październik-grudzień 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: styczeń-marzec 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: kwiecień-czerwiec 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: lipiec-wrzesień 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: październik-grudzień 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: styczeń-marzec 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: kwiecień-czerwiec 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: lipiec-wrzesień 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: październik-grudzień 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: styczeń-marzec 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: kwiecień-czerwiec 2016]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] jia7syunbwco7ej9zoif8v0hd67katk Manual:Installing MediaWiki/cs 100 810251 5387489 5384961 2022-07-28T22:45:16Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">MediaWiki může být náročná na instalaci pro každého, kdo nemá zkušenosti s Apache, PHP a MySQL/MariaDB.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Stažení software MediaWiki == Stáhněte si soubor tar MediaWiki z [[Special:MyLanguage/Download|oficiální stránky pro stažení]]. Obecně platí, že pokud používáte produkční prostředí, chcete používat nejnovější stabilní verzi, kterou je MediaWiki {{MW stable release number}}. == Extrahování software MediaWiki == Stažený soubor je ve formátu <code>.zip</code> nebo <code>.tar.gz</code>. Před použitím musíte tento archivní soubor rozbalit. Soubor můžete dekomprimovat lokálně (a poté nahrát přes FTP na server) nebo přímo na vašem serveru. Dekomprimace se obvykle provádí pomocí softwaru, jako je [https://www.7-zip.org/ 7-Zip] (zdarma), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] nebo [https://www.izarc.org/ IZArc] (zdarma) ve Windows. V systémech Linux a Mac OS X můžete soubor dekomprimovat pomocí tohoto příkazu: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} == Nahrání souborů na váš server == <div class="mw-translate-fuzzy"> Pokud ještě nemáte soubory nahrané na server, udělejte to takto: </div> Nahrajte soubory do úložiště serveru buď: # přímo zkopírováním extrahované složky nebo <div class="mw-translate-fuzzy"> # použitím FTP klienta jako [https://filezilla-project.org/ FileZilla] (Open Source Software, Windows, OSX a Linux) nebo [https://cyberduck.io/ Cyberduck] (také OSS, Windows a OSX). </div> # <span class="mw-translate-fuzzy">pomocí cPanel File Manager ([[Special:MyLanguage/Hosting services|viz níže]])</span> Pokud má váš nahrávací nástroj možnost "změnit názvy souborů na malá písmena", musíte to zakázat. <span class="mw-translate-fuzzy">Pokud máte nainstalován Apache, správný adresář je zadán ve vašem souboru <code>httpd.conf</code> (je to [$docroot DocumentRoot] obvykle $1 nebo {{$2|apache-folder}}).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Poznámka: To se změnilo v Ubuntu 14.04 s Apache 2.4.7, kde primární konfigurační soubor pro nastavení a adresáře serveru Apache je <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Přejmenujte nahranou složku na cokoliv co chcete mít v URL. <span class="mw-translate-fuzzy">Pokud váš webový server pracuje například jako <code>http://localhost</code>, přejmenování na adresář <code>/w/</code> by znamenalo, že byste přistupovali ke své wiki za <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span class="mw-translate-fuzzy">'''''Nepoužívejte <code>/wiki/</code>, pokud jej chcete použít jako [[Special:MyLanguage/Manual:Short URL|krátkou URL adresu]]''''' (Short URL).</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Vytvoření databáze == </div> <div class="mw-translate-fuzzy"> MediaWiki vás požádá o databázi a uživatelské jméno a pokusí se je vytvořit, pokud ještě neexistují. </div> <div class="mw-translate-fuzzy"> Pokud již máte databázový server a znáte pro něj root heslo, instalační skript MediaWiki vám pomůže vytvořit novou databázi. </div> <div class="mw-translate-fuzzy"> Pokud neznáte heslo uživatele root, například pokud jste na hostovaném serveru, budete si muset vytvořit novou databázi. </div> <span class="mw-translate-fuzzy">V současné době musíte použít SQLite, MariaDB, MySQL nebo PostgreSQL k uložení skutečného obsahu vaší wiki.</span> <span class="mw-translate-fuzzy">Pokud si nejste jisti, kterou databázi zvolit, použijte MariaDB. Je nejlépe podporována MediaWiki.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">Na instalační stránce budete muset vybrat název databáze (libovolný) a adresář databáze SQLite.</span> V adresáři databáze se instalační program pokusí použít podadresář mimo kořen dokumentu a v případě potřeby jej vytvořit. Pokud tento adresář není bezpečný (například čitelný na webu), změňte jej ručně. Pro zabránění jeho zpřístupnění všem na webu. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Viz odpovídající dokumentace.</span> <span class="mw-translate-fuzzy">Případně kontaktujte svého hostitele a požádejte ho o vytvoření účtu.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Pokud vaše databáze není spuštěna na stejném serveru jako váš webový server, musíte zadat příslušný název hostitele webového serveru &mdash; mediawiki.example.com v níže uvedeném příkladu &mdash; následujícím způsobem: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=MySQL/MariaDB zaznamenává všechny dotazy do souboru historie. Bude obsahovat heslo k uživatelskému účtu. Pokud se vás to týká, smažte a deaktivujte soubor <code>.mysql_history</code> po spuštění těchto dotazů podle [dokumentace https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL].}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Pokud používáte PostgreSQL, musíte mít buď vytvořenou databázi a uživatele nebo jednoduše do konfiguračního formuláře zadat jméno uživatele PostgreSQL s oprávněními "superuživatele" (superuser).</span> <span class="mw-translate-fuzzy">Tím je často uživatel databáze s názvem '''postgres'''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (zadejte heslo) createdb -O wikiuser my_wiki nebo jako superuser (výchozí postgres) spusťte na příkazovém řádku databáze následující příkazy: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> Dejte pozor na [[phab:tag/postgreSQL|seznam známých problémů při spuštění MediaWiki s PostgreSQL]]. {{anchor|Run the installation script}} == Spusťte instalační skript == <div class="mw-translate-fuzzy"> Po dokončení všech výše uvedených kroků můžete instalaci dokončit pomocí webového prohlížeče tak, že v prohlížeči přejdete na adresu URL index.php - podívejte se na pokyny uvedené v {{ll|Manual:Config script}}. </div> <div class="mw-translate-fuzzy"> == Další kroky == </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Udržujte systém aktuální! == Po instalaci se ujistěte, že budete neustále informováni o vydáních a udržujte svůj server v bezpečí! {{Clickable button 2|<span class="mw-translate-fuzzy">[[$maillist|Přihlašte se k odběru našich oznámení o nových verzích.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Související články == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] qjaiszdt70vawxr1o4afscmrhxmfmgs Wikimedia Product/mni 0 810641 5387585 5358202 2022-07-29T03:25:55Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1='''ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯇꯥꯕꯤꯕ ꯃꯤꯑꯣꯏꯁꯤꯡ''' ꯊꯕꯛꯇꯧꯔꯤꯕ [[foundationsite:role/staff-contractors/|ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯃꯈꯣꯡ(ꯌꯨꯝꯕꯤ) ꯅꯥ ꯊꯕꯛ ꯄꯤꯕ]] ꯁꯟꯈꯠꯄ, ꯐꯒꯠꯍꯟꯕ ꯑꯃꯁꯨꯡ ꯃꯑꯣꯡ ꯃꯇꯧ ꯁꯤ ꯐꯖꯅ ꯆꯠꯊꯕ [[m:Special:MyLanguage/Wikimedia projects|ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯃꯐꯝꯁꯤꯡ]] ꯒꯤ ꯫{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">ꯁꯔꯨꯛꯌꯥꯔꯤꯕꯁꯤꯡ</span>]] * [[Readers|<span style="color:#2aa198">ꯄꯥꯕꯤꯔꯤꯕꯁꯤꯡ</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span class="mw-translate-fuzzy">ꯇꯥꯕꯤꯕ ꯃꯤꯑꯣꯏꯁꯤꯡ ꯂꯥꯟꯁꯤꯟꯗꯨꯅ</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|ꯁꯤꯟ-ꯁꯥꯔꯣꯜ ꯄꯨꯟꯁꯤꯟꯕ ꯂꯝꯕꯤ ꯄꯤꯕꯤꯔꯤꯕ]]) * [[Special:MyLanguage/Design/Statement of purpose|ꯍꯥꯏꯖꯅꯕ ꯏꯒꯗꯕ ꯋꯥꯍꯩ ꯋꯥꯇꯥ ꯃꯑꯣꯡ]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|ꯆꯩꯆꯠ ꯑꯃꯁꯨꯡ ꯄꯣꯠꯊꯣꯛꯁꯤꯡꯒꯤ ꯊꯤꯖꯤꯟꯕ ꯑꯀꯨꯞꯄ ꯋꯥꯔꯣꯜ]] * [[Special:MyLanguage/Wikimedia Research/Showcase|ꯊꯥꯒꯤ ꯊꯤꯖꯤꯟꯕꯁꯤꯡ ꯎꯨꯠꯊꯣꯛꯄ]] === ꯇꯧꯒꯗꯕ ꯊꯧꯔꯝꯁꯤꯡ === * [[m:Special:MyLanguage/Communications/Audience research|ꯇꯥꯕꯤꯕ ꯃꯤꯑꯣꯏ ꯊꯤꯖꯤꯟꯕ]] * [[m:Special:MyLanguage/Community health initiative|ꯃꯤꯌꯥꯝꯒꯤ ꯍꯛꯁꯦꯜꯒꯤ ꯁꯦꯝꯀꯠ ꯍꯧꯒꯠꯂꯛꯄ]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|ꯄꯥꯕꯤꯔꯤꯕ ꯑꯅꯧꯕ ꯃꯤꯑꯣꯏꯁꯤꯡ]] — ꯃꯈꯥ ꯆꯠꯊꯔꯤꯕ ꯊꯤꯖꯤꯟꯕꯁꯤ ꯋꯤꯀꯤꯃꯦꯗꯤꯌꯥ ꯄꯥꯕꯤꯅꯕ ꯂꯩꯕ ꯃꯤꯑꯣꯏꯁꯤꯅ ꯅꯝꯅ ꯂꯩꯕ ꯂꯩꯄꯥꯛꯀꯁꯤꯡ ꯗ ꯈꯪꯗꯣꯛꯄꯗ ꯃꯤꯠꯌꯦꯡ ꯆꯪꯕ ꯏꯟꯇꯔꯅꯦꯠ ꯁꯤꯖꯤꯟꯅꯕ ꯌꯥꯝꯈꯠꯂꯛꯄ ꯑꯣꯏꯅ ꯇꯧꯒꯅꯤ ꯫ (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|ꯀꯃꯣꯟꯁ ꯗ ꯗꯥꯇꯥ ꯒꯤ ꯑꯣꯏꯒꯗꯕ ꯃꯑꯣꯡ]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span class="mw-translate-fuzzy">ꯇꯥꯕꯤꯕ ꯃꯤꯑꯣꯏꯁꯤꯡ ꯀꯥꯡꯕꯨꯁꯤꯡ</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === ꯁꯔꯨꯛꯌꯥꯔꯤꯕꯁꯤꯡ === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span class="mw-translate-fuzzy">ꯐꯦꯕꯔꯤꯀꯦꯇꯔ ꯇꯧꯒꯗ ꯏꯁꯤꯟꯗꯨꯅ ꯊꯦꯠꯄ ꯎꯄꯥꯛꯁꯤꯡ</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span class="mw-translate-fuzzy">ꯂꯃꯥꯏ</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span class="mw-translate-fuzzy">ꯈꯣꯡꯂꯣꯏꯁꯤꯡ</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span class="mw-translate-fuzzy">ꯐꯦꯕꯔꯤꯀꯦꯇꯔ ꯎꯄꯥꯛ</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span class="mw-translate-fuzzy">ꯂꯃꯥꯏ</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === ꯄꯥꯕꯤꯔꯤꯕꯁꯤꯡ === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span class="mw-translate-fuzzy">ꯂꯃꯥꯏ</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span class="mw-translate-fuzzy">ꯐꯦꯕꯔꯤꯀꯦꯇꯔ ꯅꯥ ꯇꯧꯒꯗꯕꯁꯤꯡ ꯏꯁꯤꯟꯗꯨꯅ ꯊꯦꯠꯄ ꯎꯄꯥꯧ</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span class="mw-translate-fuzzy">ꯈꯣꯡꯂꯣꯏꯁꯤꯡ</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == ꯄꯥꯟꯖꯤꯟꯁꯤꯡ == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| ꯲꯰꯱꯸-꯲꯰꯱꯹ | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|ꯋ꯱:ꯖꯨꯂꯥꯏ-ꯁꯦꯞꯇꯦꯝꯕꯔ ꯲꯰꯱꯸]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span class="mw-translate-fuzzy">ꯋ꯴:ꯑꯦꯄ꯭ꯔꯤꯜ-ꯖꯨꯟ ꯲꯰꯱꯶꯹</span>]] |- !scope="row"| ꯲꯰꯱꯷-꯲꯰꯱꯸ | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span class="mw-translate-fuzzy">ꯋ꯱: ꯖꯨꯂꯥꯏ- ꯁꯦꯞꯇꯦꯝꯕꯔ ꯲꯰꯱꯷</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span class="mw-translate-fuzzy">ꯋ꯲:ꯑꯣꯛꯇꯣꯕꯔ-ꯗꯤꯁꯦꯝꯕꯔ ꯲꯰꯱꯷</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span class="mw-translate-fuzzy">ꯋ꯳:ꯖꯥꯅꯨꯋꯥꯔꯤ-ꯃꯥꯔꯆ ꯲꯰꯱꯸</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span class="mw-translate-fuzzy">ꯋ꯴:ꯑꯦꯄ꯭ꯔꯤꯜ- ꯖꯨꯟ ꯲꯰꯱꯸</span>]] |- !scope="row"| ꯲꯰꯱꯶-꯲꯰꯱꯷ | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span class="mw-translate-fuzzy">ꯋ꯱:ꯖꯨꯂꯥꯏ-ꯁꯦꯞꯇꯦꯝꯕꯔ ꯲꯰꯱꯶</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span class="mw-translate-fuzzy">ꯋ꯲:ꯑꯣꯛꯇꯣꯕꯔ-ꯗꯤꯁꯦꯝꯕꯔ ꯲꯰꯱꯶</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span class="mw-translate-fuzzy">ꯋ꯳:ꯖꯥꯅꯨꯋꯥꯔꯤ-ꯃꯥꯔꯆ ꯲꯰꯱꯷</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span class="mw-translate-fuzzy">ꯋ꯴:ꯑꯦꯄ꯭ꯔꯤꯜ-ꯖꯨꯟ ꯲꯰꯱꯷</span>]] |- !scope="row"| ꯲꯰꯱꯵-꯲꯰꯱꯶ | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span class="mw-translate-fuzzy">ꯋ꯱:ꯖꯨꯂꯥꯏ-ꯁꯦꯞꯇꯦꯝꯕꯔ ꯲꯰꯱꯵</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span class="mw-translate-fuzzy">ꯋ꯲:ꯑꯣꯛꯇꯣꯕꯔ-ꯗꯤꯁꯦꯝꯕꯔ ꯲꯰꯱꯵</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span class="mw-translate-fuzzy">ꯋ꯳:ꯖꯥꯅꯨꯋꯥꯔꯤ-ꯃꯥꯔꯆ ꯲꯰꯱꯶</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span class="mw-translate-fuzzy">ꯋ꯴:ꯑꯦꯄ꯭ꯔꯤꯜ-ꯖꯨꯟ ꯲꯰꯱꯶</span>]] |} == ꯆꯥꯍꯤꯒꯤ ꯂꯃꯕꯤ ꯇꯥꯛꯄ == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span class="mw-translate-fuzzy">꯲꯰꯱꯷-꯲꯰꯱꯸ ꯆꯥꯍꯤꯒꯤ ꯄꯣꯠꯊꯣꯛꯀꯤ ꯀꯣꯛꯆꯨꯪꯁꯤꯟꯅꯕ</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span class="mw-translate-fuzzy">꯲꯰꯱꯶-꯲꯰꯱꯷ ꯆꯥꯍꯤꯒꯤ ꯄꯣꯠꯊꯣꯛꯀꯤ ꯀꯣꯛꯆꯨꯪꯁꯤꯟꯅꯕ</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|꯲꯰꯱꯶ ꯄꯣꯠꯊꯣꯛꯀꯤ ꯁꯝꯂꯛꯄ]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|꯲꯰꯱꯵ ꯄꯣꯠꯊꯣꯛ ꯑꯃꯁꯨꯡ ꯁꯤꯟ-ꯁꯥꯔꯣꯜ ꯅꯩꯅꯕ ꯑꯃꯨꯛꯍꯟꯅ ꯌꯦꯡꯁꯤꯟꯕ]] [[Category:WMF Projects{{#translation:}}]] bkcn2rzg66pxaraqbbegvmf90iiva0d HHVM/ja 0 815259 5387453 5240445 2022-07-28T22:32:08Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = <span lang="en" dir="ltr" class="mw-content-ltr">Support in MediaWiki for HHVM (HipHop Virtual Machine) and deployment to the Wikimedia cluster</span> | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/HHVM/About|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref> After discussion<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See {{phabricator|T176209}} and {{phabricator|T192166}}.</span>}} '''[[:ja:HHVM|HHVM]]'''はPHPインタープリターツール(より厳密にはランタイムにPHP bytecodeをネーティブの指示に変換する仮想マシンのこと)で、2014年にウィキメディアのサーバに実装されると右記の操作でページ読み込みに要する時間が短縮されました。ログイン利用者のページ閲読、またログイン状態を問わずページの編集を保存するとき。 == ロードマップ == <span lang="en" dir="ltr" class="mw-content-ltr">HHVM is a new way for websites to run [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (written in [[w:PHP|PHP]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT).</span> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.</span> このページではウィキメディアが推進するMediaWikiのHipHopサポート業務ならびにウィキメディア製作のウィキ群への実装が主題です。 HipHopコンパイラの成り立ちとしてはFacebookのプロジェクトであり、コンピュータ言語の加速を目的としたPHPコードからC++への変換作業が含まれました。その後、Facebookが同プロジェクトを中止、現在はHHVM自体の開発へと努力を移しています。 製作クラスタで2014年にHHVMを実装する全体案は次のとおりです。 * βクラスタへの実装(他の準備と並行して作業){{done}} * 2014年7月21日の週:製作クラスタのジョブランナー数件に実装{{done}} * test.wikipedia.org アプリケーションサーバに実装{{done}} * Varnishモジュールの実装を介してアプリケーションサーバ群に部分的に実装を可能にする{{Done}} * 限定的にごく少数のアプリケーションサーバに実装{{Done}} * 段階的にアプリケーションサーバ群への実装を進めてHHVMの使用を大多数のサーバに広げる{{done}} * その他のサービスに実装{{done}} === HHVMの作業 === Phabricator: [[phabricator:project/board/79/|未完のタスク]]と[[phabricator:project/board/79/query/all/|全タスク]]。 == 設計思想 == <span lang="en" dir="ltr" class="mw-content-ltr">It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> in a solution: [http://hhvm.com HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're quite confident that this will result in big performance improvements on our sites as well.</span> == HipHop がエンドユーザに与える影響は? == <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is written in PHP, a language that is [[w:Interpreter (computing)|interpreted]] at run-time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These caches only serve users that are not logged in.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. </div> == MediaWikiがHipHop開発に関与して開発者に与える影響とは? == <span lang="en" dir="ltr" class="mw-content-ltr">In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will be on a totally opt-in basis which can be disabled at any time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.</span> == 関連項目 == * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: HHVM{{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}}にHHVMを設定する * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presenting at @Scale about migrating to HHVM] - @ScaleでHHVMへの移行について説明するOri * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM in production: what that means for Wikimedia developers] - HHVMと開発:ウィキメディア開発者に及ぼす影響 == 参考資料、脚注 == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] e5zj3p3atbkwzp94ua48ju8z3jc86r6 Wikimedia Product/hu 0 815599 5387578 5358197 2022-07-29T03:25:48Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span></span>]] * [[Readers|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Readers</span></span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Célok == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2017–2018</span> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2016–2017</span> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] k8upogg3jqaxkiruycl9jnw9c5wp2i1 Translations:HHVM/28/en 1198 816783 5387446 2883440 2022-07-28T22:32:02Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki See [[$1|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[$blog How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work. jhoc56q312ye6vkbl2ykh0byp2djhgl Manual:Installation guide/tt 100 816990 5386673 5381111 2022-07-28T17:14:38Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/tt]] jj48k8g0vozhzgcs6tnpdt4ig7qpmxv 5386688 5386673 2022-07-28T17:24:50Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/tt]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Manual:Installing third-party tools/zh 100 818240 5387827 5377086 2022-07-29T09:29:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/zh]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/zh]] qrimzzgio3038yaymj8xbmi9ea03i0e Wikimedia Product/da 0 823177 5387568 5358188 2022-07-29T03:25:37Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Bidragydere</span>]] * [[Readers|<span style="color:#2aa198">Læsere</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === Programmer === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Nye læsere]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span class="mw-translate-fuzzy">Side</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span class="mw-translate-fuzzy">Side</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span class="mw-translate-fuzzy">Side</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span class="mw-translate-fuzzy">Side</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Mål == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] l3i41erssgh5ybmytbm9pk7m4xx68xe Translations:Manual:Installation guide/11/ko 1198 826051 5387290 5265822 2022-07-28T21:57:23Z Baris6161TURK 17188421 wikitext text/x-wiki 이미지 섬네일은 추가 프로그램들이 필요합니다. $1(시각편집기에 필요함) 및 기타 서비스들은 각자 요구사항이 있습니다. fut08a6rrtem52tlrh4cxcezgt2rfll Wikimedia Product/sr 0 827979 5387593 5358210 2022-07-29T03:26:02Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span></span>]] * [[Readers|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Readers</span></span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Goals</span> == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2017–2018</span> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2016–2017</span> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] mpuicmlbqjr9ns0die2qhrofjb1pj2f Wikimedia Product/sv 0 830710 5387594 5358213 2022-07-29T03:26:03Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1='''Wikimedia-produkt''' personal [[foundationsite:role/staff-contractors/|anställda av Wikimedia Foundation]] bygger, förbättrar och underhåller funktionerna [[m:Special:MyLanguage/Wikimedia projects|Wikimedias hemsidor]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Bidragsgivare</span>]] * [[Readers|<span style="color:#2aa198">Läsare</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Över produkt == * [[Special:MyLanguage/Product Principles|Produktprinciper]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (tidigare: [[Special:MyLanguage/Technical Collaboration Guidance|Teknisk samarbetsvägledning]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === Program === * [[m:Special:MyLanguage/Communications/Audience research|Läsarundersökning]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Nya läsare]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|Strukturerad data på Commons]] === Projektsidor === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|Avancerade mobilbidrag]] * [[Special:MyLanguage/Android editing features|Androidredigeringsfunktioner]] * [[Special:MyLanguage/Content translation/V2|Innehållsöversättning, V2]] * [[Special:MyLanguage/Growth/Growth team updates|Tillväxt]] * [[Special:MyLanguage/Language tools|Förbättra tillägget Translate och översättningsprocessen på wikierna]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|iOS-redigering]] * [[Special:MyLanguage/VisualEditor on mobile|Visuellt baserad mobilredigering]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|Bättre användning av data]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|Datainsamling: Instrumentation]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|Önskelista]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|Stöd för mindre användargrupper]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|Teknikverktyg för program- och evenemangsorganisatörer]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|Rapporteringssystem]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''Övrigt:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|Parser-förening]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|MallStilar]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) == Statistik == <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === Bidragsgivare === Vi bygger samarbetande, inkluderande verktyg för att skapa och redigera fri kunskap. * Phabricator-uppgiftstavlor: [[phab:tag/contributors-team/|#Contributors-Team]] (används sällan) * Sida: [[Special:MyLanguage/Contributors|Bidragsgivare]] * Team: ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * Phabricator-uppgiftstavla: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Sida: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== Gemenskapsteknik ====== * [[phab:project/board/1274/|<span class="mw-translate-fuzzy">Phabricator-uppgiftstavla:</span>]] * Sida: [[m:Special:MyLanguage/Community Tech|Gemenskapsteknik]] ====== Redigering ====== * Phabricator-uppgiftstavlor: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Sida: [[Special:MyLanguage/Editing team|Redigeringsteam]] ====== Tillväxt ====== * Phabricator-uppgiftstavla: [[phab:project/board/1114/|#Growth-Team]] * Sida: [[Special:MyLanguage/Growth|Tillväxt]] ====== Språk ====== * Phabricator-uppgiftstavla: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Sida: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === Läsare === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * Sida: [[Special:MyLanguage/Readers|Läsare]] * Phabricator-uppgiftstavla: [https://phabricator.wikimedia.org/tag/reading/ #reading] * Team: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|Parsing]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> Sida: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|Teknisk programhantering]] Ledare: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === Produktdesign === Vi gör det lätt och kul för alla att bidra till all mänskligt vetande. Sida: [[Special:MyLanguage/Design#Product Design|Produktdesign]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === Produktanalys === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> Sida: [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] Ledare: Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--''[introtext här]''--> Sida: [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] Ledare: Margeigh Novotny === Wikidata === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * Sida: [[d:Wikidata:Main Page|Wikidata]] * Ledare: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * Diskussionslista: wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q1: januari-mars 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q2: april-juni] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q3: juli-september] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q4: oktober-december] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q1: januari-mars 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q2: april-juni] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q3: juli-september] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q4: oktober-december] |} == Mål == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: juli-september 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: oktober-december 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: januari-mars 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: april-juni 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: juli-september 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: oktober-december 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: januari-mars 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: april-juni 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: juli-september 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: oktober-december 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: januari-mars 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: april-juni 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: juli-september 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: oktober-december 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: januari-mars 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: april-juni 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: juli-september 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: oktober-december 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: januari-mars 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: april-juni 2016]] |} == Årlig vägkarta == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|Årlig plan för Product 2018-2019]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|Årlig plan för produkt 2017-2018]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|Årlig plan för produkt 2016-2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|Produktssammanfattning 2016]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|2015 produkts- & teknologisk återblick]] [[Category:WMF Projects{{#translation:}}]] 34r26fnmz625a54ryeuk8cg3mm7tm2h Translations:Manual:Installation guide/11/th 1198 836335 5387291 4700880 2022-07-28T21:57:34Z Baris6161TURK 17188421 wikitext text/x-wiki ภาพขนาดย่อ และ $texvc ต้องการโปรแกรมเพิ่มเติม $1 (ต้องการใช้โดย VisualEditor) และบริการอื่น ๆ มีความต้องการของตนเอง cmxccxe8yqk8bjy77mj5n33l7sah0nm Manual:Combating spam/da 100 843763 5387469 5255690 2022-07-28T22:40:13Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Som alle andre dynamiske hjemmesider er wikier ofte mål for spammere, der ønsker at promovere produkter eller hjemmesider. MediaWiki tilbyder en række funktioner til at [[Special:MyLanguage/Manual:Combating vandalism|bekæmpe vandalisme generelt]]. På denne side behandler vi specielt [[m:Wiki spam|wiki spam]]. == Oversigt == Almindelige værktøjer der bruges til at bekæmpe spam på wikier falder typisk inden for følgende kategorier: * Kræver indlogning og/eller CAPTCHA til visse handlinger såsom redigering, tilføjning af eksterne links eller oprettelse af nye brugere * Blokerer redigering fra kendte sortlistede IP adresser eller IP'er, der kører åbne proxier * Blokerer redigeringer som tilføjer visse uønskede kodeord eller eksterne links * Blokerer specifikke brugernavne og sidenavne ofte benyttet af spam-robotter * Blokerer redigeringer af nye eller anonyme brugere på ofte ramte sider * Godkendelse af visse skribenter såsom admin og jævnlige radaktører, men restriktioner på nye eller anonyme brugere * Udrensnings-scripts eller masse-sletning ({{ll|Extension:Nuke}}) af eksisterende posteringer fra nyligt bandlyste spam-robotter <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> Bemærk at mange af disse funktioner er ikke aktiveret som standard. <span lang="en" dir="ltr" class="mw-content-ltr">If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</span> <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It helps to raise the bar a little.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> == Afprøv først hurtig-løsninger == Det burde ikke være så svært at bekæmpe spam. <span lang="en" dir="ltr" class="mw-content-ltr">If you want to quickly and drastically reduce spam, try these few steps first.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install the [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] extension to block known spammer IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> == Grundlæggende opsætning af antispam == {{anchor|CAPTCHA}} ===CAPTCHA=== <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> * alle redigeringer <div lang="en" dir="ltr" class="mw-content-ltr"> * edits adding new, unrecognized external links </div> * registrering af brugere <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. == Antispam rutine: skræddersyet overvågning == <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} ===Beskyttelse af enkelte sider=== <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === Misbrugsfilter === <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> === Spam blokering === <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> === Åbne proxier === <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> == Hardcore kontrol == <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> === Ændringer i Apache konfigurationen === <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> ==== Forhindre ressourceforbrug af blokerede spammere ==== <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> ===Blokering af ip-adresser=== <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> ==== CPU brug og overbelastning ==== <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> ==== Men hvad så med honningkrukker? ==== <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> ==== Flere lister over proxier og spambot IP-adresser ==== <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> == Hvis spam har overtaget == Du kan stadig vinde kampen! MediaWiki tilbyder dig værktøjerne; du skal bare forberede mulighederne og svare igen når du er klar. <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> == Andre ideer == <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> ==Se også== *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === Udvidelser (extensions) === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} ==== Kommer med installationen ==== <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === Indstillinger === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External links === </div> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] h8ydpyua581545qrux90rgefmmdu2x3 Extension:Highlight Links in Category/ja 102 844681 5387151 5345728 2022-07-28T21:07:57Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} '''Highlight Links in Category'''は、あるカテゴリのメンバーを指すリンクにCSSクラスを追加する拡張機能です。 問題やバグを報告するには、[https://phabricator.miraheze.org Miraheze Phabricator]を使用してください。 ==インストール== {{ExtensionInstall|HighlightLinksInCategory|registration=required}} ==構成パラメーター== ; $wgHighlightLinksInCategory : このグローバルは、どのカテゴリに CSS クラスが追加されるかを設定する配列です。キーはカテゴリ名で、空白ではなく「_」 (アンダースコア) を含む必要があります。「Category:」(カテゴリ:) は含めないでください。各キーの値は、そのカテゴリに追加したい CSS クラスです。たとえば、以下のようになります。 {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} 複数のクラスを追加する場合は、以下のようにクラス名をスペースで区切ってください。 {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} 好きなだけ追加できますが、UXの観点からすると、500種類のスタイルリンクを追加するのはすごいことではないのかもしれません。 $wgHighlightLinksInCategory が設定されていないか、空である場合、この拡張機能は何もしません。 Wikiファームを運営していて、いくつかのWikiでこれをオフにする必要がある場合、<syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight>を設定してください; {{phpi|false}} を使用すると、正しくない動作につながる可能性があります。 == スタイル == これらのリンクに必要なスタイルを、あなたのwikiのMediaWiki:Common.cssに追加するだけです。たとえば {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} あるカテゴリを他のカテゴリより優先させたい場合は、CSS で指定する必要があります。 {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} あるいは、代わりに元の<code>a.templates</code>ルールを <code>a.templates:not(.disambig)</code>として定義することもできたでしょう。 リンクアイコンのアプローチもあります。 {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} == 利用者の切り替え == このハイライトのオン・オフを簡単に設定する方法は、CSSを入れた[[Extension:Gadgets|Gadget]]を作成することです。 そう、これはパーソナライズ部分を他のエクステンションにアウトソースするパーソナライズ拡張機能です。夜も眠れるようになりました。 ==動作の仕組み== MediaWikiがどのリンクされたページが存在するか決定した直後に(レッドリンクを作成するために)、<code>GetLinkColours</code>フックを実行します(LinkHolderArray.phpを参照)。 そのページにリンクされているすべてのページIDのリストがあるので、データベースのクエリを実行すれば、これらのリンクのうち、強調したいカテゴリのセットに含まれるものを確認することができます。 このクエリは<code>categorylinks</code>テーブルのインデックスに対してのみ発生するので、それなりに高速です。 そして、<code>$wgHighlightLinksInCategory</code>でユーザが設定した構成値を使って、結果に基づいてCSSクラスが割り当てられます。 CSSの仕組みの説明は、ドキュメントの範囲外です。 ==既知の問題点== * CSS スタイルはFlowに追加されません。なぜなら、そこでは GetLinkColorsフックを呼び出していないようです。 ==関連項目== * [[:Category:LinkEnd extensions]] - その他の方法でリンクをカスタマイズする {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] g4fiin6b4vnm6q1qcv48zj5y7sv9g9x HHVM/de 0 862221 5387448 5240442 2022-07-28T22:32:05Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = MediaWiki-Unterstützung für HHVM (HipHop Virtual Machine) und Verteilung auf dem Wikimedia-Cluster. | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/HHVM/About|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref> After discussion<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See {{phabricator|T176209}} and {{phabricator|T192166}}.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">'''[[w:HHVM|HHVM]]''' is a PHP interpreter tool (concretely a virtual machine that compiles PHP bytecode to native instructions at runtime) that was deployed on Wikimedia servers in 2014, decreasing the loading time for: any page you view while logged in, and for saving pages that you've edited whether you are logged in or not.</span> == Entwicklungsplan == <span lang="en" dir="ltr" class="mw-content-ltr">HHVM is a new way for websites to run [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (written in [[w:PHP|PHP]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT).</span> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This page is about Wikimedia-sponsored work on HipHop support in MediaWiki, and its deployment to Wikimedia production wikis. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Historically, the HipHop compiler was a project by Facebook which involved compiling PHP code into C++ for purposes of speeding up the language. Facebook has since abandoned this project, and now their development efforts are focused on HHVM itself instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is the general plan for deploying HHVM to the production cluster in 2014: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Deployment to Beta Cluster (currently ongoing work, in parallel with other work) {{done}} * Week of July 21: deployment to a few job runners in production {{done}} * Deploy to test.wikipedia.org application server {{done}} * Deploy Varnish module allowing partial deployment to a fraction of application servers{{Done}} * Limited deployment to small number of application servers {{Done}} * Ramp up deployment to more application servers until most servers use HHVM{{done}} * Deploy to remainder of services{{done}} </div> === HHVM-Arbeit === <div lang="en" dir="ltr" class="mw-content-ltr"> Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. </div> == Gründe == <span lang="en" dir="ltr" class="mw-content-ltr">It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> in a solution: [http://hhvm.com HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're quite confident that this will result in big performance improvements on our sites as well.</span> == Was macht HipHop für unsere Endnutzer? == <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is written in PHP, a language that is [[w:Interpreter (computing)|interpreted]] at run-time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These caches only serve users that are not logged in.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does our development work on HipHop affect MediaWiki developers? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will be on a totally opt-in basis which can be disabled at any time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.</span> == Siehe auch == * {{ll|HHVM/About|HHVM/Über}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: HHVM installieren in {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori präsentiert bei @Scale über HHVM-Migration] (Englisch) * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM in Produktion: Was das für Wikimedia-Entwickler bedeutet] (Englisch) == Belege und Fußnoten == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] 72knc4hv241i38kbow0045cydg6cwbe Groups/fr 0 863497 5387357 4924005 2022-07-28T22:11:28Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] Les '''groupes MediaWiki''' organisent les activités de la communauté de source libre sur des sujets et des zones géographiques spécifiques. Il existe des [[meta:Special:MyLanguage/Wikimedia user groups|Groupes d'utilisateurs Wikimedia]] qui permettent un niveau de coordination dans le contexte MediaWiki. En tant que tels, ils élargissent la capacité de la [[wmf:|Fondation Wikimedia]] pour les [[Events|événements]], la [[Volunteer coordination and outreach/Training materials|formation]], la promotion et les autres activités techniques au bénéfice de Wikipedia, du mouvement Wikimedia et du logiciel MediaWiki. <span class="mw-translate-fuzzy">Les groupes MediaWiki sont ouverts aux membres de [[Special:MyLanguage/How to contribute|différentes spécialtés]] et de niveau d'expertise.</span> Plus c'est riche et diversifié, meilleur c'est. Les utilisateurs non techniques voulant contribuer et apprendre sont les bienvenus aussi ! Tous les groupes suivent les [[wmf:Friendly space policy|règles de l'espaces amical]]. Les groupes MediaWiki peuvent [[Groups/Wikimedia support|demander du support]] auprès de la Fondation Wikimedia et des chapitres sous différentes formes. == Groupes thématiques == Les groupes thématiques de MediaWiki collaborent avec leurs contre parties logiques dans les communautés [[w:FLOSS|FLOSS]] plus étendues. Ce sont des groupes globaux, qui collaborent en ligne. * Ils sont en rappport avec les communautés pour le même but. * Ils participent aux événements sur le même sujet. * Ils font la promotion des formations associées et des activités connexes. * L'aide pour améliorer la documentation associée sur wikimedia.org. * Ils collaborent au sein des équipes de développement associées. * Eventuellement, certains d'entre-eux se retrouvent au [//wikimania.wikimedia.org/ Wikimania]. == Groupes locaux == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Les groupes locaux MediaWiki collaborent avec les [[meta:Special:MyLanguage/Wikimedia chapters|chapitres Wikimedia]]. Voir aussi les [[w:Wikipedia:Meetup|réunions Wikipedia]] et les autres communautés associées à Wikimedia, au logiciel libre, à la culture libre... Leurs objectifs sont les activités en présentiel : * Organisation d'événements locaux : réunions, formations, hackatons... Ces événements adhèrent aux [[wmf:Friendly_space_policy|règles WMF des espaces amicaux]]. * Participation aux événements qui se déroulent dans leur région. * Distribution de produits commerciaux. * Promotion de contributeurs locaux aux activités globales MediaWiki and Wikimedia. <div class="mw-translate-fuzzy"> Egalement pour les groupes qui ne parlent pas anglais : * Internationalisation de la documentation et du logiciel d'après les procédures [[Special:MyLanguage/translatewiki.net|translatewiki.net]] . </div> Les groupes locaux doivent réellement être locaux. Les points de départ comme par exemple Recife, Munich ou Saint Petersbourg sont meilleurs que Brésil, Allemagne ou Russie. <span class="mw-translate-fuzzy">Si vous avez raté une réunion sur du canal de coordination régionale vous pouvez utiliser la [[Mailing lists/Regional|liste de diffusion régionale]].</span> == Créer un groupe == Vous n'avez pas besoin que quelqu'un propose un groupe, juste vous-même. Pour qu'il soit approuvé, vous devez avoir au moins trois contributeurs. Veuillez lire les [[Groups/Proposals|propositions]] pour plus de détails sur la façon de créer un groupe MediaWiki. [[Category:MediaWiki Communication{{#translation:}}]] sjor6ox4mmztdcazdahpyp1hc6tav0j 5387376 5387357 2022-07-28T22:12:37Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] Les '''groupes MediaWiki''' organisent les activités de la communauté de source libre sur des sujets et des zones géographiques spécifiques. Il existe des [[meta:Special:MyLanguage/Wikimedia user groups|Groupes d'utilisateurs Wikimedia]] qui permettent un niveau de coordination dans le contexte MediaWiki. En tant que tels, ils élargissent la capacité de la [[wmf:|Fondation Wikimedia]] pour les [[Events|événements]], la [[Volunteer coordination and outreach/Training materials|formation]], la promotion et les autres activités techniques au bénéfice de Wikipedia, du mouvement Wikimedia et du logiciel MediaWiki. Les groupes MediaWiki sont ouverts aux membres de [[Special:MyLanguage/How to contribute|différentes spécialtés]] et de niveau d'expertise. Plus c'est riche et diversifié, meilleur c'est. Les utilisateurs non techniques voulant contribuer et apprendre sont les bienvenus aussi ! Tous les groupes suivent les [[wmf:Friendly space policy|règles de l'espaces amical]]. Les groupes MediaWiki peuvent [[Groups/Wikimedia support|demander du support]] auprès de la Fondation Wikimedia et des chapitres sous différentes formes. == Groupes thématiques == Les groupes thématiques de MediaWiki collaborent avec leurs contre parties logiques dans les communautés [[w:FLOSS|FLOSS]] plus étendues. Ce sont des groupes globaux, qui collaborent en ligne. * Ils sont en rappport avec les communautés pour le même but. * Ils participent aux événements sur le même sujet. * Ils font la promotion des formations associées et des activités connexes. * L'aide pour améliorer la documentation associée sur wikimedia.org. * Ils collaborent au sein des équipes de développement associées. * Eventuellement, certains d'entre-eux se retrouvent au [//wikimania.wikimedia.org/ Wikimania]. == Groupes locaux == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Les groupes locaux MediaWiki collaborent avec les [[meta:Special:MyLanguage/Wikimedia chapters|chapitres Wikimedia]]. Voir aussi les [[w:Wikipedia:Meetup|réunions Wikipedia]] et les autres communautés associées à Wikimedia, au logiciel libre, à la culture libre... Leurs objectifs sont les activités en présentiel : * Organisation d'événements locaux : réunions, formations, hackatons... Ces événements adhèrent aux [[wmf:Friendly_space_policy|règles WMF des espaces amicaux]]. * Participation aux événements qui se déroulent dans leur région. * Distribution de produits commerciaux. * Promotion de contributeurs locaux aux activités globales MediaWiki and Wikimedia. <div class="mw-translate-fuzzy"> Egalement pour les groupes qui ne parlent pas anglais : * Internationalisation de la documentation et du logiciel d'après les procédures [[Special:MyLanguage/translatewiki.net|translatewiki.net]] . </div> Les groupes locaux doivent réellement être locaux. Les points de départ comme par exemple Recife, Munich ou Saint Petersbourg sont meilleurs que Brésil, Allemagne ou Russie. <span class="mw-translate-fuzzy">Si vous avez raté une réunion sur du canal de coordination régionale vous pouvez utiliser la [[Mailing lists/Regional|liste de diffusion régionale]].</span> == Créer un groupe == Vous n'avez pas besoin que quelqu'un propose un groupe, juste vous-même. Pour qu'il soit approuvé, vous devez avoir au moins trois contributeurs. Veuillez lire les [[Groups/Proposals|propositions]] pour plus de détails sur la façon de créer un groupe MediaWiki. [[Category:MediaWiki Communication{{#translation:}}]] m5zz4wlzf20lr6j1n74dxt6oyo9lzv1 5387402 5387376 2022-07-28T22:15:00Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] Les '''groupes MediaWiki''' organisent les activités de la communauté de source libre sur des sujets et des zones géographiques spécifiques. Il existe des [[meta:Special:MyLanguage/Wikimedia user groups|Groupes d'utilisateurs Wikimedia]] qui permettent un niveau de coordination dans le contexte MediaWiki. En tant que tels, ils élargissent la capacité de la [[wmf:|Fondation Wikimedia]] pour les [[Events|événements]], la [[Volunteer coordination and outreach/Training materials|formation]], la promotion et les autres activités techniques au bénéfice de Wikipedia, du mouvement Wikimedia et du logiciel MediaWiki. Les groupes MediaWiki sont ouverts aux membres de [[Special:MyLanguage/How to contribute|différentes spécialtés]] et de niveau d'expertise. Plus c'est riche et diversifié, meilleur c'est. Les utilisateurs non techniques voulant contribuer et apprendre sont les bienvenus aussi ! Tous les groupes suivent les [[wmf:Friendly space policy|règles de l'espaces amical]]. Les groupes MediaWiki peuvent [[Groups/Wikimedia support|demander du support]] auprès de la Fondation Wikimedia et des chapitres sous différentes formes. == Groupes thématiques == Les groupes thématiques de MediaWiki collaborent avec leurs contre parties logiques dans les communautés [[w:FLOSS|FLOSS]] plus étendues. Ce sont des groupes globaux, qui collaborent en ligne. * Ils sont en rappport avec les communautés pour le même but. * Ils participent aux événements sur le même sujet. * Ils font la promotion des formations associées et des activités connexes. * L'aide pour améliorer la documentation associée sur wikimedia.org. * Ils collaborent au sein des équipes de développement associées. * Eventuellement, certains d'entre-eux se retrouvent au [//wikimania.wikimedia.org/ Wikimania]. == Groupes locaux == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Les groupes locaux MediaWiki collaborent avec les [[meta:Special:MyLanguage/Wikimedia chapters|chapitres Wikimedia]]. Voir aussi les [[w:Wikipedia:Meetup|réunions Wikipedia]] et les autres communautés associées à Wikimedia, au logiciel libre, à la culture libre... Leurs objectifs sont les activités en présentiel : * Organisation d'événements locaux : réunions, formations, hackatons... Ces événements adhèrent aux [[wmf:Friendly_space_policy|règles WMF des espaces amicaux]]. * Participation aux événements qui se déroulent dans leur région. * Distribution de produits commerciaux. * Promotion de contributeurs locaux aux activités globales MediaWiki and Wikimedia. Egalement pour les groupes qui ne parlent pas anglais : * Internationalisation de la documentation et du logiciel d'après les procédures [[Special:MyLanguage/translatewiki.net|translatewiki.net]] . Les groupes locaux doivent réellement être locaux. Les points de départ comme par exemple Recife, Munich ou Saint Petersbourg sont meilleurs que Brésil, Allemagne ou Russie. <span class="mw-translate-fuzzy">Si vous avez raté une réunion sur du canal de coordination régionale vous pouvez utiliser la [[Mailing lists/Regional|liste de diffusion régionale]].</span> == Créer un groupe == Vous n'avez pas besoin que quelqu'un propose un groupe, juste vous-même. Pour qu'il soit approuvé, vous devez avoir au moins trois contributeurs. Veuillez lire les [[Groups/Proposals|propositions]] pour plus de détails sur la façon de créer un groupe MediaWiki. [[Category:MediaWiki Communication{{#translation:}}]] dg4cp2d3b3r75o7xngfec85r69yddkp Extension:Scribunto/de 102 864007 5386928 5307392 2022-07-28T19:45:24Z ThisCarthing 17456337 Created page with "== Andere Seiten ==" wikitext text/x-wiki <languages/> {{Bundled|1.34}} {{Note|text=Diese Erweiterung läuft über eine ausführbare Datei. Sie müssen die Berechtigung haben, ausführbare Dateien auf Ihrem Host auszuführen, damit diese Erweiterung funktioniert.}} {{Extension |status = stable |type1 = parser |type2 = |newhook1 = ScribuntoExternalLibraries |newhook2 = ScribuntoExternalLibraryPaths |username = |author = <nowiki/> * Victor Vasiliev * Tim Starling : {{int|and}}{{int|word-separator}}{{int|version-poweredby-others}} |description = Versorgt ein Framework zum Einbetten von Skriptsprachen in MediaWiki-Seiten |image = |imagesize = |version = Kontinuierliche Aktualisierungen |update = |mediawiki = |php = 5.5+ |download = {{WikimediaDownload}} |readme = |changelog = |tags = |namespace = Module (ns:828), Talk_Module (ns:829) |example = |compatibility policy = rel |phabricator = MediaWiki-extensions-Scribunto }} Die Erweiterung '''Scribunto''' ([[w:Latin|Latein]]: „''[[wikt:scribunto|sie sollen schreiben/schreiben lassen (in der Zukunft)]]''“) ermöglicht das Einbetten von Skriptsprachen in MediaWiki. Aktuell wird nur die Skriptsprache [[w:Wikipedia:Lua|Lua]] unterstützt. Scribunto-Lua-Skripte werden in dem Namensraum '''Module''' abgelegt. == Lizenz == Die Erweiterung enthält Kodes die unter GNU General Public License v2.0 oder neuer (GPL-2.0+) lizenziert sind, sowie Kodes die unter MIT License (MIT) lizenziert sind. == Voraussetzungen == === PCRE-Version Kompatibilität === PCRE 8.33+ ist empfohlen. Die durch PHP verwendete Version von [[w:PCRE|PCRE]] ist anzusehen, indem eine phpinfo()-Webseite aufgerufen wird, oder über die Befehlszeile mit dem folgenden Befehl: <syntaxhighlight lang="bash"> php -r 'echo "pcre: " . ( extension_loaded( "pcre" ) ? PCRE_VERSION : "no" ) . "\n";' </syntaxhighlight> * Scribunto wird nicht funktionieren mit Versionen von PCRE die unter Version 8.10 sind. * PCRE 8.31 hat Fehler mit JIT-Muster-Untersuchung, das [[phab:T73922|verschiedene Muster unterbricht, wenn sie mit HHVM genutzt werden]]. * PCRE 8.32 hat [https://bugs.exim.org/show_bug.cgi?id=1340 einen Fehler], der dazu führt, dass es bestimmte [[w:Mapping of Unicode characters#Non-characters|Codepoints ohne Zeichen]] ablehnt, was zu Fehlern im mw.html-Modul führt. CentOS 6 und RHEL 6 arbeiten mit PCRE 7 und müssen aufgerüstet werden. Die Aktualisierung auf 8.33, auf einem Server mit einer älteren Version, kann relativ kompliziert sein. Siehe (auf Englisch) [[Updating to PCRE 8.33 or Higher]] für Details. === PHP pcntl ([[LTS|LTS]]) === {{MW version|version=1.25|version2=1.28}} Die Scribunto-Versionen für MediaWiki 1.25 bis 1.28 benötigten die PHP-Erweiterung [https://php.net/pcntl.installation pcntl], die nur auf Unix/Linux-Plattformen verfügbar ist, wenn Sie "LuaStandalone" verwenden wollen (d. h. in einem separaten Kindprozess laufen lassen). Diese Voraussetzung wurde in Scribunto für MediaWiki-Version 1.29 entfernt. Sie können überprüfen, ob die pcntl-Unterstützung aktiviert ist, indem Sie sich die phpinfo()-Webseite ansehen oder von der Befehlszeile aus den folgenden Befehl eingeben: <syntaxhighlight lang="bash"> php -r 'echo "pcntl: " . ( extension_loaded( "pcntl" ) ? "yes" : "no" ) . "\n";' </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> === PHP mbstring extension === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> PHP needs to have the [https://php.net/mbstring mbstring] extension enabled. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can check whether mbstring support is enabled by viewing a phpinfo() web page, or from the command line with the following command: </div> <syntaxhighlight lang="bash"> php -r 'echo "mbstring: " . ( extension_loaded( "mbstring" ) ? "yes" : "no" ) . "\n";' </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> === Lua binary === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled binaries ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Scribunto comes bundled with Lua binary distributions for Linux (x86 and x86-64), Mac OS X Lion, and Windows (32- and 64-bit). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Scribunto should work for you out of the box if: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Your web server is run on one of the above platforms.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">PHP's <code>proc_open</code> function is not restricted.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">i.e. Scribunto will not work if <code>proc_open</code> is listed in the <code>disable_functions</code> array in your server's "php.ini" file.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If it is, you may see an error message like <code>proc_open(): open_basedir restriction in effect. File(/dev/null) is not within the allowed path(s):</code></span>. <span lang="en" dir="ltr" class="mw-content-ltr">If you are using Plesk and have been granted sufficient permissions, you may be able to set <code>open_basedir</code> in the PHP settings for your domain or subdomain.</span> Versuche, <code>{WEBSPACEROOT}{/}{:}{TMP}{/}</code> zu <code>{WEBSPACEROOT}{/}{:}{TMP}{/}{:}/dev/null{:}/bin/bash</code> zu ändern</ref> # <span lang="en" dir="ltr" class="mw-content-ltr">Your web server is configured to allow the execution of binary files in the MediaWiki tree.</span> : {{Note}} <span lang="en" dir="ltr" class="mw-content-ltr">Execute permissions may need to be set; for example, in Linux use:</span> ::<syntaxhighlight lang="bash"> chmod 755 /path/to/extensions/Scribunto/includes/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua</syntaxhighlight>If you are using SELinux in "Enforcing" mode on your server, you might need to set a proper context for the binaries. Example for RHEL/CentOS 7:<syntaxhighlight lang="bash"> chcon -t httpd_sys_script_exec_t /path/to/extensions/Scribunto/includes/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Additional binaries ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Additional Lua binary distributions, which may be needed for your web server if its operating system is not in the list above, can be obtained from http://luabinaries.sourceforge.net/ or from your Linux distribution. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Only binary files for Lua 5.1.x are supported. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once you've installed the appropriate binary file on your web server, configure the location of the file with: </div> <syntaxhighlight lang="php"> # Where Lua is the name of the binary file # e.g. SourceForge LuaBinaries 5.1.5 - Release 2 name the binary file lua5.1 $wgScribuntoEngineConf['luastandalone']['luaPath'] = '/path/to/binaries/lua5.1'; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that you should not add the above line unless you've confirmed that Scribunto's built-in binaries don't work for you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> LuaJIT, although theoretically compatible, is not supported. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The support was removed due to [[w:Spectre (security vulnerability)|Spectre]] and bitrot concerns ([[phab:T184156]]). </div> {{anchor|Installation}} == Installation == {{ExtensionInstall |vagrant=scribunto |localsettings= $wgScribuntoDefaultEngine = 'luastandalone'; |custom-steps=* <span lang="en" dir="ltr" class="mw-content-ltr">Set execute permissions for the Lua binaries bundled with this extension:</span> <syntaxhighlight lang="bash">chmod a+x /path/to/extensions/Scribunto/includes/engines/LuaStandalone/binaries/yourOS/lua</syntaxhighlight> * <span lang="en" dir="ltr" class="mw-content-ltr">Set type to <code>httpd_sys_script_exec_t</code> if SELinux is enforced:</span> <syntaxhighlight lang="bash">chcon -t httpd_sys_script_exec_t /path/to/extensions/Scribunto/includes/engines/LuaStandalone/binaries/yourOS/lua</syntaxhighlight> |registration=Yes |no-registration-version=1.29 }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Optional installation == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Integrating extensions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For a more pleasant user interface, with syntax highlighting and a code editor with autoindent, install the following extensions: </div> * {{ll|Extension:WikiEditor|nsp=0}} * {{ll|Extension:SyntaxHighlight|nsp=0}} * {{ll|Extension:CodeEditor|nsp=0}} {{MW version|version=1.30|comment=and before}} <div lang="en" dir="ltr" class="mw-content-ltr"> Then in your <code>LocalSettings.php</code> after all the extension registrations, add: </div> <syntaxhighlight lang="php"> $wgScribuntoUseGeSHi = true; $wgScribuntoUseCodeEditor = true; </syntaxhighlight> === LuaSandbox === Wir haben eine in C geschriebene PHP-Erweiterung entwickelt, die LuaSandbox heißt. Sie kann als Alternative zum unabhängigen Binärprogramm verwendet werden und bietet eine verbesserte Leistung. Siehe {{ll|LuaSandbox}} für Details und die Installationsanleitung. Wenn Sie die Erweiterung ursprünglich installiert haben, um die eigenständige Lua-Binärdatei zu verwenden, stellen Sie sicher, dass Sie <code>LocalSettings.php</code> mit der folgenden Konfigurationseinstellung aktualisieren: <syntaxhighlight lang="php"> $wgScribuntoDefaultEngine = 'luasandbox'; </syntaxhighlight> == Konfiguration == Die folgenden Konfigurationsvariablen sind verfügbar: ; $wgScribuntoDefaultEngine : Wählen Sie die Engine aus. Gültige Werte sind die Schlüssel in <code>$wgScribuntoEngineConf</code>, welche standardmäßig <code>'luasandbox'</code> oder <code>'luastandalone'</code> sind. ; $wgScribuntoUseGeSHi : Wenn {{ll|Extension:SyntaxHighlight}} installiert ist, setzen Sie diesen Wert auf true, um ihn bei der Anzeige von Modulseiten zu verwenden. (MediaWiki 1.30 oder früher.) ; $wgScribuntoUseCodeEditor : Wenn {{ll|Extension:CodeEditor}} installiert ist, setzen Sie diesen Wert auf <code>true</code>, um ihn beim Bearbeiten von Modulseiten zu verwenden. (MediaWiki 1.30 oder früher.) ; $wgScribuntoEngineConf : Ein assoziatives Array zur Engine-Konfiguration. Als Schlüssel werden die gültigen Werte für <code>$wgScribuntoDefaultEngine</code> bezeichnet und als Werte assoziative Arrays von Konfigurationsdaten. Jedes Konfigurations-Array muss einen Schlüssel <code>'class'</code> enthalten, der die Unterklasse <code>ScribuntoEngineBase</code> benennt, welche benutzt werden soll. === LuaStandalone === Die folgenden Schlüssel werden in <code>$wgScribuntoEngineConf</code> für <code>Scribunto_LuaStandaloneEngine</code> angewendet. Normalerweise sollten Sie in etwa die folgenden Einstellungen vornehmen: <syntaxhighlight lang="php"> $wgScribuntoEngineConf['luastandalone']['key'] = 'value'; </syntaxhighlight> ; luaPath : Bestimmen Sie den Pfad zu einem Lua-Interpreter. ; errorFile : Geben Sie den Pfad zu einer Datei an, die vom Web-Server-User beschreibbar ist und in der die Fehler- und Debugging-Ausgaben des Standalone-Interpreters protokolliert werden sollen. : Vom Standalone-Interpreter erzeugte Fehlermeldungen werden standardmäßig nicht protokolliert. Die Protokollierung wird konfiguriert mit: <syntaxhighlight lang="php"> $wgScribuntoEngineConf['luastandalone']['errorFile'] = '/path/to/file.log'; </syntaxhighlight> ; memoryLimit : Geben Sie das Speicherlimit in Bytes für den Standalone-Interpreter unter Linux an (wird mittels ''ulimit'' erzwungen). ; cpuLimit : Geben Sie das CPU-Zeitlimit in Sekunden für den Standalone-Interpreter unter Linux an (wird mittels ''ulimit'' erzwungen). ; allowEnvFuncs : <span lang="en" dir="ltr" class="mw-content-ltr">Set true to allow use of setfenv and getfenv in modules.</span> === LuaSandbox === <span lang="en" dir="ltr" class="mw-content-ltr">The following keys are used in <code>$wgScribuntoEngineConf</code> for <code>Scribunto_LuaSandboxEngine</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Generally you'd set these as something like</span> <syntaxhighlight lang="php"> $wgScribuntoEngineConf['luasandbox']['Schlüssel'] = 'Wert'; </syntaxhighlight> ; memoryLimit : <span lang="en" dir="ltr" class="mw-content-ltr">Specify the memory limit in bytes.</span> ; cpuLimit : <span lang="en" dir="ltr" class="mw-content-ltr">Specify the CPU time limit in seconds.</span> ; profilerPeriod : <span lang="en" dir="ltr" class="mw-content-ltr">Specify the time between polls in sections for the Lua profiler.</span> ; allowEnvFuncs : <span lang="en" dir="ltr" class="mw-content-ltr">Set true to allow use of setfenv and getfenv in modules.</span> {{Anchor|Usage}} == Benutzung == <span lang="en" dir="ltr" class="mw-content-ltr">Scripts go in a new namespace called '''[[Special:PrefixIndex/Module:|Module]]'''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each module has a collection of functions, which can be called using wikitext syntax such as:</span> {{Anchor|#invoke|.23invoke}}<nowiki>{{#invoke:</nowiki> ''Module_name'' | ''function_name'' | ''arg1'' | ''arg2'' | ''arg3'' ... }} ==Lua== === Lua lernen === <span lang="en" dir="ltr" class="mw-content-ltr">Lua is a simple programming language intended to be accessible to beginners.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For a quick crash-course on Lua, try [http://tylerneylon.com/a/learn-lua/ Learn Lua in 15 Minutes].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The best comprehensive introduction to Lua is the book ''Programming in Lua''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The first edition (for Lua 5.0) is available online and is mostly relevant to Lua 5.1, the version used by Scribunto:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * [https://www.lua.org/pil/index.html Programming in Lua] (scroll down past the book ads to find the text) </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The reference manual is also useful: </div> * {{ll|Extension:Scribunto/Lua reference manual}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Lua environment === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In Lua, the set of all global variables and functions is called an environment. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Each <code><nowiki>{{#invoke:}}</nowiki></code> call runs in a separate environment.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Variables defined in one <code><nowiki>{{#invoke:}}</nowiki></code> will not be available from another.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This restriction was necessary to maintain flexibility in the wikitext parser implementation.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The environment which scripts run in is not quite the same as in standard Lua.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These differences are noted in [[Special:MyLanguage/Extension:Scribunto/Lua reference manual#Differences from standard Lua|Extension:Scribunto/Lua reference manual]].</span>}} === Debugkonsole === [[File:Scribunto debug console usage example.png|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Debug console usage example</span>]] :''Siehe auch: {{ll|Extension:Scribunto/Debug console}}'' <span lang="en" dir="ltr" class="mw-content-ltr">When editing a Lua module a so-called "debug console" can be found underneath the edit form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this debug console Lua code can be executed without having to save or even create the Lua module in question.</span> == Fehlerbehebung == [[File:Script error clickable Scribunto.png|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Troubleshooting using the clickable "Script error" link.</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> Note that red <strong class="error">{{int|scribunto-parser-dialog-title}}</strong> messages are clickable and will provide more detailed information. </div> === {{int|scribunto-luastandalone-exited||1}} === <span lang="en" dir="ltr" class="mw-content-ltr">When using the LuaStandalone engine (this is the default), errors along the lines of '''"{{int|scribunto-luastandalone-exited||1}}"''' may be generated if the standalone Lua interpreter cannot be executed or runs into various runtime errors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To obtain more information, assign a file path to <syntaxhighlight lang="php" inline>$wgScribuntoEngineConf['luastandalone']['errorFile']</syntaxhighlight>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The interpreter's error output will be logged to the specified file, which should prove more helpful in tracking down the issue.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The information in the debug log includes debugging information, which is why there is so much of it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should be able to ignore any line beginning with "TX" or "RX".</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're setting up Scribunto and are using IIS/Windows, this appears to be solved by commenting out [https://www.mediawiki.org/w/index.php?title=Topic:W6pj4xql1tjpvfyb&topic_showPostId=watax8fwicsi11ps#flow-post-watax8fwicsi11ps a particular line].</span> === {{int|scribunto-luastandalone-exited||2}} === <span lang="en" dir="ltr" class="mw-content-ltr">When using the LuaStandalone engine (this is the default), status 2 suggests memory allocation errors, probably caused by settings that allocate inadequate memory space for PHP or Lua, or both.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Assigning a file path to <syntaxhighlight lang="php" inline>$wgScribuntoEngineConf['luastandalone']['errorFile']</syntaxhighlight> and examining that output can be valuable in diagnosing memory allocation errors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Increase PHP allocation in your PHP configuration; add the line <code>memory_limit = 200M</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This allocation of 200MB is often sufficient (as of MediaWiki 1.24) but can be increased as required.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set Scribunto's memory allocation in <code>LocalSettings.php</code> as a line:</span> <syntaxhighlight lang="php"> $wgScribuntoEngineConf['luastandalone']['memoryLimit'] = 209715200; # Bytes </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Finally, depending on the server configuration, some installations may be helped by adding another <code>LocalSettings.php</code> line </div> <syntaxhighlight lang="php"> $wgMaxShellMemory = 204800; # in KB </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that all 3 memory limits are given in different units. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Lua error: Internal error: 2. on ARM architecture === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you're using an ARM architecture processor like on a RaspberryPi you'll face the error <code>Lua error: Internal error: The interpreter exited with status 2.</code> due to wrong delivered binary format of the Lua interpreter. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check your Lua interpreter in: </div> /path/to/webdir/Scribunto/includes/engines/LuaStandalone/binaries/lua5_1_5_linux_32_generic <div lang="en" dir="ltr" class="mw-content-ltr"> Check the interpreter by using: </div> file lua <div lang="en" dir="ltr" class="mw-content-ltr"> The result should look like : </div> lua: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0 <div lang="en" dir="ltr" class="mw-content-ltr"> The installed default Lua interpreter shows: </div> lua: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.9, <div lang="en" dir="ltr" class="mw-content-ltr"> look at the "Intel 80386" part what definitely is not correct. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Check in <code>/usr/bin</code> what version of Lua is installed on your system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you have lua5.1 installed, you can either copy the interpreter to your <code>lua5_1_5_linux_32_generic</code> directory or set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> $wgScribuntoEngineConf['luastandalone']['luaPath'] = '/usr/bin/lua5.1' </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> At present don't set <code>wgScribuntoEngineConf</code> to /usr/bin/lua5.3, it'll lead to the "Internal error 1". </div> === {{int|scribunto-luastandalone-exited||24}} === <span lang="en" dir="ltr" class="mw-content-ltr">When using the LuaStandalone engine (this is the default), status 24 suggests CPU time limit errors, although those should be generating a "The time allocated for running scripts has expired" message instead.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It would be useful to file a task in {{ll|Phabricator}} and participate in determining why the XCPU signal isn't being caught.</span> === {{int|scribunto-luastandalone-exited||126}} === <span lang="en" dir="ltr" class="mw-content-ltr">When using the LuaStandalone engine (this is the default), errors along the lines of '''"{{int|scribunto-luastandalone-exited||126}}"''' may be generated if the standalone Lua interpreter cannot be executed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This generally arises from either of two causes:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * The lua executable file's permissions do not include Execute. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Set permissions as described under [[#Installation|#Installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server does not allow execution of files from the place where the executable is installed, e.g. the filesystem is mounted with the <code>'noexec'</code> flag. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This often occurs with shared hosted servers.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Remedies include adjusting <syntaxhighlight lang="php" inline>$wgScribuntoEngineConf['luastandalone']['luaPath']</syntaxhighlight> to point to a Lua 5.1 binary installed in an executable location, or adjusting or convincing the shared host to adjust the setting preventing execution.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Error condition such as: Fatal exception of type MWException=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check the MediaWiki, PHP, or webserver logs for more details on the exception, or temporarily set {{ll|Manual:$wgShowExceptionDetails|$wgShowExceptionDetails}} to <code>true</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===version 'GLIBC_2.11' not found=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">If the above gives you errors such as "version 'GLIBC_2.11' not found", it means the version of the standard C library on your system is too old for the binaries provided with Scribunto.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should upgrade your C library, or use a version of Lua 5.1 compiled for the C library you do have installed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To upgrade your C library, your best option is usually to follow your distribution's instructions for upgrading packages (or for upgrading to a new release of the distribution, if applicable).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you copy the lua binaries from Scribunto master (or from [[gerrit:77905]]), that should suffice, if you can't or don't want to upgrade your C library.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The distributed binaries were recently recompiled against an older version of glibc, so the minimum is now 2.3 rather than 2.11.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Lua errors in Scribunto files === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Errors here include: </div> * '''<span lang="en" dir="ltr" class="mw-content-ltr">attempt to index field 'text' (a nil value)</span>''' * '''<span lang="en" dir="ltr" class="mw-content-ltr">Lua error in mw.html.lua at line 253: Invalid class given:</span>''' <div lang="en" dir="ltr" class="mw-content-ltr"> If you are getting errors such these when attempting to use modules imported from WMF wikis, most likely your version of Scribunto is out of date. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upgrade if possible; for advanced users, you might also try to identify the needed newer commits and cherry-pick them into your local installation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === preg_replace_callback(): Compilation failed: unknown property name after \P or \p at offset 7 === </div> <code><span lang="en" dir="ltr" class="mw-content-ltr">preg_replace_callback(): Compilation failed: unknown property name after \P or \p at offset 7</span></code> * <span lang="en" dir="ltr" class="mw-content-ltr">this usually indicates an incompatible version of PCRE; you'll need to update to >= 8.10</span> * <span lang="en" dir="ltr" class="mw-content-ltr">@todo: link to instructions on how to upgrade</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Lua error === </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you copy templates from Wikipedia and then get big red "Lua error: x" messages where the Scribunto invocation (e.g. the template that uses <code><nowiki>{{#invoke:}}</nowiki></code>) should be, that probably means that you didn't import everything you needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Make sure that you tick the "Include templates" box at [[w:Special:Export]] when you export.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> When importing pages from another wiki, it is also possible for templates or modules in the imported data to overwrite existing templates or modules with the same title, which may break existing pages, templates, and modules that depend on the overwritten versions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Blank screen === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure your extension version is applicable to your MediaWiki version. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Design documents == </div> *[[File:Linux.conf.au 2014 - Scribunto presentation.webm|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">[[User:Tim Starling|Tim Starling]]'s presentation at [[w:Linux.conf.au|linux.conf.au]] 2014 discussing the motivations, implementation challenges and results of deploying Scribunto and Lua.</span>]]{{ll|Extension:Scribunto/Parser interface design}} * {{ll|Extension:Scribunto/Victor's API proposal}} * {{ll|Extension:Scribunto/Documentation specification}} * {{ll|Extension:Scribunto/Tim's draft roadmap}} == Andere Seiten == * {{ll|Extension:Scribunto/Deployment priorities}} * {{ll|Extension:Scribunto/Brainstorming}} * {{ll|Lua scripting}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia activity page describing deployment plan to Wikimedia sites.</span> * {{ll|Extension:Scribunto/Lua reference manual}} - <span lang="en" dir="ltr" class="mw-content-ltr">The reference about the Lua language, as well as its standard libraries and common Scribunto modules supported on Wikimedia sites.</span> * {{ll|Extension:Scribunto/Lua 5.2 changes}} - <span lang="en" dir="ltr" class="mw-content-ltr">A list of known changes in Lua 5.2 that may cause code written in 5.1 to function unexpectedly.</span> * {{ll|Extension:Scribunto/Example modules}} * {{ll|Extension:Scribunto/Example extension}} - <span lang="en" dir="ltr" class="mw-content-ltr">Code for example extensions extending the Scribunto library.</span> * {{ll|Extension:Scribunto/We use Lua}} == Siehe auch == ; General * {{ll|Extension:Wikibase Client/Lua|Lua Wikibase client}} - <span lang="en" dir="ltr" class="mw-content-ltr">functionality for the Scribunto extension.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[commons:Special:MyLanguage/Commons:Lua|Commons:Lua]] - there may be specific notes for using Lua modules on Wikimedia Commons, including additional Lua extensions installed (e.g. for local support of internationalization and for parsing or playing medias).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Some general purpose modules may be reused in other wikis in various languages (except specific tunings for policies, namespaces or project/maintenance pages with dedicated names).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If possible, modules that could be widely reused across wikis should be tested and internationalized on Wikimedia Commons.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[w:Help:Lua]] - there may be specific notes for using Lua modules on Wikipedia, including additional Lua extensions installed (including for integrating Wikidata and Wikimedia Commons contents, generating complex infoboxes and navigation boxes, or to facilitate the general administration/maintenance of the wiki contents under applicable policies).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Some other localized Wikipedia editions (or other projects such Wiktionnary, Wikisource or Wikinews) may also have their own needs and Lua modules.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[d:Special:MyLanguage/Help:Lua|d:Help:Lua]] - there may be specific notes for using Lua modules on Wikidata, including additional Lua extensions installed (e.g. for local support of internationalization and for database queries)</span> ; Extensions * {{ll|Extension:Capiunto|nsp=0}} - <span lang="en" dir="ltr" class="mw-content-ltr">Provides basic [[Special:MyLanguage/Extension:Capiunto/Infobox|infobox]] functionality for the Scribunto extension.</span> * {{ll|Extension:Semantic Scribunto|nsp=0}} - <span lang="en" dir="ltr" class="mw-content-ltr">provides native support for the Scribunto extension for usage with {{ll|Extension:Semantic MediaWiki|nsp=0}}</span> * {{ll|Extension:VariablesLua|nsp=0}} - <span lang="en" dir="ltr" class="mw-content-ltr">provides a Scribunto Lua interface for the Variables extension</span> * {{ll|Extension:Wikibase Client|nsp=0}} - <span lang="en" dir="ltr" class="mw-content-ltr">provides {{ll|Wikibase}} (part of [[m:Special:MyLanguage/Wikidata|Wikidata]] project)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Notes == </div> <references /> {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|prowiki=1}} [[Category:Scribunto extensions{{#translation:}}| ]] [[Category:ContentHandler extensions{{#translation:}}]] [[Category:GPL licensed extensions{{#translation:}}]] [[Category:MIT licensed extensions{{#translation:}}]] 55b9r9hylgtpvyyff1fmxhgmzhq9fqs Translations:Groups/4/fr 1198 864497 5387375 3040950 2022-07-28T22:12:36Z Shirayuki 472859 update wikitext text/x-wiki Les groupes MediaWiki sont ouverts aux membres de [[$1|différentes spécialtés]] et de niveau d'expertise. pns9sjp3xkq9u3qvwddiggqhwy2wzya Translations:Groups/25/fr 1198 864669 5387400 3041557 2022-07-28T22:14:59Z Shirayuki 472859 update wikitext text/x-wiki Egalement pour les groupes qui ne parlent pas anglais : * Internationalisation de la documentation et du logiciel d'après les procédures $1 . 4djuo8q1a90bfz1q3o3fisnzs82wbjm Wikimedia Product/vi 0 866930 5387600 5358219 2022-07-29T03:26:09Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Người đóng góp</span>]] * [[Readers|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Readers</span></span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] (hiếm khi dùng) * <span class="mw-translate-fuzzy">Trang</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span class="mw-translate-fuzzy">Đội ngũ</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span class="mw-translate-fuzzy">Trang</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span class="mw-translate-fuzzy">Trang</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Trang [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span class="mw-translate-fuzzy">Trang</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span class="mw-translate-fuzzy">Trang</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span class="mw-translate-fuzzy">Trang</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span class="mw-translate-fuzzy">Đội ngũ</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === Wikidata === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span class="mw-translate-fuzzy">Trang</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Mục tiêu == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: tháng 7 – tháng 9 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span class="mw-translate-fuzzy">Q2: tháng 10 – tháng 12 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span class="mw-translate-fuzzy">Q3: tháng 1 – tháng 3 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span class="mw-translate-fuzzy">Q4: tháng 4 – tháng 6 2019</span>]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span class="mw-translate-fuzzy">Q1: tháng 7 – tháng 9 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span class="mw-translate-fuzzy">Q2: tháng 10 – tháng 12 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span class="mw-translate-fuzzy">Q3: tháng 1 – tháng 3 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span class="mw-translate-fuzzy">Q4: tháng 4 – tháng 6 2018</span>]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span class="mw-translate-fuzzy">Q1: tháng 7 – tháng 9 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span class="mw-translate-fuzzy">Q2: tháng 10 – tháng 12 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span class="mw-translate-fuzzy">Q3: tháng 1 – tháng 3 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span class="mw-translate-fuzzy">Q4: tháng 4 – tháng 6 2017</span>]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span class="mw-translate-fuzzy">Q1: tháng 7 – tháng 9 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span class="mw-translate-fuzzy">Q2: tháng 10 – tháng 12 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span class="mw-translate-fuzzy">Q3: tháng 1 – tháng 3 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span class="mw-translate-fuzzy">Q4: tháng 4 – tháng 6 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] jvrtdib022t7714nghud50yxo8s4ony Wikimedia Product/es 0 867949 5387574 5358193 2022-07-29T03:25:43Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=El equipo del '''Producto Wikimedia''' [[foundationsite:role/staff-contractors/|empleado por la Fundación Wikimedia]] crea, improvisa y mantiene las características principales de los [[m:Special:MyLanguage/Wikimedia projects|sitios de Wikimedia]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Colaboradores</span>]] * [[Readers|<span style="color:#2aa198">Lectores</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|Principios del producto]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (anteriormente: [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === Programas === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] (Raramente utilizado) * Página: [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Página: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== Salud Comunitaria ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * Página [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Página [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * Página [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Página [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * Página [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|Web]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span class="mw-translate-fuzzy">Página</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Objetivos == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: April @– junio 2019]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2017–2018</span> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2016–2017</span> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] s8n6e68la6mxpj168trwcib0hl4rcor Translations:Groups/25/pt-br 1198 871823 5387413 3063680 2022-07-28T22:15:33Z Shirayuki 472859 update wikitext text/x-wiki Também para grupos que não falam inglês: * Localização de documentação e software seguindo processos do $1. msqmbgqxpcksbq4rk0phnml5ntsaued Manual:Installing third-party tools/ko 100 880944 5387824 5377082 2022-07-29T09:29:27Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/ko]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/ko]] 2mv5oubsjsrbcsagzy12ozik9wg3xf7 Manual:Installation guide/sc 100 882025 5386669 5381103 2022-07-28T17:14:36Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/sc]] tbvmvprun1200r3b6b6sqwc5l77cwi7 5386684 5386669 2022-07-28T17:22:35Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/sc]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Translations:Manual:Installation guide/11/sc 1198 882052 5387292 4700878 2022-07-28T21:57:46Z Baris6161TURK 17188421 wikitext text/x-wiki S'anteprima de sas immàgines e $texvc tenent bisòngiu de programmas annantivos. $1 (pedidu dae VisualEditor) e àteros servìtzios tenent sos recuisidos pròpios. n5f31zefdg67d8030l7wdq52zvqk539 Template:InstallationNav/ckb 10 890485 5387190 5384775 2022-07-28T21:17:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 HHVM/es 0 912431 5387450 5240443 2022-07-28T22:32:05Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = Soporte en MediaWiki para HHVM (Máquina Virtual HipHop) e implementación en el clúster de Wikimedia | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span class="mw-translate-fuzzy">Véase [[Special:MyLanguage/HHVM/About|HHVM/Acerca de]] para obtener una descripción más breve y la publicación del blog de diciembre de 2014 sobre '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ Cómo hicimos la edición de Wikipedia dos veces más rápido]"''' para obtener más información sobre HHVM, sus beneficios y una mirada retrospectiva al trabajo de implementación.</span> {{note|1=En septiembre de 2017, Facebook anunció que HHVM no apuntaría a la compatibilidad con PHP en el futuro.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "El futuro de HHVM"]</ref> Después de la discusión,<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adoptó un plan para migrar el clúster de producción de WMF a PHP 7. La compatibilidad con HHVM se ha eliminado de MediaWiki. Véase {{phabricator|T176209}} y {{phabricator|T192166}}.}} '''[[w:HHVM|HHVM]]''' es una herramienta de interpretación de PHP (concretamente una máquina virtual que compila el código de bytes de PHP a las instrucciones nativas en tiempo de ejecución) que se implementó en los servidores de Wikimedia en 2014, lo que reduce el tiempo de carga de: cualquier página que vea mientras está conectado, y para guardar las páginas que hayas editado tanto como si hubieras iniciado sesión o no. == Hoja de ruta == <span class="mw-translate-fuzzy">HHVM es una nueva forma para que los sitios web ejecuten [[special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (escrito en [[:es:PHP|PHP]]).</span> A veces se le conoce por su nombre completo HipHop Virtual Machine (en [[:es:Idioma inglés|inglés]] Máquina Virtual HipHop), y tiene un compilador en tiempo de ejecución (JIT). HHVM debe acelerar la visualización de la página para los usuarios que hayan iniciado sesión y también acelerar el guardado de páginas editadas para todos los usuarios. Esta página trata sobre el trabajo patrocinado por Wikimedia sobre el soporte de HipHop en MediaWiki y su implementación en los wikis de producción de Wikimedia. Históricamente, el compilador HipHop fue un proyecto de Facebook que involucró el compilamiento del código PHP en C++ con el fin de acelerar el lenguaje. Desde entonces, Facebook ha abandonado este proyecto, y ahora sus esfuerzos de desarrollo se centran en HHVM en su lugar. Este es el plan general para implementar HHVM en el clúster de producción en 2014: * Implementación en Beta Cluster (trabajo actualmente en curso, en paralelo con otro trabajo) {{done}} * Semana del 21 de julio: el despliegue del funcionamiento de trabajo en la producción {{done}} * Implementar en el servidor de aplicaciones test.wikipedia.org {{done}} * Implementar el módulo Varnish permitiendo la implementación parcial en una fracción de los servidores de aplicaciones{{Done}} * Implementación limitada a un pequeño número de servidores de aplicaciones {{Done}} * Acelerar la implementación a más servidores de aplicaciones hasta que la mayoría de los servidores utilicen HHVM{{done}} *Implementar al resto de servicios{{done}} === Trabajo de HHVM === En Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. == Justificación == <span class="mw-translate-fuzzy">Es un fenómeno bien estudiado que incluso pequeños retrasos en el tiempo de respuesta (por ejemplo, la mitad de un segundo) pueden dar lugar a fuertes disminuciones en la retención de usuarios de la web.<ref>[$radar "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</ref><ref>[$glinden Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> Como resultado, los sitios web populares como Google y Facebook invierten mucho en iniciativas de rendimiento del sitio, y como resultado, siguen siendo populares. <span class="mw-translate-fuzzy">Antiguamente los sitios populares (como Friendster) sufrían debido a la falta de atención a estos problemas.<ref>"[$nytimes Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> Wikipedia y sus proyectos hermanos deben seguir siendo utilizables y receptivos para que el movimiento pueda sostener su misión. Facebook, como gran usuario de PHP, ha reconocido este problema e invirtió mucho<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> en una solución: [http://hhvm.com HHVM], una máquina virtual que compila el código de bytes de PHP con instrucciones nativas en tiempo de ejecución, la misma estrategia utilizada por Java y C# para lograr sus ventajas de velocidad. Estamos bastante seguros de que esto también dará como resultado grandes mejoras de rendimiento en nuestros sitios. == ¿Qué hace HipHop por nuestros usuarios finales? == MediaWiki está escrito en PHP, un lenguaje que se [[w:es:Intérprete (informática)|interpreta]] en tiempo de ejecución. La sobrecarga de ejecutar este código PHP cada vez que alguien visita una página requiere el uso de servidores de almacenamiento en caché, ejecutando software como [[:es:Varnish Cache|Varnish]], que almacena el HTML generado al ejecutar este PHP, de modo que PHP no tiene que ejecutarse cada vez que se visita una página. <span class="mw-translate-fuzzy">Estos cachés solo sirven a los usuarios que no han iniciado sesión.<ref>Por definición, a los usuarios que han iniciado sesión no se les pueden servir páginas desde un caché estático, ya que la página que se les proporciona debe incluir HTML específico del usuario, como su nombre de usuario en la parte superior derecha de la página. Desafortunadamente, esto crea una situación en la que simplemente el inicio de sesión provoca una disminución tangible en el rendimiento de nuestros sitios para usted.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> Las acciones que no se ven afectadas por el caché, y por lo tanto ''se ven'' afectadas por el tiempo de ejecución del código PHP, incluyen: *Cualquier página que vea mientras está conectado. *Páginas guardadas que hayas editado, ya sea que hayas iniciado sesión o no. Por lo tanto, cualquier acción que podamos tomar para reducir el tiempo que toma el código PHP de MediaWiki también disminuirá los tiempos de carga de nuestro sitio para todos nuestros usuarios registrados y cualquier persona que edite anónimamente. HipHop fue escrito para ser un intérprete de PHP más rápido y eficiente que nuestro intérprete actual ([[:es:Motor Zend|Zend]]). Esperamos que al implementar HipHop como un reemplazo para Zend, nuestros usuarios noten un aumento tangible en el rendimiento de nuestros sitios. == ¿Cómo afecta nuestro trabajo en HipHop a los desarrolladores de MediaWiki? == En nuestro rápido inicio del trabajo inicial, que se que se debe haber terminado a fines de marzo de 2014, esperamos hacerlo para que cualquiera pueda elegir usar HipHop en Beta Cluster en lugar de Zend. Esto será sobre una base totalmente optativa que puede ser deshabilitada en cualquier momento. Esto permitirá que el equipo de MediaWiki Core evalúe el rendimiento de HipHop contra el de Zend directamente utilizando nuestra infraestructura de prueba actual, en lugar de estimar los aumentos de rendimiento teóricos. También creará un entorno de desarrollo que nos ayudará a ver cuánto trabajo se necesita para hacer que HipHop sea compatible con MediaWiki, y como tal, nos permite hacer una estimación de cuánto tiempo nos tomará hacer que HipHop se mantenga en producción, como un reemplazo completo de Zend. Para otros desarrolladores de MediaWiki, la consecuencia de que HipHop se implemente de esta manera es que si utilizan Beta Cluster como un entorno de prueba, les resultará trivial probar cómo funcionan sus parches utilizando HipHop en lugar de Zend, si así lo desean. Sin embargo, para minimizar la interrupción de nuestro trabajo, la naturaleza opt-in de la infraestructura permitirá que los desarrolladores puedan continuar desarrollando una actitud totalmente independiente de la futura migración a HipHop si así lo desean. == Véase también == * {{ll|HHVM/About|HHVM/Acerca de}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Configurando HHVM en {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presentando en @Scale sobre la migración a HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM en producción: lo que eso significa para los desarrolladores de Wikimedia] == Notas y referencias == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] fekw73zb8yh2rh8e9twqfsncdxaqfa9 5387461 5387450 2022-07-28T22:32:53Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = Soporte en MediaWiki para HHVM (Máquina Virtual HipHop) e implementación en el clúster de Wikimedia | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :Véase [[Special:MyLanguage/HHVM/About|HHVM/Acerca de]] para obtener una descripción más breve y la publicación del blog de diciembre de 2014 sobre '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ Cómo hicimos la edición de Wikipedia dos veces más rápido]"''' para obtener más información sobre HHVM, sus beneficios y una mirada retrospectiva al trabajo de implementación. {{note|1=En septiembre de 2017, Facebook anunció que HHVM no apuntaría a la compatibilidad con PHP en el futuro.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "El futuro de HHVM"]</ref> Después de la discusión,<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adoptó un plan para migrar el clúster de producción de WMF a PHP 7. La compatibilidad con HHVM se ha eliminado de MediaWiki. Véase {{phabricator|T176209}} y {{phabricator|T192166}}.}} '''[[w:HHVM|HHVM]]''' es una herramienta de interpretación de PHP (concretamente una máquina virtual que compila el código de bytes de PHP a las instrucciones nativas en tiempo de ejecución) que se implementó en los servidores de Wikimedia en 2014, lo que reduce el tiempo de carga de: cualquier página que vea mientras está conectado, y para guardar las páginas que hayas editado tanto como si hubieras iniciado sesión o no. == Hoja de ruta == <span class="mw-translate-fuzzy">HHVM es una nueva forma para que los sitios web ejecuten [[special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (escrito en [[:es:PHP|PHP]]).</span> A veces se le conoce por su nombre completo HipHop Virtual Machine (en [[:es:Idioma inglés|inglés]] Máquina Virtual HipHop), y tiene un compilador en tiempo de ejecución (JIT). HHVM debe acelerar la visualización de la página para los usuarios que hayan iniciado sesión y también acelerar el guardado de páginas editadas para todos los usuarios. Esta página trata sobre el trabajo patrocinado por Wikimedia sobre el soporte de HipHop en MediaWiki y su implementación en los wikis de producción de Wikimedia. Históricamente, el compilador HipHop fue un proyecto de Facebook que involucró el compilamiento del código PHP en C++ con el fin de acelerar el lenguaje. Desde entonces, Facebook ha abandonado este proyecto, y ahora sus esfuerzos de desarrollo se centran en HHVM en su lugar. Este es el plan general para implementar HHVM en el clúster de producción en 2014: * Implementación en Beta Cluster (trabajo actualmente en curso, en paralelo con otro trabajo) {{done}} * Semana del 21 de julio: el despliegue del funcionamiento de trabajo en la producción {{done}} * Implementar en el servidor de aplicaciones test.wikipedia.org {{done}} * Implementar el módulo Varnish permitiendo la implementación parcial en una fracción de los servidores de aplicaciones{{Done}} * Implementación limitada a un pequeño número de servidores de aplicaciones {{Done}} * Acelerar la implementación a más servidores de aplicaciones hasta que la mayoría de los servidores utilicen HHVM{{done}} *Implementar al resto de servicios{{done}} === Trabajo de HHVM === En Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. == Justificación == <span class="mw-translate-fuzzy">Es un fenómeno bien estudiado que incluso pequeños retrasos en el tiempo de respuesta (por ejemplo, la mitad de un segundo) pueden dar lugar a fuertes disminuciones en la retención de usuarios de la web.<ref>[$radar "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</ref><ref>[$glinden Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> Como resultado, los sitios web populares como Google y Facebook invierten mucho en iniciativas de rendimiento del sitio, y como resultado, siguen siendo populares. <span class="mw-translate-fuzzy">Antiguamente los sitios populares (como Friendster) sufrían debido a la falta de atención a estos problemas.<ref>"[$nytimes Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> Wikipedia y sus proyectos hermanos deben seguir siendo utilizables y receptivos para que el movimiento pueda sostener su misión. Facebook, como gran usuario de PHP, ha reconocido este problema e invirtió mucho<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> en una solución: [http://hhvm.com HHVM], una máquina virtual que compila el código de bytes de PHP con instrucciones nativas en tiempo de ejecución, la misma estrategia utilizada por Java y C# para lograr sus ventajas de velocidad. Estamos bastante seguros de que esto también dará como resultado grandes mejoras de rendimiento en nuestros sitios. == ¿Qué hace HipHop por nuestros usuarios finales? == MediaWiki está escrito en PHP, un lenguaje que se [[w:es:Intérprete (informática)|interpreta]] en tiempo de ejecución. La sobrecarga de ejecutar este código PHP cada vez que alguien visita una página requiere el uso de servidores de almacenamiento en caché, ejecutando software como [[:es:Varnish Cache|Varnish]], que almacena el HTML generado al ejecutar este PHP, de modo que PHP no tiene que ejecutarse cada vez que se visita una página. <span class="mw-translate-fuzzy">Estos cachés solo sirven a los usuarios que no han iniciado sesión.<ref>Por definición, a los usuarios que han iniciado sesión no se les pueden servir páginas desde un caché estático, ya que la página que se les proporciona debe incluir HTML específico del usuario, como su nombre de usuario en la parte superior derecha de la página. Desafortunadamente, esto crea una situación en la que simplemente el inicio de sesión provoca una disminución tangible en el rendimiento de nuestros sitios para usted.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> Las acciones que no se ven afectadas por el caché, y por lo tanto ''se ven'' afectadas por el tiempo de ejecución del código PHP, incluyen: *Cualquier página que vea mientras está conectado. *Páginas guardadas que hayas editado, ya sea que hayas iniciado sesión o no. Por lo tanto, cualquier acción que podamos tomar para reducir el tiempo que toma el código PHP de MediaWiki también disminuirá los tiempos de carga de nuestro sitio para todos nuestros usuarios registrados y cualquier persona que edite anónimamente. HipHop fue escrito para ser un intérprete de PHP más rápido y eficiente que nuestro intérprete actual ([[:es:Motor Zend|Zend]]). Esperamos que al implementar HipHop como un reemplazo para Zend, nuestros usuarios noten un aumento tangible en el rendimiento de nuestros sitios. == ¿Cómo afecta nuestro trabajo en HipHop a los desarrolladores de MediaWiki? == En nuestro rápido inicio del trabajo inicial, que se que se debe haber terminado a fines de marzo de 2014, esperamos hacerlo para que cualquiera pueda elegir usar HipHop en Beta Cluster en lugar de Zend. Esto será sobre una base totalmente optativa que puede ser deshabilitada en cualquier momento. Esto permitirá que el equipo de MediaWiki Core evalúe el rendimiento de HipHop contra el de Zend directamente utilizando nuestra infraestructura de prueba actual, en lugar de estimar los aumentos de rendimiento teóricos. También creará un entorno de desarrollo que nos ayudará a ver cuánto trabajo se necesita para hacer que HipHop sea compatible con MediaWiki, y como tal, nos permite hacer una estimación de cuánto tiempo nos tomará hacer que HipHop se mantenga en producción, como un reemplazo completo de Zend. Para otros desarrolladores de MediaWiki, la consecuencia de que HipHop se implemente de esta manera es que si utilizan Beta Cluster como un entorno de prueba, les resultará trivial probar cómo funcionan sus parches utilizando HipHop en lugar de Zend, si así lo desean. Sin embargo, para minimizar la interrupción de nuestro trabajo, la naturaleza opt-in de la infraestructura permitirá que los desarrolladores puedan continuar desarrollando una actitud totalmente independiente de la futura migración a HipHop si así lo desean. == Véase también == * {{ll|HHVM/About|HHVM/Acerca de}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Configurando HHVM en {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presentando en @Scale sobre la migración a HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM en producción: lo que eso significa para los desarrolladores de Wikimedia] == Notas y referencias == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] q65ze6g55awoalfyljjddsvjor8v31x 5387465 5387461 2022-07-28T22:34:20Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = Soporte en MediaWiki para HHVM (Máquina Virtual HipHop) e implementación en el clúster de Wikimedia | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :Véase [[Special:MyLanguage/HHVM/About|HHVM/Acerca de]] para obtener una descripción más breve y la publicación del blog de diciembre de 2014 sobre '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ Cómo hicimos la edición de Wikipedia dos veces más rápido]"''' para obtener más información sobre HHVM, sus beneficios y una mirada retrospectiva al trabajo de implementación. {{note|1=En septiembre de 2017, Facebook anunció que HHVM no apuntaría a la compatibilidad con PHP en el futuro.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "El futuro de HHVM"]</ref> Después de la discusión,<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adoptó un plan para migrar el clúster de producción de WMF a PHP 7. La compatibilidad con HHVM se ha eliminado de MediaWiki. Véase {{phabricator|T176209}} y {{phabricator|T192166}}.}} '''[[w:HHVM|HHVM]]''' es una herramienta de interpretación de PHP (concretamente una máquina virtual que compila el código de bytes de PHP a las instrucciones nativas en tiempo de ejecución) que se implementó en los servidores de Wikimedia en 2014, lo que reduce el tiempo de carga de: cualquier página que vea mientras está conectado, y para guardar las páginas que hayas editado tanto como si hubieras iniciado sesión o no. == Hoja de ruta == HHVM es una nueva forma para que los sitios web ejecuten [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (escrito en [[:es:PHP|PHP]]). A veces se le conoce por su nombre completo HipHop Virtual Machine (en [[:es:Idioma inglés|inglés]] Máquina Virtual HipHop), y tiene un compilador en tiempo de ejecución (JIT). HHVM debe acelerar la visualización de la página para los usuarios que hayan iniciado sesión y también acelerar el guardado de páginas editadas para todos los usuarios. Esta página trata sobre el trabajo patrocinado por Wikimedia sobre el soporte de HipHop en MediaWiki y su implementación en los wikis de producción de Wikimedia. Históricamente, el compilador HipHop fue un proyecto de Facebook que involucró el compilamiento del código PHP en C++ con el fin de acelerar el lenguaje. Desde entonces, Facebook ha abandonado este proyecto, y ahora sus esfuerzos de desarrollo se centran en HHVM en su lugar. Este es el plan general para implementar HHVM en el clúster de producción en 2014: * Implementación en Beta Cluster (trabajo actualmente en curso, en paralelo con otro trabajo) {{done}} * Semana del 21 de julio: el despliegue del funcionamiento de trabajo en la producción {{done}} * Implementar en el servidor de aplicaciones test.wikipedia.org {{done}} * Implementar el módulo Varnish permitiendo la implementación parcial en una fracción de los servidores de aplicaciones{{Done}} * Implementación limitada a un pequeño número de servidores de aplicaciones {{Done}} * Acelerar la implementación a más servidores de aplicaciones hasta que la mayoría de los servidores utilicen HHVM{{done}} *Implementar al resto de servicios{{done}} === Trabajo de HHVM === En Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. == Justificación == <span class="mw-translate-fuzzy">Es un fenómeno bien estudiado que incluso pequeños retrasos en el tiempo de respuesta (por ejemplo, la mitad de un segundo) pueden dar lugar a fuertes disminuciones en la retención de usuarios de la web.<ref>[$radar "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</ref><ref>[$glinden Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> Como resultado, los sitios web populares como Google y Facebook invierten mucho en iniciativas de rendimiento del sitio, y como resultado, siguen siendo populares. <span class="mw-translate-fuzzy">Antiguamente los sitios populares (como Friendster) sufrían debido a la falta de atención a estos problemas.<ref>"[$nytimes Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> Wikipedia y sus proyectos hermanos deben seguir siendo utilizables y receptivos para que el movimiento pueda sostener su misión. Facebook, como gran usuario de PHP, ha reconocido este problema e invirtió mucho<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> en una solución: [http://hhvm.com HHVM], una máquina virtual que compila el código de bytes de PHP con instrucciones nativas en tiempo de ejecución, la misma estrategia utilizada por Java y C# para lograr sus ventajas de velocidad. Estamos bastante seguros de que esto también dará como resultado grandes mejoras de rendimiento en nuestros sitios. == ¿Qué hace HipHop por nuestros usuarios finales? == MediaWiki está escrito en PHP, un lenguaje que se [[w:es:Intérprete (informática)|interpreta]] en tiempo de ejecución. La sobrecarga de ejecutar este código PHP cada vez que alguien visita una página requiere el uso de servidores de almacenamiento en caché, ejecutando software como [[:es:Varnish Cache|Varnish]], que almacena el HTML generado al ejecutar este PHP, de modo que PHP no tiene que ejecutarse cada vez que se visita una página. <span class="mw-translate-fuzzy">Estos cachés solo sirven a los usuarios que no han iniciado sesión.<ref>Por definición, a los usuarios que han iniciado sesión no se les pueden servir páginas desde un caché estático, ya que la página que se les proporciona debe incluir HTML específico del usuario, como su nombre de usuario en la parte superior derecha de la página. Desafortunadamente, esto crea una situación en la que simplemente el inicio de sesión provoca una disminución tangible en el rendimiento de nuestros sitios para usted.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> Las acciones que no se ven afectadas por el caché, y por lo tanto ''se ven'' afectadas por el tiempo de ejecución del código PHP, incluyen: *Cualquier página que vea mientras está conectado. *Páginas guardadas que hayas editado, ya sea que hayas iniciado sesión o no. Por lo tanto, cualquier acción que podamos tomar para reducir el tiempo que toma el código PHP de MediaWiki también disminuirá los tiempos de carga de nuestro sitio para todos nuestros usuarios registrados y cualquier persona que edite anónimamente. HipHop fue escrito para ser un intérprete de PHP más rápido y eficiente que nuestro intérprete actual ([[:es:Motor Zend|Zend]]). Esperamos que al implementar HipHop como un reemplazo para Zend, nuestros usuarios noten un aumento tangible en el rendimiento de nuestros sitios. == ¿Cómo afecta nuestro trabajo en HipHop a los desarrolladores de MediaWiki? == En nuestro rápido inicio del trabajo inicial, que se que se debe haber terminado a fines de marzo de 2014, esperamos hacerlo para que cualquiera pueda elegir usar HipHop en Beta Cluster en lugar de Zend. Esto será sobre una base totalmente optativa que puede ser deshabilitada en cualquier momento. Esto permitirá que el equipo de MediaWiki Core evalúe el rendimiento de HipHop contra el de Zend directamente utilizando nuestra infraestructura de prueba actual, en lugar de estimar los aumentos de rendimiento teóricos. También creará un entorno de desarrollo que nos ayudará a ver cuánto trabajo se necesita para hacer que HipHop sea compatible con MediaWiki, y como tal, nos permite hacer una estimación de cuánto tiempo nos tomará hacer que HipHop se mantenga en producción, como un reemplazo completo de Zend. Para otros desarrolladores de MediaWiki, la consecuencia de que HipHop se implemente de esta manera es que si utilizan Beta Cluster como un entorno de prueba, les resultará trivial probar cómo funcionan sus parches utilizando HipHop en lugar de Zend, si así lo desean. Sin embargo, para minimizar la interrupción de nuestro trabajo, la naturaleza opt-in de la infraestructura permitirá que los desarrolladores puedan continuar desarrollando una actitud totalmente independiente de la futura migración a HipHop si así lo desean. == Véase también == * {{ll|HHVM/About|HHVM/Acerca de}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Configurando HHVM en {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presentando en @Scale sobre la migración a HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM en producción: lo que eso significa para los desarrolladores de Wikimedia] == Notas y referencias == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] jf6rrtzb19moyhpmbracy3hmg5gosn9 Translations:HHVM/28/es 1198 912434 5387460 3187440 2022-07-28T22:32:52Z Shirayuki 472859 update wikitext text/x-wiki Véase [[$1|HHVM/Acerca de]] para obtener una descripción más breve y la publicación del blog de diciembre de 2014 sobre '''"[$blog Cómo hicimos la edición de Wikipedia dos veces más rápido]"''' para obtener más información sobre HHVM, sus beneficios y una mirada retrospectiva al trabajo de implementación. 8dsat56uqqwqpy0on5r9l0tcaabdgs8 Translations:HHVM/5/es 1198 912441 5387464 4299827 2022-07-28T22:34:19Z Shirayuki 472859 update wikitext text/x-wiki HHVM es una nueva forma para que los sitios web ejecuten [[$1|MediaWiki]] (escrito en [[:es:PHP|PHP]]). nr7qis84qg6abg74nfn39angwhtzxsr Help:Reference Previews/ja 12 914354 5387442 5230220 2022-07-28T22:21:33Z Shirayuki 472859 wrong markup wikitext text/x-wiki <languages /> {{PD Help Page}} [[File:Example of a Reference Preview.png|300px|right]] '''参照プレビュー'''は、脚注マーカーの上にカーソルを置くと脚注の内容を小窓に表示する機能です。この機能は MediaWiki 拡張機能である {{ll|Extension:Popups|Popups}} の一部であり、{{ll|Page Previews}} に使用されます。 現時点ではベータ版の機能です。 <span lang="en" dir="ltr" class="mw-content-ltr">It's currently a default feature on some wikis and a beta feature on many other wikis.</span> == 背景 == 参考資料プレビュー機能はドイツ語話者コミュニティの技術要望リストに対応する目的で、開発はウィキメディアドイツ支部 (WMDE) の技術チームが担当しウィキメディア財団 (WMF) Reading Web チームが支援しました。設計部分は WMFが開発しています。 詳細は[[m:WMDE Technical Wishes/ReferencePreviews|Metaにあるプロジェクトのメインページ]]をご参照ください。 === 概要 === 参考資料プレビューは、脚注のプレビューを、脚注一覧で表示されるように見ることができます。プレビュー上では、脚注のすべてのコンテンツが表示されます。プレビューの一番上には、脚注の種類が表示されます。 参考資料プレビューは、[[mw:Page Previews/ja|ページプレビュー]]のように、記事でも脚注でもマウスポインターを当てればプレビューを見ることができるように作られました。 [[File:Page Previews and Reference Previews.png|thumb|400x400px|<span lang="en" dir="ltr" class="mw-content-ltr">Reference Previews and Page Previews next to each other.</span>]] '''操作''' * 脚注の上にマウスポインターを置くことでプレビューを見ることができます。 * 脚注をクリックすることで、プレビューがないときと同じように、脚注一覧へ飛ぶことができます。 * 短い脚注の場合は、プレビューのサイズも小さくなります。 * プレビューの最大サイズよりも脚注が長い場合は、プレビュー内でスクロールすることができます。 * 脚注内の外部リンクは新しいタブで開きます。 この機能は、JavaScriptを使用しています。JavaScriptが有効になってない場合は、脚注マークにマウスポインターを当てても何も起こりません。 <div lang="en" dir="ltr" class="mw-content-ltr"> === Opt-out feature === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Reference Previews will be '''activated by default for everyone''' (logged-in users, logged-out/anonymous users, readers of a wiki). </div> * <span lang="en" dir="ltr" class="mw-content-ltr">You can toggle them off under the Appearance tab in your preferences.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">You can also open this preference tab directly by clicking on the cog wheel in the pop-up.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Anonymous users/logged-out users/readers''' can turn the previews off by clicking the cog wheel and toggling the setting. This saves the preference via a cookie. They can be turned back on using the “Edit preview settings” link in the website footer.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Please note:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Reference Tooltips or Navigation Popups '''gadget''' – either because it’s a default gadget on your wiki or because you enabled it individually – you won’t see Reference Previews.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">For wikis where Reference Previews are still a '''beta feature''', you need to activate it in your beta settings.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Exposed reference types === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> At the top of each pop-up, Reference Previews prominently indicate what kind of source is being referenced. We currently define six reference types: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Reference (generic)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Web reference</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Journal reference</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Book reference</span> * <span lang="en" dir="ltr" class="mw-content-ltr">News reference</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Note</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === How to assign a reference type to your reference === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Each reference is defined by CSS classes, e.g., <syntaxhighlight lang=html inline><cite class="journal"></syntaxhighlight> for journal references. These classes are set in the {{tag|cite|open}} element in a reference's content. References without cite tags and classes (e.g., plain {{tag|ref|open}} tags) are displayed as "Reference". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To assign a reference type: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">The '''easiest way''' is to use a citation template that includes the <code>cite</code> class. The English <code>cite</code> templates, for [[:en:Template:Cite web|example this one]], specify the <code>cite</code> class already, and derivations of these templates are used in many wikis. Other templates can also be updated to do so.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">If you're not using templates to add references, another option is to add a {{tag|cite|open}} class directly into a {{tag|cite|open}} tag, like so: <code><nowiki><ref><cite class="book">reference content</cite></ref></nowiki></code>.</span> == 展開ロードマップ == * {{tick}} test.wikipedia.org (<code>testwiki</code>): {{ymd|2019|2|28}} * ベータ機能の展開: ** {{tick}} {{int|project-localized-name-dewiki}}: {{ymd|2019|4|4}} ** {{tick}} {{int|project-localized-name-arwiki}}: {{ymd|2019|4|4}} ** [[mw:Extension:Popups|ポップアップ]]拡張機能を使用するすべてのウィキ (すべてのウィキペディアと英語版、ヘブライ語版、中国語版ウィキボヤージュ) {{ymd|2019|10|24}} * <span lang="en" dir="ltr" class="mw-content-ltr">default feature:</span> ** {{tick}} {{int|project-localized-name-dewiki}}, {{int|project-localized-name-rowiki}}, {{int|project-localized-name-etwiki}}, {{int|project-localized-name-euwiki}}, {{int|project-localized-name-arwiki}}, {{int|project-localized-name-hewiki}}, {{int|project-localized-name-guwiki}}, {{int|project-localized-name-fiwiki}}: {{ymd|2021|5|6}} ** {{tick}} {{int|project-localized-name-mrwiki}}: {{ymd|2021|5|10}} == リンク == * [[Extension:Popups|extension manual on MediaWiki.org]] 拡張機能のマニュアル 出典プレビュー * [https://phabricator.wikimedia.org/tag/reference_previews/ project board on Phabricator] プロジェクトのボード * [[m:WMDE Technical Wishes/ReferencePreviews|main project page on Meta]] プロジェクトのメインページ * [[Help talk:Reference Previews|central feedback page on MediaWiki.org]] フィードバックの受付 ページ プレビュー * [[Page_Previews|メインのプロジェクトページ、MediaWiki.org]] * [[Talk:Page_Previews|メインのフィードバック投稿先、MediaWiki.org]] == 翻訳をお手伝いください == [[translatewiki:Special:Translate/ext-popups|この機能のソフトウェアメッセージ]]はtranslate wikiで翻訳の対象になっています。できる範囲でお手伝いをお願いします! [[Category:Help{{#translation:}}| ]] [[Category:Beta Features{{#translation:}}]] o3xajmbd7ui3ff54x8qo17anbg99tdc Translations:Manual:Installation guide/66/cs 1198 917786 5386465 4994741 2022-07-28T14:26:17Z ENeRZet 17359278 wikitext text/x-wiki Hostingové služby, které poskytují automatickou instalaci aplikací, jako je MediaWiki, mohou nabízet zastaralé verze nebo mít jiné problémy. Pokud narazíte na problémy, ''neznamená to'', že nemůžete nainstalovat MediaWiki. To znamená, že byste měli nainstalovat MediaWiki ručně. d9prmpiuq96lyqo873wg989fmmhjvql Manual:Combating spam/fr 100 923608 5387474 5255700 2022-07-28T22:40:17Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Comme tous les sites Web dynamiques actuels, les wikis constituent une cible courante pour les spammeurs souhaitant promouvoir des produits ou des sites Web. MediaWiki propose un certain nombre de fonctionnalités conçues pour [[Special:MyLanguage/Manual:Combating vandalism|lutter contre le vandalisme en général]]. <span lang="en" dir="ltr" class="mw-content-ltr">On this page we deal specifically with [[m:Wiki spam|wiki spam]], which is often automated.</span> == Résumé == Les outils couramment utilisés pour lutter contre le spam de wikis appartiennent généralement aux catégories suivantes: * Nécessité d'une connexion et/ou un CAPTCHA pour certaines opérations, telles que des modifications, l'ajout de liens externes ou la création d'un nouvel utilisateur. * Blocage des modifications des adresses IP connues figurant sur la liste noire ou des adresses IP exécutant des proxys ouverts * Blocage des modifications servant ajouter des mots-clés ou des liens externes spécifiques non désirés * Blocage de modèles de nom d'utilisateur et de titre de page spécifiques couramment utilisés par les spambots * Blocage des modifications apportées par de nouveaux utilisateurs ou anonymes à des pages spécifiques souvent ciblées <div lang="en" dir="ltr" class="mw-content-ltr"> * Whitelisting known-good editors (such as admins, regular contributors) while placing restrictions on new or anonymous users </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Cleanup scripts or bulk deletion ({{ll|Extension:Nuke}}) of existing posts from recently-banned spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Note that many of these features are not activated by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</span> <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It helps to raise the bar a little.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> == Solutions de test rapide à essayer en premier == <span lang="en" dir="ltr" class="mw-content-ltr">Fighting spam should not be too hard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to quickly and drastically reduce spam, try these few steps first.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install the [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] extension to block known spammer IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> == Bases de la configuration antispam == {{anchor|CAPTCHA}} === Les CAPTCHAs === <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * all edits </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * edits adding new, unrecognized external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * user registration </div> <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. == Routines antispam : les mesures adaptées == <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} === Protection individuelle des pages === <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. == Filtre anti-abus == <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> === Liste noire des pourriels === <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> === Serveurs mandataires ouverts === <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> == Mesures du noyau == <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> === Modifications de la configuration Apache === <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> ==== Filtrage par agent utilisateur ==== <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> ==== Empêcher des contrevenants bloqués d'utiliser des ressources ==== <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> === Listes noires d'adresses IP === <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> ==== Utilisation du CPU et surcharge ==== <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> ==== DNSBL ==== <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. ==== Mauvais comportement et pot de miel du projet ==== <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> ==== Pots de miel, DNS BLs et HTTP BLs ==== <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> ==== Mais qu'est-ce ceci par rapport aux pots de miel ? ==== <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> ==== Davantage de liste d'adresses IP de serveurs mandataires et de robots de pourriel ==== <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # Ajoutez une ligne à {{ll|Manual:LocalSettings.php|LocalSettings.php}} pour définir : <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> == Et si le pourriel gagnait la bataille ? == <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> == Autres idées == <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> == Voir aussi == *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === Extensions === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} ==== Fourni avec l'installateur ==== <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === Paramètres === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External links === </div> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] jfzbhr34jutnlf5zyrm1b5gkihrjsuy Wikimedia Product/id 0 925627 5387580 5358198 2022-07-29T03:25:51Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=Staf '''Audiens Wikimedia''' [[:foundation:Staff and contractors|dipekerjakan oleh Yayasan Wikimedia]] untuk membangun, meningkatkan dan merawat infrastruktur [[m:Special:MyLanguage/Wikimedia projects|situs-situs Wikimedia]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Kontributor-kontributor</span>]] * [[Readers|<span style="color:#2aa198">Pembaca</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Seluruh Produk == * [[Special:MyLanguage/Product Principles|Prinsip Audiens]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (sebelumnya: [[Special:MyLanguage/Technical Collaboration Guidance|Pemanduan Kolaborasi Teknis]]) * [[Special:MyLanguage/Design/Statement of purpose|Pernyataan Desain Tujuan]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|Informasi penelitian dan data untuk produk]] * [[Special:MyLanguage/Wikimedia Research/Showcase|Pameran Penelitian Bulanan]] === Program === * [[m:Special:MyLanguage/Communications/Audience research|Penelitian Audiens]] * [[m:Special:MyLanguage/Community health initiative|Inisiatif Kesehatan Komunitas]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|Pengalaman Pengguna Baru]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Pembaca Baru]] — Penelitian yang sedang berlangsung yang berfokus dalam memahami potensi pembaca Wikimedia di negara-negara dimana akses ke internet berkembang pesat. (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|Data Terstruktur di Commons]] === Halaman proyek === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|Tujuan Rencana Tahunan: Konten Baru]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|Kontribusi Seluler Lanjutan]] * [[Special:MyLanguage/Android editing features|Fitur Penyunting Android]] * [[Special:MyLanguage/Content translation/V2|Terjemahan Konten, V2]] * [[Special:MyLanguage/Growth/Growth team updates|Pertumbuhan]] * [[Special:MyLanguage/Language tools|Memperbaiki Terjemahkan Ekstensi dan proses Terjemahkan Wiki]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|Penyunting iOS]] * [[Special:MyLanguage/VisualEditor on mobile|Penyuntingan peranti bergerak berbasis visual]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''Tujuan Rencana Tahunan: Penggunaan Data yang Lebih Baik''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|Penggunaan Data yang lebih baik]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|Pengumpulan data: Instrumentasi]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|Pelayanan laporan]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''Tujuan Rencana Tahunan: Daftar Keinginan Komunitas''']] * [[m:Special:MyLanguage/Community Tech#Projects|Daftar keinginan]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|Dukungan untuk kelompok pengguna kecil]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|Peralatan teknologi untuk penyelenggara program dan kegiatan]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''Tujuan Rencana Tahunan: Peralatan Anti-Pelecehan''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|Sistem pelaporan]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''Tujuan Rencana Tahunan: Wikidata''']] '''Lainnya:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 Tujuan Rencana Tahunan: Evolusi Platform CDP] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|Investasi dalam arsitektur bagian depan MobileFrontend & MinervaNeue]] ** [[Special:MyLanguage/Parsing/Parser Unification|Unifikasi parser]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|TemplateStyles]] * [[m:Special:MyLanguage/Movement Organizers|Penelitian Penyelenggara Gerakan]] (2019) == Metrik == [[Special:MyLanguage/Product Analytics|Analitika Produk]] mencatat sekumpulan metrik kunci yang dirancang untuk memberikan gambaran tingkat tinggi dari keadaan gerakan. [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|Laporan bulanan mengenai metrik kunci mencatat keadaan umum dari gerakan Wikimedia.]] == Tim-tim produk == Sebuah tim Produk mencakup satu set fitur yang dikembangkan berdasarkan kebutuhan dan aliran pengguna yang spesifik. === Kontributor-kontributor === Kami membangun perkakas yang inklusif, kolaboratif untuk membuat dan menyunting pengetahuan bebas. * Papan kerja Phabricator: [[phab:tag/contributors-team/|#Contributors-Team]] (jarang digunakan) * Halaman: [[Special:MyLanguage/Contributors|Kontributor-kontributor]] * Tim: ====== Peralatan Anti-Pelecehan ====== * Papan kerja Phabricator: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Halaman: [[Special:MyLanguage/Anti-Harassment Tools|Peralatan Anti-Pelecehan]] ====== Komunitas Teknis ====== * [[phab:project/board/1274/|Papan Phabricator]] * Halaman: [[m:Special:MyLanguage/Community Tech|Komunitas Teknis]] ====== Penyuntingan ====== * Papan kerja Phabricator: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Halaman: [[Special:MyLanguage/Editing team|Tim penyuntingan]] ====== Pertumbuhan ====== * Papan kerja Phabricator: [[phab:project/board/1114/|#Growth-Team]] * Halaman: [[Special:MyLanguage/Growth|Pertumbuhan]] ====== Bahasa ====== * Papan kerja Phabricator: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Halaman: [[Special:MyLanguage/Wikimedia Language engineering|Teknis Bahasa Wikimedia]] === Pembaca === Kami membangun pengalaman membaca dan belajar untuk semua pengetahuan. * Halaman: [[Special:MyLanguage/Readers|Pembaca]] * Papan kerja Phabricator: [https://phabricator.wikimedia.org/tag/reading/ #reading] * Tim: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|Penguraian]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|Infrastruktur Produk]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|Web]] ====== * [[Reading/Component responsibility|Tangungjawab kode membaca]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|Pembacaan halaman bulanan, Mei 2013–Januari 2019. File:Wikimedia pageviews year-over-year comparison (since May 2013).png|Perbandingan total jumlah tampilan halaman per tahun, Mei 2013–Februari 2019. File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|Perbandingan jumlah tampilan desktop halaman per tahun, Mei 2013–Februari 2019. File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|Perbandingan jumlah tampilan mobile halaman per tahun, Mei 2013–Februari 2019. </gallery> === Manajemen Program Teknis === Kami berdedikasi untuk memandu proses pengantaran dan memfasilitasi kesehatan tim melalui praktik yang benar. Halaman: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|Manajemen Program Teknis]] Pimpinan: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === Desain Produk === Kami membuat berbagi semua pengetahuan manusia menjadi mudah dan menyenangkan. Bagi semua orang. Halaman: [[Special:MyLanguage/Design#Product Design|Desain Produk]] Direktur: [[User:MNovotny_(WMF)|Margeigh Novotny]] === Analitika Produk === Kami memberikan saran berdasarkan hasil analisis, mendukung praktik data yang etis, dan mengajarkan topik-topik mengenai data dan statistik. Halaman: [[Special:MyLanguage/Product Analytics|Analitika Produk]] Pimpinan: Kate Zimmerman === Strategi Desain Produk === <!--''[masukkan teks intro]''--> Halaman: [[Special:MyLanguage/Design#Design Strategy|Strategi Desain Produk]] Pimpinan: Margeigh Novotny === Wikidata === Wikidata adalah sebuah basis pengetahuan bebas dan terbuka yang bisa dibaca dan disunting oleh manusia dan mesin. Proyek ini dirawat oleh departemen Rekayasa & Pengembangan Perangkat Lunak di [[WMDE Engineering|Wikimedia Deutschland]]. * Halaman: [[d:Wikidata:Main Page|Wikidata]] * Pimpinan: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Papan kerja & bug Phabricator: [[phab:project/profile/71/|#wikidata]] * Daftar Diskusi: wikidata@lists.wikimedia.org {|class="wikitable" |+ Tujuan Tim Wikidata |- !scope="row"| Tahun Fiskal 2017 WMDE | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q1: Januari–Maret 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q2: April–Juni] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q3: Juli–September] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q4: Oktober–Desember] |- !scope="row"| Tahun Fiskal 2016 WMDE | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q1: Januari–Maret 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q2: April–Juni] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q3: Juli–September] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q4: Oktober–Desember] |} == Tujuan-tujuan == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: Juli – September 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: Oktober – Desember 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: Januari – Maret 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: April – Juni 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: Juli–September 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: Oktober–Desember 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: Januari–Maret 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: April – Juni 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: Juli – September 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: Oktober–Desember 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: Januari – Maret 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: April–Juni 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: Juli–September 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: Oktober–Desember 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: Januari–Maret 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: April–Juni 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: Juli–September 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: Oktober–Desember 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: Januari–Maret 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: April–Juni 2016]] |} == Peta jalan rutin == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|Rencana rutin untuk Produk 2018-2019]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|Rencana rutin untuk Produk 2017–2018]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|Rencana Rutin untuk Produk 2016–2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|Iktisar Produk 2016]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|Kajian Produk & Teknologi 2015]] [[Category:WMF Projects{{#translation:}}]] qllghhs1m47nn13u0aijuttmb4jic4i Wikibase/id 0 934571 5387521 5383917 2022-07-29T02:22:39Z Harditaher 2685976 Created page with "Selamat datang di halaman utama '''Wikibase'''" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' <span lang="en" dir="ltr" class="mw-content-ltr">Here you'll find documentation and resources for the open-source software suite created by [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] that you can use to create collaborative knowledge bases -- and open the door to the Linked Open Data web.</span> {{ start tab | tab-1 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Getting started</span></font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Using Wikibase</span></font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Reference</span></font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=<span lang="en" dir="ltr" class="mw-content-ltr">What is Wikibase?</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">A brief introduction to this powerful software for managing structured data.</span> }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|<span lang="en" dir="ltr" class="mw-content-ltr">Should I use Wikibase?</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 6e5641j9ogqjopdrnxhojymqgh53o49 5387523 5387521 2022-07-29T02:24:06Z Harditaher 2685976 Created page with "Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh $1 yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut." wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Getting started</span></font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Using Wikibase</span></font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Reference</span></font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=<span lang="en" dir="ltr" class="mw-content-ltr">What is Wikibase?</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">A brief introduction to this powerful software for managing structured data.</span> }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|<span lang="en" dir="ltr" class="mw-content-ltr">Should I use Wikibase?</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] ho0kugjuutudi6hbenwu58u26m19rcc 5387525 5387523 2022-07-29T02:24:33Z Harditaher 2685976 Created page with "Memulai" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Using Wikibase</span></font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Reference</span></font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=<span lang="en" dir="ltr" class="mw-content-ltr">What is Wikibase?</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">A brief introduction to this powerful software for managing structured data.</span> }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|<span lang="en" dir="ltr" class="mw-content-ltr">Should I use Wikibase?</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 97dt8mxv4wftkpev7tc5ru1xjvbt59s 5387527 5387525 2022-07-29T02:24:41Z Harditaher 2685976 Created page with "== Menggunakan Wikibase ==" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2"><span lang="en" dir="ltr" class="mw-content-ltr">Reference</span></font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=<span lang="en" dir="ltr" class="mw-content-ltr">What is Wikibase?</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">A brief introduction to this powerful software for managing structured data.</span> }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|<span lang="en" dir="ltr" class="mw-content-ltr">Should I use Wikibase?</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 1ysg3hjbcx7vs5kdxnc0enedhrwhxux 5387529 5387527 2022-07-29T02:24:44Z Harditaher 2685976 Created page with "Referensi" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=<span lang="en" dir="ltr" class="mw-content-ltr">What is Wikibase?</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">A brief introduction to this powerful software for managing structured data.</span> }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|<span lang="en" dir="ltr" class="mw-content-ltr">Should I use Wikibase?</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 6hfw1x0xrkpemnevl9f3ggs1u60dk7i 5387531 5387529 2022-07-29T02:24:55Z Harditaher 2685976 Created page with "Apa itu Wikibase?" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">A brief introduction to this powerful software for managing structured data.</span> }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|<span lang="en" dir="ltr" class="mw-content-ltr">Should I use Wikibase?</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] j5fg71d4z3yyk2mjo825fp80pzxkv1m 5387533 5387531 2022-07-29T02:25:25Z Harditaher 2685976 Created page with "Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur." wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|<span lang="en" dir="ltr" class="mw-content-ltr">Should I use Wikibase?</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 1pucf6m88rorfy4uazz7bqhkxuuae03 5387535 5387533 2022-07-29T02:25:39Z Harditaher 2685976 Created page with "Haruskan saya menggunakan Wikibase?" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskan saya menggunakan Wikibase?]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] kmeegf8d0o0qwueyliqurgcqpq0p2uo 5387537 5387535 2022-07-29T02:26:23Z Harditaher 2685976 wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Answers the question "Should I use Wikibase?" using English words and punctuation.</span> }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 840dnvpsr63p9mwkx1yaw4s7441mdtl 5387539 5387537 2022-07-29T02:26:36Z Harditaher 2685976 Created page with "Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris." wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|<span lang="en" dir="ltr" class="mw-content-ltr">Case studies</span>]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] eqebnmy15mdy6rjal2naza4h2hgk31b 5387541 5387539 2022-07-29T02:26:41Z Harditaher 2685976 Created page with "Studi Kasus:" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = <span lang="en" dir="ltr" class="mw-content-ltr">Some useful examples of who's currently using Wikibase and how.</span> }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 0vwmlztksl5z4t8ed1ntclv8l5havlj 5387543 5387541 2022-07-29T02:27:04Z Harditaher 2685976 Created page with "Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya." wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=<span lang="en" dir="ltr" class="mw-content-ltr">Quick start</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] bdrjttsz514h1sdi4adgkb5nzd1364y 5387545 5387543 2022-07-29T02:27:33Z Harditaher 2685976 Created page with "Memulai cepat" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=Memulai cepat}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Dive into Wikibase in no time!</span> }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] jjnt03gkgv8pxwujm0z9bsim6pv9i7s 5387547 5387545 2022-07-29T02:27:58Z Harditaher 2685976 Created page with "Jelajahi Wikibase dalam waktu singkat!" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=Memulai cepat}} |content = Jelajahi Wikibase dalam waktu singkat! }} {{Colored box |title = {{ll|Wikibase/FAQ|2=<span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] i7vcyqg9wo0fblpqtn1m6g8iyx0rjyo 5387549 5387547 2022-07-29T02:28:01Z Harditaher 2685976 Created page with "Pertanyaan umum" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=Memulai cepat}} |content = Jelajahi Wikibase dalam waktu singkat! }} {{Colored box |title = {{ll|Wikibase/FAQ|2=Pertanyaan umum}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Frequently asked questions about Wikibase.</span> }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 3375q3l6xmd7lpb5zoyrmt7trpoh8y7 5387551 5387549 2022-07-29T02:28:15Z Harditaher 2685976 Created page with "'''Pertanyaan yang sering diajukan (FAQ)''' tentang penggunaan Wikibase." wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=Memulai cepat}} |content = Jelajahi Wikibase dalam waktu singkat! }} {{Colored box |title = {{ll|Wikibase/FAQ|2=Pertanyaan umum}} |content = '''Pertanyaan yang sering diajukan (FAQ)''' tentang penggunaan Wikibase. }} {{Colored box |title = {{ll|Wikibase/Install|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 6g8dtl16b72y087x0whhjxphr3q44ov 5387553 5387551 2022-07-29T02:28:22Z Harditaher 2685976 Created page with "Instal" wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=Memulai cepat}} |content = Jelajahi Wikibase dalam waktu singkat! }} {{Colored box |title = {{ll|Wikibase/FAQ|2=Pertanyaan umum}} |content = '''Pertanyaan yang sering diajukan (FAQ)''' tentang penggunaan Wikibase. }} {{Colored box |title = {{ll|Wikibase/Install|2=Instal}} |content = <span lang="en" dir="ltr" class="mw-content-ltr">Set up Wikibase on your own system.</span> }} }} [[Category:Wikibase{{#translation:}}| ]] 3027mjtagdwae1vuh7uxahdzg5mu1nn 5387555 5387553 2022-07-29T02:28:55Z Harditaher 2685976 Created page with "Menyiapkan Wikibase di sistem Anda." wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">== Menggunakan Wikibase ==</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=Memulai cepat}} |content = Jelajahi Wikibase dalam waktu singkat! }} {{Colored box |title = {{ll|Wikibase/FAQ|2=Pertanyaan umum}} |content = '''Pertanyaan yang sering diajukan (FAQ)''' tentang penggunaan Wikibase. }} {{Colored box |title = {{ll|Wikibase/Install|2=Instal}} |content = Menyiapkan Wikibase di sistem Anda. }} }} [[Category:Wikibase{{#translation:}}| ]] 0l1tmss3f8p3enmpnrnvtme1qzenszx 5387557 5387555 2022-07-29T02:29:58Z Harditaher 2685976 wikitext text/x-wiki <languages/> Selamat datang di halaman utama '''Wikibase''' Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh [[meta:Wikimedia Deutschland|Wikimedia Deutschland]] yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. {{ start tab | tab-1 = <font size="+2">Memulai</font> | link-1 = Special:MyLanguage/Wikibase | tab-2 = <font size="+2">Menggunakan Wikibase</font> | link-2 = Special:MyLanguage/Wikibase/Using_Wikibase | tab-3 = <font size="+2">Referensi</font> | link-3 = Special:MyLanguage/Wikibase/Reference | border = 1px solid #778899 | off tab color = #FFFFFF | on tab color = | rounding = 1em | tab alignment = center }} {{ContentGrid |content= {{Colored box |title = {{ll|Wikibase/What is Wikibase|2=Apa itu Wikibase?}} |content = Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. }} <!-- {{Colored box |title = [[Wikibase/Should_I_use_Wikibase|Haruskah saya menggunakan Wikibase?]] |content = Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. }} {{Colored box |title = [[Wikibase/Case_studies|Studi Kasus:]] |content = Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. }} --> {{Colored box |title = {{ll|Wikibase/Quick start|2=Memulai cepat}} |content = Jelajahi Wikibase dalam waktu singkat! }} {{Colored box |title = {{ll|Wikibase/FAQ|2=Pertanyaan umum}} |content = '''Pertanyaan yang sering diajukan (FAQ)''' tentang penggunaan Wikibase. }} {{Colored box |title = {{ll|Wikibase/Install|2=Instal}} |content = Menyiapkan Wikibase di sistem Anda. }} }} [[Category:Wikibase{{#translation:}}| ]] ioain4wuipfatg4jzh008dfg5pu2l4w Wikimedia Product/my 0 945510 5387586 5358205 2022-07-29T03:25:56Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">ပံ့ပိုးသူများ</span>]] * [[Readers|<span style="color:#2aa198">စာဖတ်သူများ</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === ပံ့ပိုးသူများ === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span class="mw-translate-fuzzy">စာမျက်နှာ</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * အသင်းများ ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span class="mw-translate-fuzzy">စာမျက်နှာ</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span class="mw-translate-fuzzy">စာမျက်နှာ</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span class="mw-translate-fuzzy">စာမျက်နှာ</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span class="mw-translate-fuzzy">စာမျက်နှာ</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * စာမျက်နှာ [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === စာဖတ်သူများ === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * စာမျက်နှာ [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span class="mw-translate-fuzzy">အသင်းများ</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === ဝီကီဒေတာ === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span class="mw-translate-fuzzy">စာမျက်နှာ</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Goals</span> == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| ၂၀၁၈-၂၀၁၉ | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| ၂၀၁၇-၂၀၁၈ | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| ၂၀၁၆-၂၀၁၇ | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| ၂၀၁၅-၂၀၁၆ | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] ri7kd6claxkvqa2lq7gnhse0vqisa6r Wikidata Bridge/Development/de 0 955711 5386755 4664664 2022-07-28T18:54:45Z ThisCarthing 17456337 Created page with "Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen." wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. <span class="mw-translate-fuzzy">Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In order to make sure that we’re building a tool that is answering editors’ needs, we’re using agile methods in our development process.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We don’t start with a fixed idea of the tool we want to deliver: we will build it together with the communities, based on feedback loops that we will regularly organize.</span> Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** The infoboxes maintainers will need to [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox|adapt the templates]] to get the new feature. If it’s not done, the infoboxes will continue to work as they are currently, so the template builders make the choice if they want to enable editing Wikidata’s data or not </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** On adapted infoboxes, a link or icon (for example “edit Wikidata’s data”) will open the editing interface </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On Wikidata </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A tag for edits coming from Wikidata Bridge will be added </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** More Wikipedia editors will start editing Wikidata </div> eq2muce0byqtiy61tf7lxgr1g2qfr4f 5386757 5386755 2022-07-28T18:55:02Z ThisCarthing 17456337 Created page with "Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren." wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. <span class="mw-translate-fuzzy">Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In order to make sure that we’re building a tool that is answering editors’ needs, we’re using agile methods in our development process.</span> Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** The infoboxes maintainers will need to [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox|adapt the templates]] to get the new feature. If it’s not done, the infoboxes will continue to work as they are currently, so the template builders make the choice if they want to enable editing Wikidata’s data or not </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** On adapted infoboxes, a link or icon (for example “edit Wikidata’s data”) will open the editing interface </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On Wikidata </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A tag for edits coming from Wikidata Bridge will be added </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** More Wikipedia editors will start editing Wikidata </div> k9mea6nmnqolearza3i88530ri5wgip 5386759 5386757 2022-07-28T18:55:18Z ThisCarthing 17456337 Replaced content with "'''Wie arbeiten wir?'''" wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' <span lang="en" dir="ltr" class="mw-content-ltr">In order to make sure that we’re building a tool that is answering editors’ needs, we’re using agile methods in our development process.</span> Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** The infoboxes maintainers will need to [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox|adapt the templates]] to get the new feature. If it’s not done, the infoboxes will continue to work as they are currently, so the template builders make the choice if they want to enable editing Wikidata’s data or not </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** On adapted infoboxes, a link or icon (for example “edit Wikidata’s data”) will open the editing interface </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On Wikidata </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A tag for edits coming from Wikidata Bridge will be added </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** More Wikipedia editors will start editing Wikidata </div> 92fl6uedsj71l1x4c1sdzj3d10abc08 5386761 5386759 2022-07-28T18:55:22Z ThisCarthing 17456337 Created page with "Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden." wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** The infoboxes maintainers will need to [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox|adapt the templates]] to get the new feature. If it’s not done, the infoboxes will continue to work as they are currently, so the template builders make the choice if they want to enable editing Wikidata’s data or not </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** On adapted infoboxes, a link or icon (for example “edit Wikidata’s data”) will open the editing interface </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On Wikidata </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A tag for edits coming from Wikidata Bridge will be added </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** More Wikipedia editors will start editing Wikidata </div> 3ao3lzoy6fnptcubxdtze6gc7502vru 5386763 5386761 2022-07-28T18:57:53Z ThisCarthing 17456337 start of splitting wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** The infoboxes maintainers will need to [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox|adapt the templates]] to get the new feature. If it’s not done, the infoboxes will continue to work as they are currently, so the template builders make the choice if they want to enable editing Wikidata’s data or not </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** On adapted infoboxes, a link or icon (for example “edit Wikidata’s data”) will open the editing interface </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On Wikidata </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A tag for edits coming from Wikidata Bridge will be added </div> ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten 6c2rpcvxvgl7ujvslq29fclhiwb4rwf 5386765 5386763 2022-07-28T18:58:05Z ThisCarthing 17456337 Created page with "** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt" wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** The infoboxes maintainers will need to [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox|adapt the templates]] to get the new feature. If it’s not done, the infoboxes will continue to work as they are currently, so the template builders make the choice if they want to enable editing Wikidata’s data or not </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** On adapted infoboxes, a link or icon (for example “edit Wikidata’s data”) will open the editing interface </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On Wikidata </div> ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten 30iasdtyk8zqyy4jjbcfogapzhxy76n 5386767 5386765 2022-07-28T18:58:16Z ThisCarthing 17456337 Created page with "* In Wikidata" wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** The infoboxes maintainers will need to [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox|adapt the templates]] to get the new feature. If it’s not done, the infoboxes will continue to work as they are currently, so the template builders make the choice if they want to enable editing Wikidata’s data or not </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** On adapted infoboxes, a link or icon (for example “edit Wikidata’s data”) will open the editing interface </div> * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten 1peyl3i71nq5iixn3b4xsohgtanmlbn 5386769 5386767 2022-07-28T18:58:33Z ThisCarthing 17456337 Created page with "** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet" wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** The infoboxes maintainers will need to [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox|adapt the templates]] to get the new feature. If it’s not done, the infoboxes will continue to work as they are currently, so the template builders make the choice if they want to enable editing Wikidata’s data or not </div> ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten n16og54ptwvgmbmayk6ro999ec85e4v 5386771 5386769 2022-07-28T18:59:49Z ThisCarthing 17456337 Created page with "** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht" wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * On infoboxes </div> ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten ps477odptbqals0rzzho0e4cv7c83id 5386773 5386771 2022-07-28T18:59:57Z ThisCarthing 17456337 Created page with "* In Infoboxen" wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** A new feature of the Wikibase Client extension will be enabled </div> * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten f55zpkq4bbljdyy605ia4w1ti9pbkka 5386775 5386773 2022-07-28T19:00:06Z ThisCarthing 17456337 Created page with "** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert" wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== <div class="mw-translate-fuzzy"> * Änderungen in Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * Änderungen in Infoboxen ** Die Betreuer der Infoboxen müssen die Vorlagen anpassen, um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * Änderungen in Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten </div> ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten hk9zal6inq0d9sl1l135qbq687q6otp 5386777 5386775 2022-07-28T19:00:14Z ThisCarthing 17456337 finishing up the split wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ====== Was vorerst nicht geplant ist ====== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== * In Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten fi630id5jvjz1id34pb4oontv5eljnq 5386780 5386777 2022-07-28T19:00:48Z ThisCarthing 17456337 wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ===Was nicht Teil des Projekts ist=== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== * In Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten eh69nyjad8qklgz6y3s0clf8qde6qfv 5386782 5386780 2022-07-28T19:00:58Z ThisCarthing 17456337 wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ===Was nicht Teil des Projekts ist=== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ====Was wird sich ändern?==== * In Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten qo84r7agf6ca3y3nlc8elw2638p4f2m 5386784 5386782 2022-07-28T19:01:05Z ThisCarthing 17456337 wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ====== Geplante Funktionen ====== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ===Was nicht Teil des Projekts ist=== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ==Was wird sich ändern?== * In Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten kgfc1npw6afdch6d4ikyjqu9ma0npkv 5386786 5386784 2022-07-28T19:01:21Z ThisCarthing 17456337 wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==== Wie wird es funktionieren? ==== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ===Geplante Funktionen für die nächsten Schritte=== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ===Was nicht Teil des Projekts ist=== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ==Was wird sich ändern?== * In Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten kr9n6akoibnlxeh4n5a65geg59rmhst 5386788 5386786 2022-07-28T19:01:29Z ThisCarthing 17456337 wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==== Was wollen wir erreichen? ==== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==Wie wird es funktionieren?== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ===Geplante Funktionen für die nächsten Schritte=== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ===Was nicht Teil des Projekts ist=== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ==Was wird sich ändern?== * In Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten hq0mtq2qvpnepyzy1aj5pc9mq201n90 5386790 5386788 2022-07-28T19:02:06Z ThisCarthing 17456337 wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. <span lang="en" dir="ltr" class="mw-content-ltr">The first version will not necessarily have all of the features you want, but it will keep evolving.</span> ==Was ist unser Ziel?== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==Wie wird es funktionieren?== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ===Geplante Funktionen für die nächsten Schritte=== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ===Was nicht Teil des Projekts ist=== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ==Was wird sich ändern?== * In Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten hf2g8sn1o9c5wrep1bba0uvbmm4a6nn 5386793 5386790 2022-07-28T19:03:01Z ThisCarthing 17456337 Created page with "Die erste Version wird nicht unbedingt alle Funktionen haben, die du möchtest, aber es wird sich weiterentwickeln." wikitext text/x-wiki <languages /> {{Wikidata Bridge/Header}} '''Wer arbeitet an dem Projekt?''' Der erste Teil dieser Funktion wird vom Wikidata-Entwicklerteam bei Wikimedia Deutschland entwickelt (einschließlich: Organisationsteam, Produktmanager, UX-Designer, Community-Kommunikation). In Zukunft könnte die Wikimedia Foundation auch mitarbeiten, wenn es um die Integration in Wikipedia geht. '''Wie arbeiten wir?''' Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. Die erste Version wird nicht unbedingt alle Funktionen haben, die du möchtest, aber es wird sich weiterentwickeln. ==Was ist unser Ziel?== Hier sind die Ziele, die wir erreichen wollen: * Reduzierung der veralteten Daten in den Infoboxen * Reduzierung der (ungewollt) widersprüchlichen Daten in Infoboxen verschiedener Projekte * Höhere Datenqualität auf Wikidata * Mehr Daten für Leser in allen Wikis (besonders in kleineren) * Insgesamt sind weniger Daten pro Editor in den Wikimedia-Projekten zu pflegen * Dafür sorgen, dass Wikidata für Autoren von anderen Wikimedia-Projekten präsenter wird ==Wie wird es funktionieren?== [[File:18.06.19 - Frame 1.1.png|thumb|Screenshot vom aktuellen Prototyp. Es öffnet sich beim Bearbeiten ein Dialogfeld.]] Wir möchten eine Benutzeroberfläche erstellen, auf die über eine Infobox-Vorlage in Wikipedia zugegriffen werden kann (z. B. über einen in der Infobox befindlichen Link zum Bearbeiten), mit der die in Wikidata gespeicherten und in dieser Infobox angezeigten Werte bearbeitet werden können. ====== Geplante Funktionen für die erste Version (minimale Funktionsfähigkeit) ====== * Möglichkeit, einen lokalen Editor in Wikipedia zu öffnen, mit dem Wikidata-Werte bearbeitet werden können * Bearbeiten eines einfachen Werts aus Wikidata (z. B. Datum oder Anzahl der Einwohner, jedoch keinen Wert, der mit einem anderen Artikel verknüpft ist) * Möglichkeit unterschiedlicher Zugänge, je nachdem, ob Autoren den Wert entweder bearbeiten (weil er in Wikidata falsch eingegeben wurde) oder aktualisieren möchten (z. B. weil sich die Einwohnerzahl geändert hat). ===Geplante Funktionen für die nächsten Schritte=== * Bearbeiten von Werten, die einen beliebigen Datentyp haben (z. B. Bürgermeister einer Stadt) * Einfacheres Umschalten zwischen lokalen Werten und Werten aus Wikidata * Bearbeiten von lokalen Werten und Werten, die aus Wikidata stammen, und zwar in derselben Oberfläche, die im Visual Editor integriert ist * Hinzufügen oder Bearbeiten von Werten für eine Eigenschaft, die nicht bereits in der Infobox verwendet wird * Bearbeiten von Werten für andere Elemente als die, die über einen Sitelink verbunden sind ===Was nicht Teil des Projekts ist=== Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen ==Was wird sich ändern?== * In Wikipedias und anderen Projekten ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert * In Infoboxen ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet * In Wikidata ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten 57fpx9nabfi5tlejqwm3epc1wfkbq7g Translations:Wikidata Bridge/Development/2/de 1198 955713 5386758 3316947 2022-07-28T18:55:17Z ThisCarthing 17456337 Replaced content with "'''Wie arbeiten wir?'''" wikitext text/x-wiki '''Wie arbeiten wir?''' 3nzeqhe5wjhgsujcokrwje1faka2f4d Translations:Wikidata Bridge/Development/3/de 1198 955714 5386789 3316951 2022-07-28T19:01:46Z ThisCarthing 17456337 wikitext text/x-wiki Was ist unser Ziel? 6y344e7mjuo98m1pcvetor2p6fdjetl Translations:Wikidata Bridge/Development/5/de 1198 955716 5386787 3316957 2022-07-28T19:01:28Z ThisCarthing 17456337 wikitext text/x-wiki Wie wird es funktionieren? khfwbw01otkk923hagjw2d8m08tab3m Translations:Wikidata Bridge/Development/10/de 1198 955721 5386785 3316967 2022-07-28T19:01:20Z ThisCarthing 17456337 wikitext text/x-wiki Geplante Funktionen für die nächsten Schritte 1o8pbfnaisz14sqa68awtrof00oqvyc Translations:Wikidata Bridge/Development/13/de 1198 955723 5386781 3316977 2022-07-28T19:00:57Z ThisCarthing 17456337 wikitext text/x-wiki Nachfolgende Funktionen sind vorerst nicht geplant. Möglicherweise werden sie in Zukunft implementiert. * Erstellen neuer Elemente, wenn kein vorhandenes gefunden wird * Anzeigen von Wikidata-Bearbeitungen im Verlauf des Wikipedia-Artikels * Bearbeiten von Daten in Eigenschaften und Lexemen haahx04kb1prpenfyflmtthxre8ulbv Translations:Wikidata Bridge/Development/14/de 1198 955724 5386783 3316991 2022-07-28T19:01:04Z ThisCarthing 17456337 wikitext text/x-wiki Was wird sich ändern? 40g59hpcizn53c95gevo63te1udy2uk Translations:Wikidata Bridge/Development/15/de 1198 955725 5386776 3316981 2022-07-28T19:00:14Z ThisCarthing 17456337 finishing up the split wikitext text/x-wiki * In Wikipedias und anderen Projekten kwoubkpw76cx58qqmox7ujfvrmbz7tr Translations:Wikidata Bridge/Development/12/de 1198 955727 5386779 3316986 2022-07-28T19:00:47Z ThisCarthing 17456337 wikitext text/x-wiki Was nicht Teil des Projekts ist e2zp31gl3mqi5yjgat3ywlm20l1zul4 Groups/de 0 957070 5387356 4924002 2022-07-28T22:11:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki-Gruppen''' organisieren Open-Source-Community-Aktivitäten im Rahmen spezifischer Themen und geografischer Gebiete. Es sind [[meta:Special:MyLanguage/Wikimedia User Groups|Wikimedia Benutzergruppen]], die sich auf eine gemeinsame Koordinierungsebene im MediaWiki-Kontext einigen. Als solche erweitern sie die Leistungsfähigkeit der Freiwilligen in der Wikimedia Foundation bei [[Events|Veranstaltungen]], der [[Volunteer coordination and outreach/Training materials|Koordination und Öffentlichkeitsarbeit / Schulungsmaterialien]], bei der Werbung und anderen technischen Aktivitäten zugunsten von Wikipedia, der Wikimedia-Bewegung und der MediaWiki-Software. <span class="mw-translate-fuzzy">MediaWiki-Gruppen sind für Mitglieder [[Special:MyLanguage/How to contribute|verschiedener Fachgebiete]] und unterschiedlichem Wissensstand offen.</span> Je reichhaltiger und vielfältiger, desto besser. Auch nicht-technische Nutzer, die bereit sind, etwas beizutragen und zu lernen, sind willkommen! Alle Gruppen verpflichten sich zur [[wmf:Friendly space policy|Friendly space policy]]. MediaWiki-Gruppen können von der Wikimedia Foundation und ihren Sektionen auf unterschiedliche Art und Weise ´ [[Groups/Wikimedia support|Unterstützung anfordern]]. == Themengruppen == Thematisch gleichartige MediaWiki-Gruppen arbeiten mit den ihnen entsprechenden Kollegen in der breiteren [[w:FLOSS|FLOSS]] Community zusammen. Sie sind globale Gruppen, die online zusammenarbeiten. * Sie haben Kontakt zu communities mit demselben Fokus. * Sie nehmen an Veranstaltungen zum gleichen Thema teil. * Sie fördern entsprechende Schulungs- und Öffentlichkeitsarbeit. * Sie helfen dabei, die zugehörige Dokumentation in [https://www.wikimedia.org/ wikimedia.org] zu verbessern. * Sie arbeiten mit den entsprechenden Entwicklungsteams zusammen. * Schließlich treffen sich einige von ihnen unter [//wikimania.wikimedia.org/ Wikimania]. == Lokale Gruppen == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Lokale MediaWiki-Gruppen arbeiten mit [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia Sektionen]] zusammen, siehe auch [[w:Wikipedia:Meetup|Wikipedia meetups]] und andere lokalen Gemeinschaften, die mit Wikimedia, freier Software, freier Kultur etc. verbunden sind. Ihr Fokus liegt auf persönlichen Aktivitäten: * Organisation von lokalen Veranstaltungen: Meetups, Schulungen, Hackertreffen..... Diese Ereignisse entsprechen der [[wmf:Friendly_space_policy|WMF Friendly space policy]]. * Teilnahme an Veranstaltungen, die in ihrem Bereich stattfinden. * Vertrieb und Verkaufsförderung. * Förderung lokaler Mitwirkender an globalen MediaWiki- und Wikimedia-Aktivitäten. <div class="mw-translate-fuzzy"> Auch für nicht englischsprachige Gruppen: * Lokalisierung von Dokumentation und Software nach [[Special:MyLanguage/translatewiki.net|translatewiki.net]]-Verfahren. </div> Lokale Gruppen müssen sich tatsächlich vor Ort befinden. Ausgangspunkte wie z.B. Recife, München oder Sankt Petersburg sind besser als Brasilien, Deutschland oder Russland. <span class="mw-translate-fuzzy">Wenn Sie keine Möglichkeit für die regionale Koordination sehen, dann fragen Sie in einer [[Mailing lists/Regional|regionalen Mailingliste]] nach.</span> == Eine Gruppe gründen == Du brauchst niemanden, um eine Gruppe vorzuschlagen, nur dich selbst. Um die Genehmigung dafür zu erhalten, müssen Sie über mindestens drei Mitwirkende verfügen. Unter [[Groups/Proposals|Gruppen/Vorschläge]] findest du weitere Details zur Gründung deiner MediaWiki-Gruppe. [[Category:MediaWiki Communication{{#translation:}}]] 6i0zzk2tnvu38kjhqpsj5z33uda8bog 5387374 5387356 2022-07-28T22:12:26Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki-Gruppen''' organisieren Open-Source-Community-Aktivitäten im Rahmen spezifischer Themen und geografischer Gebiete. Es sind [[meta:Special:MyLanguage/Wikimedia User Groups|Wikimedia Benutzergruppen]], die sich auf eine gemeinsame Koordinierungsebene im MediaWiki-Kontext einigen. Als solche erweitern sie die Leistungsfähigkeit der Freiwilligen in der Wikimedia Foundation bei [[Events|Veranstaltungen]], der [[Volunteer coordination and outreach/Training materials|Koordination und Öffentlichkeitsarbeit / Schulungsmaterialien]], bei der Werbung und anderen technischen Aktivitäten zugunsten von Wikipedia, der Wikimedia-Bewegung und der MediaWiki-Software. MediaWiki-Gruppen sind für Mitglieder [[Special:MyLanguage/How to contribute|verschiedener Fachgebiete]] und unterschiedlichem Wissensstand offen. Je reichhaltiger und vielfältiger, desto besser. Auch nicht-technische Nutzer, die bereit sind, etwas beizutragen und zu lernen, sind willkommen! Alle Gruppen verpflichten sich zur [[wmf:Friendly space policy|Friendly space policy]]. MediaWiki-Gruppen können von der Wikimedia Foundation und ihren Sektionen auf unterschiedliche Art und Weise ´ [[Groups/Wikimedia support|Unterstützung anfordern]]. == Themengruppen == Thematisch gleichartige MediaWiki-Gruppen arbeiten mit den ihnen entsprechenden Kollegen in der breiteren [[w:FLOSS|FLOSS]] Community zusammen. Sie sind globale Gruppen, die online zusammenarbeiten. * Sie haben Kontakt zu communities mit demselben Fokus. * Sie nehmen an Veranstaltungen zum gleichen Thema teil. * Sie fördern entsprechende Schulungs- und Öffentlichkeitsarbeit. * Sie helfen dabei, die zugehörige Dokumentation in [https://www.wikimedia.org/ wikimedia.org] zu verbessern. * Sie arbeiten mit den entsprechenden Entwicklungsteams zusammen. * Schließlich treffen sich einige von ihnen unter [//wikimania.wikimedia.org/ Wikimania]. == Lokale Gruppen == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Lokale MediaWiki-Gruppen arbeiten mit [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia Sektionen]] zusammen, siehe auch [[w:Wikipedia:Meetup|Wikipedia meetups]] und andere lokalen Gemeinschaften, die mit Wikimedia, freier Software, freier Kultur etc. verbunden sind. Ihr Fokus liegt auf persönlichen Aktivitäten: * Organisation von lokalen Veranstaltungen: Meetups, Schulungen, Hackertreffen..... Diese Ereignisse entsprechen der [[wmf:Friendly_space_policy|WMF Friendly space policy]]. * Teilnahme an Veranstaltungen, die in ihrem Bereich stattfinden. * Vertrieb und Verkaufsförderung. * Förderung lokaler Mitwirkender an globalen MediaWiki- und Wikimedia-Aktivitäten. <div class="mw-translate-fuzzy"> Auch für nicht englischsprachige Gruppen: * Lokalisierung von Dokumentation und Software nach [[Special:MyLanguage/translatewiki.net|translatewiki.net]]-Verfahren. </div> Lokale Gruppen müssen sich tatsächlich vor Ort befinden. Ausgangspunkte wie z.B. Recife, München oder Sankt Petersburg sind besser als Brasilien, Deutschland oder Russland. <span class="mw-translate-fuzzy">Wenn Sie keine Möglichkeit für die regionale Koordination sehen, dann fragen Sie in einer [[Mailing lists/Regional|regionalen Mailingliste]] nach.</span> == Eine Gruppe gründen == Du brauchst niemanden, um eine Gruppe vorzuschlagen, nur dich selbst. Um die Genehmigung dafür zu erhalten, müssen Sie über mindestens drei Mitwirkende verfügen. Unter [[Groups/Proposals|Gruppen/Vorschläge]] findest du weitere Details zur Gründung deiner MediaWiki-Gruppe. [[Category:MediaWiki Communication{{#translation:}}]] 5k19if3rp9qlpypasy7ypup4znfnh82 5387398 5387374 2022-07-28T22:14:50Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki-Gruppen''' organisieren Open-Source-Community-Aktivitäten im Rahmen spezifischer Themen und geografischer Gebiete. Es sind [[meta:Special:MyLanguage/Wikimedia User Groups|Wikimedia Benutzergruppen]], die sich auf eine gemeinsame Koordinierungsebene im MediaWiki-Kontext einigen. Als solche erweitern sie die Leistungsfähigkeit der Freiwilligen in der Wikimedia Foundation bei [[Events|Veranstaltungen]], der [[Volunteer coordination and outreach/Training materials|Koordination und Öffentlichkeitsarbeit / Schulungsmaterialien]], bei der Werbung und anderen technischen Aktivitäten zugunsten von Wikipedia, der Wikimedia-Bewegung und der MediaWiki-Software. MediaWiki-Gruppen sind für Mitglieder [[Special:MyLanguage/How to contribute|verschiedener Fachgebiete]] und unterschiedlichem Wissensstand offen. Je reichhaltiger und vielfältiger, desto besser. Auch nicht-technische Nutzer, die bereit sind, etwas beizutragen und zu lernen, sind willkommen! Alle Gruppen verpflichten sich zur [[wmf:Friendly space policy|Friendly space policy]]. MediaWiki-Gruppen können von der Wikimedia Foundation und ihren Sektionen auf unterschiedliche Art und Weise ´ [[Groups/Wikimedia support|Unterstützung anfordern]]. == Themengruppen == Thematisch gleichartige MediaWiki-Gruppen arbeiten mit den ihnen entsprechenden Kollegen in der breiteren [[w:FLOSS|FLOSS]] Community zusammen. Sie sind globale Gruppen, die online zusammenarbeiten. * Sie haben Kontakt zu communities mit demselben Fokus. * Sie nehmen an Veranstaltungen zum gleichen Thema teil. * Sie fördern entsprechende Schulungs- und Öffentlichkeitsarbeit. * Sie helfen dabei, die zugehörige Dokumentation in [https://www.wikimedia.org/ wikimedia.org] zu verbessern. * Sie arbeiten mit den entsprechenden Entwicklungsteams zusammen. * Schließlich treffen sich einige von ihnen unter [//wikimania.wikimedia.org/ Wikimania]. == Lokale Gruppen == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Lokale MediaWiki-Gruppen arbeiten mit [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia Sektionen]] zusammen, siehe auch [[w:Wikipedia:Meetup|Wikipedia meetups]] und andere lokalen Gemeinschaften, die mit Wikimedia, freier Software, freier Kultur etc. verbunden sind. Ihr Fokus liegt auf persönlichen Aktivitäten: * Organisation von lokalen Veranstaltungen: Meetups, Schulungen, Hackertreffen..... Diese Ereignisse entsprechen der [[wmf:Friendly_space_policy|WMF Friendly space policy]]. * Teilnahme an Veranstaltungen, die in ihrem Bereich stattfinden. * Vertrieb und Verkaufsförderung. * Förderung lokaler Mitwirkender an globalen MediaWiki- und Wikimedia-Aktivitäten. Auch für nicht englischsprachige Gruppen: * Lokalisierung von Dokumentation und Software nach [[Special:MyLanguage/translatewiki.net|translatewiki.net]]-Verfahren. Lokale Gruppen müssen sich tatsächlich vor Ort befinden. Ausgangspunkte wie z.B. Recife, München oder Sankt Petersburg sind besser als Brasilien, Deutschland oder Russland. <span class="mw-translate-fuzzy">Wenn Sie keine Möglichkeit für die regionale Koordination sehen, dann fragen Sie in einer [[Mailing lists/Regional|regionalen Mailingliste]] nach.</span> == Eine Gruppe gründen == Du brauchst niemanden, um eine Gruppe vorzuschlagen, nur dich selbst. Um die Genehmigung dafür zu erhalten, müssen Sie über mindestens drei Mitwirkende verfügen. Unter [[Groups/Proposals|Gruppen/Vorschläge]] findest du weitere Details zur Gründung deiner MediaWiki-Gruppe. [[Category:MediaWiki Communication{{#translation:}}]] 3a50zlunfvatam31cpsy6jx5qaxnoxt Translations:Groups/4/de 1198 957075 5387373 3325741 2022-07-28T22:12:25Z Shirayuki 472859 update wikitext text/x-wiki MediaWiki-Gruppen sind für Mitglieder [[$1|verschiedener Fachgebiete]] und unterschiedlichem Wissensstand offen. cuhq6uxx6vstrx4v1hlw3gd7uifo1ic Translations:Groups/25/de 1198 957105 5387397 3325781 2022-07-28T22:14:49Z Shirayuki 472859 update wikitext text/x-wiki Auch für nicht englischsprachige Gruppen: * Lokalisierung von Dokumentation und Software nach $1-Verfahren. bxn93to8vuccv7ddiqzb03sjp83cwmn Wikimedia Product/tg-cyrl 0 960839 5387595 5358214 2022-07-29T03:26:03Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Саҳмгузорон</span>]] * [[Readers|<span style="color:#2aa198">Хонандагон</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span class="mw-translate-fuzzy">Саҳифа</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span class="mw-translate-fuzzy">Саҳифа</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span class="mw-translate-fuzzy">Саҳифа</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === Викидода === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span class="mw-translate-fuzzy">Рӯйхати музокираҳо</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Goals</span> == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2017–2018</span> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2016–2017</span> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] plxpucnpp0dkhpbirdg08m3ffqj6srk New Developers/de 0 961529 5386844 5371100 2022-07-28T19:21:29Z ThisCarthing 17456337 update wikitext text/x-wiki <languages/> <span lang="en" dir="ltr" class="mw-content-ltr">This page explains how to get started as a developer who wants to contribute to [[Special:MyLanguage/Differences between Wikipedia, Wikimedia, MediaWiki, and wiki|Wikimedia]] technical projects.</span> {{toclimit|limit=2}} == Willkommen == [[File:Wikimedia Hackathon Prague 2019 - Group Photo - CLK.png|{{dir|{{pagelang}}|left|right}}|thumb|400px|Teilnehmer der {{ll|Wikimedia Hackathon 2019}}]] Die technische Community von [[m:Special:MyLanguage/Wikimedia movement|Wikimedia]] freut sich immer über neue Mitwirkende! Werde Teil einer globalen Community und erleichtere allen den Zugang zu kostenlosem Wissen! == How to start contributing == The following steps are a general outline of how to get started contributing: # Learn [[#Some basics to know|the basics of how Wikimedia open source software projects work]]. # Read the [[#Communication|Communication guidelines]]. # Set up accounts: [[Special:MyLanguage/Developer_account|Create a developer account]]. Depending on the type of contribution you want to make, you may also need to set up accounts in [[Special:MyLanguage/Phabricator/Help|Phabricator]], and [[Special:MyLanguage/Gerrit/Tutorial|set up Git and Gerrit]]. # [[#Choose a software project| Wähle ein Softwareprojekt]] # Wähle und löse eine Aufgabe (schreibe und teste deinen Code) # Übermittle deine Code-Änderungen zur Überprüfung. Follow the [[Special:MyLanguage/Gerrit/Code review/Getting reviews|Guide to getting your code reviewed]] and [[Special:MyLanguage/Gerrit/Tutorial#Submit_a_patch|submit a patch]]. The rest of this guide provides additional details about the process. {{anchor|Some basics to know}} ==Basics of how Wikimedia software projects work== Wikimedia hat Softwareprojekte in [[c:File:Slides from Wikipedia session at LibrePlanet 2019.pdf|vielen verschiedenen Bereichen]]. <div class="mw-translate-fuzzy"> Den Betreuern der einzelnen Softwareprojekte steht es ziemlich frei, die von ihnen bevorzugte Infrastruktur auszuwählen. Grundsätzlich haben alle Softwareprojekte </div> * ein Task-Tracking-Tool, mit dem Softwarefehler und Verbesserungswünsche gemeldet, verwaltet und besprochen werden. Beispiele sind [[Special:MyLanguage/Phabricator|Wikimedia Phabricator]], GitHub oder [[Special:MyLanguage/GitLab|Wikimedia GitLab]]. <div class="mw-translate-fuzzy"> * ein '''Code-Repository''', in dem der Quellcode für alle "ausgecheckt" werden kann. Beispiele sind [[Gerrit|Wikimedia Git/Gerrit]], GitHub oder Sourceforge. </div> <div class="mw-translate-fuzzy"> * ein Tool zur Codeüberprüfung, mit dem vorgeschlagene Codeänderungen (sogenannte Patches) diskutiert und verbessert werden. Beispiele sind Wikimedia Git/Gerrit, GitHub oder Sourceforge. Sobald Dein vorgeschlagener Patch fehlerfrei ist und mit dem Code-Repository zusammengeführt wurde, stehen Deine Codeänderungen allen zur Verfügung. ([[$1|Hier kannst Du mehr über bewährte Methoden für die Codeüberprüfung lesen.]]) </div> <div class="mw-translate-fuzzy"> * allgemeine Orte für Diskussionen über das Softwareprojekt und / oder um Hilfe und Unterstützung zu erhalten. Diese Orte können Mailinglisten oder IRC-Chat-Kanäle oder Wiki-Seiten oder andere Orte sein. Die genauen Orte hängen von jedem Projekt ab. Du kannst bestimmte Mentoren auch über "Diesem Benutzer eine E-Mail senden" auf ihren Benutzerseiten kontaktieren. Beachte jedoch, dass "privat gestellte Fragen anderen nicht helfen". </div> <div class="mw-translate-fuzzy"> Wenn Du Probleme hast oder Hilfe benötigst, kannst Du gerne jederzeit fragen. Wenn Du an den richtigen Stellen gute Fragen stellen möchtest, empfehlen wir Dir, den Abschnitt [[#communication| "Feedback, Fragen und Support"]] zu lesen. </div> {{anchor|Choose a software project}} == Wähle ein Softwareprojekt == <span lang="en" dir="ltr" class="mw-content-ltr">The following projects offer resources, mentorship, and are looking for new developers to contribute to them.</span> Wähle eines der folgenden Projekte aus und befolge die Projektdokumentation, um deine Entwicklungsumgebung einzurichten, eine Aufgabe auszuwählen, an der gearbeitet werden soll, die Aufgabe zu lösen und Ihre Codeänderungen zur Überprüfung einzureichen. <span lang="en" dir="ltr" class="mw-content-ltr">You are free to contribute to these projects or any others you are interested in related to Wikimedia.</span> Most can be found by searching for them on {{ll|Phabricator}} or online. {{TwoColumnGrid |content = <!-- ↑↑ This common outer template makes the projects appear organised in a grid ↑↑ --> {{NewDeveloperProject |project = [[File: Kiwix-horizontal-logo.svg |middle|frameless|x24px|alt=Kiwix|link=meta:Kiwix]] |content = [[File:Kiwix 2 alpha search screenshot.png|{{dir|{{pagelang}}|left|right}}|frameless|x120px|alt=Screenshot]] An [https://www.kiwix.org offline reader] for people without internet access * Erforderliche Fähigkeiten: Java/Kotlin (Android), Swift (iOS), Qt (desktop), NodeJS (mediawiki offliner), C++ * Nimm Kontakt auf: [mailto:hello@kiwix.org Mailing list] / Slack [https://join.slack.com/t/kiwixoffline/shared_invite/zt-c5fgl342-VDYtm7fwY6w0BAeBqYxIGg here] * Hole Dir den Quellcode: [https://github.com/kiwix/ GitHub] * Lies die [https://github.com/kiwix/overview/blob/master/CONTRIBUTING.md allgemeine Dokumentation] und die README.md-Datei des entsprechenden Projekts * Überprüfe die empfohlenen Aufgaben, an denen gearbeitet werden kann: [https://github.com/kiwix/kiwix-android/labels/good%20first%20issue Android], [https://github.com/kiwix/iOS/labels/good%20first%20issue iOS], [https://github.com/kiwix/kiwix-js/labels/good%20first%20issue JS], [https://github.com/openzim/mwoffliner/labels/good%20first%20issue mwoffliner] on GitHub * Mentor(en): Matthieu Gauthier, [[user:Kelson|Emmanuel Engelhart]], [[User:The other Kiwix guy|Stephane Coillet-Matillon]] }} {{NewDeveloperProject |project = [https://commons-app.github.io/ Commons App für Android] |content = [[File:Wikimedia_Commons_Android_App_-_Multiple_Image_Uploads.png|{{dir|{{pagelang}}|left|right}}|frameless|x120px|alt=Screenshot]] Eine App für Android-Geräte zum Hochladen deiner Bilder zu [[c:|Wikimedia Commons]] * Erforderliche Fähigkeiten: Java * Nimm Kontakt auf: [https://groups.google.com/forum/#!forum/commons-app-android Google Groups] * Hole Dir den Quellcode: [https://github.com/commons-app/apps-android-commons/ GitHub] * Lese die [https://github.com/commons-app/apps-android-commons/#documentation Dokumentation] * Überprüfe die empfohlenen Aufgaben, an denen gearbeitet werden kann: [https://github.com/commons-app/apps-android-commons/labels/good%20first%20issue GitHub] * Mentor(en): [[User:Misaochan|Josephine Lim]] }} {{NewDeveloperProject |project = [https://outreachdashboard.wmflabs.org/ Wiki Education Dashboard] |content = [[File:Wiki_Ed_Dashboard_course_page,_November_2016.png|{{dir|{{pagelang}}|left|right}}|frameless|x120px|alt=Screenshot]] Eine Webanwendung, die Wikipedia-Bildungsaufgaben unterstützt, bietet Daten- und Kursverwaltung für Dozenten und Studenten * Erforderliche Fähigkeiten: Ruby, JavaScript * Nimm Kontakt auf: {{irc|wikimedia-ed}} auf irc.libera.chat * Hole Dir den Quellcode: [https://github.com/WikiEducationFoundation/WikiEduDashboard GitHub] * Lese die [https://github.com/WikiEducationFoundation/WikiEduDashboard DoKumentation] * Schau Dir die empfohlenen Aufgaben an, an denen zu arbeiten ist: [https://github.com/WikiEducationFoundation/WikiEduDashboard/labels/newcomer%20friendly GitHub] * Mentor(en): [[c:User:Ragesoss|Sage Ross]] }} {{NewDeveloperProject |project = [[File:Pywikibot_MW_gear_icon.svg|middle|frameless|x30px|alt=Logo]] {{ll|Manual:Pywikibot|2=Pywikibot}} |content = [[File:Pywikibot Commonscat 2011.jpg|{{dir|{{pagelang}}|left|right}}|frameless|x50px|alt=Terminal]] Eine "Python"-Bibliothek und eine Sammlung von Skripten, die die Arbeit auf MediaWiki-Seiten automatisieren. * Erforderliche Fähigkeiten: Python * Nimm Kontakt auf: {{irc|pywikibot}} on irc.libera.chat / [https://lists.wikimedia.org/mailman/listinfo/pywikibot Mailing list] * Hole Dir den Quellcode: [[$Gerrit/Tutorial#Download code using Git|Verwende Git]] um den [$https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/ Quellcode] zu erhalten * <span class="mw-translate-fuzzy">Lese die [[Manual:Pywikibot|Dokumentation]]</span> * Überprüfe die empfohlenen Aufgaben, an denen gearbeitet werden kann: [https://phabricator.wikimedia.org/maniphest/query/D.pe8.a.NRmY/#R Phabricator] * Mentor(en): [[User:xqt|xqt]] }} {{NewDeveloperProject |project = [[File: ScribeAppLogo.png |middle|frameless|x70px|alt=Scribe|link=https://github.com/scribe-org]] |content = [[File:ScribeNewWMFDevsImg.png|{{dir|{{pagelang}}|left|right}}|frameless|x150px|alt=Scribe features]] [https://github.com/scribe-org Scribe] provides Wikidata based keyboards for second language learners. Features include translation, verb conjugation and noun-gender annotation. This project is very open to those who want to learn the needed languages and how to work with Wikidata! * Skills required: Swift for [https://github.com/scribe-org/Scribe-iOS iOS]; Kotlin for [https://github.com/scribe-org/Scribe-Android Android]; Python and/or Wikidata Query Service for [https://github.com/scribe-org/Scribe-Data Wikidata queries and formatting] * Get in touch: [https://github.com/scribe-org GitHub] or [[User:AndrewTavis|email]] * Get the source code: [https://github.com/scribe-org GitHub] * Read the contribution guidelines: [https://github.com/scribe-org/Scribe-iOS/blob/main/CONTRIBUTING.md iOS] or [https://github.com/scribe-org/Scribe-Android/blob/main/CONTRIBUTING.md Android] * Check the recommended tasks: [https://github.com/scribe-org/Scribe-iOS/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22 iOS] or [https://github.com/scribe-org/Scribe-Android/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22 Android] * Mentor(s): [[User:AndrewTavis|Andrew McAllister]] }} {{NewDeveloperProject |project = [[File:JeremyNguyenGCI_-_Video_Cut_Tool_Logo.svg|middle|frameless|x30px|alt=Logo]] [https://videocuttool.wmflabs.org/ Video-Werkzeug] |content = [[File: VideoCutTool_Editing_Video.png|{{dir|{{pagelang}}|left|right}}|frameless|x160px|alt=VideoCutTool]] Ein Werkzeug zum Bearbeiten von Videos auf Wikimedia Commons. * Erforderliche Fähigkeiten: React JS, Node JS. * Nimm Kontakt auf: [https://wikimedia.zulipchat.com/#narrow/stream/275007-VideoCutTool #VideoCutTool] in [[Outreach programs/Zulip|Zulip]] * Hole dir den Quellcode: See link in [[phab:project/profile/4054/|description in Phabricator]] * Lies die [[c:Special:MyLanguage/Commons:VideoCutTool|Dokumentation]] * Überprüfe die empfohlenen Aufgaben, an denen gearbeitet werden kann: [[phab:project/board/4054/|Phabricator]] * Mentor(en): [[User:Gopavasanth|Gopa Vasanth]] }} }} <!-- closure to content grid template --> {{anchor|Outreach programs and single tasks}} ''Bist Du ein Software-Betreuer und möchtest, dass Dein Projekt in die Liste der oben genannten Softwareprojekte aufgenommen wird? [[New Developers/Featured Projects|Informiere Dich und mach mit!]]'' == Outreach-Programme und einzelne Aufgaben == Abgesehen von den oben empfohlenen Softwareprojekten gibt es weitere Möglichkeiten, ein Projekt oder eine Aufgabe auszuwählen, an denen man arbeiten kann: {{TwoColumnGrid |content = {{NewDeveloperProject |project = [[File:GSoC-icon-192.png|middle|frameless|x30px|alt=Logo|]] [[Special:MyLanguage/Outreach programs|Outreach Programme]] |content = Wikimedia bietet Praktika in Programmen wie Google Summer of Code und Outreachy an. }} {{NewDeveloperProject |project = [[File:Bug icon - Noun project 198.svg|middle|frameless|x30px|alt=Logo|]] [[Special:MyLanguage/Good first bugs|Gute erste Aufgaben]] |content = <span class="mw-translate-fuzzy">Es gibt zahlreiche einzelne Aufgaben (quer durch viele Softwareprojekte), die für Neueinsteiger geeignet sind. <br /> Du bist dabei jedoch mehr oder minder auf Dich allein gestellt: Wir können nicht garantieren, dass Mentoren verfügbar sind oder dass Deine vorgeschlagenen Patches schnell überprüft werden.</span> }} }} <!-- closure for content grid template --> {{anchor|communication|Communication}} == Tipps zur Kommunikation == {{:New_Developers/Communication_tips}} == Zusätzliche Ressourcen == <div class="mw-translate-fuzzy"> * [[Special:MyLanguage/How to contribute|Wie kann ich mitarbeiten?]] listet viele weitere Möglichkeiten auf, auch in nicht-technischen Bereichen. </div> * [[Special:MyLanguage/How to become a MediaWiki hacker|So wirst Du ein MediaWiki-Hacker]]: Für Entwickler, die an MediaWiki-Kern- oder MediaWiki-Erweiterungen arbeiten möchten. * [[Special:MyLanguage/Developer hub|Entwickler-Zentrum]]: Weitere Ressourcen für erfahrene Wikimedia-Entwickler. <div lang="en" dir="ltr" class="mw-content-ltr"> * To ask your questions and to join general discussions, check the places listed on [[Special:MyLanguage/Communication|Communication]]. </div> * [[Wikimedia tutorials]]: Ein Index von Tutorials, die verschiedene Sprachen, APIs und Frameworks im Wikimedia-Technologie-Stack präsentieren. [[Category:New_contributors{{#translation:}}]] b3kmsvpimgk19dph4bug5664awvxj8s Translations:New Developers/14/de 1198 962008 5386843 5117999 2022-07-28T19:21:28Z ThisCarthing 17456337 update wikitext text/x-wiki * ein Task-Tracking-Tool, mit dem Softwarefehler und Verbesserungswünsche gemeldet, verwaltet und besprochen werden. Beispiele sind [[$1|Wikimedia Phabricator]], GitHub oder [[$2|Wikimedia GitLab]]. 0vnw886xpcpumui8y9gjy7zs62gg9qz Wikimedia Product/de 0 962542 5387571 5358189 2022-07-29T03:25:40Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=Mitarbeiter von '''Wikimedia Produkt''', [[foundationsite:role/staff-contractors/|angestellt bei der Wikimedia Foundation]], erstellen, verbessern und unterhalten die Funktionen der [[m:Special:MyLanguage/Wikimedia projects|Wikimedia-Websites]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Mitwirkende</span>]] * [[Readers|<span style="color:#2aa198">Leser</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === Programme === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|Initiative für eine gesunde Gemeinschaft]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Neue Leser]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|Strukturierte Daten auf Commons]] === Projektseiten === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|Inhaltsübersetzung, V2]] * [[Special:MyLanguage/Growth/Growth team updates|Growth (<i>Wachstum</i>)]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''Jährliches Planungsziel: Anti-Belästigungs-Tools''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''Sonstiges:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) == Metriken == <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === Mitwirkende === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * Phabricator-Arbeitsumgebung: [[phab:tag/contributors-team/|#Contributors-Team]] (selten verwendet) * Seite: [[Special:MyLanguage/Contributors|Mitwirkende]] * Teams: ====== Werkzeuge gegen Belästigung ====== * Phabricator-Arbeitsumgebung: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Seite: [[Special:MyLanguage/Anti-Harassment Tools|Werkzeuge gegen Belästigung]] ====== Gemeinschaftstechnologie ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * Seite: [[m:Special:MyLanguage/Community Tech|Gemeinschaftstechnologie]] ====== Bearbeiten ====== * Phabricator-Arbeitsumgebung: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Seite: [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== Growth (<i>Wachstum</i>) ====== * Phabricator-Arbeitsumgebung: [[phab:project/board/1114/|#Growth-Team]] * Seite: [[Special:MyLanguage/Growth|Growth (<i>Wachstum</i>)]] ====== Sprache ====== * Phabricator-Arbeitsumgebung: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Seite: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === Leser === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * Seite: [[Special:MyLanguage/Readers|Leser]] * Phabricator-Arbeitsumgebung: [https://phabricator.wikimedia.org/tag/reading/ #reading] * Teams: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> Seite: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] Leitung: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> Seite: [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] Direktor: [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> Seite: [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] Leitung: Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> Seite: [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] Leitung: Margeigh Novotny === Wikidata === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * Seite: [[d:Wikidata:Main Page|Wikidata]] * Leitung: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| WMDE Fiskaljahr 2017 | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q1: Januar-März 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q2: April-Juni] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q3: Juli-September] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q4: Oktober-Dezember] |- !scope="row"| WMDE Fiskaljahr 2016 | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q1: Januar-März 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q2: April-Juni] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q3: Juli-September] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q4: Oktober-Dezember] |} == Ziele == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: Juli-September 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: Oktober-Dezember 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: Januar-März 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: April-Juni 2020]]--> |- !scope="row"| 2018-2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: Juli-September 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: Oktober-Dezember 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: Januar-März 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: April-Juni 2019]] |- !scope="row"| 2017-2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: Juli-September 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: Oktober-Dezember 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: Januar-März 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: April-Juni 2018]] |- !scope="row"| 2016-2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: Juli-September 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: Oktober-Dezember 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: Januar-März 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: April-Juni 2017]] |- !scope="row"| 2015-2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: Juli-September 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: Oktober-Dezember 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: Januar-März 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: April-Juni 2016]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] pct9n10vowfnm7yivs0tcnfitvgjuno Wikimedia Product/pt 0 968334 5387589 5358207 2022-07-29T03:25:58Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=Equipa de '''Wikimedia Product''' [[foundationsite:role/staff-contractors/|empregada pela Fundação Wikimedia]] cria, melhora e mantém as funcionalidades dos [[m:Special:MyLanguage/Wikimedia projects|''sites'' da Wikimedia]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Colaboradores</span>]] * [[Readers|<span style="color:#2aa198">Leitores</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|Princípios do Produto]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|Guia de Colaboração Técnica]]) * [[Special:MyLanguage/Design/Statement of purpose|Declaração de Finalidade do Projeto]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|Dados e informação de pesquisa para produtos]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === Programas === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Novos Leitores]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === Páginas de Projetos === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * Página: [[Special:MyLanguage/Contributors|Colaboradores]] * Equipas: ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Página: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * Página: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== Edição ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Página: [[Special:MyLanguage/Editing team|Equipa de edição]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * Página: [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== Idioma ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Página: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === Leitores === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * Página: [[Special:MyLanguage/Readers|Leitores]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * Equipas: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|Análise]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> Página: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> Página: [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> Página: [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> Página: [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * Página: [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * Lista de discussão: wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Objetivos == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: julho–setembro de 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: outubro–dezembro de 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: janeiro–março de 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: abril–junho de 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == Agenda Anual == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|2016 Resumo do Produto]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|2015 Revisão do Produto e Tecnologia]] [[Category:WMF Projects{{#translation:}}]] gk9yagam8ha0eolplqjyydyy3tnz6bp Talk:Reading/Web/Desktop Improvements 1 974037 5386203 5383325 2022-07-28T12:05:08Z OVasileva (WMF) 7047284 /* External link icon */ Reply wikitext text/x-wiki {{Reading/Web/Desktop Improvements/Header}} {{WMF present |1=SGrabarczuk (WMF)|timezone_1=UTC+1/2|lang_1=pl, en, fr|photo_1=Wikispotkanie-warszawa-2021-07-03-rd-26.jpg |2=OVasileva (WMF)|timezone_2=UTC+1/2|lang_2=en, es, bg|photo_2=Vasileva, Olga January 2017.jpg }} {{Archive box| *[[Talk:Reading/Web/Desktop Improvements/Archive1|Archive1 (before the 1st batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive2|Archive2 (before the 2nd batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive3|Archive3 (before the 3nd batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive4|Archive4]] *[[Talk:Reading/Web/Desktop Improvements|Current discussion]] }} {{Reading/Web/Desktop Improvements/Talk page intro}} __TOC__ == Where is the TOC? == People here are complaining about it. I don't even get one! [[User:Betaneptune|Betaneptune]] ([[User talk:Betaneptune|talk]]) 17:38, 25 May 2022 (UTC) :Hello @[[User:Betaneptune|Betaneptune]]. Do you still have this problem? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:52, 8 June 2022 (UTC) ::Hi ! I have the same problem on the French version of Wikipedia. The TOC just disappeared. The problem appears in Firefox desktop (last version 101.0.1), even in "troubleshoot" mode with all my add-ons deactivated. However, the problem does not appear in Chrome. This is extremely confusing. I reported it on some discussion page on the french version of WP, but I also mention it here, as I'm not sure at all where to report the problem for it to be taken into account. [[Special:Contributions/85.169.195.108|85.169.195.108]] 17:56, 26 June 2022 (UTC) : The TOC is now on the left side, but after other menu lists. It should probably come first. But to keep things accessible, the (hidden) "jump to main menu" link should be kept as first element of course. [[User:Psychoslave|Psychoslave]] ([[User talk:Psychoslave|talk]]) 15:00, 5 July 2022 (UTC) ::Agreed. The TOC ''really'' should come first. The {{mono|#mw-navigation}} menu (which currently appears first) is comprised of mostly ancillary links unrelated to the page's content, many of which are rarely used (e.g., ''"Download as PDF"'', ''"Create a book"'', ''"Permanent link"'', etc). [[User:OmenBreeze|OmenBreeze]] ([[User talk:OmenBreeze|talk]]) 00:17, 6 July 2022 (UTC) :::{{ping|85.169.195.108}} It has been tracked here [[phab:T312022]].--[[Special:Contributions/37.103.14.65|37.103.14.65]] 09:03, 7 July 2022 (UTC) ::::Suggestions: ::::* ''If'' the TOC will ''not'' come first, the other menu lists on the left side should become hidden (collapsed) when there is a TOC below them, so that the TOC is always visible. ::::* The TOC should always be shown in its entirety, and not displayed as a box that you have to scroll through. ::::[[User:Förbätterlig|Förbätterlig]] ([[User talk:Förbätterlig|talk]]) 14:03, 12 July 2022 (UTC) == Too narrow (again) == Why waste all that space? I have a nice wide screen so I want to take advantage of it. Those who want to have it narrow can just reduce their window sizes? Overall, not a great look. Not exciting. Quite boring.--[[User:Xania|Xania]] ([[User talk:Xania|talk]]) 11:23, 22 December 2021 (UTC) :Hello @[[User:Xania|Xania]], you can read about our [[Reading/Web/Desktop_Improvements/Features/Limiting_content_width#Goals_and_motivation|goals and motivation]] for limiting the width. Also, we are working on a solution to use the empty space. Could you take a look at [[Reading/Web/Desktop Improvements/Fourth prototype testing/it|our fourth prototype]] and write more on what you think about arranging the space as it is presented there? Thank you in advance! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 14:59, 26 April 2022 (UTC) :: Oh my dear God, why don't you give an option to unrestrict the width?? It's beyond ridiculous how absolutely tiny is the page content on my monitor horizontally! I have to scroll all the time to read! Don't ruin Wikipedia the same way Fandom was ruined! [[Special:Contributions/90.188.46.13|90.188.46.13]] 04:38, 13 May 2022 (UTC) :::We have given this option. This can be done with the [[:en:User:Jdlrobson/vector-max-width-toggle.js|gadget one of our engineers made]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 03:39, 14 May 2022 (UTC) ::::Thanks, but maybe we should have an easy plug-in system for ordinary users or, at least, the instructions how to apply it and a place where to find those customisations. By default it is really narrow to read and it feels like a news site rather than an encyclopedia article. [[User:Krnl0138|Krnl0138]] ([[User talk:Krnl0138|talk]]) 09:55, 15 May 2022 (UTC) :::::I agree, the toggle option should be there by default! By the way, that script does not work well currently, so I [[:en:User:Arthurfragoso/vector-max-width-toggle.js|updated it here]]. — [[User:Arthurfragoso|Arthurfragoso]] ([[User talk:Arthurfragoso|talk]]) 13:28, 21 May 2022 (UTC) ::I don't understand why you are still pushing on us that bad design choice. It still is time to pull the plug and start to work on a plain page design. You are convincing no one here. Please, please, really, please stop this nonsense. Forcing bad choices on your users because you are the only product on the market is never a good thing. ::Since it has been forced without asking anyone on the French Wikipedia I had to register just to come back to the normal and good design. That's something, as a simple reader, I should never have had to do in the first place. ::So one last time, please come back to reason and stop hurting your user base foolishly. [[User:DerpFox|DerpFox]] ([[User talk:DerpFox|talk]]) 21:33, 13 May 2022 (UTC) :::Hello @[[User:DerpFox|DerpFox]], thanks for your comment. Have you maybe followed the links I've shared in my answer to Xania? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 03:42, 14 May 2022 (UTC) ::The lines in the fourth prototype seem to be slightly wider to me on 1080p display than in the current version of 2022 vector design, but those empty strips on the sides, each of which are almost the size of the old navigation mv-panel, constantly remind about the space wasted. ::If the only reason of this thinning is the recommended line lengths in symbols and you want to keep it for any price, I would suggest using a dynamic font size, so, for example, starting from some resolution the symbols just grow larger. This might also reduce the eye strain connected to focusing on the small text. ::[[User:Kageneko|Kageneko]] ([[User talk:Kageneko|talk]]) 13:51, 17 May 2022 (UTC) ::I had a browse over the reasons for the change, but I still don't like or agree with the main justification more or less boiling down to "everyone else is doing it so we should too". Even in the linked examples, the page still feels a lot more "full" despite having a dedicated deadspace on the site, due to the way the page has been very carefully designed in a mixture of different kinds of block contents (images, text interactive eliments, etc). ::Accepted Webpage standards used to be against having blank, unused and waisted deadspace, but at some point in the last 10 years there seems to have been a weird shift to the opposite where deadspace is all the rage, though it's not one I've personally ever liked or agreed with. ::While I'm sure there are good uses of limiting page width, I'm not sure if Wikipedia, being a site that is mainly made up of text would really benefit from it as it's likely just going to squash pages and increase the amount of vertical scrolling required to navigate. [[User:Dave247|Dave247]] ([[User talk:Dave247|talk]]) 07:32, 18 May 2022 (UTC) ::Yeah it's too narrow otherwise. the look is very nice, it's not boring as you tell. [[User:Crater bug|Crater bug]] ([[User talk:Crater bug|talk]]) 15:28, 28 May 2022 (UTC) :I totally agree! I dislike the vector skin because how small it is. [[User:OverAWallOfMetaKnight|OverAWallOfMetaKnight]] ([[User talk:OverAWallOfMetaKnight|talk]]) 15:55, 15 May 2022 (UTC) :Agreed. I use a 3440x1440 screen (usually with a tiled layout), and this new layout forces all the content to occupy a comically narrow strip, instead of allowing me to choose the width myself. [[User:Emptyflask|Emptyflask]] ([[User talk:Emptyflask|talk]]) 13:47, 17 May 2022 (UTC) :I agree, there is simply too much space wasted that could be used for more article space and a button specifically for those who want to edit wikipedia [[User:Techny3000|Techny3000]] ([[User talk:Techny3000|talk]]) 02:52, 28 May 2022 (UTC) :hard to read I'm glad I stayed the same as before No changes required [[Special:Contributions/240B:11:E7E0:5E00:6005:3399:E6C:2B48|240B:11:E7E0:5E00:6005:3399:E6C:2B48]] 14:06, 2 July 2022 (UTC) :Strongly agree. I want to decide the readable width for me. In the old skin and most websites, I can do it by adjusting the width of window. I definitely don't want to care about "CORRECT READABLE WIDTH FOR EVERYONE" decided by someone somewhere, even if they are great scholars. [[User:Kyoku|Kyoku]] ([[User talk:Kyoku|talk]]) 08:32, 10 July 2022 (UTC) After reviewing the posted defense of the narrowing and the feedback listed here, this feature belongs entirely as an optional setting. It most certainly should not be the website's default. [[User:RightQuark|RightQuark]] ([[User talk:RightQuark|talk]]) 01:29, 24 May 2022 (UTC) :The defence of the narrowing seems to have little real-world bonuses. It may be theoretically good but makes it bad to read because Wikipedia articles can be long [[User:Torqueing|Torqueing]] ([[User talk:Torqueing|talk]]) 17:10, 24 May 2022 (UTC) I'm fine with the text being narrow but the ui and nav bar should be full width. --[[User:Thedonquixotic|Thedonquixotic]] ([[User talk:Thedonquixotic|talk]]) 00:18, 26 May 2022 (UTC) :@[[User:Thedonquixotic|Thedonquixotic]], what do you mean by the ui and nav bar? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:54, 8 June 2022 (UTC) ::Not sure what is unclear here. I mean the navbar. As in the bar up at the top of the page with use account, search etc. [[User:Thedonquixotic|Thedonquixotic]] ([[User talk:Thedonquixotic|talk]]) 19:07, 1 July 2022 (UTC) I also have a wide screen monitor. I do not like this forced width shrinkage in the Vector 2022 skin. [[User:OhanaUnited|<b><font color="#0000FF">OhanaUnited</font></b>]][[User talk:OhanaUnited|<b><font color="green"><sup>Talk page</sup></font></b>]] 17:24, 9 June 2022 (UTC) In current form without a toggle for width this layout is unacceptable on large monitors. Even my old 14'' monitor. For now I am reverting to avoid having in forced horizontal white-space. [[User:Phatom87|phatom87]] ([[User talk:Phatom87|talk]]) 14:32, 20 June 2022 (UTC) :Absolutely unacceptable, too narrow, an unjustified waste of space. [[User:Loupeter|Loupeter]] ([[User talk:Loupeter|talk]]) 10:39, 24 June 2022 (UTC) :It sounds like the fixed-max-width (assuming one's window is wide enough, and regardless of how much wider it might be) is a compromise between the needs of two different types of reading activities. I have both habits (skim vs detail-read), and felt especially the concern that the text doesn't obey what *I* do with my window. A reason I might widen my window is exactly because I want wider content. A comprimse necessarily isn't ideal for either one side. A better solution is to make it easy and discoverable how to get the *best* feel for whatever one is trying to do, rather than forcing so many to have a sub-par experience. A third-party gadget isn't discoverable and is surely more fragile than a first-class toggle feature of the skin itself. [[User:DMacks|DMacks]] ([[User talk:DMacks|talk]]) 15:16, 29 June 2022 (UTC) In my opinion, [[Skin:Timeless]] does a much better job at restricting article space to improve readability. This is because the UI is not entirely positioned on the left-hand side of the screen, and the background colour is not blindingly bright. If the intention is to create whitespace, please don't use bright colours. Timeless also has more space for pictures. For the past 20 years, articles have been written with the understanding that 80%+ of the screen will be for content. There are width and upright tags all over the place that, once viewed with this narrow a perspective, become overwhelming. A skin should not change the fundamental readability of the page. Compare [https://en.wikipedia.org/wiki/The_World_Before_the_Flood?useskin=vector-2022 this] with [https://en.wikipedia.org/wiki/The_World_Before_the_Flood?useskin=timeless this]. In Timeless, when the content ends, grey begins. In Vector 2022, it looks like the HTML was corrupted and failed to load because it continues with white for no discernable reason. Vector also artificially makes articles look longer than they are, which may actually dissuade people from reading. For instance, using a 27" 16:9 monitor, on the article for Barack Obama, [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=vector-2022 Vector] just about lets me see the entire lead on my screen at once. [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=timeless Timeless] allows me to see the whole lead quite easily, as well as part of the ToC. [[:en:Line length|Line length]] may be a thing, but you must take into account the total amount of text on the screen at once, too. There's no use having the perfect 50 character line if you need 100 of them all bunched up together. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:18, 13 July 2022 (UTC) :Quick update and aside: I just learned about wide-vector-2022. This is fantastic. I actually like the ToC being placed where it is when using that gadget. If the plan was to make the wide skin the default, I would be less hesitant. For comparison with the links in my previous message, [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=vector-2022&withgadget=wide-vector-2022 here is Barack Obama] with wide-vector-2022. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:25, 13 July 2022 (UTC) ::This "wide-vector-2022" version should be the default IMO. [[User:Some1|Some1]] ([[User talk:Some1|talk]]) 02:50, 17 July 2022 (UTC) :> For the past 20 years, articles have been written with the understanding that 80%+ of the screen will be for content. :I'll just note that for the past 10 years that means you've written things that just do not work that way on mobile. :) :> A skin should not change the fundamental readability of the page. [..] In Vector 2022, it looks like the HTML was corrupted and failed to load because it continues with white for no discernable reason. :This seems like a lot of assumptions to me personally. Do we have wider evidence for this ? :> There's no use having the perfect 50 character line if you need 100 of them all bunched up together. :Literally every mobile user on the Barack Obama page, the majority of the readers. Screens and screens till you hit the end of the lead... —[[User:TheDJ|Th<span style="color: green">e</span>DJ (Not WMF)]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 20:20, 14 July 2022 (UTC) ::{{tq|I'll just note that for the past 10 years that means you've written things that just do not work that way on mobile. :)}} :::MinervaNeue, when viewed on normal phone screens, ignores width tags. The only difference between writing for desktop screens and mobile screens is file placement. ::{{tq|This seems like a lot of assumptions to me personally. Do we have wider evidence for this ?}} :::I don't need to provide evidence to state my opinion. The page looks unfinished with the extra whitespace on the right hand side. If you do want more than just my opinion, CNTRL+F for "whitespace" on this page. 12 other posts mention it. ::{{tq|Literally every mobile user on the Barack Obama page, the majority of the readers. Screens and screens till you hit the end of the lead...}} :::Difference is that my phone is in my hand. I'm not getting overloaded with line after line if the screen is only 15cm long. I can see a whole paragraph on at once and then scroll when necessary. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:10, 15 July 2022 (UTC) == Keyboard shortcut does not focus search field in sticky header == {{tracked|T307024}} When pressing the keyboard shortcut for search (alt + shift + f) the search field at the top of the page is focused, even if the sticky header is showing. It would be better if the search field in the sticky header was focused. As it is now the page will scroll to the top which is unnecessary. [[User:Sebastian Berlin (WMSE)|Sebastian Berlin (WMSE)]] ([[User talk:Sebastian Berlin (WMSE)|talk]]) 16:10, 12 January 2022 (UTC) == Page-title and Search == In a nutshell, I believe * the Search would benefit from being (a) more consistently placed, and (b) more accessible from the sticky header by having a larger click-target. ** See image at [[:File:Vector-sticky-header-version1-search-size.png]] (and more [[#Search_box_size_and_location|details above]]) * the Page-title is already visible in multiple locations, and ''might'' not need this additional instance? AFAIK only users with "Fullscreen - F11" enabled would hide the existing locations where it is already displayed, whilst scrolled. ** See image at [[:File:Page_title_repetition_and_cutoff.png]] Hope that helps! –[[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 20:53, 21 January 2022 (UTC) == Feedback regarding the new language switcher == Hello, I am a French person using Wikipedia in both French and English. I usually decide the language of the article depending on the topic. If it's related to France, I know the French version is going to be better. If it's a general topic, I usually select English. However, it's been a few months that the language picker has been moved to the top of the screen when an article is display in French. And I really can't get used to it. Sure, it's easy to discover - but it's more complicated to use. Having to click twice is a regression for anyone switching language frequently. An action that used to require half a second now takes 2 seconds. If you do this about ten times every time you browse Wikipedia, it does become irritating... I hope this feature is not shipped to other languages, and France gets the sidebar back. If you want to make this feature more discoverable, maybe you could add a shortcut but keep the sidebar. Or display a tooltip once in a while to educate newcomers. But please, keep "heavy users" of language switching in consideration. Thanks {{unsigned|77.148.113.166|19:54, 25 January 2022}} : I'd state this as 'what used to take me a second (finding the right language) now takes 10': Open language switcher, often don't see the language I want, have to search? want to see which languages have a version, have to scroll; don't have a quick way to default present all languages by-alpha. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 16:49, 2 May 2022 (UTC) : I have to agree with this as another French person frequently switching languages on Wikipedia and Wiktionary. I should add, in addition to the intrinsic usability of the interface (I do agree it's a slight regression for my usage), the fact that most language editions still use the old interface (and most other sites using mediawiki, and the latter is likely to remain the case for a long time) means you don't actually get the opportunity to unlearn it. So every time I want to switch languages from a French page, I will first scroll down to the old location and waste 1s parsing the sidebar and wondering where the links are. I check out other languages almost every time I read any article and those milliseconds of irritation do add up. Anyway, I strongly think that “don't fix what ain't broke” should apply here! [[Special:Contributions/37.183.2.114|37.183.2.114]] 12:06, 8 May 2022 (UTC) : +1 to [[User:Sj|Sj]]. --[[User:ThurnerRupert|ThurnerRupert]] ([[User talk:ThurnerRupert|talk]]) 18:58, 11 June 2022 (UTC) Often I use the language switcher not to navigate to the article on different language, but just to look up how that article is titled in a different language. In other words, using Wikipedia's inter-language links as a sort of dictionary. By hovering over the list of languages I can gather multiple titles, see their similarity between languages. With the New Look, language switcher became less accessible, though gathering titles by hovering still works there. Also this new dropdown-based language switcher seems either to require tricky CSS features or JavaScript. Will it make problems for simplistic browsers like w3m? [[User:Vi2|_Vi]] ([[User talk:Vi2|talk]]) 17:48, 20 May 2022 (UTC) I find the language switcher the worst of both worlds of the two variants in the old interface. It can be annoying to scroll through 200+ languages in an idiosyncratic ordering (for example, كوردی [Kurdi in Perso-Arabic script] is filed under S for Sorani), but at least I can see them all and preview the name of the article in various target languages. With the drop-down menu in the old interface, I get the languages grouped geographically, and I can also search for a specific language, with the system recognizing many name variations. The new interface gives me a drop down menu with all 200+ languages in the same idiosyncratic order, with no geographic grouping and no ability to search for a specific language. [[User:LincMad|LincMad]] ([[User talk:LincMad|talk]]) 22:28, 25 May 2022 (UTC) I am primarily an active user on the Japanese Wikipedia (now defaulted to vector2022) and I agree with you completely. Why doesn't this use the blank spaces on the left and right? No need to hide buttons and functions everywhere just to make the page look hollow. As for the other features, there are so many problems with the new Vector. I definitely want the old version to remain. I will continue to use it and not the new one. --[[User:Sugarman|Sugarman]] ([[User talk:Sugarman|talk]]) 07:14, 6 July 2022 (UTC) == Feedback on ToC functionality == Hello, I’m not sure how far you are in the development of the new table of content functionality, but I was looking at [https://en-toc.wmcloud.org/wiki/Moon this prototype] and noticed a potential problem. Here the ToC is on the side and that’s a good thing, but the ToC in the text have also been deleted and that’s not much a good thing. When there is a big infobox, the in-text ToC compensate partly or totally for it, hence the page arrangement take it into consideration for the position of the images. Now if you delete it, all the text will go up, along with the images, but the images can’t always follow, because the infobox, so the right-aligned images are going to pile under it, while the left-aligned will reduce the text to a very small column between them and the infobox. On fr:wp, infoboxes are very widely used, so deleting the in-text ToC is going to break the page layout of most articles (and rather probably upset the community). So I’d suggest that, whatever you do with the ToC, to not delete the in-text ToC until there is also a functionality to move the infobox outside the text too (that would be great by the way, as infoboxes always cause difficulties with page layout). --[[User:Runi Gerardsen|Runi Gerardsen]] ([[User talk:Runi Gerardsen|talk]]) 09:30, 7 February 2022 (UTC) :I would like to add myself as having this same concern about images. At present, image placement in many articles was determined by this factor of the TOC being inline, sometimes offsetting the issues of long infoboxes and allowing the first image in the first section to be right-justified (like anyone with any experience in professional publishing, I ''really'' hate left-justified lead images as they break up the flow of the text by interposing themselves between heds and text. Similarly, I try to maintain alternation in the justification of images since that mirrors the sweep of our vision and makes text with images easier to read (but of course you don't do this when it creates other layout issues).<p>''When'' this is deployed, a lot of articles are going to suddenly have image placement issues at the top that didn't previously. And this will probably make a lot of people ''very angry''.<p>I can see the need for the sticky TOC but I think it would still be better as something that could be toggled there from its current position while reading depending on how the user prefers it in an individual article. [[User:Daniel Case|Daniel Case]] ([[User talk:Daniel Case|talk]]) 05:50, 29 April 2022 (UTC) ::What if we kept both the inline/in-text ToC ''and'' the sticky/sidebar ToC, but only display the latter when the user's scrolled past the former? A user preference could be added that forces the latter to always (or never) be displayed. I agree that the situation with images is a <abbr title="Pain In The Frigging Arse">PITFA</abbr>, but I really don't want to give up the sticky ToC either… [[User:OmenBreeze|OmenBreeze]] ([[User talk:OmenBreeze|talk]]) 00:43, 6 July 2022 (UTC) I'm not sure, but until I manually switched back to "Vector legacy (2010)", then again to "Vector (2022)", ToC section was absent completely (neither new-style nor old-style). Also maybe, like with the language switcher, there should be [temporary] notice about ToC having moved to the left where it was previously? [[User:Vi2|_Vi]] ([[User talk:Vi2|talk]]) 17:57, 20 May 2022 (UTC) == Feedback on new language switcher in French == As a translator, I litteraly jump from one language to another every hour of every day. It is simply unbearable to now have to go to a sub-menu to switch from French to English or Italian. That added click translates (pun intended) into lost time and nerves on a daily basis. I'm not hostile to a more smartphone-friendly interface, and maybe that kind of switcher is perfect on a little screen. But it's not okay to make the overall experience so much unsteady (especially with the links being there for some languages and moved away for other ones) when # switching seamlessly from one language to another is precisely the one advantage Wikipedia has over any other encyclopedia and # my 32" monitor has plenty of space to display these links in the left column. Last year I had selected the old Vector theme for this very reason and this morning, I was force-switched into the new Vector 2022 theme. So for the second time I'm back on the classic Vector theme and really, really hope it will stick. [[User:Herisson26|Herisson26]] ([[User talk:Herisson26|talk]]) 22:16, 7 February 2022 (UTC) :Hello @[[User:Herisson26|Herisson26]]. Thank you for asking here. :* We've been planning to provide [[Reading/Web/Desktop_Improvements/Features#Language_switching_2:_One-click_access_to_preferred_languages|one-click access to preferred languages]] but it's dependent on the work of another team ([[Wikimedia Language engineering|Language]]). We can't promise anything in terms of the timeline yet. :* What do you mean by "with the links being there for some languages and moved away for other ones"? You saw the new Vector on some wikis, and the old Vector on some other wikis, didn't you? I think that's related to the next issue. :* Why you had to switch back again - [https://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Caf%C3%A9_dos_programadores&diff=prev&oldid=62956756&diffmode=source here's my explanation]. We're sorry, this was an extremely rare oversight. :* It's interesting that you write this interface is smartphone-friendly. Many volunteers note this. Out of curiosity, what makes you think that? Is this just about the responsiveness, or something more? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 00:30, 17 March 2022 (UTC) ::Hello @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], ::* For a translator, direct access to "preferred" languages is not enough. I need the complete list of languages, as it exists on old Vector. My preferred languages would be French, English, Spanish and Italian, but I will regularly read directly a page in Japanese, Portuguese or any other if it's the one that will get me the information I'm looking for (which is quite often the case when dealing with foreign people). So limiting direct access to a select few languages will still break Wikipedia for me. ::* Yes, lots of wikis use old Vector while the French one uses the new ones. It completely breaks the user interface. It is of utmost importance to me that all Wikipedia pages have the same layout, whatever the language. I understand the need to test things, but when you make a public switch that impacts the ergonomics of the site, it should be made across all languages. Maybe make the change per-user instead of per-language if you don't want to switch everyone at once. ::* Nothing to do with responsiveness. Smartphones don't have the physical space to display the language list and the article content at the same time, so having a button on the top of the page to show/hide the language panel makes sense. It does NOT on computers, which have plenty of free space for the left column and the traditional language list. ::[[User:Herisson26|Herisson26]] ([[User talk:Herisson26|talk]]) 08:21, 18 March 2022 (UTC) Very bad indeed. The French version of Wikipedia, which has put all interwiki language links in a dropdown menu, is most annoying. It is a big waste of time, and not user-friendly at all. To switch to the article in another language, instead of having the whole choice displayed at once and just having to click, one now has to go back up to the right-hand corner of the article, click on the dropdown menu, scroll down the list until the desired language apears, click again... This change is not an improvement. It tends to isolate each linguistic version of Wikipedia, by rendering the language switching much harder. If ever it is useful for smartphones, please change the layout for mobiles only ("m" version of Wikipedia), but not for the desktop version. This cumbersome change should NOT be extended to other Wikipedias, and the French version should revert as soon as possible to a user-friendly layout, such as that of the English language Wikipedia. [[User:Baronnet|Baronnet]] ([[User talk:Baronnet|talk]]) 15:49, 20 March 2022 (UTC) @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] very cool that you bring one click different language!! would you please include the language team in this discussion here, and provide a link so people can view the progress? --[[User:ThurnerRupert|ThurnerRupert]] ([[User talk:ThurnerRupert|talk]]) 18:56, 11 June 2022 (UTC) == TOC Feedback == I noticed that the newest designs for the table of contents do not allow for it to be collapsed. I think the ability for the TOC to be collapsed is very important, specifically for users that have a touchscreen laptop. I and a friend of mine often use our left hand and our touchscreen to scroll articles because on our laptops it is often easier to scroll quicker than to use the touchpad. If the TOC remained expanded we might accidentally tap a link. A button to collapse it and a preference to expand or collapse it by default would be nice. [[User:Lectrician1|Lectrician1]] ([[User talk:Lectrician1|talk]]) 20:07, 8 February 2022 (UTC) :Hello @[[User:Lectrician1|Lectrician1]]. Indeed, the first version of the TOC was not possible to be collapsed. This was because the results of user testings (both in-person and on-wiki) didn't indicate that the functionality was important. Now, given the feedback we've collected, we've decided to consider options how to make the TOC collapsible. In this context, what do you think about our [https://di-collapsible-menus.web.app/Brown_bear newest prototype]? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 13:46, 6 May 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] Thank you for responding! :::Hi, @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], I came to this page to ask whether the ToC can be moved from the sidebar, and really like the prototype. However it seems to be malfunctioning in Safari 15.4 (17613.1.17.1.13): https://imgur.com/a/O0Jhti1 :::Thanks. [[User:HughLilly|&#32;—Hugh]] ([[User talk:HughLilly|talk]]) 05:43, 20 May 2022 (UTC) ::My feedback: ::* I really dislike the usage of the bracket type of buttons for <code>[hide]</code> and think a OOUI button or a smaller alernative should be used instead. ::* I like that all of the headers in the TOC are collapsed by-default, however, I think they when you're scrolling inside of a section, they need to expand and collpase as you go through one section to another. I've seen this functionality on other platforms and it allows the reader to understand the outline better when they're viewing the article. ::* The hiding action of the TOC has an inconsistent navigational pattern. UIs should always require the same amount of actions to disable something as to enable something. That always feels the most natural. Hiding the TOC for its default position requires one button press, but to return it back to its previous state requires two. Also, its location next to the title and then how it switches to the upper left to become sticky is really weird too. I don't like either of those locations. I was thinking it could look something like this collapsed and you could press the icon on the right to both collapse and expand it: ::[[File:MediaWiki table of contents collapsed idea.png|frameless]] ::[[User:Lectrician1|Lectrician1]] ([[User talk:Lectrician1|talk]]) 00:42, 7 May 2022 (UTC) Hi, i just cant find the table of contents, i need it for easier navigation. please, help == Sticky header in the namespace Project == ([[:fr:Discussion_utilisateur:Patafisik_(WMF)#En-tête_figé_et_accès_aux_langues|original discussion in French]]) Hi, a user suggests to add the sticky header in the namespace Project too, not only in [[Talk:Reading/Web/Desktop_Improvements#Talk_page_and_page_history|Talk pages or History pages]] (see for exemple [[phab:T289641#7365946]] and [[phab:T299115]]). Best regards, [[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 09:15, 9 March 2022 (UTC) == Left margin menu pushes down content == I normally use Monobook, but happened to get into the new Vector. Odd experience. The search box was absent and I had to scroll down for the content. I now see that you are supposed to click the magnifying glass to get the search box. OK. But the scrolling? It seems the new Vector tries to guarantee wide enough space for the content. Perhaps that's what people surfing with maximised windows expect, but if you have a narrower window, is that really optimal? To get the left margin menu to the left of the content, I need a window some 1000 px wide. This "minimum" width gives me lines of about 100 characters, while I've heard reading is easiest at 47–72 or something like that. I like to have several windows open in parallel, and a narrower windows makes them fit better. Anyway, if one's browser window is narrow, for whatever reason, does the empty space to the right of the margin menu really give the best possible experience? Is the 100 char width something that needs to be guaranteed for those planning layout of individual articles? (This experience is with Firefox 91.7.0esr on Debian.) –[[User:LPfi|LPfi]] ([[User talk:LPfi|talk]]) 20:07, 17 March 2022 (UTC) == Questions I shouldn't need to ask == I can tell WMF developers put a lot of work into this, but I'm sorry, this isn't cutting it. This latest prototype is Vector in name only. It's a completely different look and a completely different experience. * Why do I have to click twice to get to my talk/contribs/preferences? * Don't you think you could have fit those important links if you didn't go overboard on the whitespace or if the search bar wasn't so enormous? * Is the language switcher really so important that it belongs in the sticky menu? * I had to think for a few seconds about what the hamburger/star icon was (it's the Watchlist). Why are the icons necessary? I'll answer this one — too much whitespace at the top. * Why is the new interface such a step down for the editors who will have to use it every day? * ''And why are you still trying to put a hamburger menu on a desktop site?'' It's not all bad — I do think the max width improves readability. But that was already present on previous less-bad prototypes. We were promised "improvements" to Vector, and what we're getting is an entirely new (and entirely inferior) skin. If this is really going to still be called Vector, that is highly misleading. The early comments that "total replacement is not an option" don't make a lot of sense now that Wikipedia appears to be getting exactly the top-down redesign I had feared this project would produce. Pigs will fly before this gets deployed to English Wikipedia ''without'' the community getting their pitchforks. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 04:45, 26 March 2022 (UTC) : I went into Preferences to turn off the changes and I saw that the software is now treating "vector-2022" as a new skin. This is better than what I thought was going on but maybe there should be a more original name> : Also, wouldn't it be a much better use of developer time to, say, work on the many unresolved Community Wishlist items? —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 17:09, 26 March 2022 (UTC) ::Hi @[[User:Pythoncoder|Pythoncoder]], thanks for these comments. I'd just like you to know that I'm working on an answer for you and I'll paste it soon. You've asked many important and basic questions (like the one about the Community Wishlist Survey), and I'm truly happy that you've done that. It's much better to clarify the basics. You don't know whether these are clear as long as no one questions it. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 00:53, 8 April 2022 (UTC) ::: {{ping|SGrabarczuk (WMF)}} I should have made it more clear above, but most of my comments are regarding the Fourth Prototype. And now that I read through my earlier comments it makes sense to make the sidebar collapsible in case readers don't want distractions. I believe the sidebar is shown by default so please disregard my complaints in that area. This is why I shouldn't edit when I'm sleep-deprived. I do still think the new skin needs a new name though. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:03, 8 April 2022 (UTC) ::: Also re: wishlist, I suspect the two projects are probably worked on by completely different dev teams. Again, I'm sorry for the passive-aggressiveness above. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:06, 8 April 2022 (UTC) ::::Hello @[[User:Pythoncoder|Pythoncoder]], no worries, I'm really glad you've figured some issues out yourself! Would it be possible for you to state what remains unclear? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:05, 14 April 2022 (UTC) :::::I think it mostly boils down to the amount of whitespace at the top and the hiding of important links such as talk, contribs, and login under a dropdown. I think this should be fixed. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:28, 15 April 2022 (UTC) == Sticky header doesn't show the name or the logo of the project: the risk of loss of identity for Wikimedia sister projects == ([[wikt:fr:Wiktionnaire:Wikidémie/mars_2022#Interface_bureau_%3A_venez_tester_le_quatrième_prototype|From French Wiktionary]]) {{Tracked|T293395}} "I'm still observing the same problem when using this new skin: if you scroll down the page, it's impossible to know on which Wikimedia project you're on. The sticky header doesn't include the name of the site you are on, which is penalizing users for sharing screenshots, but also for identifying the editorial lines/ editorial policies of the different projects. Sister projects have important specificities. On the French Wiktionary, we already have people complaining that they can't find the content they expect to see on Wikipedia, and we have to tell them that it doesn't belong on the Wiktionary. I'm afraid that the phenomenon will only get worse."-Translated by --[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 13:28, 29 March 2022 (UTC) (original message: ''"J’observe toujours le même problème, que je constate au quotidien en utilisant ce nouvel habillage : on ne sait pas sur quel projet on est dès que l’on défile un peu. L’en-tête fixe n’intègre pas le nom du site sur lequel on se trouve, ce qui est pénalisant pour le partage de capture d’écran, mais aussi pour l’identification des lignes éditoriales des différents projets qui ont des spécificités importantes. On a déjà actuellement des gens qui se plaignent de ne pas trouver tel contenu qu’ils s’attendent à voir sur Wikipédia, et à qui on doit répondre que ça n’a pas sa place sur le Wiktionnaire. Je crains que le phénomène ne fasse qu’empirer. [[user:Noé|Noé]] 29 mars 2022 à 12:37 (UTC)"'') == The "sticky table of contents" is the worst among all the bad changes == I am sorry, but this sticky table of contents is such an eyesore, its sole addition might make me quit reading Wikipedia altogether. I'm not exaggerating, a similar update to Liquipedia made me want to avoid that project. It's more than an annoying waste of screen space - it also makes the different parts of the table of contents bold depending on where in the article my screen is, and thus it triggers my OCD, and it simply irritates me. I hate these moving parts in forced mobile designs. > "The results of our 3rd prototype testing showed an overwhelming support for the proposed table of contents." Have they? I don't see any discussion here. > "The new table of contents will be persistent - users will have access to it at all times. It will also make it easier to understand the context of the page." Are the TikTok memes reality? Excuse me, but I don't randomly forget what page or section I'm reading, thus I don't need a sticky title on my screen at all times. > "In addition to that, it will be possible to navigate to different parts of the page without having to scroll all the way back to the top." How is that "need" in any way difficult? It's one button on the keyboard - called ''Home''. Or you hold the slider on the right and jerk it up in a millisecond. But I suspect I know where "scrolling" is an issue - on mobile phones. This entire update in an exercise in transitioning a fine desktop UI from the 2000s which I had an honour to fall in love with in the 2010s to the non-constructive, downgraded, annoying and irritating experience of mobile phones. Thankfully, not all projects choose to go this way. For an example of a new encyclopaedia with a traditional design, see the immensely popular Korean Namu Wiki. [[User:Adûnâi|Adûnâi]] ([[User talk:Adûnâi|talk]]) 12:53, 10 April 2022 (UTC) :100% agree. [[User:Football Lab|Football Lab]] ([[User talk:Football Lab|talk]]) 09:12, 26 June 2022 (UTC) == some feeback on the layout == I really like the preview, it is much cleaner, a few thoughts from viewing this on desktop (I saw the Blue whale article and the Potato article): # The 'in other projects' section is really nice, however I wonder what would be a sensible heirachy for this. Should it be contextual based on the topic or something else? Currently its suggesting me WikiNews which isn't relevant or a particularly well maintained Wikimedia Project. Also the other projects is more about navigating to other information on that topic, rather than being a tool, I wonder if it should be under the TOC instead? Its more about navigating information on the topic rather than using a tool. # I'm not sure if this is intended, the images sit on top of the sections instead of being displayed along the side the text, especially for portrait format images this creates a lot of empty space. # When logged out having the TOC on the left is really nice, works really well. But when I'm logged in the TOC is hidden under half of the tools but then the other half is on the right hand side is quite confusing. I realise this is a really difficult thing to organise, maybe it could live under the TOC? There isn't a clear deliniation between reading and contributing which is confusing. # The taxonomy templates at the bottom are pretty broken and make long lists, also lists within the Potato article lose their formatting meaning on the page for potato the list of synonyms is one column wide making a very long section which isn't going to useful for a general reader right in the middle of the article. [[User:John Cummings|John Cummings]] ([[User talk:John Cummings|talk]]) 18:03, 12 April 2022 (UTC) == I hate the new TOC == I was directed here from [[phab:T273473]].<br /><br />That left-of-the-article TOC is a horrible nightmare. I absolutely hate it. I would seriously avoid any website that forced it upon me. Can't scroll it out of sight, can't collapse it, can't disable it, takes up too much space, I hate it I hate it I hate it. This was the reason I switched back to Vector classic on beta cluster. (and if Vector classic gets it too I'll switch to Monobook, Timeless or just murder it with a userscript) I'm not much of a fan of Vector 2022 (but it's not a lost cause, just needs work), but this TOC pushed me over the edge.<br /><br />As a personal note: I rarely use the existing TOC. But I can scroll it out of sight so it doesn't bother me. If the TOC went completely missing tomorrow, I wouldn't miss it. Having this big, (to me) useless thing that contrasts with the main content (it's much darker) permanently in my field of vision greatly annoys me. And because of the fixed position, my banner blindness fails to kick in. This results in pure hatred for something that, on the face it, could seem innocuous. <span id="Alexis_Jazz:1650385558357:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 16:25, 19 April 2022 (UTC)</span> :I was not "directed" anywhere, I blundered onto here after finally finding information about this new skin. And let me be clear, APART from the ridiculous handling of the TOC, the new skin is great, precisely BECAUSE, before the TOC-debacle, this skin allowed me to get more of the article on the screen, and allowed me to hide the standard list of menu choices that I only need 0.something % of the time. :So, please, Please, PLEASE make that TOC hideable! It's perhaps (!) a great default for newbies, but it's a bloody nuisance for us who usually never use the TOC, and if we do, we know where to find it! [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 21:49, 25 April 2022 (UTC) ::I totally agree. [[Special:Contributions/185.53.157.151|185.53.157.151]] 08:13, 26 April 2022 (UTC) ::@[[User:Autokefal Dialytiker|Autokefal Dialytiker]], right, it's not that easy to get here. We'll put link to the project page on the list of available skins in preferences. The task is documented as [[phab:T307113|T307113]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:25, 28 April 2022 (UTC) :Hey @[[User:Alexis Jazz|Alexis Jazz]] - thanks for talking to us. It’s good to hear you were using Vector 2022. I hope that you will switch back to it. In terms of the table of contents, you raise good points. A lot has been happening since you wrote your comment, so my answer is longer than it would have been last week. :* The first version of the design was based on the feedback we got on our previous prototypes from readers and editors (see [[Reading/Web/Desktop Improvements/Repository/Sticky Header and Table of Contents User Testing#toc-intro|in-person reader & editor testing]] and [[Reading/Web/Desktop Improvements/Third prototype testing|on-wiki community testing]]). :* That said, we have not yet made the design final. We are working on different ideas for the visual design of the entire site. We'll make the main content of the page be the primary focus of attention, even when other navigational elements (such as the ToC) are present. If you’re interested in following along with that work, most of it will be tracked on [[phab:T301780|T301780]] and in subtasks of that ticket. :* We are also considering the way the ToC will display at smaller resolutions ([[phab:T306904|T306904]], [[phab:T306660|T306660]]) and looking into some options for collapsing it that could work for wider screens as well. :* As you can see, people like you who have chosen Vector 2022 individually share a lot of feedback with us now. [[phab:T307004|T307004]], [[phab:T306562|T306562]] are some examples on things we are or will be working on. :* In the meantime, we will be A/B testing the ToC on the pilot wikis. Our hypothesis is that the ToC will decrease the amount that people have to scroll to the top of the page to switch to a different section. The design might also vary once we have the results of the test. :* Since these changes might take a little while to reach the beta cluster, we would also encourage technically-skilled folks to set up a script or gadget to make a temporary solution. :And... yeah, [[Newsletter:Desktop Improvements updates|subscribe to our newsletter]], join our office hours ([[Reading/Web/Desktop Improvements/Updates/Talk to Web|tomorrow]] or [[Reading/Web/Desktop Improvements/Participate|later]]) and talk to us more. Thank you! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:23, 28 April 2022 (UTC) ::[[User:SGrabarczuk (WMF)|SGrabarczuk]], here's another thought: [[wikt:reverse]]. It's not a long page, but that TOC is so bloody huge a full HD display isn't enough to read ''any'' of the actual page content without scrolling. <span id="Alexis_Jazz:1651369145562:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 01:39, 1 May 2022 (UTC)</span> :::Right, right. Let's just take a look at [[:pl:Gramatyka języka fińskiego]]. I mean, this is an edge case, and as such, it's not that critical. From what I know, all TOC sections aren't uncollapsed by default, and you need to make an effort to see the full TOC. Is this your experience, too, @[[User:Alexis Jazz|Alexis Jazz]]? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:45, 5 May 2022 (UTC) ::::[[User:SGrabarczuk (WMF)|SGrabarczuk]], sorry for being possibly unclear. It was just a thought about the classic inline TOC which is disproportionally huge on Wiktionary, so it's something to think about when designing a new TOC. On the Gramatyka page on plwiki you at least get the intro without scrolling and the page actually ''is'' very long, so it's understandable the TOC also gets big. I've taken a look at the CSS (should have done that sooner) and simply disabling "position:sticky" stops the new TOC from being so infuriating. IMHO that should be the default, or at the very least, proper research should be done into this. Not only to determine by majority vote what users prefer (I wouldn't be surprised if sticky wins a binary majority vote) but also how crazy either option can drive users who ''don't'' like it. Pleasing a majority is no good if it causes a minority to be greatly aggravated. While I personally can get around it using technical means, that isn't true for most people. I'll also note that the experience on devices that are primarily controlled with a touchscreen may very well be different. With a keyboard, scrolling back up to the TOC is nearly no effort. Just press "home" or hold "page up". With a touchscreen, not so much, so I can see why sticky might have a greater appeal there. <span id="Alexis_Jazz:1651821096574:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 07:11, 6 May 2022 (UTC)</span> :::::What TOC? I don't get any such thing. [[User:Betaneptune|Betaneptune]] ([[User talk:Betaneptune|talk]]) 17:36, 25 May 2022 (UTC) :100% agree. [[User:Football Lab|Football Lab]] ([[User talk:Football Lab|talk]]) 09:14, 26 June 2022 (UTC) == Watchlist icon == [[User:Schierbecker|Schierbecker]] [[Topic:Wu23w3nlomndp5f1|wrote]]: <blockquote>The watchlist icon too closely resembles a hamburger menu button. I can see many clicking the button thinking it is a dropdown menu. Some may lose unsaved edits after clicking it.</blockquote> I completely agree, but not really because it resembles a hamburger button but because it's sandwiched (no pun intended!) between dynamic menus. If there was the dropdown arrow next to the interlangs, alerts and notices buttons just like the personal menu, it would communicate more clearly that the watchlist button is a simple link and not a menu. [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 02:38, 21 April 2022 (UTC) :Thanks for this comment, @[[User:Nardog|Nardog]]. We'll think how we could improve this. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:55, 27 April 2022 (UTC) ::Information on the design process that led to the current icon can be found here: ::https://phabricator.wikimedia.org/T297979 ::Nardog is already involved in that task. It's probably best to add this feedback there, as not all designers are reviewing this talk page. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 17:01, 6 July 2022 (UTC) == Sidepanel is bloated == Tonight size of left panel is increased too much. It covers more than ¼ screen now. https://imgur.com/3YJlcii Can I reduce size of panel, as it was before? [[User:Tucvbif|Tucvbif]] ([[User talk:Tucvbif|talk]]) 21:18, 25 April 2022 (UTC) : Agreed. I feel there's too much white space padding the left and right of the sidebar. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 00:53, 26 April 2022 (UTC) :@[[User:Tucvbif|Tucvbif]] @[[User:Tenryuu|Tenryuu]] thank you for these reports. It seems like you may have your browser window zoomed in, is that correct? Also, if you are able to please add any additional thoughts, needs, screenshots, and ideas to this task: https://phabricator.wikimedia.org/T306660. [[User:AHollender (WMF)|AHollender (WMF)]] ([[User talk:AHollender (WMF)|talk]]) 14:54, 26 April 2022 (UTC) ::No, my browser not using zoom. I using personal css with font-size 14pt, but when I login to other account without personal css, the sidepanel still terrible huge. ::https://imgur.com/l8bIrDF [[User:Tucvbif|Tucvbif]] ([[User talk:Tucvbif|talk]]) 15:07, 26 April 2022 (UTC) :: @[[User:AHollender (WMF)|AHollender (WMF)]]: Apologies, I should have clarified. The sidebar here is fine; the one at Wikipedia isn't. Resetting the zoom level on Wikipedia doesn't address the issue; there's still a lot of white space padding the element. I'll leave this discussion and focus on [[#I oppose the new sidebar/TOC]] and the mentioned Phabricator ticket, which describes my issue more accurately. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 15:10, 26 April 2022 (UTC) ::: The ambiguity and confusion evident from the preceding discussion suggests that the interface has become to complex. Aren't the original sidebar and TOC at the top of the page enough? Why change? Is another popup menu necessary to switch language? What about setting language in user preferences? Simplify, simplify, simplify. Regards, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|talk]]) 00:28, 25 May 2022 (UTC) == TOC limit doesn't work anymore == It seems that this "sidebar TOC" has different classes, making [[:en:Template:TOC limit]] doesn't work anymore. [[User:William Surya Permana|William Surya Permana]] ([[User talk:William Surya Permana|talk]]) 07:46, 26 April 2022 (UTC) :Templates can only control the content of an article so [[en:Template:TOC_limit/styles.css]] won't apply outside the article area so new classes won't help here. A magic word would need to be added so support this use case if important and time allows. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 15:37, 26 April 2022 (UTC) == I oppose the new sidebar/TOC == Please make it possible for the users to collapse the left sidebar/TOC or to reduce the white space size. I for one use a browser sidebar (Sidebery) as well as 150% or even bigger text size. Combined with the forced sidebar/TOC, the actual line length becomes much smaller than the recommended length. [[User:PeterTrompeter|PeterTrompeter]] ([[User talk:PeterTrompeter|talk]]) 08:43, 26 April 2022 (UTC) :Hi @[[User:PeterTrompeter|PeterTrompeter]] - thanks for your feedback. We're currently exploring better solutions for the ToC at narrow widths, which include the option of collapsing as well. Check out [[phab:T306660]] for the details and prototypes. It would be great to get your opinion on some of these. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:40, 26 April 2022 (UTC) ::I wonder about one thing: Who on earth thought that having such a monstrosity as that [pejorative snipped] TOC as a PERMANENT part of the skin would be a good idea ? I mean, having it pop up might be a useful thing for newbies (and I find even that a stretch of my imagination), but PERMANENTLY wasting space on a table of contents you consult perhaps once or twice per (long) article ? So KINDLY have it fixed to be hideable/collapsible so that we can get actual article contents on our screens. (One sidenote here: Apart from my blowout here - yes, I am aware that working on these projects is a chore, and despite my invectives here, I AM grateful for your efforts. It's just that this kind of stuff goes so completely against what would be the natural idea here, that I blow my top unnecessarily hard - people generally want to read the TEXT of the articles, so when a new skin development deliberately wastes space on the table of contents - ????? ) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 16:43, 26 April 2022 (UTC) :::Hey @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], we test all of the proposed changes. Editors and readers were strongly in support of this change. More details here: [[Reading/Web/Desktop Improvements/Features/Table of contents]]. Cheers, [[User:AHollender (WMF)|AHollender (WMF)]] ([[User talk:AHollender (WMF)|talk]]) 17:47, 26 April 2022 (UTC) ::::My question stands: Why having it there PERMANENTLY ??? Ok, I find something that's relevant for me to read; usually, I then want to READ just that; not the thread that led me there... So, why PERMANENTLY ??? [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 17:54, 26 April 2022 (UTC) == Public and private views... == While thinking about this, I was struck with what appears to me to be a central point of division here: This is not a question of how THE user interface should look like; but, rather, it is a question of what we should look like to anonymous users, and what choices should be available to those of us who log in ? Does that differentiation make sense ? (I should mention that I'm coming to this from Wikipedia, and that I have very little experience with the other projects.) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 19:14, 26 April 2022 (UTC) :Yeah @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], this makes sense. With the caveat that I don't know what central point of division you are referring to :D :At the moment, except for gadgets and such little tweaks, we aren't able to offer different interfaces for logged-out and logged-in users. Also, we can't make it possible to easily switch between different settings like dark/light mode, contrast versions, font sizes, etc. We need to improve the basics of the viewing/reading experience, we can do ''that'', so we're doing it. :As a result, readers use our interface more comfortably, we check that with regular A/B tests. As for the most dedicated editors, they can/should: :# Help us build an interface useful to them (by giving feedback on the prototypes, on the changing interface on "pilot wikis", by adjusting gadgets, etc.) :# Accept the arguments about the results of user testing, A/B testing, community feedback... :# Accept the "final" version as the basic version, and :# Configure it further if they want. :Our team would like to work the interface deeper. We would like to make it more modular and adjustable. (Of course, content would stay objectively the same for all.) A few months ago, we started working with more closely [[Growth]] and [[Editing]]. Now we're checking how ambitious we can be. :Does that answer your question? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:26, 27 April 2022 (UTC) ::My way of thinking here, is that the main divider here is between what should be visible and available to those who are NOT logged in, and what should be available and possible for those who DO log in. This is because the big difference between the two groups, is that those who are logged in, are also able to seek detailed information and make informed choices (and possibly programmed adaptations), whereas the non-logged in can not be trusted to have any particular information about the system, do not have a way of communicating preferences, and therefore needs to be given visual cues as to what's possible and available, precisely because they are strangers here... (Sidenote: I am of the Wikipedia, and that is the project I write in relation to; each project will have some peculiarities that do not apply to the other (to the same degree, at least); for this reason I should remember to mention this.) :: ::I hope what I'm writing here makes some sense, I try to avoid giving specific "orders" to anyone, but rather contribute to clarifying the context so that I understand it; hopefully, what I then write makes sense to others as well... (About here my subconscious can be heard muttering "and if pigs could fly"...) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 13:17, 9 May 2022 (UTC) == "Beginning" is confusing == More feedback: when I was at [[w:Gotcha journalism]] just now, I became confused because there appeared to be a section titled "beginning", which I assumed covered the early history of the term. It took me a minute to figure out that that wasn't referring to a section but rather a way to scroll to the top of the page. Many other articles are going to have a similar problem, since we often begin with history sections that might reasonably be titled "Beginning" for early history. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 22:42, 27 April 2022 (UTC) :@[[User:Sdkb|Sdkb]] - good catch! This is something we discussed quite a bit internally in order to finally settle on beginning, although I agree that it's still imperfect. Previously we were using "introduction". The issue there was that many articles have "introduction" as the name of their first section, causing duplication. Other options we were considering were location-based (back to top, beginning of page, etc). We are welcome to ideas on how to make this clearer. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 09:05, 28 April 2022 (UTC) ::The name used by wikipedians? ''Lead section'' in English, ''résumé introductif'' in French, etc ([[d:Q10966628|Q10966628]]) [[User:Pyb|Pyb]] ([[User talk:Pyb|talk]]) 11:07, 28 April 2022 (UTC) :::On Translatewiki.net I found "Début" for fr.wiki and "Inizio" for it.wiki (on it.wiki we use also "Incipit" or "Introduzione", see [[phab:T306990]]). [[User:Patafisik|Patafisik]] ([[User talk:Patafisik|talk]]) 15:09, 28 April 2022 (UTC) ::::@[[User:OVasileva (WMF)|OVasileva (WMF)]], did you consider different design approaches in addition to different names? If the word had been accompanied by something like [[File:Font Awesome 5 solid caret-up.svg|16px]], it might have been a lot clearer. I also think there's some benefit to matching the terminology we already use as editors ("lead section" or "introduction"), since that makes it easier for newcomers. The Wikipedia articles that currently have "Introduction" as their first named section should not—they should be tagged with [[w:Template:Overview section]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 20:16, 28 April 2022 (UTC) :::::<small>Bumping @[[User:OVasileva (WMF)|OVasileva (WMF)]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:16, 6 July 2022 (UTC)</small> ::::::Just leaving a note here that we're still watching this conversation and considering different options, but haven't made a decision yet. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:58, 11 July 2022 (UTC) ::I think using the article title would make the most sense, as the title is the uppermost heading in the article. That way the header that the reader arrives at always matches the one they've clicked on. (I'm sure "Beginning" is better than "Introduction," but it's not unheard of as a section title either: e.g. [[w:Creolization|Creolization]], [[w:Ashikaga shogunate|Ashikaga shogunate]], [[w:History of Carthage|History of Carthage]]. Is there any way to determine how often it's used?) [[User:Arms &#38; Hearts|Arms &#38; Hearts]] ([[User talk:Arms &#38; Hearts|talk]]) 19:35, 29 May 2022 (UTC) I think "Top" would be less confusing and generally make more sense as that seems to be the common English term for the top of the page. [[Special:Contributions/132.170.199.112|132.170.199.112]] 19:32, 22 June 2022 (UTC) == Table of contents below sidebar just doesn't work == On a broader note than the two pieces of feedback above, I have to say that my experience so far with the new table of contents has been really frustrating. As an editor, I use lots of the links in the left sidebar quite frequently, so I don't want to collapse it (and even if I did, the way it persists in whatever state you leave it in means that every time I used it it'd return). But preserving the left sidebar forces the table of contents below it, which is just awful. The number one time I want to use the ToC is when I first navigate to an article, and I either want to jump to a specific section or just to see what sections it has to get an overview. Forcing me to scroll to get to that information is extremely annoying, and if it's kept in the final version, I predict the outcry will be intense. You could resolve this either by retaining the old style ToC alongside the new (which would also solve the [[w:MOS:SANDWICH|sandwiching]] concerns I've previously raised) or by moving the ToC above the left sidebar. From your previews, I know you've been working on moving some stuff around and introducing pinning, so I hope this will be resolved in future iterations. But the initial version being introduced here is clearly not ready yet. Best, <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 22:53, 27 April 2022 (UTC) : For me it seems the table of contents and the sidebar seems to be two different things. On Wikipedia, I collapsed the sidebar and the table of contents still remain. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 03:09, 28 April 2022 (UTC) ::I want ToC collapsed too. But there is no way to do it. It uses almost 1/3 of my screen and makes reading very difficult.- [[User:Nizil Shah|Nizil Shah]] ([[User talk:Nizil Shah|talk]]) 05:32, 28 April 2022 (UTC) :::Same here. 14" Screen, collapsed sidebar menu, open only when needed. With the new TOC I cannot collapse the sidebar, it's just a toggle between navbar and TOC. I appreciate the effort and that it's a first attempt, but it definitely should be optional. And yes, I was involved in feedbacks and testing earlier. Regards [[User:Elya|Elya]] ([[User talk:Elya|talk]]) 14:24, 29 April 2022 (UTC) :::: +1, the TOC should be accessible from the top of the page, and collapsible (vertically; also horiz if it is making the sidebar too wide - many pages have section heads that are quite long). [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 17:35, 2 May 2022 (UTC) :::::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] and @[[User:OVasileva (WMF)|OVasileva (WMF)]], neither of you have replied here. This is a major concern, and I predict that if it is not addressed, it may single-handedly prevent the community from being willing to accept New Vector. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:14, 6 July 2022 (UTC) ::::::Hi @[[User:Sdkb|Sdkb]] - thanks for the ping! Currently, we're working on making the ToC collapsible, especially on narrow screens ([[phab:T306660]]). Collapsing it would allow for access further up in the page, but won't completely solve the issue you're describing. To make using both the sidebar and the table of contents a bit easier, we are planning two things. For logged-out users, we plan on collapsing the sidebar by default so that the table of contents will be shown further up in the page. We are also planning on separating the tools related to pages in a separate menu. This will significantly shorten the space for the sidebar, and create a clear definition between which tool acts on the page as a whole, and which one acts only on the page itself. In this example, this puts the ToC above the end of the introduction section, which is higher than the previous ToC location (admittedly, this will not be the case for all articles). ::::::[[File:Prototype_of_table_of_contents_and_tools_menu_for_desktop_Wikipedia.png|thumb|Prototype of table of contents and tools menu for desktop Wikipedia]] ::::::[[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 14:07, 11 July 2022 (UTC) :::::::Thanks for the reply, @[[User:OVasileva (WMF)|OVasileva (WMF)]]! Moving the tools elsewhere (ideally to a Twinkle-like menu) is something I certainly support and have been trying to set up since [[w:WP:SIDEBAR20|the 2020 revamp]], and it would help with this. Your screenshot appears to be from a standard resolution display rather than a widescreen display, so I can't tell whether it's going to help enough to ensure that the ToC will always be visible on a normal monitor with neither it nor the main menu collapsed. Getting to a point where that's the case will be essential for getting community consensus. :::::::Is there a reason you don't seem to be considering placing the ToC above the main menu? <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 23:49, 13 July 2022 (UTC) == About Google Docs and Zoom == {{Ping|SGrabarczuk (WMF)}} Thank you for the invitation I received for tomorrow's videcall since I was an interface admin and a developer! but sadly I cannot participate since I don't use Google Docs or Zoom for security reasons (partially related: [https://www.zdnet.com/article/us-senate-german-government-tell-staff-not-to-use-zoom/] [https://www.gnu.org/proprietary/malware-google.html]). I don't know if it could be useful but maybe in the future you may consider to land the doc on the wiki itself, or using Etherpad [https://etherpad.wikimedia.org/] when realtime is needed. To drop Zoom, maybe I can propose Jitsi Meeting [https://meet.jit.si/] that is gratis and libre and supports streaming on social network to support large audience. (Also [[Wikimedia Meet]] deserves a try and some feedback). [[User:Valerio Bozzolan|Valerio Bozzolan]] ([[User talk:Valerio Bozzolan|talk]]) 15:38, 28 April 2022 (UTC) :Hello @[[User:Valerio Bozzolan|Valerio Bozzolan]]. I understand your concerns and thank you for the language you use. I do appreciate that. As you may have realized, it isn't without a reason why we use these particular tools/platforms. :# Google Docs are used by the Foundation as the default tool for making internal notes and docs. We might, for the purposes of the office hours, replace it with Etherpad. There's a problem with the translations, though. Asking translators to update just one word, and waiting until they've done that, could be troublesome. This is why I can only commit to replace this if we make more changes to the announcement. (By the way, the announcement is [[Template:Reading/Web/Desktop Improvements/Office hours announcement|fully standardized]] and translated into 16 languages, some of which use declination or are not written in the Latin script.) :# We need our office hours to be technically (platform-wise) predictable. Although Jitsi is open source and Zoom is not, the latter is more effective. It has been widely used for online meetings in the movement. It's been used by the WMF for office hours with the CEO, Maryana; it's been used by affiliates. There are hundreds of Wikimedians who at least once have participated in a Wikimedia meeting on Zoom. We know how to provide live translations there. Jitsi, on the other hand, is less popular, and we'd have to learn how to support live translations, including more trainings organized specifically for our meetings. :# We may consider having office hours on IRC. Frankly, I have a feeling that since the migration from Freenode, IRC has been more and more marginalized, but we could give it a try. :I'm curious what other Wikimedians watching this page think. Add your comments! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:15, 5 May 2022 (UTC) ::Just asking for an understanding that Google Form and Zoom are a bug, not a feature, to participate in a Wikimedia project. A bug that deserves a long-term fix. [[User:Valerio Bozzolan|Valerio Bozzolan]] ([[User talk:Valerio Bozzolan|talk]]) 15:57, 7 May 2022 (UTC) ::: I appreciate these are standard across parts of the Foundation. And agree w/ [[user:Valerio Bozzolan|Valerio]] this is a bug, not a feature. Perhaps it's time to revisit this across the org. :) We should be using tools that can be constantly used and deployed by communities for events, workshops, office hours, talks without sending traffic through commercial servers. ::: ''Text'': Google makes some very wiki-spirited tools (they did absorb JotSpot back in 2006) so it's stayed around for a while. But we simply must stop using it as a crutch that keeps us from using and being delighted by notetaking on our own platform. Our collaborative platform for drafting and discussing documents. Our versioned, searchable platform. ::: ''Video'': I too have to use Zoom sometime, but I'm always surprised and a bit dismayed when a Wikimedia meeting uses it! Jitsi is stable, widely used + repackaged, easily modded and forked, and we host a [https://meet.wmcloud.org/ lovely instance] on the WM cloud. [We also regularly use BigBlueButton for larger audiences.] It makes it easy to name a persistent rooms, embed it it in other places or tools (see Jitsi-as-a-service + [[w:Brave Talk|Brave Talk]] these days), &c. We should be thinking about how to better use video streams in our projects, and using this framework as we do so. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 12:54, 14 May 2022 (UTC) ::::Thanks @[[User:Sj|Sj]] and @[[User:Valerio Bozzolan|Valerio Bozzolan]]. ::::# First of all, I really hear what you're saying. Perhaps you're right, Google and Zoom may be bugs - it's definitely not up to me to decide. "Perhaps it's time to revisit this across the org. :)" - I'm grateful that you specifically used the words "across the org". That's way wider than just Olga and me (people who organize ''our'' office hours), or [[m:Community Relations Specialists|Community Relations]] ("technical liaisons" so to speak), or [[m:Movement Communications|Movement Communications]] alone. If it's about ''the standard'', then it needs a broad agreement. ::::# @SJ, do Jitsi or any open-source alternatives provide the speech-to-text functionality and parallel voice tracks for live translators (interpreters)? I'm asking because each time we have a meeting, there are people who need the speech-to-text functionality . Unfortunately, we haven't been able to provide the live translation support yet. We're still working on it, and it seems we may have found a solution. ::::[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:55, 6 July 2022 (UTC) ::::: [[User:SGrabarczuk (WMF)|SGrabarczuk]]: :::::: 1. We ''should'' change the standard [though there seem to be many even within one org!], but I only mentioned that to suggest that none are set in stone. :) As this thread is about these particular discussions, I hope we can try a different standard for these sessions, or understand what prevents such a change. If it is purely a matter of accessibility features, that would make a phabulous ticket even if it is not yet known who could set them up. :::::: 2. Yes they do! Other collaborative orgs w/ similar issues of language equity use jitsi regularly. There are solutions or workarounds for both. [also, to the point of "supporting essential infrastructure for free knowledge", our engagement would certainly help make them better for all.] ::::: '''speech to text''': Google Voice integration seems to be there, and a number of open-source s2t services that are not quite comparable. You can see the range of Summer of Code [https://jitsi.org/gsoc/s2t/ projects] + community submissions scratching their own itches in the [https://github.com/jitsi/jigasi/issues/157 jigasi repo]. ::::: '''remote simultaneous interpretation''': the most recent solution (for a single language, letting you tune in or out of the raw audio and into a translator's audio channel) is use by [https://i.meet.mayfirst.org May First] (which we should [https://mayfirst.coop/en/ work more closely with] on choosing technology stacks, frankly) and is maintained [https://gitlab.com/mfmt/jsi here]. There are improvements, and pushes to integrate into jitsi core, both of which could be facilitated by small technical bounties or large expressions of interest [like Wikimedia indicating this is a crucial feature for us]. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 02:37, 7 July 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], I will not participate in any forum that is not public. Why the wmf foundation wants to share information via Zoom, a for-profit corporation which provides no guarantee of privacy, is anyone's guess. We have been using wiki-code for discussion since 2001, why this change? ::I apologize if you find my message above irrespecutful, but this represents the views of many. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|talk]]) 18:26, 13 June 2022 (UTC) :::@[[User:Ottawahitech|Ottawahitech]], above, you can find explanations on why we (the Web team) are using Zoom now. Are you also asking why we have any voice online meetings in general? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:57, 6 July 2022 (UTC) == Instant jumping vs. animated scrolling for table of contents == As you're polishing up the table of contents, one thing it'd be nice to consider is the behavior when you click on a section in it. Currently, it instantly jumps to that section, but I think it'd be better if it instead did a very quick scroll (maybe a quarter of a second). This would help readers to more easily understand what's happening when they click the link, and to get a better intuitive sense of what the article contains by seeing it flash by. Would that be possible? <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 02:37, 30 April 2022 (UTC) :<small>Bumping @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] and @[[User:OVasileva (WMF)|OVasileva (WMF)]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:12, 6 July 2022 (UTC)</small> == Wide-column + Multi-column options for large screens == Readers vary in what form factor they prefer, especially for long-form high-volume reading. That's part of why this change and research into 'optimal layout' is controversial. I'm someone who finds it hard and slow to read a narrow column and have to scroll all the time, including when searching a page for a term. General feedback on width: # Include a comfortable default for large screens. The (potentially large) gray margins on left and right, outside large white margins, bracketing a forced-maxwidth central column, do not feel good. Wide-col or multi-col could work. # Offer an explicit wide-column pref that doesn't require people to change skins, even if that is less aggressively supported/tested across all platforms. # A multi-column design for text within sections – mimicking the style of most long-form magazines and scholarly journals – would be interesting and can be surpassingly beautiful. That's what I'd like to see our wide-screen layouts transition to. We already do this within sections for references, lists, and galleries. Even low-end desktop monitors these days are high enough resolution to support two-column layouts. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 18:20, 2 May 2022 (UTC) == I think sticky elements ruin Vector == I liked vector a lot more when it didn't have the new distracting elements (sticky header and sticky TOC). ''I care about the contents of the page, not the interface'', nor about the need to scroll to the top of the page every now and then. [[User:Tokujin|Tokujin]] ([[User talk:Tokujin|talk]]) 17:50, 4 May 2022 (UTC) :Hello @[[User:Tokujin|Tokujin]]. Congratulations for finding this page :D You can add <code>.vector-sticky-header {display:none;}</code> to your [[metawiki:Special:MyPage/global.css|global.css]]. For now, I'm not entirely sure what to advise about the TOC, though. When the collapsible version has been deployed, we'll know what code you should use to make it not sticky and keep some other version. I invite you to revisit this topic in 2-3 weeks. :By the way, I very much liked the first sentence of [https://www.mediawiki.org/w/index.php?diff=prev&oldid=5009784 your comment to the third prototype]. Have you seen the [[Reading/Web/Desktop Improvements/Fourth prototype testing|fourth one]]? I encourage you to follow the instructions and share your opinion about it, too. (BTW, compare it with [https://di-collapsible-menus.web.app/Brown_bear the newest version, also a prototype].) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:28, 5 May 2022 (UTC) ::Hi Szymon :-) [[Reading/Web/Desktop_Improvements/Fourth_prototype_testing/Feedback#Username%3ATokujin|Done]], thank you. Regarding the global.css setting, notice that with sticky table headers enabled (in Preferences > Gadgets > Testing and development) there's a bug whereby in tables such as those in [https://en.wikipedia.org/wiki/List_of_Disenchantment_episodes#Part_4_(2022) this page] the table header leaves space for the absent page header. Other tables, such as that [https://en.wikipedia.org/wiki/Ninety-nine%20Novels here], don't have this issue. [[User:Tokujin|Tokujin]] ([[User talk:Tokujin|talk]]). 07:41, 9 May 2022 (UTC) == Skin differences between wikis == I'm using the 2022 Vector skin globally now (with [[:m:User:Tol/global.css|some modifications]] to remove whitespace), but I'm noticing that some wikis' sidebars are different from others. For example, MediaWiki wiki (this wiki) and French Wikipedia have a thinner white-background sidebar which sits on top of the page body (and ToC in the page body), while Meta-Wiki, Wikidata, and English Wikipedia have a wider grey-background box which is not layered on top of the page body (and ToC beneath said box). I can't figure out why this is. [[User:Tol|<span style="color:#f542d7">Tol</span>]] ([[User talk:Tol|talk]] &#124; [[Special:Contribs/Tol|contribs]]) @ 00:12, 8 May 2022 (UTC) :@[[User:Tol|Tol]] - thanks for your question, and good catch! This is due to the table of contents still needing to being A/B tested on some wikis (frwiki and mediawiki wiki being two of these). The ToC functionality is not yet available there. That said, we've began some work on reducing the margins for the ToC as a whole ([[phab:T307004]]) that will make the differences in width fairly negligible. This change will be on all wikis next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:31, 9 May 2022 (UTC) ::@[[User:OVasileva (WMF)|OVasileva (WMF)]]: Ah; looks great! I look forward to that change rolling out. Thanks! [[User:Tol|<span style="color:#f542d7">Tol</span>]] ([[User talk:Tol|talk]] &#124; [[Special:Contribs/Tol|contribs]]) @ 14:14, 9 May 2022 (UTC) == Tool bars and tables == Hi, thanks for the update. A few observations: # I would suggest that users have the option to keep the tool bar on the sidebar from the beginning, instead of having to click "tools" -> "[move to sidebar]" every single time. # The readability of tables and graphs that are wider than the (quite tight) text column is an issue. In certain cases, the tables represent time series data (e.g. population in a country or municipality over time) that cannot just be tightened. Do you have a proposal to solve this issue? The NYT, which is a site that you explicitly mention as inspiration, lets tables and images occupy the whole width of the screen if necessary. [[User:GeneraleAutunno|GeneraleAutunno]] ([[User talk:GeneraleAutunno|talk]]) 20:39, 8 May 2022 (UTC) == Next steps for the Table of Contents == Hey all - thank you for all the feedback around the issues you were experiencing with the ToC, especially on narrow screens. We've taken a few steps to fix some of these issues: * We're reducing the margins of the ToC to more closely resemble those of the prototype (tracked in [[phab:T307004]]) * We have a temporary solution for the ToC at narrow widths, which removes the ToC alltogether * We are building functionality to allow for the ToC to be collapsible and expandable at narrow widths (tracked in [[phab:T306660]]) * We are planning on making the ToC collapsible at all screen sizes and widths (tracked in [[phab:T307901]]) * https://di-collapsible-menus.web.app/Brown_bear links to a prototype that puts all of these changes together. We would appreciate your feedback and thoughts on the decisions made within the prototype and whether they work for you. Thanks! [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:38, 9 May 2022 (UTC) :cc @[[User:Lectrician1|Lectrician1]], @[[User:Alexis Jazz|Alexis Jazz]], @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], @[[User:Tenryuu|Tenryuu]], @[[User:Tucvbif|Tucvbif]], @[[User:Tokujin|Tokujin]] - in case you're interested. Apologies if I'm forgetting anyone else that was asking about this! [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:46, 9 May 2022 (UTC) ::[[User:OVasileva (WMF)|OVasileva]], thank you, it's a solid improvement! Just one request: can the hiding/unhiding be made persistent so my choice remains in effect even if I navigate to another page? <span id="Alexis_Jazz:1652099702223:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 12:35, 9 May 2022 (UTC)</span> ::Thank you, that's good news! (Adding a clarification: I'm responding to OVasileva, here.) My thinking is that making it collapsible is the only reasonable way to go; with the added point that for newcomers and anonymous readers it should perhaps be turned "on" as default; if the collapse button is clearly visible, the TOC will be useful to some, and easily removable for the rest, which should be the useful level of the intrusive/invisible conundrum... Thank you, once again. [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 13:02, 9 May 2022 (UTC) :: @[[User:OVasileva (WMF)|OVasileva (WMF)]]: Thanks for letting me know. Since this seems to be only in effect for the new Vector skin, maybe some work could be done to have the table of contents be shown in focus and have a button on the sticky header, as well as a keyboard shortcut for it? [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 14:07, 9 May 2022 (UTC) :Thanks for the work, I like the prototype a lot. I've missed the easily available overview that the ToC provides. Compare to the 2010 design, it is very useful to have the ToC available no matter how far down you scroll. :On small screens, the "move to sidebar" link text is not accurate with regards to what happens visually when you click on it. [[User:PeterTrompeter|PeterTrompeter]] ([[User talk:PeterTrompeter|talk]]) 16:51, 11 May 2022 (UTC) :On narrow screens this is still quite jarring, and having no TOC is a loss, being able to move the TOC back in to the body (dynamically and programmatically) seems a better compromise. A problem I see is that even when there is no TOC on a page, all that space it could use is still being consume by blank space, that wasted horizontal space needs to be able to be reclaimed somehow. We've been testing some options that are aimed at more power desktop '''editors''' so they can use vector-2022, but still have access to most of their screen (see [https://en.wikipedia.org/wiki/Hate_%C3%9Cber_Alles?useskin=vector-2022&withgadget=wide-vector-2022 example] (will really only be strikingly noticable if you are on a wide screen)) but still are getting complaints about the huge space used by the TOC. [[User:Xaosflux|Xaosflux]] ([[User talk:Xaosflux|talk]]) 11:40, 14 May 2022 (UTC) == Banners and roadmap == Hi, I think you should consider to add banners in order to present the restyling to a much wider part of users. IMO they should link to discussion and presentation pages. You should also consider to present to the wikis a clear roadmap with dates in order to present ahead of time big changes like the adoption of the new Vector. This two changes would make you work clearer to the eyes of the users and would prevent some dissatisfactions.<small> In particular I'd like to point out that [[:it:Wikipedia:Bar/Discussioni/La_nuova_interfaccia_desktop|what is happening on itwiki]] is being perceived as an imposition against the general consensus and I agree with the Italian users that are saying that forcing the adoption of the new skin is not the right way to act. These two are some ideas to widen the discussion, forcing something against the will of most will just radicalize the opposing positions even more.</small> -- [[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 11:44, 9 May 2022 (UTC) :<small>I just received the good piece of news that the adoption of the new skin has been delayed for itwiki and I thank you for this. But I still think that the two ideas that I presented above would be good tools to prevent something similar to happen again. ----[[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 11:58, 9 May 2022 (UTC)</small> :Thanks @[[User:WikiLuke|WikiLuke]]. These are great suggestions. :* Banners - [[phab:T304839|T304839]] - we've been working this for some time. Soon, the banner should be visible to some logged-in Vector users. They will be encouraged to switch to the new skin, and some time later, they'll see another banner with a link to this talk page. :* Links to the project page - [[phab:T307113|T307113]] - our idea was similar. We'll add a link to the list of skins in preferences. :* Roadmap - that's also a very good point. We'll consider how to present this to the community most effectively. :* Itwiki - we'll continue this topic on itwiki, alright? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:33, 9 May 2022 (UTC) ::Thank you for you consideration! :) <small>And speaking of itwiki of course we will continue the topic right there.</small> -- [[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 16:14, 9 May 2022 (UTC) == Sticky header 'dead zone' in articles with long lead sections == {{tracked|T307345}} Steps to reproduce: # Visit an article with at least a moderately long lead section (e.g., [[en:Charles de Gaulle]]). # Scroll down a little way. # Observe that the sticky header appears. # Scroll down a little further, so that the first heading appears, but not much further than that. # Observe that the sticky header vanishes. # Scroll down even further. # Observe that the sticky header re-appears. This does not seem like intended behaviour. I am testing on Firefox 100. [[User:FrankSpheres|FrankSpheres]] ([[User talk:FrankSpheres|talk]]) 04:14, 10 May 2022 (UTC) :Hi @[[User:FrankSpheres|FrankSpheres]] - thank you for your report! We already have a fix for this bug, tracked in [[phab:T307345|T307345]]. It will be available early next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 08:11, 10 May 2022 (UTC) == Feedback on new look == I like that stuff that is generally rarely used is hidden, such as the language picker. I am not a fan of moving the table of contents off the main article body section. I didn't even register that the table of contents was there and I frequently use the TOC to get an overview of interesting sections of articles. With the TOC being isolated at the side bar, it seems separated from the article itself, while it should be a central part. Maybe it would work better if it appeared on the right of the article, where there is currently just whitespace? Speaking of whitespace: I dislike the move to a max-width on article pages. This feature should at the very least be toggle-able with a button (without a need to log in). I feel like it makes the article feel more cramped, with less space for images and figures. There is already a very good solution to setting the effective width in the old view: Simply resize your window or zoom in on your browser. With the new look, I am forced to a max-width and I don't have a solution to control the width like I did before. Whitespace and the TOC did something beautiful together in the old look actually. The TOC conveniently visually separated the article lead section from the rest of the article by introducing white space, which I personally found very pleasing. The new look has the lead section blend in with the rest of the article. This makes the lead appear more daunting, while its purpose is to serve as a quicker summary. Perhaps the lead section should be followed by a larger piece of whitespace than is normally found above headings, so as to separate the lead from the rest as before? Finally I am quite sad to see that the Wikipedia globe logo is diminished - I really like the globe with the symbols and it doesn't look very good at low resolutions. I think the size of the globe was perfectly fine before. Besides, it seems there's plenty of space for it to have the same size as before so I'm kind of puzzled why this change was made in the first place. I will also say that the arrow next to the Wikipedia globe (the one to minimize the side bar) leads to an unfortunate usability flaw. I initially thought the arrow was supposed to take me back to the front page (it is right next to the logo and the leftward direction suggests a "back" action). But that is not what it does at all. So the arrow is kind of confusing at first. --[[User:SorteKanin|SorteKanin]] ([[User talk:SorteKanin|talk]]) 16:40, 13 May 2022 (UTC) == When testing the new skin, offer a one-click way to change back == The banners inviting users to test the new skin offer a one-click option that updates your skin to new Vector. The banner is then replaced with a message saying "give us feedback!", but it should also offer a one-click way to revert the change. Users may not be familiar with how to undo the change. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 12:56, 14 May 2022 (UTC) :The one-click option to revert is the final item of the sidebar's top section, in bold. Are you suggesting a second method should be included, or that the link should be made more obvious and flashy by moving to the banner? :The sidebar link seems fine to me. Particularly because this is less about the theme and more ergonomics for migration. [[User:Kees Person|Kees Person]] ([[User talk:Kees Person|talk]]) 15:34, 14 May 2022 (UTC) :: I found it eventually, thanks. Yes, putting it in the banner, or putting a js link in the banner that highlighted the sidebar link, would be clearer :) [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 19:59, 20 May 2022 (UTC) == Too little space == It's probably fine for those who don't use wide-screen monitors, but as someone who does it is quite annoying having everything mushed together like on mobile. I have read the page on this, but I think there should be a way to keep the functionality of the skin but lengthen the screen. [[User:Lallint|Lallint]] ([[User talk:Lallint|talk]]) 13:57, 14 May 2022 (UTC) : I concur. I tried the new skin a couple of times and just could not do it. I have bought a standalone monitor for a reason - and it's not that large anyway (1920 x 1200) - yet the new skin wastes a third of my screen space. [[User:Kashmiri|Kashmiri]] ([[User talk:Kashmiri|talk]]) 12:31, 20 May 2022 (UTC) ::Actually I use a 13" laptop and I initially thought that my computer switched to mobile version by mistake, but I later realized that was the desktop layout. I think the way everything is squeezed-in together takes away from the experience; there is nothing wrong with the header and tools bar they look fine to me, yet the sizing seems off for desktop users. [[User:Humanized|Humanized]] ([[User talk:Humanized|talk]]) 10:20, 24 May 2022 (UTC) == Sidebar too long == Sidebar too long and page too small on Wikimedia wikis [[User:LisafBia6531|LisafBia6531]] ([[User talk:LisafBia6531|talk]]) 16:24, 14 May 2022 (UTC) == Do not use a sticky header. == I think the new layout makes much better use of whitespace on 16:9 displays, making paragraphs easier to read. However, vertical space is someone no website that serves text-rich pages to users can ever get enough of. I believe that every (non-redundant, e.g. the article name is displayed twice on most browsers in the window tab title and the sticky header) element currently placed on the sticky header would not just fit on the sticky sidebar, but by removing the sticky header the layout will better serve what readers come to a wiki to do. As a side note though, I am awfully sentimental about the old Wikipedia header logo and type layout, that giant globe and the accompanying text beneath it is far too iconic to change in my opinion, even for a redesign. [[User:Saedes|Saedes]] ([[User talk:Saedes|talk]]) 14:18, 15 May 2022 (UTC) == Sidebar considerations for vertical monitors/half-width windows == I haven't tested this out thoroughly yet, but I'm going to be adding this section to start a discussion on how the new layout uses responsive design when display device/window aspect ratios are greater in height than width. [[User:Saedes|Saedes]] ([[User talk:Saedes|talk]]) 14:28, 15 May 2022 (UTC) == The table of contents is in the wrong place == It's nice to have a table of contents right there on the side so you can move back and forth between sections but i don't like the fact that you have to scroll down a bit to find it. If there's a way to keep it at the top of the page so you see it right as the page loads then as the user scrolls down it changes into a sticky header, that would be better. [[User:Abhaypradjha|Abhaypradjha]] ([[User talk:Abhaypradjha|talk]]) 10:04, 16 May 2022 (UTC) == Search bar UX is inefficient (Fitts's law) == I want to search. # If I am at the top of the article, I click mindlessly anywhere on the header and type straight away. # If I am down the article, I have to pinpoint an icon. This is bad because * The inconsistency turns my muscle memory against me * It goes against [[w:en:Fitts's_law#Implications_for_UI_design|Fitts's law]]: pinpointing an icon requires precision and is slower than clicking a large bar at the border of the screen without giving much thought into it. A solution would be that clicking on the article title or empty space in the sticky header hides the article title and displays the search bar (empty and focused). My case is that I often read the documents with the help of Wiktionary, so I use the search bar heavily and my usage pattern is fundamentally different than on Wikipedia. On Wiktionary, the interesting information is on one line or two, for each one of many unrelated entries, so searching is almost exclusively my means of navigation. [[User:Wanlpz|Wanlpz]] ([[User talk:Wanlpz|talk]]) 19:05, 17 May 2022 (UTC) == TOC: the position of the content == Hi, I like your [https://di-collapsible-menus.web.app/Brown_bear last prototype of TOC], in particular the blu color which helps to find a menu when you collapse it. I notice something I consider a bug: when the TOC is collapsed, if the tools menu is collapsed too the content is in the correct position, but if you move to the sidebar the tools, the content changes his position (it shifts on the left side). It feels strange. It doesn't happens when the TOC is on the sidebar, and you open/collapse the Tools menu.--[[Special:Contributions/151.42.0.114|151.42.0.114]] 13:17, 18 May 2022 (UTC) ==Sidebar== The sidebar has extended a bit (and by that, I mean a LOT) too far, which makes things very uncomfortable for me. I'm fine with the skin other than that, but the overintrusive sidebar is just awful. Plus, there are these white extensions to it that shouldn't be there. I hope you understand what I'm talking about, and at least take notes on it! [[User:ARandomPage|ARandomPage]] ([[User talk:ARandomPage|talk]]) 11:33, 19 May 2022 (UTC) == Зробіть для кожного коментатора окремий відділ == '''Привіт я досі не можу зрозуміти чому кожен коментатор не може писати окремо це набагато зручніше...''' '''Новий дизайн набагато простіший в візуальному плані але до нього треба звикати)))''' '''Також я побачив що новий дизайн не працює в деяких мовах''' [[User:Ilolg|Ilolg]] ([[User talk:Ilolg|talk]]) 14:34, 19 May 2022 (UTC) == Some incoherence == Hey there! To begin with, I want to make it clear I've got nothing against updating the desktop experience at all. I wanted to make it clear in case I seem like a person ranting something like, "Give me back my good old skin!121". What I think is that by making the skin you folks tried to reconcile the legacy appearance with some modernity. A good point, though the effect is not as optimistic. The top buttons (edit & history & etc) that retain the legacy shadowing do not fit in with the new cohesive background as seen in the left-hand sidebar. I'd consider re-adapting the former so that they better suit the new design. [[User:Mustafar29|Mustafar29]] ([[User talk:Mustafar29|talk]]) 10:05, 20 May 2022 (UTC) == A few more issues with the Page header vs Sticky header icons == Premise: I agree with the comments above that an update can only be a good thing; I'm sending kudos to all the teams working behind the scenes; and I only started using Vector 2022 a few weeks ago - noticing that it gets better each day. I'm not sure if the issues I'm having are slated to be improved or are haven't yet been considered. 1. Lack of coherence in the sticky header iconography I frequently work on the special pages where the sticky header is absent which makes it frustrating when I move to another page (article page) and it appears and then back to 'edit' or 'view the history' of a page and it disappears again. I feel that I should be able to move from page type to page type without noticing drastic changes in the header. 2. Order of icons and functionality is different between the sticky header and page header - specifically some items disappear completely, some move from one area to the next and others are simply re-ordered. (Until just now I thought the search bar had been remove but I just found it as an icon that was pushed to the extreme left hand side after the article title. Now I understand the others who said that with a 27" monitor the left side icons are essentially out of sight.) [[file:Headers-sticky-vs-page.jpg|600px]] * Examining the two headers more in detail we see that the icons seem to be in the same place which makes it hard to notice they are different. Starting from the right, we see that the icons are identical in both therefore, we naturally expect the two (people) dropdown menus to contian the same items. * Moving towards the left we see two icons with a star which pertain to the same semiotic sphere yet actually have different functionalities. One icon (that looks like a drop down menu but isn't) takes you to your watchlist while the other simply indicates whether the current page is on your watchlist and fuctions as a toggle to add the page if it isn't. There is a futher issue with how similar this icon is to the 'Contributions' icon, making it hard to distinguish for those of us who have bad eyesight - but that is an issue for another post. * Continuing to the left, the issue becomes more confusing. 'Your notices' from the page header disappears (or maybe I just haven't found it yet) and the text menu 'View history' moves into the sticky header as an icon -the tool tips are the same in both and they are basically in the same position onthe page, which helps a bit. * And with the final icons (still moving left) the 'Your alerts' bell disappears (or hasn't been found) and the 'Discussions about this page' transform from a text menu on the left into an icon on the right, at least the tooltip is the same. I have to admit that it's not clear to me why my user name is only visible on the page header and then moves under the person icon in the sticky header. It's not exactly a problem in itself, but it does add to the confusion of icons and functionality that seems to jump around from page to page. * Finally, it seems that the “Edit” and “Edit source” functions have disappeared along with the special menu items of “delete”, “purge” and “move” unless you scroll back up to the top of the page. I believe these issues have already been mentioned by others above. Again a big thanks to all of you working hard to update the interface and the 'restyling'. I hope when this is all finished, the sticky header will be unobtrusive and not noticeable like the ones normally found on modern webpages. --[[User:Lepido|Lepido]] ([[User talk:Lepido|talk]]) 21:07, 20 May 2022 (UTC) == Left menu too wide == The main menu on the left is too wide and makes the rest of the page appear too cramped in relation to the menu. [[User:Urban Versis 32|Urban Versis 32]] ([[User talk:Urban Versis 32|talk]]) 00:02, 24 May 2022 (UTC) == The TOC, again == It just makes all look too narrow and tight, at least to me. I've been working on various lists projects recently and now they all look god awful because they had the old look in mind. [[User:Tintero21|Tintero21]] ([[User talk:Tintero21|talk]]) 02:08, 24 May 2022 (UTC) ==I prefer the old version == It's cool but I prefer the old version. [[User:Super ninja2|Super ninja2]] ([[User talk:Super ninja2|talk]]) 07:18, 24 May 2022 (UTC) == suggestion: collapsible table of contents == the appearance of the site is far too narrow. i would suggest making the table of contents collpasible to the left. [[User:Lettherebedarklight|Lettherebedarklight]] ([[User talk:Lettherebedarklight|talk]]) 12:02, 24 May 2022 (UTC) : Me too. Also could be hidden, in options, so the user can read better the text. Now, it is too narrow and tight. --[[User:BoldLuis|BoldLuis]] ([[User talk:BoldLuis|talk]]) 13:04, 24 May 2022 (UTC) == Line under title colliding with coordinates == {{Tracked|T310369}} [[File:TitleLineColliding.png|thumb|alt=Gray horizontal line under the title colliding with coordinates given on top right of page]] See image. The horizontal line under the title collides with any coordinates that are displayed on the top right. --[[User:MimiKal797|MimiKal797]] ([[User talk:MimiKal797|talk]]) 14:56, 24 May 2022 (UTC) :Even I wanted to state this same issue. [[User:Excellenc1|Excellenc1]] ([[User talk:Excellenc1|talk]]) 16:00, 24 May 2022 (UTC) : Also the floating title can obscure content. For example, open the front page of [[b:Oberon|Oberon]] and scroll to the bottom. Click on instance "a" of footnote 43. That should take you to "MT, in V5, the constant address ...". In fact, the next glossary entry "native, modifies the name ..." is displayed. Not a terrible defect but baffling for a novice trying to learn. Thx, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|talk]]) 00:08, 25 May 2022 (UTC) ::I came here for a MeToo (about the coords/line collision). Classic Vector does not have the problem. Also, I think the languages dropdown is uncomfortably close to the coordinates; if you hover over that button you can see they overlap, which generates cruft when the dropdown is activated. Did anyone write up a ticket? [[User:DavidBrooks|DavidBrooks]] ([[User talk:DavidBrooks|talk]]) 15:35, 9 June 2022 (UTC) - OK, I did: T310369 [[User:DavidBrooks|DavidBrooks]] ([[User talk:DavidBrooks|talk]]) 15:19, 10 June 2022 (UTC) :::This is being discussed in [[:en:Template talk:Coord#Coordinates bad positioning]]. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:32, 10 June 2022 (UTC) == Great GUI == Everything looks very appealing to me. I think the blank left space really aids in reading as the width of the line reduces its easier for me to not to confuse the line which I have to read next. Overall I loved it. One suggestion that I want to give is that it would be very nice if you could change the visual of the tab. It looks a little too classic to me and would be very nice of you if you could add dark mode ( I don't know if it already exists), this I think would give a very appealing look to the website . Thank You. [[Special:Contributions/]] 17:59, 24 May 2022 (UTC) : If you ever want to reduce the width of the lines you are reading, I suggest you just resize your window, as the elegance of desktop browsing is that it gives you control over the size of the page. As for me, this layout takes away that control. Using it, I can no longer read an article with the full width of my screen without fiddling with my common.css, a luxury that would not be available to me when I'm not logged in, and am instead forced to use ~2/3 of that width, even when the window is reaching into every corner of my screen. There are several ways of using dark mode on wikipedia listed [[wikipedia:Wikipedia:Dark_mode|here]], but I agree it should be made easier. --[[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 16:42, 25 May 2022 (UTC) == Feedback == I was prompted to give some feedback on the 2022 Vector skin, and I have to say that it needs a bit more work. * The mix of new and old UI elements doesn't look good; specifically the View, Edit, Edit Source etc. menu bar looks out of place among the flatter new UI * There's uneven and unnecessary padding around the left pane with the many links that can be filled with the pane * There should be an option to have the content filling any display larger than 4:3, as most displays are 16:9. I understand the argument that it helps some people in reading but having an option is better, as it doesn't help ''all'' people. Additionally, a poll should be run in all Wikimedia projects on which one should be the default (4:3 or full width) — [[User:Dimsar01|Dimsar01]] ([[User talk:Dimsar01|talk]]) 23:33, 24 May 2022 (UTC) Here is My feedback *I see that the sections are not properly sectioned on the screen *I am using dark mode and when I want to add reference or qualifier or something like that, I see a white suggestion screen All in all I can say for now is that I really needs more work done and I can prefer the older one for now thank you [[User:Micheal Kaluba|Micheal Kaluba]] ([[User talk:Micheal Kaluba|talk]]) 05:58, 26 May 2022 (UTC) == Short description == It would be great to have the short description visible on pages, like it is on the search and on mobile, so users can more easily edit them and identify information. Like said by other users, the mix of new and old UI looks bad. The [https://di-article-tools-2.web.app/Blue_whale most recent prototype], for all its faults, had a well unified UI. I also think that the page tools (and "In other projects") should be separated from links for the whole website like was done in the [https://di-article-tools-2.web.app/Blue_whale most recent prototype], though there were many flaws with that execution (see [[Reading/Web/Desktop Improvements/Fourth prototype testing/Feedback#User: BappleBusiness|my comments]]), and all those links should be condensed by default. "Beginning" should definitely be named "Lead" or "Lead section", like said by others. I really appreciate the effort that is going into this. I think the vast majority of these changes are for the better, it just needs more work. [[User:BappleBusiness|BappleBusiness]] ([[User talk:BappleBusiness|talk]]) 00:32, 25 May 2022 (UTC) == Software Gore == [[File:Languages on Wiktionary with new layout.png|thumb|Software gore]] This is pure software gore. If you want to explain to me why it's like this, you're wasting your breath. I've edited Wiktionary for over a decade and I understand how it's come to look like this, and I don't even have a solution to propose. But I feel terrible for anyone trying to navigate this mess for the first time. —[[User:Pengo|Pengo]] ([[User talk:Pengo|talk]]) 00:54, 25 May 2022 (UTC) == Watchlist tooltip == Hi folks! I'm vaguely used to the watchlist icon (since I've switched themes many times over the past decade or so, and use the mobile app/website), but I still need to resort to the tooltips when I'm on my desktop. It would seem I'm not the only one that takes a moment to mentally translate the icon to the concept in my brain (per {{ping|Nardog}}'s earlier [[#Watchlist icon]] comment). I may stay with "Vector 2022" over on [[commons:Main_page|commons.wikimedia.org]] after trying it out for a bit, but please: could y'all change the tooltip so that the word "watchlist" is in the tooltip? Currently, the icon sports the the very verbose tooltip: "''A list of pages you are monitoring for changes [Alt+Shift+I]''", which takes a moment for me to mentally translate into "''oh, they're trying to say 'Watchlist'!''". It would be helpful if (in addition to the keyboard shortcut), the tooltip also gave the mental shortcut, perhaps with the phrase: "''Watchlist: your list of pages to monitor for changes [Alt+Shift+I]''". Since I'm guessing y'all aren't changing "watchlist" to another word, I can imagine it would be helpful for new users too. -- [[User:RobLa|RobLa]] ([[User talk:RobLa|talk]]) 04:12, 25 May 2022 (UTC) :Yeah, given all the other tooltips are just "Your alerts", "Your notices", and "User menu", it seems to me it should be simply "Watchlist" or at best "Your watchlist". [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 04:22, 25 May 2022 (UTC) == I want the code to make the sidebar TOC disappear == Please. Ping me. [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 05:46, 25 May 2022 (UTC) It's probably not too hard since there seems to still be a {{tag|mw:tocplace}} element left -- you need to grab the element, move it back and do some style fixups. Kinda like [[w:zh:User:Artoria2e5/Gadget-sidetoc.js]] but backwards. --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:43, 26 May 2022 (UTC) Ah well, I am pretty convinced that having {{tag|mw:tocplace}} but not the actual TOC hidden there is a bug now. If that gets fixed, it should be just some CSS work in your vector-2022.css: <pre> #mw-panel-toc {display:none;} #toc {display:block;} </pre> May need to sprinkle on a bit of !important. ping [[User:Bageense|Bageense]] --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:55, 26 May 2022 (UTC) :Yep, TOC disappeared, leaving a blank space. [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 16:55, 26 May 2022 (UTC) ::Well, just gotta wait until they come to their senses. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 00:55, 27 May 2022 (UTC) == Space for article too narrow == The article took up less than the full width of the screen in the old skin, but the increased padding and needlessly wide sidebar here make the usable region even smaller. This just reproduces the issues that have had to be worked-around on mobile, including some tables being too wide to fit in the space and causing horizontal scrolling, creating the need to scroll further to get between sections, as well as causing some large image thumbs to squish the article text into narrow strips. In my opinion, the sidebar, which I think most readers rarely make use of anyway, should be consigned to a modal rather than taking up even more space, so that the article can appear centred all the way down the page. This would make room for fairly wide margins on either side without causing as many issues. (I suggest this because it seems the most noticeable "improvement" here is the addition of extra whitespace, but really, what is wrong with making full use of the window width you are given?) [[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 15:50, 25 May 2022 (UTC) : I came here to complain about the same thing - limiting the width of the pageview doesn't make sense when you have a lot of text to display. Especially the discussions became harder to read. [[Special:Contributions/78.11.223.83|78.11.223.83]] 06:29, 26 May 2022 (UTC) == TOC should make the page slowly scroll to the right section, and not just jump == By the way, I'm still waiting for the code necessary to deactivate the lateral TOC. I've already disabled the sticky header by using .vector-sticky-header {display:none;} [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 07:51, 26 May 2022 (UTC) :That would make it take longer to get where you want to be, and prevent the user from scrolling during the time the page is sliding. The current TOC works using anchors linked to IDs, which means you can get back to where you were by simply paging back, but this, I think, would not be possible if the links were actually buttons triggering JavaScript animations. [[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 08:14, 26 May 2022 (UTC) == TOC not appearing at all == It seems that Vector 2022 is not showing ''any'' TOC -- neither the regular one nor the side one -- when it probably should. I noticed this issue about a couple of days ago but assumed it was an error on my side. Today I checked out [[w:Dmitri_Shostakovich]], tried to add a <code>_<nowiki>_TOC__</nowiki></code> magic word, found out it does nothing, and then realized it's the skin that's broken when I retried in a logged out private tab. In a private tab: * https://en.wikipedia.org/wiki/Dmitri_Shostakovich?useskin=vector-2022 has no TOC right now, but * https://en.wikipedia.org/wiki/Dmitri_Shostakovich?useskin=vector has a TOC. What's going on here? [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:35, 26 May 2022 (UTC) :One refresh later it's showing the side one. I must be descending into some sort of madness. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:37, 26 May 2022 (UTC) ::Annd it's gone again. No outstanding errors in the console. Seems to be sone <code>@media screen { ... .sidebar-toc {display:none; ...</code> in one of the many load.php's ([https://en.wikipedia.org/w/load.php?lang=en&modules=ext.cite.styles%7Cext.echo.styles.badge%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cjquery.makeCollapsible.styles%7Cmediawiki.ui.button%2Cicon%7Coojs-ui.styles.icons-alerts%7Cskins.vector.icons%2Cstyles%7Cwikibase.client.init&only=styles&skin=vector-2022]). What. the. heck. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:48, 26 May 2022 (UTC) ::The intention of the code seems to be to show the sidebar only for screens wider than a value. That's a good idea, but only if the original TOC is not removed! --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:50, 26 May 2022 (UTC) == Bold, yet very appreciated changes == At first I didn't like it. My first thought was that it took more space, so I got less content in my screen. I compared it side by side with the old skin and in fact, elements got more margin. But after giving it a try, reading and moving through the article, I fell in love. I really like that the TOC is now on the left and moves along with the page. It was OK before but now it feels fancy. And I feel more people are going to benefit from it now. The cleaner, more "plain white" look is nice. I understand the decision of limiting the width of the page on (very) wide screens. In my opinion, it is a sensible design decision that improves readability. Because if lines get too wide, it can make it harder to read. Maybe this "max-width" setting can become a thing users can tweak? I tested this new skin on a modern computer and a 1440p screen. If I were to use my old laptop, I'm sure I'd like to have the option to change to the old skin. As it fits more content and uses less CPU resources. I appreciate this changes, and feel they are for the better. Thank you! -- [[User:Zazke grt|Zazke grt]] ([[User talk:Zazke grt|talk]]) 06:42, 27 May 2022 (UTC) : I've temporarily switched back to the old Vector skin in Wikipedia because some pages like this one [https://en.wikipedia.org/wiki/Portal:Video%20games Wikipedia:Portal:Video_games] have their contents very croped or overflowing their boxes. --[[User:Zazke grt|Zazke grt]] ([[User talk:Zazke grt|talk]]) 06:49, 28 May 2022 (UTC) == TOC not immediately visible == {{Tracked|T309632}} I am going to refrain from complaining too much as I'm prone to do with any and all UI changes :) However, I do find the placement of the TOC particularly problematic. Personally the first thing I do when landing on a Wikipedia article is, usually, click on something in the TOC. Having to scroll down first to find it is, to me, very frustrating. [[User:Argymeg|Argymeg]] ([[User talk:Argymeg|talk]]) 12:24, 27 May 2022 (UTC) == Better font for Arabic/Persian فونت بهتر برای فارسی/عربی == As a Persian user, I think font of wikipedia is not good for these languages; Maybe Vazirmatn or other open-source good looking fonts could be better. به عنوان یک کاربر ایرانی، من فکر می‌کنم که فونت ویکی‌پدیا برای فارسی و عربی جالب نیست؛ شاید وزیرمتن یا سایر فونت‌های منبع‌باز که ظاهری خوبی دارند انتخاب‌های بهتری باشند. [[User:Amiria703|Amiria703]] ([[User talk:Amiria703|talk]]) 22:27, 27 May 2022 (UTC) == It seems like the Page Previews isn't working for me here == Although the new skin looks more sleek, I can't use the (very useful) feature of Page Previews here. So every time I'm in for a deep read, I have to switch back to the old look. Please implement the page previews here too. [[User:SamyakShirsh|SamyakShirsh]] ([[User talk:SamyakShirsh|talk]]) 03:31, 29 May 2022 (UTC) :Hi there! Thanks for the report! Could I get some more information on this issue? Page previews is working for me on both Vector and Vector 2022 skin. Are you talking about the user gadget https://en.wikipedia.org/wiki/Wikipedia:Tools/Navigation_popups ? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:28, 1 June 2022 (UTC) == Use the white page on the right for TOC and navigation == The mobie version of wikipedia app has this really nice way of navigating through sections by swiping eight. I think you can imlement this in the desktop by placing the toc on the right [[User:SamyakShirsh|SamyakShirsh]] ([[User talk:SamyakShirsh|talk]]) 03:35, 29 May 2022 (UTC) == Lone value inside calc() == The style sheet of the new sticky table of contents uses <code>.mw-table-of-contents-container { top: calc(-2em); }</code>. Is there a reason for putting a lone value inside <code>calc()</code>? [[User:Anerisys|Anerisys]] ([[User talk:Anerisys|talk]]) 09:22, 29 May 2022 (UTC) :Thanks for flagging. :The patch introducing this is: :https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/789691/5/resources/skins.vector.styles/layouts/screen.less :The use of calc is accidental, and I think a mix up our end with the appropriate LESS mixin. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:40, 1 June 2022 (UTC) == Trouble With Zooming In == My vision is poor so I usually zoom to 200% on my browser and it is no problem. With the new skin that same magnification causes the sidebar to take up the top of my screen and I can't see the title of the article and know what page I'm on without scrolling. == Opt-in/out for page tools? == There've been a few discussions on this page about the page tools links, but one possibility I haven't seen mentioned here or at [[Reading/Web/Desktop Improvements/Features/Page tools]] is providing a way for each reader/editor to choose which links appear. For example, I use "what links here" quite a lot, "related changes" and "random article" occasionally, and all the others virtually never. Other editors will have different experiences. How about allowing us to reduce clutter by choosing what we want to keep in the menu and what we can do without? [[User:Arms &#38; Hearts|Arms &#38; Hearts]] ([[User talk:Arms &#38; Hearts|talk]]) 19:47, 29 May 2022 (UTC) :+1. I just want to say this was the last straw that made me force legacy Vector on all sites in GlobalPreferences. Is there no opt-out aside from putting <code>tableofcontents=0</code> in the URL? No "Expand all" button? Why is there a blank space beneath the ToC? Why fade it out rather than show as much as possible? This is just user-hostile. [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 16:16, 31 May 2022 (UTC) == Tabs misaligned? == The tabs on the left seem to be next to the tabs on the right, as depicted [https://imgur.com/UfeemZ1 here]. This wasn't the case last week; should this be reported here or elsewhere? Please move if need be. [[User:Ifly6|Ifly6]] ([[User talk:Ifly6|talk]]) 07:01, 31 May 2022 (UTC) :: Hi there, could I get a little more information on this one? What browser and device are you using? Are you viewing this on a mobile phone by any chance? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:23, 1 June 2022 (UTC) == TOC hidden for some reason == {{Tracked|T309632}} When I put my Wikipedia tab to one side at half-width, which I often do whilst multitasking, the TOC disappears for some reason, even though the other side menu (which is the same width as the TOC) stays? I am clueless as to why. All article text is pushed way to the right for some reason. It would make more sense for it to be centred on all screen widths, or to make the entirety of the left menu a solid colour like it was before. Basically, the sidebar should be made thinner as the tab width decreases. Also the lack of a TOC below the lead results in images fighting for space with the infoboxes of articles. There should definitely be an option to move the TOC to where it normally resides as I and likely a lot of other editors find that placement more intuitive. [[User:Miklogfeather|Miklogfeather]] ([[User talk:Miklogfeather|talk]]) 16:06, 31 May 2022 (UTC) :My whole left sidebar has disappeared this morning. I had to switch themes just to get some editing done. — [[User:Xenophore|Xenophore]] ([[User talk:Xenophore|talk]]) 19:42, 6 June 2022 (UTC) == My many criticisms with this == Since it seems like Miraheze is also going to be using this new Vector skin as its default, I would like to offer mine and a lot of other users' criticisms with this new skin: * First of all, the unnecessary dead space. The actual content space is now more narrow and there is a ton of dead space. * The user menu is now completely messed up. The log in button and talk and contribution buttons are hidden behind the three dots, even though those are the most important buttons and should be readily available. In fact, there is no need for anything to be hidden. * The giant TOC in the sidebar. It serves no purpose and just further limits content space. I fail to see how exactly this is an "improvement". Also, the current layout of the skin looks nothing like what is described on the page. There is nothing about a smaller user menu. Currently, the new skin just feels off to me, and I would prefer that this skin be currently branded as "experimental", since it is far from finished. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 21:41, 5 June 2022 (UTC) :I'm fine with everything except the user menu changes and content width changes. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 21:50, 5 June 2022 (UTC) ::Hello @[[User:Blubabluba9990|Blubabluba9990]]. Have you maybe read our documentation where we present the reasons why particular changes are needed, why we've introduced the limited width, and what we're taking into consideration regarding how to use the unused space? I invite you to explore [[Reading/Web/Desktop Improvements/Features|this page]] and its sub-pages. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 19:11, 8 June 2022 (UTC) :::I already did. I read through them more thoroughly and while some seem like a good idea on paper, the user menu and limited width do not really seem to be an "improvement", as there are now extra steps involved. The user menu is the most important thing for me and many users, and now I have to click on a separate button to log in. Maybe less limited width, since right now 1/4 of the screen is just empty space with the new skin. I still use the original Vector as my personal default, but I usually browse logged out. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 22:40, 8 June 2022 (UTC) == Wikistories == Will Vector 2022 be influenced by [[Wikistories]]? --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:09, 6 June 2022 (UTC) :@[[User:NGC 54|NGC 54]], what do you mean by influenced? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:18, 14 June 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: If Vector 2022 will be adapted for (compatible from a design perspective with) Wikistories. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:06, 15 June 2022 (UTC) :::@[[User:NGC 54|NGC 54]], definitely. All the projects that currently are being built are compatible with or neutral to Vector 2022. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:47, 30 June 2022 (UTC) == Visibility Suggestions == Hi, first of all thanks for the work and the nice redesign. I really prefer it over the old vector look already. I use Wikipedia mainly to get an overview or better intuition about topics related to my studies. For me, I prefer the narrower text for better readability and the persistent TOC on the left side of the screen. Makes reading complex pages a lot less painful with easy access to quick navigation. I have some suggestions for the default behaviour of the current design: * There should be an '''option to collapse the navigation sidebar/area''' by default (the area which contains ''Main page'', ''Contents'', ''Current events'' etc.). I am one of those people who rarely uses any of those links. * More of an issue is due to this: The '''TOC is not always immediately visible as the navigation sidebar pushes it too far down.''' Perhaps move the sidebar to somewhere else or make it collapsible by default as suggested? * Additionally, It '''should be more obvious that the navigation sidebar/area is collapsible.''' Currently the toggle is kind of far and disconnected from the area. I only found this out after wondering what that arrow ''<<'' meant. * A nice addition would be to add '''more obvious indicators for current position in the TOC''' (loved this new feature the most!). I think right now the text of the current headline is just black. It would be cool if there was some highlighting or perhaps a dot to make it easier to see at a quick glance. [[User:Devin.halsted|Devin.halsted]] ([[User talk:Devin.halsted|talk]]) 11:21, 8 June 2022 (UTC) :I just noticed, that the toggling of the '''navigation sidebar/area''' does indeed persist. I just didn't notice because i switched between too many tabs. :Something other I noticed, is perhaps that would be good for '''scrollable TOC''' to be more visibly "scrollable"? Right now there is no indication except that maybe some text is cut off. [[User:Devin.halsted|Devin.halsted]] ([[User talk:Devin.halsted|talk]]) 11:27, 8 June 2022 (UTC) == Fifth prototype testing == :''Moved from [[Topic:Wx2jt9he9u1ipkpb]]'' Nothing about sticky header? The order of icons, the present icons for IPs, etc. [[User:NGC 54|NGC 54]] ([[User talk:NGC 54|talk]]) 17:08, 8 June 2022 (UTC) : Thanks for this comment, [[User:NGC 54|NGC 54]]. As we explain on the [[Reading/Web/Desktop Improvements/Fifth prototype testing|page of the fifth round of prototype testing]], that round will only be dedicated to considerations around the visual design. Pure aesthetics. The order of icons, selection of icons for IP etc., are functional considerations which may be discussed right here, on this talk page, regardless of the 5th prototype testing. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:38, 8 June 2022 (UTC) == General Feedback on Sidebar == I agree with other feedback that complains about the sidebar being to wide. This is a waste of space, please reduce the width a bit. However, I think it's not the width of the container but the left margin that makes people (including myself) upset. Therefore, I suggest to completely get rid of the left padding of the main container. Also please reduce the left margin of the article container to just 10 or 20 px. Even more space is wasted if the side bar is collapsed: Why is the sidebar positioned higher than ToC? This leaves free space on top of it. You discussed that the lines of text would be too long otherwise. You could significantly reduce the length if you moved the side bar from the left side to right. You then would have (from left to right) ToC, article, sidebar. Furthermore, the ToC should be on top of the other sections because for most people, ToC is more important than the other links. Although I understand the intention behind this to invite more people to contribute to Wikipedia, I still don't like it. [[User:GeographyMasterDE|GeographyMasterDE]] ([[User talk:GeographyMasterDE|talk]]) 09:16, 9 June 2022 (UTC) == JPG screenshots == Just to point out that [[Reading/Web/Desktop_Improvements|this page]], in which supposed design gurus are offering a lifeline to a wikipedia supposedly plagued by unsofisticated looks, is illustrated with screenshots saved in JPEG format… [[User:Tuvalkin|Tuvalkin]] ([[User talk:Tuvalkin|talk]]) 14:33, 9 June 2022 (UTC) == Limited Content Width == I want to state my opposition the limited content width. I understand the research that the narrower format improves readability. However, there are number of good reasons not to adopt the change: * Yes, [[Reading/Web/Desktop Improvements/Features/Limiting content width#Popular sites with limited width|many sites]] do use fixed width content, but in many cases their motivation is to use the space to sell advertising – a function not befitting Wikimedia. (Some news sites, such as those run by [http://www.gannett.com Gannett] have even taken the theory one step further and display all their articles as overlays – meaning that if a user accidentally clicks in the shadowed area on either side, they are frustratingly taken back to the homepage.) For this reason, full width content suggests a more reputable website. It implies a dedication to the facts, rather than attempting to fill the page with flashy content. (A [http://motherfuckingwebsite.com different website] has a more profane take on the concept. It doesn't deal directly with the issue at hand, but the underlying issue is the same.) This change just seems like another case of mobile overoptimization. * Additionally, as correctly the noted at the [[Reading/Web/Desktop Improvements/Features/Limiting content width#Additional notes|end of the page on the change]] is "part of what makes Wikipedia, and other Wikimedia wikis, a powerful tool for sharing knowledge is that there are very few constraints on how information is presented." For example, it's the reason that widths are specified in "ems" rather than number of columns in the [http://en.wikipedia.org/wiki/Template:Div_col div col template]. Don't get me wrong, I very strongly appreciate the [[Reading/Web/Desktop Improvements/Features/Limiting content width#Establishing a common reading experience|need for a common standard]]. I have [http://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Aviation/Style_guide#Proposed_Aircraft_Manufacture_Aircraft_Section_Table fought for it] on Wikipedia. However, this is not the place for it. * It is clear to me that the majority of commenters here strongly oppose limited content width. It is not to be confused with people just being afraid of change. Note that there are far fewer complaints with most of the other proposed features. I don't have access to the survey results, but a [[Reading/Web/Desktop Improvements/Repository/First Prototype Feedback Report#Summary of results|sample size of 230 users]] seems exceedingly small for such a major change. Furthermore, the commenters here are likely to a better representation of the dedicated portion of the userbase, as they took the time to respond here. I would like to end by stating I am not completely opposed to the change. However, it should only be ''opt-in'', not the default skin. –[[User:Noha307|Noha307]] ([[User talk:Noha307|talk]]) 03:23, 10 June 2022 (UTC) == Width and font size and color == As above, I don't like adding so much margin around the sides, or punishing people with large monitors by forcing them to change skins (which is not easy for everyone). If you are set on fixed-width columns, find a way to wrap columns within a section for wide screens :) rather than leaving huge vistas blank. I like the move to slightly larger font. The link color changes are most welcome. The purple could be a bit more red, to make it less pastel. Good to have a combination of "high contrast w/ other text" and "doesn't wash out on displays or projection in bright areas". [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 00:27, 11 June 2022 (UTC) == Section number in new ToC == I noticed that there is no section number in the new ToC. I hope the section number will be added again because I can quickly see how many topics there are on the talk page. [[User:Bluehill|Bluehill]] ([[User talk:Bluehill|talk]]) 07:28, 11 June 2022 (UTC) == Move infoboxes out of the text area == Given that we are limiting the space for text and freeing up space on the sides, it seems to me that it would be much better to move the infoboxes to the left side, and stretch the text to its full width. Like this: https://znaniya.org/c/pushkin-aleksandr-sergeevich-8cab44. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 23:50, 11 June 2022 (UTC) : I second this. Such a shame that this request is already explicitly [[Reading/Web/Desktop_Improvements/Frequently_asked_questions#Will_you_improve_charts,_maps,_a-/f-/o-/tmboxes,_infoboxes,_navboxes,_other_templates?|rejected in the FAQ]]. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:15, 14 June 2022 (UTC) :@[[User:Iniquity|Iniquity]] & @[[User:Adamant.pwn|Adamant.pwn]], generally, we agree that it is a nice idea. From a reader's standpoint, infoboxes aren't pure content - rather, these are metadata and could totally work as something put next to the content area. However, these are absolutely content from the technical point of view (because these are regular templates). This issue makes it... impossible? to move them. For underlying infrastructural/back-end reasons I can't explain yet. :However, there's a turning point. What would we work on after the Desktop Improvements? We're considering options for functionalities put in that (currently) empty area. So this topic may be revisited in the future. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 19:45, 14 June 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], thanks for the answer! Note: We can create a separate edit area that will be responsible for the infobox, or we can move the infobox using HTML :) [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 19:58, 14 June 2022 (UTC) == July? == > ''We are hoping to increase the set of early adopter wikis gradually, until our improvements are default on all wikis in July 2022.''<br> Has the schedule changed? [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 00:57, 12 June 2022 (UTC) :It has, @[[User:Iniquity|Iniquity]]. Previously it was June, now it's July. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:13, 14 June 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], thanks! It's just strange that there was no information about this before. And the wikis was not informed about it. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:15, 14 June 2022 (UTC) :::Information was sent yesterday in Tech News. Also, this week, I'll send an update to the Village Pumps. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:30, 14 June 2022 (UTC) :::: Yes, I saw it, thanks for that! But the day before yesterday, when I saw this, I got scared, because the community was not ready for this. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 19:59, 14 June 2022 (UTC) :::::We work with individual communities to help them prepare. We also don't ask the most "demanding" communities to prepare yet because Vector 2022 isn't ready to get deployed there either. We take into account that some prefer Vector 2022 to be closer to "finished", and then they would start thinking about preparing. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:17, 14 June 2022 (UTC) == Language switcher opt-out == The new language picker is a deal breaker for me as an active editor who is working with a very diverse array of topics on Wikipedia. I write about [https://en.wikipedia.org/wiki/Māori_phonology Māori language], [https://ru.wikipedia.org/wiki/Тэруха Japanese geisha], [https://ru.wikipedia.org/wiki/Литература_Тайваня Taiwanese literature], [https://ru.wikipedia.org/wiki/Эскимосская_кухня Inuit cuisine], [https://ru.wikipedia.org/wiki/Парагвайская_арфа Paraguayan instruments], [https://ru.wikipedia.org/wiki/Мишон Vietnamese temples], [https://ru.wikipedia.org/wiki/Кабилия Algerian regions], [https://ru.wikipedia.org/wiki/Берберская_кухня Berber cuisine], [https://ru.wikipedia.org/wiki/Кайна_(профессия) Arabic professions]. I write [https://en.wikipedia.org/wiki/Sister_exchange articles] that compare dozens of cultures [https://ru.wikipedia.org/wiki/Грамматическое_число or languages]. I need a way to hover over the list of languages to see the name of the page in a different random language (which can be anything from Korean to Twi). I need to be able to open 50 language editions very quickly to estimate if any of them have good illustrations or any new literature on the topic that I am working on. I often read the same article in 4 languages simply because I can read in a lot of languages and I am wondering which language edition has the best article. The workflow with the new language picker is tremendously stunted. The main idea of the new interface seems to be making the page width more narrow. With that, there is a lot of free space at the sides, and I would like to propose putting a full list of languages there, as an option. [[User:Le Loy|Le Loy]] ([[User talk:Le Loy|talk]]) 00:29, 13 June 2022 (UTC) : Yes, I agree, the decision taken now does not help advanced editors work in projects, but hinders them. I think we need to make a separate setting for the "always open" list. The problems of this list have still existed since sorting was removed. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 15:43, 14 June 2022 (UTC) :{{support}}--[[User:Wdpp|Wdpp]] ([[User talk:Wdpp|talk]]) 11:47, 3 July 2022 (UTC) == Old version == :''Moved from [[Topic:Wxcz2an2ck4s4cdy]]'' After these changes are made, can I still use the old settings? [[user:Ilovemydoodle|Ilovemydoodle]] ([[user talk: Ilovemydoodle|talk]]) 09:26, 13 June 2022 (UTC) : Yes [[user:Ilovemydoodle|Ilovemydoodle]], legacy Vector will be available and you will be able to use it as your skin. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:24, 14 June 2022 (UTC) ::{{ping|SGrabarczuk (WMF)}} Why does have to be called “legacy”? legacy implies that something is outdated, inferior, no longer supported, none of which apply to Vector "legacy". Maybe instead, you could call it "advanced", "expert", or "classic". – [[User:Ilovemydoodle2|Ilovemydoodle2]] ([[User talk:Ilovemydoodle2|talk]]) 17:48, 20 July 2022 (UTC) :::@[[User:Ilovemydoodle2|Ilovemydoodle2]], the motivation is purely technical. This is because it's "frozen". The Wikimedia Foundation will not develop it - there will be no actively built version of Vector parallel to Vector 2022. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 20:46, 20 July 2022 (UTC) == Incorrect language name for Czech == I noticed that for Czech (čeština in Czech) in the new look the first letter is incorrect, it says "Ceština" instead of "Čeština". I do think it is pretty funny, but would say it should be consistent with the rest of the themes. I hope this is the right place for this, I didn't find anywhere else to post. [[User:Filiptronicek|Filiptronicek]] ([[User talk:Filiptronicek|talk]]) 09:46, 13 June 2022 (UTC) :Hello @[[User:Filiptronicek|Filiptronicek]]. Thanks for writing to us. Most likely, it's not within our area, but I'll help you if the problem still exists. Where do you see this? On Polish and English Wikipedias, I see "Čeština". [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:42, 14 June 2022 (UTC) ::Hi there @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], perhaps it may have something to do with Czech being suggested to me as a language? I don't have an alt account to test this with though. ::Screenshot of what I see on the English wikipedia: https://i.imgur.com/T40u7rN.png. It is some very interesting behavior. Thanks for looking into this. [[User:Filiptronicek|Filiptronicek]] ([[User talk:Filiptronicek|talk]]) 13:45, 15 June 2022 (UTC) == Please take the interlanguage link (aka "green link") on Chinese Wikipedia into consideration! == The Chinese Wikipedia currently uses a green-colored link for interlanguage links in articles, and it seems to fail the WCAG AAA. These links can been seen at [[zh:Deadmau5]], for instance. These links are used a lot on Chinese Wikipedia, and I'm not sure if it is good for readers. If you want to evaluate link colors, please also take this green link into consideration, thank you. Looking forward to your professional advice! [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 11:38, 13 June 2022 (UTC) :I know these links are not part of Vector 2022, but they are part of the user experience, and currently there is a discussion at Chinese Wikipedia's Village Pump about the choice of color of them, so I posted my message here. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 11:43, 13 June 2022 (UTC) == Table of content (ToC) == Hi! Since weeks ago I don't see the table of content in the sidebar like I used to do before. It just disappeared. It happens when I'm connected in my phone using desktop version. Best regards! '''''[[User talk:Miaow|<span style="background:#88b;color:#cff;">Mia<span style="background:#99c">o<span style="background:#88b">w</span></span></span>]]''''' 12:06, 13 June 2022 (UTC) :Hello @[[User:Miaow|Miaow]]. Thank you for reporting this problem. We're working on a better look of TOC on small screens. I also strongly suggest you selecting the [[Reading/Web/Advanced mobile contributions|advanced mobile contributions]] mode when you're using your phone. That mode is dedicated for mobile, in contrast to Desktop Improvements. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 10:38, 14 June 2022 (UTC) == Better alignment for wide screens == [[File:Article with new vector.png|thumb|]] Here's how the new design looks on my laptop with 2560x1600 resolution. Ok, I get it, you won't do anything about the max-width and you insist on using this path. But look, the parts highlighted with purple ellipses just look misaligned. It just begs for the following: * Reduce the white background so that its right end matches the right end of the article OR insert something into that area. Having gray empty space is ok, but having both white and gray empty spaces look just silly. * Reduce the header so that its right end matches the right end of the article OR extend the white background of the header so that it fills the whole width of the page (see e.g. how it's done on [https://stackexchange.com StackExchange] or [https://www.reddit.com Reddit]. Again, I get your rationale that having empty space is ok. But having a white empty space on top of the gray empty space... Don't you think it's a bit too much? [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 01:23, 14 June 2022 (UTC) : [https://squidfunk.github.io/mkdocs-material/getting-started/ Material for MkDocs] is another example of what I consider a more successful implementation of reduced max-width. The main part has the same background (having same white background on the whole page would also look good on wiki) and the header part has background that extends beyond max-width. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 01:25, 14 June 2022 (UTC) ::When we look to the prototype https://di-article-tools-2.web.app/Blue%20whale?en (and https://vector-2022.web.app/Brown_bear), it's fill by "Tools", "In other projects", "Print, share, link" [[User:Koreller|Koreller]] ([[User talk:Koreller|talk]]) 08:31, 14 June 2022 (UTC) ::: It looks somewhat nicer, but the white empty space is still there if you collapse sidebars or scroll a bit... Also seem to have different defaults for logged in and logged out users. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:12, 14 June 2022 (UTC) == Launching New Version == :''Moved from [[Topic:Wxf5fv5pmxyyccdy]]'' When shall the new version ([[Reading/Web/Desktop Improvements/Fifth prototype testing/Feedback|Fifth prototype]]) be launched? [[user: Stnts256|Stnts256]] ([[user talk:Stnts256|talk]]) 08:54, 14 June 2022 (UTC) : We hope to launch Vector 2022 as default by the end of July. You can use it already by [[Special:Preferences#mw-prefsection-rendering|selecting this option in your preferences]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:28, 14 June 2022 (UTC) ::Thank you [[User:SGrabarczuk (WMF)|SGrabarczuk]] [[User:Stnts256|Stnts256]] ([[User talk:Stnts256|talk]]) 14:04, 14 June 2022 (UTC) == Keep watchlist in the sticky header == For an active Wikipedia editor, watchlist is likely the most popular destination when you're on some page. Would be great to keep the link there in the header, even after some scrolling. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:24, 14 June 2022 (UTC) : Keeping alerts and notices would also be nice. And also for it to work on the talk pages... [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:26, 14 June 2022 (UTC) : Yes, it bothers me that my control panel disappears. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:01, 14 June 2022 (UTC) : Second that. The most-used buttons of the standard interface (watchlist, contribs, interwikis) should stay in place, accessible with one mouse click. With the proposed layout I have to press tab-tab-tab... and then ctrl-enter to get to the watchlist. Why so? I can't reliably use the proposed drop-down menu with mouse, it's a common age-related ailment. I'd highly recommend to retain at least some bits of usability-for-disabilities: no complex manipulations. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 09:39, 15 June 2022 (UTC) == clear:both rendering on old browsers == {{Tracked|T309711}} I have tried browsing the wiki on Internet Explorer 11 on the new skin for one last time before Microsoft disables it, and it worked well, except something I have noticed is that the CSS property <code>@media screen .mw-body-header::after { clear:both; }</code> causes the side bar to push down the content. When unticking <code>clear:both</code> in the page inspector or when the side bar is hidden, it appears as usual. While fixing it for IE11 won't be relevant anymore, earlier versions of other browsers might have this flaw too. Mentioning it just in case. [[User:Octobod|Octobod]] ([[User talk:Octobod|talk]]) 23:29, 14 June 2022 (UTC) == Where are the interwikis? == Is there a simple way to access interwikis, other than by going to wikidata? Also, having two quasi-interwikis for wikidata is quite confusing. Only the second one actually works, the first one defaults to wikidata's start page. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 09:46, 15 June 2022 (UTC) :@[[User:Retired electrician|Retired electrician]] - currently, the adding interwiki links is available from the sidebar: "Edit interlanguage links" in the tools section. In the future, we would like to add them into the language selector as well. We are currently working with our Language team on this - see [[phab:T290436|Add support for empty states to the current language selector]] in phabricator for more details. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:23, 16 June 2022 (UTC) :: {{ping|OVasileva (WMF)}}, I see. Curiously, "Edit interlanguage links" does not appear on the main page (at least in ru-wp). [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 13:50, 16 June 2022 (UTC) == Suggestion: Round borders == I appreciate very much the efforts to make the design of Wikipedia less outdated, and imo this new design is amazing. To make it even better I would suggest you guys to put round borders in the boxes, so let's add border-radius:14px in these functions! This will make it cleaner and softer! [[User:Duke of Wikipädia|Duke of Wikipädia]] ([[User talk:Duke of Wikipädia|talk]]) 22:27, 16 June 2022 (UTC) == Top margin in title == Just noticed the new version and it looks like the title's top margin was reduced. There is an awkward amount of bottom margin for the title compared to top margin and I personally prefer the previous margins. [[User:0xDeadbeef|0xDeadbeef]] ([[User talk:0xDeadbeef|talk]]) 06:55, 17 June 2022 (UTC) == Very minor improvements == I just got the new toolbar this morning, and I absolutely love it! Finally Wikipedia does not look old anymore. But I would like you guys to add a little more than just a border for the active section in the toolbar, probably a lighter background for active tabs and a darker one for non active tabs. For example, if I'm reading an article, the 'Read' tab in addition to the bottom border, it should be lighter. The 'Talk' tab should be lighter also if I'm in the talk section. This should work well with something like option 3 combined with option 9 (where the header and the title has grey background) in [https://di-visual-design-borders-bgs.web.app/Zebra this border and background demo here]. I like option 3 a lot so it would be good if you guys implemented it, haha. I apologize if my English is not clear. [[User:Klrfl|Klrfl]] ([[User talk:Klrfl|talk]]) 12:26, 17 June 2022 (UTC) == new table of contents == For pages with a long table of contents such as this one, the table of contents starts jumping to highlight the current heading. Would it be possible to consider smooth scrolling behaviour for the table of contents at the new location (as for example invoked by <code>.vector-toc-enabled .sidebar-toc { scroll-behavior: smooth; }</code>)? Or is there something like a frozen state or is/was/will be this rejected for another reason? --[[User:CamelCaseNick|CamelCaseNick]] ([[User talk:CamelCaseNick|talk]]) 23:15, 17 June 2022 (UTC) :{{support}} [[User:Patafisik|Patafisik]] ([[User talk:Patafisik|talk]]) 10:06, 21 June 2022 (UTC) == Sister project links == (From [https://it.wikipedia.org/w/index.php?title=Discussioni_utente%3APatafisik_%28WMF%29&type=revision&diff=127968745&oldid=127933193 it.wikipedia]) {{ping|Friniate}} suggests to gather the Wikidata link and the Sister project links in the same place.--[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 09:49, 20 June 2022 (UTC) == Impact == How does the team plan to assess/measure whether the Vector changes work towards their stated goals, so that we're able to correct course in case they don't? [[User:Nemo_bis|Nemo]] 00:41, 21 June 2022 (UTC) == Great addition of ToC menu through icon wrt zoom !!! == I <s>have just</s> discovered a few days ago, in the french version of WP, as well as here in MediaWiki, the addition of a ToC menu, just before the title, that appears when the left column is NOT visible (at least effect of zooming), and '''this is a GREAT GREAT improvement, MANY-many thanks to the developpers'''. There still remains a small bug that appeared with this change (at least I didn't notice it before) : the upper (collapsile) bar appears no more. It reappears back when zoom permits back the side left column (tested with an article page in fr.WP ; no appearance "here" while editing, or even while just reading. but I guess it's a different thing, maybe because this is a talk page : I get the same "behaviour" in a talk page from fr.WP : no appearance of the upper collapside bar even if a left colum ToC is present. Might not be a "bug", but a feature, though I would personnaly prefer a uniform behaviour). Whatever, great thanks to the developers.<br/> &nbsp; (Poke @[[User:Patafisik (WMF)|Patafisik (WMF)]] : thanks for relaying these improvements, and back, our comments. Best :-) )<br/> &nbsp; -- [[User:Eric.LEWIN|Eric.LEWIN]] ([[User talk:Eric.LEWIN|talk]]) 06:17, 21 June 2022 (UTC) == Both the ToCs == (From the French Wikipedia [[:fr:Discussion_Projet:Am%C3%A9lioration_de_l%27interface_par_la_WMF#Sommaire_%C3%A0_gauche_:_ajouter_plut%C3%B4t_que_remplacer_?|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/24_mai_2022#Sommaire|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/26_mai_2022#Bug_du_sommaire|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/19_juin_2022#Tables_des_mati%C3%A8res|here]] and [[:fr:Wikipédia:Le_Bistro/25_juin_2022#Sommaire_dans_la_barre_de_gauche|here]]) I've already reported this to Szymon, but I think it will be important to have this suggestion also in this page, visible to all and open to comments. Different users of the French Wikipedia consider the old ToC and the new one as two complementary tools, and they want both! Reasons: 1) for the context, the ToC should be on the top of the article. If we have the first part of the sidebar occupied by the wiki navigation menu, the ToC is too far on the bottom of the page, it appears on the top only when you scroll down 2) the layout of articles with illustrations is completely disrupted. Both why? "When I look at the beginning of an article, I expect to see a ToC with the main sections in order to understand how the article is structured (quite like in a Word document). This makes it easier to read. The ToC on the left is then very useful when you scroll down the article and want to navigate between sections, but it is an additional feature. It should not replace the current summary, which is still useful. Or it should be displayed from the start at the top left, when you are at the top of the article (quite like on Universalis)." (summarised by Pronoia [https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia%3ALe_Bistro%2F26_mai_2022&type=revision&diff=194205255&oldid=194153014 here])--[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 11:45, 21 June 2022 (UTC) == Интервики в правый блок == Сейчас правое поле статьи абсолютно пустое. Что мешает перенести туда интервики-ссылки, вместо их полного сворачивания, а также подходящие по смыслу к ним ссылки на братские проекты? Это позволит: 1) избежать совершенно ненужного сворачивания списка (бессмысленно его уменьшать, когда высвободилось столько места); 2) заполнить правое поле; 3) частично разгрузить левое поле, чтобы оглавление было лучше видно сразу на первой же странице текста (сейчас при текущих настройках экрана я во французской Википедии вижу в среднем две верхних строки оглавления). [[User:AndyVolykhov|AndyVolykhov]] ([[User talk:AndyVolykhov|talk]]) 12:51, 21 June 2022 (UTC) == Languages in the new desktop interface == In the older interface I can select the interwikis that I need most and put them on top of the interwikis' list; same possibility should be in the newer interface. [[User:Leokand|Leokand]] ([[User talk:Leokand|talk]]) 15:06, 21 June 2022 (UTC) == minor issues == * The position at which the table of contents is sticky changes with the sticky header becoming visible/hidden. (<code>.vector-toc-enabled.vector-sticky-header-visible .sidebar-toc { margin-top: 1.5em }</code> vs. <code>.vector-toc-enabled .sidebar-toc { margin-top: 3.5em }</code>) With the sidebar navigation hidden, this makes the table of contents jump up by <code>2em</code> while scrolling. * At a window width of exactly 1000px the table of contents on the left is displayed but styled like the drop-down table of contents and the drop-down button is still visible but has no influence on the table of contents. * At 720px+ the logo is displayed, the username and potentially a language switcher. With my username on this wiki in German, the watchlist and the user menu are outside the viewport, so this threshold is chosen to narrow. Maybe a solution would be to move the username link to the user menu at 1000px and lower. (For CSS rendering, I use Firefox v101.) -- [[User:CamelCaseNick|CamelCaseNick]] ([[User talk:CamelCaseNick|talk]]) 17:28, 21 June 2022 (UTC) == Drop-down menues = poor accessibility == Repeating prior statements for clarity: May I speak on behalf of old folks with less-than-perfect control of palms and fingers. The replacement of simple "button" links (contribution, statistics, interwikis...) with drop-down menues becomes a huge inconvenience. In plain monobook, I can simply click on the interwiki, and hopefully get the desired tab at the first try. In vector-2022, I cannot reliably pull down the drop-down list and then select something with a mouse... it almost never works as intended. A very common age-related ailment, it just happens. The only robust workaround is to use the keyboard to "tab-tab-tab..." to the desired control box, and then "enter-tab-tab-...-enter" through the list. And, in case of interwikis, selecting the main (en:) wikipedia takes atrociously long time - instead of being #1 entry, as in old good monobook with my normal preference settings, it's somewhere down the middle of the list. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:46, 21 June 2022 (UTC) == Irish language Wikipedia and Vector 2022 == [[File:Irish Wikipedia random article - Vector 2022.png|thumb|ga.wp random article screencap - Vector 2022]] [[File:Irish Wikipedia random article - Vector old.png|thumb|ga.wp random article screencap - current Vector]] Hi there. I'm [[w:ga:User:Alison]] - admin and bureaucrat on the Irish language Wikipedia. I'd be remiss in not providing feedback, I think, so here goes. * I see other folks pointing out the massive amount of whitespace / padding in the left side navbar which is squeezing out the actual article text on the right. On our wiki, it really seems significant. IMO, article is all, and we seem to be sacrificing actual content real-estate for ... what, exactly? Yes, it looks 'less cluttered', but there's actually less content - especially for those of us who both browse ''and'' edit on laptop screens. * On the top tab section (which is otherwise quite nice), you can see the ''Plé'' (Talk) and ''Léigh'' (Read) are scrunched together with no separation. I18n bug, maybe? * The main image and title have lost their localization and now show "Wikipedia" instead of "Vicipéid" - this could just be an image localization / config issue. Could someone point me in the right direction, maybe? I did the original, later-font localization for our wiki, some years back, so happy to dip in and fix :) Le gach dea-ghuí (best regards), -- Allie [[User:Alison|<span style="color:#FF823D;font-family: comic sans ms">'''A<font color= "#FF7C0A">l<font color= "#FFB550">is</font>o</font>n'''</span>]] <sup>[[User talk:Alison|❤]]</sup> 16:17, 22 June 2022 (UTC) :multilingual Wikipedians: during redesigh include current non-english desighs for evaluation, including spanish, french and german. They have good ideas and bad ideas... [[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 01:10, 23 June 2022 (UTC) : The "PléLéigh" issue looks like it's [[phab:T309223|T309223]], a known issue. Until it is fixed in MediaWiki, try updating your browser(s) – the issue occurs if your browser doesn't support a certain relatively new feature. [[User:Rummskartoffel|Rummskartoffel]] ([[User talk:Rummskartoffel|talk]]) 21:59, 23 June 2022 (UTC) ::Hey there! Regarding logos https://phabricator.wikimedia.org/T244486 is what you are looking for - basically every logo needs to be recreated. You can request one on that ticket to be prioritized higher or find information about creating new ones. ::Regarding sidebar whitespace I am not sure I understand. The extra padding is for the table of contents underneath the sidebar. You say it's squeezing article text on the right but in your screenshots the Vector 2022 screenshot shows more of the article text. I can see the description section heading for example. ::I can confirm the PléLéigh issue is a bug and will hopefully be fixed soon. ::Hope this is helpful. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 01:02, 1 July 2022 (UTC) == TOC-Feedback == I just recognized what disturbs me the most with the new TOC. I wasn't able to access the TOC without scrolling or clicking when using a community-Page. The main thing: '''It's mixing system and content'''. The TOC is for the content, but appearing on a place of "system". The "frame" is the Media-Wikisystem: accessing Community-Pages, Help, recent changes, user-page etc. Inside the "frame" is the content (the "article", the "book"...). Although it's kind of logical to have the TOC sticky on the side there are so many problems with it: # the TOC can't be manipulated by magic words, which is a pretty well used functionality. # the TOC can't be placed to the right, which is pretty often used in german wikibooks. # the TOC is in competition with the other menus. # the TOC is now at a place where normally links to other pages are placed. The same fear of mixing system and content goes with switching the Header and the "Editing-Tabs" (Compare https://di-article-tools-2.web.app/Blue_whale: '''Blue Whale''' first, ''read/edit'' second). BTW the TOC works at this demo-page because the Main Menu is so short. But since this is not fixed (which is a good thing!), the Main Menu might be longer. A good illustration of the problem is visible just the paragraph above this: [[#Irish language Wikipedia and Vector 2022]]. The TOC in the Vector22-Example is completely missing! So, just as an Idea: '''divide system and content''' - say system top&left (as it's always been) and content bottom&right. the TOC could be placed "always right" next to the text. At least please let the editor choose what to do with the TOC. I mean, wouldn't it be so bad if it's within the Content '''and''' at the side? I'm fine with the new skin and all the work that has been put in, but the TOC is becoming unusable for me like it is right now. If it's really becoming permanent, it will probably result in "self-made-TOCs" which will break pretty often, because of the "wiki"-system. [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 17:37, 22 June 2022 (UTC) == The new design is everything I feared == Jumpable, irritatingly movable buttons? Check. Sticky UI that eats up immense space both at the top (header) and to the left (table of contents)? Check. Tiny narrow line of text in the middle? Check. Buttons not looking like buttons, thus confusing me as to what I may click? Check. The language menu made objectively worse, with more clicks necessary to use than before? Check. Every single change is atrocious, negative, and honestly makes me feel depressed - I will either try to scour Reddit for browser extensions to remove as much of it as possible (no, logged in user things are useless to me as I'm never logged in), or I will leave Wikipedia for good (mental health is more important than knowledge). Just look at this useless eyesore of a sticky table of contents ([https://i.postimg.cc/bz2zZM2C/2022-06-22-Wikipedia-English-51-UI-bug.png screenshot on postimage] - I hope, you aren't getting the ads, I'm getting none). Even aesthetics-wise, it's botched - the bottom is smudged, the top cut-off. And it's not even at the edge of the screen! It's an exercise in ugliness. And just saying it here, this Wikimedia redesign is already making it unintuitive for me to write. When I tried to insert the link, I couldn't even see the [https://i.postimg.cc/qBp0ZvDS/2022-06-22-Wikipedia-English-53-UI-bug.png ''upload'' button] - because it's on the edge of the sub-menu (like on phones), not somewhere sensible, like on computers (again, compare how it is on current Wikipedia - a [https://postimg.cc/TpMNbPHg large nice menu with clear buttons at the bottom], computer design). [[User:Adûnâi|Adûnâi]] ([[User talk:Adûnâi|talk]]) 18:55, 22 June 2022 (UTC) == wordmark no longer appears after upgrading to MediaWiki 1.38.1, style bugs == After upgrading to MediaWiki 1.38.1 from 1.36.1, the wordmark no longer appears next to the icon in the upper left. If the window is wide enough, the 150px space for the wordmark is reserved but is empty. When you make the window wider past a certain width, the coloring behind the sidebar also vanishes. This happens with Vector 2010 in both legacy and non-legacy mode and in Vector 2022. The wordmark image is an svg that has not moved and still has correct permissions [[User:Queernix1028|Queernix1028]] ([[User talk:Queernix1028|talk]]) 19:43, 22 June 2022 (UTC) :What is the value of wgLogos in your LocalSettings.php? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:22, 29 June 2022 (UTC) $wgLogos = [ 'icon' => "$wgScriptPath/images/arcc/logo.svg", '1x' => "$wgScriptPath/images/arcc/logo.png", 'wordmark' => [ 'src' => "$wgScriptPath/images/arcc/wordmark.png", '1x' => "$wgScriptPath/images/arcc/wordmark.svg", 'width' => 150, ], ]; ::It previously worked with wordmark src set to the svg file, but now neither that configuration nor the one above work. [[User:Queernix1028|Queernix1028]] ([[User talk:Queernix1028|talk]]) 14:32, 29 June 2022 (UTC) :I believe you need to set a height on the wordmark. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 00:55, 1 July 2022 (UTC) == Menus — https://di-visual-design-menus.web.app/Brown_bear. == *left side menu persistency is screen wasteful, bad idea ** use a tab like google maps? *left side menu: should be hamburger only **as an option for experienced, registered users **need style sheet that puts ''left side column'' '''at bottom of page''' as a footer *language list: **should include native and english names **include a user-customizable shortlist *[[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 00:57, 23 June 2022 (UTC) == Language links on Wikidata are right at the bottom of the page == I've enabled the new theme (Vector 2022) globally on all wikis. I generally like the new interface. However when I am on wikidata, previously the interlanguage links were on the right. (Where an infobox usually goes on a wikipedia page) Now they are right at the bottom of the page! Some wikidata pages are massive, and having to scroll all the way down to the bottom of the screen to do the thing I do most frequently on wikidata (add new language links) is a real pain. Please can you move the language links on wikidata back to the top (top right) of the page? - [[User:Rooiratel|Rooiratel]] ([[User talk:Rooiratel|talk]]) 14:25, 23 June 2022 (UTC) :Hello @[[User:Rooiratel|Rooiratel]]. Thanks for your opinion. Are you talking about the desktop view? What's the resolution of your screen? I've tried to narrow my window down and change its width, and it seems that the width thresholds when the interwiki links go from the bottom to the right are the same. Is there any setting you use that may make your experience different? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:50, 27 June 2022 (UTC) ::Hi {{ping|SGrabarczuk (WMF)}} this is for the desktop view. I am seeing this behaviour on my 1080p laptop screen and my 1440p desktop screen. I haven't used the mobile view, so can't comment on that. - [[User:Rooiratel|Rooiratel]] ([[User talk:Rooiratel|talk]]) 06:32, 28 June 2022 (UTC) == Infobox element alignment is mangled in mobile view == Maybe I'm doing something wrong, but when I click on "Mobile view" with Vector 2022, many of the infobox elements are misaligned. Many elements that should be centered are left-aligned, and many elements that should be left-aligned are centered. At least that's what it looks like for me in Chrome for Mac OS at [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic&useskin=vector-2022 this page]. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 02:57, 24 June 2022 (UTC) :Wow, that looks odd. Thanks @[[User:Jonesey95|Jonesey95]] for reporting this. Right now, I only have one question - why do you use the mobile view and Vector 2022 mixed together? Minerva is dedicated for mobile, and Vector 2022 is dedicated for desktop. Having these two at the same time is bold and original :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:08, 27 June 2022 (UTC) ::I was just doing some very beginner-level QA testing. Editors do all sorts of ridiculous things, so I try to do some QA testing by doing ridiculous things. If you want editors to use Vector 2022 for desktop-only and Minerva for mobile-only, then make the "Mobile view"/"Desktop view" link at the bottom of the screen switch between the skins. Meanwhile, I'll be over here in legacy Vector where I can fill my browser window with content.... [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 01:15, 28 June 2022 (UTC) Using the mobile domain with the Vector skin invokes a special mode with lots of odd behaviour. It's not part of this project but will hopefully get fixed some day. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:30, 28 June 2022 (UTC) == "Related articles" appear to be missing == I do not see the "Related articles" section at the bottom of the mobile view. I don't really care, but since the "Principles" section of this page says "We do not remove any functionality", I thought I'd mention it. It makes me wonder what other functionality has been removed, and whether this principle is really being followed in a systematic way. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 03:02, 24 June 2022 (UTC) RelatedArticles appears to be working fine to me. I see it on Minerva. What do you mean by "at the bottom of mobile view"? The scope of this project is the desktop site so no changes to the mobile domain have been made. RelatedArticles does not show on the skins of certain websites and has not shown on Vector or Vector 2022 unless the community has explicitly requested. See [[phab:T144812]], [[phab:T181242]] and [[phab:T278611]] for example. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:59, 24 June 2022 (UTC) :I think this is my mistake. I was comparing [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic this] (default mobile view on en.WP) with [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic&useskin=vector-2022 this] (Vector 2022 mobile view) and assuming that the default mobile view used some version of the Vector skin, but I think that is not correct. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 16:38, 24 June 2022 (UTC) Ah okay. This mode is only accessible by a special URL and is not being worked on as part of this project. Thanks for taking the time to explain! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:28, 28 June 2022 (UTC) == 非常に見にくい == 日本語で失礼します。本日ごろから日本語版ウィキペディアのスキンに変更があったようですが、 # 文字の大きさをブラウザ側から変更できない(Safari使用)。 # そもそも標準の文字サイズが大きすぎる。 # 目次が項目名の横に位置が変わったせいでアクセスが煩雑になった。 # Infoボックスが大きすぎる などの変更のせいで、余計見づらくなったような気がします。可能であれば改善するか、もしくは変更前のスキンに戻して欲しいです。 [[User:イカしたイカ|イカしたイカ]] ([[User talk:イカしたイカ|talk]]) 08:38, 24 June 2022 (UTC) :感謝します、@[[User:イカしたイカ|イカしたイカ]]さん。 :First of all, you don't need to apologize for writing in Japanese. We welcome comments in any language. :# Would you like just to change the default font size? Or would you be able to zoom in and out, and see the font size adjust? :# Do you think making the text line wider and keeping the default font size would fix the problem? :# Why do you think access is more complicated now? Our motivation was to reposition the table of context to make it more accessible. What do you think is not working? :# Do you think the problem is related to the default font size? :まず第一に、あなたは日本語で書いたことを謝罪する必要はありません。 どんな言語でもコメントを歓迎します。 :# デフォルトのフォントサイズを変更しますか? または、ズームインおよびズームアウトして、フォントサイズが調整されるのを確認できますか? :# テキスト行を広くし、デフォルトのフォントサイズを維持することで、問題が解決すると思いますか? :# なぜ今、アクセスがより複雑になっていると思いますか? 私たちの動機は、コンテキストのテーブルを再配置して、よりアクセスしやすくすることでした。 何が機能していないと思いますか? :# 問題はデフォルトのフォントサイズに関連していると思いますか? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:18, 12 July 2022 (UTC) == Please evaluate CJK characters' font size in Vector 2022 == {{tracked|T311469}} For your infomation, the Chinese Wikipedia already has a [[zh:MediaWiki:Gadget-large-font.css|gadget]] that increases the font size for a better Chinese reading experience. Japanese and classical Chinese Wikipedia also have such kinds of gadgets. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 08:19, 25 June 2022 (UTC) :It would be nice if we could integrate these gadgets into new Vector skin directly. This would benefit other CJK and multilingual wikis. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 08:20, 25 June 2022 (UTC) ::Thanks @[[User:Diskdance|Diskdance]]! @[[User:AHollender (WMF)|AHollender (WMF)]] FYI :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:03, 27 June 2022 (UTC) I think we should create a phabricator ticket for this one. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:29, 28 June 2022 (UTC) == Feedback regarding Vector (2022) TOC == I've had Vector (2022) enabled for a while, and generally like it. However: * I don't feel the new way of handling the TOC and side menu is user friendly. It took me a while to notice I could hide the side menu only to raise the TOC up the page, as I assumed it would also hide the TOC since the two are part of the same sidebar. With the side menu visible, I had to scroll much further down than usual to find the TOC on many articles with short lead sections, which undermined the convenience previously provided by the TOC as a way to skip scrolling and quickly navigate to a desired section. ** It also doesn't help that the [[w:Template_talk:Skip_to_talk#Broken_functionality_with_new_version_of_vector_theme|new TOC breaks the functionality of]] {{tl|Skip to talk}}, widely used on talk pages on Wikipedia, but I now understand that the change is intended to make that template unnecessary. ** The prototype [https://di-visual-design-menus.web.app/Brown_bear linked by others above] deals with some of these issues but is still a bit confusing. It's not clear that clicking "hide" on the TOC should result in a menu appearing by the article title rather than just collapsing it like collapsible lists which use the same "[hide]" links; while this behaviour can be learned, it's not clear why the hidden TOC menu button doesn't persist between the search icon and article title when scrolling down, which is what I expected after seeing it collapse to a button beside the article title. * The new sidebar is wider to accommodate the TOC, but much of that space is blank so I'm not sure it needs to be quite so wide, particularly as the added width can cause issues such as galleries by default having less space for images per row. I understand the motivation is to limit the characters of text per line, but doing so by padding the sidebar with empty space seems like an unhelpful way to achieve that. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 16:57, 26 June 2022 (UTC) == Where are the watch/unwatch buttons? == Alright, if the article is long enough to be scrolled, I should scroll it down, the top row of icons will jerk left-right, and the "watchlist" icon will become the "watch/unwatch" toggle. Hopelessly inconvenient, counterintuitive, but it works. But what if the article is so short that it won't scroll at all? [https://ru.wikipedia.org/w/index.php?title=%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%8F:%D0%A0%D0%B5%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5/%D0%9E%D0%B1%D1%8A%D0%B5%D0%B4%D0%B8%D0%BD%D1%91%D0%BD%D0%BD%D1%8B%D0%B9_%D0%B2%D0%BE%D0%BA%D0%B7%D0%B0%D0%BB_%D0%A6%D0%B8%D0%BD%D1%86%D0%B8%D0%BD%D0%BD%D0%B0%D1%82%D0%B8&oldid=123611287 example] Seems like "preferences/watchlist/edit raw watchlist" is the only go-around, is it not? [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 12:13, 27 June 2022 (UTC) :@[[User:Retired electrician|Retired electrician]]: There's a smaller star-shaped watch/unwatch toggle to the right of the "View history"/"История" link. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 14:48, 27 June 2022 (UTC) :: Thanks, that was most unexpected. I'd rather prefer old good text links. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 15:59, 27 June 2022 (UTC) The new star looks almost exactly like the existing GA star, just a different shade of grey (but in almost the same corner location as in standard monobook). [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 16:02, 27 June 2022 (UTC) :"Thanks, that was most unexpected. I'd rather prefer old good text links" - you're a Monobook user, am I right? This may be a good reason why it's most unexpected for you. Vector 2022 is based on Vector legacy (2010), and the star icon has been there for 12 years. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 01:51, 28 June 2022 (UTC) == Merge notification block in the header: notifications and alerts == {{Tracked|T142981}} For me, it has always been a strange decision that notifications were divided into two unrelated blocks and icons with incomprehensible categorization. I forgot about it, but now I'm paying attention again. Given that we removed the text from all menus, there are now a lot of icons at the top that do not understand what they do. Different blocks of notifications do not help this at all. Maybe it's time to put them in one menu and break it there already? Filters, tabs, whatever :) But at least you won't get confused in the icons. I personally still (6 years!) do not know what their fundamental difference is. I asked my friends and they don't know either. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 17:29, 27 June 2022 (UTC) :{{Strong oppose}}. The notices are the notifications that are not very important/urgent, unlike the alerts. Merging them would make me unable to found out at a glance if I have any important/urgent notification, and would also overload the notification box, as I receive many notifications. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 22:19, 27 June 2022 (UTC) :: It seems to me that it is possible to do this with filters and colored marker icons. Or a separate setting for users who really need it. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 09:47, 28 June 2022 (UTC) :{{Comment}}. I agree that the distinction could be clearer, but don't necessarily agree that there should be only one button. Presently, when both are empty the only difference between them is the header text and icon. Both share the exact same two buttons, which link to the same destinations. The text in the box doesn't even distinguish, reading "There are no notifications" instead of "There are no alerts". There isn't even a "help" or "about" link unique to each of them to explain the difference or what gets sent where. If you follow the links to the special page or preferences, it's still not clear which notifications are sent where. :Based on the names, I would've assumed the difference would be that alerts are specifically for subscriptions to [[Wikipedia:Article alerts|article alerts]], whereas notifications would be for everything else. It makes sense to split them, since alerts would be activity that's less personal to the receiver. "Alerts" would be like a daily newspaper, but "notifications" are more like personal mail. Except this isn't how the system actually functions; messages to the receiver's talk page are placed under "Alerts" rather "Notices", for example. :I understand that it may be helpful to filter urgent notifications from less urgent ones, but what counts as urgent or important? Shouldn't that be decided by the user's preferences? It would make more sense to have something like tabs, as Iniquity suggested, to filter types of notifications; this would let that user decide what is important. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 22:33, 27 June 2022 (UTC) == Table of contents: Bold format for active section == I really appreciate the new skin and layout. In the beta, the active/current section of the article was formatted bold in the table of contents on the left side. But in the live version, it's regular and black. I find it really, really hard to differentiate between the normal blue titles and the active title, because the only difference is the black vs. blue color. Could you please make the active titles bold again? Thank you! [[User:Lhennen|Lhennen]] ([[User talk:Lhennen|talk]]) 21:11, 29 June 2022 (UTC) :+1 Bold and black would be best imo. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:43, 1 July 2022 (UTC) ::@[[User:Lhennen|Lhennen]], @[[User:L.xschlag|L.xschlag]] - thank you for your feedback! Not sure if you've seen, but we are currently in the middle of testing some [[Reading/Web/Desktop Improvements/Fifth prototype testing|prototypes]] related to this question. You're welcome to give us more detailed feedback on the prototype page. One of the things we're testing on these is the way links should appear within the table of contents (see https://di-visual-design-toc-active.web.app/Otter) for an example. Currently, our feedback is showing us that people are leaning towards option 2: bold and black so we will most likely be continuing with that option and making the titles bold. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:08, 4 July 2022 (UTC) == Jawiki has NOT reached consensus on implementing Vector 2022 yet == Jawiki has '''NOT''' reached consensus on implementing Vector 2022 yet. Why was it implemented without our consent? [[User:AppleRingo777|AppleRingo777]] ([[User talk:AppleRingo777|talk]]) 22:01, 29 June 2022 (UTC) :Hi @[[User:AppleRingo777|AppleRingo777]] - we apologize for the confusion that the deployment process has caused and the lack of clarity from our side.  We are currently working on reading back through our previous communications and clarifying the process and what happened with individual members of the community.  We will to get back to the community with more detailed thoughts and a process for next steps by tomorrow July 1st.   [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 12:04, 30 June 2022 (UTC) == [[MediaWiki:Sidebar]] == Hello! I asked a question at the meeting, but I would like to duplicate it here. Will it be possible to control the location of blocks (right or left) through [[MediaWiki:Sidebar]]? [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 15:34, 30 June 2022 (UTC) :Hey! We are still thinking through how this would work. Input valued in [[phab:T306519]] ! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:27, 6 July 2022 (UTC) :: Thanks! :) [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:16, 6 July 2022 (UTC) == Keep the TOC under the main menu as long as possible (Vector 2022) == When the window gets narrower the TOC is moved into a "Hamburger button". But the main menu stays where it is until the window get's quite a bit more narrower. I think as long as the main menu fits, the TOC should stay at its original place. Especially since the TOC behind the "Hamburger button" is quite easy to miss. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:30, 1 July 2022 (UTC) :This was a bug. I believe it should be fixed by the end of the week. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:28, 6 July 2022 (UTC) == "Move" is the only in the "More" drop down menu (Vector 2022) == I think it's quite odd that the "More" drop down menu most of the time contains only "move". Is it on purpose to make it harder to find for the average user? [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:35, 1 July 2022 (UTC) * {{ping|L.xschlag}}, I have two items - the other is an add-on via preferences/gadgets. Unfortunately, I cannot use drop-down menues easily, so getting there in V-2022 is quite a nuisance. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:31, 3 July 2022 (UTC) *:Isn't the behaviour the same here on the other skins? *:I agree it's not great having one item in a menu, but I think this case is quite rare since on most wikis move privilege is added along with page protection and deletion. There is a trade off here between the complexity of maintaining multiple variants of the skin in different circumstances and what looks best. Here we could add special treatment for the one item menu but we'd need to add additional code complexity and tests to cover it. Hope this insight is helpful. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:32, 6 July 2022 (UTC) == Actions menu overflows when main menu is active (Vector 2022) == {{Tracked|T311471}} When the main menu is active (meaning visible) and the window is quite narrow the actions menu (Read, Edit source, Add topic, View history) doesn't get condensed in the "More" drop down menu, resulting in a very ugly overflow. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:41, 1 July 2022 (UTC) :@[[User:L.xschlag|L.xschlag]] - thank you for your feedback! This should now be fixed, let us know if you continue seeing issues. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:34, 11 July 2022 (UTC) == Audio player issues (Vector 2022) == When pressing play from a wikipedia article (e.g. first clip in [[:w:en:Aftermath_(Rolling_Stones_album)]]), the page changes text colour from black to pale grey. Almost unreadable. This dead time varies from a few seconds to many minutes, probably caused by unsteady connection on my side. I tried opening 2-3-4... windows with the same article, and some windows seem to be stuck indefinitely while others play with minimal (but still annoying) delay. If I press play directly from file description page ( [[:w:en:File:Under_My_Thumb.ogg]]), it always plays instantly and the text always stays black. Win 10 Home / Chrome 102.0.5005.115 (64-bit) [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 19:29, 3 July 2022 (UTC) :I've flagged this bug to the developers of [[Extension:TimedMediaHandler]]. This is not related to this project. I'll let you know if I hear anything back. Thanks for reporting! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:43, 11 July 2022 (UTC) == Language mix in the interface == Pardon me if this had already been discussed here. It seems that the language of the interface (as set in preferences) mixes up with local-language elements where it shouldn't. # My preferences are always "interface=en", and thus I always see "Contents Beginning" in the TOC section - be it Chinese, Russian or Spanish wiki. # The pink box above TOC in ru-wiki says "On this Википедия<sup>[sic!]</sup> the language links are at the top of the page across from the article title. Go to top." In zh-wiki, however, the message is correctly "On this Wikipedia the language links ..." [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:23, 3 July 2022 (UTC) :Thank you @[[User:Retired electrician|Retired electrician]] for reporting this. That's odd. 🤔 [[betawiki:MediaWiki:Vector-language-redirect-to-top/en|The source code]] is: <tt><nowiki>On this {{SITENAME}} the language links</nowiki></tt>... - so apparently, something about <nowiki>{{SITENAME}}</nowiki> isn't working here. But I don't know what yet. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:20, 6 July 2022 (UTC) == Where are the categories? == Hi this is my first time looking at the prototype, so apologies if this question has been answered elsewhere - where are the categories? [[User:MassiveEartha|MassiveEartha]] ([[User talk:MassiveEartha|talk]]) 04:15, 5 July 2022 (UTC) :Hello @[[User:MassiveEartha|MassiveEartha]]. I'm sorry that you felt confused. We don't touch elements such as categories. These prototypes were only created for editors to help us decide on the visual design matters. If the categories aren't displayed in any of the prototypes, then it's definitely unintentional and also irrelevant to what we do. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:02, 6 July 2022 (UTC) == 開発者集団は日本語版を軽視していると思われるThe group of developers seems to downplay the Japanese version == 日本語版の利用者の一人としては、開発者の集団は日本語版を軽視していると考える。一つの証拠として開発者からの意見を求めるメッセージが英語だけで書かれていたことを挙げておく。機械翻訳があるのだから英語と共に日本語を添えることは簡単なことのはずである。それすらせずにVectorからVector2022への変更を強行したことは、一種の文化帝国主義であると評さざるを得ない。As one of the users of the Japanese version, I think that the group of developers disregards the Japanese version. One proof is that the message for the developer's opinion was written in English only. Since there is machine translation, it should be easy to add Japanese along with English. It must be said that forcing the change from Vector to Vector 2022 without doing so is a kind of cultural imperialism.--[[Special:Contributions/27.85.205.84|27.85.205.84]] 07:17, 5 July 2022 (UTC) :Hello 27.85.205.84. Do you maybe know good open-source machine translators working for Japanese and English? I've noticed that Google Translate doesn't work for these languages well. Sometimes it changes words, meanings, and the tone of entire sentences completely. I could write in Polish, my first language, but I'm sure that would be even more difficult. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:15, 6 July 2022 (UTC) == Vector 2022を強要する行為は、開発者が読者を軽視していることの証拠である The act of forcing Vector 2022 is evidence that developers are downplaying their readers. == 開発者(の集団)はアカウントユーザーなら自分で好きなスキンを使えるのだから、あまり出来がよいとは言えないVector 2022を強要してっもかまわないと考えているようである。しかし、元々Vector 2022は読者として快適に使えることを考慮していない。開発者(の集団)は読者がいなければいくら記事を作っても意味がないということを忘れているのだろうか。It seems that developers (a group of people) are willing to force Vector 2022, which is not very good, because account users can use their favorite skins. However, originally Vector 2022 did not consider it to be comfortable to use as a reader. Do developers (groups) forget that it doesn't make sense to write an article without a reader?--[[Special:Contributions/27.85.205.84|27.85.205.84]] 07:29, 5 July 2022 (UTC) :Hello! As I can see, the translation was done by Google Translate. It's not good. I've used DeepL and this message is very different in English. Why do you think Vector 2022 was not originally designed to be comfortable to use as a reader? I would like to understand what made you think so. :こんにちは! ご覧のとおり、翻訳はGoogle翻訳によって行われました。 良くない。 私はDeepLを使用しましたが、このメッセージは英語では大きく異なります。 なぜVector2022は、もともとリーダーとして快適に使用できるように設計されていなかったと思いますか? どうしてそう思ったのか理解したい。 [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:06, 12 July 2022 (UTC) :: [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)-san]], your great DeepL-ed message causes a [[:ja:Wikipedia:削除依頼/Wikipedia:井戸端/subj/デスクトップ版外装(スキン)改善バージョンの実装について|deletion discussion]] due to copyright violation. I wish a good Foundation staff would deeply understand the copyright policy in Wikipedia and recognize that copypasting from machine translation could violate the copyright that was attributed to that translation service. :: So, while I'm not the original poster of this section, let me answer the question: :: > Why do you think Vector 2022 was not originally designed to be comfortable to use as a reader? :: If you think the only problem is new Vector 2022 design itself, I must say you are missing an important point: how you all introduced the new skin. All of the changes has never been announced in jawiki before being applied (and unfortunately, after that, until today). Many of the editors, the readers, the users were surprised at the new design all of the sudden, and not a few of them regarded it as a big bug or something. :: You may wonder, "we let you know this in advance, via a member of your community." That's true, partially. [[User:AppleRingo777|AppleRingo777-san]] took your messages and passed them to us per your instruction. I heard that you (or someone in Foundation) asked to post the message in WP:NEWS. How did you determine that WP:NEWS, generally where announcements '''only for the editors''' are posted, was enough to communicate this important news that obviously affected the entirety of community members including the readers? Will you also assign the responsibility on this to AppleRingo777-san, a good community member? I cannot help but want the Foundation to realize that you all destroyed our trust. --[[Special:Contributions/2400:4052:3420:4500:444C:45BF:13AC:59E2|2400:4052:3420:4500:444C:45BF:13AC:59E2]] 14:40, 14 July 2022 (UTC) == Listed coordinates overlapping with header weirdly == {{Tracked|T281974}} for an example of this, see wp's [[:en:London|london]] article ([https://imgur.com/a/rEngM3R screenshot]) [[User:LarstonMarston|LarstonMarston]] ([[User talk:LarstonMarston|talk]]) 20:00, 5 July 2022 (UTC) :Thank you @[[User:LarstonMarston|LarstonMarston]]. In this case, we need to fix the bug together with the communities - some code should be changed by editors on each wiki with this bug separately. We can help (and we're working on it). [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:11, 6 July 2022 (UTC) ::thanks, good to hear [[User:LarstonMarston|LarstonMarston]] ([[User talk:LarstonMarston|talk]]) 20:06, 6 July 2022 (UTC) == Default to Collapsed Menu Exposed TOC == {{Tracked|T287609}} I was trying to figure out why I didn't like the new TOC, and then it hit me that the main reason was that it is hidden by the side menu when you first visit a page (I very rarely login to Wikipedia, and I'm thinking that's the norm for most visitors). Then I was thinking that I almost never use the main navigation links, they just aren't part of my normal use case of visiting Wikipedia (it is to learn a specific thing that I don't currently know enough about). I was going to post to make it possible to hide the main nav, but then realized that you already built it, but the default is for it to show. My hypothesis is that the bulk of users don't look or click on any of the menu items, and that the menu should be hidden by default and the TOC exposed above the fold. [[Special:Contributions/195.134.163.110|195.134.163.110]] 10:34, 6 July 2022 (UTC) :Yes, TOC should be exposed above the article not on the right. In fact in desktop view if I click PC version it does not open stuff on the left. [[Special:Contributions/2A00:1370:8184:2478:A928:87EF:D073:FEEA|2A00:1370:8184:2478:A928:87EF:D073:FEEA]] 16:22, 6 July 2022 (UTC) :Thank you for your feedback! We are planning on implementing this change within the next couple of weeks. Progress can be tracked in the phabricator ticket linked above. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:04, 11 July 2022 (UTC) ::I would like you to give logged-in users the right to choose that as well. If you knew about these plans, don't you think that was a little premature to set Vector (2022) as the default in JAWP ? If you make changes right after you start it in JAWP, Japanese users will be confused. --[[User:呉野|呉野]] ([[User talk:呉野|talk]]) 13:21, 14 July 2022 (UTC) == Replace the "new section" tab text with "+" gadget not working. == {{Fixed}} On the English Wikipedia upon switching to Modern Vector the aforementioned gadget ceases to function as intended. [[User:Nathanielcwm|Nathanielcwm]] ([[User talk:Nathanielcwm|talk]]) 13:14, 6 July 2022 (UTC) :Looks like the gadget is setup to only work on Vector and Monobook. I have updated it to also apply to Vector 2022 skin (https://en.wikipedia.org/w/index.php?title=MediaWiki%3AGadget-addsection-plus.js&type=revision&diff=1096783301&oldid=1047498910) [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 15:59, 6 July 2022 (UTC) == July == @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: Does Vector 2022 will be deployed (as default) at all Wikimedia wikis until the end of July, as it is written [[Reading/Web/Desktop Improvements|here]]? I am asking this because I see that there is still some work to do and the deadline written there changed several times. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 21:56, 6 July 2022 (UTC) :Hello @[[User:NGC 54|NGC 54]], thanks for this question. This information is already outdated. It will ''not'' be deployed in July. We hope to send an update to the village pumps next week. We're working on the announcement right now. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:01, 7 July 2022 (UTC) == Language switching == Hi, I really appreciate the suggestion of translations within the language button, thank you! [[Special:Contributions/37.103.14.65|37.103.14.65]] 09:06, 7 July 2022 (UTC) :Thanks! Appreciation also goes to the [[Wikimedia Language engineering]] team, because they have made this particular change. We have "only" provided the language button :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:01, 12 July 2022 (UTC) == Vector (2022)のウィキペディア日本語版への導入について About the introduction of Vector (2022) to the Japanese version of Wikipedia == 「[[:ja:Wikipedia:井戸端/subj/デスクトップ版外装(スキン)改善バージョンの実装について]]」での案内によると7月14日までこのページでコメントを受け付けるとのことなので意見を書く。--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:25, 8 July 2022 (UTC) * 開発者は開発すること自体に喜びを感じるべきであり、日本語版で行ったように強引に導入して「見えるところ」に成果が表れることに喜びを感じるべきでない。 * 開発者は裏方として、開発に専念するべきであり、それを使うかどうかは「利用者」の判断にゆだねるべきである。 * スキンはインフラストラクチャーである。技術者が陥りがちな間違いだが「新しければよい」というものではない。 * 現在のVector (2022)は完成品とは言えずベータテストの段階でしかない。この段階で全面導入を進めようとするのは技術者の姿勢として適切でない。ベータテストは希望者を募って行うべきである。 * Vector (2022)をデフォルトのスキンとすることについて、本当に開発者チームに権限が与えられているのか。証拠があるなら、リンクをつけて示してほしい。 * 今回の経緯を見ると「読者」に対する観点が脱落している。「読者」のいない記事に何の意味があるのだろうか。 :ja: Wikipedia: Idobata / subj / Desktop version According to the guidance on implementing the improved exterior (skin) version, comments will be accepted on this page until July 14, so I will write my opinion. * Developers should be delighted with the development itself, and should not be delighted with the "visible" results of the forcible introduction as was done in the Japanese version. * Developers should concentrate on development behind the scenes and leave it to the "user" to decide whether or not to use it. * Skins are infrastructure. It's a mistake that engineers tend to make, but it's not "just new." * The current Vector (2022) is not a finished product, it is only in the beta test stage. It is not appropriate as an engineer's attitude to proceed with full-scale introduction at this stage. Beta testing should be done by recruiting applicants. * Is the developer team really empowered to make Vector (2022) the default skin? If you have proof, please link to it. * Looking at the history of this time, the viewpoint for "readers" is missing. What does an article without a "reader" mean? [[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:25, 8 July 2022 (UTC) *:Hi @[[User:匿竜類|匿竜類]] - Thank you for your feedback and for the bug reports below. We are currently in the process of taking the Vector (2022) skin out of beta testing/pilot mode and into the stage where we scale the skin, with the hopes of making it the default on all the wikis. Over the course of the next month, we will be hosting conversations with the largest Wikipedias and getting their feedback on the skin, similar to our conversations with Japanese Wikipedia right now. Even when default, logged-in users will still be able to chose whether they want to use the skin or not. If they decide not to use it, they can turn it off at any moment in their user preferences. *:In terms of readers, for every change we have made when building the skin, we have tested both quantitatively and qualitatively with readers and well as editors. To access more detail on the research and testing we have done, please go [[Reading/Web/Desktop Improvements/Features|to the Features page]] and select the feature you are interested in learning about. From there, you can read the sections named Quantitative research or Qualitative research to see the testing we have done. In addition, we have also done more open-ended testing with readers to identify the issues with the skin starting in 2020 until now. Please see the [[Reading/Web/Desktop Improvements/Repository/Hureo User Research Report/ja|Hureo User Research Report]] with Readers and Editors, the [[Reading/Web/Desktop Improvements/Repository/Wikimania Stockholm research report/ja|Wikimania Stockholm research report]], the [https://nbviewer.org/github/wikimedia-research/Desktop-behavior-analysis-Aug-2019/blob/master/Desktop_usage_behavior_analysis.ipynb Wikimedia Desktop Usage and Behavior Data Analysis], or the [[Reading/Web/Desktop Improvements/Repository/Sticky Header and Table of Contents User Testing/ja|Sticky Header and Table of Contents User Testing]] reports for some examples of the studies we have done with readers (which have translations in Japanese), what we have learned, and how we used those learnings to create the new skin. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:00, 11 July 2022 (UTC) == Vector (2022)の不具合の報告 Report a bug in Vector (2022) == {{Tracked|T303267}} {{Tracked|T281974}} 日本語版でVector (2022)を使うと、左側に「このWikipediaでは言語間リンクがページの先頭にある記事タイトルの向かい側に設置されています。ページの先頭をご覧ください。」と表示されるのだが、実際には「記事タイトル」は「ページの先頭」ではなくこのメッセージの下に表示される。以前は、このようなことがなかったように思うので一時的なものかもしれないが、症状が出ていることを確認してほしい。When I use Vector (2022) in the Japanese version, it says "In this Wikipedia, the interlingual link is located opposite the article title at the top of the page. Please see the top of the page." However, in reality, the "article title" is displayed below this message instead of "at the top of the page". I don't think this happened before, so it may be temporary, but please make sure that you have symptoms.--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:42, 8 July 2022 (UTC) :上記不具合を報告してから、1日経過していますが、応答がありません。[[:ja:Wikipedia:表示改善依頼#Vector(2022)スキンで、バッジと地図のタグが重なって表示される#]]によると、どうやらこの種の不具合はファブリケータで処理することになっているようですが、そちらの方への連絡はしていただけたのでしょうか。とりあえず担当者の応答を求めます。One day has passed since I reported the above problem, but there is no response. ja: Wikipedia: Display improvement request #Vector (2022) In the skin, the badge and the map tag are displayed overlapping. According to #, it seems that this kind of defect is to be handled by the fabricator. Could you contact that person? For the time being, ask for the response of the person in charge.--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 03:05, 9 July 2022 (UTC) ::Hello! The coordinates issue is known but the language one wasn't. Thank you for bringing it to our attention. ::I will reply with more details next week. Have a great weekend and thank you for the bug reports. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 18:27, 9 July 2022 (UTC) :::These are tracked in [[phab:T303267]] and [[phab:T281974]]. Thanks for the report! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:39, 11 July 2022 (UTC) == Merge [ca-view] and [ca-nstab-main] in the article toolbar == Currently, in the article toolbar, we have two links (Read and Article) that lead to the same location. One of them is located in the left and the other one is located in the right navigation. This can be confusing to readers, and also adds unnecessary weight to the toolbar. [https://imgur.com/56mbihi Current look]. It would be good if we could merge these two tabs into one. Ideally, the best solution, in my opinion, would be to merge the right and left navigation and center the items, [https://imgur.com/a/ih52zYZ like this]. Please tell me what you think about this. Thank you! — [[User:Aca|Aca]] ([[User talk:Aca|talk]]) 11:18, 9 July 2022 (UTC) :{{O}}. Now, the tabs are clear. You have 2 pages: the article and the talk page. You can select 1 action at a time for each of them: reading, visual editing, source editing, and viewing the history. Form the proposed design, you can understand that the tabs led to different types of pages. The watch is something not related to the article? And if now you are on article tabs, if you would press on the editing source tab, you would arrive on a page not related to the article (this is a possible confusion)? And so on. "This can be confusing to readers," - how so? Are there any data? And if there are, are there any data that the proposed design is better? P.S. I also dislike the proposed design, due to visual reasons. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:00, 9 July 2022 (UTC) == Big blank space when on a big zoom == Unlike the old layout that adjust depending of the size of zoom, the new format seems to follow a single size that, when zoomed in, creates a big blank space like if the page was still loading It needs be fixed so the wiki pages can be better for people that have vison issues - [[:en:User:Meganinja202|User:Meganinja202]] | [[:en:User_talk:Meganinja202|¿]] 10:17:00 11 July 2022 (UTC) [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 10:17, 11 July 2022 (UTC) :[[User:Meganinja202]] are you taking about [[Reading/Web/Desktop_Improvements/Features/Limiting_content_width]] or reporting a bug? If the latter, what browser and device are you using? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:34, 11 July 2022 (UTC) ::i think should be a bug since its a thing that happens from top to bottom of the page and not from the sides, i am use Chromium Based MS Edge [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 17:02, 11 July 2022 (UTC) == Language box recommendation == A minor suggestion: why not insert the language box on the title header so I don't have to go all up to the top of the page to change language versions. So yeah, thanks! [[User:PeaceSeekers|PeaceSeekers]] ([[User talk:PeaceSeekers|talk]]) 11:00, 11 July 2022 (UTC) :ya, they should had kept the language bar on the side of page instead of the top, leaving the language option on top only on mobile/touch machines [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 17:03, 11 July 2022 (UTC) :@[[User:PeaceSeekers|PeaceSeekers]] - do you use the site while logged-in? If so, you can access the language switching button from the persistent ("sticky") header at the top of the page while you're scrolling. We are also in discussion of bringing this functionality to all logged-in users as well. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 08:15, 12 July 2022 (UTC) ::I did log in, but I can't see it though ... what I have is only, from the left: the search button, article title, discussion page, edit history, watchlist and my profile stuff (for lack of better words). So that's that. [[User:PeaceSeekers|PeaceSeekers]] ([[User talk:PeaceSeekers|talk]]) 08:43, 12 July 2022 (UTC) == What I still would love to see different solutions to == I'm very much looking forward to not having the text fill an entire wide screen. This will make Wikipedia far easier to read on big screens. Thanks! A few things that still don't work for me: '''Table of contents''' If I haven't collapsed the left menu, the ToC is not visible when I start reading the article. This makes it more difficult to get an overview. It's also ''generally'' more difficult to get an overview of the article content, as I need to go to the ToC in the sidebar and scroll down to see everything on big pages (like a Village Pump). This both makes it more difficult for me to conceptualize what's on the page – as I've tested this, I've realised I find it challenging to get a grasp of a page if I can't see the various topics at the same time – and adds more work, as I have to move the mouse pointer to the ToC to be able to scroll. I would have much preferred if it used more of the space available to get around this. '''My contributions''' My own user contributions is something I use all the time – it's my way of getting back to what I was doing before. Making it less accessible in the top menu is wrench thrown into my workflow. '''Language links''' This is my main issue. I use other languages ''all the time''. As a reader, I glance at them to conceptualise the topic – which languages have written about this subject? This hints at things that aren't available in the content itself. As an editor, I check out other languages to see what sources they have and so on. Having to click to even see if there are languages I can read is an extra step that both requires more work, but also makes it less inviting, as the opportunity doesn't stare me in the face. This is so central to my workflow that it might in itself be reason to keep using Vector 2010, but that's certainly not my preferred solution. [[User:Julle|Julle]] ([[User talk:Julle|talk]]) 10:13, 12 July 2022 (UTC) == feedback == asbra med maxbredd! coolt att wikipedia tar steget in i 2010-talet och blir läsbart på stor skärm. språklänkarna blir mycket sämre. man borde kunna se språken direkt och klicka på dem, det är en sak man använder hela tiden. jag förstår inte varför ni har bytt ut texten i användarmenyn mot symboler? det var tydligare med text. nu måste man gissa vad de betyder och många kommer aldrig lista ut det. man borde inte behöva skrolla INNE I innehållsförteckningen för att se hela. sjukt störande att behöva gå till den och skrolla I DEN för att se vad som finns på sidan. [[Special:Contributions/81.92.27.129|81.92.27.129]] 18:12, 12 July 2022 (UTC) :Thanks for the feedback! :(google translation) :* max width: cool that wikipedia takes the step into the 2010s and becomes readable on the big screen. :* language links: you should be able to see the languages ​​directly and click on them, it is one thing you use all the time. :* Icons: I do not understand why you have replaced the text in the user menu with symbols? it was clearer with text. now you have to guess what they mean and many will never figure it out. :* Table of contents: you should not have to scroll INSIDE the table of contents to see the whole thing. Very annoying to have to go to it and scroll IN IT to see what's on the page. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 19:00, 12 July 2022 (UTC) :::("Sjukt störande", which the machine translation rendered as "ill disturbing", means "very annoying".) [[User:Julle|Julle]] ([[User talk:Julle|talk]]) 00:15, 13 July 2022 (UTC) == More TOC concerns == On pages with long headings (f.i. [[Wikipedia:Closure_requests]]), the new TOC is highly impractical. The headings are difficult to parse, sometimes cutting words in two. A lot of scrolling is also required to get an overview of what discussions to close. Will it be possible to go back to the old TOC on a per-page base? I can imagine a lot of non-article pages will have similar problems (including this one). Less importantly, I noticed that the default is having only the top heading displayed. In some pages / articles there are very few top-level headings, and this would always require the reader to uncollapse. Can this be made more dynamic? [[User:Femke|Femke]] ([[User talk:Femke|talk]]) 18:09, 14 July 2022 (UTC) :Would it be possible (probably only on bigger screens) to use the empty white space on the right for tools (for logged-in editors), so that the TOC is less cramped? Solves two problems in one. [[User:Femke|Femke]] ([[User talk:Femke|talk]]) 17:00, 18 July 2022 (UTC) == incorrect translation Vector 2022(jpwiki) == The information text on where to switch languages is partially translated incorrectly. I think , "このWikipediaでは言語間リンクがページの先頭にある記事タイトルの向かい側に設置されています。" is a slightly mistaken translation. This may mean that the language switch is outside the display. You probably meant to write that, "他言語版へのリンクは、ページ先頭の記事タイトルの右側にあります。". But I would rather you don't adopt this with no check. [[User:呉野|呉野]] ([[User talk:呉野|talk]]) 10:01, 15 July 2022 (UTC) == 'Talk' and 'Contributions' buttons shouldn't be hidden in the navigation bar's drop down menu. == We shouldn't have to click twice to get to our '''Talk''' and '''Contribution''' pages from the navigation bar. I mean, there's already a bunch of wasted white space to right of the search box and to the the left of our Userpage button for those two icons to be added in the nav bar without any problems. [[User:Some1|Some1]] ([[User talk:Some1|talk]]) 02:57, 17 July 2022 (UTC) == Simple English sidebar == I notice in Simple English with the 2022 Vector, the menus on the left side of the page are to the left of the page text as they should be, but they are far above rather than beside the text. [[User:Jim.henderson|Jim.henderson]] ([[User talk:Jim.henderson|talk]]) 05:47, 17 July 2022 (UTC) == The new sidebar TOC is confusive, not intuitive, unusable == I strongly oppose the new sidebar TOC. It is extremely confusing, not intuitive, and unusable. The removal of the numbering for paragraphs and their transformation into collapsible lists, will make the articles and discussions unreadable, as their structure will be completely unclear. The TOC at the top of the article right below the lead text was perfect for giving a clear impression of the article's structure and for exploring its contents. I think that keeping both the old and the new TOC (if the latter is really necessary) would be a good solution. The new TOC proves useful only in the bottom sections of very long articles. [[Special:Contributions/2001:B07:A2A:1884:D5D:3606:C70C:5366|2001:B07:A2A:1884:D5D:3606:C70C:5366]] 14:03, 17 July 2022 (UTC) == This gives me depression == By merely see this happen week-by-week, I can see this sacred project gradually being destroyed. I wish I could stop this. – [[User:Ilovemydoodle2|Ilovemydoodle2]] ([[User talk:Ilovemydoodle2|talk]]) 07:35, 18 July 2022 (UTC) == wrong name for a language == someone is having a laugh, or got really confused about translation. In the main page https://www.wikipedia.org/, '''Français''' now appears as '''anglais''', both in the top 'wheel' and in the 'Read Wikipedia in your language' drop-down. This is very wrong. What other languages have been disappeared in this way ? a bit of QA would go a long way :-) [[Special:Contributions/92.16.98.145|92.16.98.145]] 16:23, 19 July 2022 (UTC) :Thanks for letting us know! This looks like a mistake/error on translatewiki.net. We'll try to fix that immediately. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 18:28, 19 July 2022 (UTC) ::FYI this wasn't related to the project. ::See related Reddit thread for details on what happened here if you are curious: https://www.reddit.com/r/wikipedia/comments/w2iidz/why_anglais_did_someone_sabotage_it/ [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 20:03, 20 July 2022 (UTC) == coordinates being weird (again) == there was an issue a little while ago where location coordinates in an article would overlap with the header. that's fixed now, but some icons are still uncomfortably close to them, like the FA star; for an example of this, see the english wiki's [[:en:India|India]] article ([https://imgur.com/a/uuXPMzk screenshot]) [[Special:Contributions/2600:1700:7AA1:2400:9CA1:1220:42FD:1F12|2600:1700:7AA1:2400:9CA1:1220:42FD:1F12]] 20:17, 20 July 2022 (UTC) == General concerns! == Well I was part of the process for quite some time now. And up until the move of the TOC from inside the content to the sidebar it was okay with me. I had some minor things, I thought I will get used to: the white space (anyone wanting that, can narrow their window), some inconsistencies (compare [[#A few more issues with the Page header vs Sticky header icons]]), the language switcher, which I fear will leave the impression of reading ''the same'' thing in different languages (compare [[Talk:Reading/Web/Desktop_Improvements/Archive3#Language_Selector_misunderstandable]], as a side-note: nothing happened here, at least nothing I recognized). But today I got this message: [[Topic:Wsfx4tbwzkgamaek]] asking for a translation for [[Reading/Web/Desktop_Improvements/Updates/2022-07_for_the_largest_wikis]]. Let me cite: *'''"...before discussing the change itself"''' *'''"...that allows for a way to identify the needs of the community from the new skin."''' *'''"We would love to see the Vector 2022 skin [...] become the new default across all wikis..."''' *'''"We will be ready to begin making the change at the end of August (and not in July, as previously announced), when the ''visual refinements'' and other ''deployment blockers'' are ready."''' *'''"The goal for that discussion will be to identify breaking issues or opportunities for improvement for the new skin. It will be important for us to reduce the risk of bugs or imperfections that would be particularly troublesome on [insert your language] Wikipedia"''' All that reads like: Well, we're just talking, let's see, what needs to be done, that everyone is happy. There are some things that need to be done anyways. Now let's read those two cites: *'''"...difficult discussions about the launch as the default"''' (compare [[Topic:Wsfx4tbwzkgamaek]]) *'''"...until our improvements are default on all wikis in July 2022."''' (compare [[Reading/Web/Desktop_Improvements]] So isn't this not just a request for bug reports instead of a "discussion"? Is this not more of a fear of "Flak" instead of "needs of the community"? Isn't it happening anyways, instead of you "loving to see it"? What about all the other projects, wikibooks for example ("[insert your language] Wikipedia")? I understand, you do the work, you decide. '''But:''' * Is it wise to "discuss" while there are still tasks to be done and decisions to be made? (compare [[Reading/Web/Desktop_Improvements/Features/Visual_Refinements]], which by the way doesn't even seem finished, and for example [[#MediaWiki:Sidebar]]) * Is the Date of the end of August (6 weeks) really feasible? Who will translate all the feedback that will come in german? * Is it good to leave the impression, that communities will have a choice (compare [[#Jawiki has NOT reached consensus on implementing Vector 2022 yet]])? Some suggestions, if I may: # Why not try to slow the process down? Why the haste? One could remove the deadlines and refine everything. ''Then'' ask the communities for bug reports. # Why not try some marketing "tricks"? I think the discussion about the white space clearly shows that desktop ''improvements'' are highly subjective. Why not use for example ''skin changes''? Another Option could be deploying Vector 2022 only for not logged in users and hence prolong/smooth the transition-process creating time for bug reports and discussions. Most of anonymous usage would probably not care for the change, as long as the content is there. On another plus-side it will create "data" on how the menu-usage changes and community-links are perceived. It will probably even create data on how many logged in users switch to the new layout deliberately and or switch back hence providing "hard" success-data. # Would it be that bad to really leave the community a choice? # If you are relying on volunteers, grant them a little more slack. Bug reports from the community need time: Bugs need to be recognized as bugs, they need to be reported, triaged ''and'' handled. Is this possible in 6 weeks? Volunteers might have another life, a job, kids, a week might be pretty short notice. Phabricator-use is not that trivial. # Let's talk or try, if the new design might eventually be a problem for recruiting new volunteers. Did anyone think about a possible impact of hiding ''community-links'' in collapsed menus? Nobody seems to talk about community-pages or discussion-pages or even other project-scopes. Is the new menu-structure as fitting for these as for wikipedia-articles? I'm deeply saddened. The new TOC will make my life within wikimedia really hard and I commented about that early on (compare [[Reading/Web/Desktop_Improvements/Third_prototype_testing/Feedback#Benutzername:HirnSpuk|here, bullet 7]]). I think all the TOC-comments on this page (see above) should raise at least some concern. And last but not least, I'm deeply troubled, that the new language-links will do more harm, than good. So, ping @[[User:OVasileva (WMF)|OVasileva (WMF)]] and @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], my sincere apology, I don't mean to be rude or mean and I appreciate your work and the work of your colleagues. But I don't want to volunteer for the translation-request, because all of the above mentioned problems. Regards [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 22:25, 20 July 2022 (UTC) :Hello @[[User:HirnSpuk|HirnSpuk]]. Thank you for your outstanding involvement, and appreciation for our work. I'm glad to see that. Also, thank you for your sincere, thoughtful, and thorough comment with all the links and quotes. I think I understand what your approach is, I'm happy that you're saying this. :Before I answer the questions, I'll admit/confirm that: :# The ToC work hasn't been finished yet. So haven't the visual refinements. There's a list of issues labelled as "[[phab:T309972|deployment blockers]]", by which we mean issues we need to solve before making it the default everywhere. I hope this will make you less sad! :# Bug reports do need time. Phabricator is not that trivial. :# While indeed focusing on the most typical use cases, like interacting with articles. :# In some discussions, it has been confusing what exactly is for the individual communities to choose between. :Regarding the questions, my answers to the easiest part: :# We've been working since 2019, most work is behind us and we're headed towards the end. Now, we need to make sure what else the largest communities may need. :# What about all the other projects - the message I asked if you could translate is dedicated to the largest communities of the top language versions of Wikipedia. :# This is why in that message, we're initiating a pre-discussion about culture of collaboration. After that, we'll ask for bug reports and other technical requests. :# We use the name Desktop Improvements because the point is to make changes that are actual measured improvements. Only some of the visual refinements are really subjective. But regarding the feature changes, the idea for each of these is that it should be an improvement compared to Legacy Vector. :# We're part of [[Core Experiences]] and work closely with the teams focusing on newbies and more experienced editors. It's our plan to make entry points for new volunteers prominent, in collaboration with Growth. We hope that Desktop Improvements will be an introduction to even more sophisticated changes addressing very specific use cases. :OK, enough now for one comment. Let's keep talking, though. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 01:30, 21 July 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], because you said "let's keep talking", let me react to your latter 5 points. ::# I do not want to diminish in any way the work you (plural) have done since 2019 and I think the plan is good. But I'm convinced, that the timing is not right. "The end of August" I find far to soon if you "need to make sure what else the largest communities may need." ::# I wasn't able to find the "we talk to the «big guys» first"-idea anywhere. The only thing I find is "We would like our improvements to be default on all wikis in August/September 2022." There will probably not be time to talk to the «small guys». And in addition, the text to translate suggest, that there is a choice, and you'd like to "talk". My impression is you want to ask: how can we best ask for bug reports. That might (and probably will) work, but I don't want to be part of exactly this approach. ::# same as first and second. ::# How is the improvement measured? Is there any "hard data" anywhere? Everything needs more clicks hence more time. It "looks" a little better and modern, which I also find necessary and good. But what is actually "improved"? ::#*I need more scrolling for the TOC, ::#* I will need more work (and creative ideas btw) for rework of community-pages that rely on the "old" version of the TOC at the moment, and even worse, I need to check the visual appearance and usability of pages in even more configurations (to mobile and desktop and VE and source, now I need to add different skins), ::#* I need more clicks for almost anything (if menus are hidden, but this is nearly imperative, to get at least some use out of the new ToC), ::#* I'm deeply troubled about the "impression" some changes might make (which hence wouldn't be an improvement either and which is by default not measurable)... ::#* What about the visually impaired? Is it an improvement for them too, any hard data? ::#:Please, feel free to elaborate. I know it would be baloney to change the name in the last 6 weeks of the work. My point is not to do that, but to take a step back, review what's done so far, and if the decision will be made to prolong the process a really long time, then ''maybe'' one ''might'' think about a change, and if it's only to get less of the "if you do this I'll be done with wiki..."-criticism that's just consuming time for everyone. ::# I'm not addressing technical issues. It's the possible "hiding" of prominent community-links in the sidebar by using elaborate restructuring and collapsing mechanisms. On that the single communities won't have influence as far as I see it at the moment. ::PS: I appreciate trying to cheer me up ("make you less sad"), but my sadness stems from the uncertainty how this will all work out. In the end the prototype is only a prototype. And how much work in the community must be done afterwards to facilitate the "improvements" is also not clear. The main point being, that I struggle with checking and cross-checking functionalities in different systems. It was okay until the move of the ToC. But as long as there is still work to be done, I can't even think about workarounds for not having the ToC where and how I was used to it. ::Regards [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 07:34, 21 July 2022 (UTC) ==Sorry but user expereince is kind of awful== Okay. I've given "Vector 2022" a shot for a while and it is just confusing and difficult to use. Too much animation-style issues. Too much whitespace. Difficult discovery of functions. Difficult to obtain a feeling of confidence in mastery. If I would have been keeping a log, I'd have dozens of gripes by now. I don't wish to waste time enumerating specific things because it's besides the point because the entire experience is bad. I can't hack it anymore. I thought I'd get used to it but I'm going back to Vector 2010. Keep things simple. Keep it static. I know many people but a lot of work into this and it was a valid attempt but it just didn't suceed in improving over Vector 2010. [[User:Jason Quinn|Jason Quinn]] ([[User talk:Jason Quinn|talk]]) 02:24, 26 July 2022 (UTC) == External link icon == The external link icon currently deployed on mediawiki.org looks horrible. What happened? The icon shown at [[phab:T261391]] in the "After" screenshot looks much better. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:55, 26 July 2022 (UTC) :@[[User:NGC 54|NGC 54]], what's the difference you're referring to? Could you maybe share a screenshot? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:36, 26 July 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: Here. ::[[File:Vector2022 Broken External Link Icon.png|thumb|The icon looks thin and pixeled. Not like at Phabricator.]] --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:48, 27 July 2022 (UTC) :::I saw that the issue was already reported. Compare [https://phab.wmfusercontent.org/file/data/zm2w6tyla7ap4pm54oxw/PHID-FILE-jxp2g6oxik24v6zcst5o/image.png this] with [https://phab.wmfusercontent.org/file/data/6tvujxqmvz53tlojn4qi/PHID-FILE-gq23v5redy2o4ki63rnq/Screen_Shot_2022-07-21_at_11.46.24_AM.png this]. Also, for me it looks like the arrow is misshaped. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:53, 27 July 2022 (UTC) ::::Hi @[[User:NGC 54|NGC 54]] - thanks for your report. The icon is indeed broken as of right now. We're looking into this right now and hope to have a fix later this week or early next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 12:05, 28 July 2022 (UTC) 3vqwd5jfrnqviifvvd6kqayxpx41vec 5387558 5386203 2022-07-29T02:44:33Z SGrabarczuk (WMF) 9240933 /* General concerns! */ Reply wikitext text/x-wiki {{Reading/Web/Desktop Improvements/Header}} {{WMF present |1=SGrabarczuk (WMF)|timezone_1=UTC+1/2|lang_1=pl, en, fr|photo_1=Wikispotkanie-warszawa-2021-07-03-rd-26.jpg |2=OVasileva (WMF)|timezone_2=UTC+1/2|lang_2=en, es, bg|photo_2=Vasileva, Olga January 2017.jpg }} {{Archive box| *[[Talk:Reading/Web/Desktop Improvements/Archive1|Archive1 (before the 1st batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive2|Archive2 (before the 2nd batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive3|Archive3 (before the 3nd batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive4|Archive4]] *[[Talk:Reading/Web/Desktop Improvements|Current discussion]] }} {{Reading/Web/Desktop Improvements/Talk page intro}} __TOC__ == Where is the TOC? == People here are complaining about it. I don't even get one! [[User:Betaneptune|Betaneptune]] ([[User talk:Betaneptune|talk]]) 17:38, 25 May 2022 (UTC) :Hello @[[User:Betaneptune|Betaneptune]]. Do you still have this problem? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:52, 8 June 2022 (UTC) ::Hi ! I have the same problem on the French version of Wikipedia. The TOC just disappeared. The problem appears in Firefox desktop (last version 101.0.1), even in "troubleshoot" mode with all my add-ons deactivated. However, the problem does not appear in Chrome. This is extremely confusing. I reported it on some discussion page on the french version of WP, but I also mention it here, as I'm not sure at all where to report the problem for it to be taken into account. [[Special:Contributions/85.169.195.108|85.169.195.108]] 17:56, 26 June 2022 (UTC) : The TOC is now on the left side, but after other menu lists. It should probably come first. But to keep things accessible, the (hidden) "jump to main menu" link should be kept as first element of course. [[User:Psychoslave|Psychoslave]] ([[User talk:Psychoslave|talk]]) 15:00, 5 July 2022 (UTC) ::Agreed. The TOC ''really'' should come first. The {{mono|#mw-navigation}} menu (which currently appears first) is comprised of mostly ancillary links unrelated to the page's content, many of which are rarely used (e.g., ''"Download as PDF"'', ''"Create a book"'', ''"Permanent link"'', etc). [[User:OmenBreeze|OmenBreeze]] ([[User talk:OmenBreeze|talk]]) 00:17, 6 July 2022 (UTC) :::{{ping|85.169.195.108}} It has been tracked here [[phab:T312022]].--[[Special:Contributions/37.103.14.65|37.103.14.65]] 09:03, 7 July 2022 (UTC) ::::Suggestions: ::::* ''If'' the TOC will ''not'' come first, the other menu lists on the left side should become hidden (collapsed) when there is a TOC below them, so that the TOC is always visible. ::::* The TOC should always be shown in its entirety, and not displayed as a box that you have to scroll through. ::::[[User:Förbätterlig|Förbätterlig]] ([[User talk:Förbätterlig|talk]]) 14:03, 12 July 2022 (UTC) == Too narrow (again) == Why waste all that space? I have a nice wide screen so I want to take advantage of it. Those who want to have it narrow can just reduce their window sizes? Overall, not a great look. Not exciting. Quite boring.--[[User:Xania|Xania]] ([[User talk:Xania|talk]]) 11:23, 22 December 2021 (UTC) :Hello @[[User:Xania|Xania]], you can read about our [[Reading/Web/Desktop_Improvements/Features/Limiting_content_width#Goals_and_motivation|goals and motivation]] for limiting the width. Also, we are working on a solution to use the empty space. Could you take a look at [[Reading/Web/Desktop Improvements/Fourth prototype testing/it|our fourth prototype]] and write more on what you think about arranging the space as it is presented there? Thank you in advance! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 14:59, 26 April 2022 (UTC) :: Oh my dear God, why don't you give an option to unrestrict the width?? It's beyond ridiculous how absolutely tiny is the page content on my monitor horizontally! I have to scroll all the time to read! Don't ruin Wikipedia the same way Fandom was ruined! [[Special:Contributions/90.188.46.13|90.188.46.13]] 04:38, 13 May 2022 (UTC) :::We have given this option. This can be done with the [[:en:User:Jdlrobson/vector-max-width-toggle.js|gadget one of our engineers made]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 03:39, 14 May 2022 (UTC) ::::Thanks, but maybe we should have an easy plug-in system for ordinary users or, at least, the instructions how to apply it and a place where to find those customisations. By default it is really narrow to read and it feels like a news site rather than an encyclopedia article. [[User:Krnl0138|Krnl0138]] ([[User talk:Krnl0138|talk]]) 09:55, 15 May 2022 (UTC) :::::I agree, the toggle option should be there by default! By the way, that script does not work well currently, so I [[:en:User:Arthurfragoso/vector-max-width-toggle.js|updated it here]]. — [[User:Arthurfragoso|Arthurfragoso]] ([[User talk:Arthurfragoso|talk]]) 13:28, 21 May 2022 (UTC) ::I don't understand why you are still pushing on us that bad design choice. It still is time to pull the plug and start to work on a plain page design. You are convincing no one here. Please, please, really, please stop this nonsense. Forcing bad choices on your users because you are the only product on the market is never a good thing. ::Since it has been forced without asking anyone on the French Wikipedia I had to register just to come back to the normal and good design. That's something, as a simple reader, I should never have had to do in the first place. ::So one last time, please come back to reason and stop hurting your user base foolishly. [[User:DerpFox|DerpFox]] ([[User talk:DerpFox|talk]]) 21:33, 13 May 2022 (UTC) :::Hello @[[User:DerpFox|DerpFox]], thanks for your comment. Have you maybe followed the links I've shared in my answer to Xania? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 03:42, 14 May 2022 (UTC) ::The lines in the fourth prototype seem to be slightly wider to me on 1080p display than in the current version of 2022 vector design, but those empty strips on the sides, each of which are almost the size of the old navigation mv-panel, constantly remind about the space wasted. ::If the only reason of this thinning is the recommended line lengths in symbols and you want to keep it for any price, I would suggest using a dynamic font size, so, for example, starting from some resolution the symbols just grow larger. This might also reduce the eye strain connected to focusing on the small text. ::[[User:Kageneko|Kageneko]] ([[User talk:Kageneko|talk]]) 13:51, 17 May 2022 (UTC) ::I had a browse over the reasons for the change, but I still don't like or agree with the main justification more or less boiling down to "everyone else is doing it so we should too". Even in the linked examples, the page still feels a lot more "full" despite having a dedicated deadspace on the site, due to the way the page has been very carefully designed in a mixture of different kinds of block contents (images, text interactive eliments, etc). ::Accepted Webpage standards used to be against having blank, unused and waisted deadspace, but at some point in the last 10 years there seems to have been a weird shift to the opposite where deadspace is all the rage, though it's not one I've personally ever liked or agreed with. ::While I'm sure there are good uses of limiting page width, I'm not sure if Wikipedia, being a site that is mainly made up of text would really benefit from it as it's likely just going to squash pages and increase the amount of vertical scrolling required to navigate. [[User:Dave247|Dave247]] ([[User talk:Dave247|talk]]) 07:32, 18 May 2022 (UTC) ::Yeah it's too narrow otherwise. the look is very nice, it's not boring as you tell. [[User:Crater bug|Crater bug]] ([[User talk:Crater bug|talk]]) 15:28, 28 May 2022 (UTC) :I totally agree! I dislike the vector skin because how small it is. [[User:OverAWallOfMetaKnight|OverAWallOfMetaKnight]] ([[User talk:OverAWallOfMetaKnight|talk]]) 15:55, 15 May 2022 (UTC) :Agreed. I use a 3440x1440 screen (usually with a tiled layout), and this new layout forces all the content to occupy a comically narrow strip, instead of allowing me to choose the width myself. [[User:Emptyflask|Emptyflask]] ([[User talk:Emptyflask|talk]]) 13:47, 17 May 2022 (UTC) :I agree, there is simply too much space wasted that could be used for more article space and a button specifically for those who want to edit wikipedia [[User:Techny3000|Techny3000]] ([[User talk:Techny3000|talk]]) 02:52, 28 May 2022 (UTC) :hard to read I'm glad I stayed the same as before No changes required [[Special:Contributions/240B:11:E7E0:5E00:6005:3399:E6C:2B48|240B:11:E7E0:5E00:6005:3399:E6C:2B48]] 14:06, 2 July 2022 (UTC) :Strongly agree. I want to decide the readable width for me. In the old skin and most websites, I can do it by adjusting the width of window. I definitely don't want to care about "CORRECT READABLE WIDTH FOR EVERYONE" decided by someone somewhere, even if they are great scholars. [[User:Kyoku|Kyoku]] ([[User talk:Kyoku|talk]]) 08:32, 10 July 2022 (UTC) After reviewing the posted defense of the narrowing and the feedback listed here, this feature belongs entirely as an optional setting. It most certainly should not be the website's default. [[User:RightQuark|RightQuark]] ([[User talk:RightQuark|talk]]) 01:29, 24 May 2022 (UTC) :The defence of the narrowing seems to have little real-world bonuses. It may be theoretically good but makes it bad to read because Wikipedia articles can be long [[User:Torqueing|Torqueing]] ([[User talk:Torqueing|talk]]) 17:10, 24 May 2022 (UTC) I'm fine with the text being narrow but the ui and nav bar should be full width. --[[User:Thedonquixotic|Thedonquixotic]] ([[User talk:Thedonquixotic|talk]]) 00:18, 26 May 2022 (UTC) :@[[User:Thedonquixotic|Thedonquixotic]], what do you mean by the ui and nav bar? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:54, 8 June 2022 (UTC) ::Not sure what is unclear here. I mean the navbar. As in the bar up at the top of the page with use account, search etc. [[User:Thedonquixotic|Thedonquixotic]] ([[User talk:Thedonquixotic|talk]]) 19:07, 1 July 2022 (UTC) I also have a wide screen monitor. I do not like this forced width shrinkage in the Vector 2022 skin. [[User:OhanaUnited|<b><font color="#0000FF">OhanaUnited</font></b>]][[User talk:OhanaUnited|<b><font color="green"><sup>Talk page</sup></font></b>]] 17:24, 9 June 2022 (UTC) In current form without a toggle for width this layout is unacceptable on large monitors. Even my old 14'' monitor. For now I am reverting to avoid having in forced horizontal white-space. [[User:Phatom87|phatom87]] ([[User talk:Phatom87|talk]]) 14:32, 20 June 2022 (UTC) :Absolutely unacceptable, too narrow, an unjustified waste of space. [[User:Loupeter|Loupeter]] ([[User talk:Loupeter|talk]]) 10:39, 24 June 2022 (UTC) :It sounds like the fixed-max-width (assuming one's window is wide enough, and regardless of how much wider it might be) is a compromise between the needs of two different types of reading activities. I have both habits (skim vs detail-read), and felt especially the concern that the text doesn't obey what *I* do with my window. A reason I might widen my window is exactly because I want wider content. A comprimse necessarily isn't ideal for either one side. A better solution is to make it easy and discoverable how to get the *best* feel for whatever one is trying to do, rather than forcing so many to have a sub-par experience. A third-party gadget isn't discoverable and is surely more fragile than a first-class toggle feature of the skin itself. [[User:DMacks|DMacks]] ([[User talk:DMacks|talk]]) 15:16, 29 June 2022 (UTC) In my opinion, [[Skin:Timeless]] does a much better job at restricting article space to improve readability. This is because the UI is not entirely positioned on the left-hand side of the screen, and the background colour is not blindingly bright. If the intention is to create whitespace, please don't use bright colours. Timeless also has more space for pictures. For the past 20 years, articles have been written with the understanding that 80%+ of the screen will be for content. There are width and upright tags all over the place that, once viewed with this narrow a perspective, become overwhelming. A skin should not change the fundamental readability of the page. Compare [https://en.wikipedia.org/wiki/The_World_Before_the_Flood?useskin=vector-2022 this] with [https://en.wikipedia.org/wiki/The_World_Before_the_Flood?useskin=timeless this]. In Timeless, when the content ends, grey begins. In Vector 2022, it looks like the HTML was corrupted and failed to load because it continues with white for no discernable reason. Vector also artificially makes articles look longer than they are, which may actually dissuade people from reading. For instance, using a 27" 16:9 monitor, on the article for Barack Obama, [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=vector-2022 Vector] just about lets me see the entire lead on my screen at once. [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=timeless Timeless] allows me to see the whole lead quite easily, as well as part of the ToC. [[:en:Line length|Line length]] may be a thing, but you must take into account the total amount of text on the screen at once, too. There's no use having the perfect 50 character line if you need 100 of them all bunched up together. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:18, 13 July 2022 (UTC) :Quick update and aside: I just learned about wide-vector-2022. This is fantastic. I actually like the ToC being placed where it is when using that gadget. If the plan was to make the wide skin the default, I would be less hesitant. For comparison with the links in my previous message, [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=vector-2022&withgadget=wide-vector-2022 here is Barack Obama] with wide-vector-2022. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:25, 13 July 2022 (UTC) ::This "wide-vector-2022" version should be the default IMO. [[User:Some1|Some1]] ([[User talk:Some1|talk]]) 02:50, 17 July 2022 (UTC) :> For the past 20 years, articles have been written with the understanding that 80%+ of the screen will be for content. :I'll just note that for the past 10 years that means you've written things that just do not work that way on mobile. :) :> A skin should not change the fundamental readability of the page. [..] In Vector 2022, it looks like the HTML was corrupted and failed to load because it continues with white for no discernable reason. :This seems like a lot of assumptions to me personally. Do we have wider evidence for this ? :> There's no use having the perfect 50 character line if you need 100 of them all bunched up together. :Literally every mobile user on the Barack Obama page, the majority of the readers. Screens and screens till you hit the end of the lead... —[[User:TheDJ|Th<span style="color: green">e</span>DJ (Not WMF)]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 20:20, 14 July 2022 (UTC) ::{{tq|I'll just note that for the past 10 years that means you've written things that just do not work that way on mobile. :)}} :::MinervaNeue, when viewed on normal phone screens, ignores width tags. The only difference between writing for desktop screens and mobile screens is file placement. ::{{tq|This seems like a lot of assumptions to me personally. Do we have wider evidence for this ?}} :::I don't need to provide evidence to state my opinion. The page looks unfinished with the extra whitespace on the right hand side. If you do want more than just my opinion, CNTRL+F for "whitespace" on this page. 12 other posts mention it. ::{{tq|Literally every mobile user on the Barack Obama page, the majority of the readers. Screens and screens till you hit the end of the lead...}} :::Difference is that my phone is in my hand. I'm not getting overloaded with line after line if the screen is only 15cm long. I can see a whole paragraph on at once and then scroll when necessary. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:10, 15 July 2022 (UTC) == Keyboard shortcut does not focus search field in sticky header == {{tracked|T307024}} When pressing the keyboard shortcut for search (alt + shift + f) the search field at the top of the page is focused, even if the sticky header is showing. It would be better if the search field in the sticky header was focused. As it is now the page will scroll to the top which is unnecessary. [[User:Sebastian Berlin (WMSE)|Sebastian Berlin (WMSE)]] ([[User talk:Sebastian Berlin (WMSE)|talk]]) 16:10, 12 January 2022 (UTC) == Page-title and Search == In a nutshell, I believe * the Search would benefit from being (a) more consistently placed, and (b) more accessible from the sticky header by having a larger click-target. ** See image at [[:File:Vector-sticky-header-version1-search-size.png]] (and more [[#Search_box_size_and_location|details above]]) * the Page-title is already visible in multiple locations, and ''might'' not need this additional instance? AFAIK only users with "Fullscreen - F11" enabled would hide the existing locations where it is already displayed, whilst scrolled. ** See image at [[:File:Page_title_repetition_and_cutoff.png]] Hope that helps! –[[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 20:53, 21 January 2022 (UTC) == Feedback regarding the new language switcher == Hello, I am a French person using Wikipedia in both French and English. I usually decide the language of the article depending on the topic. If it's related to France, I know the French version is going to be better. If it's a general topic, I usually select English. However, it's been a few months that the language picker has been moved to the top of the screen when an article is display in French. And I really can't get used to it. Sure, it's easy to discover - but it's more complicated to use. Having to click twice is a regression for anyone switching language frequently. An action that used to require half a second now takes 2 seconds. If you do this about ten times every time you browse Wikipedia, it does become irritating... I hope this feature is not shipped to other languages, and France gets the sidebar back. If you want to make this feature more discoverable, maybe you could add a shortcut but keep the sidebar. Or display a tooltip once in a while to educate newcomers. But please, keep "heavy users" of language switching in consideration. Thanks {{unsigned|77.148.113.166|19:54, 25 January 2022}} : I'd state this as 'what used to take me a second (finding the right language) now takes 10': Open language switcher, often don't see the language I want, have to search? want to see which languages have a version, have to scroll; don't have a quick way to default present all languages by-alpha. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 16:49, 2 May 2022 (UTC) : I have to agree with this as another French person frequently switching languages on Wikipedia and Wiktionary. I should add, in addition to the intrinsic usability of the interface (I do agree it's a slight regression for my usage), the fact that most language editions still use the old interface (and most other sites using mediawiki, and the latter is likely to remain the case for a long time) means you don't actually get the opportunity to unlearn it. So every time I want to switch languages from a French page, I will first scroll down to the old location and waste 1s parsing the sidebar and wondering where the links are. I check out other languages almost every time I read any article and those milliseconds of irritation do add up. Anyway, I strongly think that “don't fix what ain't broke” should apply here! [[Special:Contributions/37.183.2.114|37.183.2.114]] 12:06, 8 May 2022 (UTC) : +1 to [[User:Sj|Sj]]. --[[User:ThurnerRupert|ThurnerRupert]] ([[User talk:ThurnerRupert|talk]]) 18:58, 11 June 2022 (UTC) Often I use the language switcher not to navigate to the article on different language, but just to look up how that article is titled in a different language. In other words, using Wikipedia's inter-language links as a sort of dictionary. By hovering over the list of languages I can gather multiple titles, see their similarity between languages. With the New Look, language switcher became less accessible, though gathering titles by hovering still works there. Also this new dropdown-based language switcher seems either to require tricky CSS features or JavaScript. Will it make problems for simplistic browsers like w3m? [[User:Vi2|_Vi]] ([[User talk:Vi2|talk]]) 17:48, 20 May 2022 (UTC) I find the language switcher the worst of both worlds of the two variants in the old interface. It can be annoying to scroll through 200+ languages in an idiosyncratic ordering (for example, كوردی [Kurdi in Perso-Arabic script] is filed under S for Sorani), but at least I can see them all and preview the name of the article in various target languages. With the drop-down menu in the old interface, I get the languages grouped geographically, and I can also search for a specific language, with the system recognizing many name variations. The new interface gives me a drop down menu with all 200+ languages in the same idiosyncratic order, with no geographic grouping and no ability to search for a specific language. [[User:LincMad|LincMad]] ([[User talk:LincMad|talk]]) 22:28, 25 May 2022 (UTC) I am primarily an active user on the Japanese Wikipedia (now defaulted to vector2022) and I agree with you completely. Why doesn't this use the blank spaces on the left and right? No need to hide buttons and functions everywhere just to make the page look hollow. As for the other features, there are so many problems with the new Vector. I definitely want the old version to remain. I will continue to use it and not the new one. --[[User:Sugarman|Sugarman]] ([[User talk:Sugarman|talk]]) 07:14, 6 July 2022 (UTC) == Feedback on ToC functionality == Hello, I’m not sure how far you are in the development of the new table of content functionality, but I was looking at [https://en-toc.wmcloud.org/wiki/Moon this prototype] and noticed a potential problem. Here the ToC is on the side and that’s a good thing, but the ToC in the text have also been deleted and that’s not much a good thing. When there is a big infobox, the in-text ToC compensate partly or totally for it, hence the page arrangement take it into consideration for the position of the images. Now if you delete it, all the text will go up, along with the images, but the images can’t always follow, because the infobox, so the right-aligned images are going to pile under it, while the left-aligned will reduce the text to a very small column between them and the infobox. On fr:wp, infoboxes are very widely used, so deleting the in-text ToC is going to break the page layout of most articles (and rather probably upset the community). So I’d suggest that, whatever you do with the ToC, to not delete the in-text ToC until there is also a functionality to move the infobox outside the text too (that would be great by the way, as infoboxes always cause difficulties with page layout). --[[User:Runi Gerardsen|Runi Gerardsen]] ([[User talk:Runi Gerardsen|talk]]) 09:30, 7 February 2022 (UTC) :I would like to add myself as having this same concern about images. At present, image placement in many articles was determined by this factor of the TOC being inline, sometimes offsetting the issues of long infoboxes and allowing the first image in the first section to be right-justified (like anyone with any experience in professional publishing, I ''really'' hate left-justified lead images as they break up the flow of the text by interposing themselves between heds and text. Similarly, I try to maintain alternation in the justification of images since that mirrors the sweep of our vision and makes text with images easier to read (but of course you don't do this when it creates other layout issues).<p>''When'' this is deployed, a lot of articles are going to suddenly have image placement issues at the top that didn't previously. And this will probably make a lot of people ''very angry''.<p>I can see the need for the sticky TOC but I think it would still be better as something that could be toggled there from its current position while reading depending on how the user prefers it in an individual article. [[User:Daniel Case|Daniel Case]] ([[User talk:Daniel Case|talk]]) 05:50, 29 April 2022 (UTC) ::What if we kept both the inline/in-text ToC ''and'' the sticky/sidebar ToC, but only display the latter when the user's scrolled past the former? A user preference could be added that forces the latter to always (or never) be displayed. I agree that the situation with images is a <abbr title="Pain In The Frigging Arse">PITFA</abbr>, but I really don't want to give up the sticky ToC either… [[User:OmenBreeze|OmenBreeze]] ([[User talk:OmenBreeze|talk]]) 00:43, 6 July 2022 (UTC) I'm not sure, but until I manually switched back to "Vector legacy (2010)", then again to "Vector (2022)", ToC section was absent completely (neither new-style nor old-style). Also maybe, like with the language switcher, there should be [temporary] notice about ToC having moved to the left where it was previously? [[User:Vi2|_Vi]] ([[User talk:Vi2|talk]]) 17:57, 20 May 2022 (UTC) == Feedback on new language switcher in French == As a translator, I litteraly jump from one language to another every hour of every day. It is simply unbearable to now have to go to a sub-menu to switch from French to English or Italian. That added click translates (pun intended) into lost time and nerves on a daily basis. I'm not hostile to a more smartphone-friendly interface, and maybe that kind of switcher is perfect on a little screen. But it's not okay to make the overall experience so much unsteady (especially with the links being there for some languages and moved away for other ones) when # switching seamlessly from one language to another is precisely the one advantage Wikipedia has over any other encyclopedia and # my 32" monitor has plenty of space to display these links in the left column. Last year I had selected the old Vector theme for this very reason and this morning, I was force-switched into the new Vector 2022 theme. So for the second time I'm back on the classic Vector theme and really, really hope it will stick. [[User:Herisson26|Herisson26]] ([[User talk:Herisson26|talk]]) 22:16, 7 February 2022 (UTC) :Hello @[[User:Herisson26|Herisson26]]. Thank you for asking here. :* We've been planning to provide [[Reading/Web/Desktop_Improvements/Features#Language_switching_2:_One-click_access_to_preferred_languages|one-click access to preferred languages]] but it's dependent on the work of another team ([[Wikimedia Language engineering|Language]]). We can't promise anything in terms of the timeline yet. :* What do you mean by "with the links being there for some languages and moved away for other ones"? You saw the new Vector on some wikis, and the old Vector on some other wikis, didn't you? I think that's related to the next issue. :* Why you had to switch back again - [https://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Caf%C3%A9_dos_programadores&diff=prev&oldid=62956756&diffmode=source here's my explanation]. We're sorry, this was an extremely rare oversight. :* It's interesting that you write this interface is smartphone-friendly. Many volunteers note this. Out of curiosity, what makes you think that? Is this just about the responsiveness, or something more? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 00:30, 17 March 2022 (UTC) ::Hello @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], ::* For a translator, direct access to "preferred" languages is not enough. I need the complete list of languages, as it exists on old Vector. My preferred languages would be French, English, Spanish and Italian, but I will regularly read directly a page in Japanese, Portuguese or any other if it's the one that will get me the information I'm looking for (which is quite often the case when dealing with foreign people). So limiting direct access to a select few languages will still break Wikipedia for me. ::* Yes, lots of wikis use old Vector while the French one uses the new ones. It completely breaks the user interface. It is of utmost importance to me that all Wikipedia pages have the same layout, whatever the language. I understand the need to test things, but when you make a public switch that impacts the ergonomics of the site, it should be made across all languages. Maybe make the change per-user instead of per-language if you don't want to switch everyone at once. ::* Nothing to do with responsiveness. Smartphones don't have the physical space to display the language list and the article content at the same time, so having a button on the top of the page to show/hide the language panel makes sense. It does NOT on computers, which have plenty of free space for the left column and the traditional language list. ::[[User:Herisson26|Herisson26]] ([[User talk:Herisson26|talk]]) 08:21, 18 March 2022 (UTC) Very bad indeed. The French version of Wikipedia, which has put all interwiki language links in a dropdown menu, is most annoying. It is a big waste of time, and not user-friendly at all. To switch to the article in another language, instead of having the whole choice displayed at once and just having to click, one now has to go back up to the right-hand corner of the article, click on the dropdown menu, scroll down the list until the desired language apears, click again... This change is not an improvement. It tends to isolate each linguistic version of Wikipedia, by rendering the language switching much harder. If ever it is useful for smartphones, please change the layout for mobiles only ("m" version of Wikipedia), but not for the desktop version. This cumbersome change should NOT be extended to other Wikipedias, and the French version should revert as soon as possible to a user-friendly layout, such as that of the English language Wikipedia. [[User:Baronnet|Baronnet]] ([[User talk:Baronnet|talk]]) 15:49, 20 March 2022 (UTC) @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] very cool that you bring one click different language!! would you please include the language team in this discussion here, and provide a link so people can view the progress? --[[User:ThurnerRupert|ThurnerRupert]] ([[User talk:ThurnerRupert|talk]]) 18:56, 11 June 2022 (UTC) == TOC Feedback == I noticed that the newest designs for the table of contents do not allow for it to be collapsed. I think the ability for the TOC to be collapsed is very important, specifically for users that have a touchscreen laptop. I and a friend of mine often use our left hand and our touchscreen to scroll articles because on our laptops it is often easier to scroll quicker than to use the touchpad. If the TOC remained expanded we might accidentally tap a link. A button to collapse it and a preference to expand or collapse it by default would be nice. [[User:Lectrician1|Lectrician1]] ([[User talk:Lectrician1|talk]]) 20:07, 8 February 2022 (UTC) :Hello @[[User:Lectrician1|Lectrician1]]. Indeed, the first version of the TOC was not possible to be collapsed. This was because the results of user testings (both in-person and on-wiki) didn't indicate that the functionality was important. Now, given the feedback we've collected, we've decided to consider options how to make the TOC collapsible. In this context, what do you think about our [https://di-collapsible-menus.web.app/Brown_bear newest prototype]? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 13:46, 6 May 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] Thank you for responding! :::Hi, @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], I came to this page to ask whether the ToC can be moved from the sidebar, and really like the prototype. However it seems to be malfunctioning in Safari 15.4 (17613.1.17.1.13): https://imgur.com/a/O0Jhti1 :::Thanks. [[User:HughLilly|&#32;—Hugh]] ([[User talk:HughLilly|talk]]) 05:43, 20 May 2022 (UTC) ::My feedback: ::* I really dislike the usage of the bracket type of buttons for <code>[hide]</code> and think a OOUI button or a smaller alernative should be used instead. ::* I like that all of the headers in the TOC are collapsed by-default, however, I think they when you're scrolling inside of a section, they need to expand and collpase as you go through one section to another. I've seen this functionality on other platforms and it allows the reader to understand the outline better when they're viewing the article. ::* The hiding action of the TOC has an inconsistent navigational pattern. UIs should always require the same amount of actions to disable something as to enable something. That always feels the most natural. Hiding the TOC for its default position requires one button press, but to return it back to its previous state requires two. Also, its location next to the title and then how it switches to the upper left to become sticky is really weird too. I don't like either of those locations. I was thinking it could look something like this collapsed and you could press the icon on the right to both collapse and expand it: ::[[File:MediaWiki table of contents collapsed idea.png|frameless]] ::[[User:Lectrician1|Lectrician1]] ([[User talk:Lectrician1|talk]]) 00:42, 7 May 2022 (UTC) Hi, i just cant find the table of contents, i need it for easier navigation. please, help == Sticky header in the namespace Project == ([[:fr:Discussion_utilisateur:Patafisik_(WMF)#En-tête_figé_et_accès_aux_langues|original discussion in French]]) Hi, a user suggests to add the sticky header in the namespace Project too, not only in [[Talk:Reading/Web/Desktop_Improvements#Talk_page_and_page_history|Talk pages or History pages]] (see for exemple [[phab:T289641#7365946]] and [[phab:T299115]]). Best regards, [[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 09:15, 9 March 2022 (UTC) == Left margin menu pushes down content == I normally use Monobook, but happened to get into the new Vector. Odd experience. The search box was absent and I had to scroll down for the content. I now see that you are supposed to click the magnifying glass to get the search box. OK. But the scrolling? It seems the new Vector tries to guarantee wide enough space for the content. Perhaps that's what people surfing with maximised windows expect, but if you have a narrower window, is that really optimal? To get the left margin menu to the left of the content, I need a window some 1000 px wide. This "minimum" width gives me lines of about 100 characters, while I've heard reading is easiest at 47–72 or something like that. I like to have several windows open in parallel, and a narrower windows makes them fit better. Anyway, if one's browser window is narrow, for whatever reason, does the empty space to the right of the margin menu really give the best possible experience? Is the 100 char width something that needs to be guaranteed for those planning layout of individual articles? (This experience is with Firefox 91.7.0esr on Debian.) –[[User:LPfi|LPfi]] ([[User talk:LPfi|talk]]) 20:07, 17 March 2022 (UTC) == Questions I shouldn't need to ask == I can tell WMF developers put a lot of work into this, but I'm sorry, this isn't cutting it. This latest prototype is Vector in name only. It's a completely different look and a completely different experience. * Why do I have to click twice to get to my talk/contribs/preferences? * Don't you think you could have fit those important links if you didn't go overboard on the whitespace or if the search bar wasn't so enormous? * Is the language switcher really so important that it belongs in the sticky menu? * I had to think for a few seconds about what the hamburger/star icon was (it's the Watchlist). Why are the icons necessary? I'll answer this one — too much whitespace at the top. * Why is the new interface such a step down for the editors who will have to use it every day? * ''And why are you still trying to put a hamburger menu on a desktop site?'' It's not all bad — I do think the max width improves readability. But that was already present on previous less-bad prototypes. We were promised "improvements" to Vector, and what we're getting is an entirely new (and entirely inferior) skin. If this is really going to still be called Vector, that is highly misleading. The early comments that "total replacement is not an option" don't make a lot of sense now that Wikipedia appears to be getting exactly the top-down redesign I had feared this project would produce. Pigs will fly before this gets deployed to English Wikipedia ''without'' the community getting their pitchforks. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 04:45, 26 March 2022 (UTC) : I went into Preferences to turn off the changes and I saw that the software is now treating "vector-2022" as a new skin. This is better than what I thought was going on but maybe there should be a more original name> : Also, wouldn't it be a much better use of developer time to, say, work on the many unresolved Community Wishlist items? —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 17:09, 26 March 2022 (UTC) ::Hi @[[User:Pythoncoder|Pythoncoder]], thanks for these comments. I'd just like you to know that I'm working on an answer for you and I'll paste it soon. You've asked many important and basic questions (like the one about the Community Wishlist Survey), and I'm truly happy that you've done that. It's much better to clarify the basics. You don't know whether these are clear as long as no one questions it. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 00:53, 8 April 2022 (UTC) ::: {{ping|SGrabarczuk (WMF)}} I should have made it more clear above, but most of my comments are regarding the Fourth Prototype. And now that I read through my earlier comments it makes sense to make the sidebar collapsible in case readers don't want distractions. I believe the sidebar is shown by default so please disregard my complaints in that area. This is why I shouldn't edit when I'm sleep-deprived. I do still think the new skin needs a new name though. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:03, 8 April 2022 (UTC) ::: Also re: wishlist, I suspect the two projects are probably worked on by completely different dev teams. Again, I'm sorry for the passive-aggressiveness above. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:06, 8 April 2022 (UTC) ::::Hello @[[User:Pythoncoder|Pythoncoder]], no worries, I'm really glad you've figured some issues out yourself! Would it be possible for you to state what remains unclear? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:05, 14 April 2022 (UTC) :::::I think it mostly boils down to the amount of whitespace at the top and the hiding of important links such as talk, contribs, and login under a dropdown. I think this should be fixed. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:28, 15 April 2022 (UTC) == Sticky header doesn't show the name or the logo of the project: the risk of loss of identity for Wikimedia sister projects == ([[wikt:fr:Wiktionnaire:Wikidémie/mars_2022#Interface_bureau_%3A_venez_tester_le_quatrième_prototype|From French Wiktionary]]) {{Tracked|T293395}} "I'm still observing the same problem when using this new skin: if you scroll down the page, it's impossible to know on which Wikimedia project you're on. The sticky header doesn't include the name of the site you are on, which is penalizing users for sharing screenshots, but also for identifying the editorial lines/ editorial policies of the different projects. Sister projects have important specificities. On the French Wiktionary, we already have people complaining that they can't find the content they expect to see on Wikipedia, and we have to tell them that it doesn't belong on the Wiktionary. I'm afraid that the phenomenon will only get worse."-Translated by --[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 13:28, 29 March 2022 (UTC) (original message: ''"J’observe toujours le même problème, que je constate au quotidien en utilisant ce nouvel habillage : on ne sait pas sur quel projet on est dès que l’on défile un peu. L’en-tête fixe n’intègre pas le nom du site sur lequel on se trouve, ce qui est pénalisant pour le partage de capture d’écran, mais aussi pour l’identification des lignes éditoriales des différents projets qui ont des spécificités importantes. On a déjà actuellement des gens qui se plaignent de ne pas trouver tel contenu qu’ils s’attendent à voir sur Wikipédia, et à qui on doit répondre que ça n’a pas sa place sur le Wiktionnaire. Je crains que le phénomène ne fasse qu’empirer. [[user:Noé|Noé]] 29 mars 2022 à 12:37 (UTC)"'') == The "sticky table of contents" is the worst among all the bad changes == I am sorry, but this sticky table of contents is such an eyesore, its sole addition might make me quit reading Wikipedia altogether. I'm not exaggerating, a similar update to Liquipedia made me want to avoid that project. It's more than an annoying waste of screen space - it also makes the different parts of the table of contents bold depending on where in the article my screen is, and thus it triggers my OCD, and it simply irritates me. I hate these moving parts in forced mobile designs. > "The results of our 3rd prototype testing showed an overwhelming support for the proposed table of contents." Have they? I don't see any discussion here. > "The new table of contents will be persistent - users will have access to it at all times. It will also make it easier to understand the context of the page." Are the TikTok memes reality? Excuse me, but I don't randomly forget what page or section I'm reading, thus I don't need a sticky title on my screen at all times. > "In addition to that, it will be possible to navigate to different parts of the page without having to scroll all the way back to the top." How is that "need" in any way difficult? It's one button on the keyboard - called ''Home''. Or you hold the slider on the right and jerk it up in a millisecond. But I suspect I know where "scrolling" is an issue - on mobile phones. This entire update in an exercise in transitioning a fine desktop UI from the 2000s which I had an honour to fall in love with in the 2010s to the non-constructive, downgraded, annoying and irritating experience of mobile phones. Thankfully, not all projects choose to go this way. For an example of a new encyclopaedia with a traditional design, see the immensely popular Korean Namu Wiki. [[User:Adûnâi|Adûnâi]] ([[User talk:Adûnâi|talk]]) 12:53, 10 April 2022 (UTC) :100% agree. [[User:Football Lab|Football Lab]] ([[User talk:Football Lab|talk]]) 09:12, 26 June 2022 (UTC) == some feeback on the layout == I really like the preview, it is much cleaner, a few thoughts from viewing this on desktop (I saw the Blue whale article and the Potato article): # The 'in other projects' section is really nice, however I wonder what would be a sensible heirachy for this. Should it be contextual based on the topic or something else? Currently its suggesting me WikiNews which isn't relevant or a particularly well maintained Wikimedia Project. Also the other projects is more about navigating to other information on that topic, rather than being a tool, I wonder if it should be under the TOC instead? Its more about navigating information on the topic rather than using a tool. # I'm not sure if this is intended, the images sit on top of the sections instead of being displayed along the side the text, especially for portrait format images this creates a lot of empty space. # When logged out having the TOC on the left is really nice, works really well. But when I'm logged in the TOC is hidden under half of the tools but then the other half is on the right hand side is quite confusing. I realise this is a really difficult thing to organise, maybe it could live under the TOC? There isn't a clear deliniation between reading and contributing which is confusing. # The taxonomy templates at the bottom are pretty broken and make long lists, also lists within the Potato article lose their formatting meaning on the page for potato the list of synonyms is one column wide making a very long section which isn't going to useful for a general reader right in the middle of the article. [[User:John Cummings|John Cummings]] ([[User talk:John Cummings|talk]]) 18:03, 12 April 2022 (UTC) == I hate the new TOC == I was directed here from [[phab:T273473]].<br /><br />That left-of-the-article TOC is a horrible nightmare. I absolutely hate it. I would seriously avoid any website that forced it upon me. Can't scroll it out of sight, can't collapse it, can't disable it, takes up too much space, I hate it I hate it I hate it. This was the reason I switched back to Vector classic on beta cluster. (and if Vector classic gets it too I'll switch to Monobook, Timeless or just murder it with a userscript) I'm not much of a fan of Vector 2022 (but it's not a lost cause, just needs work), but this TOC pushed me over the edge.<br /><br />As a personal note: I rarely use the existing TOC. But I can scroll it out of sight so it doesn't bother me. If the TOC went completely missing tomorrow, I wouldn't miss it. Having this big, (to me) useless thing that contrasts with the main content (it's much darker) permanently in my field of vision greatly annoys me. And because of the fixed position, my banner blindness fails to kick in. This results in pure hatred for something that, on the face it, could seem innocuous. <span id="Alexis_Jazz:1650385558357:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 16:25, 19 April 2022 (UTC)</span> :I was not "directed" anywhere, I blundered onto here after finally finding information about this new skin. And let me be clear, APART from the ridiculous handling of the TOC, the new skin is great, precisely BECAUSE, before the TOC-debacle, this skin allowed me to get more of the article on the screen, and allowed me to hide the standard list of menu choices that I only need 0.something % of the time. :So, please, Please, PLEASE make that TOC hideable! It's perhaps (!) a great default for newbies, but it's a bloody nuisance for us who usually never use the TOC, and if we do, we know where to find it! [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 21:49, 25 April 2022 (UTC) ::I totally agree. [[Special:Contributions/185.53.157.151|185.53.157.151]] 08:13, 26 April 2022 (UTC) ::@[[User:Autokefal Dialytiker|Autokefal Dialytiker]], right, it's not that easy to get here. We'll put link to the project page on the list of available skins in preferences. The task is documented as [[phab:T307113|T307113]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:25, 28 April 2022 (UTC) :Hey @[[User:Alexis Jazz|Alexis Jazz]] - thanks for talking to us. It’s good to hear you were using Vector 2022. I hope that you will switch back to it. In terms of the table of contents, you raise good points. A lot has been happening since you wrote your comment, so my answer is longer than it would have been last week. :* The first version of the design was based on the feedback we got on our previous prototypes from readers and editors (see [[Reading/Web/Desktop Improvements/Repository/Sticky Header and Table of Contents User Testing#toc-intro|in-person reader & editor testing]] and [[Reading/Web/Desktop Improvements/Third prototype testing|on-wiki community testing]]). :* That said, we have not yet made the design final. We are working on different ideas for the visual design of the entire site. We'll make the main content of the page be the primary focus of attention, even when other navigational elements (such as the ToC) are present. If you’re interested in following along with that work, most of it will be tracked on [[phab:T301780|T301780]] and in subtasks of that ticket. :* We are also considering the way the ToC will display at smaller resolutions ([[phab:T306904|T306904]], [[phab:T306660|T306660]]) and looking into some options for collapsing it that could work for wider screens as well. :* As you can see, people like you who have chosen Vector 2022 individually share a lot of feedback with us now. [[phab:T307004|T307004]], [[phab:T306562|T306562]] are some examples on things we are or will be working on. :* In the meantime, we will be A/B testing the ToC on the pilot wikis. Our hypothesis is that the ToC will decrease the amount that people have to scroll to the top of the page to switch to a different section. The design might also vary once we have the results of the test. :* Since these changes might take a little while to reach the beta cluster, we would also encourage technically-skilled folks to set up a script or gadget to make a temporary solution. :And... yeah, [[Newsletter:Desktop Improvements updates|subscribe to our newsletter]], join our office hours ([[Reading/Web/Desktop Improvements/Updates/Talk to Web|tomorrow]] or [[Reading/Web/Desktop Improvements/Participate|later]]) and talk to us more. Thank you! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:23, 28 April 2022 (UTC) ::[[User:SGrabarczuk (WMF)|SGrabarczuk]], here's another thought: [[wikt:reverse]]. It's not a long page, but that TOC is so bloody huge a full HD display isn't enough to read ''any'' of the actual page content without scrolling. <span id="Alexis_Jazz:1651369145562:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 01:39, 1 May 2022 (UTC)</span> :::Right, right. Let's just take a look at [[:pl:Gramatyka języka fińskiego]]. I mean, this is an edge case, and as such, it's not that critical. From what I know, all TOC sections aren't uncollapsed by default, and you need to make an effort to see the full TOC. Is this your experience, too, @[[User:Alexis Jazz|Alexis Jazz]]? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:45, 5 May 2022 (UTC) ::::[[User:SGrabarczuk (WMF)|SGrabarczuk]], sorry for being possibly unclear. It was just a thought about the classic inline TOC which is disproportionally huge on Wiktionary, so it's something to think about when designing a new TOC. On the Gramatyka page on plwiki you at least get the intro without scrolling and the page actually ''is'' very long, so it's understandable the TOC also gets big. I've taken a look at the CSS (should have done that sooner) and simply disabling "position:sticky" stops the new TOC from being so infuriating. IMHO that should be the default, or at the very least, proper research should be done into this. Not only to determine by majority vote what users prefer (I wouldn't be surprised if sticky wins a binary majority vote) but also how crazy either option can drive users who ''don't'' like it. Pleasing a majority is no good if it causes a minority to be greatly aggravated. While I personally can get around it using technical means, that isn't true for most people. I'll also note that the experience on devices that are primarily controlled with a touchscreen may very well be different. With a keyboard, scrolling back up to the TOC is nearly no effort. Just press "home" or hold "page up". With a touchscreen, not so much, so I can see why sticky might have a greater appeal there. <span id="Alexis_Jazz:1651821096574:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 07:11, 6 May 2022 (UTC)</span> :::::What TOC? I don't get any such thing. [[User:Betaneptune|Betaneptune]] ([[User talk:Betaneptune|talk]]) 17:36, 25 May 2022 (UTC) :100% agree. [[User:Football Lab|Football Lab]] ([[User talk:Football Lab|talk]]) 09:14, 26 June 2022 (UTC) == Watchlist icon == [[User:Schierbecker|Schierbecker]] [[Topic:Wu23w3nlomndp5f1|wrote]]: <blockquote>The watchlist icon too closely resembles a hamburger menu button. I can see many clicking the button thinking it is a dropdown menu. Some may lose unsaved edits after clicking it.</blockquote> I completely agree, but not really because it resembles a hamburger button but because it's sandwiched (no pun intended!) between dynamic menus. If there was the dropdown arrow next to the interlangs, alerts and notices buttons just like the personal menu, it would communicate more clearly that the watchlist button is a simple link and not a menu. [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 02:38, 21 April 2022 (UTC) :Thanks for this comment, @[[User:Nardog|Nardog]]. We'll think how we could improve this. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:55, 27 April 2022 (UTC) ::Information on the design process that led to the current icon can be found here: ::https://phabricator.wikimedia.org/T297979 ::Nardog is already involved in that task. It's probably best to add this feedback there, as not all designers are reviewing this talk page. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 17:01, 6 July 2022 (UTC) == Sidepanel is bloated == Tonight size of left panel is increased too much. It covers more than ¼ screen now. https://imgur.com/3YJlcii Can I reduce size of panel, as it was before? [[User:Tucvbif|Tucvbif]] ([[User talk:Tucvbif|talk]]) 21:18, 25 April 2022 (UTC) : Agreed. I feel there's too much white space padding the left and right of the sidebar. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 00:53, 26 April 2022 (UTC) :@[[User:Tucvbif|Tucvbif]] @[[User:Tenryuu|Tenryuu]] thank you for these reports. It seems like you may have your browser window zoomed in, is that correct? Also, if you are able to please add any additional thoughts, needs, screenshots, and ideas to this task: https://phabricator.wikimedia.org/T306660. [[User:AHollender (WMF)|AHollender (WMF)]] ([[User talk:AHollender (WMF)|talk]]) 14:54, 26 April 2022 (UTC) ::No, my browser not using zoom. I using personal css with font-size 14pt, but when I login to other account without personal css, the sidepanel still terrible huge. ::https://imgur.com/l8bIrDF [[User:Tucvbif|Tucvbif]] ([[User talk:Tucvbif|talk]]) 15:07, 26 April 2022 (UTC) :: @[[User:AHollender (WMF)|AHollender (WMF)]]: Apologies, I should have clarified. The sidebar here is fine; the one at Wikipedia isn't. Resetting the zoom level on Wikipedia doesn't address the issue; there's still a lot of white space padding the element. I'll leave this discussion and focus on [[#I oppose the new sidebar/TOC]] and the mentioned Phabricator ticket, which describes my issue more accurately. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 15:10, 26 April 2022 (UTC) ::: The ambiguity and confusion evident from the preceding discussion suggests that the interface has become to complex. Aren't the original sidebar and TOC at the top of the page enough? Why change? Is another popup menu necessary to switch language? What about setting language in user preferences? Simplify, simplify, simplify. Regards, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|talk]]) 00:28, 25 May 2022 (UTC) == TOC limit doesn't work anymore == It seems that this "sidebar TOC" has different classes, making [[:en:Template:TOC limit]] doesn't work anymore. [[User:William Surya Permana|William Surya Permana]] ([[User talk:William Surya Permana|talk]]) 07:46, 26 April 2022 (UTC) :Templates can only control the content of an article so [[en:Template:TOC_limit/styles.css]] won't apply outside the article area so new classes won't help here. A magic word would need to be added so support this use case if important and time allows. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 15:37, 26 April 2022 (UTC) == I oppose the new sidebar/TOC == Please make it possible for the users to collapse the left sidebar/TOC or to reduce the white space size. I for one use a browser sidebar (Sidebery) as well as 150% or even bigger text size. Combined with the forced sidebar/TOC, the actual line length becomes much smaller than the recommended length. [[User:PeterTrompeter|PeterTrompeter]] ([[User talk:PeterTrompeter|talk]]) 08:43, 26 April 2022 (UTC) :Hi @[[User:PeterTrompeter|PeterTrompeter]] - thanks for your feedback. We're currently exploring better solutions for the ToC at narrow widths, which include the option of collapsing as well. Check out [[phab:T306660]] for the details and prototypes. It would be great to get your opinion on some of these. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:40, 26 April 2022 (UTC) ::I wonder about one thing: Who on earth thought that having such a monstrosity as that [pejorative snipped] TOC as a PERMANENT part of the skin would be a good idea ? I mean, having it pop up might be a useful thing for newbies (and I find even that a stretch of my imagination), but PERMANENTLY wasting space on a table of contents you consult perhaps once or twice per (long) article ? So KINDLY have it fixed to be hideable/collapsible so that we can get actual article contents on our screens. (One sidenote here: Apart from my blowout here - yes, I am aware that working on these projects is a chore, and despite my invectives here, I AM grateful for your efforts. It's just that this kind of stuff goes so completely against what would be the natural idea here, that I blow my top unnecessarily hard - people generally want to read the TEXT of the articles, so when a new skin development deliberately wastes space on the table of contents - ????? ) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 16:43, 26 April 2022 (UTC) :::Hey @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], we test all of the proposed changes. Editors and readers were strongly in support of this change. More details here: [[Reading/Web/Desktop Improvements/Features/Table of contents]]. Cheers, [[User:AHollender (WMF)|AHollender (WMF)]] ([[User talk:AHollender (WMF)|talk]]) 17:47, 26 April 2022 (UTC) ::::My question stands: Why having it there PERMANENTLY ??? Ok, I find something that's relevant for me to read; usually, I then want to READ just that; not the thread that led me there... So, why PERMANENTLY ??? [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 17:54, 26 April 2022 (UTC) == Public and private views... == While thinking about this, I was struck with what appears to me to be a central point of division here: This is not a question of how THE user interface should look like; but, rather, it is a question of what we should look like to anonymous users, and what choices should be available to those of us who log in ? Does that differentiation make sense ? (I should mention that I'm coming to this from Wikipedia, and that I have very little experience with the other projects.) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 19:14, 26 April 2022 (UTC) :Yeah @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], this makes sense. With the caveat that I don't know what central point of division you are referring to :D :At the moment, except for gadgets and such little tweaks, we aren't able to offer different interfaces for logged-out and logged-in users. Also, we can't make it possible to easily switch between different settings like dark/light mode, contrast versions, font sizes, etc. We need to improve the basics of the viewing/reading experience, we can do ''that'', so we're doing it. :As a result, readers use our interface more comfortably, we check that with regular A/B tests. As for the most dedicated editors, they can/should: :# Help us build an interface useful to them (by giving feedback on the prototypes, on the changing interface on "pilot wikis", by adjusting gadgets, etc.) :# Accept the arguments about the results of user testing, A/B testing, community feedback... :# Accept the "final" version as the basic version, and :# Configure it further if they want. :Our team would like to work the interface deeper. We would like to make it more modular and adjustable. (Of course, content would stay objectively the same for all.) A few months ago, we started working with more closely [[Growth]] and [[Editing]]. Now we're checking how ambitious we can be. :Does that answer your question? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:26, 27 April 2022 (UTC) ::My way of thinking here, is that the main divider here is between what should be visible and available to those who are NOT logged in, and what should be available and possible for those who DO log in. This is because the big difference between the two groups, is that those who are logged in, are also able to seek detailed information and make informed choices (and possibly programmed adaptations), whereas the non-logged in can not be trusted to have any particular information about the system, do not have a way of communicating preferences, and therefore needs to be given visual cues as to what's possible and available, precisely because they are strangers here... (Sidenote: I am of the Wikipedia, and that is the project I write in relation to; each project will have some peculiarities that do not apply to the other (to the same degree, at least); for this reason I should remember to mention this.) :: ::I hope what I'm writing here makes some sense, I try to avoid giving specific "orders" to anyone, but rather contribute to clarifying the context so that I understand it; hopefully, what I then write makes sense to others as well... (About here my subconscious can be heard muttering "and if pigs could fly"...) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 13:17, 9 May 2022 (UTC) == "Beginning" is confusing == More feedback: when I was at [[w:Gotcha journalism]] just now, I became confused because there appeared to be a section titled "beginning", which I assumed covered the early history of the term. It took me a minute to figure out that that wasn't referring to a section but rather a way to scroll to the top of the page. Many other articles are going to have a similar problem, since we often begin with history sections that might reasonably be titled "Beginning" for early history. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 22:42, 27 April 2022 (UTC) :@[[User:Sdkb|Sdkb]] - good catch! This is something we discussed quite a bit internally in order to finally settle on beginning, although I agree that it's still imperfect. Previously we were using "introduction". The issue there was that many articles have "introduction" as the name of their first section, causing duplication. Other options we were considering were location-based (back to top, beginning of page, etc). We are welcome to ideas on how to make this clearer. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 09:05, 28 April 2022 (UTC) ::The name used by wikipedians? ''Lead section'' in English, ''résumé introductif'' in French, etc ([[d:Q10966628|Q10966628]]) [[User:Pyb|Pyb]] ([[User talk:Pyb|talk]]) 11:07, 28 April 2022 (UTC) :::On Translatewiki.net I found "Début" for fr.wiki and "Inizio" for it.wiki (on it.wiki we use also "Incipit" or "Introduzione", see [[phab:T306990]]). [[User:Patafisik|Patafisik]] ([[User talk:Patafisik|talk]]) 15:09, 28 April 2022 (UTC) ::::@[[User:OVasileva (WMF)|OVasileva (WMF)]], did you consider different design approaches in addition to different names? If the word had been accompanied by something like [[File:Font Awesome 5 solid caret-up.svg|16px]], it might have been a lot clearer. I also think there's some benefit to matching the terminology we already use as editors ("lead section" or "introduction"), since that makes it easier for newcomers. The Wikipedia articles that currently have "Introduction" as their first named section should not—they should be tagged with [[w:Template:Overview section]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 20:16, 28 April 2022 (UTC) :::::<small>Bumping @[[User:OVasileva (WMF)|OVasileva (WMF)]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:16, 6 July 2022 (UTC)</small> ::::::Just leaving a note here that we're still watching this conversation and considering different options, but haven't made a decision yet. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:58, 11 July 2022 (UTC) ::I think using the article title would make the most sense, as the title is the uppermost heading in the article. That way the header that the reader arrives at always matches the one they've clicked on. (I'm sure "Beginning" is better than "Introduction," but it's not unheard of as a section title either: e.g. [[w:Creolization|Creolization]], [[w:Ashikaga shogunate|Ashikaga shogunate]], [[w:History of Carthage|History of Carthage]]. Is there any way to determine how often it's used?) [[User:Arms &#38; Hearts|Arms &#38; Hearts]] ([[User talk:Arms &#38; Hearts|talk]]) 19:35, 29 May 2022 (UTC) I think "Top" would be less confusing and generally make more sense as that seems to be the common English term for the top of the page. [[Special:Contributions/132.170.199.112|132.170.199.112]] 19:32, 22 June 2022 (UTC) == Table of contents below sidebar just doesn't work == On a broader note than the two pieces of feedback above, I have to say that my experience so far with the new table of contents has been really frustrating. As an editor, I use lots of the links in the left sidebar quite frequently, so I don't want to collapse it (and even if I did, the way it persists in whatever state you leave it in means that every time I used it it'd return). But preserving the left sidebar forces the table of contents below it, which is just awful. The number one time I want to use the ToC is when I first navigate to an article, and I either want to jump to a specific section or just to see what sections it has to get an overview. Forcing me to scroll to get to that information is extremely annoying, and if it's kept in the final version, I predict the outcry will be intense. You could resolve this either by retaining the old style ToC alongside the new (which would also solve the [[w:MOS:SANDWICH|sandwiching]] concerns I've previously raised) or by moving the ToC above the left sidebar. From your previews, I know you've been working on moving some stuff around and introducing pinning, so I hope this will be resolved in future iterations. But the initial version being introduced here is clearly not ready yet. Best, <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 22:53, 27 April 2022 (UTC) : For me it seems the table of contents and the sidebar seems to be two different things. On Wikipedia, I collapsed the sidebar and the table of contents still remain. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 03:09, 28 April 2022 (UTC) ::I want ToC collapsed too. But there is no way to do it. It uses almost 1/3 of my screen and makes reading very difficult.- [[User:Nizil Shah|Nizil Shah]] ([[User talk:Nizil Shah|talk]]) 05:32, 28 April 2022 (UTC) :::Same here. 14" Screen, collapsed sidebar menu, open only when needed. With the new TOC I cannot collapse the sidebar, it's just a toggle between navbar and TOC. I appreciate the effort and that it's a first attempt, but it definitely should be optional. And yes, I was involved in feedbacks and testing earlier. Regards [[User:Elya|Elya]] ([[User talk:Elya|talk]]) 14:24, 29 April 2022 (UTC) :::: +1, the TOC should be accessible from the top of the page, and collapsible (vertically; also horiz if it is making the sidebar too wide - many pages have section heads that are quite long). [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 17:35, 2 May 2022 (UTC) :::::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] and @[[User:OVasileva (WMF)|OVasileva (WMF)]], neither of you have replied here. This is a major concern, and I predict that if it is not addressed, it may single-handedly prevent the community from being willing to accept New Vector. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:14, 6 July 2022 (UTC) ::::::Hi @[[User:Sdkb|Sdkb]] - thanks for the ping! Currently, we're working on making the ToC collapsible, especially on narrow screens ([[phab:T306660]]). Collapsing it would allow for access further up in the page, but won't completely solve the issue you're describing. To make using both the sidebar and the table of contents a bit easier, we are planning two things. For logged-out users, we plan on collapsing the sidebar by default so that the table of contents will be shown further up in the page. We are also planning on separating the tools related to pages in a separate menu. This will significantly shorten the space for the sidebar, and create a clear definition between which tool acts on the page as a whole, and which one acts only on the page itself. In this example, this puts the ToC above the end of the introduction section, which is higher than the previous ToC location (admittedly, this will not be the case for all articles). ::::::[[File:Prototype_of_table_of_contents_and_tools_menu_for_desktop_Wikipedia.png|thumb|Prototype of table of contents and tools menu for desktop Wikipedia]] ::::::[[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 14:07, 11 July 2022 (UTC) :::::::Thanks for the reply, @[[User:OVasileva (WMF)|OVasileva (WMF)]]! Moving the tools elsewhere (ideally to a Twinkle-like menu) is something I certainly support and have been trying to set up since [[w:WP:SIDEBAR20|the 2020 revamp]], and it would help with this. Your screenshot appears to be from a standard resolution display rather than a widescreen display, so I can't tell whether it's going to help enough to ensure that the ToC will always be visible on a normal monitor with neither it nor the main menu collapsed. Getting to a point where that's the case will be essential for getting community consensus. :::::::Is there a reason you don't seem to be considering placing the ToC above the main menu? <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 23:49, 13 July 2022 (UTC) == About Google Docs and Zoom == {{Ping|SGrabarczuk (WMF)}} Thank you for the invitation I received for tomorrow's videcall since I was an interface admin and a developer! but sadly I cannot participate since I don't use Google Docs or Zoom for security reasons (partially related: [https://www.zdnet.com/article/us-senate-german-government-tell-staff-not-to-use-zoom/] [https://www.gnu.org/proprietary/malware-google.html]). I don't know if it could be useful but maybe in the future you may consider to land the doc on the wiki itself, or using Etherpad [https://etherpad.wikimedia.org/] when realtime is needed. To drop Zoom, maybe I can propose Jitsi Meeting [https://meet.jit.si/] that is gratis and libre and supports streaming on social network to support large audience. (Also [[Wikimedia Meet]] deserves a try and some feedback). [[User:Valerio Bozzolan|Valerio Bozzolan]] ([[User talk:Valerio Bozzolan|talk]]) 15:38, 28 April 2022 (UTC) :Hello @[[User:Valerio Bozzolan|Valerio Bozzolan]]. I understand your concerns and thank you for the language you use. I do appreciate that. As you may have realized, it isn't without a reason why we use these particular tools/platforms. :# Google Docs are used by the Foundation as the default tool for making internal notes and docs. We might, for the purposes of the office hours, replace it with Etherpad. There's a problem with the translations, though. Asking translators to update just one word, and waiting until they've done that, could be troublesome. This is why I can only commit to replace this if we make more changes to the announcement. (By the way, the announcement is [[Template:Reading/Web/Desktop Improvements/Office hours announcement|fully standardized]] and translated into 16 languages, some of which use declination or are not written in the Latin script.) :# We need our office hours to be technically (platform-wise) predictable. Although Jitsi is open source and Zoom is not, the latter is more effective. It has been widely used for online meetings in the movement. It's been used by the WMF for office hours with the CEO, Maryana; it's been used by affiliates. There are hundreds of Wikimedians who at least once have participated in a Wikimedia meeting on Zoom. We know how to provide live translations there. Jitsi, on the other hand, is less popular, and we'd have to learn how to support live translations, including more trainings organized specifically for our meetings. :# We may consider having office hours on IRC. Frankly, I have a feeling that since the migration from Freenode, IRC has been more and more marginalized, but we could give it a try. :I'm curious what other Wikimedians watching this page think. Add your comments! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:15, 5 May 2022 (UTC) ::Just asking for an understanding that Google Form and Zoom are a bug, not a feature, to participate in a Wikimedia project. A bug that deserves a long-term fix. [[User:Valerio Bozzolan|Valerio Bozzolan]] ([[User talk:Valerio Bozzolan|talk]]) 15:57, 7 May 2022 (UTC) ::: I appreciate these are standard across parts of the Foundation. And agree w/ [[user:Valerio Bozzolan|Valerio]] this is a bug, not a feature. Perhaps it's time to revisit this across the org. :) We should be using tools that can be constantly used and deployed by communities for events, workshops, office hours, talks without sending traffic through commercial servers. ::: ''Text'': Google makes some very wiki-spirited tools (they did absorb JotSpot back in 2006) so it's stayed around for a while. But we simply must stop using it as a crutch that keeps us from using and being delighted by notetaking on our own platform. Our collaborative platform for drafting and discussing documents. Our versioned, searchable platform. ::: ''Video'': I too have to use Zoom sometime, but I'm always surprised and a bit dismayed when a Wikimedia meeting uses it! Jitsi is stable, widely used + repackaged, easily modded and forked, and we host a [https://meet.wmcloud.org/ lovely instance] on the WM cloud. [We also regularly use BigBlueButton for larger audiences.] It makes it easy to name a persistent rooms, embed it it in other places or tools (see Jitsi-as-a-service + [[w:Brave Talk|Brave Talk]] these days), &c. We should be thinking about how to better use video streams in our projects, and using this framework as we do so. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 12:54, 14 May 2022 (UTC) ::::Thanks @[[User:Sj|Sj]] and @[[User:Valerio Bozzolan|Valerio Bozzolan]]. ::::# First of all, I really hear what you're saying. Perhaps you're right, Google and Zoom may be bugs - it's definitely not up to me to decide. "Perhaps it's time to revisit this across the org. :)" - I'm grateful that you specifically used the words "across the org". That's way wider than just Olga and me (people who organize ''our'' office hours), or [[m:Community Relations Specialists|Community Relations]] ("technical liaisons" so to speak), or [[m:Movement Communications|Movement Communications]] alone. If it's about ''the standard'', then it needs a broad agreement. ::::# @SJ, do Jitsi or any open-source alternatives provide the speech-to-text functionality and parallel voice tracks for live translators (interpreters)? I'm asking because each time we have a meeting, there are people who need the speech-to-text functionality . Unfortunately, we haven't been able to provide the live translation support yet. We're still working on it, and it seems we may have found a solution. ::::[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:55, 6 July 2022 (UTC) ::::: [[User:SGrabarczuk (WMF)|SGrabarczuk]]: :::::: 1. We ''should'' change the standard [though there seem to be many even within one org!], but I only mentioned that to suggest that none are set in stone. :) As this thread is about these particular discussions, I hope we can try a different standard for these sessions, or understand what prevents such a change. If it is purely a matter of accessibility features, that would make a phabulous ticket even if it is not yet known who could set them up. :::::: 2. Yes they do! Other collaborative orgs w/ similar issues of language equity use jitsi regularly. There are solutions or workarounds for both. [also, to the point of "supporting essential infrastructure for free knowledge", our engagement would certainly help make them better for all.] ::::: '''speech to text''': Google Voice integration seems to be there, and a number of open-source s2t services that are not quite comparable. You can see the range of Summer of Code [https://jitsi.org/gsoc/s2t/ projects] + community submissions scratching their own itches in the [https://github.com/jitsi/jigasi/issues/157 jigasi repo]. ::::: '''remote simultaneous interpretation''': the most recent solution (for a single language, letting you tune in or out of the raw audio and into a translator's audio channel) is use by [https://i.meet.mayfirst.org May First] (which we should [https://mayfirst.coop/en/ work more closely with] on choosing technology stacks, frankly) and is maintained [https://gitlab.com/mfmt/jsi here]. There are improvements, and pushes to integrate into jitsi core, both of which could be facilitated by small technical bounties or large expressions of interest [like Wikimedia indicating this is a crucial feature for us]. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 02:37, 7 July 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], I will not participate in any forum that is not public. Why the wmf foundation wants to share information via Zoom, a for-profit corporation which provides no guarantee of privacy, is anyone's guess. We have been using wiki-code for discussion since 2001, why this change? ::I apologize if you find my message above irrespecutful, but this represents the views of many. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|talk]]) 18:26, 13 June 2022 (UTC) :::@[[User:Ottawahitech|Ottawahitech]], above, you can find explanations on why we (the Web team) are using Zoom now. Are you also asking why we have any voice online meetings in general? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:57, 6 July 2022 (UTC) == Instant jumping vs. animated scrolling for table of contents == As you're polishing up the table of contents, one thing it'd be nice to consider is the behavior when you click on a section in it. Currently, it instantly jumps to that section, but I think it'd be better if it instead did a very quick scroll (maybe a quarter of a second). This would help readers to more easily understand what's happening when they click the link, and to get a better intuitive sense of what the article contains by seeing it flash by. Would that be possible? <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 02:37, 30 April 2022 (UTC) :<small>Bumping @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] and @[[User:OVasileva (WMF)|OVasileva (WMF)]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:12, 6 July 2022 (UTC)</small> == Wide-column + Multi-column options for large screens == Readers vary in what form factor they prefer, especially for long-form high-volume reading. That's part of why this change and research into 'optimal layout' is controversial. I'm someone who finds it hard and slow to read a narrow column and have to scroll all the time, including when searching a page for a term. General feedback on width: # Include a comfortable default for large screens. The (potentially large) gray margins on left and right, outside large white margins, bracketing a forced-maxwidth central column, do not feel good. Wide-col or multi-col could work. # Offer an explicit wide-column pref that doesn't require people to change skins, even if that is less aggressively supported/tested across all platforms. # A multi-column design for text within sections – mimicking the style of most long-form magazines and scholarly journals – would be interesting and can be surpassingly beautiful. That's what I'd like to see our wide-screen layouts transition to. We already do this within sections for references, lists, and galleries. Even low-end desktop monitors these days are high enough resolution to support two-column layouts. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 18:20, 2 May 2022 (UTC) == I think sticky elements ruin Vector == I liked vector a lot more when it didn't have the new distracting elements (sticky header and sticky TOC). ''I care about the contents of the page, not the interface'', nor about the need to scroll to the top of the page every now and then. [[User:Tokujin|Tokujin]] ([[User talk:Tokujin|talk]]) 17:50, 4 May 2022 (UTC) :Hello @[[User:Tokujin|Tokujin]]. Congratulations for finding this page :D You can add <code>.vector-sticky-header {display:none;}</code> to your [[metawiki:Special:MyPage/global.css|global.css]]. For now, I'm not entirely sure what to advise about the TOC, though. When the collapsible version has been deployed, we'll know what code you should use to make it not sticky and keep some other version. I invite you to revisit this topic in 2-3 weeks. :By the way, I very much liked the first sentence of [https://www.mediawiki.org/w/index.php?diff=prev&oldid=5009784 your comment to the third prototype]. Have you seen the [[Reading/Web/Desktop Improvements/Fourth prototype testing|fourth one]]? I encourage you to follow the instructions and share your opinion about it, too. (BTW, compare it with [https://di-collapsible-menus.web.app/Brown_bear the newest version, also a prototype].) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:28, 5 May 2022 (UTC) ::Hi Szymon :-) [[Reading/Web/Desktop_Improvements/Fourth_prototype_testing/Feedback#Username%3ATokujin|Done]], thank you. Regarding the global.css setting, notice that with sticky table headers enabled (in Preferences > Gadgets > Testing and development) there's a bug whereby in tables such as those in [https://en.wikipedia.org/wiki/List_of_Disenchantment_episodes#Part_4_(2022) this page] the table header leaves space for the absent page header. Other tables, such as that [https://en.wikipedia.org/wiki/Ninety-nine%20Novels here], don't have this issue. [[User:Tokujin|Tokujin]] ([[User talk:Tokujin|talk]]). 07:41, 9 May 2022 (UTC) == Skin differences between wikis == I'm using the 2022 Vector skin globally now (with [[:m:User:Tol/global.css|some modifications]] to remove whitespace), but I'm noticing that some wikis' sidebars are different from others. For example, MediaWiki wiki (this wiki) and French Wikipedia have a thinner white-background sidebar which sits on top of the page body (and ToC in the page body), while Meta-Wiki, Wikidata, and English Wikipedia have a wider grey-background box which is not layered on top of the page body (and ToC beneath said box). I can't figure out why this is. [[User:Tol|<span style="color:#f542d7">Tol</span>]] ([[User talk:Tol|talk]] &#124; [[Special:Contribs/Tol|contribs]]) @ 00:12, 8 May 2022 (UTC) :@[[User:Tol|Tol]] - thanks for your question, and good catch! This is due to the table of contents still needing to being A/B tested on some wikis (frwiki and mediawiki wiki being two of these). The ToC functionality is not yet available there. That said, we've began some work on reducing the margins for the ToC as a whole ([[phab:T307004]]) that will make the differences in width fairly negligible. This change will be on all wikis next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:31, 9 May 2022 (UTC) ::@[[User:OVasileva (WMF)|OVasileva (WMF)]]: Ah; looks great! I look forward to that change rolling out. Thanks! [[User:Tol|<span style="color:#f542d7">Tol</span>]] ([[User talk:Tol|talk]] &#124; [[Special:Contribs/Tol|contribs]]) @ 14:14, 9 May 2022 (UTC) == Tool bars and tables == Hi, thanks for the update. A few observations: # I would suggest that users have the option to keep the tool bar on the sidebar from the beginning, instead of having to click "tools" -> "[move to sidebar]" every single time. # The readability of tables and graphs that are wider than the (quite tight) text column is an issue. In certain cases, the tables represent time series data (e.g. population in a country or municipality over time) that cannot just be tightened. Do you have a proposal to solve this issue? The NYT, which is a site that you explicitly mention as inspiration, lets tables and images occupy the whole width of the screen if necessary. [[User:GeneraleAutunno|GeneraleAutunno]] ([[User talk:GeneraleAutunno|talk]]) 20:39, 8 May 2022 (UTC) == Next steps for the Table of Contents == Hey all - thank you for all the feedback around the issues you were experiencing with the ToC, especially on narrow screens. We've taken a few steps to fix some of these issues: * We're reducing the margins of the ToC to more closely resemble those of the prototype (tracked in [[phab:T307004]]) * We have a temporary solution for the ToC at narrow widths, which removes the ToC alltogether * We are building functionality to allow for the ToC to be collapsible and expandable at narrow widths (tracked in [[phab:T306660]]) * We are planning on making the ToC collapsible at all screen sizes and widths (tracked in [[phab:T307901]]) * https://di-collapsible-menus.web.app/Brown_bear links to a prototype that puts all of these changes together. We would appreciate your feedback and thoughts on the decisions made within the prototype and whether they work for you. Thanks! [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:38, 9 May 2022 (UTC) :cc @[[User:Lectrician1|Lectrician1]], @[[User:Alexis Jazz|Alexis Jazz]], @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], @[[User:Tenryuu|Tenryuu]], @[[User:Tucvbif|Tucvbif]], @[[User:Tokujin|Tokujin]] - in case you're interested. Apologies if I'm forgetting anyone else that was asking about this! [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:46, 9 May 2022 (UTC) ::[[User:OVasileva (WMF)|OVasileva]], thank you, it's a solid improvement! Just one request: can the hiding/unhiding be made persistent so my choice remains in effect even if I navigate to another page? <span id="Alexis_Jazz:1652099702223:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 12:35, 9 May 2022 (UTC)</span> ::Thank you, that's good news! (Adding a clarification: I'm responding to OVasileva, here.) My thinking is that making it collapsible is the only reasonable way to go; with the added point that for newcomers and anonymous readers it should perhaps be turned "on" as default; if the collapse button is clearly visible, the TOC will be useful to some, and easily removable for the rest, which should be the useful level of the intrusive/invisible conundrum... Thank you, once again. [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 13:02, 9 May 2022 (UTC) :: @[[User:OVasileva (WMF)|OVasileva (WMF)]]: Thanks for letting me know. Since this seems to be only in effect for the new Vector skin, maybe some work could be done to have the table of contents be shown in focus and have a button on the sticky header, as well as a keyboard shortcut for it? [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 14:07, 9 May 2022 (UTC) :Thanks for the work, I like the prototype a lot. I've missed the easily available overview that the ToC provides. Compare to the 2010 design, it is very useful to have the ToC available no matter how far down you scroll. :On small screens, the "move to sidebar" link text is not accurate with regards to what happens visually when you click on it. [[User:PeterTrompeter|PeterTrompeter]] ([[User talk:PeterTrompeter|talk]]) 16:51, 11 May 2022 (UTC) :On narrow screens this is still quite jarring, and having no TOC is a loss, being able to move the TOC back in to the body (dynamically and programmatically) seems a better compromise. A problem I see is that even when there is no TOC on a page, all that space it could use is still being consume by blank space, that wasted horizontal space needs to be able to be reclaimed somehow. We've been testing some options that are aimed at more power desktop '''editors''' so they can use vector-2022, but still have access to most of their screen (see [https://en.wikipedia.org/wiki/Hate_%C3%9Cber_Alles?useskin=vector-2022&withgadget=wide-vector-2022 example] (will really only be strikingly noticable if you are on a wide screen)) but still are getting complaints about the huge space used by the TOC. [[User:Xaosflux|Xaosflux]] ([[User talk:Xaosflux|talk]]) 11:40, 14 May 2022 (UTC) == Banners and roadmap == Hi, I think you should consider to add banners in order to present the restyling to a much wider part of users. IMO they should link to discussion and presentation pages. You should also consider to present to the wikis a clear roadmap with dates in order to present ahead of time big changes like the adoption of the new Vector. This two changes would make you work clearer to the eyes of the users and would prevent some dissatisfactions.<small> In particular I'd like to point out that [[:it:Wikipedia:Bar/Discussioni/La_nuova_interfaccia_desktop|what is happening on itwiki]] is being perceived as an imposition against the general consensus and I agree with the Italian users that are saying that forcing the adoption of the new skin is not the right way to act. These two are some ideas to widen the discussion, forcing something against the will of most will just radicalize the opposing positions even more.</small> -- [[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 11:44, 9 May 2022 (UTC) :<small>I just received the good piece of news that the adoption of the new skin has been delayed for itwiki and I thank you for this. But I still think that the two ideas that I presented above would be good tools to prevent something similar to happen again. ----[[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 11:58, 9 May 2022 (UTC)</small> :Thanks @[[User:WikiLuke|WikiLuke]]. These are great suggestions. :* Banners - [[phab:T304839|T304839]] - we've been working this for some time. Soon, the banner should be visible to some logged-in Vector users. They will be encouraged to switch to the new skin, and some time later, they'll see another banner with a link to this talk page. :* Links to the project page - [[phab:T307113|T307113]] - our idea was similar. We'll add a link to the list of skins in preferences. :* Roadmap - that's also a very good point. We'll consider how to present this to the community most effectively. :* Itwiki - we'll continue this topic on itwiki, alright? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:33, 9 May 2022 (UTC) ::Thank you for you consideration! :) <small>And speaking of itwiki of course we will continue the topic right there.</small> -- [[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 16:14, 9 May 2022 (UTC) == Sticky header 'dead zone' in articles with long lead sections == {{tracked|T307345}} Steps to reproduce: # Visit an article with at least a moderately long lead section (e.g., [[en:Charles de Gaulle]]). # Scroll down a little way. # Observe that the sticky header appears. # Scroll down a little further, so that the first heading appears, but not much further than that. # Observe that the sticky header vanishes. # Scroll down even further. # Observe that the sticky header re-appears. This does not seem like intended behaviour. I am testing on Firefox 100. [[User:FrankSpheres|FrankSpheres]] ([[User talk:FrankSpheres|talk]]) 04:14, 10 May 2022 (UTC) :Hi @[[User:FrankSpheres|FrankSpheres]] - thank you for your report! We already have a fix for this bug, tracked in [[phab:T307345|T307345]]. It will be available early next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 08:11, 10 May 2022 (UTC) == Feedback on new look == I like that stuff that is generally rarely used is hidden, such as the language picker. I am not a fan of moving the table of contents off the main article body section. I didn't even register that the table of contents was there and I frequently use the TOC to get an overview of interesting sections of articles. With the TOC being isolated at the side bar, it seems separated from the article itself, while it should be a central part. Maybe it would work better if it appeared on the right of the article, where there is currently just whitespace? Speaking of whitespace: I dislike the move to a max-width on article pages. This feature should at the very least be toggle-able with a button (without a need to log in). I feel like it makes the article feel more cramped, with less space for images and figures. There is already a very good solution to setting the effective width in the old view: Simply resize your window or zoom in on your browser. With the new look, I am forced to a max-width and I don't have a solution to control the width like I did before. Whitespace and the TOC did something beautiful together in the old look actually. The TOC conveniently visually separated the article lead section from the rest of the article by introducing white space, which I personally found very pleasing. The new look has the lead section blend in with the rest of the article. This makes the lead appear more daunting, while its purpose is to serve as a quicker summary. Perhaps the lead section should be followed by a larger piece of whitespace than is normally found above headings, so as to separate the lead from the rest as before? Finally I am quite sad to see that the Wikipedia globe logo is diminished - I really like the globe with the symbols and it doesn't look very good at low resolutions. I think the size of the globe was perfectly fine before. Besides, it seems there's plenty of space for it to have the same size as before so I'm kind of puzzled why this change was made in the first place. I will also say that the arrow next to the Wikipedia globe (the one to minimize the side bar) leads to an unfortunate usability flaw. I initially thought the arrow was supposed to take me back to the front page (it is right next to the logo and the leftward direction suggests a "back" action). But that is not what it does at all. So the arrow is kind of confusing at first. --[[User:SorteKanin|SorteKanin]] ([[User talk:SorteKanin|talk]]) 16:40, 13 May 2022 (UTC) == When testing the new skin, offer a one-click way to change back == The banners inviting users to test the new skin offer a one-click option that updates your skin to new Vector. The banner is then replaced with a message saying "give us feedback!", but it should also offer a one-click way to revert the change. Users may not be familiar with how to undo the change. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 12:56, 14 May 2022 (UTC) :The one-click option to revert is the final item of the sidebar's top section, in bold. Are you suggesting a second method should be included, or that the link should be made more obvious and flashy by moving to the banner? :The sidebar link seems fine to me. Particularly because this is less about the theme and more ergonomics for migration. [[User:Kees Person|Kees Person]] ([[User talk:Kees Person|talk]]) 15:34, 14 May 2022 (UTC) :: I found it eventually, thanks. Yes, putting it in the banner, or putting a js link in the banner that highlighted the sidebar link, would be clearer :) [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 19:59, 20 May 2022 (UTC) == Too little space == It's probably fine for those who don't use wide-screen monitors, but as someone who does it is quite annoying having everything mushed together like on mobile. I have read the page on this, but I think there should be a way to keep the functionality of the skin but lengthen the screen. [[User:Lallint|Lallint]] ([[User talk:Lallint|talk]]) 13:57, 14 May 2022 (UTC) : I concur. I tried the new skin a couple of times and just could not do it. I have bought a standalone monitor for a reason - and it's not that large anyway (1920 x 1200) - yet the new skin wastes a third of my screen space. [[User:Kashmiri|Kashmiri]] ([[User talk:Kashmiri|talk]]) 12:31, 20 May 2022 (UTC) ::Actually I use a 13" laptop and I initially thought that my computer switched to mobile version by mistake, but I later realized that was the desktop layout. I think the way everything is squeezed-in together takes away from the experience; there is nothing wrong with the header and tools bar they look fine to me, yet the sizing seems off for desktop users. [[User:Humanized|Humanized]] ([[User talk:Humanized|talk]]) 10:20, 24 May 2022 (UTC) == Sidebar too long == Sidebar too long and page too small on Wikimedia wikis [[User:LisafBia6531|LisafBia6531]] ([[User talk:LisafBia6531|talk]]) 16:24, 14 May 2022 (UTC) == Do not use a sticky header. == I think the new layout makes much better use of whitespace on 16:9 displays, making paragraphs easier to read. However, vertical space is someone no website that serves text-rich pages to users can ever get enough of. I believe that every (non-redundant, e.g. the article name is displayed twice on most browsers in the window tab title and the sticky header) element currently placed on the sticky header would not just fit on the sticky sidebar, but by removing the sticky header the layout will better serve what readers come to a wiki to do. As a side note though, I am awfully sentimental about the old Wikipedia header logo and type layout, that giant globe and the accompanying text beneath it is far too iconic to change in my opinion, even for a redesign. [[User:Saedes|Saedes]] ([[User talk:Saedes|talk]]) 14:18, 15 May 2022 (UTC) == Sidebar considerations for vertical monitors/half-width windows == I haven't tested this out thoroughly yet, but I'm going to be adding this section to start a discussion on how the new layout uses responsive design when display device/window aspect ratios are greater in height than width. [[User:Saedes|Saedes]] ([[User talk:Saedes|talk]]) 14:28, 15 May 2022 (UTC) == The table of contents is in the wrong place == It's nice to have a table of contents right there on the side so you can move back and forth between sections but i don't like the fact that you have to scroll down a bit to find it. If there's a way to keep it at the top of the page so you see it right as the page loads then as the user scrolls down it changes into a sticky header, that would be better. [[User:Abhaypradjha|Abhaypradjha]] ([[User talk:Abhaypradjha|talk]]) 10:04, 16 May 2022 (UTC) == Search bar UX is inefficient (Fitts's law) == I want to search. # If I am at the top of the article, I click mindlessly anywhere on the header and type straight away. # If I am down the article, I have to pinpoint an icon. This is bad because * The inconsistency turns my muscle memory against me * It goes against [[w:en:Fitts's_law#Implications_for_UI_design|Fitts's law]]: pinpointing an icon requires precision and is slower than clicking a large bar at the border of the screen without giving much thought into it. A solution would be that clicking on the article title or empty space in the sticky header hides the article title and displays the search bar (empty and focused). My case is that I often read the documents with the help of Wiktionary, so I use the search bar heavily and my usage pattern is fundamentally different than on Wikipedia. On Wiktionary, the interesting information is on one line or two, for each one of many unrelated entries, so searching is almost exclusively my means of navigation. [[User:Wanlpz|Wanlpz]] ([[User talk:Wanlpz|talk]]) 19:05, 17 May 2022 (UTC) == TOC: the position of the content == Hi, I like your [https://di-collapsible-menus.web.app/Brown_bear last prototype of TOC], in particular the blu color which helps to find a menu when you collapse it. I notice something I consider a bug: when the TOC is collapsed, if the tools menu is collapsed too the content is in the correct position, but if you move to the sidebar the tools, the content changes his position (it shifts on the left side). It feels strange. It doesn't happens when the TOC is on the sidebar, and you open/collapse the Tools menu.--[[Special:Contributions/151.42.0.114|151.42.0.114]] 13:17, 18 May 2022 (UTC) ==Sidebar== The sidebar has extended a bit (and by that, I mean a LOT) too far, which makes things very uncomfortable for me. I'm fine with the skin other than that, but the overintrusive sidebar is just awful. Plus, there are these white extensions to it that shouldn't be there. I hope you understand what I'm talking about, and at least take notes on it! [[User:ARandomPage|ARandomPage]] ([[User talk:ARandomPage|talk]]) 11:33, 19 May 2022 (UTC) == Зробіть для кожного коментатора окремий відділ == '''Привіт я досі не можу зрозуміти чому кожен коментатор не може писати окремо це набагато зручніше...''' '''Новий дизайн набагато простіший в візуальному плані але до нього треба звикати)))''' '''Також я побачив що новий дизайн не працює в деяких мовах''' [[User:Ilolg|Ilolg]] ([[User talk:Ilolg|talk]]) 14:34, 19 May 2022 (UTC) == Some incoherence == Hey there! To begin with, I want to make it clear I've got nothing against updating the desktop experience at all. I wanted to make it clear in case I seem like a person ranting something like, "Give me back my good old skin!121". What I think is that by making the skin you folks tried to reconcile the legacy appearance with some modernity. A good point, though the effect is not as optimistic. The top buttons (edit & history & etc) that retain the legacy shadowing do not fit in with the new cohesive background as seen in the left-hand sidebar. I'd consider re-adapting the former so that they better suit the new design. [[User:Mustafar29|Mustafar29]] ([[User talk:Mustafar29|talk]]) 10:05, 20 May 2022 (UTC) == A few more issues with the Page header vs Sticky header icons == Premise: I agree with the comments above that an update can only be a good thing; I'm sending kudos to all the teams working behind the scenes; and I only started using Vector 2022 a few weeks ago - noticing that it gets better each day. I'm not sure if the issues I'm having are slated to be improved or are haven't yet been considered. 1. Lack of coherence in the sticky header iconography I frequently work on the special pages where the sticky header is absent which makes it frustrating when I move to another page (article page) and it appears and then back to 'edit' or 'view the history' of a page and it disappears again. I feel that I should be able to move from page type to page type without noticing drastic changes in the header. 2. Order of icons and functionality is different between the sticky header and page header - specifically some items disappear completely, some move from one area to the next and others are simply re-ordered. (Until just now I thought the search bar had been remove but I just found it as an icon that was pushed to the extreme left hand side after the article title. Now I understand the others who said that with a 27" monitor the left side icons are essentially out of sight.) [[file:Headers-sticky-vs-page.jpg|600px]] * Examining the two headers more in detail we see that the icons seem to be in the same place which makes it hard to notice they are different. Starting from the right, we see that the icons are identical in both therefore, we naturally expect the two (people) dropdown menus to contian the same items. * Moving towards the left we see two icons with a star which pertain to the same semiotic sphere yet actually have different functionalities. One icon (that looks like a drop down menu but isn't) takes you to your watchlist while the other simply indicates whether the current page is on your watchlist and fuctions as a toggle to add the page if it isn't. There is a futher issue with how similar this icon is to the 'Contributions' icon, making it hard to distinguish for those of us who have bad eyesight - but that is an issue for another post. * Continuing to the left, the issue becomes more confusing. 'Your notices' from the page header disappears (or maybe I just haven't found it yet) and the text menu 'View history' moves into the sticky header as an icon -the tool tips are the same in both and they are basically in the same position onthe page, which helps a bit. * And with the final icons (still moving left) the 'Your alerts' bell disappears (or hasn't been found) and the 'Discussions about this page' transform from a text menu on the left into an icon on the right, at least the tooltip is the same. I have to admit that it's not clear to me why my user name is only visible on the page header and then moves under the person icon in the sticky header. It's not exactly a problem in itself, but it does add to the confusion of icons and functionality that seems to jump around from page to page. * Finally, it seems that the “Edit” and “Edit source” functions have disappeared along with the special menu items of “delete”, “purge” and “move” unless you scroll back up to the top of the page. I believe these issues have already been mentioned by others above. Again a big thanks to all of you working hard to update the interface and the 'restyling'. I hope when this is all finished, the sticky header will be unobtrusive and not noticeable like the ones normally found on modern webpages. --[[User:Lepido|Lepido]] ([[User talk:Lepido|talk]]) 21:07, 20 May 2022 (UTC) == Left menu too wide == The main menu on the left is too wide and makes the rest of the page appear too cramped in relation to the menu. [[User:Urban Versis 32|Urban Versis 32]] ([[User talk:Urban Versis 32|talk]]) 00:02, 24 May 2022 (UTC) == The TOC, again == It just makes all look too narrow and tight, at least to me. I've been working on various lists projects recently and now they all look god awful because they had the old look in mind. [[User:Tintero21|Tintero21]] ([[User talk:Tintero21|talk]]) 02:08, 24 May 2022 (UTC) ==I prefer the old version == It's cool but I prefer the old version. [[User:Super ninja2|Super ninja2]] ([[User talk:Super ninja2|talk]]) 07:18, 24 May 2022 (UTC) == suggestion: collapsible table of contents == the appearance of the site is far too narrow. i would suggest making the table of contents collpasible to the left. [[User:Lettherebedarklight|Lettherebedarklight]] ([[User talk:Lettherebedarklight|talk]]) 12:02, 24 May 2022 (UTC) : Me too. Also could be hidden, in options, so the user can read better the text. Now, it is too narrow and tight. --[[User:BoldLuis|BoldLuis]] ([[User talk:BoldLuis|talk]]) 13:04, 24 May 2022 (UTC) == Line under title colliding with coordinates == {{Tracked|T310369}} [[File:TitleLineColliding.png|thumb|alt=Gray horizontal line under the title colliding with coordinates given on top right of page]] See image. The horizontal line under the title collides with any coordinates that are displayed on the top right. --[[User:MimiKal797|MimiKal797]] ([[User talk:MimiKal797|talk]]) 14:56, 24 May 2022 (UTC) :Even I wanted to state this same issue. [[User:Excellenc1|Excellenc1]] ([[User talk:Excellenc1|talk]]) 16:00, 24 May 2022 (UTC) : Also the floating title can obscure content. For example, open the front page of [[b:Oberon|Oberon]] and scroll to the bottom. Click on instance "a" of footnote 43. That should take you to "MT, in V5, the constant address ...". In fact, the next glossary entry "native, modifies the name ..." is displayed. Not a terrible defect but baffling for a novice trying to learn. Thx, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|talk]]) 00:08, 25 May 2022 (UTC) ::I came here for a MeToo (about the coords/line collision). Classic Vector does not have the problem. Also, I think the languages dropdown is uncomfortably close to the coordinates; if you hover over that button you can see they overlap, which generates cruft when the dropdown is activated. Did anyone write up a ticket? [[User:DavidBrooks|DavidBrooks]] ([[User talk:DavidBrooks|talk]]) 15:35, 9 June 2022 (UTC) - OK, I did: T310369 [[User:DavidBrooks|DavidBrooks]] ([[User talk:DavidBrooks|talk]]) 15:19, 10 June 2022 (UTC) :::This is being discussed in [[:en:Template talk:Coord#Coordinates bad positioning]]. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:32, 10 June 2022 (UTC) == Great GUI == Everything looks very appealing to me. I think the blank left space really aids in reading as the width of the line reduces its easier for me to not to confuse the line which I have to read next. Overall I loved it. One suggestion that I want to give is that it would be very nice if you could change the visual of the tab. It looks a little too classic to me and would be very nice of you if you could add dark mode ( I don't know if it already exists), this I think would give a very appealing look to the website . Thank You. [[Special:Contributions/]] 17:59, 24 May 2022 (UTC) : If you ever want to reduce the width of the lines you are reading, I suggest you just resize your window, as the elegance of desktop browsing is that it gives you control over the size of the page. As for me, this layout takes away that control. Using it, I can no longer read an article with the full width of my screen without fiddling with my common.css, a luxury that would not be available to me when I'm not logged in, and am instead forced to use ~2/3 of that width, even when the window is reaching into every corner of my screen. There are several ways of using dark mode on wikipedia listed [[wikipedia:Wikipedia:Dark_mode|here]], but I agree it should be made easier. --[[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 16:42, 25 May 2022 (UTC) == Feedback == I was prompted to give some feedback on the 2022 Vector skin, and I have to say that it needs a bit more work. * The mix of new and old UI elements doesn't look good; specifically the View, Edit, Edit Source etc. menu bar looks out of place among the flatter new UI * There's uneven and unnecessary padding around the left pane with the many links that can be filled with the pane * There should be an option to have the content filling any display larger than 4:3, as most displays are 16:9. I understand the argument that it helps some people in reading but having an option is better, as it doesn't help ''all'' people. Additionally, a poll should be run in all Wikimedia projects on which one should be the default (4:3 or full width) — [[User:Dimsar01|Dimsar01]] ([[User talk:Dimsar01|talk]]) 23:33, 24 May 2022 (UTC) Here is My feedback *I see that the sections are not properly sectioned on the screen *I am using dark mode and when I want to add reference or qualifier or something like that, I see a white suggestion screen All in all I can say for now is that I really needs more work done and I can prefer the older one for now thank you [[User:Micheal Kaluba|Micheal Kaluba]] ([[User talk:Micheal Kaluba|talk]]) 05:58, 26 May 2022 (UTC) == Short description == It would be great to have the short description visible on pages, like it is on the search and on mobile, so users can more easily edit them and identify information. Like said by other users, the mix of new and old UI looks bad. The [https://di-article-tools-2.web.app/Blue_whale most recent prototype], for all its faults, had a well unified UI. I also think that the page tools (and "In other projects") should be separated from links for the whole website like was done in the [https://di-article-tools-2.web.app/Blue_whale most recent prototype], though there were many flaws with that execution (see [[Reading/Web/Desktop Improvements/Fourth prototype testing/Feedback#User: BappleBusiness|my comments]]), and all those links should be condensed by default. "Beginning" should definitely be named "Lead" or "Lead section", like said by others. I really appreciate the effort that is going into this. I think the vast majority of these changes are for the better, it just needs more work. [[User:BappleBusiness|BappleBusiness]] ([[User talk:BappleBusiness|talk]]) 00:32, 25 May 2022 (UTC) == Software Gore == [[File:Languages on Wiktionary with new layout.png|thumb|Software gore]] This is pure software gore. If you want to explain to me why it's like this, you're wasting your breath. I've edited Wiktionary for over a decade and I understand how it's come to look like this, and I don't even have a solution to propose. But I feel terrible for anyone trying to navigate this mess for the first time. —[[User:Pengo|Pengo]] ([[User talk:Pengo|talk]]) 00:54, 25 May 2022 (UTC) == Watchlist tooltip == Hi folks! I'm vaguely used to the watchlist icon (since I've switched themes many times over the past decade or so, and use the mobile app/website), but I still need to resort to the tooltips when I'm on my desktop. It would seem I'm not the only one that takes a moment to mentally translate the icon to the concept in my brain (per {{ping|Nardog}}'s earlier [[#Watchlist icon]] comment). I may stay with "Vector 2022" over on [[commons:Main_page|commons.wikimedia.org]] after trying it out for a bit, but please: could y'all change the tooltip so that the word "watchlist" is in the tooltip? Currently, the icon sports the the very verbose tooltip: "''A list of pages you are monitoring for changes [Alt+Shift+I]''", which takes a moment for me to mentally translate into "''oh, they're trying to say 'Watchlist'!''". It would be helpful if (in addition to the keyboard shortcut), the tooltip also gave the mental shortcut, perhaps with the phrase: "''Watchlist: your list of pages to monitor for changes [Alt+Shift+I]''". Since I'm guessing y'all aren't changing "watchlist" to another word, I can imagine it would be helpful for new users too. -- [[User:RobLa|RobLa]] ([[User talk:RobLa|talk]]) 04:12, 25 May 2022 (UTC) :Yeah, given all the other tooltips are just "Your alerts", "Your notices", and "User menu", it seems to me it should be simply "Watchlist" or at best "Your watchlist". [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 04:22, 25 May 2022 (UTC) == I want the code to make the sidebar TOC disappear == Please. Ping me. [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 05:46, 25 May 2022 (UTC) It's probably not too hard since there seems to still be a {{tag|mw:tocplace}} element left -- you need to grab the element, move it back and do some style fixups. Kinda like [[w:zh:User:Artoria2e5/Gadget-sidetoc.js]] but backwards. --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:43, 26 May 2022 (UTC) Ah well, I am pretty convinced that having {{tag|mw:tocplace}} but not the actual TOC hidden there is a bug now. If that gets fixed, it should be just some CSS work in your vector-2022.css: <pre> #mw-panel-toc {display:none;} #toc {display:block;} </pre> May need to sprinkle on a bit of !important. ping [[User:Bageense|Bageense]] --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:55, 26 May 2022 (UTC) :Yep, TOC disappeared, leaving a blank space. [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 16:55, 26 May 2022 (UTC) ::Well, just gotta wait until they come to their senses. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 00:55, 27 May 2022 (UTC) == Space for article too narrow == The article took up less than the full width of the screen in the old skin, but the increased padding and needlessly wide sidebar here make the usable region even smaller. This just reproduces the issues that have had to be worked-around on mobile, including some tables being too wide to fit in the space and causing horizontal scrolling, creating the need to scroll further to get between sections, as well as causing some large image thumbs to squish the article text into narrow strips. In my opinion, the sidebar, which I think most readers rarely make use of anyway, should be consigned to a modal rather than taking up even more space, so that the article can appear centred all the way down the page. This would make room for fairly wide margins on either side without causing as many issues. (I suggest this because it seems the most noticeable "improvement" here is the addition of extra whitespace, but really, what is wrong with making full use of the window width you are given?) [[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 15:50, 25 May 2022 (UTC) : I came here to complain about the same thing - limiting the width of the pageview doesn't make sense when you have a lot of text to display. Especially the discussions became harder to read. [[Special:Contributions/78.11.223.83|78.11.223.83]] 06:29, 26 May 2022 (UTC) == TOC should make the page slowly scroll to the right section, and not just jump == By the way, I'm still waiting for the code necessary to deactivate the lateral TOC. I've already disabled the sticky header by using .vector-sticky-header {display:none;} [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 07:51, 26 May 2022 (UTC) :That would make it take longer to get where you want to be, and prevent the user from scrolling during the time the page is sliding. The current TOC works using anchors linked to IDs, which means you can get back to where you were by simply paging back, but this, I think, would not be possible if the links were actually buttons triggering JavaScript animations. [[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 08:14, 26 May 2022 (UTC) == TOC not appearing at all == It seems that Vector 2022 is not showing ''any'' TOC -- neither the regular one nor the side one -- when it probably should. I noticed this issue about a couple of days ago but assumed it was an error on my side. Today I checked out [[w:Dmitri_Shostakovich]], tried to add a <code>_<nowiki>_TOC__</nowiki></code> magic word, found out it does nothing, and then realized it's the skin that's broken when I retried in a logged out private tab. In a private tab: * https://en.wikipedia.org/wiki/Dmitri_Shostakovich?useskin=vector-2022 has no TOC right now, but * https://en.wikipedia.org/wiki/Dmitri_Shostakovich?useskin=vector has a TOC. What's going on here? [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:35, 26 May 2022 (UTC) :One refresh later it's showing the side one. I must be descending into some sort of madness. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:37, 26 May 2022 (UTC) ::Annd it's gone again. No outstanding errors in the console. Seems to be sone <code>@media screen { ... .sidebar-toc {display:none; ...</code> in one of the many load.php's ([https://en.wikipedia.org/w/load.php?lang=en&modules=ext.cite.styles%7Cext.echo.styles.badge%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cjquery.makeCollapsible.styles%7Cmediawiki.ui.button%2Cicon%7Coojs-ui.styles.icons-alerts%7Cskins.vector.icons%2Cstyles%7Cwikibase.client.init&only=styles&skin=vector-2022]). What. the. heck. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:48, 26 May 2022 (UTC) ::The intention of the code seems to be to show the sidebar only for screens wider than a value. That's a good idea, but only if the original TOC is not removed! --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:50, 26 May 2022 (UTC) == Bold, yet very appreciated changes == At first I didn't like it. My first thought was that it took more space, so I got less content in my screen. I compared it side by side with the old skin and in fact, elements got more margin. But after giving it a try, reading and moving through the article, I fell in love. I really like that the TOC is now on the left and moves along with the page. It was OK before but now it feels fancy. And I feel more people are going to benefit from it now. The cleaner, more "plain white" look is nice. I understand the decision of limiting the width of the page on (very) wide screens. In my opinion, it is a sensible design decision that improves readability. Because if lines get too wide, it can make it harder to read. Maybe this "max-width" setting can become a thing users can tweak? I tested this new skin on a modern computer and a 1440p screen. If I were to use my old laptop, I'm sure I'd like to have the option to change to the old skin. As it fits more content and uses less CPU resources. I appreciate this changes, and feel they are for the better. Thank you! -- [[User:Zazke grt|Zazke grt]] ([[User talk:Zazke grt|talk]]) 06:42, 27 May 2022 (UTC) : I've temporarily switched back to the old Vector skin in Wikipedia because some pages like this one [https://en.wikipedia.org/wiki/Portal:Video%20games Wikipedia:Portal:Video_games] have their contents very croped or overflowing their boxes. --[[User:Zazke grt|Zazke grt]] ([[User talk:Zazke grt|talk]]) 06:49, 28 May 2022 (UTC) == TOC not immediately visible == {{Tracked|T309632}} I am going to refrain from complaining too much as I'm prone to do with any and all UI changes :) However, I do find the placement of the TOC particularly problematic. Personally the first thing I do when landing on a Wikipedia article is, usually, click on something in the TOC. Having to scroll down first to find it is, to me, very frustrating. [[User:Argymeg|Argymeg]] ([[User talk:Argymeg|talk]]) 12:24, 27 May 2022 (UTC) == Better font for Arabic/Persian فونت بهتر برای فارسی/عربی == As a Persian user, I think font of wikipedia is not good for these languages; Maybe Vazirmatn or other open-source good looking fonts could be better. به عنوان یک کاربر ایرانی، من فکر می‌کنم که فونت ویکی‌پدیا برای فارسی و عربی جالب نیست؛ شاید وزیرمتن یا سایر فونت‌های منبع‌باز که ظاهری خوبی دارند انتخاب‌های بهتری باشند. [[User:Amiria703|Amiria703]] ([[User talk:Amiria703|talk]]) 22:27, 27 May 2022 (UTC) == It seems like the Page Previews isn't working for me here == Although the new skin looks more sleek, I can't use the (very useful) feature of Page Previews here. So every time I'm in for a deep read, I have to switch back to the old look. Please implement the page previews here too. [[User:SamyakShirsh|SamyakShirsh]] ([[User talk:SamyakShirsh|talk]]) 03:31, 29 May 2022 (UTC) :Hi there! Thanks for the report! Could I get some more information on this issue? Page previews is working for me on both Vector and Vector 2022 skin. Are you talking about the user gadget https://en.wikipedia.org/wiki/Wikipedia:Tools/Navigation_popups ? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:28, 1 June 2022 (UTC) == Use the white page on the right for TOC and navigation == The mobie version of wikipedia app has this really nice way of navigating through sections by swiping eight. I think you can imlement this in the desktop by placing the toc on the right [[User:SamyakShirsh|SamyakShirsh]] ([[User talk:SamyakShirsh|talk]]) 03:35, 29 May 2022 (UTC) == Lone value inside calc() == The style sheet of the new sticky table of contents uses <code>.mw-table-of-contents-container { top: calc(-2em); }</code>. Is there a reason for putting a lone value inside <code>calc()</code>? [[User:Anerisys|Anerisys]] ([[User talk:Anerisys|talk]]) 09:22, 29 May 2022 (UTC) :Thanks for flagging. :The patch introducing this is: :https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/789691/5/resources/skins.vector.styles/layouts/screen.less :The use of calc is accidental, and I think a mix up our end with the appropriate LESS mixin. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:40, 1 June 2022 (UTC) == Trouble With Zooming In == My vision is poor so I usually zoom to 200% on my browser and it is no problem. With the new skin that same magnification causes the sidebar to take up the top of my screen and I can't see the title of the article and know what page I'm on without scrolling. == Opt-in/out for page tools? == There've been a few discussions on this page about the page tools links, but one possibility I haven't seen mentioned here or at [[Reading/Web/Desktop Improvements/Features/Page tools]] is providing a way for each reader/editor to choose which links appear. For example, I use "what links here" quite a lot, "related changes" and "random article" occasionally, and all the others virtually never. Other editors will have different experiences. How about allowing us to reduce clutter by choosing what we want to keep in the menu and what we can do without? [[User:Arms &#38; Hearts|Arms &#38; Hearts]] ([[User talk:Arms &#38; Hearts|talk]]) 19:47, 29 May 2022 (UTC) :+1. I just want to say this was the last straw that made me force legacy Vector on all sites in GlobalPreferences. Is there no opt-out aside from putting <code>tableofcontents=0</code> in the URL? No "Expand all" button? Why is there a blank space beneath the ToC? Why fade it out rather than show as much as possible? This is just user-hostile. [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 16:16, 31 May 2022 (UTC) == Tabs misaligned? == The tabs on the left seem to be next to the tabs on the right, as depicted [https://imgur.com/UfeemZ1 here]. This wasn't the case last week; should this be reported here or elsewhere? Please move if need be. [[User:Ifly6|Ifly6]] ([[User talk:Ifly6|talk]]) 07:01, 31 May 2022 (UTC) :: Hi there, could I get a little more information on this one? What browser and device are you using? Are you viewing this on a mobile phone by any chance? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:23, 1 June 2022 (UTC) == TOC hidden for some reason == {{Tracked|T309632}} When I put my Wikipedia tab to one side at half-width, which I often do whilst multitasking, the TOC disappears for some reason, even though the other side menu (which is the same width as the TOC) stays? I am clueless as to why. All article text is pushed way to the right for some reason. It would make more sense for it to be centred on all screen widths, or to make the entirety of the left menu a solid colour like it was before. Basically, the sidebar should be made thinner as the tab width decreases. Also the lack of a TOC below the lead results in images fighting for space with the infoboxes of articles. There should definitely be an option to move the TOC to where it normally resides as I and likely a lot of other editors find that placement more intuitive. [[User:Miklogfeather|Miklogfeather]] ([[User talk:Miklogfeather|talk]]) 16:06, 31 May 2022 (UTC) :My whole left sidebar has disappeared this morning. I had to switch themes just to get some editing done. — [[User:Xenophore|Xenophore]] ([[User talk:Xenophore|talk]]) 19:42, 6 June 2022 (UTC) == My many criticisms with this == Since it seems like Miraheze is also going to be using this new Vector skin as its default, I would like to offer mine and a lot of other users' criticisms with this new skin: * First of all, the unnecessary dead space. The actual content space is now more narrow and there is a ton of dead space. * The user menu is now completely messed up. The log in button and talk and contribution buttons are hidden behind the three dots, even though those are the most important buttons and should be readily available. In fact, there is no need for anything to be hidden. * The giant TOC in the sidebar. It serves no purpose and just further limits content space. I fail to see how exactly this is an "improvement". Also, the current layout of the skin looks nothing like what is described on the page. There is nothing about a smaller user menu. Currently, the new skin just feels off to me, and I would prefer that this skin be currently branded as "experimental", since it is far from finished. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 21:41, 5 June 2022 (UTC) :I'm fine with everything except the user menu changes and content width changes. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 21:50, 5 June 2022 (UTC) ::Hello @[[User:Blubabluba9990|Blubabluba9990]]. Have you maybe read our documentation where we present the reasons why particular changes are needed, why we've introduced the limited width, and what we're taking into consideration regarding how to use the unused space? I invite you to explore [[Reading/Web/Desktop Improvements/Features|this page]] and its sub-pages. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 19:11, 8 June 2022 (UTC) :::I already did. I read through them more thoroughly and while some seem like a good idea on paper, the user menu and limited width do not really seem to be an "improvement", as there are now extra steps involved. The user menu is the most important thing for me and many users, and now I have to click on a separate button to log in. Maybe less limited width, since right now 1/4 of the screen is just empty space with the new skin. I still use the original Vector as my personal default, but I usually browse logged out. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 22:40, 8 June 2022 (UTC) == Wikistories == Will Vector 2022 be influenced by [[Wikistories]]? --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:09, 6 June 2022 (UTC) :@[[User:NGC 54|NGC 54]], what do you mean by influenced? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:18, 14 June 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: If Vector 2022 will be adapted for (compatible from a design perspective with) Wikistories. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:06, 15 June 2022 (UTC) :::@[[User:NGC 54|NGC 54]], definitely. All the projects that currently are being built are compatible with or neutral to Vector 2022. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:47, 30 June 2022 (UTC) == Visibility Suggestions == Hi, first of all thanks for the work and the nice redesign. I really prefer it over the old vector look already. I use Wikipedia mainly to get an overview or better intuition about topics related to my studies. For me, I prefer the narrower text for better readability and the persistent TOC on the left side of the screen. Makes reading complex pages a lot less painful with easy access to quick navigation. I have some suggestions for the default behaviour of the current design: * There should be an '''option to collapse the navigation sidebar/area''' by default (the area which contains ''Main page'', ''Contents'', ''Current events'' etc.). I am one of those people who rarely uses any of those links. * More of an issue is due to this: The '''TOC is not always immediately visible as the navigation sidebar pushes it too far down.''' Perhaps move the sidebar to somewhere else or make it collapsible by default as suggested? * Additionally, It '''should be more obvious that the navigation sidebar/area is collapsible.''' Currently the toggle is kind of far and disconnected from the area. I only found this out after wondering what that arrow ''<<'' meant. * A nice addition would be to add '''more obvious indicators for current position in the TOC''' (loved this new feature the most!). I think right now the text of the current headline is just black. It would be cool if there was some highlighting or perhaps a dot to make it easier to see at a quick glance. [[User:Devin.halsted|Devin.halsted]] ([[User talk:Devin.halsted|talk]]) 11:21, 8 June 2022 (UTC) :I just noticed, that the toggling of the '''navigation sidebar/area''' does indeed persist. I just didn't notice because i switched between too many tabs. :Something other I noticed, is perhaps that would be good for '''scrollable TOC''' to be more visibly "scrollable"? Right now there is no indication except that maybe some text is cut off. [[User:Devin.halsted|Devin.halsted]] ([[User talk:Devin.halsted|talk]]) 11:27, 8 June 2022 (UTC) == Fifth prototype testing == :''Moved from [[Topic:Wx2jt9he9u1ipkpb]]'' Nothing about sticky header? The order of icons, the present icons for IPs, etc. [[User:NGC 54|NGC 54]] ([[User talk:NGC 54|talk]]) 17:08, 8 June 2022 (UTC) : Thanks for this comment, [[User:NGC 54|NGC 54]]. As we explain on the [[Reading/Web/Desktop Improvements/Fifth prototype testing|page of the fifth round of prototype testing]], that round will only be dedicated to considerations around the visual design. Pure aesthetics. The order of icons, selection of icons for IP etc., are functional considerations which may be discussed right here, on this talk page, regardless of the 5th prototype testing. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:38, 8 June 2022 (UTC) == General Feedback on Sidebar == I agree with other feedback that complains about the sidebar being to wide. This is a waste of space, please reduce the width a bit. However, I think it's not the width of the container but the left margin that makes people (including myself) upset. Therefore, I suggest to completely get rid of the left padding of the main container. Also please reduce the left margin of the article container to just 10 or 20 px. Even more space is wasted if the side bar is collapsed: Why is the sidebar positioned higher than ToC? This leaves free space on top of it. You discussed that the lines of text would be too long otherwise. You could significantly reduce the length if you moved the side bar from the left side to right. You then would have (from left to right) ToC, article, sidebar. Furthermore, the ToC should be on top of the other sections because for most people, ToC is more important than the other links. Although I understand the intention behind this to invite more people to contribute to Wikipedia, I still don't like it. [[User:GeographyMasterDE|GeographyMasterDE]] ([[User talk:GeographyMasterDE|talk]]) 09:16, 9 June 2022 (UTC) == JPG screenshots == Just to point out that [[Reading/Web/Desktop_Improvements|this page]], in which supposed design gurus are offering a lifeline to a wikipedia supposedly plagued by unsofisticated looks, is illustrated with screenshots saved in JPEG format… [[User:Tuvalkin|Tuvalkin]] ([[User talk:Tuvalkin|talk]]) 14:33, 9 June 2022 (UTC) == Limited Content Width == I want to state my opposition the limited content width. I understand the research that the narrower format improves readability. However, there are number of good reasons not to adopt the change: * Yes, [[Reading/Web/Desktop Improvements/Features/Limiting content width#Popular sites with limited width|many sites]] do use fixed width content, but in many cases their motivation is to use the space to sell advertising – a function not befitting Wikimedia. (Some news sites, such as those run by [http://www.gannett.com Gannett] have even taken the theory one step further and display all their articles as overlays – meaning that if a user accidentally clicks in the shadowed area on either side, they are frustratingly taken back to the homepage.) For this reason, full width content suggests a more reputable website. It implies a dedication to the facts, rather than attempting to fill the page with flashy content. (A [http://motherfuckingwebsite.com different website] has a more profane take on the concept. It doesn't deal directly with the issue at hand, but the underlying issue is the same.) This change just seems like another case of mobile overoptimization. * Additionally, as correctly the noted at the [[Reading/Web/Desktop Improvements/Features/Limiting content width#Additional notes|end of the page on the change]] is "part of what makes Wikipedia, and other Wikimedia wikis, a powerful tool for sharing knowledge is that there are very few constraints on how information is presented." For example, it's the reason that widths are specified in "ems" rather than number of columns in the [http://en.wikipedia.org/wiki/Template:Div_col div col template]. Don't get me wrong, I very strongly appreciate the [[Reading/Web/Desktop Improvements/Features/Limiting content width#Establishing a common reading experience|need for a common standard]]. I have [http://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Aviation/Style_guide#Proposed_Aircraft_Manufacture_Aircraft_Section_Table fought for it] on Wikipedia. However, this is not the place for it. * It is clear to me that the majority of commenters here strongly oppose limited content width. It is not to be confused with people just being afraid of change. Note that there are far fewer complaints with most of the other proposed features. I don't have access to the survey results, but a [[Reading/Web/Desktop Improvements/Repository/First Prototype Feedback Report#Summary of results|sample size of 230 users]] seems exceedingly small for such a major change. Furthermore, the commenters here are likely to a better representation of the dedicated portion of the userbase, as they took the time to respond here. I would like to end by stating I am not completely opposed to the change. However, it should only be ''opt-in'', not the default skin. –[[User:Noha307|Noha307]] ([[User talk:Noha307|talk]]) 03:23, 10 June 2022 (UTC) == Width and font size and color == As above, I don't like adding so much margin around the sides, or punishing people with large monitors by forcing them to change skins (which is not easy for everyone). If you are set on fixed-width columns, find a way to wrap columns within a section for wide screens :) rather than leaving huge vistas blank. I like the move to slightly larger font. The link color changes are most welcome. The purple could be a bit more red, to make it less pastel. Good to have a combination of "high contrast w/ other text" and "doesn't wash out on displays or projection in bright areas". [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 00:27, 11 June 2022 (UTC) == Section number in new ToC == I noticed that there is no section number in the new ToC. I hope the section number will be added again because I can quickly see how many topics there are on the talk page. [[User:Bluehill|Bluehill]] ([[User talk:Bluehill|talk]]) 07:28, 11 June 2022 (UTC) == Move infoboxes out of the text area == Given that we are limiting the space for text and freeing up space on the sides, it seems to me that it would be much better to move the infoboxes to the left side, and stretch the text to its full width. Like this: https://znaniya.org/c/pushkin-aleksandr-sergeevich-8cab44. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 23:50, 11 June 2022 (UTC) : I second this. Such a shame that this request is already explicitly [[Reading/Web/Desktop_Improvements/Frequently_asked_questions#Will_you_improve_charts,_maps,_a-/f-/o-/tmboxes,_infoboxes,_navboxes,_other_templates?|rejected in the FAQ]]. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:15, 14 June 2022 (UTC) :@[[User:Iniquity|Iniquity]] & @[[User:Adamant.pwn|Adamant.pwn]], generally, we agree that it is a nice idea. From a reader's standpoint, infoboxes aren't pure content - rather, these are metadata and could totally work as something put next to the content area. However, these are absolutely content from the technical point of view (because these are regular templates). This issue makes it... impossible? to move them. For underlying infrastructural/back-end reasons I can't explain yet. :However, there's a turning point. What would we work on after the Desktop Improvements? We're considering options for functionalities put in that (currently) empty area. So this topic may be revisited in the future. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 19:45, 14 June 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], thanks for the answer! Note: We can create a separate edit area that will be responsible for the infobox, or we can move the infobox using HTML :) [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 19:58, 14 June 2022 (UTC) == July? == > ''We are hoping to increase the set of early adopter wikis gradually, until our improvements are default on all wikis in July 2022.''<br> Has the schedule changed? [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 00:57, 12 June 2022 (UTC) :It has, @[[User:Iniquity|Iniquity]]. Previously it was June, now it's July. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:13, 14 June 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], thanks! It's just strange that there was no information about this before. And the wikis was not informed about it. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:15, 14 June 2022 (UTC) :::Information was sent yesterday in Tech News. Also, this week, I'll send an update to the Village Pumps. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:30, 14 June 2022 (UTC) :::: Yes, I saw it, thanks for that! But the day before yesterday, when I saw this, I got scared, because the community was not ready for this. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 19:59, 14 June 2022 (UTC) :::::We work with individual communities to help them prepare. We also don't ask the most "demanding" communities to prepare yet because Vector 2022 isn't ready to get deployed there either. We take into account that some prefer Vector 2022 to be closer to "finished", and then they would start thinking about preparing. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:17, 14 June 2022 (UTC) == Language switcher opt-out == The new language picker is a deal breaker for me as an active editor who is working with a very diverse array of topics on Wikipedia. I write about [https://en.wikipedia.org/wiki/Māori_phonology Māori language], [https://ru.wikipedia.org/wiki/Тэруха Japanese geisha], [https://ru.wikipedia.org/wiki/Литература_Тайваня Taiwanese literature], [https://ru.wikipedia.org/wiki/Эскимосская_кухня Inuit cuisine], [https://ru.wikipedia.org/wiki/Парагвайская_арфа Paraguayan instruments], [https://ru.wikipedia.org/wiki/Мишон Vietnamese temples], [https://ru.wikipedia.org/wiki/Кабилия Algerian regions], [https://ru.wikipedia.org/wiki/Берберская_кухня Berber cuisine], [https://ru.wikipedia.org/wiki/Кайна_(профессия) Arabic professions]. I write [https://en.wikipedia.org/wiki/Sister_exchange articles] that compare dozens of cultures [https://ru.wikipedia.org/wiki/Грамматическое_число or languages]. I need a way to hover over the list of languages to see the name of the page in a different random language (which can be anything from Korean to Twi). I need to be able to open 50 language editions very quickly to estimate if any of them have good illustrations or any new literature on the topic that I am working on. I often read the same article in 4 languages simply because I can read in a lot of languages and I am wondering which language edition has the best article. The workflow with the new language picker is tremendously stunted. The main idea of the new interface seems to be making the page width more narrow. With that, there is a lot of free space at the sides, and I would like to propose putting a full list of languages there, as an option. [[User:Le Loy|Le Loy]] ([[User talk:Le Loy|talk]]) 00:29, 13 June 2022 (UTC) : Yes, I agree, the decision taken now does not help advanced editors work in projects, but hinders them. I think we need to make a separate setting for the "always open" list. The problems of this list have still existed since sorting was removed. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 15:43, 14 June 2022 (UTC) :{{support}}--[[User:Wdpp|Wdpp]] ([[User talk:Wdpp|talk]]) 11:47, 3 July 2022 (UTC) == Old version == :''Moved from [[Topic:Wxcz2an2ck4s4cdy]]'' After these changes are made, can I still use the old settings? [[user:Ilovemydoodle|Ilovemydoodle]] ([[user talk: Ilovemydoodle|talk]]) 09:26, 13 June 2022 (UTC) : Yes [[user:Ilovemydoodle|Ilovemydoodle]], legacy Vector will be available and you will be able to use it as your skin. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:24, 14 June 2022 (UTC) ::{{ping|SGrabarczuk (WMF)}} Why does have to be called “legacy”? legacy implies that something is outdated, inferior, no longer supported, none of which apply to Vector "legacy". Maybe instead, you could call it "advanced", "expert", or "classic". – [[User:Ilovemydoodle2|Ilovemydoodle2]] ([[User talk:Ilovemydoodle2|talk]]) 17:48, 20 July 2022 (UTC) :::@[[User:Ilovemydoodle2|Ilovemydoodle2]], the motivation is purely technical. This is because it's "frozen". The Wikimedia Foundation will not develop it - there will be no actively built version of Vector parallel to Vector 2022. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 20:46, 20 July 2022 (UTC) == Incorrect language name for Czech == I noticed that for Czech (čeština in Czech) in the new look the first letter is incorrect, it says "Ceština" instead of "Čeština". I do think it is pretty funny, but would say it should be consistent with the rest of the themes. I hope this is the right place for this, I didn't find anywhere else to post. [[User:Filiptronicek|Filiptronicek]] ([[User talk:Filiptronicek|talk]]) 09:46, 13 June 2022 (UTC) :Hello @[[User:Filiptronicek|Filiptronicek]]. Thanks for writing to us. Most likely, it's not within our area, but I'll help you if the problem still exists. Where do you see this? On Polish and English Wikipedias, I see "Čeština". [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:42, 14 June 2022 (UTC) ::Hi there @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], perhaps it may have something to do with Czech being suggested to me as a language? I don't have an alt account to test this with though. ::Screenshot of what I see on the English wikipedia: https://i.imgur.com/T40u7rN.png. It is some very interesting behavior. Thanks for looking into this. [[User:Filiptronicek|Filiptronicek]] ([[User talk:Filiptronicek|talk]]) 13:45, 15 June 2022 (UTC) == Please take the interlanguage link (aka "green link") on Chinese Wikipedia into consideration! == The Chinese Wikipedia currently uses a green-colored link for interlanguage links in articles, and it seems to fail the WCAG AAA. These links can been seen at [[zh:Deadmau5]], for instance. These links are used a lot on Chinese Wikipedia, and I'm not sure if it is good for readers. If you want to evaluate link colors, please also take this green link into consideration, thank you. Looking forward to your professional advice! [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 11:38, 13 June 2022 (UTC) :I know these links are not part of Vector 2022, but they are part of the user experience, and currently there is a discussion at Chinese Wikipedia's Village Pump about the choice of color of them, so I posted my message here. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 11:43, 13 June 2022 (UTC) == Table of content (ToC) == Hi! Since weeks ago I don't see the table of content in the sidebar like I used to do before. It just disappeared. It happens when I'm connected in my phone using desktop version. Best regards! '''''[[User talk:Miaow|<span style="background:#88b;color:#cff;">Mia<span style="background:#99c">o<span style="background:#88b">w</span></span></span>]]''''' 12:06, 13 June 2022 (UTC) :Hello @[[User:Miaow|Miaow]]. Thank you for reporting this problem. We're working on a better look of TOC on small screens. I also strongly suggest you selecting the [[Reading/Web/Advanced mobile contributions|advanced mobile contributions]] mode when you're using your phone. That mode is dedicated for mobile, in contrast to Desktop Improvements. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 10:38, 14 June 2022 (UTC) == Better alignment for wide screens == [[File:Article with new vector.png|thumb|]] Here's how the new design looks on my laptop with 2560x1600 resolution. Ok, I get it, you won't do anything about the max-width and you insist on using this path. But look, the parts highlighted with purple ellipses just look misaligned. It just begs for the following: * Reduce the white background so that its right end matches the right end of the article OR insert something into that area. Having gray empty space is ok, but having both white and gray empty spaces look just silly. * Reduce the header so that its right end matches the right end of the article OR extend the white background of the header so that it fills the whole width of the page (see e.g. how it's done on [https://stackexchange.com StackExchange] or [https://www.reddit.com Reddit]. Again, I get your rationale that having empty space is ok. But having a white empty space on top of the gray empty space... Don't you think it's a bit too much? [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 01:23, 14 June 2022 (UTC) : [https://squidfunk.github.io/mkdocs-material/getting-started/ Material for MkDocs] is another example of what I consider a more successful implementation of reduced max-width. The main part has the same background (having same white background on the whole page would also look good on wiki) and the header part has background that extends beyond max-width. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 01:25, 14 June 2022 (UTC) ::When we look to the prototype https://di-article-tools-2.web.app/Blue%20whale?en (and https://vector-2022.web.app/Brown_bear), it's fill by "Tools", "In other projects", "Print, share, link" [[User:Koreller|Koreller]] ([[User talk:Koreller|talk]]) 08:31, 14 June 2022 (UTC) ::: It looks somewhat nicer, but the white empty space is still there if you collapse sidebars or scroll a bit... Also seem to have different defaults for logged in and logged out users. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:12, 14 June 2022 (UTC) == Launching New Version == :''Moved from [[Topic:Wxf5fv5pmxyyccdy]]'' When shall the new version ([[Reading/Web/Desktop Improvements/Fifth prototype testing/Feedback|Fifth prototype]]) be launched? [[user: Stnts256|Stnts256]] ([[user talk:Stnts256|talk]]) 08:54, 14 June 2022 (UTC) : We hope to launch Vector 2022 as default by the end of July. You can use it already by [[Special:Preferences#mw-prefsection-rendering|selecting this option in your preferences]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:28, 14 June 2022 (UTC) ::Thank you [[User:SGrabarczuk (WMF)|SGrabarczuk]] [[User:Stnts256|Stnts256]] ([[User talk:Stnts256|talk]]) 14:04, 14 June 2022 (UTC) == Keep watchlist in the sticky header == For an active Wikipedia editor, watchlist is likely the most popular destination when you're on some page. Would be great to keep the link there in the header, even after some scrolling. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:24, 14 June 2022 (UTC) : Keeping alerts and notices would also be nice. And also for it to work on the talk pages... [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:26, 14 June 2022 (UTC) : Yes, it bothers me that my control panel disappears. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:01, 14 June 2022 (UTC) : Second that. The most-used buttons of the standard interface (watchlist, contribs, interwikis) should stay in place, accessible with one mouse click. With the proposed layout I have to press tab-tab-tab... and then ctrl-enter to get to the watchlist. Why so? I can't reliably use the proposed drop-down menu with mouse, it's a common age-related ailment. I'd highly recommend to retain at least some bits of usability-for-disabilities: no complex manipulations. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 09:39, 15 June 2022 (UTC) == clear:both rendering on old browsers == {{Tracked|T309711}} I have tried browsing the wiki on Internet Explorer 11 on the new skin for one last time before Microsoft disables it, and it worked well, except something I have noticed is that the CSS property <code>@media screen .mw-body-header::after { clear:both; }</code> causes the side bar to push down the content. When unticking <code>clear:both</code> in the page inspector or when the side bar is hidden, it appears as usual. While fixing it for IE11 won't be relevant anymore, earlier versions of other browsers might have this flaw too. Mentioning it just in case. [[User:Octobod|Octobod]] ([[User talk:Octobod|talk]]) 23:29, 14 June 2022 (UTC) == Where are the interwikis? == Is there a simple way to access interwikis, other than by going to wikidata? Also, having two quasi-interwikis for wikidata is quite confusing. Only the second one actually works, the first one defaults to wikidata's start page. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 09:46, 15 June 2022 (UTC) :@[[User:Retired electrician|Retired electrician]] - currently, the adding interwiki links is available from the sidebar: "Edit interlanguage links" in the tools section. In the future, we would like to add them into the language selector as well. We are currently working with our Language team on this - see [[phab:T290436|Add support for empty states to the current language selector]] in phabricator for more details. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:23, 16 June 2022 (UTC) :: {{ping|OVasileva (WMF)}}, I see. Curiously, "Edit interlanguage links" does not appear on the main page (at least in ru-wp). [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 13:50, 16 June 2022 (UTC) == Suggestion: Round borders == I appreciate very much the efforts to make the design of Wikipedia less outdated, and imo this new design is amazing. To make it even better I would suggest you guys to put round borders in the boxes, so let's add border-radius:14px in these functions! This will make it cleaner and softer! [[User:Duke of Wikipädia|Duke of Wikipädia]] ([[User talk:Duke of Wikipädia|talk]]) 22:27, 16 June 2022 (UTC) == Top margin in title == Just noticed the new version and it looks like the title's top margin was reduced. There is an awkward amount of bottom margin for the title compared to top margin and I personally prefer the previous margins. [[User:0xDeadbeef|0xDeadbeef]] ([[User talk:0xDeadbeef|talk]]) 06:55, 17 June 2022 (UTC) == Very minor improvements == I just got the new toolbar this morning, and I absolutely love it! Finally Wikipedia does not look old anymore. But I would like you guys to add a little more than just a border for the active section in the toolbar, probably a lighter background for active tabs and a darker one for non active tabs. For example, if I'm reading an article, the 'Read' tab in addition to the bottom border, it should be lighter. The 'Talk' tab should be lighter also if I'm in the talk section. This should work well with something like option 3 combined with option 9 (where the header and the title has grey background) in [https://di-visual-design-borders-bgs.web.app/Zebra this border and background demo here]. I like option 3 a lot so it would be good if you guys implemented it, haha. I apologize if my English is not clear. [[User:Klrfl|Klrfl]] ([[User talk:Klrfl|talk]]) 12:26, 17 June 2022 (UTC) == new table of contents == For pages with a long table of contents such as this one, the table of contents starts jumping to highlight the current heading. Would it be possible to consider smooth scrolling behaviour for the table of contents at the new location (as for example invoked by <code>.vector-toc-enabled .sidebar-toc { scroll-behavior: smooth; }</code>)? Or is there something like a frozen state or is/was/will be this rejected for another reason? --[[User:CamelCaseNick|CamelCaseNick]] ([[User talk:CamelCaseNick|talk]]) 23:15, 17 June 2022 (UTC) :{{support}} [[User:Patafisik|Patafisik]] ([[User talk:Patafisik|talk]]) 10:06, 21 June 2022 (UTC) == Sister project links == (From [https://it.wikipedia.org/w/index.php?title=Discussioni_utente%3APatafisik_%28WMF%29&type=revision&diff=127968745&oldid=127933193 it.wikipedia]) {{ping|Friniate}} suggests to gather the Wikidata link and the Sister project links in the same place.--[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 09:49, 20 June 2022 (UTC) == Impact == How does the team plan to assess/measure whether the Vector changes work towards their stated goals, so that we're able to correct course in case they don't? [[User:Nemo_bis|Nemo]] 00:41, 21 June 2022 (UTC) == Great addition of ToC menu through icon wrt zoom !!! == I <s>have just</s> discovered a few days ago, in the french version of WP, as well as here in MediaWiki, the addition of a ToC menu, just before the title, that appears when the left column is NOT visible (at least effect of zooming), and '''this is a GREAT GREAT improvement, MANY-many thanks to the developpers'''. There still remains a small bug that appeared with this change (at least I didn't notice it before) : the upper (collapsile) bar appears no more. It reappears back when zoom permits back the side left column (tested with an article page in fr.WP ; no appearance "here" while editing, or even while just reading. but I guess it's a different thing, maybe because this is a talk page : I get the same "behaviour" in a talk page from fr.WP : no appearance of the upper collapside bar even if a left colum ToC is present. Might not be a "bug", but a feature, though I would personnaly prefer a uniform behaviour). Whatever, great thanks to the developers.<br/> &nbsp; (Poke @[[User:Patafisik (WMF)|Patafisik (WMF)]] : thanks for relaying these improvements, and back, our comments. Best :-) )<br/> &nbsp; -- [[User:Eric.LEWIN|Eric.LEWIN]] ([[User talk:Eric.LEWIN|talk]]) 06:17, 21 June 2022 (UTC) == Both the ToCs == (From the French Wikipedia [[:fr:Discussion_Projet:Am%C3%A9lioration_de_l%27interface_par_la_WMF#Sommaire_%C3%A0_gauche_:_ajouter_plut%C3%B4t_que_remplacer_?|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/24_mai_2022#Sommaire|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/26_mai_2022#Bug_du_sommaire|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/19_juin_2022#Tables_des_mati%C3%A8res|here]] and [[:fr:Wikipédia:Le_Bistro/25_juin_2022#Sommaire_dans_la_barre_de_gauche|here]]) I've already reported this to Szymon, but I think it will be important to have this suggestion also in this page, visible to all and open to comments. Different users of the French Wikipedia consider the old ToC and the new one as two complementary tools, and they want both! Reasons: 1) for the context, the ToC should be on the top of the article. If we have the first part of the sidebar occupied by the wiki navigation menu, the ToC is too far on the bottom of the page, it appears on the top only when you scroll down 2) the layout of articles with illustrations is completely disrupted. Both why? "When I look at the beginning of an article, I expect to see a ToC with the main sections in order to understand how the article is structured (quite like in a Word document). This makes it easier to read. The ToC on the left is then very useful when you scroll down the article and want to navigate between sections, but it is an additional feature. It should not replace the current summary, which is still useful. Or it should be displayed from the start at the top left, when you are at the top of the article (quite like on Universalis)." (summarised by Pronoia [https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia%3ALe_Bistro%2F26_mai_2022&type=revision&diff=194205255&oldid=194153014 here])--[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 11:45, 21 June 2022 (UTC) == Интервики в правый блок == Сейчас правое поле статьи абсолютно пустое. Что мешает перенести туда интервики-ссылки, вместо их полного сворачивания, а также подходящие по смыслу к ним ссылки на братские проекты? Это позволит: 1) избежать совершенно ненужного сворачивания списка (бессмысленно его уменьшать, когда высвободилось столько места); 2) заполнить правое поле; 3) частично разгрузить левое поле, чтобы оглавление было лучше видно сразу на первой же странице текста (сейчас при текущих настройках экрана я во французской Википедии вижу в среднем две верхних строки оглавления). [[User:AndyVolykhov|AndyVolykhov]] ([[User talk:AndyVolykhov|talk]]) 12:51, 21 June 2022 (UTC) == Languages in the new desktop interface == In the older interface I can select the interwikis that I need most and put them on top of the interwikis' list; same possibility should be in the newer interface. [[User:Leokand|Leokand]] ([[User talk:Leokand|talk]]) 15:06, 21 June 2022 (UTC) == minor issues == * The position at which the table of contents is sticky changes with the sticky header becoming visible/hidden. (<code>.vector-toc-enabled.vector-sticky-header-visible .sidebar-toc { margin-top: 1.5em }</code> vs. <code>.vector-toc-enabled .sidebar-toc { margin-top: 3.5em }</code>) With the sidebar navigation hidden, this makes the table of contents jump up by <code>2em</code> while scrolling. * At a window width of exactly 1000px the table of contents on the left is displayed but styled like the drop-down table of contents and the drop-down button is still visible but has no influence on the table of contents. * At 720px+ the logo is displayed, the username and potentially a language switcher. With my username on this wiki in German, the watchlist and the user menu are outside the viewport, so this threshold is chosen to narrow. Maybe a solution would be to move the username link to the user menu at 1000px and lower. (For CSS rendering, I use Firefox v101.) -- [[User:CamelCaseNick|CamelCaseNick]] ([[User talk:CamelCaseNick|talk]]) 17:28, 21 June 2022 (UTC) == Drop-down menues = poor accessibility == Repeating prior statements for clarity: May I speak on behalf of old folks with less-than-perfect control of palms and fingers. The replacement of simple "button" links (contribution, statistics, interwikis...) with drop-down menues becomes a huge inconvenience. In plain monobook, I can simply click on the interwiki, and hopefully get the desired tab at the first try. In vector-2022, I cannot reliably pull down the drop-down list and then select something with a mouse... it almost never works as intended. A very common age-related ailment, it just happens. The only robust workaround is to use the keyboard to "tab-tab-tab..." to the desired control box, and then "enter-tab-tab-...-enter" through the list. And, in case of interwikis, selecting the main (en:) wikipedia takes atrociously long time - instead of being #1 entry, as in old good monobook with my normal preference settings, it's somewhere down the middle of the list. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:46, 21 June 2022 (UTC) == Irish language Wikipedia and Vector 2022 == [[File:Irish Wikipedia random article - Vector 2022.png|thumb|ga.wp random article screencap - Vector 2022]] [[File:Irish Wikipedia random article - Vector old.png|thumb|ga.wp random article screencap - current Vector]] Hi there. I'm [[w:ga:User:Alison]] - admin and bureaucrat on the Irish language Wikipedia. I'd be remiss in not providing feedback, I think, so here goes. * I see other folks pointing out the massive amount of whitespace / padding in the left side navbar which is squeezing out the actual article text on the right. On our wiki, it really seems significant. IMO, article is all, and we seem to be sacrificing actual content real-estate for ... what, exactly? Yes, it looks 'less cluttered', but there's actually less content - especially for those of us who both browse ''and'' edit on laptop screens. * On the top tab section (which is otherwise quite nice), you can see the ''Plé'' (Talk) and ''Léigh'' (Read) are scrunched together with no separation. I18n bug, maybe? * The main image and title have lost their localization and now show "Wikipedia" instead of "Vicipéid" - this could just be an image localization / config issue. Could someone point me in the right direction, maybe? I did the original, later-font localization for our wiki, some years back, so happy to dip in and fix :) Le gach dea-ghuí (best regards), -- Allie [[User:Alison|<span style="color:#FF823D;font-family: comic sans ms">'''A<font color= "#FF7C0A">l<font color= "#FFB550">is</font>o</font>n'''</span>]] <sup>[[User talk:Alison|❤]]</sup> 16:17, 22 June 2022 (UTC) :multilingual Wikipedians: during redesigh include current non-english desighs for evaluation, including spanish, french and german. They have good ideas and bad ideas... [[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 01:10, 23 June 2022 (UTC) : The "PléLéigh" issue looks like it's [[phab:T309223|T309223]], a known issue. Until it is fixed in MediaWiki, try updating your browser(s) – the issue occurs if your browser doesn't support a certain relatively new feature. [[User:Rummskartoffel|Rummskartoffel]] ([[User talk:Rummskartoffel|talk]]) 21:59, 23 June 2022 (UTC) ::Hey there! Regarding logos https://phabricator.wikimedia.org/T244486 is what you are looking for - basically every logo needs to be recreated. You can request one on that ticket to be prioritized higher or find information about creating new ones. ::Regarding sidebar whitespace I am not sure I understand. The extra padding is for the table of contents underneath the sidebar. You say it's squeezing article text on the right but in your screenshots the Vector 2022 screenshot shows more of the article text. I can see the description section heading for example. ::I can confirm the PléLéigh issue is a bug and will hopefully be fixed soon. ::Hope this is helpful. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 01:02, 1 July 2022 (UTC) == TOC-Feedback == I just recognized what disturbs me the most with the new TOC. I wasn't able to access the TOC without scrolling or clicking when using a community-Page. The main thing: '''It's mixing system and content'''. The TOC is for the content, but appearing on a place of "system". The "frame" is the Media-Wikisystem: accessing Community-Pages, Help, recent changes, user-page etc. Inside the "frame" is the content (the "article", the "book"...). Although it's kind of logical to have the TOC sticky on the side there are so many problems with it: # the TOC can't be manipulated by magic words, which is a pretty well used functionality. # the TOC can't be placed to the right, which is pretty often used in german wikibooks. # the TOC is in competition with the other menus. # the TOC is now at a place where normally links to other pages are placed. The same fear of mixing system and content goes with switching the Header and the "Editing-Tabs" (Compare https://di-article-tools-2.web.app/Blue_whale: '''Blue Whale''' first, ''read/edit'' second). BTW the TOC works at this demo-page because the Main Menu is so short. But since this is not fixed (which is a good thing!), the Main Menu might be longer. A good illustration of the problem is visible just the paragraph above this: [[#Irish language Wikipedia and Vector 2022]]. The TOC in the Vector22-Example is completely missing! So, just as an Idea: '''divide system and content''' - say system top&left (as it's always been) and content bottom&right. the TOC could be placed "always right" next to the text. At least please let the editor choose what to do with the TOC. I mean, wouldn't it be so bad if it's within the Content '''and''' at the side? I'm fine with the new skin and all the work that has been put in, but the TOC is becoming unusable for me like it is right now. If it's really becoming permanent, it will probably result in "self-made-TOCs" which will break pretty often, because of the "wiki"-system. [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 17:37, 22 June 2022 (UTC) == The new design is everything I feared == Jumpable, irritatingly movable buttons? Check. Sticky UI that eats up immense space both at the top (header) and to the left (table of contents)? Check. Tiny narrow line of text in the middle? Check. Buttons not looking like buttons, thus confusing me as to what I may click? Check. The language menu made objectively worse, with more clicks necessary to use than before? Check. Every single change is atrocious, negative, and honestly makes me feel depressed - I will either try to scour Reddit for browser extensions to remove as much of it as possible (no, logged in user things are useless to me as I'm never logged in), or I will leave Wikipedia for good (mental health is more important than knowledge). Just look at this useless eyesore of a sticky table of contents ([https://i.postimg.cc/bz2zZM2C/2022-06-22-Wikipedia-English-51-UI-bug.png screenshot on postimage] - I hope, you aren't getting the ads, I'm getting none). Even aesthetics-wise, it's botched - the bottom is smudged, the top cut-off. And it's not even at the edge of the screen! It's an exercise in ugliness. And just saying it here, this Wikimedia redesign is already making it unintuitive for me to write. When I tried to insert the link, I couldn't even see the [https://i.postimg.cc/qBp0ZvDS/2022-06-22-Wikipedia-English-53-UI-bug.png ''upload'' button] - because it's on the edge of the sub-menu (like on phones), not somewhere sensible, like on computers (again, compare how it is on current Wikipedia - a [https://postimg.cc/TpMNbPHg large nice menu with clear buttons at the bottom], computer design). [[User:Adûnâi|Adûnâi]] ([[User talk:Adûnâi|talk]]) 18:55, 22 June 2022 (UTC) == wordmark no longer appears after upgrading to MediaWiki 1.38.1, style bugs == After upgrading to MediaWiki 1.38.1 from 1.36.1, the wordmark no longer appears next to the icon in the upper left. If the window is wide enough, the 150px space for the wordmark is reserved but is empty. When you make the window wider past a certain width, the coloring behind the sidebar also vanishes. This happens with Vector 2010 in both legacy and non-legacy mode and in Vector 2022. The wordmark image is an svg that has not moved and still has correct permissions [[User:Queernix1028|Queernix1028]] ([[User talk:Queernix1028|talk]]) 19:43, 22 June 2022 (UTC) :What is the value of wgLogos in your LocalSettings.php? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:22, 29 June 2022 (UTC) $wgLogos = [ 'icon' => "$wgScriptPath/images/arcc/logo.svg", '1x' => "$wgScriptPath/images/arcc/logo.png", 'wordmark' => [ 'src' => "$wgScriptPath/images/arcc/wordmark.png", '1x' => "$wgScriptPath/images/arcc/wordmark.svg", 'width' => 150, ], ]; ::It previously worked with wordmark src set to the svg file, but now neither that configuration nor the one above work. [[User:Queernix1028|Queernix1028]] ([[User talk:Queernix1028|talk]]) 14:32, 29 June 2022 (UTC) :I believe you need to set a height on the wordmark. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 00:55, 1 July 2022 (UTC) == Menus — https://di-visual-design-menus.web.app/Brown_bear. == *left side menu persistency is screen wasteful, bad idea ** use a tab like google maps? *left side menu: should be hamburger only **as an option for experienced, registered users **need style sheet that puts ''left side column'' '''at bottom of page''' as a footer *language list: **should include native and english names **include a user-customizable shortlist *[[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 00:57, 23 June 2022 (UTC) == Language links on Wikidata are right at the bottom of the page == I've enabled the new theme (Vector 2022) globally on all wikis. I generally like the new interface. However when I am on wikidata, previously the interlanguage links were on the right. (Where an infobox usually goes on a wikipedia page) Now they are right at the bottom of the page! Some wikidata pages are massive, and having to scroll all the way down to the bottom of the screen to do the thing I do most frequently on wikidata (add new language links) is a real pain. Please can you move the language links on wikidata back to the top (top right) of the page? - [[User:Rooiratel|Rooiratel]] ([[User talk:Rooiratel|talk]]) 14:25, 23 June 2022 (UTC) :Hello @[[User:Rooiratel|Rooiratel]]. Thanks for your opinion. Are you talking about the desktop view? What's the resolution of your screen? I've tried to narrow my window down and change its width, and it seems that the width thresholds when the interwiki links go from the bottom to the right are the same. Is there any setting you use that may make your experience different? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:50, 27 June 2022 (UTC) ::Hi {{ping|SGrabarczuk (WMF)}} this is for the desktop view. I am seeing this behaviour on my 1080p laptop screen and my 1440p desktop screen. I haven't used the mobile view, so can't comment on that. - [[User:Rooiratel|Rooiratel]] ([[User talk:Rooiratel|talk]]) 06:32, 28 June 2022 (UTC) == Infobox element alignment is mangled in mobile view == Maybe I'm doing something wrong, but when I click on "Mobile view" with Vector 2022, many of the infobox elements are misaligned. Many elements that should be centered are left-aligned, and many elements that should be left-aligned are centered. At least that's what it looks like for me in Chrome for Mac OS at [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic&useskin=vector-2022 this page]. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 02:57, 24 June 2022 (UTC) :Wow, that looks odd. Thanks @[[User:Jonesey95|Jonesey95]] for reporting this. Right now, I only have one question - why do you use the mobile view and Vector 2022 mixed together? Minerva is dedicated for mobile, and Vector 2022 is dedicated for desktop. Having these two at the same time is bold and original :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:08, 27 June 2022 (UTC) ::I was just doing some very beginner-level QA testing. Editors do all sorts of ridiculous things, so I try to do some QA testing by doing ridiculous things. If you want editors to use Vector 2022 for desktop-only and Minerva for mobile-only, then make the "Mobile view"/"Desktop view" link at the bottom of the screen switch between the skins. Meanwhile, I'll be over here in legacy Vector where I can fill my browser window with content.... [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 01:15, 28 June 2022 (UTC) Using the mobile domain with the Vector skin invokes a special mode with lots of odd behaviour. It's not part of this project but will hopefully get fixed some day. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:30, 28 June 2022 (UTC) == "Related articles" appear to be missing == I do not see the "Related articles" section at the bottom of the mobile view. I don't really care, but since the "Principles" section of this page says "We do not remove any functionality", I thought I'd mention it. It makes me wonder what other functionality has been removed, and whether this principle is really being followed in a systematic way. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 03:02, 24 June 2022 (UTC) RelatedArticles appears to be working fine to me. I see it on Minerva. What do you mean by "at the bottom of mobile view"? The scope of this project is the desktop site so no changes to the mobile domain have been made. RelatedArticles does not show on the skins of certain websites and has not shown on Vector or Vector 2022 unless the community has explicitly requested. See [[phab:T144812]], [[phab:T181242]] and [[phab:T278611]] for example. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:59, 24 June 2022 (UTC) :I think this is my mistake. I was comparing [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic this] (default mobile view on en.WP) with [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic&useskin=vector-2022 this] (Vector 2022 mobile view) and assuming that the default mobile view used some version of the Vector skin, but I think that is not correct. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 16:38, 24 June 2022 (UTC) Ah okay. This mode is only accessible by a special URL and is not being worked on as part of this project. Thanks for taking the time to explain! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:28, 28 June 2022 (UTC) == 非常に見にくい == 日本語で失礼します。本日ごろから日本語版ウィキペディアのスキンに変更があったようですが、 # 文字の大きさをブラウザ側から変更できない(Safari使用)。 # そもそも標準の文字サイズが大きすぎる。 # 目次が項目名の横に位置が変わったせいでアクセスが煩雑になった。 # Infoボックスが大きすぎる などの変更のせいで、余計見づらくなったような気がします。可能であれば改善するか、もしくは変更前のスキンに戻して欲しいです。 [[User:イカしたイカ|イカしたイカ]] ([[User talk:イカしたイカ|talk]]) 08:38, 24 June 2022 (UTC) :感謝します、@[[User:イカしたイカ|イカしたイカ]]さん。 :First of all, you don't need to apologize for writing in Japanese. We welcome comments in any language. :# Would you like just to change the default font size? Or would you be able to zoom in and out, and see the font size adjust? :# Do you think making the text line wider and keeping the default font size would fix the problem? :# Why do you think access is more complicated now? Our motivation was to reposition the table of context to make it more accessible. What do you think is not working? :# Do you think the problem is related to the default font size? :まず第一に、あなたは日本語で書いたことを謝罪する必要はありません。 どんな言語でもコメントを歓迎します。 :# デフォルトのフォントサイズを変更しますか? または、ズームインおよびズームアウトして、フォントサイズが調整されるのを確認できますか? :# テキスト行を広くし、デフォルトのフォントサイズを維持することで、問題が解決すると思いますか? :# なぜ今、アクセスがより複雑になっていると思いますか? 私たちの動機は、コンテキストのテーブルを再配置して、よりアクセスしやすくすることでした。 何が機能していないと思いますか? :# 問題はデフォルトのフォントサイズに関連していると思いますか? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:18, 12 July 2022 (UTC) == Please evaluate CJK characters' font size in Vector 2022 == {{tracked|T311469}} For your infomation, the Chinese Wikipedia already has a [[zh:MediaWiki:Gadget-large-font.css|gadget]] that increases the font size for a better Chinese reading experience. Japanese and classical Chinese Wikipedia also have such kinds of gadgets. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 08:19, 25 June 2022 (UTC) :It would be nice if we could integrate these gadgets into new Vector skin directly. This would benefit other CJK and multilingual wikis. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 08:20, 25 June 2022 (UTC) ::Thanks @[[User:Diskdance|Diskdance]]! @[[User:AHollender (WMF)|AHollender (WMF)]] FYI :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:03, 27 June 2022 (UTC) I think we should create a phabricator ticket for this one. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:29, 28 June 2022 (UTC) == Feedback regarding Vector (2022) TOC == I've had Vector (2022) enabled for a while, and generally like it. However: * I don't feel the new way of handling the TOC and side menu is user friendly. It took me a while to notice I could hide the side menu only to raise the TOC up the page, as I assumed it would also hide the TOC since the two are part of the same sidebar. With the side menu visible, I had to scroll much further down than usual to find the TOC on many articles with short lead sections, which undermined the convenience previously provided by the TOC as a way to skip scrolling and quickly navigate to a desired section. ** It also doesn't help that the [[w:Template_talk:Skip_to_talk#Broken_functionality_with_new_version_of_vector_theme|new TOC breaks the functionality of]] {{tl|Skip to talk}}, widely used on talk pages on Wikipedia, but I now understand that the change is intended to make that template unnecessary. ** The prototype [https://di-visual-design-menus.web.app/Brown_bear linked by others above] deals with some of these issues but is still a bit confusing. It's not clear that clicking "hide" on the TOC should result in a menu appearing by the article title rather than just collapsing it like collapsible lists which use the same "[hide]" links; while this behaviour can be learned, it's not clear why the hidden TOC menu button doesn't persist between the search icon and article title when scrolling down, which is what I expected after seeing it collapse to a button beside the article title. * The new sidebar is wider to accommodate the TOC, but much of that space is blank so I'm not sure it needs to be quite so wide, particularly as the added width can cause issues such as galleries by default having less space for images per row. I understand the motivation is to limit the characters of text per line, but doing so by padding the sidebar with empty space seems like an unhelpful way to achieve that. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 16:57, 26 June 2022 (UTC) == Where are the watch/unwatch buttons? == Alright, if the article is long enough to be scrolled, I should scroll it down, the top row of icons will jerk left-right, and the "watchlist" icon will become the "watch/unwatch" toggle. Hopelessly inconvenient, counterintuitive, but it works. But what if the article is so short that it won't scroll at all? [https://ru.wikipedia.org/w/index.php?title=%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%8F:%D0%A0%D0%B5%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5/%D0%9E%D0%B1%D1%8A%D0%B5%D0%B4%D0%B8%D0%BD%D1%91%D0%BD%D0%BD%D1%8B%D0%B9_%D0%B2%D0%BE%D0%BA%D0%B7%D0%B0%D0%BB_%D0%A6%D0%B8%D0%BD%D1%86%D0%B8%D0%BD%D0%BD%D0%B0%D1%82%D0%B8&oldid=123611287 example] Seems like "preferences/watchlist/edit raw watchlist" is the only go-around, is it not? [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 12:13, 27 June 2022 (UTC) :@[[User:Retired electrician|Retired electrician]]: There's a smaller star-shaped watch/unwatch toggle to the right of the "View history"/"История" link. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 14:48, 27 June 2022 (UTC) :: Thanks, that was most unexpected. I'd rather prefer old good text links. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 15:59, 27 June 2022 (UTC) The new star looks almost exactly like the existing GA star, just a different shade of grey (but in almost the same corner location as in standard monobook). [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 16:02, 27 June 2022 (UTC) :"Thanks, that was most unexpected. I'd rather prefer old good text links" - you're a Monobook user, am I right? This may be a good reason why it's most unexpected for you. Vector 2022 is based on Vector legacy (2010), and the star icon has been there for 12 years. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 01:51, 28 June 2022 (UTC) == Merge notification block in the header: notifications and alerts == {{Tracked|T142981}} For me, it has always been a strange decision that notifications were divided into two unrelated blocks and icons with incomprehensible categorization. I forgot about it, but now I'm paying attention again. Given that we removed the text from all menus, there are now a lot of icons at the top that do not understand what they do. Different blocks of notifications do not help this at all. Maybe it's time to put them in one menu and break it there already? Filters, tabs, whatever :) But at least you won't get confused in the icons. I personally still (6 years!) do not know what their fundamental difference is. I asked my friends and they don't know either. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 17:29, 27 June 2022 (UTC) :{{Strong oppose}}. The notices are the notifications that are not very important/urgent, unlike the alerts. Merging them would make me unable to found out at a glance if I have any important/urgent notification, and would also overload the notification box, as I receive many notifications. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 22:19, 27 June 2022 (UTC) :: It seems to me that it is possible to do this with filters and colored marker icons. Or a separate setting for users who really need it. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 09:47, 28 June 2022 (UTC) :{{Comment}}. I agree that the distinction could be clearer, but don't necessarily agree that there should be only one button. Presently, when both are empty the only difference between them is the header text and icon. Both share the exact same two buttons, which link to the same destinations. The text in the box doesn't even distinguish, reading "There are no notifications" instead of "There are no alerts". There isn't even a "help" or "about" link unique to each of them to explain the difference or what gets sent where. If you follow the links to the special page or preferences, it's still not clear which notifications are sent where. :Based on the names, I would've assumed the difference would be that alerts are specifically for subscriptions to [[Wikipedia:Article alerts|article alerts]], whereas notifications would be for everything else. It makes sense to split them, since alerts would be activity that's less personal to the receiver. "Alerts" would be like a daily newspaper, but "notifications" are more like personal mail. Except this isn't how the system actually functions; messages to the receiver's talk page are placed under "Alerts" rather "Notices", for example. :I understand that it may be helpful to filter urgent notifications from less urgent ones, but what counts as urgent or important? Shouldn't that be decided by the user's preferences? It would make more sense to have something like tabs, as Iniquity suggested, to filter types of notifications; this would let that user decide what is important. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 22:33, 27 June 2022 (UTC) == Table of contents: Bold format for active section == I really appreciate the new skin and layout. In the beta, the active/current section of the article was formatted bold in the table of contents on the left side. But in the live version, it's regular and black. I find it really, really hard to differentiate between the normal blue titles and the active title, because the only difference is the black vs. blue color. Could you please make the active titles bold again? Thank you! [[User:Lhennen|Lhennen]] ([[User talk:Lhennen|talk]]) 21:11, 29 June 2022 (UTC) :+1 Bold and black would be best imo. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:43, 1 July 2022 (UTC) ::@[[User:Lhennen|Lhennen]], @[[User:L.xschlag|L.xschlag]] - thank you for your feedback! Not sure if you've seen, but we are currently in the middle of testing some [[Reading/Web/Desktop Improvements/Fifth prototype testing|prototypes]] related to this question. You're welcome to give us more detailed feedback on the prototype page. One of the things we're testing on these is the way links should appear within the table of contents (see https://di-visual-design-toc-active.web.app/Otter) for an example. Currently, our feedback is showing us that people are leaning towards option 2: bold and black so we will most likely be continuing with that option and making the titles bold. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:08, 4 July 2022 (UTC) == Jawiki has NOT reached consensus on implementing Vector 2022 yet == Jawiki has '''NOT''' reached consensus on implementing Vector 2022 yet. Why was it implemented without our consent? [[User:AppleRingo777|AppleRingo777]] ([[User talk:AppleRingo777|talk]]) 22:01, 29 June 2022 (UTC) :Hi @[[User:AppleRingo777|AppleRingo777]] - we apologize for the confusion that the deployment process has caused and the lack of clarity from our side.  We are currently working on reading back through our previous communications and clarifying the process and what happened with individual members of the community.  We will to get back to the community with more detailed thoughts and a process for next steps by tomorrow July 1st.   [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 12:04, 30 June 2022 (UTC) == [[MediaWiki:Sidebar]] == Hello! I asked a question at the meeting, but I would like to duplicate it here. Will it be possible to control the location of blocks (right or left) through [[MediaWiki:Sidebar]]? [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 15:34, 30 June 2022 (UTC) :Hey! We are still thinking through how this would work. Input valued in [[phab:T306519]] ! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:27, 6 July 2022 (UTC) :: Thanks! :) [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:16, 6 July 2022 (UTC) == Keep the TOC under the main menu as long as possible (Vector 2022) == When the window gets narrower the TOC is moved into a "Hamburger button". But the main menu stays where it is until the window get's quite a bit more narrower. I think as long as the main menu fits, the TOC should stay at its original place. Especially since the TOC behind the "Hamburger button" is quite easy to miss. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:30, 1 July 2022 (UTC) :This was a bug. I believe it should be fixed by the end of the week. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:28, 6 July 2022 (UTC) == "Move" is the only in the "More" drop down menu (Vector 2022) == I think it's quite odd that the "More" drop down menu most of the time contains only "move". Is it on purpose to make it harder to find for the average user? [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:35, 1 July 2022 (UTC) * {{ping|L.xschlag}}, I have two items - the other is an add-on via preferences/gadgets. Unfortunately, I cannot use drop-down menues easily, so getting there in V-2022 is quite a nuisance. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:31, 3 July 2022 (UTC) *:Isn't the behaviour the same here on the other skins? *:I agree it's not great having one item in a menu, but I think this case is quite rare since on most wikis move privilege is added along with page protection and deletion. There is a trade off here between the complexity of maintaining multiple variants of the skin in different circumstances and what looks best. Here we could add special treatment for the one item menu but we'd need to add additional code complexity and tests to cover it. Hope this insight is helpful. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:32, 6 July 2022 (UTC) == Actions menu overflows when main menu is active (Vector 2022) == {{Tracked|T311471}} When the main menu is active (meaning visible) and the window is quite narrow the actions menu (Read, Edit source, Add topic, View history) doesn't get condensed in the "More" drop down menu, resulting in a very ugly overflow. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:41, 1 July 2022 (UTC) :@[[User:L.xschlag|L.xschlag]] - thank you for your feedback! This should now be fixed, let us know if you continue seeing issues. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:34, 11 July 2022 (UTC) == Audio player issues (Vector 2022) == When pressing play from a wikipedia article (e.g. first clip in [[:w:en:Aftermath_(Rolling_Stones_album)]]), the page changes text colour from black to pale grey. Almost unreadable. This dead time varies from a few seconds to many minutes, probably caused by unsteady connection on my side. I tried opening 2-3-4... windows with the same article, and some windows seem to be stuck indefinitely while others play with minimal (but still annoying) delay. If I press play directly from file description page ( [[:w:en:File:Under_My_Thumb.ogg]]), it always plays instantly and the text always stays black. Win 10 Home / Chrome 102.0.5005.115 (64-bit) [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 19:29, 3 July 2022 (UTC) :I've flagged this bug to the developers of [[Extension:TimedMediaHandler]]. This is not related to this project. I'll let you know if I hear anything back. Thanks for reporting! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:43, 11 July 2022 (UTC) == Language mix in the interface == Pardon me if this had already been discussed here. It seems that the language of the interface (as set in preferences) mixes up with local-language elements where it shouldn't. # My preferences are always "interface=en", and thus I always see "Contents Beginning" in the TOC section - be it Chinese, Russian or Spanish wiki. # The pink box above TOC in ru-wiki says "On this Википедия<sup>[sic!]</sup> the language links are at the top of the page across from the article title. Go to top." In zh-wiki, however, the message is correctly "On this Wikipedia the language links ..." [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:23, 3 July 2022 (UTC) :Thank you @[[User:Retired electrician|Retired electrician]] for reporting this. That's odd. 🤔 [[betawiki:MediaWiki:Vector-language-redirect-to-top/en|The source code]] is: <tt><nowiki>On this {{SITENAME}} the language links</nowiki></tt>... - so apparently, something about <nowiki>{{SITENAME}}</nowiki> isn't working here. But I don't know what yet. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:20, 6 July 2022 (UTC) == Where are the categories? == Hi this is my first time looking at the prototype, so apologies if this question has been answered elsewhere - where are the categories? [[User:MassiveEartha|MassiveEartha]] ([[User talk:MassiveEartha|talk]]) 04:15, 5 July 2022 (UTC) :Hello @[[User:MassiveEartha|MassiveEartha]]. I'm sorry that you felt confused. We don't touch elements such as categories. These prototypes were only created for editors to help us decide on the visual design matters. If the categories aren't displayed in any of the prototypes, then it's definitely unintentional and also irrelevant to what we do. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:02, 6 July 2022 (UTC) == 開発者集団は日本語版を軽視していると思われるThe group of developers seems to downplay the Japanese version == 日本語版の利用者の一人としては、開発者の集団は日本語版を軽視していると考える。一つの証拠として開発者からの意見を求めるメッセージが英語だけで書かれていたことを挙げておく。機械翻訳があるのだから英語と共に日本語を添えることは簡単なことのはずである。それすらせずにVectorからVector2022への変更を強行したことは、一種の文化帝国主義であると評さざるを得ない。As one of the users of the Japanese version, I think that the group of developers disregards the Japanese version. One proof is that the message for the developer's opinion was written in English only. Since there is machine translation, it should be easy to add Japanese along with English. It must be said that forcing the change from Vector to Vector 2022 without doing so is a kind of cultural imperialism.--[[Special:Contributions/27.85.205.84|27.85.205.84]] 07:17, 5 July 2022 (UTC) :Hello 27.85.205.84. Do you maybe know good open-source machine translators working for Japanese and English? I've noticed that Google Translate doesn't work for these languages well. Sometimes it changes words, meanings, and the tone of entire sentences completely. I could write in Polish, my first language, but I'm sure that would be even more difficult. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:15, 6 July 2022 (UTC) == Vector 2022を強要する行為は、開発者が読者を軽視していることの証拠である The act of forcing Vector 2022 is evidence that developers are downplaying their readers. == 開発者(の集団)はアカウントユーザーなら自分で好きなスキンを使えるのだから、あまり出来がよいとは言えないVector 2022を強要してっもかまわないと考えているようである。しかし、元々Vector 2022は読者として快適に使えることを考慮していない。開発者(の集団)は読者がいなければいくら記事を作っても意味がないということを忘れているのだろうか。It seems that developers (a group of people) are willing to force Vector 2022, which is not very good, because account users can use their favorite skins. However, originally Vector 2022 did not consider it to be comfortable to use as a reader. Do developers (groups) forget that it doesn't make sense to write an article without a reader?--[[Special:Contributions/27.85.205.84|27.85.205.84]] 07:29, 5 July 2022 (UTC) :Hello! As I can see, the translation was done by Google Translate. It's not good. I've used DeepL and this message is very different in English. Why do you think Vector 2022 was not originally designed to be comfortable to use as a reader? I would like to understand what made you think so. :こんにちは! ご覧のとおり、翻訳はGoogle翻訳によって行われました。 良くない。 私はDeepLを使用しましたが、このメッセージは英語では大きく異なります。 なぜVector2022は、もともとリーダーとして快適に使用できるように設計されていなかったと思いますか? どうしてそう思ったのか理解したい。 [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:06, 12 July 2022 (UTC) :: [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)-san]], your great DeepL-ed message causes a [[:ja:Wikipedia:削除依頼/Wikipedia:井戸端/subj/デスクトップ版外装(スキン)改善バージョンの実装について|deletion discussion]] due to copyright violation. I wish a good Foundation staff would deeply understand the copyright policy in Wikipedia and recognize that copypasting from machine translation could violate the copyright that was attributed to that translation service. :: So, while I'm not the original poster of this section, let me answer the question: :: > Why do you think Vector 2022 was not originally designed to be comfortable to use as a reader? :: If you think the only problem is new Vector 2022 design itself, I must say you are missing an important point: how you all introduced the new skin. All of the changes has never been announced in jawiki before being applied (and unfortunately, after that, until today). Many of the editors, the readers, the users were surprised at the new design all of the sudden, and not a few of them regarded it as a big bug or something. :: You may wonder, "we let you know this in advance, via a member of your community." That's true, partially. [[User:AppleRingo777|AppleRingo777-san]] took your messages and passed them to us per your instruction. I heard that you (or someone in Foundation) asked to post the message in WP:NEWS. How did you determine that WP:NEWS, generally where announcements '''only for the editors''' are posted, was enough to communicate this important news that obviously affected the entirety of community members including the readers? Will you also assign the responsibility on this to AppleRingo777-san, a good community member? I cannot help but want the Foundation to realize that you all destroyed our trust. --[[Special:Contributions/2400:4052:3420:4500:444C:45BF:13AC:59E2|2400:4052:3420:4500:444C:45BF:13AC:59E2]] 14:40, 14 July 2022 (UTC) == Listed coordinates overlapping with header weirdly == {{Tracked|T281974}} for an example of this, see wp's [[:en:London|london]] article ([https://imgur.com/a/rEngM3R screenshot]) [[User:LarstonMarston|LarstonMarston]] ([[User talk:LarstonMarston|talk]]) 20:00, 5 July 2022 (UTC) :Thank you @[[User:LarstonMarston|LarstonMarston]]. In this case, we need to fix the bug together with the communities - some code should be changed by editors on each wiki with this bug separately. We can help (and we're working on it). [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:11, 6 July 2022 (UTC) ::thanks, good to hear [[User:LarstonMarston|LarstonMarston]] ([[User talk:LarstonMarston|talk]]) 20:06, 6 July 2022 (UTC) == Default to Collapsed Menu Exposed TOC == {{Tracked|T287609}} I was trying to figure out why I didn't like the new TOC, and then it hit me that the main reason was that it is hidden by the side menu when you first visit a page (I very rarely login to Wikipedia, and I'm thinking that's the norm for most visitors). Then I was thinking that I almost never use the main navigation links, they just aren't part of my normal use case of visiting Wikipedia (it is to learn a specific thing that I don't currently know enough about). I was going to post to make it possible to hide the main nav, but then realized that you already built it, but the default is for it to show. My hypothesis is that the bulk of users don't look or click on any of the menu items, and that the menu should be hidden by default and the TOC exposed above the fold. [[Special:Contributions/195.134.163.110|195.134.163.110]] 10:34, 6 July 2022 (UTC) :Yes, TOC should be exposed above the article not on the right. In fact in desktop view if I click PC version it does not open stuff on the left. [[Special:Contributions/2A00:1370:8184:2478:A928:87EF:D073:FEEA|2A00:1370:8184:2478:A928:87EF:D073:FEEA]] 16:22, 6 July 2022 (UTC) :Thank you for your feedback! We are planning on implementing this change within the next couple of weeks. Progress can be tracked in the phabricator ticket linked above. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:04, 11 July 2022 (UTC) ::I would like you to give logged-in users the right to choose that as well. If you knew about these plans, don't you think that was a little premature to set Vector (2022) as the default in JAWP ? If you make changes right after you start it in JAWP, Japanese users will be confused. --[[User:呉野|呉野]] ([[User talk:呉野|talk]]) 13:21, 14 July 2022 (UTC) == Replace the "new section" tab text with "+" gadget not working. == {{Fixed}} On the English Wikipedia upon switching to Modern Vector the aforementioned gadget ceases to function as intended. [[User:Nathanielcwm|Nathanielcwm]] ([[User talk:Nathanielcwm|talk]]) 13:14, 6 July 2022 (UTC) :Looks like the gadget is setup to only work on Vector and Monobook. I have updated it to also apply to Vector 2022 skin (https://en.wikipedia.org/w/index.php?title=MediaWiki%3AGadget-addsection-plus.js&type=revision&diff=1096783301&oldid=1047498910) [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 15:59, 6 July 2022 (UTC) == July == @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: Does Vector 2022 will be deployed (as default) at all Wikimedia wikis until the end of July, as it is written [[Reading/Web/Desktop Improvements|here]]? I am asking this because I see that there is still some work to do and the deadline written there changed several times. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 21:56, 6 July 2022 (UTC) :Hello @[[User:NGC 54|NGC 54]], thanks for this question. This information is already outdated. It will ''not'' be deployed in July. We hope to send an update to the village pumps next week. We're working on the announcement right now. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:01, 7 July 2022 (UTC) == Language switching == Hi, I really appreciate the suggestion of translations within the language button, thank you! [[Special:Contributions/37.103.14.65|37.103.14.65]] 09:06, 7 July 2022 (UTC) :Thanks! Appreciation also goes to the [[Wikimedia Language engineering]] team, because they have made this particular change. We have "only" provided the language button :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:01, 12 July 2022 (UTC) == Vector (2022)のウィキペディア日本語版への導入について About the introduction of Vector (2022) to the Japanese version of Wikipedia == 「[[:ja:Wikipedia:井戸端/subj/デスクトップ版外装(スキン)改善バージョンの実装について]]」での案内によると7月14日までこのページでコメントを受け付けるとのことなので意見を書く。--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:25, 8 July 2022 (UTC) * 開発者は開発すること自体に喜びを感じるべきであり、日本語版で行ったように強引に導入して「見えるところ」に成果が表れることに喜びを感じるべきでない。 * 開発者は裏方として、開発に専念するべきであり、それを使うかどうかは「利用者」の判断にゆだねるべきである。 * スキンはインフラストラクチャーである。技術者が陥りがちな間違いだが「新しければよい」というものではない。 * 現在のVector (2022)は完成品とは言えずベータテストの段階でしかない。この段階で全面導入を進めようとするのは技術者の姿勢として適切でない。ベータテストは希望者を募って行うべきである。 * Vector (2022)をデフォルトのスキンとすることについて、本当に開発者チームに権限が与えられているのか。証拠があるなら、リンクをつけて示してほしい。 * 今回の経緯を見ると「読者」に対する観点が脱落している。「読者」のいない記事に何の意味があるのだろうか。 :ja: Wikipedia: Idobata / subj / Desktop version According to the guidance on implementing the improved exterior (skin) version, comments will be accepted on this page until July 14, so I will write my opinion. * Developers should be delighted with the development itself, and should not be delighted with the "visible" results of the forcible introduction as was done in the Japanese version. * Developers should concentrate on development behind the scenes and leave it to the "user" to decide whether or not to use it. * Skins are infrastructure. It's a mistake that engineers tend to make, but it's not "just new." * The current Vector (2022) is not a finished product, it is only in the beta test stage. It is not appropriate as an engineer's attitude to proceed with full-scale introduction at this stage. Beta testing should be done by recruiting applicants. * Is the developer team really empowered to make Vector (2022) the default skin? If you have proof, please link to it. * Looking at the history of this time, the viewpoint for "readers" is missing. What does an article without a "reader" mean? [[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:25, 8 July 2022 (UTC) *:Hi @[[User:匿竜類|匿竜類]] - Thank you for your feedback and for the bug reports below. We are currently in the process of taking the Vector (2022) skin out of beta testing/pilot mode and into the stage where we scale the skin, with the hopes of making it the default on all the wikis. Over the course of the next month, we will be hosting conversations with the largest Wikipedias and getting their feedback on the skin, similar to our conversations with Japanese Wikipedia right now. Even when default, logged-in users will still be able to chose whether they want to use the skin or not. If they decide not to use it, they can turn it off at any moment in their user preferences. *:In terms of readers, for every change we have made when building the skin, we have tested both quantitatively and qualitatively with readers and well as editors. To access more detail on the research and testing we have done, please go [[Reading/Web/Desktop Improvements/Features|to the Features page]] and select the feature you are interested in learning about. From there, you can read the sections named Quantitative research or Qualitative research to see the testing we have done. In addition, we have also done more open-ended testing with readers to identify the issues with the skin starting in 2020 until now. Please see the [[Reading/Web/Desktop Improvements/Repository/Hureo User Research Report/ja|Hureo User Research Report]] with Readers and Editors, the [[Reading/Web/Desktop Improvements/Repository/Wikimania Stockholm research report/ja|Wikimania Stockholm research report]], the [https://nbviewer.org/github/wikimedia-research/Desktop-behavior-analysis-Aug-2019/blob/master/Desktop_usage_behavior_analysis.ipynb Wikimedia Desktop Usage and Behavior Data Analysis], or the [[Reading/Web/Desktop Improvements/Repository/Sticky Header and Table of Contents User Testing/ja|Sticky Header and Table of Contents User Testing]] reports for some examples of the studies we have done with readers (which have translations in Japanese), what we have learned, and how we used those learnings to create the new skin. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:00, 11 July 2022 (UTC) == Vector (2022)の不具合の報告 Report a bug in Vector (2022) == {{Tracked|T303267}} {{Tracked|T281974}} 日本語版でVector (2022)を使うと、左側に「このWikipediaでは言語間リンクがページの先頭にある記事タイトルの向かい側に設置されています。ページの先頭をご覧ください。」と表示されるのだが、実際には「記事タイトル」は「ページの先頭」ではなくこのメッセージの下に表示される。以前は、このようなことがなかったように思うので一時的なものかもしれないが、症状が出ていることを確認してほしい。When I use Vector (2022) in the Japanese version, it says "In this Wikipedia, the interlingual link is located opposite the article title at the top of the page. Please see the top of the page." However, in reality, the "article title" is displayed below this message instead of "at the top of the page". I don't think this happened before, so it may be temporary, but please make sure that you have symptoms.--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:42, 8 July 2022 (UTC) :上記不具合を報告してから、1日経過していますが、応答がありません。[[:ja:Wikipedia:表示改善依頼#Vector(2022)スキンで、バッジと地図のタグが重なって表示される#]]によると、どうやらこの種の不具合はファブリケータで処理することになっているようですが、そちらの方への連絡はしていただけたのでしょうか。とりあえず担当者の応答を求めます。One day has passed since I reported the above problem, but there is no response. ja: Wikipedia: Display improvement request #Vector (2022) In the skin, the badge and the map tag are displayed overlapping. According to #, it seems that this kind of defect is to be handled by the fabricator. Could you contact that person? For the time being, ask for the response of the person in charge.--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 03:05, 9 July 2022 (UTC) ::Hello! The coordinates issue is known but the language one wasn't. Thank you for bringing it to our attention. ::I will reply with more details next week. Have a great weekend and thank you for the bug reports. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 18:27, 9 July 2022 (UTC) :::These are tracked in [[phab:T303267]] and [[phab:T281974]]. Thanks for the report! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:39, 11 July 2022 (UTC) == Merge [ca-view] and [ca-nstab-main] in the article toolbar == Currently, in the article toolbar, we have two links (Read and Article) that lead to the same location. One of them is located in the left and the other one is located in the right navigation. This can be confusing to readers, and also adds unnecessary weight to the toolbar. [https://imgur.com/56mbihi Current look]. It would be good if we could merge these two tabs into one. Ideally, the best solution, in my opinion, would be to merge the right and left navigation and center the items, [https://imgur.com/a/ih52zYZ like this]. Please tell me what you think about this. Thank you! — [[User:Aca|Aca]] ([[User talk:Aca|talk]]) 11:18, 9 July 2022 (UTC) :{{O}}. Now, the tabs are clear. You have 2 pages: the article and the talk page. You can select 1 action at a time for each of them: reading, visual editing, source editing, and viewing the history. Form the proposed design, you can understand that the tabs led to different types of pages. The watch is something not related to the article? And if now you are on article tabs, if you would press on the editing source tab, you would arrive on a page not related to the article (this is a possible confusion)? And so on. "This can be confusing to readers," - how so? Are there any data? And if there are, are there any data that the proposed design is better? P.S. I also dislike the proposed design, due to visual reasons. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:00, 9 July 2022 (UTC) == Big blank space when on a big zoom == Unlike the old layout that adjust depending of the size of zoom, the new format seems to follow a single size that, when zoomed in, creates a big blank space like if the page was still loading It needs be fixed so the wiki pages can be better for people that have vison issues - [[:en:User:Meganinja202|User:Meganinja202]] | [[:en:User_talk:Meganinja202|¿]] 10:17:00 11 July 2022 (UTC) [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 10:17, 11 July 2022 (UTC) :[[User:Meganinja202]] are you taking about [[Reading/Web/Desktop_Improvements/Features/Limiting_content_width]] or reporting a bug? If the latter, what browser and device are you using? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:34, 11 July 2022 (UTC) ::i think should be a bug since its a thing that happens from top to bottom of the page and not from the sides, i am use Chromium Based MS Edge [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 17:02, 11 July 2022 (UTC) == Language box recommendation == A minor suggestion: why not insert the language box on the title header so I don't have to go all up to the top of the page to change language versions. So yeah, thanks! [[User:PeaceSeekers|PeaceSeekers]] ([[User talk:PeaceSeekers|talk]]) 11:00, 11 July 2022 (UTC) :ya, they should had kept the language bar on the side of page instead of the top, leaving the language option on top only on mobile/touch machines [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 17:03, 11 July 2022 (UTC) :@[[User:PeaceSeekers|PeaceSeekers]] - do you use the site while logged-in? If so, you can access the language switching button from the persistent ("sticky") header at the top of the page while you're scrolling. We are also in discussion of bringing this functionality to all logged-in users as well. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 08:15, 12 July 2022 (UTC) ::I did log in, but I can't see it though ... what I have is only, from the left: the search button, article title, discussion page, edit history, watchlist and my profile stuff (for lack of better words). So that's that. [[User:PeaceSeekers|PeaceSeekers]] ([[User talk:PeaceSeekers|talk]]) 08:43, 12 July 2022 (UTC) == What I still would love to see different solutions to == I'm very much looking forward to not having the text fill an entire wide screen. This will make Wikipedia far easier to read on big screens. Thanks! A few things that still don't work for me: '''Table of contents''' If I haven't collapsed the left menu, the ToC is not visible when I start reading the article. This makes it more difficult to get an overview. It's also ''generally'' more difficult to get an overview of the article content, as I need to go to the ToC in the sidebar and scroll down to see everything on big pages (like a Village Pump). This both makes it more difficult for me to conceptualize what's on the page – as I've tested this, I've realised I find it challenging to get a grasp of a page if I can't see the various topics at the same time – and adds more work, as I have to move the mouse pointer to the ToC to be able to scroll. I would have much preferred if it used more of the space available to get around this. '''My contributions''' My own user contributions is something I use all the time – it's my way of getting back to what I was doing before. Making it less accessible in the top menu is wrench thrown into my workflow. '''Language links''' This is my main issue. I use other languages ''all the time''. As a reader, I glance at them to conceptualise the topic – which languages have written about this subject? This hints at things that aren't available in the content itself. As an editor, I check out other languages to see what sources they have and so on. Having to click to even see if there are languages I can read is an extra step that both requires more work, but also makes it less inviting, as the opportunity doesn't stare me in the face. This is so central to my workflow that it might in itself be reason to keep using Vector 2010, but that's certainly not my preferred solution. [[User:Julle|Julle]] ([[User talk:Julle|talk]]) 10:13, 12 July 2022 (UTC) == feedback == asbra med maxbredd! coolt att wikipedia tar steget in i 2010-talet och blir läsbart på stor skärm. språklänkarna blir mycket sämre. man borde kunna se språken direkt och klicka på dem, det är en sak man använder hela tiden. jag förstår inte varför ni har bytt ut texten i användarmenyn mot symboler? det var tydligare med text. nu måste man gissa vad de betyder och många kommer aldrig lista ut det. man borde inte behöva skrolla INNE I innehållsförteckningen för att se hela. sjukt störande att behöva gå till den och skrolla I DEN för att se vad som finns på sidan. [[Special:Contributions/81.92.27.129|81.92.27.129]] 18:12, 12 July 2022 (UTC) :Thanks for the feedback! :(google translation) :* max width: cool that wikipedia takes the step into the 2010s and becomes readable on the big screen. :* language links: you should be able to see the languages ​​directly and click on them, it is one thing you use all the time. :* Icons: I do not understand why you have replaced the text in the user menu with symbols? it was clearer with text. now you have to guess what they mean and many will never figure it out. :* Table of contents: you should not have to scroll INSIDE the table of contents to see the whole thing. Very annoying to have to go to it and scroll IN IT to see what's on the page. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 19:00, 12 July 2022 (UTC) :::("Sjukt störande", which the machine translation rendered as "ill disturbing", means "very annoying".) [[User:Julle|Julle]] ([[User talk:Julle|talk]]) 00:15, 13 July 2022 (UTC) == More TOC concerns == On pages with long headings (f.i. [[Wikipedia:Closure_requests]]), the new TOC is highly impractical. The headings are difficult to parse, sometimes cutting words in two. A lot of scrolling is also required to get an overview of what discussions to close. Will it be possible to go back to the old TOC on a per-page base? I can imagine a lot of non-article pages will have similar problems (including this one). Less importantly, I noticed that the default is having only the top heading displayed. In some pages / articles there are very few top-level headings, and this would always require the reader to uncollapse. Can this be made more dynamic? [[User:Femke|Femke]] ([[User talk:Femke|talk]]) 18:09, 14 July 2022 (UTC) :Would it be possible (probably only on bigger screens) to use the empty white space on the right for tools (for logged-in editors), so that the TOC is less cramped? Solves two problems in one. [[User:Femke|Femke]] ([[User talk:Femke|talk]]) 17:00, 18 July 2022 (UTC) == incorrect translation Vector 2022(jpwiki) == The information text on where to switch languages is partially translated incorrectly. I think , "このWikipediaでは言語間リンクがページの先頭にある記事タイトルの向かい側に設置されています。" is a slightly mistaken translation. This may mean that the language switch is outside the display. You probably meant to write that, "他言語版へのリンクは、ページ先頭の記事タイトルの右側にあります。". But I would rather you don't adopt this with no check. [[User:呉野|呉野]] ([[User talk:呉野|talk]]) 10:01, 15 July 2022 (UTC) == 'Talk' and 'Contributions' buttons shouldn't be hidden in the navigation bar's drop down menu. == We shouldn't have to click twice to get to our '''Talk''' and '''Contribution''' pages from the navigation bar. I mean, there's already a bunch of wasted white space to right of the search box and to the the left of our Userpage button for those two icons to be added in the nav bar without any problems. [[User:Some1|Some1]] ([[User talk:Some1|talk]]) 02:57, 17 July 2022 (UTC) == Simple English sidebar == I notice in Simple English with the 2022 Vector, the menus on the left side of the page are to the left of the page text as they should be, but they are far above rather than beside the text. [[User:Jim.henderson|Jim.henderson]] ([[User talk:Jim.henderson|talk]]) 05:47, 17 July 2022 (UTC) == The new sidebar TOC is confusive, not intuitive, unusable == I strongly oppose the new sidebar TOC. It is extremely confusing, not intuitive, and unusable. The removal of the numbering for paragraphs and their transformation into collapsible lists, will make the articles and discussions unreadable, as their structure will be completely unclear. The TOC at the top of the article right below the lead text was perfect for giving a clear impression of the article's structure and for exploring its contents. I think that keeping both the old and the new TOC (if the latter is really necessary) would be a good solution. The new TOC proves useful only in the bottom sections of very long articles. [[Special:Contributions/2001:B07:A2A:1884:D5D:3606:C70C:5366|2001:B07:A2A:1884:D5D:3606:C70C:5366]] 14:03, 17 July 2022 (UTC) == This gives me depression == By merely see this happen week-by-week, I can see this sacred project gradually being destroyed. I wish I could stop this. – [[User:Ilovemydoodle2|Ilovemydoodle2]] ([[User talk:Ilovemydoodle2|talk]]) 07:35, 18 July 2022 (UTC) == wrong name for a language == someone is having a laugh, or got really confused about translation. In the main page https://www.wikipedia.org/, '''Français''' now appears as '''anglais''', both in the top 'wheel' and in the 'Read Wikipedia in your language' drop-down. This is very wrong. What other languages have been disappeared in this way ? a bit of QA would go a long way :-) [[Special:Contributions/92.16.98.145|92.16.98.145]] 16:23, 19 July 2022 (UTC) :Thanks for letting us know! This looks like a mistake/error on translatewiki.net. We'll try to fix that immediately. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 18:28, 19 July 2022 (UTC) ::FYI this wasn't related to the project. ::See related Reddit thread for details on what happened here if you are curious: https://www.reddit.com/r/wikipedia/comments/w2iidz/why_anglais_did_someone_sabotage_it/ [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 20:03, 20 July 2022 (UTC) == coordinates being weird (again) == there was an issue a little while ago where location coordinates in an article would overlap with the header. that's fixed now, but some icons are still uncomfortably close to them, like the FA star; for an example of this, see the english wiki's [[:en:India|India]] article ([https://imgur.com/a/uuXPMzk screenshot]) [[Special:Contributions/2600:1700:7AA1:2400:9CA1:1220:42FD:1F12|2600:1700:7AA1:2400:9CA1:1220:42FD:1F12]] 20:17, 20 July 2022 (UTC) == General concerns! == Well I was part of the process for quite some time now. And up until the move of the TOC from inside the content to the sidebar it was okay with me. I had some minor things, I thought I will get used to: the white space (anyone wanting that, can narrow their window), some inconsistencies (compare [[#A few more issues with the Page header vs Sticky header icons]]), the language switcher, which I fear will leave the impression of reading ''the same'' thing in different languages (compare [[Talk:Reading/Web/Desktop_Improvements/Archive3#Language_Selector_misunderstandable]], as a side-note: nothing happened here, at least nothing I recognized). But today I got this message: [[Topic:Wsfx4tbwzkgamaek]] asking for a translation for [[Reading/Web/Desktop_Improvements/Updates/2022-07_for_the_largest_wikis]]. Let me cite: *'''"...before discussing the change itself"''' *'''"...that allows for a way to identify the needs of the community from the new skin."''' *'''"We would love to see the Vector 2022 skin [...] become the new default across all wikis..."''' *'''"We will be ready to begin making the change at the end of August (and not in July, as previously announced), when the ''visual refinements'' and other ''deployment blockers'' are ready."''' *'''"The goal for that discussion will be to identify breaking issues or opportunities for improvement for the new skin. It will be important for us to reduce the risk of bugs or imperfections that would be particularly troublesome on [insert your language] Wikipedia"''' All that reads like: Well, we're just talking, let's see, what needs to be done, that everyone is happy. There are some things that need to be done anyways. Now let's read those two cites: *'''"...difficult discussions about the launch as the default"''' (compare [[Topic:Wsfx4tbwzkgamaek]]) *'''"...until our improvements are default on all wikis in July 2022."''' (compare [[Reading/Web/Desktop_Improvements]] So isn't this not just a request for bug reports instead of a "discussion"? Is this not more of a fear of "Flak" instead of "needs of the community"? Isn't it happening anyways, instead of you "loving to see it"? What about all the other projects, wikibooks for example ("[insert your language] Wikipedia")? I understand, you do the work, you decide. '''But:''' * Is it wise to "discuss" while there are still tasks to be done and decisions to be made? (compare [[Reading/Web/Desktop_Improvements/Features/Visual_Refinements]], which by the way doesn't even seem finished, and for example [[#MediaWiki:Sidebar]]) * Is the Date of the end of August (6 weeks) really feasible? Who will translate all the feedback that will come in german? * Is it good to leave the impression, that communities will have a choice (compare [[#Jawiki has NOT reached consensus on implementing Vector 2022 yet]])? Some suggestions, if I may: # Why not try to slow the process down? Why the haste? One could remove the deadlines and refine everything. ''Then'' ask the communities for bug reports. # Why not try some marketing "tricks"? I think the discussion about the white space clearly shows that desktop ''improvements'' are highly subjective. Why not use for example ''skin changes''? Another Option could be deploying Vector 2022 only for not logged in users and hence prolong/smooth the transition-process creating time for bug reports and discussions. Most of anonymous usage would probably not care for the change, as long as the content is there. On another plus-side it will create "data" on how the menu-usage changes and community-links are perceived. It will probably even create data on how many logged in users switch to the new layout deliberately and or switch back hence providing "hard" success-data. # Would it be that bad to really leave the community a choice? # If you are relying on volunteers, grant them a little more slack. Bug reports from the community need time: Bugs need to be recognized as bugs, they need to be reported, triaged ''and'' handled. Is this possible in 6 weeks? Volunteers might have another life, a job, kids, a week might be pretty short notice. Phabricator-use is not that trivial. # Let's talk or try, if the new design might eventually be a problem for recruiting new volunteers. Did anyone think about a possible impact of hiding ''community-links'' in collapsed menus? Nobody seems to talk about community-pages or discussion-pages or even other project-scopes. Is the new menu-structure as fitting for these as for wikipedia-articles? I'm deeply saddened. The new TOC will make my life within wikimedia really hard and I commented about that early on (compare [[Reading/Web/Desktop_Improvements/Third_prototype_testing/Feedback#Benutzername:HirnSpuk|here, bullet 7]]). I think all the TOC-comments on this page (see above) should raise at least some concern. And last but not least, I'm deeply troubled, that the new language-links will do more harm, than good. So, ping @[[User:OVasileva (WMF)|OVasileva (WMF)]] and @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], my sincere apology, I don't mean to be rude or mean and I appreciate your work and the work of your colleagues. But I don't want to volunteer for the translation-request, because all of the above mentioned problems. Regards [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 22:25, 20 July 2022 (UTC) :Hello @[[User:HirnSpuk|HirnSpuk]]. Thank you for your outstanding involvement, and appreciation for our work. I'm glad to see that. Also, thank you for your sincere, thoughtful, and thorough comment with all the links and quotes. I think I understand what your approach is, I'm happy that you're saying this. :Before I answer the questions, I'll admit/confirm that: :# The ToC work hasn't been finished yet. So haven't the visual refinements. There's a list of issues labelled as "[[phab:T309972|deployment blockers]]", by which we mean issues we need to solve before making it the default everywhere. I hope this will make you less sad! :# Bug reports do need time. Phabricator is not that trivial. :# While indeed focusing on the most typical use cases, like interacting with articles. :# In some discussions, it has been confusing what exactly is for the individual communities to choose between. :Regarding the questions, my answers to the easiest part: :# We've been working since 2019, most work is behind us and we're headed towards the end. Now, we need to make sure what else the largest communities may need. :# What about all the other projects - the message I asked if you could translate is dedicated to the largest communities of the top language versions of Wikipedia. :# This is why in that message, we're initiating a pre-discussion about culture of collaboration. After that, we'll ask for bug reports and other technical requests. :# We use the name Desktop Improvements because the point is to make changes that are actual measured improvements. Only some of the visual refinements are really subjective. But regarding the feature changes, the idea for each of these is that it should be an improvement compared to Legacy Vector. :# We're part of [[Core Experiences]] and work closely with the teams focusing on newbies and more experienced editors. It's our plan to make entry points for new volunteers prominent, in collaboration with Growth. We hope that Desktop Improvements will be an introduction to even more sophisticated changes addressing very specific use cases. :OK, enough now for one comment. Let's keep talking, though. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 01:30, 21 July 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], because you said "let's keep talking", let me react to your latter 5 points. ::# I do not want to diminish in any way the work you (plural) have done since 2019 and I think the plan is good. But I'm convinced, that the timing is not right. "The end of August" I find far to soon if you "need to make sure what else the largest communities may need." ::# I wasn't able to find the "we talk to the «big guys» first"-idea anywhere. The only thing I find is "We would like our improvements to be default on all wikis in August/September 2022." There will probably not be time to talk to the «small guys». And in addition, the text to translate suggest, that there is a choice, and you'd like to "talk". My impression is you want to ask: how can we best ask for bug reports. That might (and probably will) work, but I don't want to be part of exactly this approach. ::# same as first and second. ::# How is the improvement measured? Is there any "hard data" anywhere? Everything needs more clicks hence more time. It "looks" a little better and modern, which I also find necessary and good. But what is actually "improved"? ::#*I need more scrolling for the TOC, ::#* I will need more work (and creative ideas btw) for rework of community-pages that rely on the "old" version of the TOC at the moment, and even worse, I need to check the visual appearance and usability of pages in even more configurations (to mobile and desktop and VE and source, now I need to add different skins), ::#* I need more clicks for almost anything (if menus are hidden, but this is nearly imperative, to get at least some use out of the new ToC), ::#* I'm deeply troubled about the "impression" some changes might make (which hence wouldn't be an improvement either and which is by default not measurable)... ::#* What about the visually impaired? Is it an improvement for them too, any hard data? ::#:Please, feel free to elaborate. I know it would be baloney to change the name in the last 6 weeks of the work. My point is not to do that, but to take a step back, review what's done so far, and if the decision will be made to prolong the process a really long time, then ''maybe'' one ''might'' think about a change, and if it's only to get less of the "if you do this I'll be done with wiki..."-criticism that's just consuming time for everyone. ::# I'm not addressing technical issues. It's the possible "hiding" of prominent community-links in the sidebar by using elaborate restructuring and collapsing mechanisms. On that the single communities won't have influence as far as I see it at the moment. ::PS: I appreciate trying to cheer me up ("make you less sad"), but my sadness stems from the uncertainty how this will all work out. In the end the prototype is only a prototype. And how much work in the community must be done afterwards to facilitate the "improvements" is also not clear. The main point being, that I struggle with checking and cross-checking functionalities in different systems. It was okay until the move of the ToC. But as long as there is still work to be done, I can't even think about workarounds for not having the ToC where and how I was used to it. ::Regards [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 07:34, 21 July 2022 (UTC) :::Hey @[[user:HirnSpuk|HirnSpuk]], thank you for your continued feedback. It's been super helpful. We've rewritten our message to German-language Wikipedia based on your thoughts and the learnings we've gotten through similar conversations on other wikis. We're going to post our next draft for translation this week - let us know what you think of it! We're open to suggestions. Your continued thoughts are much appreciated! :::In terms of your individual questions: :::# The timing is not right :::#* We really do believe that our changes are improvements already! We're eager to bring them to readers and editors. As you have pointed out, we've been building these for three years. We've received feedback from German-language Wikipedians, and many other communities. As you also know, we've performed prototype testing with editors across 30+ languages, and different types of quantitative testing on each feature. Many significant requests have already been discussed. :::#* The main reason we want to have this conversation now (while we're putting the finishing touches, like the visual refinements and changes to the table of contents) is that we'd like to see if any of the feedback might change what those finishing touches are. We'd also feel more confident with our plan once we know what the additional work we need to do is, if any. :::#* The process we're envisioning is to collect bugs and requests, and triage these into three categories: (1) the ones that must be done before the deployment, (2) the ones that can wait until after the deployment, and (3) the ones that we don't think are a priority. Our goal for the conversation with the communities is to establish what lies in each bucket such that the communities are comfortable with changing the default. :::#* We understand if a conversation might take longer on a given community, and do not plan on cutting any discussion short just to reach a deadline. We made a mistake with Japanese Wikipedia and made the change prior to acknowledging a common process. We'd like to avoid that mistake with the other wikis, hence the lengthier discussion with German-language Wikipedia. :::# The "we talk to the «big guys» first"-idea :::#* We try to take the approach of equity. We have conversations across the top 25 Wikipedias by size. We've attended a [[m:Wikisource Triage meetings|Wikisource Triage meeting]] and two [[m:SWAN|SWAN]] meetings. The set of pilot wikis is diverse. We inform the big and small communities about our office hours using different channels, incl. MassMessages, Tech News, Discord, Telegram, Facebook. We're going to have the interpretation support in the top UN languages. :::# How is the improvement measured? :::#* Thank you for pointing this out. This very crucial piece was missing. We'll be adding a summary of our findings to our future messages. :::#* You'll find the short answer [[:w:Wikipedia:Village_pump_(proposals)#UX_research_and_usability_testing|on the English Wikipedia Village Pump page]], quite paradoxically brought to everyone's attention using the "hidden" template. For details on any individual feature, go to the “features” section of our documentation, select the feature you are interested in, and review the qualitative and quantitative sections. :::# It's the possible "hiding" of prominent community-links in the sidebar by using elaborate restructuring and collapsing mechanisms. On that the single communities won't have influence as far as I see it at the moment. :::#* This is a great question. So far, our interviews with users have shown that newcomers are NOT more likely to begin contributing based on the number (or even presence) of community links. In fact, having so many options at hand made them feel unwelcomed to the interface as they didn't instinctively know where the links would lead, and thus, felt intimidated or lost. :::#* We think a better method is to have fewer links that are clearer to understand and pave more intuitive ways. These links are, among others, edit or history. We are working with the Growth and Editing teams to identify how we can increase the understanding of these links for readers and newcomers - both so they will know where the content they are reading is coming from, but also as a means of introducing them to contribution. See also: [[Core Experiences]]. :::# What about the visually impaired? Is it an improvement for them too, any hard data? :::#* We've been doing accessibility testings with the American Foundation for the Blind. You'll find more information in this task: [[phab:T310033|T310033]]. Generally though, part of this work goes beyond Desktop Improvements, and is done by our designers who build basic user interface elements for all the teams. :::Hey, on a side note, have you ever attended our office hours? I (Szymon) don't recall this. You'd have heard answers to some similar questions if you had joined us earlier. Anyway, feel invited. :::[[user:OVasileva (WMF)|OVasileva (WMF)]], [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:44, 29 July 2022 (UTC) ==Sorry but user expereince is kind of awful== Okay. I've given "Vector 2022" a shot for a while and it is just confusing and difficult to use. Too much animation-style issues. Too much whitespace. Difficult discovery of functions. Difficult to obtain a feeling of confidence in mastery. If I would have been keeping a log, I'd have dozens of gripes by now. I don't wish to waste time enumerating specific things because it's besides the point because the entire experience is bad. I can't hack it anymore. I thought I'd get used to it but I'm going back to Vector 2010. Keep things simple. Keep it static. I know many people but a lot of work into this and it was a valid attempt but it just didn't suceed in improving over Vector 2010. [[User:Jason Quinn|Jason Quinn]] ([[User talk:Jason Quinn|talk]]) 02:24, 26 July 2022 (UTC) == External link icon == The external link icon currently deployed on mediawiki.org looks horrible. What happened? The icon shown at [[phab:T261391]] in the "After" screenshot looks much better. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:55, 26 July 2022 (UTC) :@[[User:NGC 54|NGC 54]], what's the difference you're referring to? Could you maybe share a screenshot? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:36, 26 July 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: Here. ::[[File:Vector2022 Broken External Link Icon.png|thumb|The icon looks thin and pixeled. Not like at Phabricator.]] --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:48, 27 July 2022 (UTC) :::I saw that the issue was already reported. Compare [https://phab.wmfusercontent.org/file/data/zm2w6tyla7ap4pm54oxw/PHID-FILE-jxp2g6oxik24v6zcst5o/image.png this] with [https://phab.wmfusercontent.org/file/data/6tvujxqmvz53tlojn4qi/PHID-FILE-gq23v5redy2o4ki63rnq/Screen_Shot_2022-07-21_at_11.46.24_AM.png this]. Also, for me it looks like the arrow is misshaped. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:53, 27 July 2022 (UTC) ::::Hi @[[User:NGC 54|NGC 54]] - thanks for your report. The icon is indeed broken as of right now. We're looking into this right now and hope to have a fix later this week or early next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 12:05, 28 July 2022 (UTC) dggcfrr4kddq6egg7oxegogmc6tlrg9 5387753 5387558 2022-07-29T08:16:18Z Retired electrician 494965 /* The new sidebar TOC is confusive, not intuitive, unusable */ wikitext text/x-wiki {{Reading/Web/Desktop Improvements/Header}} {{WMF present |1=SGrabarczuk (WMF)|timezone_1=UTC+1/2|lang_1=pl, en, fr|photo_1=Wikispotkanie-warszawa-2021-07-03-rd-26.jpg |2=OVasileva (WMF)|timezone_2=UTC+1/2|lang_2=en, es, bg|photo_2=Vasileva, Olga January 2017.jpg }} {{Archive box| *[[Talk:Reading/Web/Desktop Improvements/Archive1|Archive1 (before the 1st batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive2|Archive2 (before the 2nd batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive3|Archive3 (before the 3nd batch of deployments)]] *[[Talk:Reading/Web/Desktop Improvements/Archive4|Archive4]] *[[Talk:Reading/Web/Desktop Improvements|Current discussion]] }} {{Reading/Web/Desktop Improvements/Talk page intro}} __TOC__ == Where is the TOC? == People here are complaining about it. I don't even get one! [[User:Betaneptune|Betaneptune]] ([[User talk:Betaneptune|talk]]) 17:38, 25 May 2022 (UTC) :Hello @[[User:Betaneptune|Betaneptune]]. Do you still have this problem? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:52, 8 June 2022 (UTC) ::Hi ! I have the same problem on the French version of Wikipedia. The TOC just disappeared. The problem appears in Firefox desktop (last version 101.0.1), even in "troubleshoot" mode with all my add-ons deactivated. However, the problem does not appear in Chrome. This is extremely confusing. I reported it on some discussion page on the french version of WP, but I also mention it here, as I'm not sure at all where to report the problem for it to be taken into account. [[Special:Contributions/85.169.195.108|85.169.195.108]] 17:56, 26 June 2022 (UTC) : The TOC is now on the left side, but after other menu lists. It should probably come first. But to keep things accessible, the (hidden) "jump to main menu" link should be kept as first element of course. [[User:Psychoslave|Psychoslave]] ([[User talk:Psychoslave|talk]]) 15:00, 5 July 2022 (UTC) ::Agreed. The TOC ''really'' should come first. The {{mono|#mw-navigation}} menu (which currently appears first) is comprised of mostly ancillary links unrelated to the page's content, many of which are rarely used (e.g., ''"Download as PDF"'', ''"Create a book"'', ''"Permanent link"'', etc). [[User:OmenBreeze|OmenBreeze]] ([[User talk:OmenBreeze|talk]]) 00:17, 6 July 2022 (UTC) :::{{ping|85.169.195.108}} It has been tracked here [[phab:T312022]].--[[Special:Contributions/37.103.14.65|37.103.14.65]] 09:03, 7 July 2022 (UTC) ::::Suggestions: ::::* ''If'' the TOC will ''not'' come first, the other menu lists on the left side should become hidden (collapsed) when there is a TOC below them, so that the TOC is always visible. ::::* The TOC should always be shown in its entirety, and not displayed as a box that you have to scroll through. ::::[[User:Förbätterlig|Förbätterlig]] ([[User talk:Förbätterlig|talk]]) 14:03, 12 July 2022 (UTC) == Too narrow (again) == Why waste all that space? I have a nice wide screen so I want to take advantage of it. Those who want to have it narrow can just reduce their window sizes? Overall, not a great look. Not exciting. Quite boring.--[[User:Xania|Xania]] ([[User talk:Xania|talk]]) 11:23, 22 December 2021 (UTC) :Hello @[[User:Xania|Xania]], you can read about our [[Reading/Web/Desktop_Improvements/Features/Limiting_content_width#Goals_and_motivation|goals and motivation]] for limiting the width. Also, we are working on a solution to use the empty space. Could you take a look at [[Reading/Web/Desktop Improvements/Fourth prototype testing/it|our fourth prototype]] and write more on what you think about arranging the space as it is presented there? Thank you in advance! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 14:59, 26 April 2022 (UTC) :: Oh my dear God, why don't you give an option to unrestrict the width?? It's beyond ridiculous how absolutely tiny is the page content on my monitor horizontally! I have to scroll all the time to read! Don't ruin Wikipedia the same way Fandom was ruined! [[Special:Contributions/90.188.46.13|90.188.46.13]] 04:38, 13 May 2022 (UTC) :::We have given this option. This can be done with the [[:en:User:Jdlrobson/vector-max-width-toggle.js|gadget one of our engineers made]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 03:39, 14 May 2022 (UTC) ::::Thanks, but maybe we should have an easy plug-in system for ordinary users or, at least, the instructions how to apply it and a place where to find those customisations. By default it is really narrow to read and it feels like a news site rather than an encyclopedia article. [[User:Krnl0138|Krnl0138]] ([[User talk:Krnl0138|talk]]) 09:55, 15 May 2022 (UTC) :::::I agree, the toggle option should be there by default! By the way, that script does not work well currently, so I [[:en:User:Arthurfragoso/vector-max-width-toggle.js|updated it here]]. — [[User:Arthurfragoso|Arthurfragoso]] ([[User talk:Arthurfragoso|talk]]) 13:28, 21 May 2022 (UTC) ::I don't understand why you are still pushing on us that bad design choice. It still is time to pull the plug and start to work on a plain page design. You are convincing no one here. Please, please, really, please stop this nonsense. Forcing bad choices on your users because you are the only product on the market is never a good thing. ::Since it has been forced without asking anyone on the French Wikipedia I had to register just to come back to the normal and good design. That's something, as a simple reader, I should never have had to do in the first place. ::So one last time, please come back to reason and stop hurting your user base foolishly. [[User:DerpFox|DerpFox]] ([[User talk:DerpFox|talk]]) 21:33, 13 May 2022 (UTC) :::Hello @[[User:DerpFox|DerpFox]], thanks for your comment. Have you maybe followed the links I've shared in my answer to Xania? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 03:42, 14 May 2022 (UTC) ::The lines in the fourth prototype seem to be slightly wider to me on 1080p display than in the current version of 2022 vector design, but those empty strips on the sides, each of which are almost the size of the old navigation mv-panel, constantly remind about the space wasted. ::If the only reason of this thinning is the recommended line lengths in symbols and you want to keep it for any price, I would suggest using a dynamic font size, so, for example, starting from some resolution the symbols just grow larger. This might also reduce the eye strain connected to focusing on the small text. ::[[User:Kageneko|Kageneko]] ([[User talk:Kageneko|talk]]) 13:51, 17 May 2022 (UTC) ::I had a browse over the reasons for the change, but I still don't like or agree with the main justification more or less boiling down to "everyone else is doing it so we should too". Even in the linked examples, the page still feels a lot more "full" despite having a dedicated deadspace on the site, due to the way the page has been very carefully designed in a mixture of different kinds of block contents (images, text interactive eliments, etc). ::Accepted Webpage standards used to be against having blank, unused and waisted deadspace, but at some point in the last 10 years there seems to have been a weird shift to the opposite where deadspace is all the rage, though it's not one I've personally ever liked or agreed with. ::While I'm sure there are good uses of limiting page width, I'm not sure if Wikipedia, being a site that is mainly made up of text would really benefit from it as it's likely just going to squash pages and increase the amount of vertical scrolling required to navigate. [[User:Dave247|Dave247]] ([[User talk:Dave247|talk]]) 07:32, 18 May 2022 (UTC) ::Yeah it's too narrow otherwise. the look is very nice, it's not boring as you tell. [[User:Crater bug|Crater bug]] ([[User talk:Crater bug|talk]]) 15:28, 28 May 2022 (UTC) :I totally agree! I dislike the vector skin because how small it is. [[User:OverAWallOfMetaKnight|OverAWallOfMetaKnight]] ([[User talk:OverAWallOfMetaKnight|talk]]) 15:55, 15 May 2022 (UTC) :Agreed. I use a 3440x1440 screen (usually with a tiled layout), and this new layout forces all the content to occupy a comically narrow strip, instead of allowing me to choose the width myself. [[User:Emptyflask|Emptyflask]] ([[User talk:Emptyflask|talk]]) 13:47, 17 May 2022 (UTC) :I agree, there is simply too much space wasted that could be used for more article space and a button specifically for those who want to edit wikipedia [[User:Techny3000|Techny3000]] ([[User talk:Techny3000|talk]]) 02:52, 28 May 2022 (UTC) :hard to read I'm glad I stayed the same as before No changes required [[Special:Contributions/240B:11:E7E0:5E00:6005:3399:E6C:2B48|240B:11:E7E0:5E00:6005:3399:E6C:2B48]] 14:06, 2 July 2022 (UTC) :Strongly agree. I want to decide the readable width for me. In the old skin and most websites, I can do it by adjusting the width of window. I definitely don't want to care about "CORRECT READABLE WIDTH FOR EVERYONE" decided by someone somewhere, even if they are great scholars. [[User:Kyoku|Kyoku]] ([[User talk:Kyoku|talk]]) 08:32, 10 July 2022 (UTC) After reviewing the posted defense of the narrowing and the feedback listed here, this feature belongs entirely as an optional setting. It most certainly should not be the website's default. [[User:RightQuark|RightQuark]] ([[User talk:RightQuark|talk]]) 01:29, 24 May 2022 (UTC) :The defence of the narrowing seems to have little real-world bonuses. It may be theoretically good but makes it bad to read because Wikipedia articles can be long [[User:Torqueing|Torqueing]] ([[User talk:Torqueing|talk]]) 17:10, 24 May 2022 (UTC) I'm fine with the text being narrow but the ui and nav bar should be full width. --[[User:Thedonquixotic|Thedonquixotic]] ([[User talk:Thedonquixotic|talk]]) 00:18, 26 May 2022 (UTC) :@[[User:Thedonquixotic|Thedonquixotic]], what do you mean by the ui and nav bar? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:54, 8 June 2022 (UTC) ::Not sure what is unclear here. I mean the navbar. As in the bar up at the top of the page with use account, search etc. [[User:Thedonquixotic|Thedonquixotic]] ([[User talk:Thedonquixotic|talk]]) 19:07, 1 July 2022 (UTC) I also have a wide screen monitor. I do not like this forced width shrinkage in the Vector 2022 skin. [[User:OhanaUnited|<b><font color="#0000FF">OhanaUnited</font></b>]][[User talk:OhanaUnited|<b><font color="green"><sup>Talk page</sup></font></b>]] 17:24, 9 June 2022 (UTC) In current form without a toggle for width this layout is unacceptable on large monitors. Even my old 14'' monitor. For now I am reverting to avoid having in forced horizontal white-space. [[User:Phatom87|phatom87]] ([[User talk:Phatom87|talk]]) 14:32, 20 June 2022 (UTC) :Absolutely unacceptable, too narrow, an unjustified waste of space. [[User:Loupeter|Loupeter]] ([[User talk:Loupeter|talk]]) 10:39, 24 June 2022 (UTC) :It sounds like the fixed-max-width (assuming one's window is wide enough, and regardless of how much wider it might be) is a compromise between the needs of two different types of reading activities. I have both habits (skim vs detail-read), and felt especially the concern that the text doesn't obey what *I* do with my window. A reason I might widen my window is exactly because I want wider content. A comprimse necessarily isn't ideal for either one side. A better solution is to make it easy and discoverable how to get the *best* feel for whatever one is trying to do, rather than forcing so many to have a sub-par experience. A third-party gadget isn't discoverable and is surely more fragile than a first-class toggle feature of the skin itself. [[User:DMacks|DMacks]] ([[User talk:DMacks|talk]]) 15:16, 29 June 2022 (UTC) In my opinion, [[Skin:Timeless]] does a much better job at restricting article space to improve readability. This is because the UI is not entirely positioned on the left-hand side of the screen, and the background colour is not blindingly bright. If the intention is to create whitespace, please don't use bright colours. Timeless also has more space for pictures. For the past 20 years, articles have been written with the understanding that 80%+ of the screen will be for content. There are width and upright tags all over the place that, once viewed with this narrow a perspective, become overwhelming. A skin should not change the fundamental readability of the page. Compare [https://en.wikipedia.org/wiki/The_World_Before_the_Flood?useskin=vector-2022 this] with [https://en.wikipedia.org/wiki/The_World_Before_the_Flood?useskin=timeless this]. In Timeless, when the content ends, grey begins. In Vector 2022, it looks like the HTML was corrupted and failed to load because it continues with white for no discernable reason. Vector also artificially makes articles look longer than they are, which may actually dissuade people from reading. For instance, using a 27" 16:9 monitor, on the article for Barack Obama, [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=vector-2022 Vector] just about lets me see the entire lead on my screen at once. [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=timeless Timeless] allows me to see the whole lead quite easily, as well as part of the ToC. [[:en:Line length|Line length]] may be a thing, but you must take into account the total amount of text on the screen at once, too. There's no use having the perfect 50 character line if you need 100 of them all bunched up together. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:18, 13 July 2022 (UTC) :Quick update and aside: I just learned about wide-vector-2022. This is fantastic. I actually like the ToC being placed where it is when using that gadget. If the plan was to make the wide skin the default, I would be less hesitant. For comparison with the links in my previous message, [https://en.wikipedia.org/wiki/Barack%20Obama?useskin=vector-2022&withgadget=wide-vector-2022 here is Barack Obama] with wide-vector-2022. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:25, 13 July 2022 (UTC) ::This "wide-vector-2022" version should be the default IMO. [[User:Some1|Some1]] ([[User talk:Some1|talk]]) 02:50, 17 July 2022 (UTC) :> For the past 20 years, articles have been written with the understanding that 80%+ of the screen will be for content. :I'll just note that for the past 10 years that means you've written things that just do not work that way on mobile. :) :> A skin should not change the fundamental readability of the page. [..] In Vector 2022, it looks like the HTML was corrupted and failed to load because it continues with white for no discernable reason. :This seems like a lot of assumptions to me personally. Do we have wider evidence for this ? :> There's no use having the perfect 50 character line if you need 100 of them all bunched up together. :Literally every mobile user on the Barack Obama page, the majority of the readers. Screens and screens till you hit the end of the lead... —[[User:TheDJ|Th<span style="color: green">e</span>DJ (Not WMF)]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 20:20, 14 July 2022 (UTC) ::{{tq|I'll just note that for the past 10 years that means you've written things that just do not work that way on mobile. :)}} :::MinervaNeue, when viewed on normal phone screens, ignores width tags. The only difference between writing for desktop screens and mobile screens is file placement. ::{{tq|This seems like a lot of assumptions to me personally. Do we have wider evidence for this ?}} :::I don't need to provide evidence to state my opinion. The page looks unfinished with the extra whitespace on the right hand side. If you do want more than just my opinion, CNTRL+F for "whitespace" on this page. 12 other posts mention it. ::{{tq|Literally every mobile user on the Barack Obama page, the majority of the readers. Screens and screens till you hit the end of the lead...}} :::Difference is that my phone is in my hand. I'm not getting overloaded with line after line if the screen is only 15cm long. I can see a whole paragraph on at once and then scroll when necessary. [[User:Anarchyte|Anarchyte]] ([[User talk:Anarchyte|talk]]) 13:10, 15 July 2022 (UTC) == Keyboard shortcut does not focus search field in sticky header == {{tracked|T307024}} When pressing the keyboard shortcut for search (alt + shift + f) the search field at the top of the page is focused, even if the sticky header is showing. It would be better if the search field in the sticky header was focused. As it is now the page will scroll to the top which is unnecessary. [[User:Sebastian Berlin (WMSE)|Sebastian Berlin (WMSE)]] ([[User talk:Sebastian Berlin (WMSE)|talk]]) 16:10, 12 January 2022 (UTC) == Page-title and Search == In a nutshell, I believe * the Search would benefit from being (a) more consistently placed, and (b) more accessible from the sticky header by having a larger click-target. ** See image at [[:File:Vector-sticky-header-version1-search-size.png]] (and more [[#Search_box_size_and_location|details above]]) * the Page-title is already visible in multiple locations, and ''might'' not need this additional instance? AFAIK only users with "Fullscreen - F11" enabled would hide the existing locations where it is already displayed, whilst scrolled. ** See image at [[:File:Page_title_repetition_and_cutoff.png]] Hope that helps! –[[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 20:53, 21 January 2022 (UTC) == Feedback regarding the new language switcher == Hello, I am a French person using Wikipedia in both French and English. I usually decide the language of the article depending on the topic. If it's related to France, I know the French version is going to be better. If it's a general topic, I usually select English. However, it's been a few months that the language picker has been moved to the top of the screen when an article is display in French. And I really can't get used to it. Sure, it's easy to discover - but it's more complicated to use. Having to click twice is a regression for anyone switching language frequently. An action that used to require half a second now takes 2 seconds. If you do this about ten times every time you browse Wikipedia, it does become irritating... I hope this feature is not shipped to other languages, and France gets the sidebar back. If you want to make this feature more discoverable, maybe you could add a shortcut but keep the sidebar. Or display a tooltip once in a while to educate newcomers. But please, keep "heavy users" of language switching in consideration. Thanks {{unsigned|77.148.113.166|19:54, 25 January 2022}} : I'd state this as 'what used to take me a second (finding the right language) now takes 10': Open language switcher, often don't see the language I want, have to search? want to see which languages have a version, have to scroll; don't have a quick way to default present all languages by-alpha. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 16:49, 2 May 2022 (UTC) : I have to agree with this as another French person frequently switching languages on Wikipedia and Wiktionary. I should add, in addition to the intrinsic usability of the interface (I do agree it's a slight regression for my usage), the fact that most language editions still use the old interface (and most other sites using mediawiki, and the latter is likely to remain the case for a long time) means you don't actually get the opportunity to unlearn it. So every time I want to switch languages from a French page, I will first scroll down to the old location and waste 1s parsing the sidebar and wondering where the links are. I check out other languages almost every time I read any article and those milliseconds of irritation do add up. Anyway, I strongly think that “don't fix what ain't broke” should apply here! [[Special:Contributions/37.183.2.114|37.183.2.114]] 12:06, 8 May 2022 (UTC) : +1 to [[User:Sj|Sj]]. --[[User:ThurnerRupert|ThurnerRupert]] ([[User talk:ThurnerRupert|talk]]) 18:58, 11 June 2022 (UTC) Often I use the language switcher not to navigate to the article on different language, but just to look up how that article is titled in a different language. In other words, using Wikipedia's inter-language links as a sort of dictionary. By hovering over the list of languages I can gather multiple titles, see their similarity between languages. With the New Look, language switcher became less accessible, though gathering titles by hovering still works there. Also this new dropdown-based language switcher seems either to require tricky CSS features or JavaScript. Will it make problems for simplistic browsers like w3m? [[User:Vi2|_Vi]] ([[User talk:Vi2|talk]]) 17:48, 20 May 2022 (UTC) I find the language switcher the worst of both worlds of the two variants in the old interface. It can be annoying to scroll through 200+ languages in an idiosyncratic ordering (for example, كوردی [Kurdi in Perso-Arabic script] is filed under S for Sorani), but at least I can see them all and preview the name of the article in various target languages. With the drop-down menu in the old interface, I get the languages grouped geographically, and I can also search for a specific language, with the system recognizing many name variations. The new interface gives me a drop down menu with all 200+ languages in the same idiosyncratic order, with no geographic grouping and no ability to search for a specific language. [[User:LincMad|LincMad]] ([[User talk:LincMad|talk]]) 22:28, 25 May 2022 (UTC) I am primarily an active user on the Japanese Wikipedia (now defaulted to vector2022) and I agree with you completely. Why doesn't this use the blank spaces on the left and right? No need to hide buttons and functions everywhere just to make the page look hollow. As for the other features, there are so many problems with the new Vector. I definitely want the old version to remain. I will continue to use it and not the new one. --[[User:Sugarman|Sugarman]] ([[User talk:Sugarman|talk]]) 07:14, 6 July 2022 (UTC) == Feedback on ToC functionality == Hello, I’m not sure how far you are in the development of the new table of content functionality, but I was looking at [https://en-toc.wmcloud.org/wiki/Moon this prototype] and noticed a potential problem. Here the ToC is on the side and that’s a good thing, but the ToC in the text have also been deleted and that’s not much a good thing. When there is a big infobox, the in-text ToC compensate partly or totally for it, hence the page arrangement take it into consideration for the position of the images. Now if you delete it, all the text will go up, along with the images, but the images can’t always follow, because the infobox, so the right-aligned images are going to pile under it, while the left-aligned will reduce the text to a very small column between them and the infobox. On fr:wp, infoboxes are very widely used, so deleting the in-text ToC is going to break the page layout of most articles (and rather probably upset the community). So I’d suggest that, whatever you do with the ToC, to not delete the in-text ToC until there is also a functionality to move the infobox outside the text too (that would be great by the way, as infoboxes always cause difficulties with page layout). --[[User:Runi Gerardsen|Runi Gerardsen]] ([[User talk:Runi Gerardsen|talk]]) 09:30, 7 February 2022 (UTC) :I would like to add myself as having this same concern about images. At present, image placement in many articles was determined by this factor of the TOC being inline, sometimes offsetting the issues of long infoboxes and allowing the first image in the first section to be right-justified (like anyone with any experience in professional publishing, I ''really'' hate left-justified lead images as they break up the flow of the text by interposing themselves between heds and text. Similarly, I try to maintain alternation in the justification of images since that mirrors the sweep of our vision and makes text with images easier to read (but of course you don't do this when it creates other layout issues).<p>''When'' this is deployed, a lot of articles are going to suddenly have image placement issues at the top that didn't previously. And this will probably make a lot of people ''very angry''.<p>I can see the need for the sticky TOC but I think it would still be better as something that could be toggled there from its current position while reading depending on how the user prefers it in an individual article. [[User:Daniel Case|Daniel Case]] ([[User talk:Daniel Case|talk]]) 05:50, 29 April 2022 (UTC) ::What if we kept both the inline/in-text ToC ''and'' the sticky/sidebar ToC, but only display the latter when the user's scrolled past the former? A user preference could be added that forces the latter to always (or never) be displayed. I agree that the situation with images is a <abbr title="Pain In The Frigging Arse">PITFA</abbr>, but I really don't want to give up the sticky ToC either… [[User:OmenBreeze|OmenBreeze]] ([[User talk:OmenBreeze|talk]]) 00:43, 6 July 2022 (UTC) I'm not sure, but until I manually switched back to "Vector legacy (2010)", then again to "Vector (2022)", ToC section was absent completely (neither new-style nor old-style). Also maybe, like with the language switcher, there should be [temporary] notice about ToC having moved to the left where it was previously? [[User:Vi2|_Vi]] ([[User talk:Vi2|talk]]) 17:57, 20 May 2022 (UTC) == Feedback on new language switcher in French == As a translator, I litteraly jump from one language to another every hour of every day. It is simply unbearable to now have to go to a sub-menu to switch from French to English or Italian. That added click translates (pun intended) into lost time and nerves on a daily basis. I'm not hostile to a more smartphone-friendly interface, and maybe that kind of switcher is perfect on a little screen. But it's not okay to make the overall experience so much unsteady (especially with the links being there for some languages and moved away for other ones) when # switching seamlessly from one language to another is precisely the one advantage Wikipedia has over any other encyclopedia and # my 32" monitor has plenty of space to display these links in the left column. Last year I had selected the old Vector theme for this very reason and this morning, I was force-switched into the new Vector 2022 theme. So for the second time I'm back on the classic Vector theme and really, really hope it will stick. [[User:Herisson26|Herisson26]] ([[User talk:Herisson26|talk]]) 22:16, 7 February 2022 (UTC) :Hello @[[User:Herisson26|Herisson26]]. Thank you for asking here. :* We've been planning to provide [[Reading/Web/Desktop_Improvements/Features#Language_switching_2:_One-click_access_to_preferred_languages|one-click access to preferred languages]] but it's dependent on the work of another team ([[Wikimedia Language engineering|Language]]). We can't promise anything in terms of the timeline yet. :* What do you mean by "with the links being there for some languages and moved away for other ones"? You saw the new Vector on some wikis, and the old Vector on some other wikis, didn't you? I think that's related to the next issue. :* Why you had to switch back again - [https://pt.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Caf%C3%A9_dos_programadores&diff=prev&oldid=62956756&diffmode=source here's my explanation]. We're sorry, this was an extremely rare oversight. :* It's interesting that you write this interface is smartphone-friendly. Many volunteers note this. Out of curiosity, what makes you think that? Is this just about the responsiveness, or something more? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 00:30, 17 March 2022 (UTC) ::Hello @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], ::* For a translator, direct access to "preferred" languages is not enough. I need the complete list of languages, as it exists on old Vector. My preferred languages would be French, English, Spanish and Italian, but I will regularly read directly a page in Japanese, Portuguese or any other if it's the one that will get me the information I'm looking for (which is quite often the case when dealing with foreign people). So limiting direct access to a select few languages will still break Wikipedia for me. ::* Yes, lots of wikis use old Vector while the French one uses the new ones. It completely breaks the user interface. It is of utmost importance to me that all Wikipedia pages have the same layout, whatever the language. I understand the need to test things, but when you make a public switch that impacts the ergonomics of the site, it should be made across all languages. Maybe make the change per-user instead of per-language if you don't want to switch everyone at once. ::* Nothing to do with responsiveness. Smartphones don't have the physical space to display the language list and the article content at the same time, so having a button on the top of the page to show/hide the language panel makes sense. It does NOT on computers, which have plenty of free space for the left column and the traditional language list. ::[[User:Herisson26|Herisson26]] ([[User talk:Herisson26|talk]]) 08:21, 18 March 2022 (UTC) Very bad indeed. The French version of Wikipedia, which has put all interwiki language links in a dropdown menu, is most annoying. It is a big waste of time, and not user-friendly at all. To switch to the article in another language, instead of having the whole choice displayed at once and just having to click, one now has to go back up to the right-hand corner of the article, click on the dropdown menu, scroll down the list until the desired language apears, click again... This change is not an improvement. It tends to isolate each linguistic version of Wikipedia, by rendering the language switching much harder. If ever it is useful for smartphones, please change the layout for mobiles only ("m" version of Wikipedia), but not for the desktop version. This cumbersome change should NOT be extended to other Wikipedias, and the French version should revert as soon as possible to a user-friendly layout, such as that of the English language Wikipedia. [[User:Baronnet|Baronnet]] ([[User talk:Baronnet|talk]]) 15:49, 20 March 2022 (UTC) @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] very cool that you bring one click different language!! would you please include the language team in this discussion here, and provide a link so people can view the progress? --[[User:ThurnerRupert|ThurnerRupert]] ([[User talk:ThurnerRupert|talk]]) 18:56, 11 June 2022 (UTC) == TOC Feedback == I noticed that the newest designs for the table of contents do not allow for it to be collapsed. I think the ability for the TOC to be collapsed is very important, specifically for users that have a touchscreen laptop. I and a friend of mine often use our left hand and our touchscreen to scroll articles because on our laptops it is often easier to scroll quicker than to use the touchpad. If the TOC remained expanded we might accidentally tap a link. A button to collapse it and a preference to expand or collapse it by default would be nice. [[User:Lectrician1|Lectrician1]] ([[User talk:Lectrician1|talk]]) 20:07, 8 February 2022 (UTC) :Hello @[[User:Lectrician1|Lectrician1]]. Indeed, the first version of the TOC was not possible to be collapsed. This was because the results of user testings (both in-person and on-wiki) didn't indicate that the functionality was important. Now, given the feedback we've collected, we've decided to consider options how to make the TOC collapsible. In this context, what do you think about our [https://di-collapsible-menus.web.app/Brown_bear newest prototype]? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 13:46, 6 May 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] Thank you for responding! :::Hi, @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], I came to this page to ask whether the ToC can be moved from the sidebar, and really like the prototype. However it seems to be malfunctioning in Safari 15.4 (17613.1.17.1.13): https://imgur.com/a/O0Jhti1 :::Thanks. [[User:HughLilly|&#32;—Hugh]] ([[User talk:HughLilly|talk]]) 05:43, 20 May 2022 (UTC) ::My feedback: ::* I really dislike the usage of the bracket type of buttons for <code>[hide]</code> and think a OOUI button or a smaller alernative should be used instead. ::* I like that all of the headers in the TOC are collapsed by-default, however, I think they when you're scrolling inside of a section, they need to expand and collpase as you go through one section to another. I've seen this functionality on other platforms and it allows the reader to understand the outline better when they're viewing the article. ::* The hiding action of the TOC has an inconsistent navigational pattern. UIs should always require the same amount of actions to disable something as to enable something. That always feels the most natural. Hiding the TOC for its default position requires one button press, but to return it back to its previous state requires two. Also, its location next to the title and then how it switches to the upper left to become sticky is really weird too. I don't like either of those locations. I was thinking it could look something like this collapsed and you could press the icon on the right to both collapse and expand it: ::[[File:MediaWiki table of contents collapsed idea.png|frameless]] ::[[User:Lectrician1|Lectrician1]] ([[User talk:Lectrician1|talk]]) 00:42, 7 May 2022 (UTC) Hi, i just cant find the table of contents, i need it for easier navigation. please, help == Sticky header in the namespace Project == ([[:fr:Discussion_utilisateur:Patafisik_(WMF)#En-tête_figé_et_accès_aux_langues|original discussion in French]]) Hi, a user suggests to add the sticky header in the namespace Project too, not only in [[Talk:Reading/Web/Desktop_Improvements#Talk_page_and_page_history|Talk pages or History pages]] (see for exemple [[phab:T289641#7365946]] and [[phab:T299115]]). Best regards, [[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 09:15, 9 March 2022 (UTC) == Left margin menu pushes down content == I normally use Monobook, but happened to get into the new Vector. Odd experience. The search box was absent and I had to scroll down for the content. I now see that you are supposed to click the magnifying glass to get the search box. OK. But the scrolling? It seems the new Vector tries to guarantee wide enough space for the content. Perhaps that's what people surfing with maximised windows expect, but if you have a narrower window, is that really optimal? To get the left margin menu to the left of the content, I need a window some 1000 px wide. This "minimum" width gives me lines of about 100 characters, while I've heard reading is easiest at 47–72 or something like that. I like to have several windows open in parallel, and a narrower windows makes them fit better. Anyway, if one's browser window is narrow, for whatever reason, does the empty space to the right of the margin menu really give the best possible experience? Is the 100 char width something that needs to be guaranteed for those planning layout of individual articles? (This experience is with Firefox 91.7.0esr on Debian.) –[[User:LPfi|LPfi]] ([[User talk:LPfi|talk]]) 20:07, 17 March 2022 (UTC) == Questions I shouldn't need to ask == I can tell WMF developers put a lot of work into this, but I'm sorry, this isn't cutting it. This latest prototype is Vector in name only. It's a completely different look and a completely different experience. * Why do I have to click twice to get to my talk/contribs/preferences? * Don't you think you could have fit those important links if you didn't go overboard on the whitespace or if the search bar wasn't so enormous? * Is the language switcher really so important that it belongs in the sticky menu? * I had to think for a few seconds about what the hamburger/star icon was (it's the Watchlist). Why are the icons necessary? I'll answer this one — too much whitespace at the top. * Why is the new interface such a step down for the editors who will have to use it every day? * ''And why are you still trying to put a hamburger menu on a desktop site?'' It's not all bad — I do think the max width improves readability. But that was already present on previous less-bad prototypes. We were promised "improvements" to Vector, and what we're getting is an entirely new (and entirely inferior) skin. If this is really going to still be called Vector, that is highly misleading. The early comments that "total replacement is not an option" don't make a lot of sense now that Wikipedia appears to be getting exactly the top-down redesign I had feared this project would produce. Pigs will fly before this gets deployed to English Wikipedia ''without'' the community getting their pitchforks. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 04:45, 26 March 2022 (UTC) : I went into Preferences to turn off the changes and I saw that the software is now treating "vector-2022" as a new skin. This is better than what I thought was going on but maybe there should be a more original name> : Also, wouldn't it be a much better use of developer time to, say, work on the many unresolved Community Wishlist items? —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 17:09, 26 March 2022 (UTC) ::Hi @[[User:Pythoncoder|Pythoncoder]], thanks for these comments. I'd just like you to know that I'm working on an answer for you and I'll paste it soon. You've asked many important and basic questions (like the one about the Community Wishlist Survey), and I'm truly happy that you've done that. It's much better to clarify the basics. You don't know whether these are clear as long as no one questions it. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 00:53, 8 April 2022 (UTC) ::: {{ping|SGrabarczuk (WMF)}} I should have made it more clear above, but most of my comments are regarding the Fourth Prototype. And now that I read through my earlier comments it makes sense to make the sidebar collapsible in case readers don't want distractions. I believe the sidebar is shown by default so please disregard my complaints in that area. This is why I shouldn't edit when I'm sleep-deprived. I do still think the new skin needs a new name though. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:03, 8 April 2022 (UTC) ::: Also re: wishlist, I suspect the two projects are probably worked on by completely different dev teams. Again, I'm sorry for the passive-aggressiveness above. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:06, 8 April 2022 (UTC) ::::Hello @[[User:Pythoncoder|Pythoncoder]], no worries, I'm really glad you've figured some issues out yourself! Would it be possible for you to state what remains unclear? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:05, 14 April 2022 (UTC) :::::I think it mostly boils down to the amount of whitespace at the top and the hiding of important links such as talk, contribs, and login under a dropdown. I think this should be fixed. —[[User:pythoncoder|<span style="border-radius:10px;background:blue"><span style="color:aqua"> python</span><span style="color:#ff0">coder </span></span>]] ([[User talk:pythoncoder|talk]] &#124; [[Special:Contribs/pythoncoder|contribs]]) 01:28, 15 April 2022 (UTC) == Sticky header doesn't show the name or the logo of the project: the risk of loss of identity for Wikimedia sister projects == ([[wikt:fr:Wiktionnaire:Wikidémie/mars_2022#Interface_bureau_%3A_venez_tester_le_quatrième_prototype|From French Wiktionary]]) {{Tracked|T293395}} "I'm still observing the same problem when using this new skin: if you scroll down the page, it's impossible to know on which Wikimedia project you're on. The sticky header doesn't include the name of the site you are on, which is penalizing users for sharing screenshots, but also for identifying the editorial lines/ editorial policies of the different projects. Sister projects have important specificities. On the French Wiktionary, we already have people complaining that they can't find the content they expect to see on Wikipedia, and we have to tell them that it doesn't belong on the Wiktionary. I'm afraid that the phenomenon will only get worse."-Translated by --[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 13:28, 29 March 2022 (UTC) (original message: ''"J’observe toujours le même problème, que je constate au quotidien en utilisant ce nouvel habillage : on ne sait pas sur quel projet on est dès que l’on défile un peu. L’en-tête fixe n’intègre pas le nom du site sur lequel on se trouve, ce qui est pénalisant pour le partage de capture d’écran, mais aussi pour l’identification des lignes éditoriales des différents projets qui ont des spécificités importantes. On a déjà actuellement des gens qui se plaignent de ne pas trouver tel contenu qu’ils s’attendent à voir sur Wikipédia, et à qui on doit répondre que ça n’a pas sa place sur le Wiktionnaire. Je crains que le phénomène ne fasse qu’empirer. [[user:Noé|Noé]] 29 mars 2022 à 12:37 (UTC)"'') == The "sticky table of contents" is the worst among all the bad changes == I am sorry, but this sticky table of contents is such an eyesore, its sole addition might make me quit reading Wikipedia altogether. I'm not exaggerating, a similar update to Liquipedia made me want to avoid that project. It's more than an annoying waste of screen space - it also makes the different parts of the table of contents bold depending on where in the article my screen is, and thus it triggers my OCD, and it simply irritates me. I hate these moving parts in forced mobile designs. > "The results of our 3rd prototype testing showed an overwhelming support for the proposed table of contents." Have they? I don't see any discussion here. > "The new table of contents will be persistent - users will have access to it at all times. It will also make it easier to understand the context of the page." Are the TikTok memes reality? Excuse me, but I don't randomly forget what page or section I'm reading, thus I don't need a sticky title on my screen at all times. > "In addition to that, it will be possible to navigate to different parts of the page without having to scroll all the way back to the top." How is that "need" in any way difficult? It's one button on the keyboard - called ''Home''. Or you hold the slider on the right and jerk it up in a millisecond. But I suspect I know where "scrolling" is an issue - on mobile phones. This entire update in an exercise in transitioning a fine desktop UI from the 2000s which I had an honour to fall in love with in the 2010s to the non-constructive, downgraded, annoying and irritating experience of mobile phones. Thankfully, not all projects choose to go this way. For an example of a new encyclopaedia with a traditional design, see the immensely popular Korean Namu Wiki. [[User:Adûnâi|Adûnâi]] ([[User talk:Adûnâi|talk]]) 12:53, 10 April 2022 (UTC) :100% agree. [[User:Football Lab|Football Lab]] ([[User talk:Football Lab|talk]]) 09:12, 26 June 2022 (UTC) == some feeback on the layout == I really like the preview, it is much cleaner, a few thoughts from viewing this on desktop (I saw the Blue whale article and the Potato article): # The 'in other projects' section is really nice, however I wonder what would be a sensible heirachy for this. Should it be contextual based on the topic or something else? Currently its suggesting me WikiNews which isn't relevant or a particularly well maintained Wikimedia Project. Also the other projects is more about navigating to other information on that topic, rather than being a tool, I wonder if it should be under the TOC instead? Its more about navigating information on the topic rather than using a tool. # I'm not sure if this is intended, the images sit on top of the sections instead of being displayed along the side the text, especially for portrait format images this creates a lot of empty space. # When logged out having the TOC on the left is really nice, works really well. But when I'm logged in the TOC is hidden under half of the tools but then the other half is on the right hand side is quite confusing. I realise this is a really difficult thing to organise, maybe it could live under the TOC? There isn't a clear deliniation between reading and contributing which is confusing. # The taxonomy templates at the bottom are pretty broken and make long lists, also lists within the Potato article lose their formatting meaning on the page for potato the list of synonyms is one column wide making a very long section which isn't going to useful for a general reader right in the middle of the article. [[User:John Cummings|John Cummings]] ([[User talk:John Cummings|talk]]) 18:03, 12 April 2022 (UTC) == I hate the new TOC == I was directed here from [[phab:T273473]].<br /><br />That left-of-the-article TOC is a horrible nightmare. I absolutely hate it. I would seriously avoid any website that forced it upon me. Can't scroll it out of sight, can't collapse it, can't disable it, takes up too much space, I hate it I hate it I hate it. This was the reason I switched back to Vector classic on beta cluster. (and if Vector classic gets it too I'll switch to Monobook, Timeless or just murder it with a userscript) I'm not much of a fan of Vector 2022 (but it's not a lost cause, just needs work), but this TOC pushed me over the edge.<br /><br />As a personal note: I rarely use the existing TOC. But I can scroll it out of sight so it doesn't bother me. If the TOC went completely missing tomorrow, I wouldn't miss it. Having this big, (to me) useless thing that contrasts with the main content (it's much darker) permanently in my field of vision greatly annoys me. And because of the fixed position, my banner blindness fails to kick in. This results in pure hatred for something that, on the face it, could seem innocuous. <span id="Alexis_Jazz:1650385558357:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 16:25, 19 April 2022 (UTC)</span> :I was not "directed" anywhere, I blundered onto here after finally finding information about this new skin. And let me be clear, APART from the ridiculous handling of the TOC, the new skin is great, precisely BECAUSE, before the TOC-debacle, this skin allowed me to get more of the article on the screen, and allowed me to hide the standard list of menu choices that I only need 0.something % of the time. :So, please, Please, PLEASE make that TOC hideable! It's perhaps (!) a great default for newbies, but it's a bloody nuisance for us who usually never use the TOC, and if we do, we know where to find it! [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 21:49, 25 April 2022 (UTC) ::I totally agree. [[Special:Contributions/185.53.157.151|185.53.157.151]] 08:13, 26 April 2022 (UTC) ::@[[User:Autokefal Dialytiker|Autokefal Dialytiker]], right, it's not that easy to get here. We'll put link to the project page on the list of available skins in preferences. The task is documented as [[phab:T307113|T307113]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:25, 28 April 2022 (UTC) :Hey @[[User:Alexis Jazz|Alexis Jazz]] - thanks for talking to us. It’s good to hear you were using Vector 2022. I hope that you will switch back to it. In terms of the table of contents, you raise good points. A lot has been happening since you wrote your comment, so my answer is longer than it would have been last week. :* The first version of the design was based on the feedback we got on our previous prototypes from readers and editors (see [[Reading/Web/Desktop Improvements/Repository/Sticky Header and Table of Contents User Testing#toc-intro|in-person reader & editor testing]] and [[Reading/Web/Desktop Improvements/Third prototype testing|on-wiki community testing]]). :* That said, we have not yet made the design final. We are working on different ideas for the visual design of the entire site. We'll make the main content of the page be the primary focus of attention, even when other navigational elements (such as the ToC) are present. If you’re interested in following along with that work, most of it will be tracked on [[phab:T301780|T301780]] and in subtasks of that ticket. :* We are also considering the way the ToC will display at smaller resolutions ([[phab:T306904|T306904]], [[phab:T306660|T306660]]) and looking into some options for collapsing it that could work for wider screens as well. :* As you can see, people like you who have chosen Vector 2022 individually share a lot of feedback with us now. [[phab:T307004|T307004]], [[phab:T306562|T306562]] are some examples on things we are or will be working on. :* In the meantime, we will be A/B testing the ToC on the pilot wikis. Our hypothesis is that the ToC will decrease the amount that people have to scroll to the top of the page to switch to a different section. The design might also vary once we have the results of the test. :* Since these changes might take a little while to reach the beta cluster, we would also encourage technically-skilled folks to set up a script or gadget to make a temporary solution. :And... yeah, [[Newsletter:Desktop Improvements updates|subscribe to our newsletter]], join our office hours ([[Reading/Web/Desktop Improvements/Updates/Talk to Web|tomorrow]] or [[Reading/Web/Desktop Improvements/Participate|later]]) and talk to us more. Thank you! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:23, 28 April 2022 (UTC) ::[[User:SGrabarczuk (WMF)|SGrabarczuk]], here's another thought: [[wikt:reverse]]. It's not a long page, but that TOC is so bloody huge a full HD display isn't enough to read ''any'' of the actual page content without scrolling. <span id="Alexis_Jazz:1651369145562:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 01:39, 1 May 2022 (UTC)</span> :::Right, right. Let's just take a look at [[:pl:Gramatyka języka fińskiego]]. I mean, this is an edge case, and as such, it's not that critical. From what I know, all TOC sections aren't uncollapsed by default, and you need to make an effort to see the full TOC. Is this your experience, too, @[[User:Alexis Jazz|Alexis Jazz]]? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:45, 5 May 2022 (UTC) ::::[[User:SGrabarczuk (WMF)|SGrabarczuk]], sorry for being possibly unclear. It was just a thought about the classic inline TOC which is disproportionally huge on Wiktionary, so it's something to think about when designing a new TOC. On the Gramatyka page on plwiki you at least get the intro without scrolling and the page actually ''is'' very long, so it's understandable the TOC also gets big. I've taken a look at the CSS (should have done that sooner) and simply disabling "position:sticky" stops the new TOC from being so infuriating. IMHO that should be the default, or at the very least, proper research should be done into this. Not only to determine by majority vote what users prefer (I wouldn't be surprised if sticky wins a binary majority vote) but also how crazy either option can drive users who ''don't'' like it. Pleasing a majority is no good if it causes a minority to be greatly aggravated. While I personally can get around it using technical means, that isn't true for most people. I'll also note that the experience on devices that are primarily controlled with a touchscreen may very well be different. With a keyboard, scrolling back up to the TOC is nearly no effort. Just press "home" or hold "page up". With a touchscreen, not so much, so I can see why sticky might have a greater appeal there. <span id="Alexis_Jazz:1651821096574:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 07:11, 6 May 2022 (UTC)</span> :::::What TOC? I don't get any such thing. [[User:Betaneptune|Betaneptune]] ([[User talk:Betaneptune|talk]]) 17:36, 25 May 2022 (UTC) :100% agree. [[User:Football Lab|Football Lab]] ([[User talk:Football Lab|talk]]) 09:14, 26 June 2022 (UTC) == Watchlist icon == [[User:Schierbecker|Schierbecker]] [[Topic:Wu23w3nlomndp5f1|wrote]]: <blockquote>The watchlist icon too closely resembles a hamburger menu button. I can see many clicking the button thinking it is a dropdown menu. Some may lose unsaved edits after clicking it.</blockquote> I completely agree, but not really because it resembles a hamburger button but because it's sandwiched (no pun intended!) between dynamic menus. If there was the dropdown arrow next to the interlangs, alerts and notices buttons just like the personal menu, it would communicate more clearly that the watchlist button is a simple link and not a menu. [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 02:38, 21 April 2022 (UTC) :Thanks for this comment, @[[User:Nardog|Nardog]]. We'll think how we could improve this. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:55, 27 April 2022 (UTC) ::Information on the design process that led to the current icon can be found here: ::https://phabricator.wikimedia.org/T297979 ::Nardog is already involved in that task. It's probably best to add this feedback there, as not all designers are reviewing this talk page. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 17:01, 6 July 2022 (UTC) == Sidepanel is bloated == Tonight size of left panel is increased too much. It covers more than ¼ screen now. https://imgur.com/3YJlcii Can I reduce size of panel, as it was before? [[User:Tucvbif|Tucvbif]] ([[User talk:Tucvbif|talk]]) 21:18, 25 April 2022 (UTC) : Agreed. I feel there's too much white space padding the left and right of the sidebar. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 00:53, 26 April 2022 (UTC) :@[[User:Tucvbif|Tucvbif]] @[[User:Tenryuu|Tenryuu]] thank you for these reports. It seems like you may have your browser window zoomed in, is that correct? Also, if you are able to please add any additional thoughts, needs, screenshots, and ideas to this task: https://phabricator.wikimedia.org/T306660. [[User:AHollender (WMF)|AHollender (WMF)]] ([[User talk:AHollender (WMF)|talk]]) 14:54, 26 April 2022 (UTC) ::No, my browser not using zoom. I using personal css with font-size 14pt, but when I login to other account without personal css, the sidepanel still terrible huge. ::https://imgur.com/l8bIrDF [[User:Tucvbif|Tucvbif]] ([[User talk:Tucvbif|talk]]) 15:07, 26 April 2022 (UTC) :: @[[User:AHollender (WMF)|AHollender (WMF)]]: Apologies, I should have clarified. The sidebar here is fine; the one at Wikipedia isn't. Resetting the zoom level on Wikipedia doesn't address the issue; there's still a lot of white space padding the element. I'll leave this discussion and focus on [[#I oppose the new sidebar/TOC]] and the mentioned Phabricator ticket, which describes my issue more accurately. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 15:10, 26 April 2022 (UTC) ::: The ambiguity and confusion evident from the preceding discussion suggests that the interface has become to complex. Aren't the original sidebar and TOC at the top of the page enough? Why change? Is another popup menu necessary to switch language? What about setting language in user preferences? Simplify, simplify, simplify. Regards, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|talk]]) 00:28, 25 May 2022 (UTC) == TOC limit doesn't work anymore == It seems that this "sidebar TOC" has different classes, making [[:en:Template:TOC limit]] doesn't work anymore. [[User:William Surya Permana|William Surya Permana]] ([[User talk:William Surya Permana|talk]]) 07:46, 26 April 2022 (UTC) :Templates can only control the content of an article so [[en:Template:TOC_limit/styles.css]] won't apply outside the article area so new classes won't help here. A magic word would need to be added so support this use case if important and time allows. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 15:37, 26 April 2022 (UTC) == I oppose the new sidebar/TOC == Please make it possible for the users to collapse the left sidebar/TOC or to reduce the white space size. I for one use a browser sidebar (Sidebery) as well as 150% or even bigger text size. Combined with the forced sidebar/TOC, the actual line length becomes much smaller than the recommended length. [[User:PeterTrompeter|PeterTrompeter]] ([[User talk:PeterTrompeter|talk]]) 08:43, 26 April 2022 (UTC) :Hi @[[User:PeterTrompeter|PeterTrompeter]] - thanks for your feedback. We're currently exploring better solutions for the ToC at narrow widths, which include the option of collapsing as well. Check out [[phab:T306660]] for the details and prototypes. It would be great to get your opinion on some of these. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:40, 26 April 2022 (UTC) ::I wonder about one thing: Who on earth thought that having such a monstrosity as that [pejorative snipped] TOC as a PERMANENT part of the skin would be a good idea ? I mean, having it pop up might be a useful thing for newbies (and I find even that a stretch of my imagination), but PERMANENTLY wasting space on a table of contents you consult perhaps once or twice per (long) article ? So KINDLY have it fixed to be hideable/collapsible so that we can get actual article contents on our screens. (One sidenote here: Apart from my blowout here - yes, I am aware that working on these projects is a chore, and despite my invectives here, I AM grateful for your efforts. It's just that this kind of stuff goes so completely against what would be the natural idea here, that I blow my top unnecessarily hard - people generally want to read the TEXT of the articles, so when a new skin development deliberately wastes space on the table of contents - ????? ) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 16:43, 26 April 2022 (UTC) :::Hey @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], we test all of the proposed changes. Editors and readers were strongly in support of this change. More details here: [[Reading/Web/Desktop Improvements/Features/Table of contents]]. Cheers, [[User:AHollender (WMF)|AHollender (WMF)]] ([[User talk:AHollender (WMF)|talk]]) 17:47, 26 April 2022 (UTC) ::::My question stands: Why having it there PERMANENTLY ??? Ok, I find something that's relevant for me to read; usually, I then want to READ just that; not the thread that led me there... So, why PERMANENTLY ??? [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 17:54, 26 April 2022 (UTC) == Public and private views... == While thinking about this, I was struck with what appears to me to be a central point of division here: This is not a question of how THE user interface should look like; but, rather, it is a question of what we should look like to anonymous users, and what choices should be available to those of us who log in ? Does that differentiation make sense ? (I should mention that I'm coming to this from Wikipedia, and that I have very little experience with the other projects.) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 19:14, 26 April 2022 (UTC) :Yeah @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], this makes sense. With the caveat that I don't know what central point of division you are referring to :D :At the moment, except for gadgets and such little tweaks, we aren't able to offer different interfaces for logged-out and logged-in users. Also, we can't make it possible to easily switch between different settings like dark/light mode, contrast versions, font sizes, etc. We need to improve the basics of the viewing/reading experience, we can do ''that'', so we're doing it. :As a result, readers use our interface more comfortably, we check that with regular A/B tests. As for the most dedicated editors, they can/should: :# Help us build an interface useful to them (by giving feedback on the prototypes, on the changing interface on "pilot wikis", by adjusting gadgets, etc.) :# Accept the arguments about the results of user testing, A/B testing, community feedback... :# Accept the "final" version as the basic version, and :# Configure it further if they want. :Our team would like to work the interface deeper. We would like to make it more modular and adjustable. (Of course, content would stay objectively the same for all.) A few months ago, we started working with more closely [[Growth]] and [[Editing]]. Now we're checking how ambitious we can be. :Does that answer your question? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:26, 27 April 2022 (UTC) ::My way of thinking here, is that the main divider here is between what should be visible and available to those who are NOT logged in, and what should be available and possible for those who DO log in. This is because the big difference between the two groups, is that those who are logged in, are also able to seek detailed information and make informed choices (and possibly programmed adaptations), whereas the non-logged in can not be trusted to have any particular information about the system, do not have a way of communicating preferences, and therefore needs to be given visual cues as to what's possible and available, precisely because they are strangers here... (Sidenote: I am of the Wikipedia, and that is the project I write in relation to; each project will have some peculiarities that do not apply to the other (to the same degree, at least); for this reason I should remember to mention this.) :: ::I hope what I'm writing here makes some sense, I try to avoid giving specific "orders" to anyone, but rather contribute to clarifying the context so that I understand it; hopefully, what I then write makes sense to others as well... (About here my subconscious can be heard muttering "and if pigs could fly"...) [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 13:17, 9 May 2022 (UTC) == "Beginning" is confusing == More feedback: when I was at [[w:Gotcha journalism]] just now, I became confused because there appeared to be a section titled "beginning", which I assumed covered the early history of the term. It took me a minute to figure out that that wasn't referring to a section but rather a way to scroll to the top of the page. Many other articles are going to have a similar problem, since we often begin with history sections that might reasonably be titled "Beginning" for early history. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 22:42, 27 April 2022 (UTC) :@[[User:Sdkb|Sdkb]] - good catch! This is something we discussed quite a bit internally in order to finally settle on beginning, although I agree that it's still imperfect. Previously we were using "introduction". The issue there was that many articles have "introduction" as the name of their first section, causing duplication. Other options we were considering were location-based (back to top, beginning of page, etc). We are welcome to ideas on how to make this clearer. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 09:05, 28 April 2022 (UTC) ::The name used by wikipedians? ''Lead section'' in English, ''résumé introductif'' in French, etc ([[d:Q10966628|Q10966628]]) [[User:Pyb|Pyb]] ([[User talk:Pyb|talk]]) 11:07, 28 April 2022 (UTC) :::On Translatewiki.net I found "Début" for fr.wiki and "Inizio" for it.wiki (on it.wiki we use also "Incipit" or "Introduzione", see [[phab:T306990]]). [[User:Patafisik|Patafisik]] ([[User talk:Patafisik|talk]]) 15:09, 28 April 2022 (UTC) ::::@[[User:OVasileva (WMF)|OVasileva (WMF)]], did you consider different design approaches in addition to different names? If the word had been accompanied by something like [[File:Font Awesome 5 solid caret-up.svg|16px]], it might have been a lot clearer. I also think there's some benefit to matching the terminology we already use as editors ("lead section" or "introduction"), since that makes it easier for newcomers. The Wikipedia articles that currently have "Introduction" as their first named section should not—they should be tagged with [[w:Template:Overview section]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 20:16, 28 April 2022 (UTC) :::::<small>Bumping @[[User:OVasileva (WMF)|OVasileva (WMF)]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:16, 6 July 2022 (UTC)</small> ::::::Just leaving a note here that we're still watching this conversation and considering different options, but haven't made a decision yet. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:58, 11 July 2022 (UTC) ::I think using the article title would make the most sense, as the title is the uppermost heading in the article. That way the header that the reader arrives at always matches the one they've clicked on. (I'm sure "Beginning" is better than "Introduction," but it's not unheard of as a section title either: e.g. [[w:Creolization|Creolization]], [[w:Ashikaga shogunate|Ashikaga shogunate]], [[w:History of Carthage|History of Carthage]]. Is there any way to determine how often it's used?) [[User:Arms &#38; Hearts|Arms &#38; Hearts]] ([[User talk:Arms &#38; Hearts|talk]]) 19:35, 29 May 2022 (UTC) I think "Top" would be less confusing and generally make more sense as that seems to be the common English term for the top of the page. [[Special:Contributions/132.170.199.112|132.170.199.112]] 19:32, 22 June 2022 (UTC) == Table of contents below sidebar just doesn't work == On a broader note than the two pieces of feedback above, I have to say that my experience so far with the new table of contents has been really frustrating. As an editor, I use lots of the links in the left sidebar quite frequently, so I don't want to collapse it (and even if I did, the way it persists in whatever state you leave it in means that every time I used it it'd return). But preserving the left sidebar forces the table of contents below it, which is just awful. The number one time I want to use the ToC is when I first navigate to an article, and I either want to jump to a specific section or just to see what sections it has to get an overview. Forcing me to scroll to get to that information is extremely annoying, and if it's kept in the final version, I predict the outcry will be intense. You could resolve this either by retaining the old style ToC alongside the new (which would also solve the [[w:MOS:SANDWICH|sandwiching]] concerns I've previously raised) or by moving the ToC above the left sidebar. From your previews, I know you've been working on moving some stuff around and introducing pinning, so I hope this will be resolved in future iterations. But the initial version being introduced here is clearly not ready yet. Best, <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 22:53, 27 April 2022 (UTC) : For me it seems the table of contents and the sidebar seems to be two different things. On Wikipedia, I collapsed the sidebar and the table of contents still remain. [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 03:09, 28 April 2022 (UTC) ::I want ToC collapsed too. But there is no way to do it. It uses almost 1/3 of my screen and makes reading very difficult.- [[User:Nizil Shah|Nizil Shah]] ([[User talk:Nizil Shah|talk]]) 05:32, 28 April 2022 (UTC) :::Same here. 14" Screen, collapsed sidebar menu, open only when needed. With the new TOC I cannot collapse the sidebar, it's just a toggle between navbar and TOC. I appreciate the effort and that it's a first attempt, but it definitely should be optional. And yes, I was involved in feedbacks and testing earlier. Regards [[User:Elya|Elya]] ([[User talk:Elya|talk]]) 14:24, 29 April 2022 (UTC) :::: +1, the TOC should be accessible from the top of the page, and collapsible (vertically; also horiz if it is making the sidebar too wide - many pages have section heads that are quite long). [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 17:35, 2 May 2022 (UTC) :::::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] and @[[User:OVasileva (WMF)|OVasileva (WMF)]], neither of you have replied here. This is a major concern, and I predict that if it is not addressed, it may single-handedly prevent the community from being willing to accept New Vector. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:14, 6 July 2022 (UTC) ::::::Hi @[[User:Sdkb|Sdkb]] - thanks for the ping! Currently, we're working on making the ToC collapsible, especially on narrow screens ([[phab:T306660]]). Collapsing it would allow for access further up in the page, but won't completely solve the issue you're describing. To make using both the sidebar and the table of contents a bit easier, we are planning two things. For logged-out users, we plan on collapsing the sidebar by default so that the table of contents will be shown further up in the page. We are also planning on separating the tools related to pages in a separate menu. This will significantly shorten the space for the sidebar, and create a clear definition between which tool acts on the page as a whole, and which one acts only on the page itself. In this example, this puts the ToC above the end of the introduction section, which is higher than the previous ToC location (admittedly, this will not be the case for all articles). ::::::[[File:Prototype_of_table_of_contents_and_tools_menu_for_desktop_Wikipedia.png|thumb|Prototype of table of contents and tools menu for desktop Wikipedia]] ::::::[[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 14:07, 11 July 2022 (UTC) :::::::Thanks for the reply, @[[User:OVasileva (WMF)|OVasileva (WMF)]]! Moving the tools elsewhere (ideally to a Twinkle-like menu) is something I certainly support and have been trying to set up since [[w:WP:SIDEBAR20|the 2020 revamp]], and it would help with this. Your screenshot appears to be from a standard resolution display rather than a widescreen display, so I can't tell whether it's going to help enough to ensure that the ToC will always be visible on a normal monitor with neither it nor the main menu collapsed. Getting to a point where that's the case will be essential for getting community consensus. :::::::Is there a reason you don't seem to be considering placing the ToC above the main menu? <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 23:49, 13 July 2022 (UTC) == About Google Docs and Zoom == {{Ping|SGrabarczuk (WMF)}} Thank you for the invitation I received for tomorrow's videcall since I was an interface admin and a developer! but sadly I cannot participate since I don't use Google Docs or Zoom for security reasons (partially related: [https://www.zdnet.com/article/us-senate-german-government-tell-staff-not-to-use-zoom/] [https://www.gnu.org/proprietary/malware-google.html]). I don't know if it could be useful but maybe in the future you may consider to land the doc on the wiki itself, or using Etherpad [https://etherpad.wikimedia.org/] when realtime is needed. To drop Zoom, maybe I can propose Jitsi Meeting [https://meet.jit.si/] that is gratis and libre and supports streaming on social network to support large audience. (Also [[Wikimedia Meet]] deserves a try and some feedback). [[User:Valerio Bozzolan|Valerio Bozzolan]] ([[User talk:Valerio Bozzolan|talk]]) 15:38, 28 April 2022 (UTC) :Hello @[[User:Valerio Bozzolan|Valerio Bozzolan]]. I understand your concerns and thank you for the language you use. I do appreciate that. As you may have realized, it isn't without a reason why we use these particular tools/platforms. :# Google Docs are used by the Foundation as the default tool for making internal notes and docs. We might, for the purposes of the office hours, replace it with Etherpad. There's a problem with the translations, though. Asking translators to update just one word, and waiting until they've done that, could be troublesome. This is why I can only commit to replace this if we make more changes to the announcement. (By the way, the announcement is [[Template:Reading/Web/Desktop Improvements/Office hours announcement|fully standardized]] and translated into 16 languages, some of which use declination or are not written in the Latin script.) :# We need our office hours to be technically (platform-wise) predictable. Although Jitsi is open source and Zoom is not, the latter is more effective. It has been widely used for online meetings in the movement. It's been used by the WMF for office hours with the CEO, Maryana; it's been used by affiliates. There are hundreds of Wikimedians who at least once have participated in a Wikimedia meeting on Zoom. We know how to provide live translations there. Jitsi, on the other hand, is less popular, and we'd have to learn how to support live translations, including more trainings organized specifically for our meetings. :# We may consider having office hours on IRC. Frankly, I have a feeling that since the migration from Freenode, IRC has been more and more marginalized, but we could give it a try. :I'm curious what other Wikimedians watching this page think. Add your comments! [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:15, 5 May 2022 (UTC) ::Just asking for an understanding that Google Form and Zoom are a bug, not a feature, to participate in a Wikimedia project. A bug that deserves a long-term fix. [[User:Valerio Bozzolan|Valerio Bozzolan]] ([[User talk:Valerio Bozzolan|talk]]) 15:57, 7 May 2022 (UTC) ::: I appreciate these are standard across parts of the Foundation. And agree w/ [[user:Valerio Bozzolan|Valerio]] this is a bug, not a feature. Perhaps it's time to revisit this across the org. :) We should be using tools that can be constantly used and deployed by communities for events, workshops, office hours, talks without sending traffic through commercial servers. ::: ''Text'': Google makes some very wiki-spirited tools (they did absorb JotSpot back in 2006) so it's stayed around for a while. But we simply must stop using it as a crutch that keeps us from using and being delighted by notetaking on our own platform. Our collaborative platform for drafting and discussing documents. Our versioned, searchable platform. ::: ''Video'': I too have to use Zoom sometime, but I'm always surprised and a bit dismayed when a Wikimedia meeting uses it! Jitsi is stable, widely used + repackaged, easily modded and forked, and we host a [https://meet.wmcloud.org/ lovely instance] on the WM cloud. [We also regularly use BigBlueButton for larger audiences.] It makes it easy to name a persistent rooms, embed it it in other places or tools (see Jitsi-as-a-service + [[w:Brave Talk|Brave Talk]] these days), &c. We should be thinking about how to better use video streams in our projects, and using this framework as we do so. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 12:54, 14 May 2022 (UTC) ::::Thanks @[[User:Sj|Sj]] and @[[User:Valerio Bozzolan|Valerio Bozzolan]]. ::::# First of all, I really hear what you're saying. Perhaps you're right, Google and Zoom may be bugs - it's definitely not up to me to decide. "Perhaps it's time to revisit this across the org. :)" - I'm grateful that you specifically used the words "across the org". That's way wider than just Olga and me (people who organize ''our'' office hours), or [[m:Community Relations Specialists|Community Relations]] ("technical liaisons" so to speak), or [[m:Movement Communications|Movement Communications]] alone. If it's about ''the standard'', then it needs a broad agreement. ::::# @SJ, do Jitsi or any open-source alternatives provide the speech-to-text functionality and parallel voice tracks for live translators (interpreters)? I'm asking because each time we have a meeting, there are people who need the speech-to-text functionality . Unfortunately, we haven't been able to provide the live translation support yet. We're still working on it, and it seems we may have found a solution. ::::[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:55, 6 July 2022 (UTC) ::::: [[User:SGrabarczuk (WMF)|SGrabarczuk]]: :::::: 1. We ''should'' change the standard [though there seem to be many even within one org!], but I only mentioned that to suggest that none are set in stone. :) As this thread is about these particular discussions, I hope we can try a different standard for these sessions, or understand what prevents such a change. If it is purely a matter of accessibility features, that would make a phabulous ticket even if it is not yet known who could set them up. :::::: 2. Yes they do! Other collaborative orgs w/ similar issues of language equity use jitsi regularly. There are solutions or workarounds for both. [also, to the point of "supporting essential infrastructure for free knowledge", our engagement would certainly help make them better for all.] ::::: '''speech to text''': Google Voice integration seems to be there, and a number of open-source s2t services that are not quite comparable. You can see the range of Summer of Code [https://jitsi.org/gsoc/s2t/ projects] + community submissions scratching their own itches in the [https://github.com/jitsi/jigasi/issues/157 jigasi repo]. ::::: '''remote simultaneous interpretation''': the most recent solution (for a single language, letting you tune in or out of the raw audio and into a translator's audio channel) is use by [https://i.meet.mayfirst.org May First] (which we should [https://mayfirst.coop/en/ work more closely with] on choosing technology stacks, frankly) and is maintained [https://gitlab.com/mfmt/jsi here]. There are improvements, and pushes to integrate into jitsi core, both of which could be facilitated by small technical bounties or large expressions of interest [like Wikimedia indicating this is a crucial feature for us]. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 02:37, 7 July 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], I will not participate in any forum that is not public. Why the wmf foundation wants to share information via Zoom, a for-profit corporation which provides no guarantee of privacy, is anyone's guess. We have been using wiki-code for discussion since 2001, why this change? ::I apologize if you find my message above irrespecutful, but this represents the views of many. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|talk]]) 18:26, 13 June 2022 (UTC) :::@[[User:Ottawahitech|Ottawahitech]], above, you can find explanations on why we (the Web team) are using Zoom now. Are you also asking why we have any voice online meetings in general? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:57, 6 July 2022 (UTC) == Instant jumping vs. animated scrolling for table of contents == As you're polishing up the table of contents, one thing it'd be nice to consider is the behavior when you click on a section in it. Currently, it instantly jumps to that section, but I think it'd be better if it instead did a very quick scroll (maybe a quarter of a second). This would help readers to more easily understand what's happening when they click the link, and to get a better intuitive sense of what the article contains by seeing it flash by. Would that be possible? <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 02:37, 30 April 2022 (UTC) :<small>Bumping @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] and @[[User:OVasileva (WMF)|OVasileva (WMF)]]. <span style="color:#AAA"><small>&#123;{u&#124;</small><span style="border-radius:9em;padding:0 5px;background:#088">[[User:Sdkb|<span style="color:#FFF">'''Sdkb'''</span>]]</span><small>}&#125;</small></span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 17:12, 6 July 2022 (UTC)</small> == Wide-column + Multi-column options for large screens == Readers vary in what form factor they prefer, especially for long-form high-volume reading. That's part of why this change and research into 'optimal layout' is controversial. I'm someone who finds it hard and slow to read a narrow column and have to scroll all the time, including when searching a page for a term. General feedback on width: # Include a comfortable default for large screens. The (potentially large) gray margins on left and right, outside large white margins, bracketing a forced-maxwidth central column, do not feel good. Wide-col or multi-col could work. # Offer an explicit wide-column pref that doesn't require people to change skins, even if that is less aggressively supported/tested across all platforms. # A multi-column design for text within sections – mimicking the style of most long-form magazines and scholarly journals – would be interesting and can be surpassingly beautiful. That's what I'd like to see our wide-screen layouts transition to. We already do this within sections for references, lists, and galleries. Even low-end desktop monitors these days are high enough resolution to support two-column layouts. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 18:20, 2 May 2022 (UTC) == I think sticky elements ruin Vector == I liked vector a lot more when it didn't have the new distracting elements (sticky header and sticky TOC). ''I care about the contents of the page, not the interface'', nor about the need to scroll to the top of the page every now and then. [[User:Tokujin|Tokujin]] ([[User talk:Tokujin|talk]]) 17:50, 4 May 2022 (UTC) :Hello @[[User:Tokujin|Tokujin]]. Congratulations for finding this page :D You can add <code>.vector-sticky-header {display:none;}</code> to your [[metawiki:Special:MyPage/global.css|global.css]]. For now, I'm not entirely sure what to advise about the TOC, though. When the collapsible version has been deployed, we'll know what code you should use to make it not sticky and keep some other version. I invite you to revisit this topic in 2-3 weeks. :By the way, I very much liked the first sentence of [https://www.mediawiki.org/w/index.php?diff=prev&oldid=5009784 your comment to the third prototype]. Have you seen the [[Reading/Web/Desktop Improvements/Fourth prototype testing|fourth one]]? I encourage you to follow the instructions and share your opinion about it, too. (BTW, compare it with [https://di-collapsible-menus.web.app/Brown_bear the newest version, also a prototype].) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:28, 5 May 2022 (UTC) ::Hi Szymon :-) [[Reading/Web/Desktop_Improvements/Fourth_prototype_testing/Feedback#Username%3ATokujin|Done]], thank you. Regarding the global.css setting, notice that with sticky table headers enabled (in Preferences > Gadgets > Testing and development) there's a bug whereby in tables such as those in [https://en.wikipedia.org/wiki/List_of_Disenchantment_episodes#Part_4_(2022) this page] the table header leaves space for the absent page header. Other tables, such as that [https://en.wikipedia.org/wiki/Ninety-nine%20Novels here], don't have this issue. [[User:Tokujin|Tokujin]] ([[User talk:Tokujin|talk]]). 07:41, 9 May 2022 (UTC) == Skin differences between wikis == I'm using the 2022 Vector skin globally now (with [[:m:User:Tol/global.css|some modifications]] to remove whitespace), but I'm noticing that some wikis' sidebars are different from others. For example, MediaWiki wiki (this wiki) and French Wikipedia have a thinner white-background sidebar which sits on top of the page body (and ToC in the page body), while Meta-Wiki, Wikidata, and English Wikipedia have a wider grey-background box which is not layered on top of the page body (and ToC beneath said box). I can't figure out why this is. [[User:Tol|<span style="color:#f542d7">Tol</span>]] ([[User talk:Tol|talk]] &#124; [[Special:Contribs/Tol|contribs]]) @ 00:12, 8 May 2022 (UTC) :@[[User:Tol|Tol]] - thanks for your question, and good catch! This is due to the table of contents still needing to being A/B tested on some wikis (frwiki and mediawiki wiki being two of these). The ToC functionality is not yet available there. That said, we've began some work on reducing the margins for the ToC as a whole ([[phab:T307004]]) that will make the differences in width fairly negligible. This change will be on all wikis next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:31, 9 May 2022 (UTC) ::@[[User:OVasileva (WMF)|OVasileva (WMF)]]: Ah; looks great! I look forward to that change rolling out. Thanks! [[User:Tol|<span style="color:#f542d7">Tol</span>]] ([[User talk:Tol|talk]] &#124; [[Special:Contribs/Tol|contribs]]) @ 14:14, 9 May 2022 (UTC) == Tool bars and tables == Hi, thanks for the update. A few observations: # I would suggest that users have the option to keep the tool bar on the sidebar from the beginning, instead of having to click "tools" -> "[move to sidebar]" every single time. # The readability of tables and graphs that are wider than the (quite tight) text column is an issue. In certain cases, the tables represent time series data (e.g. population in a country or municipality over time) that cannot just be tightened. Do you have a proposal to solve this issue? The NYT, which is a site that you explicitly mention as inspiration, lets tables and images occupy the whole width of the screen if necessary. [[User:GeneraleAutunno|GeneraleAutunno]] ([[User talk:GeneraleAutunno|talk]]) 20:39, 8 May 2022 (UTC) == Next steps for the Table of Contents == Hey all - thank you for all the feedback around the issues you were experiencing with the ToC, especially on narrow screens. We've taken a few steps to fix some of these issues: * We're reducing the margins of the ToC to more closely resemble those of the prototype (tracked in [[phab:T307004]]) * We have a temporary solution for the ToC at narrow widths, which removes the ToC alltogether * We are building functionality to allow for the ToC to be collapsible and expandable at narrow widths (tracked in [[phab:T306660]]) * We are planning on making the ToC collapsible at all screen sizes and widths (tracked in [[phab:T307901]]) * https://di-collapsible-menus.web.app/Brown_bear links to a prototype that puts all of these changes together. We would appreciate your feedback and thoughts on the decisions made within the prototype and whether they work for you. Thanks! [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:38, 9 May 2022 (UTC) :cc @[[User:Lectrician1|Lectrician1]], @[[User:Alexis Jazz|Alexis Jazz]], @[[User:Autokefal Dialytiker|Autokefal Dialytiker]], @[[User:Tenryuu|Tenryuu]], @[[User:Tucvbif|Tucvbif]], @[[User:Tokujin|Tokujin]] - in case you're interested. Apologies if I'm forgetting anyone else that was asking about this! [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:46, 9 May 2022 (UTC) ::[[User:OVasileva (WMF)|OVasileva]], thank you, it's a solid improvement! Just one request: can the hiding/unhiding be made persistent so my choice remains in effect even if I navigate to another page? <span id="Alexis_Jazz:1652099702223:TalkBWLCLNReading/Web/Desktop_Improvements" class="BawlCmt">[[User:Alexis Jazz|Alexis Jazz]] ([[User talk:Alexis Jazz|talk]]) 12:35, 9 May 2022 (UTC)</span> ::Thank you, that's good news! (Adding a clarification: I'm responding to OVasileva, here.) My thinking is that making it collapsible is the only reasonable way to go; with the added point that for newcomers and anonymous readers it should perhaps be turned "on" as default; if the collapse button is clearly visible, the TOC will be useful to some, and easily removable for the rest, which should be the useful level of the intrusive/invisible conundrum... Thank you, once again. [[User:Autokefal Dialytiker|Autokefal Dialytiker]] ([[User talk:Autokefal Dialytiker|talk]]) 13:02, 9 May 2022 (UTC) :: @[[User:OVasileva (WMF)|OVasileva (WMF)]]: Thanks for letting me know. Since this seems to be only in effect for the new Vector skin, maybe some work could be done to have the table of contents be shown in focus and have a button on the sticky header, as well as a keyboard shortcut for it? [[User:Tenryuu|Tenryuu]] ([[User talk:Tenryuu|talk]]) 14:07, 9 May 2022 (UTC) :Thanks for the work, I like the prototype a lot. I've missed the easily available overview that the ToC provides. Compare to the 2010 design, it is very useful to have the ToC available no matter how far down you scroll. :On small screens, the "move to sidebar" link text is not accurate with regards to what happens visually when you click on it. [[User:PeterTrompeter|PeterTrompeter]] ([[User talk:PeterTrompeter|talk]]) 16:51, 11 May 2022 (UTC) :On narrow screens this is still quite jarring, and having no TOC is a loss, being able to move the TOC back in to the body (dynamically and programmatically) seems a better compromise. A problem I see is that even when there is no TOC on a page, all that space it could use is still being consume by blank space, that wasted horizontal space needs to be able to be reclaimed somehow. We've been testing some options that are aimed at more power desktop '''editors''' so they can use vector-2022, but still have access to most of their screen (see [https://en.wikipedia.org/wiki/Hate_%C3%9Cber_Alles?useskin=vector-2022&withgadget=wide-vector-2022 example] (will really only be strikingly noticable if you are on a wide screen)) but still are getting complaints about the huge space used by the TOC. [[User:Xaosflux|Xaosflux]] ([[User talk:Xaosflux|talk]]) 11:40, 14 May 2022 (UTC) == Banners and roadmap == Hi, I think you should consider to add banners in order to present the restyling to a much wider part of users. IMO they should link to discussion and presentation pages. You should also consider to present to the wikis a clear roadmap with dates in order to present ahead of time big changes like the adoption of the new Vector. This two changes would make you work clearer to the eyes of the users and would prevent some dissatisfactions.<small> In particular I'd like to point out that [[:it:Wikipedia:Bar/Discussioni/La_nuova_interfaccia_desktop|what is happening on itwiki]] is being perceived as an imposition against the general consensus and I agree with the Italian users that are saying that forcing the adoption of the new skin is not the right way to act. These two are some ideas to widen the discussion, forcing something against the will of most will just radicalize the opposing positions even more.</small> -- [[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 11:44, 9 May 2022 (UTC) :<small>I just received the good piece of news that the adoption of the new skin has been delayed for itwiki and I thank you for this. But I still think that the two ideas that I presented above would be good tools to prevent something similar to happen again. ----[[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 11:58, 9 May 2022 (UTC)</small> :Thanks @[[User:WikiLuke|WikiLuke]]. These are great suggestions. :* Banners - [[phab:T304839|T304839]] - we've been working this for some time. Soon, the banner should be visible to some logged-in Vector users. They will be encouraged to switch to the new skin, and some time later, they'll see another banner with a link to this talk page. :* Links to the project page - [[phab:T307113|T307113]] - our idea was similar. We'll add a link to the list of skins in preferences. :* Roadmap - that's also a very good point. We'll consider how to present this to the community most effectively. :* Itwiki - we'll continue this topic on itwiki, alright? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:33, 9 May 2022 (UTC) ::Thank you for you consideration! :) <small>And speaking of itwiki of course we will continue the topic right there.</small> -- [[User:WikiLuke|WikiLuke]] ([[User talk:WikiLuke|talk]]) 16:14, 9 May 2022 (UTC) == Sticky header 'dead zone' in articles with long lead sections == {{tracked|T307345}} Steps to reproduce: # Visit an article with at least a moderately long lead section (e.g., [[en:Charles de Gaulle]]). # Scroll down a little way. # Observe that the sticky header appears. # Scroll down a little further, so that the first heading appears, but not much further than that. # Observe that the sticky header vanishes. # Scroll down even further. # Observe that the sticky header re-appears. This does not seem like intended behaviour. I am testing on Firefox 100. [[User:FrankSpheres|FrankSpheres]] ([[User talk:FrankSpheres|talk]]) 04:14, 10 May 2022 (UTC) :Hi @[[User:FrankSpheres|FrankSpheres]] - thank you for your report! We already have a fix for this bug, tracked in [[phab:T307345|T307345]]. It will be available early next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 08:11, 10 May 2022 (UTC) == Feedback on new look == I like that stuff that is generally rarely used is hidden, such as the language picker. I am not a fan of moving the table of contents off the main article body section. I didn't even register that the table of contents was there and I frequently use the TOC to get an overview of interesting sections of articles. With the TOC being isolated at the side bar, it seems separated from the article itself, while it should be a central part. Maybe it would work better if it appeared on the right of the article, where there is currently just whitespace? Speaking of whitespace: I dislike the move to a max-width on article pages. This feature should at the very least be toggle-able with a button (without a need to log in). I feel like it makes the article feel more cramped, with less space for images and figures. There is already a very good solution to setting the effective width in the old view: Simply resize your window or zoom in on your browser. With the new look, I am forced to a max-width and I don't have a solution to control the width like I did before. Whitespace and the TOC did something beautiful together in the old look actually. The TOC conveniently visually separated the article lead section from the rest of the article by introducing white space, which I personally found very pleasing. The new look has the lead section blend in with the rest of the article. This makes the lead appear more daunting, while its purpose is to serve as a quicker summary. Perhaps the lead section should be followed by a larger piece of whitespace than is normally found above headings, so as to separate the lead from the rest as before? Finally I am quite sad to see that the Wikipedia globe logo is diminished - I really like the globe with the symbols and it doesn't look very good at low resolutions. I think the size of the globe was perfectly fine before. Besides, it seems there's plenty of space for it to have the same size as before so I'm kind of puzzled why this change was made in the first place. I will also say that the arrow next to the Wikipedia globe (the one to minimize the side bar) leads to an unfortunate usability flaw. I initially thought the arrow was supposed to take me back to the front page (it is right next to the logo and the leftward direction suggests a "back" action). But that is not what it does at all. So the arrow is kind of confusing at first. --[[User:SorteKanin|SorteKanin]] ([[User talk:SorteKanin|talk]]) 16:40, 13 May 2022 (UTC) == When testing the new skin, offer a one-click way to change back == The banners inviting users to test the new skin offer a one-click option that updates your skin to new Vector. The banner is then replaced with a message saying "give us feedback!", but it should also offer a one-click way to revert the change. Users may not be familiar with how to undo the change. [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 12:56, 14 May 2022 (UTC) :The one-click option to revert is the final item of the sidebar's top section, in bold. Are you suggesting a second method should be included, or that the link should be made more obvious and flashy by moving to the banner? :The sidebar link seems fine to me. Particularly because this is less about the theme and more ergonomics for migration. [[User:Kees Person|Kees Person]] ([[User talk:Kees Person|talk]]) 15:34, 14 May 2022 (UTC) :: I found it eventually, thanks. Yes, putting it in the banner, or putting a js link in the banner that highlighted the sidebar link, would be clearer :) [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 19:59, 20 May 2022 (UTC) == Too little space == It's probably fine for those who don't use wide-screen monitors, but as someone who does it is quite annoying having everything mushed together like on mobile. I have read the page on this, but I think there should be a way to keep the functionality of the skin but lengthen the screen. [[User:Lallint|Lallint]] ([[User talk:Lallint|talk]]) 13:57, 14 May 2022 (UTC) : I concur. I tried the new skin a couple of times and just could not do it. I have bought a standalone monitor for a reason - and it's not that large anyway (1920 x 1200) - yet the new skin wastes a third of my screen space. [[User:Kashmiri|Kashmiri]] ([[User talk:Kashmiri|talk]]) 12:31, 20 May 2022 (UTC) ::Actually I use a 13" laptop and I initially thought that my computer switched to mobile version by mistake, but I later realized that was the desktop layout. I think the way everything is squeezed-in together takes away from the experience; there is nothing wrong with the header and tools bar they look fine to me, yet the sizing seems off for desktop users. [[User:Humanized|Humanized]] ([[User talk:Humanized|talk]]) 10:20, 24 May 2022 (UTC) == Sidebar too long == Sidebar too long and page too small on Wikimedia wikis [[User:LisafBia6531|LisafBia6531]] ([[User talk:LisafBia6531|talk]]) 16:24, 14 May 2022 (UTC) == Do not use a sticky header. == I think the new layout makes much better use of whitespace on 16:9 displays, making paragraphs easier to read. However, vertical space is someone no website that serves text-rich pages to users can ever get enough of. I believe that every (non-redundant, e.g. the article name is displayed twice on most browsers in the window tab title and the sticky header) element currently placed on the sticky header would not just fit on the sticky sidebar, but by removing the sticky header the layout will better serve what readers come to a wiki to do. As a side note though, I am awfully sentimental about the old Wikipedia header logo and type layout, that giant globe and the accompanying text beneath it is far too iconic to change in my opinion, even for a redesign. [[User:Saedes|Saedes]] ([[User talk:Saedes|talk]]) 14:18, 15 May 2022 (UTC) == Sidebar considerations for vertical monitors/half-width windows == I haven't tested this out thoroughly yet, but I'm going to be adding this section to start a discussion on how the new layout uses responsive design when display device/window aspect ratios are greater in height than width. [[User:Saedes|Saedes]] ([[User talk:Saedes|talk]]) 14:28, 15 May 2022 (UTC) == The table of contents is in the wrong place == It's nice to have a table of contents right there on the side so you can move back and forth between sections but i don't like the fact that you have to scroll down a bit to find it. If there's a way to keep it at the top of the page so you see it right as the page loads then as the user scrolls down it changes into a sticky header, that would be better. [[User:Abhaypradjha|Abhaypradjha]] ([[User talk:Abhaypradjha|talk]]) 10:04, 16 May 2022 (UTC) == Search bar UX is inefficient (Fitts's law) == I want to search. # If I am at the top of the article, I click mindlessly anywhere on the header and type straight away. # If I am down the article, I have to pinpoint an icon. This is bad because * The inconsistency turns my muscle memory against me * It goes against [[w:en:Fitts's_law#Implications_for_UI_design|Fitts's law]]: pinpointing an icon requires precision and is slower than clicking a large bar at the border of the screen without giving much thought into it. A solution would be that clicking on the article title or empty space in the sticky header hides the article title and displays the search bar (empty and focused). My case is that I often read the documents with the help of Wiktionary, so I use the search bar heavily and my usage pattern is fundamentally different than on Wikipedia. On Wiktionary, the interesting information is on one line or two, for each one of many unrelated entries, so searching is almost exclusively my means of navigation. [[User:Wanlpz|Wanlpz]] ([[User talk:Wanlpz|talk]]) 19:05, 17 May 2022 (UTC) == TOC: the position of the content == Hi, I like your [https://di-collapsible-menus.web.app/Brown_bear last prototype of TOC], in particular the blu color which helps to find a menu when you collapse it. I notice something I consider a bug: when the TOC is collapsed, if the tools menu is collapsed too the content is in the correct position, but if you move to the sidebar the tools, the content changes his position (it shifts on the left side). It feels strange. It doesn't happens when the TOC is on the sidebar, and you open/collapse the Tools menu.--[[Special:Contributions/151.42.0.114|151.42.0.114]] 13:17, 18 May 2022 (UTC) ==Sidebar== The sidebar has extended a bit (and by that, I mean a LOT) too far, which makes things very uncomfortable for me. I'm fine with the skin other than that, but the overintrusive sidebar is just awful. Plus, there are these white extensions to it that shouldn't be there. I hope you understand what I'm talking about, and at least take notes on it! [[User:ARandomPage|ARandomPage]] ([[User talk:ARandomPage|talk]]) 11:33, 19 May 2022 (UTC) == Зробіть для кожного коментатора окремий відділ == '''Привіт я досі не можу зрозуміти чому кожен коментатор не може писати окремо це набагато зручніше...''' '''Новий дизайн набагато простіший в візуальному плані але до нього треба звикати)))''' '''Також я побачив що новий дизайн не працює в деяких мовах''' [[User:Ilolg|Ilolg]] ([[User talk:Ilolg|talk]]) 14:34, 19 May 2022 (UTC) == Some incoherence == Hey there! To begin with, I want to make it clear I've got nothing against updating the desktop experience at all. I wanted to make it clear in case I seem like a person ranting something like, "Give me back my good old skin!121". What I think is that by making the skin you folks tried to reconcile the legacy appearance with some modernity. A good point, though the effect is not as optimistic. The top buttons (edit & history & etc) that retain the legacy shadowing do not fit in with the new cohesive background as seen in the left-hand sidebar. I'd consider re-adapting the former so that they better suit the new design. [[User:Mustafar29|Mustafar29]] ([[User talk:Mustafar29|talk]]) 10:05, 20 May 2022 (UTC) == A few more issues with the Page header vs Sticky header icons == Premise: I agree with the comments above that an update can only be a good thing; I'm sending kudos to all the teams working behind the scenes; and I only started using Vector 2022 a few weeks ago - noticing that it gets better each day. I'm not sure if the issues I'm having are slated to be improved or are haven't yet been considered. 1. Lack of coherence in the sticky header iconography I frequently work on the special pages where the sticky header is absent which makes it frustrating when I move to another page (article page) and it appears and then back to 'edit' or 'view the history' of a page and it disappears again. I feel that I should be able to move from page type to page type without noticing drastic changes in the header. 2. Order of icons and functionality is different between the sticky header and page header - specifically some items disappear completely, some move from one area to the next and others are simply re-ordered. (Until just now I thought the search bar had been remove but I just found it as an icon that was pushed to the extreme left hand side after the article title. Now I understand the others who said that with a 27" monitor the left side icons are essentially out of sight.) [[file:Headers-sticky-vs-page.jpg|600px]] * Examining the two headers more in detail we see that the icons seem to be in the same place which makes it hard to notice they are different. Starting from the right, we see that the icons are identical in both therefore, we naturally expect the two (people) dropdown menus to contian the same items. * Moving towards the left we see two icons with a star which pertain to the same semiotic sphere yet actually have different functionalities. One icon (that looks like a drop down menu but isn't) takes you to your watchlist while the other simply indicates whether the current page is on your watchlist and fuctions as a toggle to add the page if it isn't. There is a futher issue with how similar this icon is to the 'Contributions' icon, making it hard to distinguish for those of us who have bad eyesight - but that is an issue for another post. * Continuing to the left, the issue becomes more confusing. 'Your notices' from the page header disappears (or maybe I just haven't found it yet) and the text menu 'View history' moves into the sticky header as an icon -the tool tips are the same in both and they are basically in the same position onthe page, which helps a bit. * And with the final icons (still moving left) the 'Your alerts' bell disappears (or hasn't been found) and the 'Discussions about this page' transform from a text menu on the left into an icon on the right, at least the tooltip is the same. I have to admit that it's not clear to me why my user name is only visible on the page header and then moves under the person icon in the sticky header. It's not exactly a problem in itself, but it does add to the confusion of icons and functionality that seems to jump around from page to page. * Finally, it seems that the “Edit” and “Edit source” functions have disappeared along with the special menu items of “delete”, “purge” and “move” unless you scroll back up to the top of the page. I believe these issues have already been mentioned by others above. Again a big thanks to all of you working hard to update the interface and the 'restyling'. I hope when this is all finished, the sticky header will be unobtrusive and not noticeable like the ones normally found on modern webpages. --[[User:Lepido|Lepido]] ([[User talk:Lepido|talk]]) 21:07, 20 May 2022 (UTC) == Left menu too wide == The main menu on the left is too wide and makes the rest of the page appear too cramped in relation to the menu. [[User:Urban Versis 32|Urban Versis 32]] ([[User talk:Urban Versis 32|talk]]) 00:02, 24 May 2022 (UTC) == The TOC, again == It just makes all look too narrow and tight, at least to me. I've been working on various lists projects recently and now they all look god awful because they had the old look in mind. [[User:Tintero21|Tintero21]] ([[User talk:Tintero21|talk]]) 02:08, 24 May 2022 (UTC) ==I prefer the old version == It's cool but I prefer the old version. [[User:Super ninja2|Super ninja2]] ([[User talk:Super ninja2|talk]]) 07:18, 24 May 2022 (UTC) == suggestion: collapsible table of contents == the appearance of the site is far too narrow. i would suggest making the table of contents collpasible to the left. [[User:Lettherebedarklight|Lettherebedarklight]] ([[User talk:Lettherebedarklight|talk]]) 12:02, 24 May 2022 (UTC) : Me too. Also could be hidden, in options, so the user can read better the text. Now, it is too narrow and tight. --[[User:BoldLuis|BoldLuis]] ([[User talk:BoldLuis|talk]]) 13:04, 24 May 2022 (UTC) == Line under title colliding with coordinates == {{Tracked|T310369}} [[File:TitleLineColliding.png|thumb|alt=Gray horizontal line under the title colliding with coordinates given on top right of page]] See image. The horizontal line under the title collides with any coordinates that are displayed on the top right. --[[User:MimiKal797|MimiKal797]] ([[User talk:MimiKal797|talk]]) 14:56, 24 May 2022 (UTC) :Even I wanted to state this same issue. [[User:Excellenc1|Excellenc1]] ([[User talk:Excellenc1|talk]]) 16:00, 24 May 2022 (UTC) : Also the floating title can obscure content. For example, open the front page of [[b:Oberon|Oberon]] and scroll to the bottom. Click on instance "a" of footnote 43. That should take you to "MT, in V5, the constant address ...". In fact, the next glossary entry "native, modifies the name ..." is displayed. Not a terrible defect but baffling for a novice trying to learn. Thx, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|talk]]) 00:08, 25 May 2022 (UTC) ::I came here for a MeToo (about the coords/line collision). Classic Vector does not have the problem. Also, I think the languages dropdown is uncomfortably close to the coordinates; if you hover over that button you can see they overlap, which generates cruft when the dropdown is activated. Did anyone write up a ticket? [[User:DavidBrooks|DavidBrooks]] ([[User talk:DavidBrooks|talk]]) 15:35, 9 June 2022 (UTC) - OK, I did: T310369 [[User:DavidBrooks|DavidBrooks]] ([[User talk:DavidBrooks|talk]]) 15:19, 10 June 2022 (UTC) :::This is being discussed in [[:en:Template talk:Coord#Coordinates bad positioning]]. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:32, 10 June 2022 (UTC) == Great GUI == Everything looks very appealing to me. I think the blank left space really aids in reading as the width of the line reduces its easier for me to not to confuse the line which I have to read next. Overall I loved it. One suggestion that I want to give is that it would be very nice if you could change the visual of the tab. It looks a little too classic to me and would be very nice of you if you could add dark mode ( I don't know if it already exists), this I think would give a very appealing look to the website . Thank You. [[Special:Contributions/]] 17:59, 24 May 2022 (UTC) : If you ever want to reduce the width of the lines you are reading, I suggest you just resize your window, as the elegance of desktop browsing is that it gives you control over the size of the page. As for me, this layout takes away that control. Using it, I can no longer read an article with the full width of my screen without fiddling with my common.css, a luxury that would not be available to me when I'm not logged in, and am instead forced to use ~2/3 of that width, even when the window is reaching into every corner of my screen. There are several ways of using dark mode on wikipedia listed [[wikipedia:Wikipedia:Dark_mode|here]], but I agree it should be made easier. --[[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 16:42, 25 May 2022 (UTC) == Feedback == I was prompted to give some feedback on the 2022 Vector skin, and I have to say that it needs a bit more work. * The mix of new and old UI elements doesn't look good; specifically the View, Edit, Edit Source etc. menu bar looks out of place among the flatter new UI * There's uneven and unnecessary padding around the left pane with the many links that can be filled with the pane * There should be an option to have the content filling any display larger than 4:3, as most displays are 16:9. I understand the argument that it helps some people in reading but having an option is better, as it doesn't help ''all'' people. Additionally, a poll should be run in all Wikimedia projects on which one should be the default (4:3 or full width) — [[User:Dimsar01|Dimsar01]] ([[User talk:Dimsar01|talk]]) 23:33, 24 May 2022 (UTC) Here is My feedback *I see that the sections are not properly sectioned on the screen *I am using dark mode and when I want to add reference or qualifier or something like that, I see a white suggestion screen All in all I can say for now is that I really needs more work done and I can prefer the older one for now thank you [[User:Micheal Kaluba|Micheal Kaluba]] ([[User talk:Micheal Kaluba|talk]]) 05:58, 26 May 2022 (UTC) == Short description == It would be great to have the short description visible on pages, like it is on the search and on mobile, so users can more easily edit them and identify information. Like said by other users, the mix of new and old UI looks bad. The [https://di-article-tools-2.web.app/Blue_whale most recent prototype], for all its faults, had a well unified UI. I also think that the page tools (and "In other projects") should be separated from links for the whole website like was done in the [https://di-article-tools-2.web.app/Blue_whale most recent prototype], though there were many flaws with that execution (see [[Reading/Web/Desktop Improvements/Fourth prototype testing/Feedback#User: BappleBusiness|my comments]]), and all those links should be condensed by default. "Beginning" should definitely be named "Lead" or "Lead section", like said by others. I really appreciate the effort that is going into this. I think the vast majority of these changes are for the better, it just needs more work. [[User:BappleBusiness|BappleBusiness]] ([[User talk:BappleBusiness|talk]]) 00:32, 25 May 2022 (UTC) == Software Gore == [[File:Languages on Wiktionary with new layout.png|thumb|Software gore]] This is pure software gore. If you want to explain to me why it's like this, you're wasting your breath. I've edited Wiktionary for over a decade and I understand how it's come to look like this, and I don't even have a solution to propose. But I feel terrible for anyone trying to navigate this mess for the first time. —[[User:Pengo|Pengo]] ([[User talk:Pengo|talk]]) 00:54, 25 May 2022 (UTC) == Watchlist tooltip == Hi folks! I'm vaguely used to the watchlist icon (since I've switched themes many times over the past decade or so, and use the mobile app/website), but I still need to resort to the tooltips when I'm on my desktop. It would seem I'm not the only one that takes a moment to mentally translate the icon to the concept in my brain (per {{ping|Nardog}}'s earlier [[#Watchlist icon]] comment). I may stay with "Vector 2022" over on [[commons:Main_page|commons.wikimedia.org]] after trying it out for a bit, but please: could y'all change the tooltip so that the word "watchlist" is in the tooltip? Currently, the icon sports the the very verbose tooltip: "''A list of pages you are monitoring for changes [Alt+Shift+I]''", which takes a moment for me to mentally translate into "''oh, they're trying to say 'Watchlist'!''". It would be helpful if (in addition to the keyboard shortcut), the tooltip also gave the mental shortcut, perhaps with the phrase: "''Watchlist: your list of pages to monitor for changes [Alt+Shift+I]''". Since I'm guessing y'all aren't changing "watchlist" to another word, I can imagine it would be helpful for new users too. -- [[User:RobLa|RobLa]] ([[User talk:RobLa|talk]]) 04:12, 25 May 2022 (UTC) :Yeah, given all the other tooltips are just "Your alerts", "Your notices", and "User menu", it seems to me it should be simply "Watchlist" or at best "Your watchlist". [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 04:22, 25 May 2022 (UTC) == I want the code to make the sidebar TOC disappear == Please. Ping me. [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 05:46, 25 May 2022 (UTC) It's probably not too hard since there seems to still be a {{tag|mw:tocplace}} element left -- you need to grab the element, move it back and do some style fixups. Kinda like [[w:zh:User:Artoria2e5/Gadget-sidetoc.js]] but backwards. --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:43, 26 May 2022 (UTC) Ah well, I am pretty convinced that having {{tag|mw:tocplace}} but not the actual TOC hidden there is a bug now. If that gets fixed, it should be just some CSS work in your vector-2022.css: <pre> #mw-panel-toc {display:none;} #toc {display:block;} </pre> May need to sprinkle on a bit of !important. ping [[User:Bageense|Bageense]] --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:55, 26 May 2022 (UTC) :Yep, TOC disappeared, leaving a blank space. [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 16:55, 26 May 2022 (UTC) ::Well, just gotta wait until they come to their senses. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 00:55, 27 May 2022 (UTC) == Space for article too narrow == The article took up less than the full width of the screen in the old skin, but the increased padding and needlessly wide sidebar here make the usable region even smaller. This just reproduces the issues that have had to be worked-around on mobile, including some tables being too wide to fit in the space and causing horizontal scrolling, creating the need to scroll further to get between sections, as well as causing some large image thumbs to squish the article text into narrow strips. In my opinion, the sidebar, which I think most readers rarely make use of anyway, should be consigned to a modal rather than taking up even more space, so that the article can appear centred all the way down the page. This would make room for fairly wide margins on either side without causing as many issues. (I suggest this because it seems the most noticeable "improvement" here is the addition of extra whitespace, but really, what is wrong with making full use of the window width you are given?) [[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 15:50, 25 May 2022 (UTC) : I came here to complain about the same thing - limiting the width of the pageview doesn't make sense when you have a lot of text to display. Especially the discussions became harder to read. [[Special:Contributions/78.11.223.83|78.11.223.83]] 06:29, 26 May 2022 (UTC) == TOC should make the page slowly scroll to the right section, and not just jump == By the way, I'm still waiting for the code necessary to deactivate the lateral TOC. I've already disabled the sticky header by using .vector-sticky-header {display:none;} [[User:Bageense|Bageense]] ([[User talk:Bageense|talk]]) 07:51, 26 May 2022 (UTC) :That would make it take longer to get where you want to be, and prevent the user from scrolling during the time the page is sliding. The current TOC works using anchors linked to IDs, which means you can get back to where you were by simply paging back, but this, I think, would not be possible if the links were actually buttons triggering JavaScript animations. [[User:SmallJarsWithGreenLabels|SmallJarsWithGreenLabels]] ([[User talk:SmallJarsWithGreenLabels|talk]]) 08:14, 26 May 2022 (UTC) == TOC not appearing at all == It seems that Vector 2022 is not showing ''any'' TOC -- neither the regular one nor the side one -- when it probably should. I noticed this issue about a couple of days ago but assumed it was an error on my side. Today I checked out [[w:Dmitri_Shostakovich]], tried to add a <code>_<nowiki>_TOC__</nowiki></code> magic word, found out it does nothing, and then realized it's the skin that's broken when I retried in a logged out private tab. In a private tab: * https://en.wikipedia.org/wiki/Dmitri_Shostakovich?useskin=vector-2022 has no TOC right now, but * https://en.wikipedia.org/wiki/Dmitri_Shostakovich?useskin=vector has a TOC. What's going on here? [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:35, 26 May 2022 (UTC) :One refresh later it's showing the side one. I must be descending into some sort of madness. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:37, 26 May 2022 (UTC) ::Annd it's gone again. No outstanding errors in the console. Seems to be sone <code>@media screen { ... .sidebar-toc {display:none; ...</code> in one of the many load.php's ([https://en.wikipedia.org/w/load.php?lang=en&modules=ext.cite.styles%7Cext.echo.styles.badge%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cjquery.makeCollapsible.styles%7Cmediawiki.ui.button%2Cicon%7Coojs-ui.styles.icons-alerts%7Cskins.vector.icons%2Cstyles%7Cwikibase.client.init&only=styles&skin=vector-2022]). What. the. heck. [[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:48, 26 May 2022 (UTC) ::The intention of the code seems to be to show the sidebar only for screens wider than a value. That's a good idea, but only if the original TOC is not removed! --[[User:Artoria2e5|Artoria2e5]] ([[User talk:Artoria2e5|talk]]) 11:50, 26 May 2022 (UTC) == Bold, yet very appreciated changes == At first I didn't like it. My first thought was that it took more space, so I got less content in my screen. I compared it side by side with the old skin and in fact, elements got more margin. But after giving it a try, reading and moving through the article, I fell in love. I really like that the TOC is now on the left and moves along with the page. It was OK before but now it feels fancy. And I feel more people are going to benefit from it now. The cleaner, more "plain white" look is nice. I understand the decision of limiting the width of the page on (very) wide screens. In my opinion, it is a sensible design decision that improves readability. Because if lines get too wide, it can make it harder to read. Maybe this "max-width" setting can become a thing users can tweak? I tested this new skin on a modern computer and a 1440p screen. If I were to use my old laptop, I'm sure I'd like to have the option to change to the old skin. As it fits more content and uses less CPU resources. I appreciate this changes, and feel they are for the better. Thank you! -- [[User:Zazke grt|Zazke grt]] ([[User talk:Zazke grt|talk]]) 06:42, 27 May 2022 (UTC) : I've temporarily switched back to the old Vector skin in Wikipedia because some pages like this one [https://en.wikipedia.org/wiki/Portal:Video%20games Wikipedia:Portal:Video_games] have their contents very croped or overflowing their boxes. --[[User:Zazke grt|Zazke grt]] ([[User talk:Zazke grt|talk]]) 06:49, 28 May 2022 (UTC) == TOC not immediately visible == {{Tracked|T309632}} I am going to refrain from complaining too much as I'm prone to do with any and all UI changes :) However, I do find the placement of the TOC particularly problematic. Personally the first thing I do when landing on a Wikipedia article is, usually, click on something in the TOC. Having to scroll down first to find it is, to me, very frustrating. [[User:Argymeg|Argymeg]] ([[User talk:Argymeg|talk]]) 12:24, 27 May 2022 (UTC) == Better font for Arabic/Persian فونت بهتر برای فارسی/عربی == As a Persian user, I think font of wikipedia is not good for these languages; Maybe Vazirmatn or other open-source good looking fonts could be better. به عنوان یک کاربر ایرانی، من فکر می‌کنم که فونت ویکی‌پدیا برای فارسی و عربی جالب نیست؛ شاید وزیرمتن یا سایر فونت‌های منبع‌باز که ظاهری خوبی دارند انتخاب‌های بهتری باشند. [[User:Amiria703|Amiria703]] ([[User talk:Amiria703|talk]]) 22:27, 27 May 2022 (UTC) == It seems like the Page Previews isn't working for me here == Although the new skin looks more sleek, I can't use the (very useful) feature of Page Previews here. So every time I'm in for a deep read, I have to switch back to the old look. Please implement the page previews here too. [[User:SamyakShirsh|SamyakShirsh]] ([[User talk:SamyakShirsh|talk]]) 03:31, 29 May 2022 (UTC) :Hi there! Thanks for the report! Could I get some more information on this issue? Page previews is working for me on both Vector and Vector 2022 skin. Are you talking about the user gadget https://en.wikipedia.org/wiki/Wikipedia:Tools/Navigation_popups ? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:28, 1 June 2022 (UTC) == Use the white page on the right for TOC and navigation == The mobie version of wikipedia app has this really nice way of navigating through sections by swiping eight. I think you can imlement this in the desktop by placing the toc on the right [[User:SamyakShirsh|SamyakShirsh]] ([[User talk:SamyakShirsh|talk]]) 03:35, 29 May 2022 (UTC) == Lone value inside calc() == The style sheet of the new sticky table of contents uses <code>.mw-table-of-contents-container { top: calc(-2em); }</code>. Is there a reason for putting a lone value inside <code>calc()</code>? [[User:Anerisys|Anerisys]] ([[User talk:Anerisys|talk]]) 09:22, 29 May 2022 (UTC) :Thanks for flagging. :The patch introducing this is: :https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/789691/5/resources/skins.vector.styles/layouts/screen.less :The use of calc is accidental, and I think a mix up our end with the appropriate LESS mixin. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:40, 1 June 2022 (UTC) == Trouble With Zooming In == My vision is poor so I usually zoom to 200% on my browser and it is no problem. With the new skin that same magnification causes the sidebar to take up the top of my screen and I can't see the title of the article and know what page I'm on without scrolling. == Opt-in/out for page tools? == There've been a few discussions on this page about the page tools links, but one possibility I haven't seen mentioned here or at [[Reading/Web/Desktop Improvements/Features/Page tools]] is providing a way for each reader/editor to choose which links appear. For example, I use "what links here" quite a lot, "related changes" and "random article" occasionally, and all the others virtually never. Other editors will have different experiences. How about allowing us to reduce clutter by choosing what we want to keep in the menu and what we can do without? [[User:Arms &#38; Hearts|Arms &#38; Hearts]] ([[User talk:Arms &#38; Hearts|talk]]) 19:47, 29 May 2022 (UTC) :+1. I just want to say this was the last straw that made me force legacy Vector on all sites in GlobalPreferences. Is there no opt-out aside from putting <code>tableofcontents=0</code> in the URL? No "Expand all" button? Why is there a blank space beneath the ToC? Why fade it out rather than show as much as possible? This is just user-hostile. [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 16:16, 31 May 2022 (UTC) == Tabs misaligned? == The tabs on the left seem to be next to the tabs on the right, as depicted [https://imgur.com/UfeemZ1 here]. This wasn't the case last week; should this be reported here or elsewhere? Please move if need be. [[User:Ifly6|Ifly6]] ([[User talk:Ifly6|talk]]) 07:01, 31 May 2022 (UTC) :: Hi there, could I get a little more information on this one? What browser and device are you using? Are you viewing this on a mobile phone by any chance? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 21:23, 1 June 2022 (UTC) == TOC hidden for some reason == {{Tracked|T309632}} When I put my Wikipedia tab to one side at half-width, which I often do whilst multitasking, the TOC disappears for some reason, even though the other side menu (which is the same width as the TOC) stays? I am clueless as to why. All article text is pushed way to the right for some reason. It would make more sense for it to be centred on all screen widths, or to make the entirety of the left menu a solid colour like it was before. Basically, the sidebar should be made thinner as the tab width decreases. Also the lack of a TOC below the lead results in images fighting for space with the infoboxes of articles. There should definitely be an option to move the TOC to where it normally resides as I and likely a lot of other editors find that placement more intuitive. [[User:Miklogfeather|Miklogfeather]] ([[User talk:Miklogfeather|talk]]) 16:06, 31 May 2022 (UTC) :My whole left sidebar has disappeared this morning. I had to switch themes just to get some editing done. — [[User:Xenophore|Xenophore]] ([[User talk:Xenophore|talk]]) 19:42, 6 June 2022 (UTC) == My many criticisms with this == Since it seems like Miraheze is also going to be using this new Vector skin as its default, I would like to offer mine and a lot of other users' criticisms with this new skin: * First of all, the unnecessary dead space. The actual content space is now more narrow and there is a ton of dead space. * The user menu is now completely messed up. The log in button and talk and contribution buttons are hidden behind the three dots, even though those are the most important buttons and should be readily available. In fact, there is no need for anything to be hidden. * The giant TOC in the sidebar. It serves no purpose and just further limits content space. I fail to see how exactly this is an "improvement". Also, the current layout of the skin looks nothing like what is described on the page. There is nothing about a smaller user menu. Currently, the new skin just feels off to me, and I would prefer that this skin be currently branded as "experimental", since it is far from finished. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 21:41, 5 June 2022 (UTC) :I'm fine with everything except the user menu changes and content width changes. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 21:50, 5 June 2022 (UTC) ::Hello @[[User:Blubabluba9990|Blubabluba9990]]. Have you maybe read our documentation where we present the reasons why particular changes are needed, why we've introduced the limited width, and what we're taking into consideration regarding how to use the unused space? I invite you to explore [[Reading/Web/Desktop Improvements/Features|this page]] and its sub-pages. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 19:11, 8 June 2022 (UTC) :::I already did. I read through them more thoroughly and while some seem like a good idea on paper, the user menu and limited width do not really seem to be an "improvement", as there are now extra steps involved. The user menu is the most important thing for me and many users, and now I have to click on a separate button to log in. Maybe less limited width, since right now 1/4 of the screen is just empty space with the new skin. I still use the original Vector as my personal default, but I usually browse logged out. [[User:Blubabluba9990|Blubabluba9990]] ([[User talk:Blubabluba9990|talk]]) 22:40, 8 June 2022 (UTC) == Wikistories == Will Vector 2022 be influenced by [[Wikistories]]? --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:09, 6 June 2022 (UTC) :@[[User:NGC 54|NGC 54]], what do you mean by influenced? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:18, 14 June 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: If Vector 2022 will be adapted for (compatible from a design perspective with) Wikistories. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:06, 15 June 2022 (UTC) :::@[[User:NGC 54|NGC 54]], definitely. All the projects that currently are being built are compatible with or neutral to Vector 2022. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:47, 30 June 2022 (UTC) == Visibility Suggestions == Hi, first of all thanks for the work and the nice redesign. I really prefer it over the old vector look already. I use Wikipedia mainly to get an overview or better intuition about topics related to my studies. For me, I prefer the narrower text for better readability and the persistent TOC on the left side of the screen. Makes reading complex pages a lot less painful with easy access to quick navigation. I have some suggestions for the default behaviour of the current design: * There should be an '''option to collapse the navigation sidebar/area''' by default (the area which contains ''Main page'', ''Contents'', ''Current events'' etc.). I am one of those people who rarely uses any of those links. * More of an issue is due to this: The '''TOC is not always immediately visible as the navigation sidebar pushes it too far down.''' Perhaps move the sidebar to somewhere else or make it collapsible by default as suggested? * Additionally, It '''should be more obvious that the navigation sidebar/area is collapsible.''' Currently the toggle is kind of far and disconnected from the area. I only found this out after wondering what that arrow ''<<'' meant. * A nice addition would be to add '''more obvious indicators for current position in the TOC''' (loved this new feature the most!). I think right now the text of the current headline is just black. It would be cool if there was some highlighting or perhaps a dot to make it easier to see at a quick glance. [[User:Devin.halsted|Devin.halsted]] ([[User talk:Devin.halsted|talk]]) 11:21, 8 June 2022 (UTC) :I just noticed, that the toggling of the '''navigation sidebar/area''' does indeed persist. I just didn't notice because i switched between too many tabs. :Something other I noticed, is perhaps that would be good for '''scrollable TOC''' to be more visibly "scrollable"? Right now there is no indication except that maybe some text is cut off. [[User:Devin.halsted|Devin.halsted]] ([[User talk:Devin.halsted|talk]]) 11:27, 8 June 2022 (UTC) == Fifth prototype testing == :''Moved from [[Topic:Wx2jt9he9u1ipkpb]]'' Nothing about sticky header? The order of icons, the present icons for IPs, etc. [[User:NGC 54|NGC 54]] ([[User talk:NGC 54|talk]]) 17:08, 8 June 2022 (UTC) : Thanks for this comment, [[User:NGC 54|NGC 54]]. As we explain on the [[Reading/Web/Desktop Improvements/Fifth prototype testing|page of the fifth round of prototype testing]], that round will only be dedicated to considerations around the visual design. Pure aesthetics. The order of icons, selection of icons for IP etc., are functional considerations which may be discussed right here, on this talk page, regardless of the 5th prototype testing. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 15:38, 8 June 2022 (UTC) == General Feedback on Sidebar == I agree with other feedback that complains about the sidebar being to wide. This is a waste of space, please reduce the width a bit. However, I think it's not the width of the container but the left margin that makes people (including myself) upset. Therefore, I suggest to completely get rid of the left padding of the main container. Also please reduce the left margin of the article container to just 10 or 20 px. Even more space is wasted if the side bar is collapsed: Why is the sidebar positioned higher than ToC? This leaves free space on top of it. You discussed that the lines of text would be too long otherwise. You could significantly reduce the length if you moved the side bar from the left side to right. You then would have (from left to right) ToC, article, sidebar. Furthermore, the ToC should be on top of the other sections because for most people, ToC is more important than the other links. Although I understand the intention behind this to invite more people to contribute to Wikipedia, I still don't like it. [[User:GeographyMasterDE|GeographyMasterDE]] ([[User talk:GeographyMasterDE|talk]]) 09:16, 9 June 2022 (UTC) == JPG screenshots == Just to point out that [[Reading/Web/Desktop_Improvements|this page]], in which supposed design gurus are offering a lifeline to a wikipedia supposedly plagued by unsofisticated looks, is illustrated with screenshots saved in JPEG format… [[User:Tuvalkin|Tuvalkin]] ([[User talk:Tuvalkin|talk]]) 14:33, 9 June 2022 (UTC) == Limited Content Width == I want to state my opposition the limited content width. I understand the research that the narrower format improves readability. However, there are number of good reasons not to adopt the change: * Yes, [[Reading/Web/Desktop Improvements/Features/Limiting content width#Popular sites with limited width|many sites]] do use fixed width content, but in many cases their motivation is to use the space to sell advertising – a function not befitting Wikimedia. (Some news sites, such as those run by [http://www.gannett.com Gannett] have even taken the theory one step further and display all their articles as overlays – meaning that if a user accidentally clicks in the shadowed area on either side, they are frustratingly taken back to the homepage.) For this reason, full width content suggests a more reputable website. It implies a dedication to the facts, rather than attempting to fill the page with flashy content. (A [http://motherfuckingwebsite.com different website] has a more profane take on the concept. It doesn't deal directly with the issue at hand, but the underlying issue is the same.) This change just seems like another case of mobile overoptimization. * Additionally, as correctly the noted at the [[Reading/Web/Desktop Improvements/Features/Limiting content width#Additional notes|end of the page on the change]] is "part of what makes Wikipedia, and other Wikimedia wikis, a powerful tool for sharing knowledge is that there are very few constraints on how information is presented." For example, it's the reason that widths are specified in "ems" rather than number of columns in the [http://en.wikipedia.org/wiki/Template:Div_col div col template]. Don't get me wrong, I very strongly appreciate the [[Reading/Web/Desktop Improvements/Features/Limiting content width#Establishing a common reading experience|need for a common standard]]. I have [http://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Aviation/Style_guide#Proposed_Aircraft_Manufacture_Aircraft_Section_Table fought for it] on Wikipedia. However, this is not the place for it. * It is clear to me that the majority of commenters here strongly oppose limited content width. It is not to be confused with people just being afraid of change. Note that there are far fewer complaints with most of the other proposed features. I don't have access to the survey results, but a [[Reading/Web/Desktop Improvements/Repository/First Prototype Feedback Report#Summary of results|sample size of 230 users]] seems exceedingly small for such a major change. Furthermore, the commenters here are likely to a better representation of the dedicated portion of the userbase, as they took the time to respond here. I would like to end by stating I am not completely opposed to the change. However, it should only be ''opt-in'', not the default skin. –[[User:Noha307|Noha307]] ([[User talk:Noha307|talk]]) 03:23, 10 June 2022 (UTC) == Width and font size and color == As above, I don't like adding so much margin around the sides, or punishing people with large monitors by forcing them to change skins (which is not easy for everyone). If you are set on fixed-width columns, find a way to wrap columns within a section for wide screens :) rather than leaving huge vistas blank. I like the move to slightly larger font. The link color changes are most welcome. The purple could be a bit more red, to make it less pastel. Good to have a combination of "high contrast w/ other text" and "doesn't wash out on displays or projection in bright areas". [[User:Sj|Sj]] ([[User talk:Sj|talk]]) 00:27, 11 June 2022 (UTC) == Section number in new ToC == I noticed that there is no section number in the new ToC. I hope the section number will be added again because I can quickly see how many topics there are on the talk page. [[User:Bluehill|Bluehill]] ([[User talk:Bluehill|talk]]) 07:28, 11 June 2022 (UTC) == Move infoboxes out of the text area == Given that we are limiting the space for text and freeing up space on the sides, it seems to me that it would be much better to move the infoboxes to the left side, and stretch the text to its full width. Like this: https://znaniya.org/c/pushkin-aleksandr-sergeevich-8cab44. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 23:50, 11 June 2022 (UTC) : I second this. Such a shame that this request is already explicitly [[Reading/Web/Desktop_Improvements/Frequently_asked_questions#Will_you_improve_charts,_maps,_a-/f-/o-/tmboxes,_infoboxes,_navboxes,_other_templates?|rejected in the FAQ]]. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:15, 14 June 2022 (UTC) :@[[User:Iniquity|Iniquity]] & @[[User:Adamant.pwn|Adamant.pwn]], generally, we agree that it is a nice idea. From a reader's standpoint, infoboxes aren't pure content - rather, these are metadata and could totally work as something put next to the content area. However, these are absolutely content from the technical point of view (because these are regular templates). This issue makes it... impossible? to move them. For underlying infrastructural/back-end reasons I can't explain yet. :However, there's a turning point. What would we work on after the Desktop Improvements? We're considering options for functionalities put in that (currently) empty area. So this topic may be revisited in the future. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 19:45, 14 June 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], thanks for the answer! Note: We can create a separate edit area that will be responsible for the infobox, or we can move the infobox using HTML :) [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 19:58, 14 June 2022 (UTC) == July? == > ''We are hoping to increase the set of early adopter wikis gradually, until our improvements are default on all wikis in July 2022.''<br> Has the schedule changed? [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 00:57, 12 June 2022 (UTC) :It has, @[[User:Iniquity|Iniquity]]. Previously it was June, now it's July. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:13, 14 June 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], thanks! It's just strange that there was no information about this before. And the wikis was not informed about it. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:15, 14 June 2022 (UTC) :::Information was sent yesterday in Tech News. Also, this week, I'll send an update to the Village Pumps. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 17:30, 14 June 2022 (UTC) :::: Yes, I saw it, thanks for that! But the day before yesterday, when I saw this, I got scared, because the community was not ready for this. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 19:59, 14 June 2022 (UTC) :::::We work with individual communities to help them prepare. We also don't ask the most "demanding" communities to prepare yet because Vector 2022 isn't ready to get deployed there either. We take into account that some prefer Vector 2022 to be closer to "finished", and then they would start thinking about preparing. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 22:17, 14 June 2022 (UTC) == Language switcher opt-out == The new language picker is a deal breaker for me as an active editor who is working with a very diverse array of topics on Wikipedia. I write about [https://en.wikipedia.org/wiki/Māori_phonology Māori language], [https://ru.wikipedia.org/wiki/Тэруха Japanese geisha], [https://ru.wikipedia.org/wiki/Литература_Тайваня Taiwanese literature], [https://ru.wikipedia.org/wiki/Эскимосская_кухня Inuit cuisine], [https://ru.wikipedia.org/wiki/Парагвайская_арфа Paraguayan instruments], [https://ru.wikipedia.org/wiki/Мишон Vietnamese temples], [https://ru.wikipedia.org/wiki/Кабилия Algerian regions], [https://ru.wikipedia.org/wiki/Берберская_кухня Berber cuisine], [https://ru.wikipedia.org/wiki/Кайна_(профессия) Arabic professions]. I write [https://en.wikipedia.org/wiki/Sister_exchange articles] that compare dozens of cultures [https://ru.wikipedia.org/wiki/Грамматическое_число or languages]. I need a way to hover over the list of languages to see the name of the page in a different random language (which can be anything from Korean to Twi). I need to be able to open 50 language editions very quickly to estimate if any of them have good illustrations or any new literature on the topic that I am working on. I often read the same article in 4 languages simply because I can read in a lot of languages and I am wondering which language edition has the best article. The workflow with the new language picker is tremendously stunted. The main idea of the new interface seems to be making the page width more narrow. With that, there is a lot of free space at the sides, and I would like to propose putting a full list of languages there, as an option. [[User:Le Loy|Le Loy]] ([[User talk:Le Loy|talk]]) 00:29, 13 June 2022 (UTC) : Yes, I agree, the decision taken now does not help advanced editors work in projects, but hinders them. I think we need to make a separate setting for the "always open" list. The problems of this list have still existed since sorting was removed. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 15:43, 14 June 2022 (UTC) :{{support}}--[[User:Wdpp|Wdpp]] ([[User talk:Wdpp|talk]]) 11:47, 3 July 2022 (UTC) == Old version == :''Moved from [[Topic:Wxcz2an2ck4s4cdy]]'' After these changes are made, can I still use the old settings? [[user:Ilovemydoodle|Ilovemydoodle]] ([[user talk: Ilovemydoodle|talk]]) 09:26, 13 June 2022 (UTC) : Yes [[user:Ilovemydoodle|Ilovemydoodle]], legacy Vector will be available and you will be able to use it as your skin. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:24, 14 June 2022 (UTC) ::{{ping|SGrabarczuk (WMF)}} Why does have to be called “legacy”? legacy implies that something is outdated, inferior, no longer supported, none of which apply to Vector "legacy". Maybe instead, you could call it "advanced", "expert", or "classic". – [[User:Ilovemydoodle2|Ilovemydoodle2]] ([[User talk:Ilovemydoodle2|talk]]) 17:48, 20 July 2022 (UTC) :::@[[User:Ilovemydoodle2|Ilovemydoodle2]], the motivation is purely technical. This is because it's "frozen". The Wikimedia Foundation will not develop it - there will be no actively built version of Vector parallel to Vector 2022. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 20:46, 20 July 2022 (UTC) == Incorrect language name for Czech == I noticed that for Czech (čeština in Czech) in the new look the first letter is incorrect, it says "Ceština" instead of "Čeština". I do think it is pretty funny, but would say it should be consistent with the rest of the themes. I hope this is the right place for this, I didn't find anywhere else to post. [[User:Filiptronicek|Filiptronicek]] ([[User talk:Filiptronicek|talk]]) 09:46, 13 June 2022 (UTC) :Hello @[[User:Filiptronicek|Filiptronicek]]. Thanks for writing to us. Most likely, it's not within our area, but I'll help you if the problem still exists. Where do you see this? On Polish and English Wikipedias, I see "Čeština". [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:42, 14 June 2022 (UTC) ::Hi there @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], perhaps it may have something to do with Czech being suggested to me as a language? I don't have an alt account to test this with though. ::Screenshot of what I see on the English wikipedia: https://i.imgur.com/T40u7rN.png. It is some very interesting behavior. Thanks for looking into this. [[User:Filiptronicek|Filiptronicek]] ([[User talk:Filiptronicek|talk]]) 13:45, 15 June 2022 (UTC) == Please take the interlanguage link (aka "green link") on Chinese Wikipedia into consideration! == The Chinese Wikipedia currently uses a green-colored link for interlanguage links in articles, and it seems to fail the WCAG AAA. These links can been seen at [[zh:Deadmau5]], for instance. These links are used a lot on Chinese Wikipedia, and I'm not sure if it is good for readers. If you want to evaluate link colors, please also take this green link into consideration, thank you. Looking forward to your professional advice! [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 11:38, 13 June 2022 (UTC) :I know these links are not part of Vector 2022, but they are part of the user experience, and currently there is a discussion at Chinese Wikipedia's Village Pump about the choice of color of them, so I posted my message here. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 11:43, 13 June 2022 (UTC) == Table of content (ToC) == Hi! Since weeks ago I don't see the table of content in the sidebar like I used to do before. It just disappeared. It happens when I'm connected in my phone using desktop version. Best regards! '''''[[User talk:Miaow|<span style="background:#88b;color:#cff;">Mia<span style="background:#99c">o<span style="background:#88b">w</span></span></span>]]''''' 12:06, 13 June 2022 (UTC) :Hello @[[User:Miaow|Miaow]]. Thank you for reporting this problem. We're working on a better look of TOC on small screens. I also strongly suggest you selecting the [[Reading/Web/Advanced mobile contributions|advanced mobile contributions]] mode when you're using your phone. That mode is dedicated for mobile, in contrast to Desktop Improvements. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 10:38, 14 June 2022 (UTC) == Better alignment for wide screens == [[File:Article with new vector.png|thumb|]] Here's how the new design looks on my laptop with 2560x1600 resolution. Ok, I get it, you won't do anything about the max-width and you insist on using this path. But look, the parts highlighted with purple ellipses just look misaligned. It just begs for the following: * Reduce the white background so that its right end matches the right end of the article OR insert something into that area. Having gray empty space is ok, but having both white and gray empty spaces look just silly. * Reduce the header so that its right end matches the right end of the article OR extend the white background of the header so that it fills the whole width of the page (see e.g. how it's done on [https://stackexchange.com StackExchange] or [https://www.reddit.com Reddit]. Again, I get your rationale that having empty space is ok. But having a white empty space on top of the gray empty space... Don't you think it's a bit too much? [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 01:23, 14 June 2022 (UTC) : [https://squidfunk.github.io/mkdocs-material/getting-started/ Material for MkDocs] is another example of what I consider a more successful implementation of reduced max-width. The main part has the same background (having same white background on the whole page would also look good on wiki) and the header part has background that extends beyond max-width. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 01:25, 14 June 2022 (UTC) ::When we look to the prototype https://di-article-tools-2.web.app/Blue%20whale?en (and https://vector-2022.web.app/Brown_bear), it's fill by "Tools", "In other projects", "Print, share, link" [[User:Koreller|Koreller]] ([[User talk:Koreller|talk]]) 08:31, 14 June 2022 (UTC) ::: It looks somewhat nicer, but the white empty space is still there if you collapse sidebars or scroll a bit... Also seem to have different defaults for logged in and logged out users. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:12, 14 June 2022 (UTC) == Launching New Version == :''Moved from [[Topic:Wxf5fv5pmxyyccdy]]'' When shall the new version ([[Reading/Web/Desktop Improvements/Fifth prototype testing/Feedback|Fifth prototype]]) be launched? [[user: Stnts256|Stnts256]] ([[user talk:Stnts256|talk]]) 08:54, 14 June 2022 (UTC) : We hope to launch Vector 2022 as default by the end of July. You can use it already by [[Special:Preferences#mw-prefsection-rendering|selecting this option in your preferences]]. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 12:28, 14 June 2022 (UTC) ::Thank you [[User:SGrabarczuk (WMF)|SGrabarczuk]] [[User:Stnts256|Stnts256]] ([[User talk:Stnts256|talk]]) 14:04, 14 June 2022 (UTC) == Keep watchlist in the sticky header == For an active Wikipedia editor, watchlist is likely the most popular destination when you're on some page. Would be great to keep the link there in the header, even after some scrolling. [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:24, 14 June 2022 (UTC) : Keeping alerts and notices would also be nice. And also for it to work on the talk pages... [[User:Adamant.pwn|Adamant.pwn]] ([[User talk:Adamant.pwn|talk]]) 14:26, 14 June 2022 (UTC) : Yes, it bothers me that my control panel disappears. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:01, 14 June 2022 (UTC) : Second that. The most-used buttons of the standard interface (watchlist, contribs, interwikis) should stay in place, accessible with one mouse click. With the proposed layout I have to press tab-tab-tab... and then ctrl-enter to get to the watchlist. Why so? I can't reliably use the proposed drop-down menu with mouse, it's a common age-related ailment. I'd highly recommend to retain at least some bits of usability-for-disabilities: no complex manipulations. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 09:39, 15 June 2022 (UTC) == clear:both rendering on old browsers == {{Tracked|T309711}} I have tried browsing the wiki on Internet Explorer 11 on the new skin for one last time before Microsoft disables it, and it worked well, except something I have noticed is that the CSS property <code>@media screen .mw-body-header::after { clear:both; }</code> causes the side bar to push down the content. When unticking <code>clear:both</code> in the page inspector or when the side bar is hidden, it appears as usual. While fixing it for IE11 won't be relevant anymore, earlier versions of other browsers might have this flaw too. Mentioning it just in case. [[User:Octobod|Octobod]] ([[User talk:Octobod|talk]]) 23:29, 14 June 2022 (UTC) == Where are the interwikis? == Is there a simple way to access interwikis, other than by going to wikidata? Also, having two quasi-interwikis for wikidata is quite confusing. Only the second one actually works, the first one defaults to wikidata's start page. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 09:46, 15 June 2022 (UTC) :@[[User:Retired electrician|Retired electrician]] - currently, the adding interwiki links is available from the sidebar: "Edit interlanguage links" in the tools section. In the future, we would like to add them into the language selector as well. We are currently working with our Language team on this - see [[phab:T290436|Add support for empty states to the current language selector]] in phabricator for more details. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:23, 16 June 2022 (UTC) :: {{ping|OVasileva (WMF)}}, I see. Curiously, "Edit interlanguage links" does not appear on the main page (at least in ru-wp). [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 13:50, 16 June 2022 (UTC) == Suggestion: Round borders == I appreciate very much the efforts to make the design of Wikipedia less outdated, and imo this new design is amazing. To make it even better I would suggest you guys to put round borders in the boxes, so let's add border-radius:14px in these functions! This will make it cleaner and softer! [[User:Duke of Wikipädia|Duke of Wikipädia]] ([[User talk:Duke of Wikipädia|talk]]) 22:27, 16 June 2022 (UTC) == Top margin in title == Just noticed the new version and it looks like the title's top margin was reduced. There is an awkward amount of bottom margin for the title compared to top margin and I personally prefer the previous margins. [[User:0xDeadbeef|0xDeadbeef]] ([[User talk:0xDeadbeef|talk]]) 06:55, 17 June 2022 (UTC) == Very minor improvements == I just got the new toolbar this morning, and I absolutely love it! Finally Wikipedia does not look old anymore. But I would like you guys to add a little more than just a border for the active section in the toolbar, probably a lighter background for active tabs and a darker one for non active tabs. For example, if I'm reading an article, the 'Read' tab in addition to the bottom border, it should be lighter. The 'Talk' tab should be lighter also if I'm in the talk section. This should work well with something like option 3 combined with option 9 (where the header and the title has grey background) in [https://di-visual-design-borders-bgs.web.app/Zebra this border and background demo here]. I like option 3 a lot so it would be good if you guys implemented it, haha. I apologize if my English is not clear. [[User:Klrfl|Klrfl]] ([[User talk:Klrfl|talk]]) 12:26, 17 June 2022 (UTC) == new table of contents == For pages with a long table of contents such as this one, the table of contents starts jumping to highlight the current heading. Would it be possible to consider smooth scrolling behaviour for the table of contents at the new location (as for example invoked by <code>.vector-toc-enabled .sidebar-toc { scroll-behavior: smooth; }</code>)? Or is there something like a frozen state or is/was/will be this rejected for another reason? --[[User:CamelCaseNick|CamelCaseNick]] ([[User talk:CamelCaseNick|talk]]) 23:15, 17 June 2022 (UTC) :{{support}} [[User:Patafisik|Patafisik]] ([[User talk:Patafisik|talk]]) 10:06, 21 June 2022 (UTC) == Sister project links == (From [https://it.wikipedia.org/w/index.php?title=Discussioni_utente%3APatafisik_%28WMF%29&type=revision&diff=127968745&oldid=127933193 it.wikipedia]) {{ping|Friniate}} suggests to gather the Wikidata link and the Sister project links in the same place.--[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 09:49, 20 June 2022 (UTC) == Impact == How does the team plan to assess/measure whether the Vector changes work towards their stated goals, so that we're able to correct course in case they don't? [[User:Nemo_bis|Nemo]] 00:41, 21 June 2022 (UTC) == Great addition of ToC menu through icon wrt zoom !!! == I <s>have just</s> discovered a few days ago, in the french version of WP, as well as here in MediaWiki, the addition of a ToC menu, just before the title, that appears when the left column is NOT visible (at least effect of zooming), and '''this is a GREAT GREAT improvement, MANY-many thanks to the developpers'''. There still remains a small bug that appeared with this change (at least I didn't notice it before) : the upper (collapsile) bar appears no more. It reappears back when zoom permits back the side left column (tested with an article page in fr.WP ; no appearance "here" while editing, or even while just reading. but I guess it's a different thing, maybe because this is a talk page : I get the same "behaviour" in a talk page from fr.WP : no appearance of the upper collapside bar even if a left colum ToC is present. Might not be a "bug", but a feature, though I would personnaly prefer a uniform behaviour). Whatever, great thanks to the developers.<br/> &nbsp; (Poke @[[User:Patafisik (WMF)|Patafisik (WMF)]] : thanks for relaying these improvements, and back, our comments. Best :-) )<br/> &nbsp; -- [[User:Eric.LEWIN|Eric.LEWIN]] ([[User talk:Eric.LEWIN|talk]]) 06:17, 21 June 2022 (UTC) == Both the ToCs == (From the French Wikipedia [[:fr:Discussion_Projet:Am%C3%A9lioration_de_l%27interface_par_la_WMF#Sommaire_%C3%A0_gauche_:_ajouter_plut%C3%B4t_que_remplacer_?|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/24_mai_2022#Sommaire|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/26_mai_2022#Bug_du_sommaire|here]], [[:fr:Wikip%C3%A9dia:Le_Bistro/19_juin_2022#Tables_des_mati%C3%A8res|here]] and [[:fr:Wikipédia:Le_Bistro/25_juin_2022#Sommaire_dans_la_barre_de_gauche|here]]) I've already reported this to Szymon, but I think it will be important to have this suggestion also in this page, visible to all and open to comments. Different users of the French Wikipedia consider the old ToC and the new one as two complementary tools, and they want both! Reasons: 1) for the context, the ToC should be on the top of the article. If we have the first part of the sidebar occupied by the wiki navigation menu, the ToC is too far on the bottom of the page, it appears on the top only when you scroll down 2) the layout of articles with illustrations is completely disrupted. Both why? "When I look at the beginning of an article, I expect to see a ToC with the main sections in order to understand how the article is structured (quite like in a Word document). This makes it easier to read. The ToC on the left is then very useful when you scroll down the article and want to navigate between sections, but it is an additional feature. It should not replace the current summary, which is still useful. Or it should be displayed from the start at the top left, when you are at the top of the article (quite like on Universalis)." (summarised by Pronoia [https://fr.wikipedia.org/w/index.php?title=Wikip%C3%A9dia%3ALe_Bistro%2F26_mai_2022&type=revision&diff=194205255&oldid=194153014 here])--[[User:Patafisik (WMF)|Patafisik (WMF)]] ([[User talk:Patafisik (WMF)|talk]]) 11:45, 21 June 2022 (UTC) == Интервики в правый блок == Сейчас правое поле статьи абсолютно пустое. Что мешает перенести туда интервики-ссылки, вместо их полного сворачивания, а также подходящие по смыслу к ним ссылки на братские проекты? Это позволит: 1) избежать совершенно ненужного сворачивания списка (бессмысленно его уменьшать, когда высвободилось столько места); 2) заполнить правое поле; 3) частично разгрузить левое поле, чтобы оглавление было лучше видно сразу на первой же странице текста (сейчас при текущих настройках экрана я во французской Википедии вижу в среднем две верхних строки оглавления). [[User:AndyVolykhov|AndyVolykhov]] ([[User talk:AndyVolykhov|talk]]) 12:51, 21 June 2022 (UTC) == Languages in the new desktop interface == In the older interface I can select the interwikis that I need most and put them on top of the interwikis' list; same possibility should be in the newer interface. [[User:Leokand|Leokand]] ([[User talk:Leokand|talk]]) 15:06, 21 June 2022 (UTC) == minor issues == * The position at which the table of contents is sticky changes with the sticky header becoming visible/hidden. (<code>.vector-toc-enabled.vector-sticky-header-visible .sidebar-toc { margin-top: 1.5em }</code> vs. <code>.vector-toc-enabled .sidebar-toc { margin-top: 3.5em }</code>) With the sidebar navigation hidden, this makes the table of contents jump up by <code>2em</code> while scrolling. * At a window width of exactly 1000px the table of contents on the left is displayed but styled like the drop-down table of contents and the drop-down button is still visible but has no influence on the table of contents. * At 720px+ the logo is displayed, the username and potentially a language switcher. With my username on this wiki in German, the watchlist and the user menu are outside the viewport, so this threshold is chosen to narrow. Maybe a solution would be to move the username link to the user menu at 1000px and lower. (For CSS rendering, I use Firefox v101.) -- [[User:CamelCaseNick|CamelCaseNick]] ([[User talk:CamelCaseNick|talk]]) 17:28, 21 June 2022 (UTC) == Drop-down menues = poor accessibility == Repeating prior statements for clarity: May I speak on behalf of old folks with less-than-perfect control of palms and fingers. The replacement of simple "button" links (contribution, statistics, interwikis...) with drop-down menues becomes a huge inconvenience. In plain monobook, I can simply click on the interwiki, and hopefully get the desired tab at the first try. In vector-2022, I cannot reliably pull down the drop-down list and then select something with a mouse... it almost never works as intended. A very common age-related ailment, it just happens. The only robust workaround is to use the keyboard to "tab-tab-tab..." to the desired control box, and then "enter-tab-tab-...-enter" through the list. And, in case of interwikis, selecting the main (en:) wikipedia takes atrociously long time - instead of being #1 entry, as in old good monobook with my normal preference settings, it's somewhere down the middle of the list. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:46, 21 June 2022 (UTC) == Irish language Wikipedia and Vector 2022 == [[File:Irish Wikipedia random article - Vector 2022.png|thumb|ga.wp random article screencap - Vector 2022]] [[File:Irish Wikipedia random article - Vector old.png|thumb|ga.wp random article screencap - current Vector]] Hi there. I'm [[w:ga:User:Alison]] - admin and bureaucrat on the Irish language Wikipedia. I'd be remiss in not providing feedback, I think, so here goes. * I see other folks pointing out the massive amount of whitespace / padding in the left side navbar which is squeezing out the actual article text on the right. On our wiki, it really seems significant. IMO, article is all, and we seem to be sacrificing actual content real-estate for ... what, exactly? Yes, it looks 'less cluttered', but there's actually less content - especially for those of us who both browse ''and'' edit on laptop screens. * On the top tab section (which is otherwise quite nice), you can see the ''Plé'' (Talk) and ''Léigh'' (Read) are scrunched together with no separation. I18n bug, maybe? * The main image and title have lost their localization and now show "Wikipedia" instead of "Vicipéid" - this could just be an image localization / config issue. Could someone point me in the right direction, maybe? I did the original, later-font localization for our wiki, some years back, so happy to dip in and fix :) Le gach dea-ghuí (best regards), -- Allie [[User:Alison|<span style="color:#FF823D;font-family: comic sans ms">'''A<font color= "#FF7C0A">l<font color= "#FFB550">is</font>o</font>n'''</span>]] <sup>[[User talk:Alison|❤]]</sup> 16:17, 22 June 2022 (UTC) :multilingual Wikipedians: during redesigh include current non-english desighs for evaluation, including spanish, french and german. They have good ideas and bad ideas... [[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 01:10, 23 June 2022 (UTC) : The "PléLéigh" issue looks like it's [[phab:T309223|T309223]], a known issue. Until it is fixed in MediaWiki, try updating your browser(s) – the issue occurs if your browser doesn't support a certain relatively new feature. [[User:Rummskartoffel|Rummskartoffel]] ([[User talk:Rummskartoffel|talk]]) 21:59, 23 June 2022 (UTC) ::Hey there! Regarding logos https://phabricator.wikimedia.org/T244486 is what you are looking for - basically every logo needs to be recreated. You can request one on that ticket to be prioritized higher or find information about creating new ones. ::Regarding sidebar whitespace I am not sure I understand. The extra padding is for the table of contents underneath the sidebar. You say it's squeezing article text on the right but in your screenshots the Vector 2022 screenshot shows more of the article text. I can see the description section heading for example. ::I can confirm the PléLéigh issue is a bug and will hopefully be fixed soon. ::Hope this is helpful. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 01:02, 1 July 2022 (UTC) == TOC-Feedback == I just recognized what disturbs me the most with the new TOC. I wasn't able to access the TOC without scrolling or clicking when using a community-Page. The main thing: '''It's mixing system and content'''. The TOC is for the content, but appearing on a place of "system". The "frame" is the Media-Wikisystem: accessing Community-Pages, Help, recent changes, user-page etc. Inside the "frame" is the content (the "article", the "book"...). Although it's kind of logical to have the TOC sticky on the side there are so many problems with it: # the TOC can't be manipulated by magic words, which is a pretty well used functionality. # the TOC can't be placed to the right, which is pretty often used in german wikibooks. # the TOC is in competition with the other menus. # the TOC is now at a place where normally links to other pages are placed. The same fear of mixing system and content goes with switching the Header and the "Editing-Tabs" (Compare https://di-article-tools-2.web.app/Blue_whale: '''Blue Whale''' first, ''read/edit'' second). BTW the TOC works at this demo-page because the Main Menu is so short. But since this is not fixed (which is a good thing!), the Main Menu might be longer. A good illustration of the problem is visible just the paragraph above this: [[#Irish language Wikipedia and Vector 2022]]. The TOC in the Vector22-Example is completely missing! So, just as an Idea: '''divide system and content''' - say system top&left (as it's always been) and content bottom&right. the TOC could be placed "always right" next to the text. At least please let the editor choose what to do with the TOC. I mean, wouldn't it be so bad if it's within the Content '''and''' at the side? I'm fine with the new skin and all the work that has been put in, but the TOC is becoming unusable for me like it is right now. If it's really becoming permanent, it will probably result in "self-made-TOCs" which will break pretty often, because of the "wiki"-system. [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 17:37, 22 June 2022 (UTC) == The new design is everything I feared == Jumpable, irritatingly movable buttons? Check. Sticky UI that eats up immense space both at the top (header) and to the left (table of contents)? Check. Tiny narrow line of text in the middle? Check. Buttons not looking like buttons, thus confusing me as to what I may click? Check. The language menu made objectively worse, with more clicks necessary to use than before? Check. Every single change is atrocious, negative, and honestly makes me feel depressed - I will either try to scour Reddit for browser extensions to remove as much of it as possible (no, logged in user things are useless to me as I'm never logged in), or I will leave Wikipedia for good (mental health is more important than knowledge). Just look at this useless eyesore of a sticky table of contents ([https://i.postimg.cc/bz2zZM2C/2022-06-22-Wikipedia-English-51-UI-bug.png screenshot on postimage] - I hope, you aren't getting the ads, I'm getting none). Even aesthetics-wise, it's botched - the bottom is smudged, the top cut-off. And it's not even at the edge of the screen! It's an exercise in ugliness. And just saying it here, this Wikimedia redesign is already making it unintuitive for me to write. When I tried to insert the link, I couldn't even see the [https://i.postimg.cc/qBp0ZvDS/2022-06-22-Wikipedia-English-53-UI-bug.png ''upload'' button] - because it's on the edge of the sub-menu (like on phones), not somewhere sensible, like on computers (again, compare how it is on current Wikipedia - a [https://postimg.cc/TpMNbPHg large nice menu with clear buttons at the bottom], computer design). [[User:Adûnâi|Adûnâi]] ([[User talk:Adûnâi|talk]]) 18:55, 22 June 2022 (UTC) == wordmark no longer appears after upgrading to MediaWiki 1.38.1, style bugs == After upgrading to MediaWiki 1.38.1 from 1.36.1, the wordmark no longer appears next to the icon in the upper left. If the window is wide enough, the 150px space for the wordmark is reserved but is empty. When you make the window wider past a certain width, the coloring behind the sidebar also vanishes. This happens with Vector 2010 in both legacy and non-legacy mode and in Vector 2022. The wordmark image is an svg that has not moved and still has correct permissions [[User:Queernix1028|Queernix1028]] ([[User talk:Queernix1028|talk]]) 19:43, 22 June 2022 (UTC) :What is the value of wgLogos in your LocalSettings.php? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:22, 29 June 2022 (UTC) $wgLogos = [ 'icon' => "$wgScriptPath/images/arcc/logo.svg", '1x' => "$wgScriptPath/images/arcc/logo.png", 'wordmark' => [ 'src' => "$wgScriptPath/images/arcc/wordmark.png", '1x' => "$wgScriptPath/images/arcc/wordmark.svg", 'width' => 150, ], ]; ::It previously worked with wordmark src set to the svg file, but now neither that configuration nor the one above work. [[User:Queernix1028|Queernix1028]] ([[User talk:Queernix1028|talk]]) 14:32, 29 June 2022 (UTC) :I believe you need to set a height on the wordmark. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 00:55, 1 July 2022 (UTC) == Menus — https://di-visual-design-menus.web.app/Brown_bear. == *left side menu persistency is screen wasteful, bad idea ** use a tab like google maps? *left side menu: should be hamburger only **as an option for experienced, registered users **need style sheet that puts ''left side column'' '''at bottom of page''' as a footer *language list: **should include native and english names **include a user-customizable shortlist *[[User:0mtwb9gd5wx|0mtwb9gd5wx]] ([[User talk:0mtwb9gd5wx|talk]]) 00:57, 23 June 2022 (UTC) == Language links on Wikidata are right at the bottom of the page == I've enabled the new theme (Vector 2022) globally on all wikis. I generally like the new interface. However when I am on wikidata, previously the interlanguage links were on the right. (Where an infobox usually goes on a wikipedia page) Now they are right at the bottom of the page! Some wikidata pages are massive, and having to scroll all the way down to the bottom of the screen to do the thing I do most frequently on wikidata (add new language links) is a real pain. Please can you move the language links on wikidata back to the top (top right) of the page? - [[User:Rooiratel|Rooiratel]] ([[User talk:Rooiratel|talk]]) 14:25, 23 June 2022 (UTC) :Hello @[[User:Rooiratel|Rooiratel]]. Thanks for your opinion. Are you talking about the desktop view? What's the resolution of your screen? I've tried to narrow my window down and change its width, and it seems that the width thresholds when the interwiki links go from the bottom to the right are the same. Is there any setting you use that may make your experience different? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:50, 27 June 2022 (UTC) ::Hi {{ping|SGrabarczuk (WMF)}} this is for the desktop view. I am seeing this behaviour on my 1080p laptop screen and my 1440p desktop screen. I haven't used the mobile view, so can't comment on that. - [[User:Rooiratel|Rooiratel]] ([[User talk:Rooiratel|talk]]) 06:32, 28 June 2022 (UTC) == Infobox element alignment is mangled in mobile view == Maybe I'm doing something wrong, but when I click on "Mobile view" with Vector 2022, many of the infobox elements are misaligned. Many elements that should be centered are left-aligned, and many elements that should be left-aligned are centered. At least that's what it looks like for me in Chrome for Mac OS at [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic&useskin=vector-2022 this page]. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 02:57, 24 June 2022 (UTC) :Wow, that looks odd. Thanks @[[User:Jonesey95|Jonesey95]] for reporting this. Right now, I only have one question - why do you use the mobile view and Vector 2022 mixed together? Minerva is dedicated for mobile, and Vector 2022 is dedicated for desktop. Having these two at the same time is bold and original :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:08, 27 June 2022 (UTC) ::I was just doing some very beginner-level QA testing. Editors do all sorts of ridiculous things, so I try to do some QA testing by doing ridiculous things. If you want editors to use Vector 2022 for desktop-only and Minerva for mobile-only, then make the "Mobile view"/"Desktop view" link at the bottom of the screen switch between the skins. Meanwhile, I'll be over here in legacy Vector where I can fill my browser window with content.... [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 01:15, 28 June 2022 (UTC) Using the mobile domain with the Vector skin invokes a special mode with lots of odd behaviour. It's not part of this project but will hopefully get fixed some day. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:30, 28 June 2022 (UTC) == "Related articles" appear to be missing == I do not see the "Related articles" section at the bottom of the mobile view. I don't really care, but since the "Principles" section of this page says "We do not remove any functionality", I thought I'd mention it. It makes me wonder what other functionality has been removed, and whether this principle is really being followed in a systematic way. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 03:02, 24 June 2022 (UTC) RelatedArticles appears to be working fine to me. I see it on Minerva. What do you mean by "at the bottom of mobile view"? The scope of this project is the desktop site so no changes to the mobile domain have been made. RelatedArticles does not show on the skins of certain websites and has not shown on Vector or Vector 2022 unless the community has explicitly requested. See [[phab:T144812]], [[phab:T181242]] and [[phab:T278611]] for example. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:59, 24 June 2022 (UTC) :I think this is my mistake. I was comparing [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic this] (default mobile view on en.WP) with [https://en.m.wikipedia.org/w/index.php?title=Russian_Soviet_Federative_Socialist_Republic&useskin=vector-2022 this] (Vector 2022 mobile view) and assuming that the default mobile view used some version of the Vector skin, but I think that is not correct. [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 16:38, 24 June 2022 (UTC) Ah okay. This mode is only accessible by a special URL and is not being worked on as part of this project. Thanks for taking the time to explain! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:28, 28 June 2022 (UTC) == 非常に見にくい == 日本語で失礼します。本日ごろから日本語版ウィキペディアのスキンに変更があったようですが、 # 文字の大きさをブラウザ側から変更できない(Safari使用)。 # そもそも標準の文字サイズが大きすぎる。 # 目次が項目名の横に位置が変わったせいでアクセスが煩雑になった。 # Infoボックスが大きすぎる などの変更のせいで、余計見づらくなったような気がします。可能であれば改善するか、もしくは変更前のスキンに戻して欲しいです。 [[User:イカしたイカ|イカしたイカ]] ([[User talk:イカしたイカ|talk]]) 08:38, 24 June 2022 (UTC) :感謝します、@[[User:イカしたイカ|イカしたイカ]]さん。 :First of all, you don't need to apologize for writing in Japanese. We welcome comments in any language. :# Would you like just to change the default font size? Or would you be able to zoom in and out, and see the font size adjust? :# Do you think making the text line wider and keeping the default font size would fix the problem? :# Why do you think access is more complicated now? Our motivation was to reposition the table of context to make it more accessible. What do you think is not working? :# Do you think the problem is related to the default font size? :まず第一に、あなたは日本語で書いたことを謝罪する必要はありません。 どんな言語でもコメントを歓迎します。 :# デフォルトのフォントサイズを変更しますか? または、ズームインおよびズームアウトして、フォントサイズが調整されるのを確認できますか? :# テキスト行を広くし、デフォルトのフォントサイズを維持することで、問題が解決すると思いますか? :# なぜ今、アクセスがより複雑になっていると思いますか? 私たちの動機は、コンテキストのテーブルを再配置して、よりアクセスしやすくすることでした。 何が機能していないと思いますか? :# 問題はデフォルトのフォントサイズに関連していると思いますか? :[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:18, 12 July 2022 (UTC) == Please evaluate CJK characters' font size in Vector 2022 == {{tracked|T311469}} For your infomation, the Chinese Wikipedia already has a [[zh:MediaWiki:Gadget-large-font.css|gadget]] that increases the font size for a better Chinese reading experience. Japanese and classical Chinese Wikipedia also have such kinds of gadgets. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 08:19, 25 June 2022 (UTC) :It would be nice if we could integrate these gadgets into new Vector skin directly. This would benefit other CJK and multilingual wikis. [[User:Diskdance|Diskdance]] ([[User talk:Diskdance|talk]]) 08:20, 25 June 2022 (UTC) ::Thanks @[[User:Diskdance|Diskdance]]! @[[User:AHollender (WMF)|AHollender (WMF)]] FYI :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:03, 27 June 2022 (UTC) I think we should create a phabricator ticket for this one. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 02:29, 28 June 2022 (UTC) == Feedback regarding Vector (2022) TOC == I've had Vector (2022) enabled for a while, and generally like it. However: * I don't feel the new way of handling the TOC and side menu is user friendly. It took me a while to notice I could hide the side menu only to raise the TOC up the page, as I assumed it would also hide the TOC since the two are part of the same sidebar. With the side menu visible, I had to scroll much further down than usual to find the TOC on many articles with short lead sections, which undermined the convenience previously provided by the TOC as a way to skip scrolling and quickly navigate to a desired section. ** It also doesn't help that the [[w:Template_talk:Skip_to_talk#Broken_functionality_with_new_version_of_vector_theme|new TOC breaks the functionality of]] {{tl|Skip to talk}}, widely used on talk pages on Wikipedia, but I now understand that the change is intended to make that template unnecessary. ** The prototype [https://di-visual-design-menus.web.app/Brown_bear linked by others above] deals with some of these issues but is still a bit confusing. It's not clear that clicking "hide" on the TOC should result in a menu appearing by the article title rather than just collapsing it like collapsible lists which use the same "[hide]" links; while this behaviour can be learned, it's not clear why the hidden TOC menu button doesn't persist between the search icon and article title when scrolling down, which is what I expected after seeing it collapse to a button beside the article title. * The new sidebar is wider to accommodate the TOC, but much of that space is blank so I'm not sure it needs to be quite so wide, particularly as the added width can cause issues such as galleries by default having less space for images per row. I understand the motivation is to limit the characters of text per line, but doing so by padding the sidebar with empty space seems like an unhelpful way to achieve that. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 16:57, 26 June 2022 (UTC) == Where are the watch/unwatch buttons? == Alright, if the article is long enough to be scrolled, I should scroll it down, the top row of icons will jerk left-right, and the "watchlist" icon will become the "watch/unwatch" toggle. Hopelessly inconvenient, counterintuitive, but it works. But what if the article is so short that it won't scroll at all? [https://ru.wikipedia.org/w/index.php?title=%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%8F:%D0%A0%D0%B5%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5/%D0%9E%D0%B1%D1%8A%D0%B5%D0%B4%D0%B8%D0%BD%D1%91%D0%BD%D0%BD%D1%8B%D0%B9_%D0%B2%D0%BE%D0%BA%D0%B7%D0%B0%D0%BB_%D0%A6%D0%B8%D0%BD%D1%86%D0%B8%D0%BD%D0%BD%D0%B0%D1%82%D0%B8&oldid=123611287 example] Seems like "preferences/watchlist/edit raw watchlist" is the only go-around, is it not? [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 12:13, 27 June 2022 (UTC) :@[[User:Retired electrician|Retired electrician]]: There's a smaller star-shaped watch/unwatch toggle to the right of the "View history"/"История" link. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 14:48, 27 June 2022 (UTC) :: Thanks, that was most unexpected. I'd rather prefer old good text links. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 15:59, 27 June 2022 (UTC) The new star looks almost exactly like the existing GA star, just a different shade of grey (but in almost the same corner location as in standard monobook). [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 16:02, 27 June 2022 (UTC) :"Thanks, that was most unexpected. I'd rather prefer old good text links" - you're a Monobook user, am I right? This may be a good reason why it's most unexpected for you. Vector 2022 is based on Vector legacy (2010), and the star icon has been there for 12 years. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 01:51, 28 June 2022 (UTC) == Merge notification block in the header: notifications and alerts == {{Tracked|T142981}} For me, it has always been a strange decision that notifications were divided into two unrelated blocks and icons with incomprehensible categorization. I forgot about it, but now I'm paying attention again. Given that we removed the text from all menus, there are now a lot of icons at the top that do not understand what they do. Different blocks of notifications do not help this at all. Maybe it's time to put them in one menu and break it there already? Filters, tabs, whatever :) But at least you won't get confused in the icons. I personally still (6 years!) do not know what their fundamental difference is. I asked my friends and they don't know either. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 17:29, 27 June 2022 (UTC) :{{Strong oppose}}. The notices are the notifications that are not very important/urgent, unlike the alerts. Merging them would make me unable to found out at a glance if I have any important/urgent notification, and would also overload the notification box, as I receive many notifications. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 22:19, 27 June 2022 (UTC) :: It seems to me that it is possible to do this with filters and colored marker icons. Or a separate setting for users who really need it. [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 09:47, 28 June 2022 (UTC) :{{Comment}}. I agree that the distinction could be clearer, but don't necessarily agree that there should be only one button. Presently, when both are empty the only difference between them is the header text and icon. Both share the exact same two buttons, which link to the same destinations. The text in the box doesn't even distinguish, reading "There are no notifications" instead of "There are no alerts". There isn't even a "help" or "about" link unique to each of them to explain the difference or what gets sent where. If you follow the links to the special page or preferences, it's still not clear which notifications are sent where. :Based on the names, I would've assumed the difference would be that alerts are specifically for subscriptions to [[Wikipedia:Article alerts|article alerts]], whereas notifications would be for everything else. It makes sense to split them, since alerts would be activity that's less personal to the receiver. "Alerts" would be like a daily newspaper, but "notifications" are more like personal mail. Except this isn't how the system actually functions; messages to the receiver's talk page are placed under "Alerts" rather "Notices", for example. :I understand that it may be helpful to filter urgent notifications from less urgent ones, but what counts as urgent or important? Shouldn't that be decided by the user's preferences? It would make more sense to have something like tabs, as Iniquity suggested, to filter types of notifications; this would let that user decide what is important. [[User:Scyrme|Scyrme]] ([[User talk:Scyrme|talk]]) 22:33, 27 June 2022 (UTC) == Table of contents: Bold format for active section == I really appreciate the new skin and layout. In the beta, the active/current section of the article was formatted bold in the table of contents on the left side. But in the live version, it's regular and black. I find it really, really hard to differentiate between the normal blue titles and the active title, because the only difference is the black vs. blue color. Could you please make the active titles bold again? Thank you! [[User:Lhennen|Lhennen]] ([[User talk:Lhennen|talk]]) 21:11, 29 June 2022 (UTC) :+1 Bold and black would be best imo. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:43, 1 July 2022 (UTC) ::@[[User:Lhennen|Lhennen]], @[[User:L.xschlag|L.xschlag]] - thank you for your feedback! Not sure if you've seen, but we are currently in the middle of testing some [[Reading/Web/Desktop Improvements/Fifth prototype testing|prototypes]] related to this question. You're welcome to give us more detailed feedback on the prototype page. One of the things we're testing on these is the way links should appear within the table of contents (see https://di-visual-design-toc-active.web.app/Otter) for an example. Currently, our feedback is showing us that people are leaning towards option 2: bold and black so we will most likely be continuing with that option and making the titles bold. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:08, 4 July 2022 (UTC) == Jawiki has NOT reached consensus on implementing Vector 2022 yet == Jawiki has '''NOT''' reached consensus on implementing Vector 2022 yet. Why was it implemented without our consent? [[User:AppleRingo777|AppleRingo777]] ([[User talk:AppleRingo777|talk]]) 22:01, 29 June 2022 (UTC) :Hi @[[User:AppleRingo777|AppleRingo777]] - we apologize for the confusion that the deployment process has caused and the lack of clarity from our side.  We are currently working on reading back through our previous communications and clarifying the process and what happened with individual members of the community.  We will to get back to the community with more detailed thoughts and a process for next steps by tomorrow July 1st.   [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 12:04, 30 June 2022 (UTC) == [[MediaWiki:Sidebar]] == Hello! I asked a question at the meeting, but I would like to duplicate it here. Will it be possible to control the location of blocks (right or left) through [[MediaWiki:Sidebar]]? [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 15:34, 30 June 2022 (UTC) :Hey! We are still thinking through how this would work. Input valued in [[phab:T306519]] ! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:27, 6 July 2022 (UTC) :: Thanks! :) [[User:Iniquity|Iniquity]] ([[User talk:Iniquity|talk]]) 16:16, 6 July 2022 (UTC) == Keep the TOC under the main menu as long as possible (Vector 2022) == When the window gets narrower the TOC is moved into a "Hamburger button". But the main menu stays where it is until the window get's quite a bit more narrower. I think as long as the main menu fits, the TOC should stay at its original place. Especially since the TOC behind the "Hamburger button" is quite easy to miss. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:30, 1 July 2022 (UTC) :This was a bug. I believe it should be fixed by the end of the week. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:28, 6 July 2022 (UTC) == "Move" is the only in the "More" drop down menu (Vector 2022) == I think it's quite odd that the "More" drop down menu most of the time contains only "move". Is it on purpose to make it harder to find for the average user? [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:35, 1 July 2022 (UTC) * {{ping|L.xschlag}}, I have two items - the other is an add-on via preferences/gadgets. Unfortunately, I cannot use drop-down menues easily, so getting there in V-2022 is quite a nuisance. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:31, 3 July 2022 (UTC) *:Isn't the behaviour the same here on the other skins? *:I agree it's not great having one item in a menu, but I think this case is quite rare since on most wikis move privilege is added along with page protection and deletion. There is a trade off here between the complexity of maintaining multiple variants of the skin in different circumstances and what looks best. Here we could add special treatment for the one item menu but we'd need to add additional code complexity and tests to cover it. Hope this insight is helpful. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 14:32, 6 July 2022 (UTC) == Actions menu overflows when main menu is active (Vector 2022) == {{Tracked|T311471}} When the main menu is active (meaning visible) and the window is quite narrow the actions menu (Read, Edit source, Add topic, View history) doesn't get condensed in the "More" drop down menu, resulting in a very ugly overflow. [[User:L.xschlag|L.xschlag]] ([[User talk:L.xschlag|talk]]) 11:41, 1 July 2022 (UTC) :@[[User:L.xschlag|L.xschlag]] - thank you for your feedback! This should now be fixed, let us know if you continue seeing issues. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 13:34, 11 July 2022 (UTC) == Audio player issues (Vector 2022) == When pressing play from a wikipedia article (e.g. first clip in [[:w:en:Aftermath_(Rolling_Stones_album)]]), the page changes text colour from black to pale grey. Almost unreadable. This dead time varies from a few seconds to many minutes, probably caused by unsteady connection on my side. I tried opening 2-3-4... windows with the same article, and some windows seem to be stuck indefinitely while others play with minimal (but still annoying) delay. If I press play directly from file description page ( [[:w:en:File:Under_My_Thumb.ogg]]), it always plays instantly and the text always stays black. Win 10 Home / Chrome 102.0.5005.115 (64-bit) [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 19:29, 3 July 2022 (UTC) :I've flagged this bug to the developers of [[Extension:TimedMediaHandler]]. This is not related to this project. I'll let you know if I hear anything back. Thanks for reporting! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:43, 11 July 2022 (UTC) == Language mix in the interface == Pardon me if this had already been discussed here. It seems that the language of the interface (as set in preferences) mixes up with local-language elements where it shouldn't. # My preferences are always "interface=en", and thus I always see "Contents Beginning" in the TOC section - be it Chinese, Russian or Spanish wiki. # The pink box above TOC in ru-wiki says "On this Википедия<sup>[sic!]</sup> the language links are at the top of the page across from the article title. Go to top." In zh-wiki, however, the message is correctly "On this Wikipedia the language links ..." [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 21:23, 3 July 2022 (UTC) :Thank you @[[User:Retired electrician|Retired electrician]] for reporting this. That's odd. 🤔 [[betawiki:MediaWiki:Vector-language-redirect-to-top/en|The source code]] is: <tt><nowiki>On this {{SITENAME}} the language links</nowiki></tt>... - so apparently, something about <nowiki>{{SITENAME}}</nowiki> isn't working here. But I don't know what yet. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:20, 6 July 2022 (UTC) == Where are the categories? == Hi this is my first time looking at the prototype, so apologies if this question has been answered elsewhere - where are the categories? [[User:MassiveEartha|MassiveEartha]] ([[User talk:MassiveEartha|talk]]) 04:15, 5 July 2022 (UTC) :Hello @[[User:MassiveEartha|MassiveEartha]]. I'm sorry that you felt confused. We don't touch elements such as categories. These prototypes were only created for editors to help us decide on the visual design matters. If the categories aren't displayed in any of the prototypes, then it's definitely unintentional and also irrelevant to what we do. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:02, 6 July 2022 (UTC) == 開発者集団は日本語版を軽視していると思われるThe group of developers seems to downplay the Japanese version == 日本語版の利用者の一人としては、開発者の集団は日本語版を軽視していると考える。一つの証拠として開発者からの意見を求めるメッセージが英語だけで書かれていたことを挙げておく。機械翻訳があるのだから英語と共に日本語を添えることは簡単なことのはずである。それすらせずにVectorからVector2022への変更を強行したことは、一種の文化帝国主義であると評さざるを得ない。As one of the users of the Japanese version, I think that the group of developers disregards the Japanese version. One proof is that the message for the developer's opinion was written in English only. Since there is machine translation, it should be easy to add Japanese along with English. It must be said that forcing the change from Vector to Vector 2022 without doing so is a kind of cultural imperialism.--[[Special:Contributions/27.85.205.84|27.85.205.84]] 07:17, 5 July 2022 (UTC) :Hello 27.85.205.84. Do you maybe know good open-source machine translators working for Japanese and English? I've noticed that Google Translate doesn't work for these languages well. Sometimes it changes words, meanings, and the tone of entire sentences completely. I could write in Polish, my first language, but I'm sure that would be even more difficult. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:15, 6 July 2022 (UTC) == Vector 2022を強要する行為は、開発者が読者を軽視していることの証拠である The act of forcing Vector 2022 is evidence that developers are downplaying their readers. == 開発者(の集団)はアカウントユーザーなら自分で好きなスキンを使えるのだから、あまり出来がよいとは言えないVector 2022を強要してっもかまわないと考えているようである。しかし、元々Vector 2022は読者として快適に使えることを考慮していない。開発者(の集団)は読者がいなければいくら記事を作っても意味がないということを忘れているのだろうか。It seems that developers (a group of people) are willing to force Vector 2022, which is not very good, because account users can use their favorite skins. However, originally Vector 2022 did not consider it to be comfortable to use as a reader. Do developers (groups) forget that it doesn't make sense to write an article without a reader?--[[Special:Contributions/27.85.205.84|27.85.205.84]] 07:29, 5 July 2022 (UTC) :Hello! As I can see, the translation was done by Google Translate. It's not good. I've used DeepL and this message is very different in English. Why do you think Vector 2022 was not originally designed to be comfortable to use as a reader? I would like to understand what made you think so. :こんにちは! ご覧のとおり、翻訳はGoogle翻訳によって行われました。 良くない。 私はDeepLを使用しましたが、このメッセージは英語では大きく異なります。 なぜVector2022は、もともとリーダーとして快適に使用できるように設計されていなかったと思いますか? どうしてそう思ったのか理解したい。 [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:06, 12 July 2022 (UTC) :: [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)-san]], your great DeepL-ed message causes a [[:ja:Wikipedia:削除依頼/Wikipedia:井戸端/subj/デスクトップ版外装(スキン)改善バージョンの実装について|deletion discussion]] due to copyright violation. I wish a good Foundation staff would deeply understand the copyright policy in Wikipedia and recognize that copypasting from machine translation could violate the copyright that was attributed to that translation service. :: So, while I'm not the original poster of this section, let me answer the question: :: > Why do you think Vector 2022 was not originally designed to be comfortable to use as a reader? :: If you think the only problem is new Vector 2022 design itself, I must say you are missing an important point: how you all introduced the new skin. All of the changes has never been announced in jawiki before being applied (and unfortunately, after that, until today). Many of the editors, the readers, the users were surprised at the new design all of the sudden, and not a few of them regarded it as a big bug or something. :: You may wonder, "we let you know this in advance, via a member of your community." That's true, partially. [[User:AppleRingo777|AppleRingo777-san]] took your messages and passed them to us per your instruction. I heard that you (or someone in Foundation) asked to post the message in WP:NEWS. How did you determine that WP:NEWS, generally where announcements '''only for the editors''' are posted, was enough to communicate this important news that obviously affected the entirety of community members including the readers? Will you also assign the responsibility on this to AppleRingo777-san, a good community member? I cannot help but want the Foundation to realize that you all destroyed our trust. --[[Special:Contributions/2400:4052:3420:4500:444C:45BF:13AC:59E2|2400:4052:3420:4500:444C:45BF:13AC:59E2]] 14:40, 14 July 2022 (UTC) == Listed coordinates overlapping with header weirdly == {{Tracked|T281974}} for an example of this, see wp's [[:en:London|london]] article ([https://imgur.com/a/rEngM3R screenshot]) [[User:LarstonMarston|LarstonMarston]] ([[User talk:LarstonMarston|talk]]) 20:00, 5 July 2022 (UTC) :Thank you @[[User:LarstonMarston|LarstonMarston]]. In this case, we need to fix the bug together with the communities - some code should be changed by editors on each wiki with this bug separately. We can help (and we're working on it). [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:11, 6 July 2022 (UTC) ::thanks, good to hear [[User:LarstonMarston|LarstonMarston]] ([[User talk:LarstonMarston|talk]]) 20:06, 6 July 2022 (UTC) == Default to Collapsed Menu Exposed TOC == {{Tracked|T287609}} I was trying to figure out why I didn't like the new TOC, and then it hit me that the main reason was that it is hidden by the side menu when you first visit a page (I very rarely login to Wikipedia, and I'm thinking that's the norm for most visitors). Then I was thinking that I almost never use the main navigation links, they just aren't part of my normal use case of visiting Wikipedia (it is to learn a specific thing that I don't currently know enough about). I was going to post to make it possible to hide the main nav, but then realized that you already built it, but the default is for it to show. My hypothesis is that the bulk of users don't look or click on any of the menu items, and that the menu should be hidden by default and the TOC exposed above the fold. [[Special:Contributions/195.134.163.110|195.134.163.110]] 10:34, 6 July 2022 (UTC) :Yes, TOC should be exposed above the article not on the right. In fact in desktop view if I click PC version it does not open stuff on the left. [[Special:Contributions/2A00:1370:8184:2478:A928:87EF:D073:FEEA|2A00:1370:8184:2478:A928:87EF:D073:FEEA]] 16:22, 6 July 2022 (UTC) :Thank you for your feedback! We are planning on implementing this change within the next couple of weeks. Progress can be tracked in the phabricator ticket linked above. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:04, 11 July 2022 (UTC) ::I would like you to give logged-in users the right to choose that as well. If you knew about these plans, don't you think that was a little premature to set Vector (2022) as the default in JAWP ? If you make changes right after you start it in JAWP, Japanese users will be confused. --[[User:呉野|呉野]] ([[User talk:呉野|talk]]) 13:21, 14 July 2022 (UTC) == Replace the "new section" tab text with "+" gadget not working. == {{Fixed}} On the English Wikipedia upon switching to Modern Vector the aforementioned gadget ceases to function as intended. [[User:Nathanielcwm|Nathanielcwm]] ([[User talk:Nathanielcwm|talk]]) 13:14, 6 July 2022 (UTC) :Looks like the gadget is setup to only work on Vector and Monobook. I have updated it to also apply to Vector 2022 skin (https://en.wikipedia.org/w/index.php?title=MediaWiki%3AGadget-addsection-plus.js&type=revision&diff=1096783301&oldid=1047498910) [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 15:59, 6 July 2022 (UTC) == July == @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: Does Vector 2022 will be deployed (as default) at all Wikimedia wikis until the end of July, as it is written [[Reading/Web/Desktop Improvements|here]]? I am asking this because I see that there is still some work to do and the deadline written there changed several times. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 21:56, 6 July 2022 (UTC) :Hello @[[User:NGC 54|NGC 54]], thanks for this question. This information is already outdated. It will ''not'' be deployed in July. We hope to send an update to the village pumps next week. We're working on the announcement right now. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 16:01, 7 July 2022 (UTC) == Language switching == Hi, I really appreciate the suggestion of translations within the language button, thank you! [[Special:Contributions/37.103.14.65|37.103.14.65]] 09:06, 7 July 2022 (UTC) :Thanks! Appreciation also goes to the [[Wikimedia Language engineering]] team, because they have made this particular change. We have "only" provided the language button :) [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:01, 12 July 2022 (UTC) == Vector (2022)のウィキペディア日本語版への導入について About the introduction of Vector (2022) to the Japanese version of Wikipedia == 「[[:ja:Wikipedia:井戸端/subj/デスクトップ版外装(スキン)改善バージョンの実装について]]」での案内によると7月14日までこのページでコメントを受け付けるとのことなので意見を書く。--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:25, 8 July 2022 (UTC) * 開発者は開発すること自体に喜びを感じるべきであり、日本語版で行ったように強引に導入して「見えるところ」に成果が表れることに喜びを感じるべきでない。 * 開発者は裏方として、開発に専念するべきであり、それを使うかどうかは「利用者」の判断にゆだねるべきである。 * スキンはインフラストラクチャーである。技術者が陥りがちな間違いだが「新しければよい」というものではない。 * 現在のVector (2022)は完成品とは言えずベータテストの段階でしかない。この段階で全面導入を進めようとするのは技術者の姿勢として適切でない。ベータテストは希望者を募って行うべきである。 * Vector (2022)をデフォルトのスキンとすることについて、本当に開発者チームに権限が与えられているのか。証拠があるなら、リンクをつけて示してほしい。 * 今回の経緯を見ると「読者」に対する観点が脱落している。「読者」のいない記事に何の意味があるのだろうか。 :ja: Wikipedia: Idobata / subj / Desktop version According to the guidance on implementing the improved exterior (skin) version, comments will be accepted on this page until July 14, so I will write my opinion. * Developers should be delighted with the development itself, and should not be delighted with the "visible" results of the forcible introduction as was done in the Japanese version. * Developers should concentrate on development behind the scenes and leave it to the "user" to decide whether or not to use it. * Skins are infrastructure. It's a mistake that engineers tend to make, but it's not "just new." * The current Vector (2022) is not a finished product, it is only in the beta test stage. It is not appropriate as an engineer's attitude to proceed with full-scale introduction at this stage. Beta testing should be done by recruiting applicants. * Is the developer team really empowered to make Vector (2022) the default skin? If you have proof, please link to it. * Looking at the history of this time, the viewpoint for "readers" is missing. What does an article without a "reader" mean? [[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:25, 8 July 2022 (UTC) *:Hi @[[User:匿竜類|匿竜類]] - Thank you for your feedback and for the bug reports below. We are currently in the process of taking the Vector (2022) skin out of beta testing/pilot mode and into the stage where we scale the skin, with the hopes of making it the default on all the wikis. Over the course of the next month, we will be hosting conversations with the largest Wikipedias and getting their feedback on the skin, similar to our conversations with Japanese Wikipedia right now. Even when default, logged-in users will still be able to chose whether they want to use the skin or not. If they decide not to use it, they can turn it off at any moment in their user preferences. *:In terms of readers, for every change we have made when building the skin, we have tested both quantitatively and qualitatively with readers and well as editors. To access more detail on the research and testing we have done, please go [[Reading/Web/Desktop Improvements/Features|to the Features page]] and select the feature you are interested in learning about. From there, you can read the sections named Quantitative research or Qualitative research to see the testing we have done. In addition, we have also done more open-ended testing with readers to identify the issues with the skin starting in 2020 until now. Please see the [[Reading/Web/Desktop Improvements/Repository/Hureo User Research Report/ja|Hureo User Research Report]] with Readers and Editors, the [[Reading/Web/Desktop Improvements/Repository/Wikimania Stockholm research report/ja|Wikimania Stockholm research report]], the [https://nbviewer.org/github/wikimedia-research/Desktop-behavior-analysis-Aug-2019/blob/master/Desktop_usage_behavior_analysis.ipynb Wikimedia Desktop Usage and Behavior Data Analysis], or the [[Reading/Web/Desktop Improvements/Repository/Sticky Header and Table of Contents User Testing/ja|Sticky Header and Table of Contents User Testing]] reports for some examples of the studies we have done with readers (which have translations in Japanese), what we have learned, and how we used those learnings to create the new skin. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 10:00, 11 July 2022 (UTC) == Vector (2022)の不具合の報告 Report a bug in Vector (2022) == {{Tracked|T303267}} {{Tracked|T281974}} 日本語版でVector (2022)を使うと、左側に「このWikipediaでは言語間リンクがページの先頭にある記事タイトルの向かい側に設置されています。ページの先頭をご覧ください。」と表示されるのだが、実際には「記事タイトル」は「ページの先頭」ではなくこのメッセージの下に表示される。以前は、このようなことがなかったように思うので一時的なものかもしれないが、症状が出ていることを確認してほしい。When I use Vector (2022) in the Japanese version, it says "In this Wikipedia, the interlingual link is located opposite the article title at the top of the page. Please see the top of the page." However, in reality, the "article title" is displayed below this message instead of "at the top of the page". I don't think this happened before, so it may be temporary, but please make sure that you have symptoms.--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 02:42, 8 July 2022 (UTC) :上記不具合を報告してから、1日経過していますが、応答がありません。[[:ja:Wikipedia:表示改善依頼#Vector(2022)スキンで、バッジと地図のタグが重なって表示される#]]によると、どうやらこの種の不具合はファブリケータで処理することになっているようですが、そちらの方への連絡はしていただけたのでしょうか。とりあえず担当者の応答を求めます。One day has passed since I reported the above problem, but there is no response. ja: Wikipedia: Display improvement request #Vector (2022) In the skin, the badge and the map tag are displayed overlapping. According to #, it seems that this kind of defect is to be handled by the fabricator. Could you contact that person? For the time being, ask for the response of the person in charge.--[[User:匿竜類|匿竜類]] ([[User talk:匿竜類|talk]]) 03:05, 9 July 2022 (UTC) ::Hello! The coordinates issue is known but the language one wasn't. Thank you for bringing it to our attention. ::I will reply with more details next week. Have a great weekend and thank you for the bug reports. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 18:27, 9 July 2022 (UTC) :::These are tracked in [[phab:T303267]] and [[phab:T281974]]. Thanks for the report! [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:39, 11 July 2022 (UTC) == Merge [ca-view] and [ca-nstab-main] in the article toolbar == Currently, in the article toolbar, we have two links (Read and Article) that lead to the same location. One of them is located in the left and the other one is located in the right navigation. This can be confusing to readers, and also adds unnecessary weight to the toolbar. [https://imgur.com/56mbihi Current look]. It would be good if we could merge these two tabs into one. Ideally, the best solution, in my opinion, would be to merge the right and left navigation and center the items, [https://imgur.com/a/ih52zYZ like this]. Please tell me what you think about this. Thank you! — [[User:Aca|Aca]] ([[User talk:Aca|talk]]) 11:18, 9 July 2022 (UTC) :{{O}}. Now, the tabs are clear. You have 2 pages: the article and the talk page. You can select 1 action at a time for each of them: reading, visual editing, source editing, and viewing the history. Form the proposed design, you can understand that the tabs led to different types of pages. The watch is something not related to the article? And if now you are on article tabs, if you would press on the editing source tab, you would arrive on a page not related to the article (this is a possible confusion)? And so on. "This can be confusing to readers," - how so? Are there any data? And if there are, are there any data that the proposed design is better? P.S. I also dislike the proposed design, due to visual reasons. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:00, 9 July 2022 (UTC) == Big blank space when on a big zoom == Unlike the old layout that adjust depending of the size of zoom, the new format seems to follow a single size that, when zoomed in, creates a big blank space like if the page was still loading It needs be fixed so the wiki pages can be better for people that have vison issues - [[:en:User:Meganinja202|User:Meganinja202]] | [[:en:User_talk:Meganinja202|¿]] 10:17:00 11 July 2022 (UTC) [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 10:17, 11 July 2022 (UTC) :[[User:Meganinja202]] are you taking about [[Reading/Web/Desktop_Improvements/Features/Limiting_content_width]] or reporting a bug? If the latter, what browser and device are you using? [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 16:34, 11 July 2022 (UTC) ::i think should be a bug since its a thing that happens from top to bottom of the page and not from the sides, i am use Chromium Based MS Edge [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 17:02, 11 July 2022 (UTC) == Language box recommendation == A minor suggestion: why not insert the language box on the title header so I don't have to go all up to the top of the page to change language versions. So yeah, thanks! [[User:PeaceSeekers|PeaceSeekers]] ([[User talk:PeaceSeekers|talk]]) 11:00, 11 July 2022 (UTC) :ya, they should had kept the language bar on the side of page instead of the top, leaving the language option on top only on mobile/touch machines [[User:Meganinja202|Meganinja202]] ([[User talk:Meganinja202|talk]]) 17:03, 11 July 2022 (UTC) :@[[User:PeaceSeekers|PeaceSeekers]] - do you use the site while logged-in? If so, you can access the language switching button from the persistent ("sticky") header at the top of the page while you're scrolling. We are also in discussion of bringing this functionality to all logged-in users as well. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 08:15, 12 July 2022 (UTC) ::I did log in, but I can't see it though ... what I have is only, from the left: the search button, article title, discussion page, edit history, watchlist and my profile stuff (for lack of better words). So that's that. [[User:PeaceSeekers|PeaceSeekers]] ([[User talk:PeaceSeekers|talk]]) 08:43, 12 July 2022 (UTC) == What I still would love to see different solutions to == I'm very much looking forward to not having the text fill an entire wide screen. This will make Wikipedia far easier to read on big screens. Thanks! A few things that still don't work for me: '''Table of contents''' If I haven't collapsed the left menu, the ToC is not visible when I start reading the article. This makes it more difficult to get an overview. It's also ''generally'' more difficult to get an overview of the article content, as I need to go to the ToC in the sidebar and scroll down to see everything on big pages (like a Village Pump). This both makes it more difficult for me to conceptualize what's on the page – as I've tested this, I've realised I find it challenging to get a grasp of a page if I can't see the various topics at the same time – and adds more work, as I have to move the mouse pointer to the ToC to be able to scroll. I would have much preferred if it used more of the space available to get around this. '''My contributions''' My own user contributions is something I use all the time – it's my way of getting back to what I was doing before. Making it less accessible in the top menu is wrench thrown into my workflow. '''Language links''' This is my main issue. I use other languages ''all the time''. As a reader, I glance at them to conceptualise the topic – which languages have written about this subject? This hints at things that aren't available in the content itself. As an editor, I check out other languages to see what sources they have and so on. Having to click to even see if there are languages I can read is an extra step that both requires more work, but also makes it less inviting, as the opportunity doesn't stare me in the face. This is so central to my workflow that it might in itself be reason to keep using Vector 2010, but that's certainly not my preferred solution. [[User:Julle|Julle]] ([[User talk:Julle|talk]]) 10:13, 12 July 2022 (UTC) == feedback == asbra med maxbredd! coolt att wikipedia tar steget in i 2010-talet och blir läsbart på stor skärm. språklänkarna blir mycket sämre. man borde kunna se språken direkt och klicka på dem, det är en sak man använder hela tiden. jag förstår inte varför ni har bytt ut texten i användarmenyn mot symboler? det var tydligare med text. nu måste man gissa vad de betyder och många kommer aldrig lista ut det. man borde inte behöva skrolla INNE I innehållsförteckningen för att se hela. sjukt störande att behöva gå till den och skrolla I DEN för att se vad som finns på sidan. [[Special:Contributions/81.92.27.129|81.92.27.129]] 18:12, 12 July 2022 (UTC) :Thanks for the feedback! :(google translation) :* max width: cool that wikipedia takes the step into the 2010s and becomes readable on the big screen. :* language links: you should be able to see the languages ​​directly and click on them, it is one thing you use all the time. :* Icons: I do not understand why you have replaced the text in the user menu with symbols? it was clearer with text. now you have to guess what they mean and many will never figure it out. :* Table of contents: you should not have to scroll INSIDE the table of contents to see the whole thing. Very annoying to have to go to it and scroll IN IT to see what's on the page. [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 19:00, 12 July 2022 (UTC) :::("Sjukt störande", which the machine translation rendered as "ill disturbing", means "very annoying".) [[User:Julle|Julle]] ([[User talk:Julle|talk]]) 00:15, 13 July 2022 (UTC) == More TOC concerns == On pages with long headings (f.i. [[Wikipedia:Closure_requests]]), the new TOC is highly impractical. The headings are difficult to parse, sometimes cutting words in two. A lot of scrolling is also required to get an overview of what discussions to close. Will it be possible to go back to the old TOC on a per-page base? I can imagine a lot of non-article pages will have similar problems (including this one). Less importantly, I noticed that the default is having only the top heading displayed. In some pages / articles there are very few top-level headings, and this would always require the reader to uncollapse. Can this be made more dynamic? [[User:Femke|Femke]] ([[User talk:Femke|talk]]) 18:09, 14 July 2022 (UTC) :Would it be possible (probably only on bigger screens) to use the empty white space on the right for tools (for logged-in editors), so that the TOC is less cramped? Solves two problems in one. [[User:Femke|Femke]] ([[User talk:Femke|talk]]) 17:00, 18 July 2022 (UTC) == incorrect translation Vector 2022(jpwiki) == The information text on where to switch languages is partially translated incorrectly. I think , "このWikipediaでは言語間リンクがページの先頭にある記事タイトルの向かい側に設置されています。" is a slightly mistaken translation. This may mean that the language switch is outside the display. You probably meant to write that, "他言語版へのリンクは、ページ先頭の記事タイトルの右側にあります。". But I would rather you don't adopt this with no check. [[User:呉野|呉野]] ([[User talk:呉野|talk]]) 10:01, 15 July 2022 (UTC) == 'Talk' and 'Contributions' buttons shouldn't be hidden in the navigation bar's drop down menu. == We shouldn't have to click twice to get to our '''Talk''' and '''Contribution''' pages from the navigation bar. I mean, there's already a bunch of wasted white space to right of the search box and to the the left of our Userpage button for those two icons to be added in the nav bar without any problems. [[User:Some1|Some1]] ([[User talk:Some1|talk]]) 02:57, 17 July 2022 (UTC) == Simple English sidebar == I notice in Simple English with the 2022 Vector, the menus on the left side of the page are to the left of the page text as they should be, but they are far above rather than beside the text. [[User:Jim.henderson|Jim.henderson]] ([[User talk:Jim.henderson|talk]]) 05:47, 17 July 2022 (UTC) == The new sidebar TOC is confusive, not intuitive, unusable == I strongly oppose the new sidebar TOC. It is extremely confusing, not intuitive, and unusable. The removal of the numbering for paragraphs and their transformation into collapsible lists, will make the articles and discussions unreadable, as their structure will be completely unclear. The TOC at the top of the article right below the lead text was perfect for giving a clear impression of the article's structure and for exploring its contents. I think that keeping both the old and the new TOC (if the latter is really necessary) would be a good solution. The new TOC proves useful only in the bottom sections of very long articles. [[Special:Contributions/2001:B07:A2A:1884:D5D:3606:C70C:5366|2001:B07:A2A:1884:D5D:3606:C70C:5366]] 14:03, 17 July 2022 (UTC) * Second that. Another point of note is that the narrow sidebar is a poor match for long section titles. Even in English wikipedia, some headings must be split in two narrow lines, or three. Other languages, that are naturally more verboise than English, are even more affected. [[User:Retired electrician|Retired electrician]] ([[User talk:Retired electrician|talk]]) 08:16, 29 July 2022 (UTC) == This gives me depression == By merely see this happen week-by-week, I can see this sacred project gradually being destroyed. I wish I could stop this. – [[User:Ilovemydoodle2|Ilovemydoodle2]] ([[User talk:Ilovemydoodle2|talk]]) 07:35, 18 July 2022 (UTC) == wrong name for a language == someone is having a laugh, or got really confused about translation. In the main page https://www.wikipedia.org/, '''Français''' now appears as '''anglais''', both in the top 'wheel' and in the 'Read Wikipedia in your language' drop-down. This is very wrong. What other languages have been disappeared in this way ? a bit of QA would go a long way :-) [[Special:Contributions/92.16.98.145|92.16.98.145]] 16:23, 19 July 2022 (UTC) :Thanks for letting us know! This looks like a mistake/error on translatewiki.net. We'll try to fix that immediately. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 18:28, 19 July 2022 (UTC) ::FYI this wasn't related to the project. ::See related Reddit thread for details on what happened here if you are curious: https://www.reddit.com/r/wikipedia/comments/w2iidz/why_anglais_did_someone_sabotage_it/ [[User:Jdlrobson|Jdlrobson]] ([[User talk:Jdlrobson|talk]]) 20:03, 20 July 2022 (UTC) == coordinates being weird (again) == there was an issue a little while ago where location coordinates in an article would overlap with the header. that's fixed now, but some icons are still uncomfortably close to them, like the FA star; for an example of this, see the english wiki's [[:en:India|India]] article ([https://imgur.com/a/uuXPMzk screenshot]) [[Special:Contributions/2600:1700:7AA1:2400:9CA1:1220:42FD:1F12|2600:1700:7AA1:2400:9CA1:1220:42FD:1F12]] 20:17, 20 July 2022 (UTC) == General concerns! == Well I was part of the process for quite some time now. And up until the move of the TOC from inside the content to the sidebar it was okay with me. I had some minor things, I thought I will get used to: the white space (anyone wanting that, can narrow their window), some inconsistencies (compare [[#A few more issues with the Page header vs Sticky header icons]]), the language switcher, which I fear will leave the impression of reading ''the same'' thing in different languages (compare [[Talk:Reading/Web/Desktop_Improvements/Archive3#Language_Selector_misunderstandable]], as a side-note: nothing happened here, at least nothing I recognized). But today I got this message: [[Topic:Wsfx4tbwzkgamaek]] asking for a translation for [[Reading/Web/Desktop_Improvements/Updates/2022-07_for_the_largest_wikis]]. Let me cite: *'''"...before discussing the change itself"''' *'''"...that allows for a way to identify the needs of the community from the new skin."''' *'''"We would love to see the Vector 2022 skin [...] become the new default across all wikis..."''' *'''"We will be ready to begin making the change at the end of August (and not in July, as previously announced), when the ''visual refinements'' and other ''deployment blockers'' are ready."''' *'''"The goal for that discussion will be to identify breaking issues or opportunities for improvement for the new skin. It will be important for us to reduce the risk of bugs or imperfections that would be particularly troublesome on [insert your language] Wikipedia"''' All that reads like: Well, we're just talking, let's see, what needs to be done, that everyone is happy. There are some things that need to be done anyways. Now let's read those two cites: *'''"...difficult discussions about the launch as the default"''' (compare [[Topic:Wsfx4tbwzkgamaek]]) *'''"...until our improvements are default on all wikis in July 2022."''' (compare [[Reading/Web/Desktop_Improvements]] So isn't this not just a request for bug reports instead of a "discussion"? Is this not more of a fear of "Flak" instead of "needs of the community"? Isn't it happening anyways, instead of you "loving to see it"? What about all the other projects, wikibooks for example ("[insert your language] Wikipedia")? I understand, you do the work, you decide. '''But:''' * Is it wise to "discuss" while there are still tasks to be done and decisions to be made? (compare [[Reading/Web/Desktop_Improvements/Features/Visual_Refinements]], which by the way doesn't even seem finished, and for example [[#MediaWiki:Sidebar]]) * Is the Date of the end of August (6 weeks) really feasible? Who will translate all the feedback that will come in german? * Is it good to leave the impression, that communities will have a choice (compare [[#Jawiki has NOT reached consensus on implementing Vector 2022 yet]])? Some suggestions, if I may: # Why not try to slow the process down? Why the haste? One could remove the deadlines and refine everything. ''Then'' ask the communities for bug reports. # Why not try some marketing "tricks"? I think the discussion about the white space clearly shows that desktop ''improvements'' are highly subjective. Why not use for example ''skin changes''? Another Option could be deploying Vector 2022 only for not logged in users and hence prolong/smooth the transition-process creating time for bug reports and discussions. Most of anonymous usage would probably not care for the change, as long as the content is there. On another plus-side it will create "data" on how the menu-usage changes and community-links are perceived. It will probably even create data on how many logged in users switch to the new layout deliberately and or switch back hence providing "hard" success-data. # Would it be that bad to really leave the community a choice? # If you are relying on volunteers, grant them a little more slack. Bug reports from the community need time: Bugs need to be recognized as bugs, they need to be reported, triaged ''and'' handled. Is this possible in 6 weeks? Volunteers might have another life, a job, kids, a week might be pretty short notice. Phabricator-use is not that trivial. # Let's talk or try, if the new design might eventually be a problem for recruiting new volunteers. Did anyone think about a possible impact of hiding ''community-links'' in collapsed menus? Nobody seems to talk about community-pages or discussion-pages or even other project-scopes. Is the new menu-structure as fitting for these as for wikipedia-articles? I'm deeply saddened. The new TOC will make my life within wikimedia really hard and I commented about that early on (compare [[Reading/Web/Desktop_Improvements/Third_prototype_testing/Feedback#Benutzername:HirnSpuk|here, bullet 7]]). I think all the TOC-comments on this page (see above) should raise at least some concern. And last but not least, I'm deeply troubled, that the new language-links will do more harm, than good. So, ping @[[User:OVasileva (WMF)|OVasileva (WMF)]] and @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], my sincere apology, I don't mean to be rude or mean and I appreciate your work and the work of your colleagues. But I don't want to volunteer for the translation-request, because all of the above mentioned problems. Regards [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 22:25, 20 July 2022 (UTC) :Hello @[[User:HirnSpuk|HirnSpuk]]. Thank you for your outstanding involvement, and appreciation for our work. I'm glad to see that. Also, thank you for your sincere, thoughtful, and thorough comment with all the links and quotes. I think I understand what your approach is, I'm happy that you're saying this. :Before I answer the questions, I'll admit/confirm that: :# The ToC work hasn't been finished yet. So haven't the visual refinements. There's a list of issues labelled as "[[phab:T309972|deployment blockers]]", by which we mean issues we need to solve before making it the default everywhere. I hope this will make you less sad! :# Bug reports do need time. Phabricator is not that trivial. :# While indeed focusing on the most typical use cases, like interacting with articles. :# In some discussions, it has been confusing what exactly is for the individual communities to choose between. :Regarding the questions, my answers to the easiest part: :# We've been working since 2019, most work is behind us and we're headed towards the end. Now, we need to make sure what else the largest communities may need. :# What about all the other projects - the message I asked if you could translate is dedicated to the largest communities of the top language versions of Wikipedia. :# This is why in that message, we're initiating a pre-discussion about culture of collaboration. After that, we'll ask for bug reports and other technical requests. :# We use the name Desktop Improvements because the point is to make changes that are actual measured improvements. Only some of the visual refinements are really subjective. But regarding the feature changes, the idea for each of these is that it should be an improvement compared to Legacy Vector. :# We're part of [[Core Experiences]] and work closely with the teams focusing on newbies and more experienced editors. It's our plan to make entry points for new volunteers prominent, in collaboration with Growth. We hope that Desktop Improvements will be an introduction to even more sophisticated changes addressing very specific use cases. :OK, enough now for one comment. Let's keep talking, though. [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 01:30, 21 July 2022 (UTC) :: @[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]], because you said "let's keep talking", let me react to your latter 5 points. ::# I do not want to diminish in any way the work you (plural) have done since 2019 and I think the plan is good. But I'm convinced, that the timing is not right. "The end of August" I find far to soon if you "need to make sure what else the largest communities may need." ::# I wasn't able to find the "we talk to the «big guys» first"-idea anywhere. The only thing I find is "We would like our improvements to be default on all wikis in August/September 2022." There will probably not be time to talk to the «small guys». And in addition, the text to translate suggest, that there is a choice, and you'd like to "talk". My impression is you want to ask: how can we best ask for bug reports. That might (and probably will) work, but I don't want to be part of exactly this approach. ::# same as first and second. ::# How is the improvement measured? Is there any "hard data" anywhere? Everything needs more clicks hence more time. It "looks" a little better and modern, which I also find necessary and good. But what is actually "improved"? ::#*I need more scrolling for the TOC, ::#* I will need more work (and creative ideas btw) for rework of community-pages that rely on the "old" version of the TOC at the moment, and even worse, I need to check the visual appearance and usability of pages in even more configurations (to mobile and desktop and VE and source, now I need to add different skins), ::#* I need more clicks for almost anything (if menus are hidden, but this is nearly imperative, to get at least some use out of the new ToC), ::#* I'm deeply troubled about the "impression" some changes might make (which hence wouldn't be an improvement either and which is by default not measurable)... ::#* What about the visually impaired? Is it an improvement for them too, any hard data? ::#:Please, feel free to elaborate. I know it would be baloney to change the name in the last 6 weeks of the work. My point is not to do that, but to take a step back, review what's done so far, and if the decision will be made to prolong the process a really long time, then ''maybe'' one ''might'' think about a change, and if it's only to get less of the "if you do this I'll be done with wiki..."-criticism that's just consuming time for everyone. ::# I'm not addressing technical issues. It's the possible "hiding" of prominent community-links in the sidebar by using elaborate restructuring and collapsing mechanisms. On that the single communities won't have influence as far as I see it at the moment. ::PS: I appreciate trying to cheer me up ("make you less sad"), but my sadness stems from the uncertainty how this will all work out. In the end the prototype is only a prototype. And how much work in the community must be done afterwards to facilitate the "improvements" is also not clear. The main point being, that I struggle with checking and cross-checking functionalities in different systems. It was okay until the move of the ToC. But as long as there is still work to be done, I can't even think about workarounds for not having the ToC where and how I was used to it. ::Regards [[User:HirnSpuk|HirnSpuk]] ([[User talk:HirnSpuk|talk]]) 07:34, 21 July 2022 (UTC) :::Hey @[[user:HirnSpuk|HirnSpuk]], thank you for your continued feedback. It's been super helpful. We've rewritten our message to German-language Wikipedia based on your thoughts and the learnings we've gotten through similar conversations on other wikis. We're going to post our next draft for translation this week - let us know what you think of it! We're open to suggestions. Your continued thoughts are much appreciated! :::In terms of your individual questions: :::# The timing is not right :::#* We really do believe that our changes are improvements already! We're eager to bring them to readers and editors. As you have pointed out, we've been building these for three years. We've received feedback from German-language Wikipedians, and many other communities. As you also know, we've performed prototype testing with editors across 30+ languages, and different types of quantitative testing on each feature. Many significant requests have already been discussed. :::#* The main reason we want to have this conversation now (while we're putting the finishing touches, like the visual refinements and changes to the table of contents) is that we'd like to see if any of the feedback might change what those finishing touches are. We'd also feel more confident with our plan once we know what the additional work we need to do is, if any. :::#* The process we're envisioning is to collect bugs and requests, and triage these into three categories: (1) the ones that must be done before the deployment, (2) the ones that can wait until after the deployment, and (3) the ones that we don't think are a priority. Our goal for the conversation with the communities is to establish what lies in each bucket such that the communities are comfortable with changing the default. :::#* We understand if a conversation might take longer on a given community, and do not plan on cutting any discussion short just to reach a deadline. We made a mistake with Japanese Wikipedia and made the change prior to acknowledging a common process. We'd like to avoid that mistake with the other wikis, hence the lengthier discussion with German-language Wikipedia. :::# The "we talk to the «big guys» first"-idea :::#* We try to take the approach of equity. We have conversations across the top 25 Wikipedias by size. We've attended a [[m:Wikisource Triage meetings|Wikisource Triage meeting]] and two [[m:SWAN|SWAN]] meetings. The set of pilot wikis is diverse. We inform the big and small communities about our office hours using different channels, incl. MassMessages, Tech News, Discord, Telegram, Facebook. We're going to have the interpretation support in the top UN languages. :::# How is the improvement measured? :::#* Thank you for pointing this out. This very crucial piece was missing. We'll be adding a summary of our findings to our future messages. :::#* You'll find the short answer [[:w:Wikipedia:Village_pump_(proposals)#UX_research_and_usability_testing|on the English Wikipedia Village Pump page]], quite paradoxically brought to everyone's attention using the "hidden" template. For details on any individual feature, go to the “features” section of our documentation, select the feature you are interested in, and review the qualitative and quantitative sections. :::# It's the possible "hiding" of prominent community-links in the sidebar by using elaborate restructuring and collapsing mechanisms. On that the single communities won't have influence as far as I see it at the moment. :::#* This is a great question. So far, our interviews with users have shown that newcomers are NOT more likely to begin contributing based on the number (or even presence) of community links. In fact, having so many options at hand made them feel unwelcomed to the interface as they didn't instinctively know where the links would lead, and thus, felt intimidated or lost. :::#* We think a better method is to have fewer links that are clearer to understand and pave more intuitive ways. These links are, among others, edit or history. We are working with the Growth and Editing teams to identify how we can increase the understanding of these links for readers and newcomers - both so they will know where the content they are reading is coming from, but also as a means of introducing them to contribution. See also: [[Core Experiences]]. :::# What about the visually impaired? Is it an improvement for them too, any hard data? :::#* We've been doing accessibility testings with the American Foundation for the Blind. You'll find more information in this task: [[phab:T310033|T310033]]. Generally though, part of this work goes beyond Desktop Improvements, and is done by our designers who build basic user interface elements for all the teams. :::Hey, on a side note, have you ever attended our office hours? I (Szymon) don't recall this. You'd have heard answers to some similar questions if you had joined us earlier. Anyway, feel invited. :::[[user:OVasileva (WMF)|OVasileva (WMF)]], [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 02:44, 29 July 2022 (UTC) ==Sorry but user expereince is kind of awful== Okay. I've given "Vector 2022" a shot for a while and it is just confusing and difficult to use. Too much animation-style issues. Too much whitespace. Difficult discovery of functions. Difficult to obtain a feeling of confidence in mastery. If I would have been keeping a log, I'd have dozens of gripes by now. I don't wish to waste time enumerating specific things because it's besides the point because the entire experience is bad. I can't hack it anymore. I thought I'd get used to it but I'm going back to Vector 2010. Keep things simple. Keep it static. I know many people but a lot of work into this and it was a valid attempt but it just didn't suceed in improving over Vector 2010. [[User:Jason Quinn|Jason Quinn]] ([[User talk:Jason Quinn|talk]]) 02:24, 26 July 2022 (UTC) == External link icon == The external link icon currently deployed on mediawiki.org looks horrible. What happened? The icon shown at [[phab:T261391]] in the "After" screenshot looks much better. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 19:55, 26 July 2022 (UTC) :@[[User:NGC 54|NGC 54]], what's the difference you're referring to? Could you maybe share a screenshot? [[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]] ([[User talk:SGrabarczuk (WMF)|talk]]) 23:36, 26 July 2022 (UTC) ::@[[User:SGrabarczuk (WMF)|SGrabarczuk (WMF)]]: Here. ::[[File:Vector2022 Broken External Link Icon.png|thumb|The icon looks thin and pixeled. Not like at Phabricator.]] --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:48, 27 July 2022 (UTC) :::I saw that the issue was already reported. Compare [https://phab.wmfusercontent.org/file/data/zm2w6tyla7ap4pm54oxw/PHID-FILE-jxp2g6oxik24v6zcst5o/image.png this] with [https://phab.wmfusercontent.org/file/data/6tvujxqmvz53tlojn4qi/PHID-FILE-gq23v5redy2o4ki63rnq/Screen_Shot_2022-07-21_at_11.46.24_AM.png this]. Also, for me it looks like the arrow is misshaped. --'''''[[User:NGC 54|<span style="color: #43b0ef;">NGC 54</span>]]''''' ([[User talk:NGC 54|<span style="color: #7cb8f4;">talk</span>]] | [[Special:Contributions/NGC 54|<span style="color: #7cb8f4;">contribs</span>]]) 10:53, 27 July 2022 (UTC) ::::Hi @[[User:NGC 54|NGC 54]] - thanks for your report. The icon is indeed broken as of right now. We're looking into this right now and hope to have a fix later this week or early next week. [[User:OVasileva (WMF)|OVasileva (WMF)]] ([[User talk:OVasileva (WMF)|talk]]) 12:05, 28 July 2022 (UTC) 44aowz2b6xemksc7yyugfqpx8stoafx Manual:System administration/tr 100 981525 5387272 5385005 2022-07-28T21:52:41Z Baris6161TURK 17188421 Created page with "=== E-posta bildirimleri gönderme ===" wikitext text/x-wiki <languages/> {{Maintenance scripts}} Bu sayfa, MediaWiki’nin [[Special:MyLanguage/Manual:Installation guide|kurulumunuzu]] tamamladıktan sonra yapmak isteyebileceğiniz ortak '''idari görevler''' talimatlarını birbirine bağlar. == Yapılandırma == :''{{ll|Manual:LocalSettings.php}} sayfasına bakın'' MediaWiki'yi web arayüzü üzerinden yüklediyseniz, ortak yapılandırma değişkenlerini ayarlayan [[Special:MyLanguage/Manual:Config script|ilk yapılandırma komut dosyası]] adlı kullanıcıyı zaten çalıştırdınız. MediaWiki'nin çeşitli yapılandırma ayarları vardır. {{ll|Manual:LocalSettings.php|LocalSettings.php}} içinde değiştirilmeleri gerekir. Tüm liste için {{ll|Manual:Configuration settings}} bakın. === Yüklemeleri aç ve kapat === :''{{ll|Manual:Configuring file uploads}} sayfasına bakın'' === Tasarım belirleme: Bir görünüm seçme === :''{{ll|Manual:Skin configuration}} sayfasına bakın'' Varsayılan kaplama, {{ll|Manual:$wgDefaultSkin|$wgDefaultSkin}} içindeki {{ll|Manual:LocalSettings.php|LocalSettings.php}} değişkenini değiştirerek ayarlanabilir. Diğer birkaç ayar da derilerle ilgili [[Special:MyLanguage/Manual:Configuration settings#Skins|ayarlanabilir]] olabilir. Bazı özel görünümler de var, [[Special:AllPages/Skin:]] kısmına bakın. === Logoyu veya favicon'u değiştirin === :''See {{ll|Manual:FAQ#Changing the interface}}' === Madde sayfalarına giden daha kısa URL'ler === :''{{ll|Manual:Short URL}} sayfasına bakın'' === E-posta bildirimleri gönderme === :''<span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:$wgEnableEmail}}</span>'' === Mobil uyumlu tasarım === :''{{ll|Manual:Mobiles, tablets and responsive design}} sayfasına bakın'' === Diğer === Yapılandırma ayarlarının bir listesi için, bakınız: * {{ll|Manual:Configuration settings}} * {{ll|Manual:Configuration settings (alphabetical)}} - alfabetik bir liste. == Yapılandırma Apache, PHP ve Veri Tabanı == [[w:MySQL|MySQL]] (veya [[w:PostgreSQL|Postgres]]) ikili paketlerini indirdiyseniz, [[w:Apache HTTP Server|Apache HTTP Sunucusu]] ve [[w:PHP|PHP]], olasılıklar sisteminiz için ayarlanmış bir kurulum betiği ile geldikleridir. Onları daha fazla ayarlamak için, bakınız: * {{ll|Apache configuration}} ** {{ll|Manual:robots.txt}} * {{ll|PHP configuration}} * Veritabanı ** {{ll|Manual:MySQL|MySQL}} or {{ll|Manual:MariaDB|MariaDB}} ** {{ll|Manual:PostgreSQL|PostgreSQL}} ** {{ll|Manual:SQLite|SQLite}} == Wikiyi hızlı yapma == :'''''{{ll|Manual:Performance tuning}}''' sayfasına bakın'' == İdari hakların belirlenmesi == MediaWiki izin tabanlı bir wiki sistemidir. Bu, kullanıcıların yalnızca yapmasına izin verilen eylemleri gerçekleştirebilecekleri anlamına gelir. Her kullanıcı için ayrı ayrı izin vermek sıkıcı ve pratik olamayacağından, MediaWiki'de önceden birkaç {{ll|Manual:User rights|nsp=0}} tanımlanmıştır. İhtiyaç duyduğunuz gibi yeni kullanıcı grupları da ilan edebilirsiniz. Bireysel [[Special:MyLanguage/Extension:Contents|uzantıları]] ayrıca yeni kullanıcı hakları oluşturmayı da gerektirebilir. Nasıl oluşturulduklarına bakılmaksızın, kullanıcı grupları {{ll|Manual:$wgGroupPermissions|$wgGroupPermissions}} dosyanızdaki {{ll|Manual:LocalSettings.php|LocalSettings.php}} ilişkisel dizisini değiştirerek tamamen özelleştirilebilir. * {{ll|Manual:User rights}} * {{ll|Manual:Preventing access}} * {{ll|Manual:Security}} === Hizmetli (Yönetici) === En yaygın kullanım. 'Hizmetli' olarak işaretlenen bir kullanıcı sayfaları silebilir ve geri alabilir, IP'leri engelleyebilir ve engelini kaldırabilir ve katkıda bulunan bir önceki kısma dönüşte gözden geçirme özelliği olan bir kısayol kullanabilir, daha fazla bilgi için bakınız. === Bürokratlar === Bu gruptaki kullanıcılar, kullanıcı haklarını [[Special:UserRights]] kullanarak değiştirebilir. === Bot === Kayıtlı bir bot hesabı. Bu kümedeki bir hesapta yapılan düzenlemeler, Son değişikliklerde varsayılan olarak görünmez; Bu, insan düzenlemelerini su baskını altında kalmadan toplu veri ithalatına yöneliktir. (Örneğin botlar tarafından yapılan değişiklikleri listelemek için ''&hidebots=0'' ekleyin, örneğin [https://en.wikipedia.org/w/wiki.phtml?title=Special:Recentchanges&hidebots=0 buna benzer]) == Uzantıları yükleme == :'''''{{ll|Manual:Extensions}}''' sayfasına bakın'' Uzantılar, yeni özellikler ekleyen veya ana MediaWiki çekirdeğinin işlevselliğini geliştiren PHP kodunun derlemeleridir. == Yerelleştirme == :'''''{{ll|Help:System message}}''' sayfasına bakın'' Bir vikinin dilini kullanıcı bazında değiştirmek isterseniz, bunu [[Special:Preferences]] ile yapılabilir. Viki ayarlarken yanlış dil seçtiyseniz, {{ll|Manual:LocalSettings.php|LocalSettings.php}} içindeki {{ll|Manual:$wgLanguageCode|$wgLanguageCode}} değerini değiştirmeniz yeterlidir. == Bakım betikleri == :'''''{{ll|Manual:Maintenance scripts}}''' sayfasına bakın'' MediaWiki'de idari görevler yapmanıza yardımcı olacak bazı bakım komut dosyaları vardır. == MediaWiki Güncelleme == :'''''{{ll|Manual:Upgrading}}''' sayfasına bakın'' == Veri alma == === Yedekleme === :'''''{{ll|Manual:Backing up a wiki}}''' sayfasına bakın'' Wikinizdeki verilerin düzenli olarak yedeklenmesi önemlidir. Bu veritabanı, yüklenen dosyalar ve uzantıları içerir. === Bir veritabanı dökümünü içe aktarma === :'''''{{ll|Manual:Importing XML dumps}}''' sayfasına bakın'' Bir Wikimedia wikinin yerel bir kopyasını istiyorsanız, [[:meta:Data dumps]] ve [http://download.wikipedia.org/ indirme siteside] genel bakışı inceleyin. === Mevcut içeriği dönüştürme (alma) === :'''''{{ll|Manual:Importing external content}}''' sayfasına bakın'' Diğer wiki motorlarından veri almak için bazı komut dosyaları bulunur. == On-wiki özelleştirmeleri == :'''''{{ll|Manual:Page customizations}}''' sayfasına bakın'' MediaWiki'nin görünümü ve mesajlaşmasının çoğu, yöneticilerin normal wiki sayfaları gibi düzenleyebileceği mesajlarla belirlenir. * Boş yardım sayfalarını ele alan kısa bir genel bakış için {{ll|Project:PD help/Copying}} sayfasına bakın. === Kenar çubuğunu değiştirme === :'''''{{ll|Manual:Sidebar}}''' sayfasına bakın'' === Etiket satırını değiştirme === :'''''{{ll|Manual:Tagline (Site Subtitle)}}''' sayfasına bakın'' === Birkaç sayfaya dahil edilecek standart metinleri ayarlama === :'''''{{ll|Help:Templates}}''' sayfasına bakın'' [[Category:MediaWiki administration{{#translation:}}| ]] n1xiakfkt3u6w2ygwimjlxc84fxm5cm HHVM/hu 0 987594 5387451 5240447 2022-07-28T22:32:07Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = A MediaWiki HHVM (HipHop Virtual Machine) támogatása és a Wikimédia-oldalakon való bevezetése | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/HHVM/About|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref> After discussion<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See {{phabricator|T176209}} and {{phabricator|T192166}}.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">'''[[w:HHVM|HHVM]]''' is a PHP interpreter tool (concretely a virtual machine that compiles PHP bytecode to native instructions at runtime) that was deployed on Wikimedia servers in 2014, decreasing the loading time for: any page you view while logged in, and for saving pages that you've edited whether you are logged in or not.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Roadmap == </div> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM is a new way for websites to run [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (written in [[w:PHP|PHP]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT).</span> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This page is about Wikimedia-sponsored work on HipHop support in MediaWiki, and its deployment to Wikimedia production wikis. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Historically, the HipHop compiler was a project by Facebook which involved compiling PHP code into C++ for purposes of speeding up the language. Facebook has since abandoned this project, and now their development efforts are focused on HHVM itself instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is the general plan for deploying HHVM to the production cluster in 2014: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Deployment to Beta Cluster (currently ongoing work, in parallel with other work) {{done}} * Week of July 21: deployment to a few job runners in production {{done}} * Deploy to test.wikipedia.org application server {{done}} * Deploy Varnish module allowing partial deployment to a fraction of application servers{{Done}} * Limited deployment to small number of application servers {{Done}} * Ramp up deployment to more application servers until most servers use HHVM{{done}} * Deploy to remainder of services{{done}} </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === HHVM work === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Rationale == </div> <span lang="en" dir="ltr" class="mw-content-ltr">It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> in a solution: [http://hhvm.com HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're quite confident that this will result in big performance improvements on our sites as well.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == What does HipHop do for our end users? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is written in PHP, a language that is [[w:Interpreter (computing)|interpreted]] at run-time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These caches only serve users that are not logged in.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does our development work on HipHop affect MediaWiki developers? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will be on a totally opt-in basis which can be disabled at any time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Setting up HHVM in {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presenting at @Scale about migrating to HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM in production: what that means for Wikimedia developers] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == References and footnotes == </div> <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] qeriaww0k73w9v8399xd995kvxda9wc Translations:Manual:Pywikibot/category redirect.py/5/en 1198 994160 5387857 4821166 2022-07-29T10:22:51Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki Only loops over [[$1|Category:Wikipedia non-empty soft redirected categories]] and moves all images, pages and categories in redirect categories to the target category rr5r58fnat6o5vqdwpcd1diau6rati7 Manual:Pywikibot/category redirect.py/en 100 994162 5387859 4821168 2022-07-29T10:22:52Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Git/pywikibot}} {{Pywikibot|scripts}} '''category_redirect.py''' is a {{ll|Manual:Pywikibot|Pywikibot}} script used to move pages out of redirected categories. The bot will look for categories that are marked with a category redirect template, take the first parameter of the template as the target of the redirect, and move all pages and subcategories of the category there. It also changes hard redirects into soft redirects, and fixes double redirects. A log is written under &lt;userpage>/category_redirect_log. Only category pages that haven't been edited for a certain cooldown period (7 days by default) are taken into account. The following parameters are supported: {{Pywikibot command table beginning}} {{option|delay:#|2=Set an amount of days. If the category is edited more recenty than given days, ignore it. Default is 7}} {{option|tiny|2=Only loops over [[:d:Q8099903|Category:Wikipedia non-empty soft redirected categories]] and moves all images, pages and categories in redirect categories to the target category}} {{Pywikibot command table end}} == Usage == <syntaxhighlight lang=shell-session> $ python pwb.py category_redirect [options] </syntaxhighlight> {{Manual:Pywikibot/Global Options}} [[Category:Pywikibot scripts{{#translation:}}|category_redirect]] ipympjzpz1euf1tx5b1fx3r4z2vdsau Reading/Web/Desktop Improvements/es 0 999604 5387378 5372056 2022-07-28T22:12:49Z Zapipedia (WMF) 17560702 wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} {{Wikimedia engineering project information | name = Mejoras a la IU de escritorio | description = Una serie de nuevas características y reordenamientos en la piel Vector | logo = Annotated Wikipedia Vector interface (logged-out).png | start = 2019-05 | end = 2022-08 | group = {{void|1=[[Special:MyLanguage/Reading/Web|Lectura/Web]]}} | lead = [[User:OVasileva (WMF)|Olga Vasileva]] (Propietaria de Producto - Product Owner) | team = [[Special:MyLanguage/Reading/Web|Lectura/Web]] | Phabricator = desktop-improvements | updates = [[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates|Subpágina de actualizaciones]] | progress = | previous = | next = | projectpage = | backlog = [[phab:project/view/67/|Mesa de trabajo en Phabricator]] | display = }} Han pasado 12 años desde que se implementó la piel predeterminada actual de Wikimedia ([[Special:MyLanguage/Skin:Vector|Vector]]). En la última década, la interfaz se ha enriquecido con [[Special:MyLanguage/Manual:Extensions|extensiones]], [[Special:MyLanguage/Extension:Gadgets|gadgets]] y [[Special:MyLanguage/Manual:Interface/JavaScript#Personal scripts|scripts de usuario]]. La mayoría de estas mejoras no estaban coordinadas visualmente ni entre wikis. Al mismo tiempo, el diseño de la web, así como las expectativas de los lectores y editores, han evolucionado. Creemos que es hora de tomar algunas de estas ideas y llevarlas a la experiencia por defecto de todos los usuarios, en todas las wikis, de una manera organizada y coherente. {{void|1= Durante los próximos dos trimestres, el [[Special:MyLanguage/Reading/Web/Team|equipo de lectores web]] investigará y desarrollará mejoras en la experiencia de escritorio basándose en la investigación y las herramientas existentes. }} Nuestros objetivos son hacer que los wikis de Wikimedia sean más acogedores y aumentar la utilidad entre los lectores y mantener la utilidad para los editores existentes. Medimos el aumento de la confianza y el sentimiento positivo hacia nuestros sitios, y la utilidad de nuestros sitios (el uso de acciones comunes como la búsqueda y el cambio de idioma). Actualmente, en la mayoría de las wikis, sólo los usuarios que han iniciado sesión pueden optar por hacerlo individualmente. En algunas wikis seleccionadas, nuestros cambios se implementan para todos por defecto, y los usuarios conectados pueden optar por no participar. Esperamos aumentar el conjunto de wikis que van implementando las Mejoras de Escritorio de manera gradual, hasta que estén activas por defecto en todas las wikis en los próximos meses de 2022. == Actualizaciones == {{main|Reading/Web/Desktop Improvements/Updates}} {{:Reading/Web/Desktop Improvements/Updates}} == ¿Cuál es nuestro objetivo? == === Imagina un armario === <gallery mode="nolines" widths="300" heights="180"> File:CLOTHES HANGING OVER BED JAPANESE STYLE.jpg|Nos gustaría reorganizar gradualmente esto... File:Wilmslow, United Kingdom (Unsplash).jpg|...en esto :) </gallery> === Actualmente, la interfaz... === '''...no cumple con las expectativas. ...está desordenada y no es intuitiva. ...no destaca el aspecto de la comunidad. ...no es consistente con la versión móvil.''' # La interfaz de escritorio no cumple con las expectativas creadas por las plataformas web modernas. Se siente desorientada y desconectada. Los enlaces de navegación e interfaz están organizados al azar. # Hay un desorden que distrae a los usuarios de concentrarse en lo que vinieron a buscar. Es un desafío para los lectores concentrarse en el contenido. No es posible que cambien de idioma de manera intuitiva, busquen contenido o ajusten la configuración de lectura. Los nuevos editores no pueden usar su intuición para configurar su cuenta, abrir el editor o aprender a usar páginas que no son artículos con fines de moderación. # Un porcentaje muy pequeño de lectores comprende cómo funcionan los wikis de Wikimedia. Muchos lectores no saben que el contenido que están leyendo está escrito por voluntarios y se actualiza con frecuencia, o que potencialmente ellos también pueden contribuir. # La gran diferencia de experiencias entre nuestra interfaz de escritorio, nuestras aplicaciones y la web móvil dificulta que los lectores se conecten con nuestros productos. Hay una falta de unidad en el concepto de los sitios de Wikimedia. == Cómo se realizan los cambios == === Principios === '''No tocamos el contenido. No eliminamos ninguna funcionalidad. No tocamos otras pieles que no sean Vector. Nos hemos inspirado en los accesorios existentes. No realizamos cambios importantes en pasos individuales.''' # Estamos trabajando solo en la interfaz. No se trabajará en términos de plantillas de estilo, la estructura del contenido de página, soporte de mapas o plantillas interwiki. # Aunque nuestros cambios se notan fácilmente, estamos adoptando un enfoque evolutivo y queremos que el sitio siga siendo familiar para los lectores y editores. Cada característica se discute, desarrolla e implementa por separado. # Los elementos de la interfaz pueden moverse, pero todos los elementos de navegación y otras funciones disponibles actualmente de forma predeterminada permanecerán. # Las pieles que no sean Vector están fuera del alcance de nuestros ajustes. Hemos congelado Vector a la versión heredada de Vector y comenzamos a implementar nuestras funciones como partes del nuevo Vector predeterminado. # Hemos analizado muchas wikis y hemos detectado muchos gadgets útiles. Algunos de ellos definitivamente merecen aparecer y ser parte de la experiencia predeterminada. # Tanto antes del desarrollo como después de la implementación, recopilamos datos (a través de [[d:Q1810071|pruebas A/B]], rondas de comentarios de prototipos, etc.). En caso de resultados significativamente negativos, revertiremos nuestros cambios. # Nuestra intención es probar nuestras mejoras en colaboración con un conjunto diverso de wikivoluntarios de ser ''primeros usuarios'', tanto Wikipedias como proyectos hermanos. {{void|1= # Las primeras tres funciones (la [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|nueva cabecera]], la [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|barra lateral plegable]] y la [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|limitación del ancho del contenido]]) se implementaron en julio de 2020. # Nuestra segunda gran funcionalidad, un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Search|widget de búsqueda]] mejorado, se implementó en las wikis de adopción temprana en febrero de 2021. }} {| class="plainlinks" style="text-align:center;" |-valign="top" ! style="padding:.5em; margin:.5em;" |en la mayoría de las wikis ! style="padding:.5em; margin:.5em;"|wikis de adopción temprana |- | style="padding:.5em; margin:.5em;" |editores o lectores<br />no ven nuestros cambios de forma predeterminada | style="padding:.5em; margin:.5em;"|editores y lectores<br />ven nuestros cambios por defecto |- | style="padding:.5em; margin:.5em;" |solo los editores pueden optar por participar<br/>(desde las preferencias del usuario, marcando '''{{int|skinname-vector-2022}}''' en la pestaña [[Special:Preferences#mw-prefsection-rendering|{{int|prefs-rendering}}]]) | style="padding:.5em; margin:.5em;"|solo editores pueden optar por no participar<br/>(usando '''[https://www.mediawiki.org/w/index.php?title=Special:Preferences&wprov=vctw1#mw-prefsection-rendering-skin-skin-prefs {{int|vector-opt-out}}]''' en la barra lateral, o directamente desde las preferencias de los usuarios) |} {{anchor|Timeline}} === Plan de implementación y cronograma === <span style="background-color:#fc3;">Nos gustaría que nuestras mejoras fueran la opción por defecto en todas las wikis en agosto/septiembre de 2022, tras la discusión con las comunidades.</span> <div style="margin:auto; text-align: center;">{{Reading/Web/Desktop Improvements/Timeline}}</div> {{anchor|test-wikis}}{{anchor|List of early adopter wikis (test wikis)}} {{hidden |1=Lista de wikis de primeros usuarios (wikis de prueba) |headercss=background-color:#eaf3ff; |2= El primer grupo de wikis (marcado como ◇ en la línea de tiempo anterior): * [[:eu:|{{int|project-localized-name-euwiki}}]] * [[:fr:|{{int|project-localized-name-frwiki}}]] * [[wikt:fr:|{{int|project-localized-name-frwiktionary}}]] * [[:he:|{{int|project-localized-name-hewiki}}]] * [[:fa:|{{int|project-localized-name-fawiki}}]] * [[v:pt:|{{int|project-localized-name-ptwikiversity}}]] * [https://office.wikimedia.org/ Office Wiki] El segundo grupo de wikis (marcado como ◇◇ en la línea de tiempo anterior): * [[:bn:|{{int|project-localized-name-bnwiki}}]] * [[:voy:de:|{{int|project-localized-name-dewikivoyage}}]] * [[:ko:|{{int|project-localized-name-kowiki}}]] * [[:pt:|{{int|project-localized-name-ptwiki}}]] * [[:sr:|{{int|project-localized-name-srwiki}}]] * [[:tr:|{{int|project-localized-name-trwiki}}]] * [[:vec:|{{int|project-localized-name-vecwiki}}]] * [[:incubator:|{{int|project-localized-name-incubatorwiki}}]] Tercer grupo de wikis (marcado como ◇◇◇ en la línea de tiempo anterior): * [[:ary:|{{int|project-localized-name-arywiki}}]] * [[q:fr:|{{int|project-localized-name-frwikiquote}}]] * [[:id:|{{int|project-localized-name-idwiki}}]] * [[n:pt:|{{int|project-localized-name-ptwikinews}}]] * [[n:pl:|{{int|project-localized-name-plwikinews}}]] * [[:th:|{{int|project-localized-name-thwiki}}]] * [[:vi:|{{int|project-localized-name-viwiki}}]] * [[b:vi:|{{int|project-localized-name-viwikibooks}}]] * MediaWiki.org (esta wiki) * [[:foundation:|Wiki de la Fundación Wikimedia]] * [https://collab.wikimedia.org/ Collab wiki] * [[:strategy:|Strategy wiki]] Cuarto grupo de wikis (marcado como ◇◇◇◇ en la línea de tiempo anterior): * [[s:ar:|{{int|project-localized-name-arwikisource}}]] * [[:ca:|{{int|project-localized-name-cawiki}}]] * [[s:pl:|{{int|project-localized-name-plwikisource}}]] * [[n:zh:|{{int|project-localized-name-zhwikinews}}]] }} {{anchor|participate}}{{anchor|contact}} == Participación & Contacto == {{void|1= '''¡[[Special:Preferences#mw-prefsection-rendering|Prueba nuestras funciones individualmente]], [[Talk:Reading/Web/Desktop Improvements|comparte tus comentarios]], y [[Special:MyLanguage/Reading/Web/Desktop Improvements/Participate#Entire communities|únete a nuestras wikis pioneras (o de adopción temprana)]]!''' }} * {{clickable button 2|Special:Newsletter/28/subscribe|Suscríbete a la newsletter}} * '''[[Special:Preferences#mw-prefsection-rendering|Prueba individualmente]]''': en Preferencias, control la opción ''{{int|skinname-vector-2022}}''. También puede habilitar nuestros cambios utilizando las [[Special:GlobalPreferences#mw-prefsection-rendering|Preferencias globales]]. * '''[[1$|Únete a las reuniones online con nosotros]]''': hasta finales de julio, organizaremos reuniones cada 2-3 semanas. Fechas tentativas: {{date||6|13}}, $2, {{date||6|28}}, {{date||7|12}}, {{date||7|26}}. * '''Promover''': informar a tu comunidad. Comparte nuestras [[$actualizaciones|actualizaciones]] y [[$posturas|post del blog]]. * '''Informe de errores''': para informar de un error, crear una tarea en Phabricator y agregar {{Phabricator inline tag|desktop-improvements}} como identificador del proyecto. * '''Early adoption''': Esperamos aumentar gradualmente el conjunto de wikis de adopción temprana. ¿Crees que tu comunidad podría estar interesada en tener nuestra interfaz por defecto? Entonces, contáctanos. <gallery mode="packed" style="float:left;"> File:Wikispotkanie-warszawa-2021-07-03-rd-26.jpg|[[User:SGrabarczuk (WMF)|Szymon Grabarczuk]]<br/>Especialista en Relaciones Comunitarias<br/>sgrabarczuk{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Mehran (WMF)|Mehran]]<br>Embajador persa<br/>mehran-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Patafisik (WMF)|Patafisik]]<br>Embajador francés<br/>patafisik-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Bluetpp (WMF)|Phuong Pham]]<br>Embajador vietnamita<br/>ppham-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Zapipedia (WMF)|Zapipedia]]<br>Embajadora Wikipedia en español<br/>izapico-ctr{{@}}wikimedia.org </gallery> {{clear}} * '''Traducir''': ayúdanos a traducir las páginas relacionadas: {{hidden|1=Traducciones prioritarias |headercss=background-color:#eaf3ff; |2= TOP3 # {{ll|Reading/Web/Desktop Improvements}} # {{ll|Reading/Web/Desktop Improvements/Frequently asked questions}} # {{ll|Reading/Web/Desktop Improvements/Features}} Otras traducciones prioritarias # [[Template:Reading/Web/Desktop Improvements/Office hours announcement]] # [[Template:Reading/Web/Desktop Improvements/Talk page intro]] # [[Template:Reading/Web/Desktop Improvements/Features/Navigation]] # [[Template:Reading/Web/Desktop Improvements/Header]] # {{ll|Reading/Web/Desktop Improvements/Updates}} # {{ll|Reading/Web/Desktop Improvements/Repository#posts}} [https://mediawiki.org/w/index.php?title=Special:Translate&group=agg-Desktop_Improvements&action=page&filter= Enlace directo a todas las traducciones] }} == Qué características se agregarán == {{main|Reading/Web/Desktop Improvements/Features}} No hemos creado una especificación de producto completa y detallada. Cada función se crea e implementa '''por separado''', con el tiempo. Las funciones que se han creado todavía se están ajustando y mejorando. Nuestras decisiones se basan en los comentarios de la comunidad, las pruebas de los usuarios y los datos extraídos de la API. <gallery mode="slideshow" showthumbnails="" caption="Visualización de versiones implementadas y conceptos iniciales"> Header Logo reconfiguration - commons pt - GIF.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|Cabecera 1: Reconfiguración del logotipo]] File:Collapsible sidebar - wikidata fr - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|Barra lateral plegable]] File:Limit content width - wikiversity pt - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|Limitación de ancho del contenido]] File:Sketch of search results with images and descriptions for Desktop improvements project.jpg|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Search|Búsqueda: movimiento de accesorios y otras mejoras]] File:04 - DIP - Language links in article header.png|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|Cambio de idioma 1: Enlaces de idioma en la barra de título del artículo]] File:Consolidated user tools prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/User menu|Menú del Usuario]] File:Search prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|Cabecera 2: Cabeceras de artículo y sitio fijo]] File:Table of contents prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|Índice de contenidos]] File:Article tools prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Page tools|Herramientas de artículo]] </gallery> rvez1rjzw0jdj7vniaelyiy9ynvunv1 5387440 5387378 2022-07-28T22:19:06Z Zapipedia (WMF) 17560702 wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} {{Wikimedia engineering project information | name = Mejoras a la IU de escritorio | description = Una serie de nuevas características y reordenamientos en la piel Vector | logo = Annotated Wikipedia Vector interface (logged-out).png | start = 2019-05 | end = 2022-08 | group = {{void|1=[[Special:MyLanguage/Reading/Web|Lectura/Web]]}} | lead = [[User:OVasileva (WMF)|Olga Vasileva]] (Propietaria de Producto - Product Owner) | team = [[Special:MyLanguage/Reading/Web|Lectura/Web]] | Phabricator = desktop-improvements | updates = [[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates|Subpágina de actualizaciones]] | progress = | previous = | next = | projectpage = | backlog = [[phab:project/view/67/|Mesa de trabajo en Phabricator]] | display = }} Han pasado 12 años desde que se implementó la skin predeterminada actual de Wikimedia ([[Special:MyLanguage/Skin:Vector|Vector]]). En la última década, la interfaz se ha enriquecido con [[Special:MyLanguage/Manual:Extensions|extensiones]], [[Special:MyLanguage/Extension:Gadgets|gadgets]] y [[Special:MyLanguage/Manual:Interface/JavaScript#Personal scripts|scripts de usuario]]. La mayoría de estas mejoras no estaban coordinadas visualmente ni entre wikis. Al mismo tiempo, el diseño de la web, así como las expectativas de los lectores y editores, han evolucionado. Creemos que es hora de tomar algunas de estas ideas y llevarlas a la experiencia por defecto de todos los usuarios, en todas las wikis, de una manera organizada y coherente. {{void|1= Durante los próximos dos trimestres, el [[Special:MyLanguage/Reading/Web/Team|equipo de lectores web]] investigará y desarrollará mejoras en la experiencia de escritorio basándose en la investigación y las herramientas existentes. }} Nuestros objetivos son hacer que los wikis de Wikimedia sean más acogedores y aumentar la utilidad entre los lectores y mantener la utilidad para los editores existentes. Medimos el aumento de la confianza y el sentimiento positivo hacia nuestros sitios, y la utilidad de nuestros sitios (el uso de acciones comunes como la búsqueda y el cambio de idioma). Actualmente, en la mayoría de las wikis, sólo los usuarios que han iniciado sesión pueden optar por hacerlo individualmente. En algunas wikis seleccionadas, nuestros cambios se implementan para todos por defecto, y los usuarios conectados pueden optar por no participar. Esperamos aumentar el conjunto de wikis que van implementando las Mejoras de Escritorio de manera gradual, hasta que estén activas por defecto en todas las wikis en los próximos meses de 2022. == Actualizaciones == {{main|Reading/Web/Desktop Improvements/Updates}} {{:Reading/Web/Desktop Improvements/Updates}} == ¿Cuál es nuestro objetivo? == === Imagina un armario === <gallery mode="nolines" widths="300" heights="180"> File:CLOTHES HANGING OVER BED JAPANESE STYLE.jpg|Nos gustaría reorganizar gradualmente esto... File:Wilmslow, United Kingdom (Unsplash).jpg|...en esto :) </gallery> === Actualmente, la interfaz... === '''...no cumple con las expectativas. ...está desordenada y no es intuitiva. ...no destaca el aspecto de la comunidad. ...no es consistente con la versión móvil.''' # La interfaz de escritorio no cumple con las expectativas creadas por las plataformas web modernas. Se siente desorientada y desconectada. Los enlaces de navegación e interfaz están organizados al azar. # Hay un desorden que distrae a los usuarios de concentrarse en lo que vinieron a buscar. Es un desafío para los lectores concentrarse en el contenido. No es posible que cambien de idioma de manera intuitiva, busquen contenido o ajusten la configuración de lectura. Los nuevos editores no pueden usar su intuición para configurar su cuenta, abrir el editor o aprender a usar páginas que no son artículos con fines de moderación. # Un porcentaje muy pequeño de lectores comprende cómo funcionan los wikis de Wikimedia. Muchos lectores no saben que el contenido que están leyendo está escrito por voluntarios y se actualiza con frecuencia, o que potencialmente ellos también pueden contribuir. # La gran diferencia de experiencias entre nuestra interfaz de escritorio, nuestras aplicaciones y la web móvil dificulta que los lectores se conecten con nuestros productos. Hay una falta de unidad en el concepto de los sitios de Wikimedia. == Cómo se realizan los cambios == === Principios === '''No tocamos el contenido. No eliminamos ninguna funcionalidad. No tocamos otras pieles que no sean Vector. Nos hemos inspirado en los accesorios existentes. No realizamos cambios importantes en pasos individuales.''' # Estamos trabajando solo en la interfaz. No se trabajará en términos de plantillas de estilo, la estructura del contenido de página, soporte de mapas o plantillas interwiki. # Aunque nuestros cambios se notan fácilmente, estamos adoptando un enfoque evolutivo y queremos que el sitio siga siendo familiar para los lectores y editores. Cada característica se discute, desarrolla e implementa por separado. # Los elementos de la interfaz pueden moverse, pero todos los elementos de navegación y otras funciones disponibles actualmente de forma predeterminada permanecerán. # Las pieles que no sean Vector están fuera del alcance de nuestros ajustes. Hemos congelado Vector a la versión heredada de Vector y comenzamos a implementar nuestras funciones como partes del nuevo Vector predeterminado. # Hemos analizado muchas wikis y hemos detectado muchos gadgets útiles. Algunos de ellos definitivamente merecen aparecer y ser parte de la experiencia predeterminada. # Tanto antes del desarrollo como después de la implementación, recopilamos datos (a través de [[d:Q1810071|pruebas A/B]], rondas de comentarios de prototipos, etc.). En caso de resultados significativamente negativos, revertiremos nuestros cambios. # Nuestra intención es probar nuestras mejoras en colaboración con un conjunto diverso de wikivoluntarios de ser ''primeros usuarios'', tanto Wikipedias como proyectos hermanos. {{void|1= # Las primeras tres funciones (la [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|nueva cabecera]], la [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|barra lateral plegable]] y la [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|limitación del ancho del contenido]]) se implementaron en julio de 2020. # Nuestra segunda gran funcionalidad, un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Search|widget de búsqueda]] mejorado, se implementó en las wikis de adopción temprana en febrero de 2021. }} {| class="plainlinks" style="text-align:center;" |-valign="top" ! style="padding:.5em; margin:.5em;" |en la mayoría de las wikis ! style="padding:.5em; margin:.5em;"|wikis de adopción temprana |- | style="padding:.5em; margin:.5em;" |editores o lectores<br />no ven nuestros cambios de forma predeterminada | style="padding:.5em; margin:.5em;"|editores y lectores<br />ven nuestros cambios por defecto |- | style="padding:.5em; margin:.5em;" |solo los editores pueden optar por participar<br/>(desde las preferencias del usuario, marcando '''{{int|skinname-vector-2022}}''' en la pestaña [[Special:Preferences#mw-prefsection-rendering|{{int|prefs-rendering}}]]) | style="padding:.5em; margin:.5em;"|solo editores pueden optar por no participar<br/>(usando '''[https://www.mediawiki.org/w/index.php?title=Special:Preferences&wprov=vctw1#mw-prefsection-rendering-skin-skin-prefs {{int|vector-opt-out}}]''' en la barra lateral, o directamente desde las preferencias de los usuarios) |} {{anchor|Timeline}} === Plan de implementación y cronograma === <span style="background-color:#fc3;">Nos gustaría que nuestras mejoras fueran la opción por defecto en todas las wikis en agosto/septiembre de 2022, tras la discusión con las comunidades.</span> <div style="margin:auto; text-align: center;">{{Reading/Web/Desktop Improvements/Timeline}}</div> {{anchor|test-wikis}}{{anchor|List of early adopter wikis (test wikis)}} {{hidden |1=Lista de wikis de primeros usuarios (wikis de prueba) |headercss=background-color:#eaf3ff; |2= El primer grupo de wikis (marcado como ◇ en la línea de tiempo anterior): * [[:eu:|{{int|project-localized-name-euwiki}}]] * [[:fr:|{{int|project-localized-name-frwiki}}]] * [[wikt:fr:|{{int|project-localized-name-frwiktionary}}]] * [[:he:|{{int|project-localized-name-hewiki}}]] * [[:fa:|{{int|project-localized-name-fawiki}}]] * [[v:pt:|{{int|project-localized-name-ptwikiversity}}]] * [https://office.wikimedia.org/ Office Wiki] El segundo grupo de wikis (marcado como ◇◇ en la línea de tiempo anterior): * [[:bn:|{{int|project-localized-name-bnwiki}}]] * [[:voy:de:|{{int|project-localized-name-dewikivoyage}}]] * [[:ko:|{{int|project-localized-name-kowiki}}]] * [[:pt:|{{int|project-localized-name-ptwiki}}]] * [[:sr:|{{int|project-localized-name-srwiki}}]] * [[:tr:|{{int|project-localized-name-trwiki}}]] * [[:vec:|{{int|project-localized-name-vecwiki}}]] * [[:incubator:|{{int|project-localized-name-incubatorwiki}}]] Tercer grupo de wikis (marcado como ◇◇◇ en la línea de tiempo anterior): * [[:ary:|{{int|project-localized-name-arywiki}}]] * [[q:fr:|{{int|project-localized-name-frwikiquote}}]] * [[:id:|{{int|project-localized-name-idwiki}}]] * [[n:pt:|{{int|project-localized-name-ptwikinews}}]] * [[n:pl:|{{int|project-localized-name-plwikinews}}]] * [[:th:|{{int|project-localized-name-thwiki}}]] * [[:vi:|{{int|project-localized-name-viwiki}}]] * [[b:vi:|{{int|project-localized-name-viwikibooks}}]] * MediaWiki.org (esta wiki) * [[:foundation:|Wiki de la Fundación Wikimedia]] * [https://collab.wikimedia.org/ Collab wiki] * [[:strategy:|Strategy wiki]] Cuarto grupo de wikis (marcado como ◇◇◇◇ en la línea de tiempo anterior): * [[s:ar:|{{int|project-localized-name-arwikisource}}]] * [[:ca:|{{int|project-localized-name-cawiki}}]] * [[s:pl:|{{int|project-localized-name-plwikisource}}]] * [[n:zh:|{{int|project-localized-name-zhwikinews}}]] }} {{anchor|participate}}{{anchor|contact}} == Participación & Contacto == {{void|1= '''¡[[Special:Preferences#mw-prefsection-rendering|Prueba nuestras funciones individualmente]], [[Talk:Reading/Web/Desktop Improvements|comparte tus comentarios]], y [[Special:MyLanguage/Reading/Web/Desktop Improvements/Participate#Entire communities|únete a nuestras wikis pioneras (o de adopción temprana)]]!''' }} * {{clickable button 2|Special:Newsletter/28/subscribe|Suscríbete a la newsletter}} * '''[[Special:Preferences#mw-prefsection-rendering|Prueba individualmente]]''': en Preferencias, control la opción ''{{int|skinname-vector-2022}}''. También puede habilitar nuestros cambios utilizando las [[Special:GlobalPreferences#mw-prefsection-rendering|Preferencias globales]]. * '''[[1$|Únete a las reuniones online con nosotros]]''': hasta finales de julio, organizaremos reuniones cada 2-3 semanas. Fechas tentativas: {{date||6|13}}, $2, {{date||6|28}}, {{date||7|12}}, {{date||7|26}}. * '''Promover''': informar a tu comunidad. Comparte nuestras [[$actualizaciones|actualizaciones]] y [[$posturas|post del blog]]. * '''Informe de errores''': para informar de un error, crear una tarea en Phabricator y agregar {{Phabricator inline tag|desktop-improvements}} como identificador del proyecto. * '''Early adoption''': Esperamos aumentar gradualmente el conjunto de wikis de adopción temprana. ¿Crees que tu comunidad podría estar interesada en tener nuestra interfaz por defecto? Entonces, contáctanos. <gallery mode="packed" style="float:left;"> File:Wikispotkanie-warszawa-2021-07-03-rd-26.jpg|[[User:SGrabarczuk (WMF)|Szymon Grabarczuk]]<br/>Especialista en Relaciones Comunitarias<br/>sgrabarczuk{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Mehran (WMF)|Mehran]]<br>Embajador persa<br/>mehran-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Patafisik (WMF)|Patafisik]]<br>Embajador francés<br/>patafisik-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Bluetpp (WMF)|Phuong Pham]]<br>Embajador vietnamita<br/>ppham-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Zapipedia (WMF)|Zapipedia]]<br>Embajadora Wikipedia en español<br/>izapico-ctr{{@}}wikimedia.org </gallery> {{clear}} * '''Traducir''': ayúdanos a traducir las páginas relacionadas: {{hidden|1=Traducciones prioritarias |headercss=background-color:#eaf3ff; |2= TOP3 # {{ll|Reading/Web/Desktop Improvements}} # {{ll|Reading/Web/Desktop Improvements/Frequently asked questions}} # {{ll|Reading/Web/Desktop Improvements/Features}} Otras traducciones prioritarias # [[Template:Reading/Web/Desktop Improvements/Office hours announcement]] # [[Template:Reading/Web/Desktop Improvements/Talk page intro]] # [[Template:Reading/Web/Desktop Improvements/Features/Navigation]] # [[Template:Reading/Web/Desktop Improvements/Header]] # {{ll|Reading/Web/Desktop Improvements/Updates}} # {{ll|Reading/Web/Desktop Improvements/Repository#posts}} [https://mediawiki.org/w/index.php?title=Special:Translate&group=agg-Desktop_Improvements&action=page&filter= Enlace directo a todas las traducciones] }} == Qué características se agregarán == {{main|Reading/Web/Desktop Improvements/Features}} No hemos creado una especificación de producto completa y detallada. Cada función se crea e implementa '''por separado''', con el tiempo. Las funciones que se han creado todavía se están ajustando y mejorando. Nuestras decisiones se basan en los comentarios de la comunidad, las pruebas de los usuarios y los datos extraídos de la API. <gallery mode="slideshow" showthumbnails="" caption="Visualización de versiones implementadas y conceptos iniciales"> Header Logo reconfiguration - commons pt - GIF.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|Cabecera 1: Reconfiguración del logotipo]] File:Collapsible sidebar - wikidata fr - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|Barra lateral plegable]] File:Limit content width - wikiversity pt - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|Limitación de ancho del contenido]] File:Sketch of search results with images and descriptions for Desktop improvements project.jpg|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Search|Búsqueda: movimiento de accesorios y otras mejoras]] File:04 - DIP - Language links in article header.png|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|Cambio de idioma 1: Enlaces de idioma en la barra de título del artículo]] File:Consolidated user tools prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/User menu|Menú del Usuario]] File:Search prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|Cabecera 2: Cabeceras de artículo y sitio fijo]] File:Table of contents prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|Índice de contenidos]] File:Article tools prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Page tools|Herramientas de artículo]] </gallery> 6kz3jm4vvqwue8i69gosov0yp4651pf Reading/Web/Desktop Improvements/zh 0 1002840 5387653 5371315 2022-07-29T04:22:56Z Chubit 17346826 wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} {{Wikimedia engineering project information | name = 桌面版改进 | description = Vector外观的一系列新功能和重新排列 | logo = Annotated Wikipedia Vector interface (logged-out).png | start = 2019-05 | end = 2022-08 | group = {{void|1=[[Special:MyLanguage/Reading/Web|阅读/网页]]}} | lead = [[User:OVasileva (WMF)|Olga Vasileva]](产品负责人) | team = [[Special:MyLanguage/Reading/Web|阅读/网页]] | Phabricator = desktop-improvements | updates = [[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates|更新子页面]] | progress = | previous = | next = | projectpage = | backlog = [[phab:project/view/67/|Phabricator任务面板]] | display = }} 当前默认的维基皮肤([[Special:MyLanguage/Skin:Vector|Vector]])已经使用了12年。 過去十年間,透過[[Special:MyLanguage/Manual:Extensions|擴充功能]]、[[Special:MyLanguage/Extension:Gadgets|小工具]]及使用者自訂程式,其介面愈來愈豐富。 這些大部分在視覺上仍欠協調,且非跨 wiki 可用。 同時,網站設計和讀者、編者的期待也逐漸改變。 我們認為,是時候採用這些想法,並讓它們成為所有 wiki 上、所有使用者有組織且一致的預設體驗, {{void|1= 接下来的几个季度里,[[Special:MyLanguage/Reading/Web/Team|读者网页组]]将基于研究和现有工具,开发对桌面版维基体验的改进。 }} 我们的目标是使维基媒体的维基更受欢迎,并增加对读者而言的实用性,维护对现有编辑者而言的实用性。我们会测量对维基的信任度、积极情绪的变化,以及维基的使用程度(常见操作,例如搜索和语言切换)。 目前在大多数维基上,只有登录用户才能选择使用改进皮肤。在特定的维基上,默认情况下所有用户都会使用改进皮肤,登录用户可以选择退出。我们希望逐渐增加“早期采用者”维基的集合,直到2022年7月所有维基都使用改进皮肤。 == 更新 == {{main|Reading/Web/Desktop Improvements/Updates}} {{:Reading/Web/Desktop Improvements/Updates}} == 我们的目标是什么? == === 想象一个衣柜 === <gallery mode="nolines" widths="300" heights="180"> File:CLOTHES HANGING OVER BED JAPANESE STYLE.jpg|我们想逐步重新排放这个… File:Wilmslow, United Kingdom (Unsplash).jpg|…变成这样:) </gallery> === 目前,界面… === '''…与期望不符。 …混乱而又不直观。 …不强调社群方面。 …与移动端不一致。''' # 桌面界面与现代网络平台的期望不符。感觉迷失了方向,脱节了。导航和界面链接随意地组织着。 # 混乱的网页使用户无法专注于他们查找的内容。对于读者而言,专注看内容具有挑战性,他们无法直观地切换语言,搜索内容或调整阅读设置。新编辑者无法凭直觉来设置帐户,打开编辑器或学习如何使用非文章页面。 # 只有极少数的读者了解维基媒体计划的功能。许多读者并不知道他们正在阅读的内容是由志愿者编写并经常更新的,也不知道他们也能做出贡献。 # 我们的桌面版网站,移动版网站和应用程序之间的体验差异很大,这使读者很难连接我们的产品。 维基媒体的网站概念缺乏统一性。 == 更改将如何进行 == === 原则 === '''我们不会影响到内容。 我们不会移除任何功能。 除了Vector,我们不会修改其它皮肤。 我们受到现有小工具的启发。 我们不会一蹴而就地进行重大更改。''' # 我们只在界面上做更改。在样式模板、页面内容结构、映射支持或跨维基模板方面不做任何更改。 # 虽然我们的变化很容易被注意到,但我们正在采取一种循序渐进的方法,并希望网站能继续让读者和编者感到熟悉。每个功能分别被讨论、开发和部署。 # 界面的元素可能会移动位置,但是所有的导航项和其他默认可用的功能将保持不变。 # Vector以外的皮肤不在我们的调整范围内。我们已经将Vector冻结为旧版Vector,并开始将我们的功能作为新的默认Vector的一部分部署。 # 我们分析了许多维基,并发现了许多有用的小工具。其中一些绝对值得出现并成为默认体验的一部分。 # 在开发前和部署后,我们都会收集数据(通过[[d:Q1810071|A/B测试]]、原型反馈回合等)。如果出现非常负面的结果,我们将回退更改。 # 我们打算与各种自愿参与的“早期采用者”维基(维基百科和姊妹项目)合作测试我们的改进。 {{void|1= # 首三个功能([[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|新头部]]、[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|可收起的侧边栏]]及[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|有限制的宽度]])已经在2020年7月部署。 # 我们的第二个大功能,一个改进的[[Reading/Web/Desktop Improvements/Features/Search/zh|搜索小工具]],将于2021年2月部署到早期采用者维基上。 }} {| class="plainlinks" style="text-align:center;" |-valign="top" ! style="padding:.5em; margin:.5em;" |大多数维基 ! style="padding:.5em; margin:.5em;"|“早期采用者”维基 |- | style="padding:.5em; margin:.5em;" |编者和读者<br />默认不显示我们的变更 | style="padding:.5em; margin:.5em;"|编者和读者<br />默认显示我们的变更 |- | style="padding:.5em; margin:.5em;" |仅编者可以加入<br/>(在用户设置中,通过选中[[Special:Preferences#mw-prefsection-rendering|{{int|prefs-rendering}}]]标签中的'''{{int|skinname-vector-2022}}''') | style="padding:.5em; margin:.5em;"|仅编者可以退出<br />(使用侧边栏中的'''[https://www.mediawiki.org/w/index.php?title=Special:Preferences&wprov=vctw1#mw-prefsection-rendering-skin-skin-prefs {{int|vector-opt-out}}]''',或直接在用户的参数设置内) |} {{anchor|Timeline}} === 部署计划和时间表 === <span style="background-color:#fc3;">我们希望我们的改进在2022年8月/9月成为所有wiki的默认设置。</span> <div style="margin:auto; text-align: center;">{{Reading/Web/Desktop Improvements/Timeline}}</div> {{anchor|test-wikis}}{{anchor|List of early adopter wikis (test wikis)}} {{hidden |1=所有的早期采用维基(测试维基) |headercss=background-color:#eaf3ff; |2= 第一组Wiki(在上面的时间轴上标记为◇): * [[:eu:|{{int|project-localized-name-euwiki}}]] * [[:fr:|{{int|project-localized-name-frwiki}}]] * [[wikt:fr:|{{int|project-localized-name-frwiktionary}}]] * [[:he:|{{int|project-localized-name-hewiki}}]] * [[:fa:|{{int|project-localized-name-fawiki}}]] * [[v:pt:|{{int|project-localized-name-ptwikiversity}}]] * [https://office.wikimedia.org/ 办公维基(Office Wiki)] 第二组Wiki(在上面的时间轴上标记为◇◇): * [[:bn:|{{int|project-localized-name-bnwiki}}]] * [[:voy:de:|{{int|project-localized-name-dewikivoyage}}]] * [[:ko:|{{int|project-localized-name-kowiki}}]] * [[:pt:|{{int|project-localized-name-ptwiki}}]] * [[:sr:|{{int|project-localized-name-srwiki}}]] * [[:tr:|{{int|project-localized-name-trwiki}}]] * [[:vec:|{{int|project-localized-name-vecwiki}}]] * [[:incubator:|{{int|project-localized-name-incubatorwiki}}]] 第三组Wiki(在上面的时间轴上标记为◇◇◇): * [[:ary:|{{int|project-localized-name-arywiki}}]] * [[q:fr:|{{int|project-localized-name-frwikiquote}}]] * [[:id:|{{int|project-localized-name-idwiki}}]] * [[n:pt:|{{int|project-localized-name-ptwikinews}}]] * [[n:pl:|{{int|project-localized-name-plwikinews}}]] * [[:th:|{{int|project-localized-name-thwiki}}]] * [[:vi:|{{int|project-localized-name-viwiki}}]] * [[b:vi:|{{int|project-localized-name-viwikibooks}}]] * <span class="mw-translate-fuzzy">MediaWiki Wiki</span> * [[:foundation:|維基媒體基金會管理Wiki]] * [https://collab.wikimedia.org/ 协作Wiki] * [[:strategy:|战略Wiki]] <span lang="en" dir="ltr" class="mw-content-ltr">Fourth group of wikis (marked as ◇◇◇◇ on the timeline above):</span> * [[s:ar:|{{int|project-localized-name-arwikisource}}]] * [[:ca:|{{int|project-localized-name-cawiki}}]] * [[s:pl:|{{int|project-localized-name-plwikisource}}]] * [[n:zh:|{{int|project-localized-name-zhwikinews}}]] }} {{anchor|participate}}{{anchor|contact}} == 参与并联系 == {{void|1= '''[[Special:Preferences#mw-prefsection-rendering|分别测试我们的功能]], [[Talk:Reading/Web/Desktop Improvements|提供反馈]], 然后[[Special:MyLanguage/Reading/Web/Desktop Improvements/Participate#Entire communities|加入我们的早期采用者维基]]!''' }} * {{clickable button 2|Special:Newsletter/28/subscribe|订阅简报}} * '''[[Special:Preferences#mw-prefsection-rendering|个人测试]]''':在首选项中,检查选项“{{int|skinname-vector-2022}}”。 您还可以使用[[Special:GlobalPreferences#mw-prefsection-rendering|全域设置]]启用我们的更改。 * '''[[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates/Talk to Web|加入我们的在线会议]]''':直到7月底,我们将每2-3周组织一次会议。暂定日期: {{date||6|13}}、{{date||6|28}}、{{date||7|12}}、{{date||7|26}}。 * '''推广''':通知您的社区。分享我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates|最新]]和[[Special:MyLanguage/Reading/Web/Desktop Improvements/Repository#posts|博客文章]]。 * '''报告错误''':要报告错误,请在Phabricator上创建一个任务(task)并添加{{Phabricator inline tag|desktop-improvements}}项目。 * '''早期采用者''':我们希望逐渐增加“早期采用者”维基的集合。 您认为您的社区可能有兴趣将我们的界面设为默认界面吗?请联系我们! <gallery mode="packed" style="float:left;"> File:Wikispotkanie-warszawa-2021-07-03-rd-26.jpg|[[User:SGrabarczuk (WMF)|Szymon Grabarczuk]]<br/>社群关系专员<br/>sgrabarczuk{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Mehran (WMF)|Mehran]]<br/>波斯语大使<br/>mehran-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Patafisik (WMF)|Patafisik]]<br/>法语大使<br/>patafisik-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Bluetpp (WMF)|Phuong Pham]]<br/>越南语大使<br/>ppham-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Zapipedia (WMF)|Zapipedia]]<br/>西班牙语大使<br/>izapico-ctr{{@}}wikimedia.org </gallery> {{clear}} * '''翻译''':帮助我们翻译相关页面: {{hidden|1=重要的翻译 |headercss=background-color:#eaf3ff; |2= 前三 # {{ll|Reading/Web/Desktop Improvements}} # {{ll|Reading/Web/Desktop Improvements/Frequently asked questions}} # {{ll|Reading/Web/Desktop Improvements/Features}} 其他重要的翻译 # [[Template:Reading/Web/Desktop Improvements/Office hours announcement]] # [[Template:Reading/Web/Desktop Improvements/Talk page intro]] # [[Template:Reading/Web/Desktop Improvements/Features/Navigation]] # [[Template:Reading/Web/Desktop Improvements/Header]] # {{ll|Reading/Web/Desktop Improvements/Updates}} # {{ll|Reading/Web/Desktop Improvements/Repository#posts}} [https://mediawiki.org/w/index.php?title=Special:Translate&group=agg-Desktop_Improvements&action=page&filter= 所有翻译的链接] }} == 什么功能将会被添加 == {{main|Reading/Web/Desktop Improvements/Features}} 我们尚未创建一份完整、详细的产品规格。随着时间的推移,每个功能都会'''分别'''构建和实施。已创建的功能仍在进行调整和改进。我们的决策基于社区反馈、用户测试和提取的API数据。 <gallery mode="slideshow" showthumbnails="" caption="已部署版本和早期概念的可视化"> Header Logo reconfiguration - commons pt - GIF.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|头部1:徽标重新布置]] File:Collapsible sidebar - wikidata fr - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|可收起的侧边栏]] File:Limit content width - wikiversity pt - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|有限制的宽度]] File:Sketch of search results with images and descriptions for Desktop improvements project.jpg|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Search|搜索:工具移动及其他改进]] File:04 - DIP - Language links in article header.png|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|语言切换1:在文章标题栏中的语言链接]] File:Consolidated user tools prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/User menu|用户菜单]] File:Search prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|头部2:固定的页面及条目头部]] File:Table of contents prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]] File:Article tools prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Page tools|文章工具]] </gallery> rz996ydrv871inbdm19odhl1itfiw3c 5387655 5387653 2022-07-29T04:23:11Z Chubit 17346826 wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} {{Wikimedia engineering project information | name = 桌面版改进 | description = Vector外观的一系列新功能和重新排列 | logo = Annotated Wikipedia Vector interface (logged-out).png | start = 2019-05 | end = 2022-08 | group = {{void|1=[[Special:MyLanguage/Reading/Web|阅读/网页]]}} | lead = [[User:OVasileva (WMF)|Olga Vasileva]](产品负责人) | team = [[Special:MyLanguage/Reading/Web|阅读/网页]] | Phabricator = desktop-improvements | updates = [[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates|更新子页面]] | progress = | previous = | next = | projectpage = | backlog = [[phab:project/view/67/|Phabricator任务面板]] | display = }} 当前默认的维基皮肤([[Special:MyLanguage/Skin:Vector|Vector]])已经使用了12年。 過去十年間,透過[[Special:MyLanguage/Manual:Extensions|擴充功能]]、[[Special:MyLanguage/Extension:Gadgets|小工具]]及使用者自訂程式,其介面愈來愈豐富。 這些大部分在視覺上仍欠協調,且非跨 wiki 可用。 同時,網站設計和讀者、編者的期待也逐漸改變。 我們認為,是時候採用這些想法,並讓它們成為所有 wiki 上、所有使用者有組織且一致的預設體驗, {{void|1= 接下来的几个季度里,[[Special:MyLanguage/Reading/Web/Team|读者网页组]]将基于研究和现有工具,开发对桌面版维基体验的改进。 }} 我们的目标是使维基媒体的维基更受欢迎,并增加对读者而言的实用性,维护对现有编辑者而言的实用性。我们会测量对维基的信任度、积极情绪的变化,以及维基的使用程度(常见操作,例如搜索和语言切换)。 目前在大多数维基上,只有登录用户才能选择使用改进皮肤。在特定的维基上,默认情况下所有用户都会使用改进皮肤,登录用户可以选择退出。我们希望逐渐增加“早期采用者”维基的集合,直到2022年7月所有维基都使用改进皮肤。 == 更新 == {{main|Reading/Web/Desktop Improvements/Updates}} {{:Reading/Web/Desktop Improvements/Updates}} == 我们的目标是什么? == === 想象一个衣柜 === <gallery mode="nolines" widths="300" heights="180"> File:CLOTHES HANGING OVER BED JAPANESE STYLE.jpg|我们想逐步重新排放这个… File:Wilmslow, United Kingdom (Unsplash).jpg|…变成这样:) </gallery> === 目前,界面… === '''…与期望不符。 …混乱而又不直观。 …不强调社群方面。 …与移动端不一致。''' # 桌面界面与现代网络平台的期望不符。感觉迷失了方向,脱节了。导航和界面链接随意地组织着。 # 混乱的网页使用户无法专注于他们查找的内容。对于读者而言,专注看内容具有挑战性,他们无法直观地切换语言,搜索内容或调整阅读设置。新编辑者无法凭直觉来设置帐户,打开编辑器或学习如何使用非文章页面。 # 只有极少数的读者了解维基媒体计划的功能。许多读者并不知道他们正在阅读的内容是由志愿者编写并经常更新的,也不知道他们也能做出贡献。 # 我们的桌面版网站,移动版网站和应用程序之间的体验差异很大,这使读者很难连接我们的产品。 维基媒体的网站概念缺乏统一性。 == 更改将如何进行 == === 原则 === '''我们不会影响到内容。 我们不会移除任何功能。 除了Vector,我们不会修改其它皮肤。 我们受到现有小工具的启发。 我们不会一蹴而就地进行重大更改。''' # 我们只在界面上做更改。在样式模板、页面内容结构、映射支持或跨维基模板方面不做任何更改。 # 虽然我们的变化很容易被注意到,但我们正在采取一种循序渐进的方法,并希望网站能继续让读者和编者感到熟悉。每个功能分别被讨论、开发和部署。 # 界面的元素可能会移动位置,但是所有的导航项和其他默认可用的功能将保持不变。 # Vector以外的皮肤不在我们的调整范围内。我们已经将Vector冻结为旧版Vector,并开始将我们的功能作为新的默认Vector的一部分部署。 # 我们分析了许多维基,并发现了许多有用的小工具。其中一些绝对值得出现并成为默认体验的一部分。 # 在开发前和部署后,我们都会收集数据(通过[[d:Q1810071|A/B测试]]、原型反馈回合等)。如果出现非常负面的结果,我们将回退更改。 # 我们打算与各种自愿参与的“早期采用者”维基(维基百科和姊妹项目)合作测试我们的改进。 {{void|1= # 首三个功能([[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|新头部]]、[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|可收起的侧边栏]]及[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|有限制的宽度]])已经在2020年7月部署。 # 我们的第二个大功能,一个改进的[[Reading/Web/Desktop Improvements/Features/Search/zh|搜索小工具]],将于2021年2月部署到早期采用者维基上。 }} {| class="plainlinks" style="text-align:center;" |-valign="top" ! style="padding:.5em; margin:.5em;" |大多数维基 ! style="padding:.5em; margin:.5em;"|“早期采用者”维基 |- | style="padding:.5em; margin:.5em;" |编者和读者<br />默认不显示我们的变更 | style="padding:.5em; margin:.5em;"|编者和读者<br />默认显示我们的变更 |- | style="padding:.5em; margin:.5em;" |仅编者可以加入<br/>(在用户设置中,通过选中[[Special:Preferences#mw-prefsection-rendering|{{int|prefs-rendering}}]]标签中的'''{{int|skinname-vector-2022}}''') | style="padding:.5em; margin:.5em;"|仅编者可以退出<br />(使用侧边栏中的'''[https://www.mediawiki.org/w/index.php?title=Special:Preferences&wprov=vctw1#mw-prefsection-rendering-skin-skin-prefs {{int|vector-opt-out}}]''',或直接在用户的参数设置内) |} {{anchor|Timeline}} === 部署计划和时间表 === <span style="background-color:#fc3;">我们希望我们的改进在2022年8月/9月成为所有wiki的默认设置。</span> <div style="margin:auto; text-align: center;">{{Reading/Web/Desktop Improvements/Timeline}}</div> {{anchor|test-wikis}}{{anchor|List of early adopter wikis (test wikis)}} {{hidden |1=所有的早期采用维基(测试维基) |headercss=background-color:#eaf3ff; |2= 第一组Wiki(在上面的时间轴上标记为◇): * [[:eu:|{{int|project-localized-name-euwiki}}]] * [[:fr:|{{int|project-localized-name-frwiki}}]] * [[wikt:fr:|{{int|project-localized-name-frwiktionary}}]] * [[:he:|{{int|project-localized-name-hewiki}}]] * [[:fa:|{{int|project-localized-name-fawiki}}]] * [[v:pt:|{{int|project-localized-name-ptwikiversity}}]] * [https://office.wikimedia.org/ 办公维基(Office Wiki)] 第二组Wiki(在上面的时间轴上标记为◇◇): * [[:bn:|{{int|project-localized-name-bnwiki}}]] * [[:voy:de:|{{int|project-localized-name-dewikivoyage}}]] * [[:ko:|{{int|project-localized-name-kowiki}}]] * [[:pt:|{{int|project-localized-name-ptwiki}}]] * [[:sr:|{{int|project-localized-name-srwiki}}]] * [[:tr:|{{int|project-localized-name-trwiki}}]] * [[:vec:|{{int|project-localized-name-vecwiki}}]] * [[:incubator:|{{int|project-localized-name-incubatorwiki}}]] 第三组Wiki(在上面的时间轴上标记为◇◇◇): * [[:ary:|{{int|project-localized-name-arywiki}}]] * [[q:fr:|{{int|project-localized-name-frwikiquote}}]] * [[:id:|{{int|project-localized-name-idwiki}}]] * [[n:pt:|{{int|project-localized-name-ptwikinews}}]] * [[n:pl:|{{int|project-localized-name-plwikinews}}]] * [[:th:|{{int|project-localized-name-thwiki}}]] * [[:vi:|{{int|project-localized-name-viwiki}}]] * [[b:vi:|{{int|project-localized-name-viwikibooks}}]] * MediaWiki.org(本维基) * [[:foundation:|維基媒體基金會管理Wiki]] * [https://collab.wikimedia.org/ 协作Wiki] * [[:strategy:|战略Wiki]] <span lang="en" dir="ltr" class="mw-content-ltr">Fourth group of wikis (marked as ◇◇◇◇ on the timeline above):</span> * [[s:ar:|{{int|project-localized-name-arwikisource}}]] * [[:ca:|{{int|project-localized-name-cawiki}}]] * [[s:pl:|{{int|project-localized-name-plwikisource}}]] * [[n:zh:|{{int|project-localized-name-zhwikinews}}]] }} {{anchor|participate}}{{anchor|contact}} == 参与并联系 == {{void|1= '''[[Special:Preferences#mw-prefsection-rendering|分别测试我们的功能]], [[Talk:Reading/Web/Desktop Improvements|提供反馈]], 然后[[Special:MyLanguage/Reading/Web/Desktop Improvements/Participate#Entire communities|加入我们的早期采用者维基]]!''' }} * {{clickable button 2|Special:Newsletter/28/subscribe|订阅简报}} * '''[[Special:Preferences#mw-prefsection-rendering|个人测试]]''':在首选项中,检查选项“{{int|skinname-vector-2022}}”。 您还可以使用[[Special:GlobalPreferences#mw-prefsection-rendering|全域设置]]启用我们的更改。 * '''[[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates/Talk to Web|加入我们的在线会议]]''':直到7月底,我们将每2-3周组织一次会议。暂定日期: {{date||6|13}}、{{date||6|28}}、{{date||7|12}}、{{date||7|26}}。 * '''推广''':通知您的社区。分享我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates|最新]]和[[Special:MyLanguage/Reading/Web/Desktop Improvements/Repository#posts|博客文章]]。 * '''报告错误''':要报告错误,请在Phabricator上创建一个任务(task)并添加{{Phabricator inline tag|desktop-improvements}}项目。 * '''早期采用者''':我们希望逐渐增加“早期采用者”维基的集合。 您认为您的社区可能有兴趣将我们的界面设为默认界面吗?请联系我们! <gallery mode="packed" style="float:left;"> File:Wikispotkanie-warszawa-2021-07-03-rd-26.jpg|[[User:SGrabarczuk (WMF)|Szymon Grabarczuk]]<br/>社群关系专员<br/>sgrabarczuk{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Mehran (WMF)|Mehran]]<br/>波斯语大使<br/>mehran-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Patafisik (WMF)|Patafisik]]<br/>法语大使<br/>patafisik-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Bluetpp (WMF)|Phuong Pham]]<br/>越南语大使<br/>ppham-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Zapipedia (WMF)|Zapipedia]]<br/>西班牙语大使<br/>izapico-ctr{{@}}wikimedia.org </gallery> {{clear}} * '''翻译''':帮助我们翻译相关页面: {{hidden|1=重要的翻译 |headercss=background-color:#eaf3ff; |2= 前三 # {{ll|Reading/Web/Desktop Improvements}} # {{ll|Reading/Web/Desktop Improvements/Frequently asked questions}} # {{ll|Reading/Web/Desktop Improvements/Features}} 其他重要的翻译 # [[Template:Reading/Web/Desktop Improvements/Office hours announcement]] # [[Template:Reading/Web/Desktop Improvements/Talk page intro]] # [[Template:Reading/Web/Desktop Improvements/Features/Navigation]] # [[Template:Reading/Web/Desktop Improvements/Header]] # {{ll|Reading/Web/Desktop Improvements/Updates}} # {{ll|Reading/Web/Desktop Improvements/Repository#posts}} [https://mediawiki.org/w/index.php?title=Special:Translate&group=agg-Desktop_Improvements&action=page&filter= 所有翻译的链接] }} == 什么功能将会被添加 == {{main|Reading/Web/Desktop Improvements/Features}} 我们尚未创建一份完整、详细的产品规格。随着时间的推移,每个功能都会'''分别'''构建和实施。已创建的功能仍在进行调整和改进。我们的决策基于社区反馈、用户测试和提取的API数据。 <gallery mode="slideshow" showthumbnails="" caption="已部署版本和早期概念的可视化"> Header Logo reconfiguration - commons pt - GIF.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|头部1:徽标重新布置]] File:Collapsible sidebar - wikidata fr - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|可收起的侧边栏]] File:Limit content width - wikiversity pt - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|有限制的宽度]] File:Sketch of search results with images and descriptions for Desktop improvements project.jpg|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Search|搜索:工具移动及其他改进]] File:04 - DIP - Language links in article header.png|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|语言切换1:在文章标题栏中的语言链接]] File:Consolidated user tools prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/User menu|用户菜单]] File:Search prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|头部2:固定的页面及条目头部]] File:Table of contents prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]] File:Article tools prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Page tools|文章工具]] </gallery> hf5k45lgvht3bihv7pft8tk8w8xgiet 5387657 5387655 2022-07-29T04:23:24Z Chubit 17346826 Created page with "第四组Wiki(在上面的时间轴上标记为$1):" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} {{Wikimedia engineering project information | name = 桌面版改进 | description = Vector外观的一系列新功能和重新排列 | logo = Annotated Wikipedia Vector interface (logged-out).png | start = 2019-05 | end = 2022-08 | group = {{void|1=[[Special:MyLanguage/Reading/Web|阅读/网页]]}} | lead = [[User:OVasileva (WMF)|Olga Vasileva]](产品负责人) | team = [[Special:MyLanguage/Reading/Web|阅读/网页]] | Phabricator = desktop-improvements | updates = [[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates|更新子页面]] | progress = | previous = | next = | projectpage = | backlog = [[phab:project/view/67/|Phabricator任务面板]] | display = }} 当前默认的维基皮肤([[Special:MyLanguage/Skin:Vector|Vector]])已经使用了12年。 過去十年間,透過[[Special:MyLanguage/Manual:Extensions|擴充功能]]、[[Special:MyLanguage/Extension:Gadgets|小工具]]及使用者自訂程式,其介面愈來愈豐富。 這些大部分在視覺上仍欠協調,且非跨 wiki 可用。 同時,網站設計和讀者、編者的期待也逐漸改變。 我們認為,是時候採用這些想法,並讓它們成為所有 wiki 上、所有使用者有組織且一致的預設體驗, {{void|1= 接下来的几个季度里,[[Special:MyLanguage/Reading/Web/Team|读者网页组]]将基于研究和现有工具,开发对桌面版维基体验的改进。 }} 我们的目标是使维基媒体的维基更受欢迎,并增加对读者而言的实用性,维护对现有编辑者而言的实用性。我们会测量对维基的信任度、积极情绪的变化,以及维基的使用程度(常见操作,例如搜索和语言切换)。 目前在大多数维基上,只有登录用户才能选择使用改进皮肤。在特定的维基上,默认情况下所有用户都会使用改进皮肤,登录用户可以选择退出。我们希望逐渐增加“早期采用者”维基的集合,直到2022年7月所有维基都使用改进皮肤。 == 更新 == {{main|Reading/Web/Desktop Improvements/Updates}} {{:Reading/Web/Desktop Improvements/Updates}} == 我们的目标是什么? == === 想象一个衣柜 === <gallery mode="nolines" widths="300" heights="180"> File:CLOTHES HANGING OVER BED JAPANESE STYLE.jpg|我们想逐步重新排放这个… File:Wilmslow, United Kingdom (Unsplash).jpg|…变成这样:) </gallery> === 目前,界面… === '''…与期望不符。 …混乱而又不直观。 …不强调社群方面。 …与移动端不一致。''' # 桌面界面与现代网络平台的期望不符。感觉迷失了方向,脱节了。导航和界面链接随意地组织着。 # 混乱的网页使用户无法专注于他们查找的内容。对于读者而言,专注看内容具有挑战性,他们无法直观地切换语言,搜索内容或调整阅读设置。新编辑者无法凭直觉来设置帐户,打开编辑器或学习如何使用非文章页面。 # 只有极少数的读者了解维基媒体计划的功能。许多读者并不知道他们正在阅读的内容是由志愿者编写并经常更新的,也不知道他们也能做出贡献。 # 我们的桌面版网站,移动版网站和应用程序之间的体验差异很大,这使读者很难连接我们的产品。 维基媒体的网站概念缺乏统一性。 == 更改将如何进行 == === 原则 === '''我们不会影响到内容。 我们不会移除任何功能。 除了Vector,我们不会修改其它皮肤。 我们受到现有小工具的启发。 我们不会一蹴而就地进行重大更改。''' # 我们只在界面上做更改。在样式模板、页面内容结构、映射支持或跨维基模板方面不做任何更改。 # 虽然我们的变化很容易被注意到,但我们正在采取一种循序渐进的方法,并希望网站能继续让读者和编者感到熟悉。每个功能分别被讨论、开发和部署。 # 界面的元素可能会移动位置,但是所有的导航项和其他默认可用的功能将保持不变。 # Vector以外的皮肤不在我们的调整范围内。我们已经将Vector冻结为旧版Vector,并开始将我们的功能作为新的默认Vector的一部分部署。 # 我们分析了许多维基,并发现了许多有用的小工具。其中一些绝对值得出现并成为默认体验的一部分。 # 在开发前和部署后,我们都会收集数据(通过[[d:Q1810071|A/B测试]]、原型反馈回合等)。如果出现非常负面的结果,我们将回退更改。 # 我们打算与各种自愿参与的“早期采用者”维基(维基百科和姊妹项目)合作测试我们的改进。 {{void|1= # 首三个功能([[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|新头部]]、[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|可收起的侧边栏]]及[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|有限制的宽度]])已经在2020年7月部署。 # 我们的第二个大功能,一个改进的[[Reading/Web/Desktop Improvements/Features/Search/zh|搜索小工具]],将于2021年2月部署到早期采用者维基上。 }} {| class="plainlinks" style="text-align:center;" |-valign="top" ! style="padding:.5em; margin:.5em;" |大多数维基 ! style="padding:.5em; margin:.5em;"|“早期采用者”维基 |- | style="padding:.5em; margin:.5em;" |编者和读者<br />默认不显示我们的变更 | style="padding:.5em; margin:.5em;"|编者和读者<br />默认显示我们的变更 |- | style="padding:.5em; margin:.5em;" |仅编者可以加入<br/>(在用户设置中,通过选中[[Special:Preferences#mw-prefsection-rendering|{{int|prefs-rendering}}]]标签中的'''{{int|skinname-vector-2022}}''') | style="padding:.5em; margin:.5em;"|仅编者可以退出<br />(使用侧边栏中的'''[https://www.mediawiki.org/w/index.php?title=Special:Preferences&wprov=vctw1#mw-prefsection-rendering-skin-skin-prefs {{int|vector-opt-out}}]''',或直接在用户的参数设置内) |} {{anchor|Timeline}} === 部署计划和时间表 === <span style="background-color:#fc3;">我们希望我们的改进在2022年8月/9月成为所有wiki的默认设置。</span> <div style="margin:auto; text-align: center;">{{Reading/Web/Desktop Improvements/Timeline}}</div> {{anchor|test-wikis}}{{anchor|List of early adopter wikis (test wikis)}} {{hidden |1=所有的早期采用维基(测试维基) |headercss=background-color:#eaf3ff; |2= 第一组Wiki(在上面的时间轴上标记为◇): * [[:eu:|{{int|project-localized-name-euwiki}}]] * [[:fr:|{{int|project-localized-name-frwiki}}]] * [[wikt:fr:|{{int|project-localized-name-frwiktionary}}]] * [[:he:|{{int|project-localized-name-hewiki}}]] * [[:fa:|{{int|project-localized-name-fawiki}}]] * [[v:pt:|{{int|project-localized-name-ptwikiversity}}]] * [https://office.wikimedia.org/ 办公维基(Office Wiki)] 第二组Wiki(在上面的时间轴上标记为◇◇): * [[:bn:|{{int|project-localized-name-bnwiki}}]] * [[:voy:de:|{{int|project-localized-name-dewikivoyage}}]] * [[:ko:|{{int|project-localized-name-kowiki}}]] * [[:pt:|{{int|project-localized-name-ptwiki}}]] * [[:sr:|{{int|project-localized-name-srwiki}}]] * [[:tr:|{{int|project-localized-name-trwiki}}]] * [[:vec:|{{int|project-localized-name-vecwiki}}]] * [[:incubator:|{{int|project-localized-name-incubatorwiki}}]] 第三组Wiki(在上面的时间轴上标记为◇◇◇): * [[:ary:|{{int|project-localized-name-arywiki}}]] * [[q:fr:|{{int|project-localized-name-frwikiquote}}]] * [[:id:|{{int|project-localized-name-idwiki}}]] * [[n:pt:|{{int|project-localized-name-ptwikinews}}]] * [[n:pl:|{{int|project-localized-name-plwikinews}}]] * [[:th:|{{int|project-localized-name-thwiki}}]] * [[:vi:|{{int|project-localized-name-viwiki}}]] * [[b:vi:|{{int|project-localized-name-viwikibooks}}]] * MediaWiki.org(本维基) * [[:foundation:|維基媒體基金會管理Wiki]] * [https://collab.wikimedia.org/ 协作Wiki] * [[:strategy:|战略Wiki]] 第四组Wiki(在上面的时间轴上标记为◇◇◇◇): * [[s:ar:|{{int|project-localized-name-arwikisource}}]] * [[:ca:|{{int|project-localized-name-cawiki}}]] * [[s:pl:|{{int|project-localized-name-plwikisource}}]] * [[n:zh:|{{int|project-localized-name-zhwikinews}}]] }} {{anchor|participate}}{{anchor|contact}} == 参与并联系 == {{void|1= '''[[Special:Preferences#mw-prefsection-rendering|分别测试我们的功能]], [[Talk:Reading/Web/Desktop Improvements|提供反馈]], 然后[[Special:MyLanguage/Reading/Web/Desktop Improvements/Participate#Entire communities|加入我们的早期采用者维基]]!''' }} * {{clickable button 2|Special:Newsletter/28/subscribe|订阅简报}} * '''[[Special:Preferences#mw-prefsection-rendering|个人测试]]''':在首选项中,检查选项“{{int|skinname-vector-2022}}”。 您还可以使用[[Special:GlobalPreferences#mw-prefsection-rendering|全域设置]]启用我们的更改。 * '''[[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates/Talk to Web|加入我们的在线会议]]''':直到7月底,我们将每2-3周组织一次会议。暂定日期: {{date||6|13}}、{{date||6|28}}、{{date||7|12}}、{{date||7|26}}。 * '''推广''':通知您的社区。分享我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Updates|最新]]和[[Special:MyLanguage/Reading/Web/Desktop Improvements/Repository#posts|博客文章]]。 * '''报告错误''':要报告错误,请在Phabricator上创建一个任务(task)并添加{{Phabricator inline tag|desktop-improvements}}项目。 * '''早期采用者''':我们希望逐渐增加“早期采用者”维基的集合。 您认为您的社区可能有兴趣将我们的界面设为默认界面吗?请联系我们! <gallery mode="packed" style="float:left;"> File:Wikispotkanie-warszawa-2021-07-03-rd-26.jpg|[[User:SGrabarczuk (WMF)|Szymon Grabarczuk]]<br/>社群关系专员<br/>sgrabarczuk{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Mehran (WMF)|Mehran]]<br/>波斯语大使<br/>mehran-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Patafisik (WMF)|Patafisik]]<br/>法语大使<br/>patafisik-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Bluetpp (WMF)|Phuong Pham]]<br/>越南语大使<br/>ppham-ctr{{@}}wikimedia.org File:Wikimedia Foundation hall blurred.jpg|[[User:Zapipedia (WMF)|Zapipedia]]<br/>西班牙语大使<br/>izapico-ctr{{@}}wikimedia.org </gallery> {{clear}} * '''翻译''':帮助我们翻译相关页面: {{hidden|1=重要的翻译 |headercss=background-color:#eaf3ff; |2= 前三 # {{ll|Reading/Web/Desktop Improvements}} # {{ll|Reading/Web/Desktop Improvements/Frequently asked questions}} # {{ll|Reading/Web/Desktop Improvements/Features}} 其他重要的翻译 # [[Template:Reading/Web/Desktop Improvements/Office hours announcement]] # [[Template:Reading/Web/Desktop Improvements/Talk page intro]] # [[Template:Reading/Web/Desktop Improvements/Features/Navigation]] # [[Template:Reading/Web/Desktop Improvements/Header]] # {{ll|Reading/Web/Desktop Improvements/Updates}} # {{ll|Reading/Web/Desktop Improvements/Repository#posts}} [https://mediawiki.org/w/index.php?title=Special:Translate&group=agg-Desktop_Improvements&action=page&filter= 所有翻译的链接] }} == 什么功能将会被添加 == {{main|Reading/Web/Desktop Improvements/Features}} 我们尚未创建一份完整、详细的产品规格。随着时间的推移,每个功能都会'''分别'''构建和实施。已创建的功能仍在进行调整和改进。我们的决策基于社区反馈、用户测试和提取的API数据。 <gallery mode="slideshow" showthumbnails="" caption="已部署版本和早期概念的可视化"> Header Logo reconfiguration - commons pt - GIF.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Header|头部1:徽标重新布置]] File:Collapsible sidebar - wikidata fr - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Collapsible sidebar|可收起的侧边栏]] File:Limit content width - wikiversity pt - GIF 2.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|有限制的宽度]] File:Sketch of search results with images and descriptions for Desktop improvements project.jpg|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Search|搜索:工具移动及其他改进]] File:04 - DIP - Language links in article header.png|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|语言切换1:在文章标题栏中的语言链接]] File:Consolidated user tools prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/User menu|用户菜单]] File:Search prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|头部2:固定的页面及条目头部]] File:Table of contents prototype for Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]] File:Article tools prototype for the Desktop improvements project.gif|[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Page tools|文章工具]] </gallery> m51ofh3lcsq5f6xqdhqgu3udv5fgjmq Translations:Help:Reference Previews/44/ja 1198 1003260 5387441 3468106 2022-07-28T22:21:32Z Shirayuki 472859 wrong markup wikitext text/x-wiki 参考資料プレビュー機能はドイツ語話者コミュニティの技術要望リストに対応する目的で、開発はウィキメディアドイツ支部 (WMDE) の技術チームが担当しウィキメディア財団 (WMF) Reading Web チームが支援しました。設計部分は WMFが開発しています。 3qvoef3vs9loza4379p84uyo8twip52 Wikimedia Release Engineering Team/Checkin archive/20191023 0 1004764 5387512 3615611 2022-07-28T23:50:46Z 93.110.180.47 wikitext text/x-wiki <!-- Pad for the Release Engineering Team weekly meeting Archive at: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Checkin_archive Last Time: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Checkin_archive/20191016 Template https://etherpad.wikimedia.org/p/releng-weekly-template --> = 2019-10-23 = == Vacations/Important dates == : https://office.wikimedia.org/wiki/HR_Corner/Holiday_List : [[Wikimedia_Release_Engineering_Team/Time_off|How to do it]] <!--https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Time_off for ease of access from etherpad --> <!-- === OCTOBER === --> * October 8: Željko holiday (Independence Day) * October 11: Željko conference (https://2019.webcampzg.org/ ) * October 14 (Indigenous Peoples' Day): US Staff <!-- YOU ARE HERE --> * October 24–27: James at WikidataCon 2019 in Berlin <!-- === NOVEMBER === --> * November 1 (All Saints' Day): Željko holiday * November 8–10: WikiCon North America (James) * November 11 (Veterans' Day): US Staff * November 12–15: TechConf19 * November 16–20: Offsite * November 21-30: Jeena * November 25-29: Dan * November 28–29 (Thanksgiving): US Staff <!-- === DECEMBER === --> * December 1-2: Jeena * December 6: Lars (Finnish Independence Day) * December 25–31 (Christmas): US Staff * December 25–26: Lars, Željko, Christmas <!-- === 2020 === --> <!-- === January === --> * 1 January (New Year's Day): US Staff, Lars, Željko * 20 January (Martin Luther King Jr. Day): US Staff == Rotating positions == === Train === <!-- https://tools.wmflabs.org/versions/ --> : ''Maniphest query for deployment blocker tasks: https://phabricator.wikimedia.org/maniphest/query/s3KW8bpsXhYF/#R'' <!-- == Rotation == * Jeena * Lars * Brennen * Antoine * Mukunda * Dan --> * 14 Oct - wmf.2 - Jeena + Lars <!-- YOU ARE HERE --> * 21 Oct - wmf.3 - Lars + Brennen * 28 Oct - wmf.4 - Brennen + Mukunda * 4 Nov - wmf.5 - Mukunda + Antoine * 11 Nov - wmf.6 - No Train (Tech conf) * 18 Nov - wmf.7 - No Train (Off site) * 25 Nov - wmf.8 - Antoine + Jeena (Thanksgiving) * 2 Dec - wmf.9 - TBD * 9 Dec - wmf.10 - TBD * 16 Dec - wmf.11 - TBD * 23 Dec - wmf.12 - No Train or any other deploys (Winterval) * 30 Dec - wmf.13 - No Train or any other deploys (Still Winterval) * 6 Jan - wmf.14 - TBD * 13 Jan - wmf.15 - TBD === SoS === * Aug 14 onward: Zeljko 🎸 🎷 \o/ == Team Business == === Timespent spreadsheet === : For the avoidance of doubt: fill out the sheet week number for the previous week * spreadsheet for week 42 (2019-10-14):https://docs.google.com/spreadsheets/d/1YS_2eUQWUOnygshMfxgGPu93GKGCO5t00yjUREQ5B-I/edit#gid=442607278 ** reminder: your time spent doesn't need to total to 100% === Clinic Duty Proposal === * https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Clinic_Duty ** thcipriani JFDI === November Offsite/Summit === * TechConf19: November 12–15 * Offsite: November 16–20 ** Arrive the 15th ** 16th is our fun day/outing ** 17–20 are working days ** 21st fly home ** https://etherpad.wikimedia.org/p/EngProdTeam-Offsite-2019-11-planning ** Dietary restrictions due TODAY! ** New proposal on etherpad: how does EngProd want to use betterworks ** Outing day! Vote please === Book club === * https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Book_club ** Good discussion! https://etherpad.wikimedia.org/p/releng-book-club === Monthly reflection on accomplishments - October '19 edition === : https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Monthly_notable_accomplishments : Add as you have them! === October === * Dev images are now automatically created as part of postmerge via the pipeline for: ** Parsoid ** Soon: RestBASE * Selenium documentation updated https://www.mediawiki.org/wiki/Selenium/Node.js * Quibble 0.0.36 released https://lists.wikimedia.org/pipermail/wikitech-l/2019-October/092658.html * Quibble 0.0.37 released https://lists.wikimedia.org/pipermail/wikitech-l/2019-October/092660.html * Quibble 0.0.38 & 0.0.39 released for mediawiki/tools/api-testing * Introducing Phatality - Streamlined error reporting from Kibana to Phabricator https://phabricator.wikimedia.org/phame/post/view/177/introducing_phatality/ * HHVM removed from CI and MediaWiki. * Gerrit is on gerrit1001 now ** … and so is most of the code review. ;-) === Incoming/Needs attention === === Scrum of Scrums for next week === ==== Internal team notes, not for pasting into the SoS notes ==== ==== Incoming from last week (aka this morning) ==== ==== Outgoing next week ==== * Blocked: ** Site Reliability Engineering: logstash-beta.wmflabs.org does not receive any mediawiki events https://phabricator.wikimedia.org/T233134 * Updates: ** v3 of CI arch document for new CI wants review and feedback https://www.mediawiki.org/wiki/User:LarsWirzenius/NewCI ** Gerrit is now on a newer (larger) server *** There was some problem with rollout (patches looking unmerged that were actually merged) *** Resolved now *** All gory details on https://phabricator.wikimedia.org/T236114 ** Train Health *** Last week: 1.35.0-wmf.2 - [[phab:T233850]] *** This week: 1.35.0-wmf.3 - [[phab:T233851]] *** Next week: 1.35.0-wmf.4 - [[phab:T233852]] ==== Callouts ==== === Train status and happenings === : https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Roles#Train_Conductor == Standup! == * Make sure your tasks are correct on our kanban board! ** https://phabricator.wikimedia.org/project/view/4311/ - 2019-10 === Antoine === ==== Last week ==== * Best thing ** Paired git fixage with Tyler for hmm lot of hours. Pair programming bash over Google Meet is a great experience. ** For Wikibase.git : extracted Selenium to a standalone jobs ( https://phabricator.wikimedia.org/T232759 ) ** Quibble 0.0.39 for mediawiki/tools/api-testing (very cool project) * Worst thing ** * What I planned vs did ** Switch integration/config to use jenkins-job-builder from pypi instead of our git repo ** PostBuildScript jenkins plugin upgrade prepared ** Nerd snipped on some weird logstash index fields limit https://phabricator.wikimedia.org/T234564 * Unplannned ** Gerrit post migration magic (thank you Tyler!) (thcipriani: thank you!) ==== This week ==== * What I plan to do ** TechConf preparation with Kosta / WMDE-Fisch * Blockers ** WMCS blocked: they need CI for a golang projects https://phabricator.wikimedia.org/T236203 (dduvall: we have a docker-pkg-built golang base image; see blubber's .pipeline/blubber.yaml) ** php-xdebug needs upgrade (slows down phpunit coverage report) ==== Other ==== * === Brennen === ==== Last week ==== * Best thing ** Pairing in general, messing with sshecret. * Worst thing ** Moments of panic about logs prior to deploy. * What I planned vs did ** {{done}} Make sure local-charts install script works on buster ** {{done}} Further TechConf input, CI session planning ** {{in progress}} Train pairing * Unplannned ** Some time investigating broken mediawiki/core dev images ** Some time investigating toollabs to restart dockerregistry ==== This week ==== * What I plan to do ** Train ** Sort out all hands travel ** Dev environment hackery *** Check out k3sup? ** Think about TechConf local dev sessions / discuss ** Improve sshecret pull req: https://github.com/thcipriani/sshecret/pull/2 * Blockers ** ==== Other ==== * === Dan === ==== Last week ==== * Best thing ** Diagramming Seakeeper subsystems * Worst thing ** Fixing janky Jenkins reports *** starting in August, 30-day reports should be accurate * What I planned vs did ** Seakeeper proposal, fleshed out descriptions of CI subsystems for proposed k8s namespaces * Unplannned ** Fixed problems with Jenkins reports at https://people.wikimedia.org/~dduvall/jenkins *** Build retention differences made for inaccurate 30-day reports. Working around this by aggregating from past build archives. ==== This week ==== * What I plan to do ** Seakeeper proposal, gathering capacity/resource utilization stats * Blockers ** ==== Other ==== * === Greg === ==== Last week ==== * Best thing ** The TechConf program committee is great to work with, even when we are stressed * Worst thing ** Time constraint on the Tuning Session slide creation (which had knock off effects of figuring out what the hell these OKRs and metrics really are) ** Effing moving * What I planned vs did ** techconf ** tuning session * Unplannned ** ==== This week ==== * What I plan to do ** tech conf schedule creation (well, version 2.0 of the schedule) and post it ** engprod logistics setup * Blockers ** time ==== Other ==== * TechConf office hours happening next week on IRC, email going out shortly announcing them * Desire/stretch: create a homepage for Engineering Producitivity somewhere :) === James === ==== Last week ==== * Best thing ** Made progress discussing with Timo way forward for static configuration work; next step is autogenerating dblists from YAML. * Worst thing ** Real jetlag for the first time in a few years. Meh. * What I planned vs did ** {{done}} OOUI migration to node 10 / PHP72 ** {{not done}} Fundraising Tech CRM image to PHP70 (could do with input from Antoine) https://gerrit.wikimedia.org/r/c/integration/config/+/540683 for https://phabricator.wikimedia.org/T230446 ** {{partially done}} More static configuration work, a bit delayed. ** {{done}} More TechConf thinking/planning. ** {{done}} UBNs as they arise. * Unplannned ** Renamed "unversioned" PHP (PHP70) images to be explicit *** Antoine: THANK YOU ** Helping Analytics put a "stats for this site" link in the site footer T235803 ==== This week ==== * What I plan to do ** WikiDataCon from tomorrow onwards; back in the US next Wednesday. ** Whatever breaks. ** YAML/static builds of dblists. * Blockers ** — ==== Other ==== * — === Jean-Rene === ==== Last week ==== * Best thing ** * Worst thing ** * What I planned vs did ** * Unplannned ** ==== This week ==== * What I plan to do ** * Blockers ** ==== Other ==== * === Jeena === ==== Last week ==== * Best thing ** finished restrouter chart...hopefully \o/ \O/ \:D/ * Worst thing ** spent time trying to debug Visual Editor not working, unexpectedly there was an error in the browser console * What I planned vs did ** {{not done}} timespent spreadsheet ** {{not done}} work with zeljko on getting local-charts running - Željko: feel free to pospond until you're done with train ** {{in progress}} look at seakeeper proposal ** {{done}} train ** {{done}} update restrouter deployment-charts config for dev purposes * Unplannned ** debug broken mw core image ==== This week ==== * What I plan to do ** tech conf session planning ** changes to mw core image publish pipeline to log more and fail if prereq script errors ** re-open patchsets to build restbase dev image ** timespent spreadsheet ** work with zeljko on getting local-charts running ** ... * Blockers ** ==== Other ==== * tiny sunflower === Lars === ==== Last week ==== * Best thing ** Going to TechConf * Worst thing ** Not going to a mountain in TN * What I planned vs did ** {{done}} Help Jeena with train, a little, as backup. ** {{done}} Seek feedback on v3 of CI arch doc. ** {{done}} Update engprod on PGP signing for offsite. ** {{not done}} Set up Argo in a K8s cluster somewhere. *** Needs uninterrupted time, and I've been easily distractable. Also train. * Unplannned ** Was invited to TechConf, and did much arranging of travel. ** More review of Dan's Seekeeper proposal. ** Wrote up book club discussion on wiki. *** https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Book_club/Software_Testing_Anti-Patterns ** Failed to deploy train, didn't get to group0 even, but much excitement was had by everyone. ** Wrote a wrapper around rsync, in case it's useful some day. ** Registered for All Hands, started arranging travel. ==== This week ==== * What I plan to do ** Train, 1.35.0-wmf.3 ** Skim Go book, write a small program from scratch: fetch a web page, diff against previously fetched version. ** Attempt to set up study groups, or possibly SIGs, for Go and Rust. * Blockers ** ==== Other ==== * The Darkness is here until about March or April, expect SADness * performance has TT; releng has BB, DD, and MM; qte has no doubled initials ** :-) ** EngProd has GG :P ** My "legal" name is Tyler Henry Turley-Cipriani, so TTish === Mukunda === ==== Last week ==== * Best thing ** Phab1001 is up and running * Worst thing ** Didn't get around to testing the "Ferret" Fulltext search engine in phab (yet) * What I planned vs did ** Mostly {{done}} Finish getting branch.py ready for the wmf production branching (WIP: https://gerrit.wikimedia.org/r/#/c/mediawiki/tools/release/+/543248/ ) ** {{done}} Try to build some tests for branch.py ** {{done}} More work on phabricator high-availability & disaster recovery planning. *** phab1001 should be nearly ready to become the primary server now. ** {{not done}} Test out phabricator's built-in search engine with an eye toward dropping elasticsearch if the integrated search performs as well. * Unplannned ** {{done}} https://phabricator.wikimedia.org/T235945 ==== This week ==== * What I plan to do ** Test out phabricator's built-in search engine ** Drum up interest in patch-triage (email wikitech-l, not sure what else to do) ** Get branch.py ready for full automation in releases-jenkins ** Deploy phatality (after https://gerrit.wikimedia.org/r/#/c/545593/ merges) ** Deploy phabricator * Blockers ** code review of https://gerrit.wikimedia.org/r/#/c/545593/ ==== <span lang="en" dir="rtl">Other</span> ==== * === Tyler === ==== Last week ==== * Best thing ** Seeing the train pairing thing work :) ** pairing with Antoine on Gerrit migration fallout * Worst thing ** Gerrit migration fallout * What I planned vs did ** {{done}} connect with SRE re New CI (again) ** {{done}} Reach out to folks about being on Sr. SWE interview loop ** {{done}} announce dec code freeze ** {{done}}? tuning session prep ** {{done}} Gerrit -> gerrit1001 * Unplannned ** Gerrit migration fallout ** Updates to deployment-calendar scheduler -- awight noticed some issues ==== This week ==== * What I plan to do ** Resumé review ** Work out clinic duty rotation ** Next bookclub email ** Gerrit/JVM tuning to make use of Moar Memory™ * Blockers ** Time ** Dog ** Blazey at conference ==== Other ==== * Picking up Blazey at airport this evening, may cut out a bit early === Zeljko === ==== Last week ==== * Best thing ** Email from Safeguard: "Please note: all documentation must be password protected from this point using the following (password)" * Worst thing ** T236282 `npm run selenium` fails with `SyntaxError: Unexpected identifier` * What I planned vs did ** {{in progress}} T234610 ERROR webdriver: Request failed due to Error: session not created: Chrome version must be between 70 and 73 ** {{in progress}} T199113 All repositories with Selenium tests should use wdio-mediawiki * Unplannned ** Safeguard ** T235795 Create test for GrowthExperiments to check for ability to disable homepage ** T233820 mediawiki/core Selenium tests fail when targeting mediawiki/vagrant VM ** T236282 `npm run selenium` fails with `SyntaxError: Unexpected identifier` ==== This week ==== * What I plan to do ** T234610 ERROR webdriver: Request failed due to Error: session not created: Chrome version must be between 70 and 73 ** T199113 All repositories with Selenium tests should use wdio-mediawiki * Blockers ** ==== Other ==== * Saw Rambo: Last Blood. Not recommended. <!-- MEETING TOTAL TIME: 36m 12s --> [[Category:Release Engineering Team checkin archive{{#translation:}}]] lvx6effe0w8qhhh78unlhkjcxb5a06x 5387745 5387512 2022-07-29T08:12:29Z P858snake 31302 Reverted edits by [[Special:Contribs/93.110.180.47|93.110.180.47]] ([[User talk:93.110.180.47|talk]]) to last version by 1234qwer1234qwer4 wikitext text/x-wiki <!-- Pad for the Release Engineering Team weekly meeting Archive at: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Checkin_archive Last Time: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Checkin_archive/20191016 Template https://etherpad.wikimedia.org/p/releng-weekly-template --> = 2019-10-23 = == Vacations/Important dates == : https://office.wikimedia.org/wiki/HR_Corner/Holiday_List : [[Wikimedia_Release_Engineering_Team/Time_off|How to do it]] <!--https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Time_off for ease of access from etherpad --> <!-- === OCTOBER === --> * October 8: Željko holiday (Independence Day) * October 11: Željko conference (https://2019.webcampzg.org/ ) * October 14 (Indigenous Peoples' Day): US Staff <!-- YOU ARE HERE --> * October 24–27: James at WikidataCon 2019 in Berlin <!-- === NOVEMBER === --> * November 1 (All Saints' Day): Željko holiday * November 8–10: WikiCon North America (James) * November 11 (Veterans' Day): US Staff * November 12–15: TechConf19 * November 16–20: Offsite * November 21-30: Jeena * November 25-29: Dan * November 28–29 (Thanksgiving): US Staff <!-- === DECEMBER === --> * December 1-2: Jeena * December 6: Lars (Finnish Independence Day) * December 25–31 (Christmas): US Staff * December 25–26: Lars, Željko, Christmas <!-- === 2020 === --> <!-- === January === --> * 1 January (New Year's Day): US Staff, Lars, Željko * 20 January (Martin Luther King Jr. Day): US Staff == Rotating positions == === Train === <!-- https://tools.wmflabs.org/versions/ --> : ''Maniphest query for deployment blocker tasks: https://phabricator.wikimedia.org/maniphest/query/s3KW8bpsXhYF/#R'' <!-- == Rotation == * Jeena * Lars * Brennen * Antoine * Mukunda * Dan --> * 14 Oct - wmf.2 - Jeena + Lars <!-- YOU ARE HERE --> * 21 Oct - wmf.3 - Lars + Brennen * 28 Oct - wmf.4 - Brennen + Mukunda * 4 Nov - wmf.5 - Mukunda + Antoine * 11 Nov - wmf.6 - No Train (Tech conf) * 18 Nov - wmf.7 - No Train (Off site) * 25 Nov - wmf.8 - Antoine + Jeena (Thanksgiving) * 2 Dec - wmf.9 - TBD * 9 Dec - wmf.10 - TBD * 16 Dec - wmf.11 - TBD * 23 Dec - wmf.12 - No Train or any other deploys (Winterval) * 30 Dec - wmf.13 - No Train or any other deploys (Still Winterval) * 6 Jan - wmf.14 - TBD * 13 Jan - wmf.15 - TBD === SoS === * Aug 14 onward: Zeljko 🎸 🎷 \o/ == Team Business == === Timespent spreadsheet === : For the avoidance of doubt: fill out the sheet week number for the previous week * spreadsheet for week 42 (2019-10-14):https://docs.google.com/spreadsheets/d/1YS_2eUQWUOnygshMfxgGPu93GKGCO5t00yjUREQ5B-I/edit#gid=442607278 ** reminder: your time spent doesn't need to total to 100% === Clinic Duty Proposal === * https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Clinic_Duty ** thcipriani JFDI === November Offsite/Summit === * TechConf19: November 12–15 * Offsite: November 16–20 ** Arrive the 15th ** 16th is our fun day/outing ** 17–20 are working days ** 21st fly home ** https://etherpad.wikimedia.org/p/EngProdTeam-Offsite-2019-11-planning ** Dietary restrictions due TODAY! ** New proposal on etherpad: how does EngProd want to use betterworks ** Outing day! Vote please === Book club === * https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Book_club ** Good discussion! https://etherpad.wikimedia.org/p/releng-book-club === Monthly reflection on accomplishments - October '19 edition === : https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Monthly_notable_accomplishments : Add as you have them! === October === * Dev images are now automatically created as part of postmerge via the pipeline for: ** Parsoid ** Soon: RestBASE * Selenium documentation updated https://www.mediawiki.org/wiki/Selenium/Node.js * Quibble 0.0.36 released https://lists.wikimedia.org/pipermail/wikitech-l/2019-October/092658.html * Quibble 0.0.37 released https://lists.wikimedia.org/pipermail/wikitech-l/2019-October/092660.html * Quibble 0.0.38 & 0.0.39 released for mediawiki/tools/api-testing * Introducing Phatality - Streamlined error reporting from Kibana to Phabricator https://phabricator.wikimedia.org/phame/post/view/177/introducing_phatality/ * HHVM removed from CI and MediaWiki. * Gerrit is on gerrit1001 now ** … and so is most of the code review. ;-) === Incoming/Needs attention === === Scrum of Scrums for next week === ==== Internal team notes, not for pasting into the SoS notes ==== ==== Incoming from last week (aka this morning) ==== ==== Outgoing next week ==== * Blocked: ** Site Reliability Engineering: logstash-beta.wmflabs.org does not receive any mediawiki events https://phabricator.wikimedia.org/T233134 * Updates: ** v3 of CI arch document for new CI wants review and feedback https://www.mediawiki.org/wiki/User:LarsWirzenius/NewCI ** Gerrit is now on a newer (larger) server *** There was some problem with rollout (patches looking unmerged that were actually merged) *** Resolved now *** All gory details on https://phabricator.wikimedia.org/T236114 ** Train Health *** Last week: 1.35.0-wmf.2 - [[phab:T233850]] *** This week: 1.35.0-wmf.3 - [[phab:T233851]] *** Next week: 1.35.0-wmf.4 - [[phab:T233852]] ==== Callouts ==== === Train status and happenings === : https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Roles#Train_Conductor == Standup! == * Make sure your tasks are correct on our kanban board! ** https://phabricator.wikimedia.org/project/view/4311/ - 2019-10 === Antoine === ==== Last week ==== * Best thing ** Paired git fixage with Tyler for hmm lot of hours. Pair programming bash over Google Meet is a great experience. ** For Wikibase.git : extracted Selenium to a standalone jobs ( https://phabricator.wikimedia.org/T232759 ) ** Quibble 0.0.39 for mediawiki/tools/api-testing (very cool project) * Worst thing ** * What I planned vs did ** Switch integration/config to use jenkins-job-builder from pypi instead of our git repo ** PostBuildScript jenkins plugin upgrade prepared ** Nerd snipped on some weird logstash index fields limit https://phabricator.wikimedia.org/T234564 * Unplannned ** Gerrit post migration magic (thank you Tyler!) (thcipriani: thank you!) ==== This week ==== * What I plan to do ** TechConf preparation with Kosta / WMDE-Fisch * Blockers ** WMCS blocked: they need CI for a golang projects https://phabricator.wikimedia.org/T236203 (dduvall: we have a docker-pkg-built golang base image; see blubber's .pipeline/blubber.yaml) ** php-xdebug needs upgrade (slows down phpunit coverage report) ==== Other ==== * === Brennen === ==== Last week ==== * Best thing ** Pairing in general, messing with sshecret. * Worst thing ** Moments of panic about logs prior to deploy. * What I planned vs did ** {{done}} Make sure local-charts install script works on buster ** {{done}} Further TechConf input, CI session planning ** {{in progress}} Train pairing * Unplannned ** Some time investigating broken mediawiki/core dev images ** Some time investigating toollabs to restart dockerregistry ==== This week ==== * What I plan to do ** Train ** Sort out all hands travel ** Dev environment hackery *** Check out k3sup? ** Think about TechConf local dev sessions / discuss ** Improve sshecret pull req: https://github.com/thcipriani/sshecret/pull/2 * Blockers ** ==== Other ==== * === Dan === ==== Last week ==== * Best thing ** Diagramming Seakeeper subsystems * Worst thing ** Fixing janky Jenkins reports *** starting in August, 30-day reports should be accurate * What I planned vs did ** Seakeeper proposal, fleshed out descriptions of CI subsystems for proposed k8s namespaces * Unplannned ** Fixed problems with Jenkins reports at https://people.wikimedia.org/~dduvall/jenkins *** Build retention differences made for inaccurate 30-day reports. Working around this by aggregating from past build archives. ==== This week ==== * What I plan to do ** Seakeeper proposal, gathering capacity/resource utilization stats * Blockers ** ==== Other ==== * === Greg === ==== Last week ==== * Best thing ** The TechConf program committee is great to work with, even when we are stressed * Worst thing ** Time constraint on the Tuning Session slide creation (which had knock off effects of figuring out what the hell these OKRs and metrics really are) ** Effing moving * What I planned vs did ** techconf ** tuning session * Unplannned ** ==== This week ==== * What I plan to do ** tech conf schedule creation (well, version 2.0 of the schedule) and post it ** engprod logistics setup * Blockers ** time ==== Other ==== * TechConf office hours happening next week on IRC, email going out shortly announcing them * Desire/stretch: create a homepage for Engineering Producitivity somewhere :) === James === ==== Last week ==== * Best thing ** Made progress discussing with Timo way forward for static configuration work; next step is autogenerating dblists from YAML. * Worst thing ** Real jetlag for the first time in a few years. Meh. * What I planned vs did ** {{done}} OOUI migration to node 10 / PHP72 ** {{not done}} Fundraising Tech CRM image to PHP70 (could do with input from Antoine) https://gerrit.wikimedia.org/r/c/integration/config/+/540683 for https://phabricator.wikimedia.org/T230446 ** {{partially done}} More static configuration work, a bit delayed. ** {{done}} More TechConf thinking/planning. ** {{done}} UBNs as they arise. * Unplannned ** Renamed "unversioned" PHP (PHP70) images to be explicit *** Antoine: THANK YOU ** Helping Analytics put a "stats for this site" link in the site footer T235803 ==== This week ==== * What I plan to do ** WikiDataCon from tomorrow onwards; back in the US next Wednesday. ** Whatever breaks. ** YAML/static builds of dblists. * Blockers ** — ==== Other ==== * — === Jean-Rene === ==== Last week ==== * Best thing ** * Worst thing ** * What I planned vs did ** * Unplannned ** ==== This week ==== * What I plan to do ** * Blockers ** ==== Other ==== * === Jeena === ==== Last week ==== * Best thing ** finished restrouter chart...hopefully \o/ \O/ \:D/ * Worst thing ** spent time trying to debug Visual Editor not working, unexpectedly there was an error in the browser console * What I planned vs did ** {{not done}} timespent spreadsheet ** {{not done}} work with zeljko on getting local-charts running - Željko: feel free to pospond until you're done with train ** {{in progress}} look at seakeeper proposal ** {{done}} train ** {{done}} update restrouter deployment-charts config for dev purposes * Unplannned ** debug broken mw core image ==== This week ==== * What I plan to do ** tech conf session planning ** changes to mw core image publish pipeline to log more and fail if prereq script errors ** re-open patchsets to build restbase dev image ** timespent spreadsheet ** work with zeljko on getting local-charts running ** ... * Blockers ** ==== Other ==== * tiny sunflower === Lars === ==== Last week ==== * Best thing ** Going to TechConf * Worst thing ** Not going to a mountain in TN * What I planned vs did ** {{done}} Help Jeena with train, a little, as backup. ** {{done}} Seek feedback on v3 of CI arch doc. ** {{done}} Update engprod on PGP signing for offsite. ** {{not done}} Set up Argo in a K8s cluster somewhere. *** Needs uninterrupted time, and I've been easily distractable. Also train. * Unplannned ** Was invited to TechConf, and did much arranging of travel. ** More review of Dan's Seekeeper proposal. ** Wrote up book club discussion on wiki. *** https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Book_club/Software_Testing_Anti-Patterns ** Failed to deploy train, didn't get to group0 even, but much excitement was had by everyone. ** Wrote a wrapper around rsync, in case it's useful some day. ** Registered for All Hands, started arranging travel. ==== This week ==== * What I plan to do ** Train, 1.35.0-wmf.3 ** Skim Go book, write a small program from scratch: fetch a web page, diff against previously fetched version. ** Attempt to set up study groups, or possibly SIGs, for Go and Rust. * Blockers ** ==== Other ==== * The Darkness is here until about March or April, expect SADness * performance has TT; releng has BB, DD, and MM; qte has no doubled initials ** :-) ** EngProd has GG :P ** My "legal" name is Tyler Henry Turley-Cipriani, so TTish === Mukunda === ==== Last week ==== * Best thing ** Phab1001 is up and running * Worst thing ** Didn't get around to testing the "Ferret" Fulltext search engine in phab (yet) * What I planned vs did ** Mostly {{done}} Finish getting branch.py ready for the wmf production branching (WIP: https://gerrit.wikimedia.org/r/#/c/mediawiki/tools/release/+/543248/ ) ** {{done}} Try to build some tests for branch.py ** {{done}} More work on phabricator high-availability & disaster recovery planning. *** phab1001 should be nearly ready to become the primary server now. ** {{not done}} Test out phabricator's built-in search engine with an eye toward dropping elasticsearch if the integrated search performs as well. * Unplannned ** {{done}} https://phabricator.wikimedia.org/T235945 ==== This week ==== * What I plan to do ** Test out phabricator's built-in search engine ** Drum up interest in patch-triage (email wikitech-l, not sure what else to do) ** Get branch.py ready for full automation in releases-jenkins ** Deploy phatality (after https://gerrit.wikimedia.org/r/#/c/545593/ merges) ** Deploy phabricator * Blockers ** code review of https://gerrit.wikimedia.org/r/#/c/545593/ ==== Other ==== * === Tyler === ==== Last week ==== * Best thing ** Seeing the train pairing thing work :) ** pairing with Antoine on Gerrit migration fallout * Worst thing ** Gerrit migration fallout * What I planned vs did ** {{done}} connect with SRE re New CI (again) ** {{done}} Reach out to folks about being on Sr. SWE interview loop ** {{done}} announce dec code freeze ** {{done}}? tuning session prep ** {{done}} Gerrit -> gerrit1001 * Unplannned ** Gerrit migration fallout ** Updates to deployment-calendar scheduler -- awight noticed some issues ==== This week ==== * What I plan to do ** Resumé review ** Work out clinic duty rotation ** Next bookclub email ** Gerrit/JVM tuning to make use of Moar Memory™ * Blockers ** Time ** Dog ** Blazey at conference ==== Other ==== * Picking up Blazey at airport this evening, may cut out a bit early === Zeljko === ==== Last week ==== * Best thing ** Email from Safeguard: "Please note: all documentation must be password protected from this point using the following (password)" * Worst thing ** T236282 `npm run selenium` fails with `SyntaxError: Unexpected identifier` * What I planned vs did ** {{in progress}} T234610 ERROR webdriver: Request failed due to Error: session not created: Chrome version must be between 70 and 73 ** {{in progress}} T199113 All repositories with Selenium tests should use wdio-mediawiki * Unplannned ** Safeguard ** T235795 Create test for GrowthExperiments to check for ability to disable homepage ** T233820 mediawiki/core Selenium tests fail when targeting mediawiki/vagrant VM ** T236282 `npm run selenium` fails with `SyntaxError: Unexpected identifier` ==== This week ==== * What I plan to do ** T234610 ERROR webdriver: Request failed due to Error: session not created: Chrome version must be between 70 and 73 ** T199113 All repositories with Selenium tests should use wdio-mediawiki * Blockers ** ==== Other ==== * Saw Rambo: Last Blood. Not recommended. <!-- MEETING TOTAL TIME: 36m 12s --> [[Category:Release Engineering Team checkin archive{{#translation:}}]] hwedh2ly127wqjhunaype3an4zg8vof Wikitext standard/fr 0 1017667 5387871 4771638 2022-07-29T10:33:06Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Historical|1=<span lang="en" dir="ltr" class="mw-content-ltr">Most of the text found on this page was written from 2003-2006.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Wikitext}} for the latest status on wikitext standardization efforts.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> A single '''[[Special:MyLanguage/wikitext|wikitext]] standard''' is of great importance for the long-term stability of the MediaWiki software. We need to describe and formalize a [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] version of the Wikitext language, based on what is used currently. In other words this work should not (for right now) involve incorporating improvements or changes to the Wikitext language. Releases must be stable and predictable so that other software developers can work to the same markup syntax, and know for sure that they will not be facing random or arbitrary changes for some fixed time period, like a year. This suggests there may be [[Special:MyLanguage/wikitext 2005|wikitext 2005]], [[Special:MyLanguage/wikitext 2006|wikitext 2006]] and so on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] was tracking which mediawiki sites are doing what best. Wikipedia won't always be the furthest ahead on an issue, nor should its needs necessarily always trump others in the mediawiki software design effort. For instance [[meta:Wikitravel|Wikitravel]] may do better on geography and [[meta:Spacetime DTD|map]] issues. The first useful map and underlying data standards like an [[meta:Ecoregion DTD|ecoregion DTD]] and [[meta:Spacetime DTD|spacetime DTD]] may be easier to work on there, where these are more central issues. Other subtasks like a [[meta:Person DTD|person DTD]] may become WikiProjects undertaken by a disciplined group of scholars who know, or want to know, everything about documenting people. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Tasks== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> #Write a [[Special:MyLanguage/markup spec|markup spec]] #Write an efficient [[Special:MyLanguage/Alternative parsers|Wikitext to HTML converter]], to replace the current PHP code. #Write a set of unit tests to validate the correctness of a Wikitext to HTML converter. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===XML-Related Tasks=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> #Write a [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]] that can serve as a canonical translation of Wikitext <=> XML, for further processing by XML tools. ''Or use [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. #Write a Wikitext to XML converter. #* Evaluate [http://www.tldp.org/wt2db/ wt2db]. #* Or use [http://schematics.sourceforge.net WebBot], A PLT Scheme package that acts as a Bot on MediaWiki and contains the parser to convert WikiText to the [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Publishing the Standard== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A clear standard can be published and supported by other wikis, like MoinMoinWiki ([[:en:Python_programming_language|python]]-based) and tikiwiki (see [http://tikiwiki.sourceforge.net sourceforge]), which are very popular, and more extensible than mediawiki, which has serious structural problems </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if mediawiki can keep up with those other packages, text import/export has to be one of our priorities, given the objectives of this project to become a central GNU FDL repository of trusted text for use all over the place. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[meta:Wikimedia|Wikimedia]] activities shouldn't be in any way trapped or tied to MediaWiki, if drastically better software emerges from tikiwiki or the Python world. And it will, eventually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Long Term Plans === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> #when things settle down, say [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], then: #create a consortium of all users, developers of various types of software, including [[meta:IRC/Channels|chat]] and [[Special:MyLanguage/email|email]] based systems that incorporate features like [[Special:MyLanguage/Trillian Instant Lookup|Trillian Instant Lookup]] - not all users of Wikipedia use a web browser #agree on a [[meta:Simple ideology of Wikitax|simple ideology of Wikitax]] to make it easy for content generated elsewhere to quickly become wiki pages #develop a unified base boot like KnoppixTiki that supports the new standard so it can be used for any kind of data storage like in a PIM #stabilize and publish something like [[Special:MyLanguage/wikitext 2008|wikitext 2008]] as a real RFC #aim for [[Special:MyLanguage/wikitext 2009|wikitext 2009]] or [[Special:MyLanguage/wikitext 2010|wikitext 2010]] to be an ITU standard </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See also: [[meta:Simple ideology of Wikitax|meta:Simple ideology of Wikitax]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Person DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] </div> [[Category:Wikitext{{#translation:}}]] lekowco5scfrv885gf4fc33rtfq1dh6 Wikitext standard/tr 0 1025491 5387873 3932902 2022-07-29T10:33:09Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Historical|1=Bu sayfada bulunan metnin çoğu 2003-2006 yılları arasında yazılmıştır. Vikimetin standardizasyon çabalarındaki son durum için {{ll|Wikitext}} sayfasına bakın.}} <div class="mw-translate-fuzzy"> Tek bir '''[[Special:MyLanguage/wikitext|vikimetin]] standart''', MediaWiki yazılımının uzun vadeli istikrarı için büyük önem taşımaktadır. Şu anda kullanılana dayanarak, vikimetin dilinin [[meta:WikiReader#Wikipedia_1.0|1.0]] sürümünü tanımlamamız ve resmileştirmemiz gerekiyor. Başka bir deyişle, bu çalışma (şu an için) vikimetin dilinde iyileştirmeler veya değişiklikler yapılmasını içermemelidir. Sürümler kararlı ve öngörülebilir olmalıdır, böylece diğer yazılım geliştiriciler aynı biçimlendirme sözdiziminde çalışabilir ve bir yıl gibi bazı sabit zaman dilimi boyunca rastgele veya rastgele değişikliklerle karşılaşmayacaklarından emin olduklarını bilmelidir. Bu, [[Special:MyLanguage/wikitext 2005|vikimetin 2005]], [[Special:MyLanguage/wikitext 2006|vikimetin 2006]] olduğunu söyleyebilir. </div> [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb], hangi mediawiki sitelerinin en iyisini yaptığını izliyordu. Vikipedi, her zaman bir konuda en ileri konu olmayacak, ihtiyaçları da her zaman mediawiki'nin yazılım tasarım çabalarında başkalarına güvenmemelidir. Örneğin [[meta:Wikitravel|Vikiseyahat]] coğrafya ve [[meta:Spacetime DTD|harita]] konularında daha iyisini yapabilir. İlk kullanışlı harita ve [[meta:Ecoregion DTD|ecoregion DTD]] ve [[meta:Spacetime DTD|zaman boşluğu DTD]] gibi temel veri standartları, bunların daha merkezi konular olduğu yerlerde çalışmak daha kolay olabilir. [[meta:Person DTD|Kişi DTD]] gibi diğer alt görevler, insanları belgelemekle ilgili her şeyi bilen veya bilmek isteyen disiplinli bir alimler grubunun üstlendiği Vikiprojeleri olabilir. == Görevler == <div class="mw-translate-fuzzy"> # [[Special:MyLanguage/markup spec|Biçimlendirme özellikleri]] yazın # Geçerli PHP kodunu değiştirmek için etkili bir [[Special:MyLanguage/Alternative parsers|Vikimetin ile HTML dönüştürücü]] yazın. # Vikimetinden HTML'ye dönüştürücünün doğruluğunu doğrulamak için bir dizi birim sınama yazın. </div> === XML ile İlgili Görevler === <div class="mw-translate-fuzzy"> #XML araçlarıyla daha fazla işlem yapmak için vikimetin <=> XML'nin kanonik bir çevirisi olarak işlev görebilecek [[Special:MyLanguage/Markup spec/DTD|Vikimetin DTD]] yazın. ''Veya [http://schematics.sourceforge.net/wikitext.xsd.zip bu XML Şemasını kullanın]''. # Vikimetin ile XML dönüştürücü yazın. #* [http://www.tldp.org/wt2db/ wt2db] değerini değerlendirin. #* Veya MediaWiki'de Bot işlevi gören ve WikiText'i [http://schematics.sourceforge.net/wikitext.xsd.zip verilen XML Şeması] dosyasına dönüştürmek için ayrıştırıcı içeren bir PLT Şeması paketi olan [http://schematics.sourceforge.net WebBot]'u kullanın. </div> == Standardı Yayınlama == Net bir standart, MoinMoinWiki ([[:tr:Python (programlama dili)|python]] - tabanlı) ve tikiwiki gibi diğer wiki'ler tarafından yayınlanabilir ve desteklenebilir ( [http://tikiwiki.sourceforge.net sourceforge] sayfasına bakın), bunlar çok popüler ve ciddi yapısal sorunları olan mediawiki'den daha genişletilebilir Mediawiki bu diğer paketlere ayak uydurabilse bile, bu projenin amaçları, güvenilir metnin her yerde kullanılmak üzere merkezi bir GNU FDL deposu haline gelmesi göz önüne alındığında, metin alma/verme önceliklerimizden biri olmalıdır. [[meta:Wikimedia|Wikimedia]] etkinlikleri, tikiwiki veya Python dünyasından çok daha iyi bir yazılım ortaya çıkarsa MediaWiki'ye hiçbir şekilde yakalanmamalı veya bağlanmamalıdır. Ve sonunda olacak. === Uzun Vadeli Planlar === #işler düzeldiğinde, [[Special:MyLanguage/wikitext standard 2007|vikimetin standard 2007]] deyin, sonra: #[[meta:IRC/Channels|sohbet]] ve [[Special:MyLanguage/email|e-posta]] tabanlı sistemler [[Special:MyLanguage/Trillian Instant Lookup|Trillian Anında Arama]] - Vikipedi'nin tüm kullanıcıları bir web tarayıcısı kullanmaz #başka bir yerde oluşturulan içeriğin hızlı bir şekilde wiki sayfası olmasını kolaylaştırmak için [[meta:Simple ideology of Wikitax|Wikitax'ın basit ideolojisi]] konusunda anlaşın #yeni standardı destekleyen KnoppixTiki gibi birleşik bir temel önyükleme geliştirin, böylece bir PIM'de olduğu gibi her türlü veri depolama için kullanılabilir #stabilize edin ve [[Special:MyLanguage/wikitext 2008|vikimetin 2008]] gibi bir şeyi gerçek bir RFC olarak yayınlayın #[[Special:MyLanguage/wikitext 2009|vikimetin 2009]] veya [[Special:MyLanguage/wikitext 2010|vikimetin 2010]]'un ITU standardı olmasını hedefleyin Ayrıca bakınız: [[meta:Simple ideology of Wikitax|meta:Wikitax'ın basit ideolojisi]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Kişi DTD]], [[meta:Ecoregion DTD|meta:Ekolojik Bölge DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] la814vbqqdfh9a1uu2db9qqyqsge7ud 5387879 5387873 2022-07-29T10:35:19Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=Bu sayfada bulunan metnin çoğu 2003-2006 yılları arasında yazılmıştır. Vikimetin standardizasyon çabalarındaki son durum için {{ll|Wikitext}} sayfasına bakın.}} Tek bir '''[[Special:MyLanguage/wikitext|vikimetin]] standart''', MediaWiki yazılımının uzun vadeli istikrarı için büyük önem taşımaktadır. Şu anda kullanılana dayanarak, vikimetin dilinin [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] sürümünü tanımlamamız ve resmileştirmemiz gerekiyor. Başka bir deyişle, bu çalışma (şu an için) vikimetin dilinde iyileştirmeler veya değişiklikler yapılmasını içermemelidir. Sürümler kararlı ve öngörülebilir olmalıdır, böylece diğer yazılım geliştiriciler aynı biçimlendirme sözdiziminde çalışabilir ve bir yıl gibi bazı sabit zaman dilimi boyunca rastgele veya rastgele değişikliklerle karşılaşmayacaklarından emin olduklarını bilmelidir. Bu, [[Special:MyLanguage/wikitext 2005|vikimetin 2005]], [[Special:MyLanguage/wikitext 2006|vikimetin 2006]] olduğunu söyleyebilir. [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb], hangi mediawiki sitelerinin en iyisini yaptığını izliyordu. Vikipedi, her zaman bir konuda en ileri konu olmayacak, ihtiyaçları da her zaman mediawiki'nin yazılım tasarım çabalarında başkalarına güvenmemelidir. Örneğin [[meta:Wikitravel|Vikiseyahat]] coğrafya ve [[meta:Spacetime DTD|harita]] konularında daha iyisini yapabilir. İlk kullanışlı harita ve [[meta:Ecoregion DTD|ecoregion DTD]] ve [[meta:Spacetime DTD|zaman boşluğu DTD]] gibi temel veri standartları, bunların daha merkezi konular olduğu yerlerde çalışmak daha kolay olabilir. [[meta:Person DTD|Kişi DTD]] gibi diğer alt görevler, insanları belgelemekle ilgili her şeyi bilen veya bilmek isteyen disiplinli bir alimler grubunun üstlendiği Vikiprojeleri olabilir. == Görevler == <div class="mw-translate-fuzzy"> # [[Special:MyLanguage/markup spec|Biçimlendirme özellikleri]] yazın # Geçerli PHP kodunu değiştirmek için etkili bir [[Special:MyLanguage/Alternative parsers|Vikimetin ile HTML dönüştürücü]] yazın. # Vikimetinden HTML'ye dönüştürücünün doğruluğunu doğrulamak için bir dizi birim sınama yazın. </div> === XML ile İlgili Görevler === <div class="mw-translate-fuzzy"> #XML araçlarıyla daha fazla işlem yapmak için vikimetin <=> XML'nin kanonik bir çevirisi olarak işlev görebilecek [[Special:MyLanguage/Markup spec/DTD|Vikimetin DTD]] yazın. ''Veya [http://schematics.sourceforge.net/wikitext.xsd.zip bu XML Şemasını kullanın]''. # Vikimetin ile XML dönüştürücü yazın. #* [http://www.tldp.org/wt2db/ wt2db] değerini değerlendirin. #* Veya MediaWiki'de Bot işlevi gören ve WikiText'i [http://schematics.sourceforge.net/wikitext.xsd.zip verilen XML Şeması] dosyasına dönüştürmek için ayrıştırıcı içeren bir PLT Şeması paketi olan [http://schematics.sourceforge.net WebBot]'u kullanın. </div> == Standardı Yayınlama == Net bir standart, MoinMoinWiki ([[:tr:Python (programlama dili)|python]] - tabanlı) ve tikiwiki gibi diğer wiki'ler tarafından yayınlanabilir ve desteklenebilir ( [http://tikiwiki.sourceforge.net sourceforge] sayfasına bakın), bunlar çok popüler ve ciddi yapısal sorunları olan mediawiki'den daha genişletilebilir Mediawiki bu diğer paketlere ayak uydurabilse bile, bu projenin amaçları, güvenilir metnin her yerde kullanılmak üzere merkezi bir GNU FDL deposu haline gelmesi göz önüne alındığında, metin alma/verme önceliklerimizden biri olmalıdır. [[meta:Wikimedia|Wikimedia]] etkinlikleri, tikiwiki veya Python dünyasından çok daha iyi bir yazılım ortaya çıkarsa MediaWiki'ye hiçbir şekilde yakalanmamalı veya bağlanmamalıdır. Ve sonunda olacak. === Uzun Vadeli Planlar === #işler düzeldiğinde, [[Special:MyLanguage/wikitext standard 2007|vikimetin standard 2007]] deyin, sonra: #[[meta:IRC/Channels|sohbet]] ve [[Special:MyLanguage/email|e-posta]] tabanlı sistemler [[Special:MyLanguage/Trillian Instant Lookup|Trillian Anında Arama]] - Vikipedi'nin tüm kullanıcıları bir web tarayıcısı kullanmaz #başka bir yerde oluşturulan içeriğin hızlı bir şekilde wiki sayfası olmasını kolaylaştırmak için [[meta:Simple ideology of Wikitax|Wikitax'ın basit ideolojisi]] konusunda anlaşın #yeni standardı destekleyen KnoppixTiki gibi birleşik bir temel önyükleme geliştirin, böylece bir PIM'de olduğu gibi her türlü veri depolama için kullanılabilir #stabilize edin ve [[Special:MyLanguage/wikitext 2008|vikimetin 2008]] gibi bir şeyi gerçek bir RFC olarak yayınlayın #[[Special:MyLanguage/wikitext 2009|vikimetin 2009]] veya [[Special:MyLanguage/wikitext 2010|vikimetin 2010]]'un ITU standardı olmasını hedefleyin Ayrıca bakınız: [[meta:Simple ideology of Wikitax|meta:Wikitax'ın basit ideolojisi]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Kişi DTD]], [[meta:Ecoregion DTD|meta:Ekolojik Bölge DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] 5q5g6kopwzi9w7h225crbnc91p86e4j 5387885 5387879 2022-07-29T10:36:58Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=Bu sayfada bulunan metnin çoğu 2003-2006 yılları arasında yazılmıştır. Vikimetin standardizasyon çabalarındaki son durum için {{ll|Wikitext}} sayfasına bakın.}} Tek bir '''[[Special:MyLanguage/wikitext|vikimetin]] standart''', MediaWiki yazılımının uzun vadeli istikrarı için büyük önem taşımaktadır. Şu anda kullanılana dayanarak, vikimetin dilinin [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] sürümünü tanımlamamız ve resmileştirmemiz gerekiyor. Başka bir deyişle, bu çalışma (şu an için) vikimetin dilinde iyileştirmeler veya değişiklikler yapılmasını içermemelidir. Sürümler kararlı ve öngörülebilir olmalıdır, böylece diğer yazılım geliştiriciler aynı biçimlendirme sözdiziminde çalışabilir ve bir yıl gibi bazı sabit zaman dilimi boyunca rastgele veya rastgele değişikliklerle karşılaşmayacaklarından emin olduklarını bilmelidir. Bu, [[Special:MyLanguage/wikitext 2005|vikimetin 2005]], [[Special:MyLanguage/wikitext 2006|vikimetin 2006]] olduğunu söyleyebilir. [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb], hangi mediawiki sitelerinin en iyisini yaptığını izliyordu. Vikipedi, her zaman bir konuda en ileri konu olmayacak, ihtiyaçları da her zaman mediawiki'nin yazılım tasarım çabalarında başkalarına güvenmemelidir. Örneğin [[meta:Wikitravel|Vikiseyahat]] coğrafya ve [[meta:Spacetime DTD|harita]] konularında daha iyisini yapabilir. İlk kullanışlı harita ve [[meta:Ecoregion DTD|ecoregion DTD]] ve [[meta:Spacetime DTD|zaman boşluğu DTD]] gibi temel veri standartları, bunların daha merkezi konular olduğu yerlerde çalışmak daha kolay olabilir. [[meta:Person DTD|Kişi DTD]] gibi diğer alt görevler, insanları belgelemekle ilgili her şeyi bilen veya bilmek isteyen disiplinli bir alimler grubunun üstlendiği Vikiprojeleri olabilir. == Görevler == # [[Special:MyLanguage/markup spec|Biçimlendirme özellikleri]] yazın # Geçerli PHP kodunu değiştirmek için etkili bir [[Special:MyLanguage/Alternative parsers|Vikimetin ile HTML dönüştürücü]] yazın. # Vikimetinden HTML'ye dönüştürücünün doğruluğunu doğrulamak için bir dizi birim sınama yazın. === XML ile İlgili Görevler === <div class="mw-translate-fuzzy"> #XML araçlarıyla daha fazla işlem yapmak için vikimetin <=> XML'nin kanonik bir çevirisi olarak işlev görebilecek [[Special:MyLanguage/Markup spec/DTD|Vikimetin DTD]] yazın. ''Veya [http://schematics.sourceforge.net/wikitext.xsd.zip bu XML Şemasını kullanın]''. # Vikimetin ile XML dönüştürücü yazın. #* [http://www.tldp.org/wt2db/ wt2db] değerini değerlendirin. #* Veya MediaWiki'de Bot işlevi gören ve WikiText'i [http://schematics.sourceforge.net/wikitext.xsd.zip verilen XML Şeması] dosyasına dönüştürmek için ayrıştırıcı içeren bir PLT Şeması paketi olan [http://schematics.sourceforge.net WebBot]'u kullanın. </div> == Standardı Yayınlama == Net bir standart, MoinMoinWiki ([[:tr:Python (programlama dili)|python]] - tabanlı) ve tikiwiki gibi diğer wiki'ler tarafından yayınlanabilir ve desteklenebilir ( [http://tikiwiki.sourceforge.net sourceforge] sayfasına bakın), bunlar çok popüler ve ciddi yapısal sorunları olan mediawiki'den daha genişletilebilir Mediawiki bu diğer paketlere ayak uydurabilse bile, bu projenin amaçları, güvenilir metnin her yerde kullanılmak üzere merkezi bir GNU FDL deposu haline gelmesi göz önüne alındığında, metin alma/verme önceliklerimizden biri olmalıdır. [[meta:Wikimedia|Wikimedia]] etkinlikleri, tikiwiki veya Python dünyasından çok daha iyi bir yazılım ortaya çıkarsa MediaWiki'ye hiçbir şekilde yakalanmamalı veya bağlanmamalıdır. Ve sonunda olacak. === Uzun Vadeli Planlar === #işler düzeldiğinde, [[Special:MyLanguage/wikitext standard 2007|vikimetin standard 2007]] deyin, sonra: #[[meta:IRC/Channels|sohbet]] ve [[Special:MyLanguage/email|e-posta]] tabanlı sistemler [[Special:MyLanguage/Trillian Instant Lookup|Trillian Anında Arama]] - Vikipedi'nin tüm kullanıcıları bir web tarayıcısı kullanmaz #başka bir yerde oluşturulan içeriğin hızlı bir şekilde wiki sayfası olmasını kolaylaştırmak için [[meta:Simple ideology of Wikitax|Wikitax'ın basit ideolojisi]] konusunda anlaşın #yeni standardı destekleyen KnoppixTiki gibi birleşik bir temel önyükleme geliştirin, böylece bir PIM'de olduğu gibi her türlü veri depolama için kullanılabilir #stabilize edin ve [[Special:MyLanguage/wikitext 2008|vikimetin 2008]] gibi bir şeyi gerçek bir RFC olarak yayınlayın #[[Special:MyLanguage/wikitext 2009|vikimetin 2009]] veya [[Special:MyLanguage/wikitext 2010|vikimetin 2010]]'un ITU standardı olmasını hedefleyin Ayrıca bakınız: [[meta:Simple ideology of Wikitax|meta:Wikitax'ın basit ideolojisi]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Kişi DTD]], [[meta:Ecoregion DTD|meta:Ekolojik Bölge DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] 0yguxcdmmkkqu48p3th16sra04636ph 5387892 5387885 2022-07-29T10:38:49Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=Bu sayfada bulunan metnin çoğu 2003-2006 yılları arasında yazılmıştır. Vikimetin standardizasyon çabalarındaki son durum için {{ll|Wikitext}} sayfasına bakın.}} Tek bir '''[[Special:MyLanguage/wikitext|vikimetin]] standart''', MediaWiki yazılımının uzun vadeli istikrarı için büyük önem taşımaktadır. Şu anda kullanılana dayanarak, vikimetin dilinin [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] sürümünü tanımlamamız ve resmileştirmemiz gerekiyor. Başka bir deyişle, bu çalışma (şu an için) vikimetin dilinde iyileştirmeler veya değişiklikler yapılmasını içermemelidir. Sürümler kararlı ve öngörülebilir olmalıdır, böylece diğer yazılım geliştiriciler aynı biçimlendirme sözdiziminde çalışabilir ve bir yıl gibi bazı sabit zaman dilimi boyunca rastgele veya rastgele değişikliklerle karşılaşmayacaklarından emin olduklarını bilmelidir. Bu, [[Special:MyLanguage/wikitext 2005|vikimetin 2005]], [[Special:MyLanguage/wikitext 2006|vikimetin 2006]] olduğunu söyleyebilir. [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb], hangi mediawiki sitelerinin en iyisini yaptığını izliyordu. Vikipedi, her zaman bir konuda en ileri konu olmayacak, ihtiyaçları da her zaman mediawiki'nin yazılım tasarım çabalarında başkalarına güvenmemelidir. Örneğin [[meta:Wikitravel|Vikiseyahat]] coğrafya ve [[meta:Spacetime DTD|harita]] konularında daha iyisini yapabilir. İlk kullanışlı harita ve [[meta:Ecoregion DTD|ecoregion DTD]] ve [[meta:Spacetime DTD|zaman boşluğu DTD]] gibi temel veri standartları, bunların daha merkezi konular olduğu yerlerde çalışmak daha kolay olabilir. [[meta:Person DTD|Kişi DTD]] gibi diğer alt görevler, insanları belgelemekle ilgili her şeyi bilen veya bilmek isteyen disiplinli bir alimler grubunun üstlendiği Vikiprojeleri olabilir. == Görevler == # [[Special:MyLanguage/markup spec|Biçimlendirme özellikleri]] yazın # Geçerli PHP kodunu değiştirmek için etkili bir [[Special:MyLanguage/Alternative parsers|Vikimetin ile HTML dönüştürücü]] yazın. # Vikimetinden HTML'ye dönüştürücünün doğruluğunu doğrulamak için bir dizi birim sınama yazın. === XML ile İlgili Görevler === #XML araçlarıyla daha fazla işlem yapmak için vikimetin <=> XML'nin kanonik bir çevirisi olarak işlev görebilecek [[Special:MyLanguage/Markup spec/DTD|Vikimetin DTD]] yazın. ''Veya [http://schematics.sourceforge.net/wikitext.xsd.zip bu XML Şemasını kullanın]''. # Vikimetin ile XML dönüştürücü yazın. #* [http://www.tldp.org/wt2db/ wt2db] değerini değerlendirin. #* Veya MediaWiki'de Bot işlevi gören ve WikiText'i [http://schematics.sourceforge.net/wikitext.xsd.zip verilen XML Şeması] dosyasına dönüştürmek için ayrıştırıcı içeren bir PLT Şeması paketi olan [http://schematics.sourceforge.net WebBot]'u kullanın. == Standardı Yayınlama == Net bir standart, MoinMoinWiki ([[:tr:Python (programlama dili)|python]] - tabanlı) ve tikiwiki gibi diğer wiki'ler tarafından yayınlanabilir ve desteklenebilir ( [http://tikiwiki.sourceforge.net sourceforge] sayfasına bakın), bunlar çok popüler ve ciddi yapısal sorunları olan mediawiki'den daha genişletilebilir Mediawiki bu diğer paketlere ayak uydurabilse bile, bu projenin amaçları, güvenilir metnin her yerde kullanılmak üzere merkezi bir GNU FDL deposu haline gelmesi göz önüne alındığında, metin alma/verme önceliklerimizden biri olmalıdır. [[meta:Wikimedia|Wikimedia]] etkinlikleri, tikiwiki veya Python dünyasından çok daha iyi bir yazılım ortaya çıkarsa MediaWiki'ye hiçbir şekilde yakalanmamalı veya bağlanmamalıdır. Ve sonunda olacak. === Uzun Vadeli Planlar === #işler düzeldiğinde, [[Special:MyLanguage/wikitext standard 2007|vikimetin standard 2007]] deyin, sonra: #[[meta:IRC/Channels|sohbet]] ve [[Special:MyLanguage/email|e-posta]] tabanlı sistemler [[Special:MyLanguage/Trillian Instant Lookup|Trillian Anında Arama]] - Vikipedi'nin tüm kullanıcıları bir web tarayıcısı kullanmaz #başka bir yerde oluşturulan içeriğin hızlı bir şekilde wiki sayfası olmasını kolaylaştırmak için [[meta:Simple ideology of Wikitax|Wikitax'ın basit ideolojisi]] konusunda anlaşın #yeni standardı destekleyen KnoppixTiki gibi birleşik bir temel önyükleme geliştirin, böylece bir PIM'de olduğu gibi her türlü veri depolama için kullanılabilir #stabilize edin ve [[Special:MyLanguage/wikitext 2008|vikimetin 2008]] gibi bir şeyi gerçek bir RFC olarak yayınlayın #[[Special:MyLanguage/wikitext 2009|vikimetin 2009]] veya [[Special:MyLanguage/wikitext 2010|vikimetin 2010]]'un ITU standardı olmasını hedefleyin Ayrıca bakınız: [[meta:Simple ideology of Wikitax|meta:Wikitax'ın basit ideolojisi]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|meta:Kişi DTD]], [[meta:Ecoregion DTD|meta:Ekolojik Bölge DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] t3cy3s7fvg9tpy6p9v5l0l28esi4gqn Translations:Wikitext standard/1/tr 1198 1025494 5387878 3932886 2022-07-29T10:35:18Z Shirayuki 472859 update wikitext text/x-wiki Tek bir '''[[$1|vikimetin]] standart''', MediaWiki yazılımının uzun vadeli istikrarı için büyük önem taşımaktadır. Şu anda kullanılana dayanarak, vikimetin dilinin [[$2|1.0]] sürümünü tanımlamamız ve resmileştirmemiz gerekiyor. Başka bir deyişle, bu çalışma (şu an için) vikimetin dilinde iyileştirmeler veya değişiklikler yapılmasını içermemelidir. Sürümler kararlı ve öngörülebilir olmalıdır, böylece diğer yazılım geliştiriciler aynı biçimlendirme sözdiziminde çalışabilir ve bir yıl gibi bazı sabit zaman dilimi boyunca rastgele veya rastgele değişikliklerle karşılaşmayacaklarından emin olduklarını bilmelidir. Bu, [[$3|vikimetin 2005]], [[$4|vikimetin 2006]] olduğunu söyleyebilir. paejgtvwnl4gz4fj17a51ktd6dxbkut Wikimedia Product/lt 0 1025547 5387583 5358200 2022-07-29T03:25:53Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span></span>]] * [[Readers|<span style="color:#2aa198">Skaitytojai</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === Programos === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * Puslapis: [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Puslapis: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * Puslapis: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Puslapis: [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * Puslapis: [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Puslapis: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * Puslapis: [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> Puslapis: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> Puslapis: [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> Puslapis: [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> Puslapis: [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === Vikiduomenys === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * Puslapis: [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Tikslai == {|class="wikitable" |- !scope="row"| 2019-2020 m. | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2017–2018</span> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2016–2017</span> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] ohxf2nb4go88ijaup7em66zhxtxaxrz Manual:Combating spam/pt-br 100 1028368 5387480 5255702 2022-07-28T22:40:21Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Como todos os sites dinâmicos atuais, as wikis são um alvo comum para os spammers que desejam promover produtos ou sites. MediaWiki oferece uma série de recursos destinados a [[Special:MyLanguage/Manual:Combating vandalism|combater o vandalismo em geral]]. Nesta página, tratamos especificamente do [[m:Wiki spam|spam wiki]]. == Visão geral == <div lang="en" dir="ltr" class="mw-content-ltr"> Common tools used to combat wiki spam typically fall into these categories: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Requiring log in and/or a CAPTCHA on certain operations, such as edits, adding external links, or new user creation </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits from known blacklisted IP addresses or IPs running open proxies </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits which add specific unwanted keywords or external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking specific username and page title patterns commonly used by spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits by new or anonymous users to specific often-targeted pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Whitelisting known-good editors (such as admins, regular contributors) while placing restrictions on new or anonymous users </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Cleanup scripts or bulk deletion ({{ll|Extension:Nuke}}) of existing posts from recently-banned spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Note that many of these features are not activated by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</span> <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It helps to raise the bar a little.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> ==As soluções mais rápidas para tentar primeiro== Combater o spam não deve ser muito difícil. Se você quiser reduzir o spam rapidamente e drasticamente, tente estes passos primeiro. * Instale a extensão [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] para bloquear os IPs de spammers conhecidos. <div lang="en" dir="ltr" class="mw-content-ltr"> * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> ==Noções básicas de configuração anti-spam== {{anchor|CAPTCHA}} ===CAPTCHA=== <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * all edits </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * edits adding new, unrecognized external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * user registration </div> <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Individual page protection=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. <div lang="en" dir="ltr" class="mw-content-ltr"> === Abuse filter === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> === Proxies abertos === <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Apache configuration changes === </div> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=Essa técnica em particular aumentará substancialmente o tempo de carregamento da página e o servidor, se a lista de IP for grande. Use com cuidado.}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Other ideas == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==See also== </div> *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. <div lang="en" dir="ltr" class="mw-content-ltr"> === Extensions === </div> *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users <div lang="en" dir="ltr" class="mw-content-ltr"> === Settings === </div> * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External links === </div> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] 226n6qzvvzc44bvtc6xnueud9g49rn6 Translations:Wikitext standard/4/tr 1198 1029520 5387884 3932891 2022-07-29T10:36:57Z Shirayuki 472859 update wikitext text/x-wiki # [[$1|Biçimlendirme özellikleri]] yazın # Geçerli PHP kodunu değiştirmek için etkili bir [[$2|Vikimetin ile HTML dönüştürücü]] yazın. # Vikimetinden HTML'ye dönüştürücünün doğruluğunu doğrulamak için bir dizi birim sınama yazın. 6sbdtx2y64jos8modv6tqkolfi298ij Manual:Installing third-party tools/es 100 1029701 5387821 5377079 2022-07-29T09:28:57Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/es]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/es]] 2gqtb4xa5rfmo3773s65aritcwisa9u Wikimedia Product/tr 0 1030488 5387597 5358217 2022-07-29T03:26:07Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1='''Wikimedia Ürünü''' çalışanları [[foundationsite:role/staff-contractors/|Wikimedia Vakfı tarafından istihdam edilmektedir]] [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sitelerin]] özelliklerini geliştirir ve korur.{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Katkılar</span>]] * [[Readers|<span style="color:#2aa198">Okuyucular</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Ürün Boyunca == * [[Special:MyLanguage/Product Principles|Ürün Prensipleri]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (eski adı: [[Special:MyLanguage/Technical Collaboration Guidance|Teknik İşbirliği Rehberliği]]) * [[Special:MyLanguage/Design/Statement of purpose|Tasarım Amaç Bildirimi]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|Ürünler için veri ve araştırma bilgileri]] * [[Special:MyLanguage/Wikimedia Research/Showcase|Aylık Araştırma Vitrinleri]] === Programlar === * [[m:Special:MyLanguage/Communications/Audience research|Seyirci Araştırması]] * [[m:Special:MyLanguage/Community health initiative|Toplum Sağlığı Girişimi]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|Yeni Editör Deneyimleri]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Yeni Okuyucular]] — İnternet erişiminin hızla büyüdüğü ülkelerdeki potansiyel Wikimedia okuyucularını anlamaya odaklanan devam eden araştırmalar. (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|Commons Hakkında Yapılandırılmış Veriler]] === Proje Sayfaları === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|Yıllık Plan hedefi: Yeni İçerik]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|Gelişmiş Mobil Katkıları]] * [[Special:MyLanguage/Android editing features|Android Düzenleme Özellikleri]] * [[Special:MyLanguage/Content translation/V2|İçerik Çevirisi, V2]] * [[Special:MyLanguage/Growth/Growth team updates|Büyüme]] * [[Special:MyLanguage/Language tools|Çeviri Uzantısını ve Çeviri Wiki sürecini iyileştirin]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|iOS Düzenleme]] * [[Special:MyLanguage/VisualEditor on mobile|Görsel tabanlı mobil düzenleme]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''Yıllık Plan hedefi: Verilerin Daha İyi Kullanımı''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|Verilerin daha iyi kullanımı]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|Veri toplama: Enstrümantasyon]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|Yöneticiliği bildir]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''Yıllık Plan hedefi: Topluluk İstek Listesi''']] * [[m:Special:MyLanguage/Community Tech#Projects|Dilek]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|Daha küçük kullanıcı grupları için destek]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|Program ve etkinlik organizatörleri için teknoloji araçları]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''Yıllık Plan hedefi: Tacizle Mücadele Araçları''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|Raporlama sistemi]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''Yıllık Plan hedefi: Vikiveri''']] '''Diğer:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 Yıllık Pan hedefi: Platform Evrim CDP'si] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|MobileFrontend ve MinervaNeue kullanıcı arabirimi mimarisine yatırım yapın]] ** [[Special:MyLanguage/Parsing/Parser Unification|Ayrıştırıcı birleştirme]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|TemplateStyles]] * [[m:Special:MyLanguage/Movement Organizers|Hareket Organizatörleri Çalışması]] (2019) == Metrikler == [[Special:MyLanguage/Product Analytics|Ürün Analizi]], hareketin sağlığına ilişkin üst düzey bir resim sunmak için tasarlanmış bir dizi önemli metriği izler. [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|Wikimedia hareketinin genel durumunu takip eden temel ölçütlere ilişkin aylık rapor.]] == Ürün ekipleri == Ürün ekibi, belirli kullanıcı akışlarına ve ihtiyaçlarına göre geliştirilmiş bir dizi özelliği kapsar. === Katkılar === Ücretsiz bilgi oluşturmak ve düzenlemek için işbirliğine dayalı, kapsayıcı araçlar geliştiriyoruz. * Phabricator görev panoları: [[phab:tag/contributors-team/|#Contributors-Team]] (nadiren kullanılmış) * Sayfa: [[Special:MyLanguage/Contributors|Katkılar]] * Ekipler: ====== Taciz Önleme Araçları ====== * Phabricator görev panosu: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Sayfa: [[Special:MyLanguage/Anti-Harassment Tools|Taciz Önleme Araçları]] ====== Topluluk Teknolojisi ====== * [[phab:project/board/1274/|Phabricator panosu]] * Sayfa: [[m:Special:MyLanguage/Community Tech|Topluluk Teknolojisi]] ====== Düzenleme ====== * Phabricator görev panoları: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Sayfa: [[Special:MyLanguage/Editing team|Ekibi düzenleme]] ====== Büyüme ====== * Phabricator görev panosu: [[phab:project/board/1114/|#Growth-Team]] * Sayfa: [[Special:MyLanguage/Growth|Büyüme]] ====== Dil ====== * Phabricator görev panosu: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Sayfa: [[Special:MyLanguage/Wikimedia Language engineering|Wikimedia Dil mühendisliği]] === Okuyucular === Tüm bilgilerin toplamı için istisnai öğrenme ve okuma deneyimleri geliştiriyoruz. * Sayfa: [[Special:MyLanguage/Readers|Okuyucular]] * Phabricator görev panosu: [https://phabricator.wikimedia.org/tag/reading/ #reading] * Ekipler: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|iOS]] ====== ====== [[Special:MyLanguage/Parsing|Ayrıştırma]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|Ürün Altyapısı]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|Web]] ====== * [[Reading/Component responsibility|Kod sorumluluğunu okuma]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|Aylık sayfa görüntüleme sayısı, Mayıs 2013–Ocak 2019. File:Wikimedia pageviews year-over-year comparison (since May 2013).png|Yıl bazında karşılaştırmada toplam sayfa görüntüleme sayısı, Mayıs 2013–Şubat 2019. File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|Yıl bazında karşılaştırmada masaüstü sayfa görüntülemeleri, Mayıs 2013–Şubat 2019. File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|Yıl bazında karşılaştırmada mobil sayfa görüntülemeleri, Mayıs 2013–Şubat 2019. </gallery> === Teknik Program Yönetimi === Teslimat süreçlerini yönlendirmeye ve iyi uygulamalarla ekip sağlığını kolaylaştırmaya adadık. Sayfa: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|Teknik Program Yönetimi]] Öncülük etme: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === Ürün Tasarımı === Tüm insan bilgilerinin paylaşımını kolay ve eğlenceli hale getiriyoruz. Herkes için. Sayfa: [[Special:MyLanguage/Design#Product Design|Ürün Tasarımı]] Yönetmen: [[User:MNovotny_(WMF)|Margeigh Novotny]] === Ürün Analizi === Analiz sonuçlarına dayanarak önerilerde bulunur, etik veri uygulamalarını savunur ve veri ve istatistiklerle ilgili konularda eğitim veririz. Sayfa: [[Special:MyLanguage/Product Analytics|Ürün Analizi]] Öncülük etme: Kate Zimmerman === Ürün Tasarım Stratejisi === <!--''[buraya giriş metni]''--> Sayfa: [[Special:MyLanguage/Design#Design Strategy|Ürün Tasarım Stratejisi]] Öncülük etme: Margeigh Novotny === Vikiveri === Vikiveri, hem insanlar hem de makineler tarafından okunabilen ve düzenlenebilen ücretsiz ve açık bir bilgi tabanıdır. Bu proje [[WMDE Engineering|Wikimedia Deutschland]]'daki Yazılım Geliştirme ve Mühendislik bölümü tarafından yürütülmektedir. * Sayfa: [[d:Wikidata:Main Page|Wikidata]] * Öncülük etme: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Phabricator hataları ve görev panosu: [[phab:project/profile/71/|#wikidata]] * Tartışma Listesi: wikidata@lists.wikimedia.org {|class="wikitable" |+ Vikiveri Ekip Hedefleri |- !scope="row"| WMDE Mali Yılı 2017 | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Q1: Ocak–Mart 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Q2: Nisan–Haziran] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Q3: Temmuz–Eylül] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Q4: Ekim–Aralık] |- !scope="row"| WMDE Mali Yılı 2016 | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Q1: Ocak–Mart 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q2: Nisan–Haziran] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q3: Temmuz–Eylül] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q4: Ekim–Aralık] |} == Hedefler == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: Temmuz–Eylül 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: Ekim–Aralık 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: Ocak–Mart 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: Nisan–Haziran 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: Temmuz–Eylül 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: Ekim–Aralık 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: Ocak–Mart 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: Nisan–Haziran 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: Temmuz–Eylül 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: Ekim–Aralık 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: Ocak–Mart 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: Nisan–Haziran 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: Temmuz–Eylül 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: Ekim–Aralık 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: Ocak–Mart 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: Nisan–Haziran 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: Temmuz–Eylül 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: Ekim–Aralık 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: Ocak–Mart 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: Nisan–Haziran 2016]] |} == Yıllık Yol Haritası == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|2018–2019 Ürün Yıllık Planı]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|2017–2018 Ürün Yıllık Planı]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|2016–2017 Ürün Yıllık Planı]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|2016 Ürün Özeti]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|2015 Ürün ve Teknoloji İncelemesi]] [[Category:WMF Projects{{#translation:}}]] 9re2qw6fgzpox2avyi50lqf3t29mv4k Translations:Wikitext standard/6/tr 1198 1030680 5387891 3932893 2022-07-29T10:38:48Z Shirayuki 472859 update wikitext text/x-wiki #XML araçlarıyla daha fazla işlem yapmak için vikimetin <=> XML'nin kanonik bir çevirisi olarak işlev görebilecek [[$1|Vikimetin DTD]] yazın. ''Veya [http://schematics.sourceforge.net/wikitext.xsd.zip bu XML Şemasını kullanın]''. # Vikimetin ile XML dönüştürücü yazın. #* [http://www.tldp.org/wt2db/ wt2db] değerini değerlendirin. #* Veya MediaWiki'de Bot işlevi gören ve WikiText'i [http://schematics.sourceforge.net/wikitext.xsd.zip verilen XML Şeması] dosyasına dönüştürmek için ayrıştırıcı içeren bir PLT Şeması paketi olan [http://schematics.sourceforge.net WebBot]'u kullanın. 63vuhvhkzq3zbg4kttiip7ows79ix9c Wikimedia Product/vec 0 1036357 5387599 5358218 2022-07-29T03:26:07Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=El staff '''Prodoto Wikimedia''' [[foundationsite:role/staff-contractors/|tolto sù da la fondasion Wikimedia]] costruise, mejora e mantien le funsionalità dei [[m:Special:MyLanguage/Wikimedia projects|siti Wikimedia]].{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">contribudori</span>]] * [[Readers|<span style="color:#2aa198">Letori</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Obietivi == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: lulio–Setenbre 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: Otobre–Diçenbre 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: Xenaro-marso 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: April–Jugno 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: lulio–Setenbre 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: Otobre–Diçenbre 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: Xenaro-marso 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: April–Jugno 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: lulio–Setenbre 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: Otobre–Diçenbre 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: Xenaro-marso 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: April–Jugno 2018]] |- !scope="row"| 2016-2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: lulio–Setenbre 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: Otobre–Diçenbre 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: Xenaro-marso 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: April–Jugno 2017]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] mz7x85d16r5lsbr4zakgb1wyyizpuug Extension:EventLogging/en 102 1040284 5387146 5381728 2022-07-28T21:07:42Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = Provides a framework for logging analytics events |version = continuous updates |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. == Features == * EventLogging supports client-side logging from JavaScript and server-side logging from PHP. * Logging behavior can be dynamically configured using {{ll|Extension:EventStreamConfig}}. * The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository. * The extension does not include any back-end code for transporting, parsing, or loading these events. A separate service, [[wikitech:Event Platform/EventGate|EventGate]], implements this functionality and deals with inserting events into Kafka. Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines. The details of these components are specific to Wikimedia Foundation's configuration. == EventLogging at Wikimedia == The Wikimedia Foundation uses the EventLogging extension as part of a [[wikitech:Analytics/Systems/EventLogging|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[m:Special:MyLanguage/Privacy policy|privacy policy]] and [[m:Special:MyLanguage/Data retention guidelines|data retention guidelines]]. This page is about general use of the EventLogging extension. The Wikimedia Foundation uses EventLogging with WMF specific backend components and [https://schema.wikimedia.org/#!/ schema repositories]. For Wikimedia specific and maintained documentation, see [[wikitech:Analytics/Systems/EventLogging]] and [[wikitech:Event Platform]]. ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} === Configuring the schema location === By default, the extension will look for schemas on [[m:Special:MyLanguage/Meta-Wiki|Meta-Wiki]]. The relevant default settings are: <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these. E.g. to use the <code>Schema</code> namespace of the local wiki, set <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> (and ensure the user account that will create the schemas is [[Special:MyLanguage/Manual:Autoconfirmed users|autoconfirmed]]). == Logging events using EventLogging == * {{ll|Extension:EventLogging/Guide}} - to developing and deploying EventLogging schemas, and more * {{ll|Extension:EventLogging/Programming}} - tips and suggestions for developers writing code to log events == Developing the EventLogging extension == === Developer setup === As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. ==== Using Docker ==== ''See {{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}'' ==== Using mediawiki-vagrant ==== If you develop using mediawiki-vagrant, everything you need is encapsulated in the <code>eventlogging</code> role. To enable it, run: <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> ==== For JavaScript development ==== If working on the JavaScript client, you'll need to install dependencies with <code>npm install</code> from the folder you're developing in. Then you can use <code>npm test</code> to run ESLint for example. The "How to run tests" section below points out how to see JavaScript test results. When adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered. ==== How to run tests ==== There are PHP tests, Python tests, and JavaScript tests. To run JavaScript tests, visit Special:JavaScriptTest/qunit on your development wiki. (See {{ll|Manual:JavaScript unit testing}}.) To run PHP tests, we use PHPUnit. Make sure it is installed, then: <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] nt27ft7myqnmjkuo39768ieiiillwha Manual:Installing MediaWiki/de-formal 100 1042192 5387493 5384966 2022-07-28T22:45:18Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span class="mw-translate-fuzzy">Die Installation von MediaWiki kann für den durchschnittlichen Computeranwender schwierig werden, der keine Erfahrung mit Apache, PHP und MySQL/MariaDB hat.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Herunterladen der MediaWiki-Software == Laden Sie die tar-Datei zu MediaWiki von der [[Special:MyLanguage/Download|offiziellen Download-Seite]] herunter. Generell gilt: Wenn Sie eine Produktionsumgebung verwenden, sollten Sie die letzte stabile Version verwenden, also MediaWiki {{MW stable release number}}. <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span class="mw-translate-fuzzy">Die heruntergeladenen Dateien liegen im <code>.tar.gz</code>-Format vor, sodass sie vor der Verwendung entpackt werden müssen.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span class="mw-translate-fuzzy">Entpacken Sie die Dateien lokal oder auf Ihrem Server.</span> Unter Windows werden dafür gewöhnlich Programme wie [https://www.7-zip.org/ 7-Zip] (quelltextoffene Software), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] oder [https://www.izarc.org/ IZArc] benutzt. Unter Linux und Mac OS X können Sie die Datei entpacken (untar), indem Sie folgenden Befehl anwenden: <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==Dateien auf den Server hochladen== <div class="mw-translate-fuzzy"> Wenn Sie die Dateien noch nicht auf Ihren Webserver hochgeladen haben, tun Sie dies jetzt. </div> Laden Sie die Dateien in das Webverzeichnis Ihres Webservers hoch, in dem Sie entweder: # das entpackte Verzeichnis direkt kopieren oder <div class="mw-translate-fuzzy"> # einen FTP-Clienten wie [https://filezilla-project.org/ FileZilla] (Open Source Software, Windows, OSX und Linux) oder [https://cyberduck.io/ Cyberduck] (OSX) nutzen. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> Wenn Ihr Kopier- oder FTP-Programm eine Option zur Umwandlung des Dateinamens in Kleinbuchstaben hat (change file names to lowercase), müssen Sie diese ausschalten. <span class="mw-translate-fuzzy">Wenn Sie Apache installiert haben, steht das korrekte Verzeichnis in Ihrer <code>httpd.conf</code>-Datei (es ist die [$docroot DocumentRoot]-Richtlinie, normalerweise <code>/var/www/</code> oder <code>&lt;apache-folder>/htdocs</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span class="mw-translate-fuzzy">Hinweis: Dies änderte sich in Ubuntu 14.04 mit Apache 2.4.7, wo die ursprüngliche Konfigurationsdatei für Apache-Server-Einstellungen und Verzeichnisse <code>/etc/apache2/apache2.conf</code> ist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> Benennen Sie den hochgeladenen Ordner (oder den symbolischen Link) so um, wie Sie ihn in der URL haben wollen. <span class="mw-translate-fuzzy">Wenn Ihr Web-Server z.&nbsp;B. wie <code>http://localhost</code> läuft, würde eine Umbenennung zu einem <code>/w/</code>-Verzeichnis bedeuten, dass Sie Ihr Wiki über <code>http://localhost/w/index.php</code> erreichen.</span> {{Note|1=<span class="mw-translate-fuzzy">'''''Benutzen Sie nicht <code>/wiki/</code>, wenn Sie es als einen [[Special:MyLanguage/Manual:Short URL|Kurzlink]] benutzen möchten.'''''</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Eine Datenbank erstellen == </div> <div class="mw-translate-fuzzy"> MediaWiki wird Sie nach der Datenbank und dem Benutzernamen fragen und versuchen, diese zu erstellen, falls sie noch nicht vorhanden sind. </div> <div class="mw-translate-fuzzy"> Sofern Sie das root-Passwort in Ihrer Datenbank kennen, kann das Installationsprogramm von MediaWiki eine Datenbank für Sie erstellen. </div> <div class="mw-translate-fuzzy"> Wenn Sie das root-Passwort nicht kennen, z.&nbsp;B. wenn Sie auf einem gemieteten Server sind, müssen Sie eine neue Datenbank erzeugen. </div> <span class="mw-translate-fuzzy">Derzeit müssen Sie entweder MariaDB/MySQL oder Postgres benutzen, um die aktuellen Inhalte des Wikis zu speichern.</span> <span class="mw-translate-fuzzy">Wenn Sie sich nicht sicher sind, welche Datenbank Sie auswählen sollen, benutzen Sie MariaDB, da dies am besten von MediaWiki unterstützt wird.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span class="mw-translate-fuzzy">Auf der Installationsseite müssen Sie einen Datenbanknamen (welcher alles sein kann) und das SQLite-Datenbankverzeichnis angeben.</span> Wenn Ihre Datenbank nicht auf dem gleichen Server wie Ihr Webserver läuft, müssen Sie den zugehörigen Webserverhostnamen &mdash; im folgenden Beispiel ''mediawiki.example.com'' &mdash; wie folgt eingeben: Wenn dieses Verzeichnis nicht sicher ist (z.&nbsp;B. für das Web lesbar), dann sollten Sie es manuell ändern, damit es nicht für das gesamte Web zugänglich ist. ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span class="mw-translate-fuzzy">Bitte lesen Sie die entsprechende Dokumentation.</span> <span class="mw-translate-fuzzy">Alternativ kann auch der Host-Provider ein Konto für Sie einrichten.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div class="mw-translate-fuzzy"> Wenn Ihre Datenbank nicht auf dem gleichen Server wie Ihr Webserver läuft, müssen Sie den zugehörigen Webserverhostnamen – im folgenden Beispiel ''mediawiki.example.com'' – wie folgt eingeben: </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span class="mw-translate-fuzzy">MySQL/MariaDB unter UNIX/Linux protokolliert alle Abfragen, die an die Datenbank gesendet werden, in einer Datei, die auch das Passwort enthält, das für das Benutzerkonto verwendet wird.</span> <span class="mw-translate-fuzzy">Wenn Sie Bedenken haben, löschen Sie Ihre <code>.mysql_history</code>-Datei, nachdem Sie diese Abfragen ausgeführt haben.</span>}} ===PostgreSQL=== <span class="mw-translate-fuzzy">Wenn Sie PostgreSQL verwenden, müssen Sie entweder eine Datenbank und einen Benutzer für sich anlegen lassen oder einfach den Namen eines PostgreSQL-Benutzers mit „Superuser“-Rechten in das Konfigurationsformular eingeben.</span> <span class="mw-translate-fuzzy">Dieser Datenbankbenutzer wird häufig '''postgres''' genannt.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (geben Sie dann das Passwort ein) createdb -O wikiuser my_wiki oder Sie geben, als Superuser (standardmäßig „postgres“), die folgenden Befehle in die Datenbank-Eingabezeile ein: <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> '''Achtung:''' die [[phab:tag/postgreSQL|Liste bekannter Probleme beim Betrieb von MediaWiki mit PostgreSQL]] sollte beachtet werden. {{anchor|Run the installation script}} == Das Installationsskript ausführen == <div class="mw-translate-fuzzy"> Wenn alle oben genannten Schritte abgeschlossen sind, kann die Installation über einen Webbrowser abgeschlossen werden, indem die URL der index.php im Browser aufgerufen wird – bitte die in {{ll|Manual:Config script}} beschriebenen Anweisungen beachten. </div> <div class="mw-translate-fuzzy"> == Nächste Schritte == </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Auf dem Laufenden bleiben == Nach der Installation stellen Sie sicher, dass Sie mit den Versionen auf dem neuesten Stand bleiben und halten Sie Ihren Server sicher! {{Clickable button 2|<span class="mw-translate-fuzzy">[[$maillist|Abonnieren Sie unsere Mailingliste über Mitteilungen zu Versionsankündigungen.]]</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Siehe auch == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] fqz5ihkqyzci6euoe77kciwr2k0y6lv Wikimedia Technical Engagement/Workshops and talks 0 1050288 5386204 5360815 2022-07-28T12:08:32Z SSapaty (WMF) 17561895 Added slides on Pywikibot Intro presentation at African Wikimedia Technical Community wikitext text/x-wiki ==2022== * [[c:File:Tricia_Burmeister_-_Documentation_to_Conquer_the_Dungeon_-_Wikimedia_Hackathon_2022.pdf|Documentation to Conquer the Dungeon]] (Slides), Wikimedia Hackathon * [[c:File:Publicize_your_tools_and_find_new_tools_(Toolhub,_wmhack_2022).pdf|Publicize your tools and find new tools with Toolhub]] (Slides), Wikimedia Hackathon *[[File:Intro To Pywikibot - AWMT Community.pdf|thumb|Intro To Pywikibot - AWMT Community]] (Slides), African Wikimedia Technical Community Hackathon ==2021== * [[c:File:How_to_find_tools_to_improve_your_workflows_(Toolhub,_Wikimania_2021).pdf|How to find tools to improve your workflows]] (Slides), Wikimania * [[phab:T287761|How can we improve Quarry and Paws to help developers in their journey?]] ([https://etherpad.wikimedia.org/p/Wikimania-2021-PAWS-and-Quarry-discussion Notes]), Wikimania Hackathon * [https://www.youtube.com/watch?v=BSNuwjnA1qk Wikimedia Toolforge, plataforma basada en Kubernetes] (Video), Kubernetes Community Days Spain * [[phab:T282265|Finding co-maintainers for your tools]] ([https://etherpad.wikimedia.org/p/wmhack21-finding-comaintainers Notes]), Wikimedia Hackathon * [[c:File:Where_can_I_run_this_An_Introduction_to_Wikimedia_Cloud_Services_-_wmhack_2021.pdf|Where can I run this? An introduction to Cloud Services]] (Slides), Wikimedia Hackathon * [[c:File:Intro_to_Toolhub_for_tool_maintainers_(wmhack_2021).pdf|Intro to Toolhub for tool maintainers]] (Slides), Wikimedia Hackathon * [[c:File:A_central_place_to_link_key_technical_documents_(wmhack_2021).pdf|A central place to link key technical documents]] (Slides), Wikimedia Hackathon ==2020== * [[c:File:Tips_for_a_successful_Outreachy_application_%26_internship_project.pdf|Tips for a successful Outreachy application and internship project]] (Slides), [https://www.shecodeafrica.org/ She Code Africa] ==2019== * [[c:File:Developer_Productivity_and_onwiki_tooling_-_Wikimedia_Technical_Conference_2019.pdf|Developer Productivity and onwiki tooling]] (Slides, [[Phab:T234661|Notes]]), Wikimedia Technical Conference * [[Phab:T234657|Platform Stewardship]] (Notes), Wikimedia Technical Conference * [[Phab:T234634|Onwiki documentation and documentation as code: strengths, weaknesses, and compromises]] (Notes), Wikimedia Technical Conference * [[Phab:T234660|Code Health/Code Review]] (Notes), Wikimedia Technical Conference * [[Phab:T238262|What is a technical contribution?]] (Notes), Wikimedia Technical Conference * [[c:File:Developing community norms for critical bots and tools, Wikimania 2019.webm|Developing community norms for critical bots and tools]] (Video), Wikimania ([[c:File:Developing_community_norms_for_critical_bots_and_tools,_Wikimania_2019_(with_speaker_notes).pdf|slides with speaker notes]]) * [[c:File:Introduction-to-Phabricator-WikiCon-2016.pdf|Basic Introduction to Phabricator]] (Slides), Wikimania Hackathon * [[c:File:Wikimedia_APIs.pdf|Wikimedia APIs workshop]] (Slides), Wikimania Hackathon * [[c:File:Userscript_and_Gadgets_workshop_toolkit.pdf|User Scripts & Gadgets workshop]] (Slides), Wikimania Hackathon * [[c:File:Introduction_to_Wikimedia_Cloud_Services_-_Wikimania_Hackathon_2019_Stockholm_Sweden.pdf|Introduction to Wikimedia Cloud Services]] (Slides), Wikimania Hackathon * [https://media.ccc.de/v/36c3-89-measuring-code-contributions-in-wikimedia-s-technical-community Measuring Code Contributions in Wikimedia's Technical Community] (Video), Chaos Communication Congress * [https://media.ccc.de/v/36c3-88-software-tools-for-wikis-beyond-mediawiki-and-its-extensions Software tools for wikis beyond MediaWiki and its extensions: A remix of the Wikimania 2019 Coolest Tool Awards session] (Video), Chaos Communication Congress * [https://media.libreplanet.org/u/libreplanet/m/sharing-global-opportunities-for-new-developers-in-the-wikipedia-community-slides/ Sharing global opportunities for new developers in the Wikipedia community] (Slides), Libre Planet ==Timeless classics and workshop series== In collaboration with many others: * [[m:Coolest Tool Award|Coolest Tool Award]] - features the coolest tools since 2019. Award ceremony includes tool demos. * [[m:Small_wiki_toolkits|Small Wiki Toollkits]] - local, regional and global technical workshops for smaller wiki communities since 2019. Frequently given sessions: * Ask anything about Phabricator - [[phab:T304160|example]] * Technical Development Statistics (Git and Gerrit) - [[phab:T281814|example]] * Wikimedia Cloud Services Introduction (see the most recent one above for the latest version) k3x567hvl4qcq86ecr5tnyru9dya5e6 5386209 5386204 2022-07-28T12:10:23Z SSapaty (WMF) 17561895 wikitext text/x-wiki ==2022== * [[c:File:Tricia_Burmeister_-_Documentation_to_Conquer_the_Dungeon_-_Wikimedia_Hackathon_2022.pdf|Documentation to Conquer the Dungeon]] (Slides), Wikimedia Hackathon * [[c:File:Publicize_your_tools_and_find_new_tools_(Toolhub,_wmhack_2022).pdf|Publicize your tools and find new tools with Toolhub]] (Slides), Wikimedia Hackathon * [[c:File:Intro To Pywikibot - AWMT Community.pdf|Intro To Pywikibot - AWMT Community]] (Slides), African Wikimedia Technical Community Hackathon ==2021== * [[c:File:How_to_find_tools_to_improve_your_workflows_(Toolhub,_Wikimania_2021).pdf|How to find tools to improve your workflows]] (Slides), Wikimania * [[phab:T287761|How can we improve Quarry and Paws to help developers in their journey?]] ([https://etherpad.wikimedia.org/p/Wikimania-2021-PAWS-and-Quarry-discussion Notes]), Wikimania Hackathon * [https://www.youtube.com/watch?v=BSNuwjnA1qk Wikimedia Toolforge, plataforma basada en Kubernetes] (Video), Kubernetes Community Days Spain * [[phab:T282265|Finding co-maintainers for your tools]] ([https://etherpad.wikimedia.org/p/wmhack21-finding-comaintainers Notes]), Wikimedia Hackathon * [[c:File:Where_can_I_run_this_An_Introduction_to_Wikimedia_Cloud_Services_-_wmhack_2021.pdf|Where can I run this? An introduction to Cloud Services]] (Slides), Wikimedia Hackathon * [[c:File:Intro_to_Toolhub_for_tool_maintainers_(wmhack_2021).pdf|Intro to Toolhub for tool maintainers]] (Slides), Wikimedia Hackathon * [[c:File:A_central_place_to_link_key_technical_documents_(wmhack_2021).pdf|A central place to link key technical documents]] (Slides), Wikimedia Hackathon ==2020== * [[c:File:Tips_for_a_successful_Outreachy_application_%26_internship_project.pdf|Tips for a successful Outreachy application and internship project]] (Slides), [https://www.shecodeafrica.org/ She Code Africa] ==2019== * [[c:File:Developer_Productivity_and_onwiki_tooling_-_Wikimedia_Technical_Conference_2019.pdf|Developer Productivity and onwiki tooling]] (Slides, [[Phab:T234661|Notes]]), Wikimedia Technical Conference * [[Phab:T234657|Platform Stewardship]] (Notes), Wikimedia Technical Conference * [[Phab:T234634|Onwiki documentation and documentation as code: strengths, weaknesses, and compromises]] (Notes), Wikimedia Technical Conference * [[Phab:T234660|Code Health/Code Review]] (Notes), Wikimedia Technical Conference * [[Phab:T238262|What is a technical contribution?]] (Notes), Wikimedia Technical Conference * [[c:File:Developing community norms for critical bots and tools, Wikimania 2019.webm|Developing community norms for critical bots and tools]] (Video), Wikimania ([[c:File:Developing_community_norms_for_critical_bots_and_tools,_Wikimania_2019_(with_speaker_notes).pdf|slides with speaker notes]]) * [[c:File:Introduction-to-Phabricator-WikiCon-2016.pdf|Basic Introduction to Phabricator]] (Slides), Wikimania Hackathon * [[c:File:Wikimedia_APIs.pdf|Wikimedia APIs workshop]] (Slides), Wikimania Hackathon * [[c:File:Userscript_and_Gadgets_workshop_toolkit.pdf|User Scripts & Gadgets workshop]] (Slides), Wikimania Hackathon * [[c:File:Introduction_to_Wikimedia_Cloud_Services_-_Wikimania_Hackathon_2019_Stockholm_Sweden.pdf|Introduction to Wikimedia Cloud Services]] (Slides), Wikimania Hackathon * [https://media.ccc.de/v/36c3-89-measuring-code-contributions-in-wikimedia-s-technical-community Measuring Code Contributions in Wikimedia's Technical Community] (Video), Chaos Communication Congress * [https://media.ccc.de/v/36c3-88-software-tools-for-wikis-beyond-mediawiki-and-its-extensions Software tools for wikis beyond MediaWiki and its extensions: A remix of the Wikimania 2019 Coolest Tool Awards session] (Video), Chaos Communication Congress * [https://media.libreplanet.org/u/libreplanet/m/sharing-global-opportunities-for-new-developers-in-the-wikipedia-community-slides/ Sharing global opportunities for new developers in the Wikipedia community] (Slides), Libre Planet ==Timeless classics and workshop series== In collaboration with many others: * [[m:Coolest Tool Award|Coolest Tool Award]] - features the coolest tools since 2019. Award ceremony includes tool demos. * [[m:Small_wiki_toolkits|Small Wiki Toollkits]] - local, regional and global technical workshops for smaller wiki communities since 2019. Frequently given sessions: * Ask anything about Phabricator - [[phab:T304160|example]] * Technical Development Statistics (Git and Gerrit) - [[phab:T281814|example]] * Wikimedia Cloud Services Introduction (see the most recent one above for the latest version) cxfdhvbts35ch5a5y4b9dwpnevrqz49 5386565 5386209 2022-07-28T15:23:09Z SSapaty (WMF) 17561895 wikitext text/x-wiki ==2022== * [[c:File:Tricia_Burmeister_-_Documentation_to_Conquer_the_Dungeon_-_Wikimedia_Hackathon_2022.pdf|Documentation to Conquer the Dungeon]] (Slides), Wikimedia Hackathon * [[c:File:Publicize_your_tools_and_find_new_tools_(Toolhub,_wmhack_2022).pdf|Publicize your tools and find new tools with Toolhub]] (Slides), Wikimedia Hackathon * [[c:File:Intro To Pywikibot - AWMT Community.pdf|Intro To Pywikibot - AWMT Community]] (Slides), [[Open_Foundation_West_Africa_Community_Hackathon_2022/Schedule|African Wikimedia Technical Community Hackathon]] ==2021== * [[c:File:How_to_find_tools_to_improve_your_workflows_(Toolhub,_Wikimania_2021).pdf|How to find tools to improve your workflows]] (Slides), Wikimania * [[phab:T287761|How can we improve Quarry and Paws to help developers in their journey?]] ([https://etherpad.wikimedia.org/p/Wikimania-2021-PAWS-and-Quarry-discussion Notes]), Wikimania Hackathon * [https://www.youtube.com/watch?v=BSNuwjnA1qk Wikimedia Toolforge, plataforma basada en Kubernetes] (Video), Kubernetes Community Days Spain * [[phab:T282265|Finding co-maintainers for your tools]] ([https://etherpad.wikimedia.org/p/wmhack21-finding-comaintainers Notes]), Wikimedia Hackathon * [[c:File:Where_can_I_run_this_An_Introduction_to_Wikimedia_Cloud_Services_-_wmhack_2021.pdf|Where can I run this? An introduction to Cloud Services]] (Slides), Wikimedia Hackathon * [[c:File:Intro_to_Toolhub_for_tool_maintainers_(wmhack_2021).pdf|Intro to Toolhub for tool maintainers]] (Slides), Wikimedia Hackathon * [[c:File:A_central_place_to_link_key_technical_documents_(wmhack_2021).pdf|A central place to link key technical documents]] (Slides), Wikimedia Hackathon ==2020== * [[c:File:Tips_for_a_successful_Outreachy_application_%26_internship_project.pdf|Tips for a successful Outreachy application and internship project]] (Slides), [https://www.shecodeafrica.org/ She Code Africa] ==2019== * [[c:File:Developer_Productivity_and_onwiki_tooling_-_Wikimedia_Technical_Conference_2019.pdf|Developer Productivity and onwiki tooling]] (Slides, [[Phab:T234661|Notes]]), Wikimedia Technical Conference * [[Phab:T234657|Platform Stewardship]] (Notes), Wikimedia Technical Conference * [[Phab:T234634|Onwiki documentation and documentation as code: strengths, weaknesses, and compromises]] (Notes), Wikimedia Technical Conference * [[Phab:T234660|Code Health/Code Review]] (Notes), Wikimedia Technical Conference * [[Phab:T238262|What is a technical contribution?]] (Notes), Wikimedia Technical Conference * [[c:File:Developing community norms for critical bots and tools, Wikimania 2019.webm|Developing community norms for critical bots and tools]] (Video), Wikimania ([[c:File:Developing_community_norms_for_critical_bots_and_tools,_Wikimania_2019_(with_speaker_notes).pdf|slides with speaker notes]]) * [[c:File:Introduction-to-Phabricator-WikiCon-2016.pdf|Basic Introduction to Phabricator]] (Slides), Wikimania Hackathon * [[c:File:Wikimedia_APIs.pdf|Wikimedia APIs workshop]] (Slides), Wikimania Hackathon * [[c:File:Userscript_and_Gadgets_workshop_toolkit.pdf|User Scripts & Gadgets workshop]] (Slides), Wikimania Hackathon * [[c:File:Introduction_to_Wikimedia_Cloud_Services_-_Wikimania_Hackathon_2019_Stockholm_Sweden.pdf|Introduction to Wikimedia Cloud Services]] (Slides), Wikimania Hackathon * [https://media.ccc.de/v/36c3-89-measuring-code-contributions-in-wikimedia-s-technical-community Measuring Code Contributions in Wikimedia's Technical Community] (Video), Chaos Communication Congress * [https://media.ccc.de/v/36c3-88-software-tools-for-wikis-beyond-mediawiki-and-its-extensions Software tools for wikis beyond MediaWiki and its extensions: A remix of the Wikimania 2019 Coolest Tool Awards session] (Video), Chaos Communication Congress * [https://media.libreplanet.org/u/libreplanet/m/sharing-global-opportunities-for-new-developers-in-the-wikipedia-community-slides/ Sharing global opportunities for new developers in the Wikipedia community] (Slides), Libre Planet ==Timeless classics and workshop series== In collaboration with many others: * [[m:Coolest Tool Award|Coolest Tool Award]] - features the coolest tools since 2019. Award ceremony includes tool demos. * [[m:Small_wiki_toolkits|Small Wiki Toollkits]] - local, regional and global technical workshops for smaller wiki communities since 2019. Frequently given sessions: * Ask anything about Phabricator - [[phab:T304160|example]] * Technical Development Statistics (Git and Gerrit) - [[phab:T281814|example]] * Wikimedia Cloud Services Introduction (see the most recent one above for the latest version) to8r1ie7403bpfdtiie5h1e4qi4zqhe User talk:MarcoAurelio/Archives/2020 3 1052604 5387902 3646310 2022-07-29T11:05:17Z MarcoAurelio 36007 archive wikitext text/x-wiki {{talkarchive|User talk:MarcoAurelio}} == About [[Extension talk:DeleteBatch]] == Somehow this talk page got borked and ended up not using Flow for some reason. I fixed this and posted your question again. Cheers --[[User:Kghbln|&#91;&#91;kgh&#93;&#93;]] ([[User talk:Kghbln|talk]]) 21:12, 1 February 2020 (UTC) : Hi [[User:Kghbln|Kghbln]]. That's because I disabled Flow there on purpose, as I have had issues with it several times already. Best regards, &mdash;[[User:MarcoAurelio|MarcoAurelio]] ([[User talk:MarcoAurelio|talk]]) 21:18, 1 February 2020 (UTC) :: Ah, I did not realize. Otherwise ... :| Acutally I already wanted to file a task on Phabricator. Good that I go in touch with you first. Huu, luckily I have not yet had issues with Flow. Cheers --[[User:Kghbln|&#91;&#91;kgh&#93;&#93;]] ([[User talk:Kghbln|talk]]) 09:20, 2 February 2020 (UTC) j52th7wcoka3cqffwu4ykgyn759mhzn Manual:Pywikibot/category redirect.py/fr 100 1055305 5387860 4821167 2022-07-29T10:22:52Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Git/pywikibot}} {{Pywikibot|scripts}} '''category_redirect.py''' est un script {{ll|Manual:Pywikibot|Pywikibot}} utilisé pour déplacer les pages des catégories redirigées. Le bot recherchera les catégories marquées d'un modèle de redirection de catégorie, prendra le premier paramètre du modèle comme cible de la redirection et y déplacera toutes les pages et sous-catégories de la catégorie. Il transforme également les redirections matérielles en redirections logicielles et corrige les doubles redirections. Un log est écrit sous &lt;userpage>/category_redirect_log. Seules les pages de catégories qui n'ont pas été modifiées depuis un certain temps de recharge (7 jours par défaut) sont prises en compte. Les paramètres suivants sont disponibles : {{Pywikibot command table beginning}} {{option|delay:#|2=Définissez un nombre de jours. Si la catégorie est modifiée plus récemment que la valeur fixée, le script l’ignore. La valeur par défaut est de 7 jours.}} {{option|tiny|2=<span lang="en" dir="ltr" class="mw-content-ltr">Only loops over [[:d:Q8099903|Category:Wikipedia non-empty soft redirected categories]] and moves all images, pages and categories in redirect categories to the target category</span>}} {{Pywikibot command table end}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Usage == </div> <syntaxhighlight lang=shell-session> $ python pwb.py category_redirect [options] </syntaxhighlight> {{Manual:Pywikibot/Global Options}} [[Category:Pywikibot scripts{{#translation:}}|category_redirect]] 5k5pfmbk4kv3fo1nbbwl215tws7k09y Manual:Installation requirements/cs 100 1065400 5386499 5384886 2022-07-28T14:42:08Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: <div class="mw-translate-fuzzy"> * Je vyžadován [[#Web server|webový server]] k zobrazení požadovaných stránek v klientském prohlížeči. </div> <div class="mw-translate-fuzzy"> * Je vyžadován [[#PHP|PHP]] ke spuštění softwaru. </div> <div class="mw-translate-fuzzy"> * Je vyžadován [[#Database server|databázový server]] pro ukládání stránek a dat z webů. </div> Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). <div class="mw-translate-fuzzy"> Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte správce serveru nebo hostitelskou společnost a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To run [[Special:MyLanguage/Manual:Maintenance scripts|MediaWiki maintenance scripts]], you will need command line access. </div> __TOC__ {{clear}} == Jednoduchá instalace jediným stažením == <div class="mw-translate-fuzzy"> Pokud používáte Linux, je nejlepší nainstalovat apache, php a MariaDB pomocí správce balíků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] zadejte následující: </div> <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === <span class="mw-translate-fuzzy">V jiných operačních systémech použijte [[:en:XAMPP|XAMPP]] z [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků webového serveru Apache, PHP a MariaDB pouze jediným stažením.</span> Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. <span class="mw-translate-fuzzy">Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš poskytovatel hostingu.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is broadly compatible with all major web servers that can invoke a compatible version of PHP.</span> <span class="mw-translate-fuzzy">Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]], který je k dispozici na [$apachedownload oficiální stránce pro stahování].</span> <span lang="en" dir="ltr" class="mw-content-ltr">[https://nginx.org/ nginx] ([https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/ configuration example]) is a good choice as well.</span> {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] pzfnluv77ujzycdyvx34kx19q6yra1i 5386501 5386499 2022-07-28T14:42:47Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. <div class="mw-translate-fuzzy"> * Je vyžadován [[#PHP|PHP]] ke spuštění softwaru. </div> <div class="mw-translate-fuzzy"> * Je vyžadován [[#Database server|databázový server]] pro ukládání stránek a dat z webů. </div> Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). <div class="mw-translate-fuzzy"> Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte správce serveru nebo hostitelskou společnost a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To run [[Special:MyLanguage/Manual:Maintenance scripts|MediaWiki maintenance scripts]], you will need command line access. </div> __TOC__ {{clear}} == Jednoduchá instalace jediným stažením == <div class="mw-translate-fuzzy"> Pokud používáte Linux, je nejlepší nainstalovat apache, php a MariaDB pomocí správce balíků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] zadejte následující: </div> <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === <span class="mw-translate-fuzzy">V jiných operačních systémech použijte [[:en:XAMPP|XAMPP]] z [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků webového serveru Apache, PHP a MariaDB pouze jediným stažením.</span> Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. <span class="mw-translate-fuzzy">Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš poskytovatel hostingu.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is broadly compatible with all major web servers that can invoke a compatible version of PHP.</span> <span class="mw-translate-fuzzy">Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]], který je k dispozici na [$apachedownload oficiální stránce pro stahování].</span> <span lang="en" dir="ltr" class="mw-content-ltr">[https://nginx.org/ nginx] ([https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/ configuration example]) is a good choice as well.</span> {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] 2wnwk0jyseygt8apo5jfb8nwuy80v7n 5386503 5386501 2022-07-28T14:44:40Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. <div class="mw-translate-fuzzy"> * Je vyžadován [[#Database server|databázový server]] pro ukládání stránek a dat z webů. </div> Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). <div class="mw-translate-fuzzy"> Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte správce serveru nebo hostitelskou společnost a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To run [[Special:MyLanguage/Manual:Maintenance scripts|MediaWiki maintenance scripts]], you will need command line access. </div> __TOC__ {{clear}} == Jednoduchá instalace jediným stažením == <div class="mw-translate-fuzzy"> Pokud používáte Linux, je nejlepší nainstalovat apache, php a MariaDB pomocí správce balíků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] zadejte následující: </div> <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === <span class="mw-translate-fuzzy">V jiných operačních systémech použijte [[:en:XAMPP|XAMPP]] z [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků webového serveru Apache, PHP a MariaDB pouze jediným stažením.</span> Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. <span class="mw-translate-fuzzy">Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš poskytovatel hostingu.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is broadly compatible with all major web servers that can invoke a compatible version of PHP.</span> <span class="mw-translate-fuzzy">Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]], který je k dispozici na [$apachedownload oficiální stránce pro stahování].</span> <span lang="en" dir="ltr" class="mw-content-ltr">[https://nginx.org/ nginx] ([https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/ configuration example]) is a good choice as well.</span> {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] lr6u910a25n1ee4kdmmx9jxxq4dvpbz 5386513 5386503 2022-07-28T14:49:36Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === <span class="mw-translate-fuzzy">V jiných operačních systémech použijte [[:en:XAMPP|XAMPP]] z [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků webového serveru Apache, PHP a MariaDB pouze jediným stažením.</span> Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. <span class="mw-translate-fuzzy">Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš poskytovatel hostingu.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is broadly compatible with all major web servers that can invoke a compatible version of PHP.</span> <span class="mw-translate-fuzzy">Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]], který je k dispozici na [$apachedownload oficiální stránce pro stahování].</span> <span lang="en" dir="ltr" class="mw-content-ltr">[https://nginx.org/ nginx] ([https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/ configuration example]) is a good choice as well.</span> {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] 8rlzql66a3ua60lll5l7kgc4wch2jx7 5386516 5386513 2022-07-28T14:50:26Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. <span class="mw-translate-fuzzy">Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš poskytovatel hostingu.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is broadly compatible with all major web servers that can invoke a compatible version of PHP.</span> <span class="mw-translate-fuzzy">Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]], který je k dispozici na [$apachedownload oficiální stránce pro stahování].</span> <span lang="en" dir="ltr" class="mw-content-ltr">[https://nginx.org/ nginx] ([https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/ configuration example]) is a good choice as well.</span> {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] oh7q53buo287i9hsl3tuerrkdvhgell 5386522 5386516 2022-07-28T14:52:06Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is broadly compatible with all major web servers that can invoke a compatible version of PHP.</span> <span class="mw-translate-fuzzy">Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]], který je k dispozici na [$apachedownload oficiální stránce pro stahování].</span> <span lang="en" dir="ltr" class="mw-content-ltr">[https://nginx.org/ nginx] ([https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/ configuration example]) is a good choice as well.</span> {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] mf076mxdk83n4tr1a8tckg0ods8aawd 5386524 5386522 2022-07-28T14:52:23Z ENeRZet 17359278 Created page with "MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP." wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. <span class="mw-translate-fuzzy">Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]], který je k dispozici na [$apachedownload oficiální stránce pro stahování].</span> <span lang="en" dir="ltr" class="mw-content-ltr">[https://nginx.org/ nginx] ([https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/ configuration example]) is a good choice as well.</span> {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] 8us6vtelcl7ity1xfdhscukswqbj5jk 5386528 5386524 2022-07-28T14:53:04Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]]. <span lang="en" dir="ltr" class="mw-content-ltr">[https://nginx.org/ nginx] ([https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/ configuration example]) is a good choice as well.</span> {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] pnjrcpgpsrbqx56gyr3da8aa2eldpj8 5386530 5386528 2022-07-28T14:53:30Z ENeRZet 17359278 Created page with "$1 ([příklad konfigurace $url]) je také dobrá volba." wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]]. [https://nginx.org/ nginx] ([příklad konfigurace https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/]) je také dobrá volba. {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] <span lang="en" dir="ltr" class="mw-content-ltr">(required since 1.33)</span> **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] a1p2oojnxbziauchpuc8dfesw0x9lun 5386532 5386530 2022-07-28T14:54:17Z ENeRZet 17359278 Created page with "(požadováno od verze 1.33)" wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]]. [https://nginx.org/ nginx] ([příklad konfigurace https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/]) je také dobrá volba. {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] (požadováno od verze 1.33) **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. <span class="mw-translate-fuzzy">Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u sdíleného hostitele.</span> * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] culin9qc95o0tsj4jpz6ljeh7d1q8k7 5386540 5386532 2022-07-28T14:55:32Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]]. [https://nginx.org/ nginx] ([příklad konfigurace https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/]) je také dobrá volba. {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] (požadováno od verze 1.33) **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u [[Special:MyLanguage/Hosting services|sdíleného hostitele]]. * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=<span class="mw-translate-fuzzy">Někteří uživatelé považují za užitečné nainstalovat další softwarový balíček, například [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [http://phppgadmin.sourceforge.net/ phpPgAdmin] (Postgres), který jim pomůže spravovat databázový server.</span> Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] fpu0sl5lr8m4oyb9hm2dnb4r3ih77ud 5386548 5386540 2022-07-28T14:56:28Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]]. [https://nginx.org/ nginx] ([příklad konfigurace https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/]) je také dobrá volba. {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] (požadováno od verze 1.33) **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u [[Special:MyLanguage/Hosting services|sdíleného hostitele]]. * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=Někteří uživatelé považují za užitečné nainstalovat další software '''control panel''', jako je [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [https://github.com/phppgadmin/phppgadmin phpPgAdmin] (PostgreSQL), který jim pomůže spravovat databázový server. Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. <div class="mw-translate-fuzzy"> * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. Aktualizace MediaWiki může být bez něj obtížnější. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] exi2djvvltlcd78zbhghylisat6z4hp 5386552 5386548 2022-07-28T14:58:14Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]]. [https://nginx.org/ nginx] ([příklad konfigurace https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/]) je také dobrá volba. {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] (požadováno od verze 1.33) **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u [[Special:MyLanguage/Hosting services|sdíleného hostitele]]. * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=Někteří uživatelé považují za užitečné nainstalovat další software '''control panel''', jako je [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [https://github.com/phppgadmin/phppgadmin phpPgAdmin] (PostgreSQL), který jim pomůže spravovat databázový server. Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. [[Special:MyLanguage/Manual:Upgrading|Aktualizace MediaWiki]] může být bez něj obtížnější. * <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Manual:$wgEnableEmail|Sending email notifications}} via the server itself requires a [[w:Message transfer agent|message transfer agent (MTA)]].</span> * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] bcnb2x7ecl4r66qkncelecai64406db 5386554 5386552 2022-07-28T14:59:27Z ENeRZet 17359278 Created page with "{{$1|Odesílání emailových upozornění}} přes samotný server vyžaduje [[w:Message transfer agent|agenta přenosu zpráv (MTA)]]." wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]]. [https://nginx.org/ nginx] ([příklad konfigurace https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/]) je také dobrá volba. {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] (požadováno od verze 1.33) **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u [[Special:MyLanguage/Hosting services|sdíleného hostitele]]. * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=Někteří uživatelé považují za užitečné nainstalovat další software '''control panel''', jako je [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [https://github.com/phppgadmin/phppgadmin phpPgAdmin] (PostgreSQL), který jim pomůže spravovat databázový server. Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. [[Special:MyLanguage/Manual:Upgrading|Aktualizace MediaWiki]] může být bez něj obtížnější. * {{ll|Manual:$wgEnableEmail|Odesílání emailových upozornění}} přes samotný server vyžaduje [[w:Message transfer agent|agenta přenosu zpráv (MTA)]]. * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. <div lang="en" dir="ltr" class="mw-content-ltr"> * '''{{ll|Manual:Memcached|memcached}}''' can be used for object caching. </div> == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] livwp6cy4orveqcgn81qn7g0wbn0s83 5386556 5386554 2022-07-28T15:00:18Z ENeRZet 17359278 Created page with "* '''{{$1|memcached}}''' lze použít pro ukládání objektů do mezipaměti." wikitext text/x-wiki <languages /> {{InstallationNav}} {{#lst:{{TNTN|Manual:Installation guide}}|requirements}} Kromě samotného [[Special:MyLanguage/Download|softwaru MediaWiki]] potřebujete: * [[#Web server|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. * [[#PHP|'''PHP''']] ke spuštění MediaWiki. * [[#Database server|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. Kromě toho existují různé [[#Optional dependencies|volitelné vlastnosti]], které jsou vyžadovány, pokud chcete používat určité pokročilé funkce (viz níže). Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[Special:MyLanguage/Hosting services|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. Ke spuštění [[Special:MyLanguage/Manual:Maintenance scripts|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. __TOC__ {{clear}} == Instalace na jedno stažení == Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: <syntaxhighlight lang="bash">sudo apt-get install php php-apcu php-intl php-mbstring php-xml php-mysql php-calendar mariadb-server apache2</syntaxhighlight> === Softwarové balíčky === Na jiných operačních systémech použijte [[Special:MyLanguage/Software bundles|softwarový balíček]] jako [[Special:MyLanguage/Manual:Installing MediaWiki on XAMPP|XAMPP]] od [https://www.apachefriends.org/ https://www.apachefriends.org] k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. Je k dispozici pro systémy Linux, Windows, Mac a Solaris. Od {{ym|2021|1}} obsahuje nejnovější verze XAMPP PHP 8.0 (nejnovější verze MediaWiki vyžaduje alespoň {{MW stable php requirement}}). Pokud máte počítač Apple, můžete použít [[w:MAMP|MAMP]], což je ekvivalent k XAMPP. MAMP v současné době zahrnuje možnost spuštění webového serveru Apache a databáze MySQL. Je k dispozici pro Windows i Mac, ale obvykle se používá pro Mac místo Windows. {{anchor|Web server}} == Web server == Aby bylo možné zobrazovat wiki stránky v prohlížečích, vyžaduje MediaWiki nějaký software webového serveru. Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[Special:MyLanguage/Hosting services|poskytovatel hostingu]]. MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. Většina instalací používá webový server [[Special:MyLanguage/Apache configuration|Apache]]. [https://nginx.org/ nginx] ([příklad konfigurace https://www.nginx.com/resources/wiki/start/topics/recipes/mediawiki/]) je také dobrá volba. {{anchor|PHP}} == PHP == [[w:PHP|PHP]] je programovací jazyk, ve kterém je napsána MediaWiki. Je proto vyžadován i pro spuštění softwaru. * Pro nejnovější stabilní verzi MediaWiki je vyžadováno alespoň '''[https://www.php.net/downloads PHP verze {{MW stable php requirement}}]'''. Další informace naleznete na stránce {{ll|Compatibility}}. {{MediaWiki PHP 7.4.0 to 7.4.2}} {{MediaWiki PHP 8}} * Jsou požadována následující rozšíření: **[https://php.net/pcre kompatibilní správné výrazy Perl (PCRE)] **[https://php.net/sessions podpory] **[https://php.net/spl spl] **[https://php.net/openssl openssl] **[https://php.net/json json] (MediaWiki 1.22+) **[https://php.net/mbstring mbstring] (požadováno od verze 1.27, doporučeno pro starší verze) **[https://php.net/fileinfo fileinfo] (požadováno od verze 1.30) **[https://php.net/intl intl] (požadováno od verze 1.36) **[https://php.net/calendar calendar] (požadováno od verze 1.33) **[https://php.net/xml xml] * Všimněte si, že všechna rozšíření jsou ve výchozím nastavení v PHP povolena. * Pokud chcete, aby MediaWiki používal MySQL, je u většiny distribucí založených na Debian nebo Ubuntu vyžadován balíček php-mysql. * Některé funkce MediaWiki mohou vyžadovat funkce PHP, které provádějí externí procesy, jako jsou miniatury obrázků, které někteří levní hostitelé obvykle deaktivují. Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u [[Special:MyLanguage/Hosting services|sdíleného hostitele]]. * Rozšíření MediaWiki mohou vyžadovat další funkce PHP, např. [[VisualEditor]] vyžaduje podporu [https://php.net/curl libcurl] (php-curl na distribucích založených na Debian nebo Ubuntu). Pokud potřebujete kompilovat PHP ze zdroje, podívejte se na {{ll|PHP configuration}} pro možnosti kompilace, které ovlivňují MediaWiki. {{anchor|Database server}} == Databázový server == MediaWiki ukládá veškerý text a data (obsahové stránky, uživatelské údaje, systémové zprávy atd.) do databáze, kterou je schopna sdílet s jinými webovými aplikacemi (phpBB atd.). K provozování nejnovější verze MediaWiki budete potřebovat jeden z následujících databázových serverů: * {{ll|Manual:MariaDB|MariaDB}} [https://mariadb.org/download/ {{MW stable MariaDB requirement}}+] nebo {{ll|Manual:MySQL|MySQL}} [https://dev.mysql.com/downloads/mysql/ {{MW stable mysql requirement}}+] * {{ll|Manual:PostgreSQL|PostgreSQL}} [https://www.postgresql.org {{MW stable postgresql requirement}}+] * {{ll|Manual:SQLite|nsp=0}} {{MW stable sqlite requirement}}+ {{Dropped Oracle MSSQL}} {{anchor|Control panel}} {{Note|1=Někteří uživatelé považují za užitečné nainstalovat další software '''control panel''', jako je [https://www.phpmyadmin.net phpMyAdmin] (MySQL/MariaDB) nebo [https://github.com/phppgadmin/phppgadmin phpPgAdmin] (PostgreSQL), který jim pomůže spravovat databázový server. Some {{ll|hosting services}} also provide such software.}} == Požadavky na hardware == Doporučené minimální požadavky jsou 256 MB RAM pro web s jedním počítačem a 85 MB úložiště. I když to nebude stačit pro rušný veřejný web nebo web s povoleným odesíláním. Někteří uživatelé hlásili, že MediaWiki běží i na počítačích s pouhými 48 MB RAM. Velikost instalace může být snížena na přibližně 50 MB v případě instalace pro vývojáře a na přibližně 26 MB v případě instalace pro koncového uživatele, která není určena pro vývojáře. Podrobnosti najdete na stránce {{ll|Manual:Reduce size of the installation}}. {{anchor|Optional dependencies}} == Volitelná rozšíření == * Pro {{ll|Manual:image thumbnailing|nsp=0}} je vyžadován '''ImageMagick''' nebo '''GD'''. * '''TeX''' je vyžadován pro inline zobrazení matematických vzorců. Ve většině distribucí založených na Debian nebo Ubuntu jsou v balíčku <code>texlive</code>. * '''Shell přístup''' (Shell access) je vyžadován pro spuštění {{ll|Manual:maintenance scripts|nsp=0}}. [[Special:MyLanguage/Manual:Upgrading|Aktualizace MediaWiki]] může být bez něj obtížnější. * {{ll|Manual:$wgEnableEmail|Odesílání emailových upozornění}} přes samotný server vyžaduje [[w:Message transfer agent|agenta přenosu zpráv (MTA)]]. * '''{{ll|Manual:$wgDiff3|GNU diff3}}''' lze poskytnout pro automatické řešení konfliktů. * '''{{ll|Manual:Memcached|memcached}}''' lze použít pro ukládání objektů do mezipaměti. == Související odkazy == * $kompatibil, pro informace o tom, jak se v budoucnu pravděpodobně změní instalační požadavky MediaWiki * {{ll|Manual:OS specific help}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] ik27er6eawgybosr2kir4hz5583m1hs Translations:Manual:Installation requirements/1/cs 1198 1065401 5386497 3687734 2022-07-28T14:42:07Z ENeRZet 17359278 wikitext text/x-wiki Kromě samotného [[$download|softwaru MediaWiki]] potřebujete: exjrfa4et6sob4i40gg7nhsf945q3py Translations:Manual:Installation requirements/2/cs 1198 1065403 5386500 3687739 2022-07-28T14:42:46Z ENeRZet 17359278 wikitext text/x-wiki * [[$1|Software '''webového serveru''']] pro poskytování stránek MediaWiki ve webovém prohlížeči. ey38h2u7od3x44lcxgzs0gijzowbt4i Translations:Manual:Installation requirements/3/cs 1198 1065404 5386502 3687741 2022-07-28T14:44:39Z ENeRZet 17359278 wikitext text/x-wiki * [[$1|'''PHP''']] ke spuštění MediaWiki. m4ns1l0d6tz7agjq290pyk7rwvxbtsm Translations:Manual:Installation requirements/4/cs 1198 1065407 5386506 4815104 2022-07-28T14:45:45Z ENeRZet 17359278 wikitext text/x-wiki * [[$1|'''Databázový server''']] pro ukládání stránek a dat MediaWiki. 4icpirwvp7unso43lcusljbiifotxbb Translations:Manual:Installation requirements/6/cs 1198 1065409 5386508 4815106 2022-07-28T14:47:17Z ENeRZet 17359278 wikitext text/x-wiki Pokud je váš web hostován (tj. nemáte nad ním přímou kontrolu), kontaktujte svého správce serveru nebo [[$1|hostingovou společnost]] a ujistěte se, že jsou tyto softwarové balíčky nainstalovány a jsou pro vás dostupné. qsfs2wr3l6h17hvjrzzk3i4jn5yvtzi Translations:Manual:Installation requirements/7/cs 1198 1065410 5386510 4993476 2022-07-28T14:48:14Z ENeRZet 17359278 wikitext text/x-wiki Instalace na jedno stažení 18nzu2yzv3913zvem4glrxiljmwkdzl Translations:Manual:Installation requirements/85/cs 1198 1065411 5386515 4993478 2022-07-28T14:50:25Z ENeRZet 17359278 wikitext text/x-wiki Na jiných operačních systémech použijte [[$1|softwarový balíček]] jako [[$2|XAMPP]] od $apachefriends k instalaci a konfiguraci všech důležitých balíčků &ndash; Webový server Apache, PHP a MariaDB &ndash; s jediným stažením. fav4qsr3bpl9fufh7g6onp47pbxzk01 Translations:Manual:Installation requirements/13/cs 1198 1065421 5386521 3687775 2022-07-28T14:52:05Z ENeRZet 17359278 wikitext text/x-wiki Často nebudete mít na výběr, který software použít. Rozhodující bude ten, který vám poskytne váš [[$1|poskytovatel hostingu]]. omzge6sisn75clis2dt2qimgeggodn8 Translations:Manual:Installation requirements/14/cs 1198 1065422 5386527 4993480 2022-07-28T14:53:03Z ENeRZet 17359278 wikitext text/x-wiki Většina instalací používá webový server [[$1|Apache]]. k9o3vpod7gj7h7jr9yxgg7xzt1j86f1 Translations:Manual:Installation requirements/35/cs 1198 1065444 5386539 4993489 2022-07-28T14:55:31Z ENeRZet 17359278 wikitext text/x-wiki Vezměte to, prosím, do úvahy, pokud plánujete nainstalovat MediaWiki u [[$1|sdíleného hostitele]]. kx2nqedaed1g4hsnhd4by52zs90m56y Translations:Manual:Installation requirements/62/cs 1198 1065474 5386551 4993513 2022-07-28T14:58:13Z ENeRZet 17359278 wikitext text/x-wiki * '''Shell přístup''' (Shell access) je vyžadován pro spuštění $1. [[$2|Aktualizace MediaWiki]] může být bez něj obtížnější. gyn7pjqrryzcmkkgwdjg2sobi6i0lz5 New requirements for user signatures 0 1066731 5386338 5325334 2022-07-28T13:22:06Z Shirayuki 472859 translation tweaks wikitext text/x-wiki <languages/> <translate><!--T:1--> Many wikis have requirements for custom user signatures.</translate> <translate><!--T:2--> The [[<tvar name=1>Special:MyLanguage/Editing team</tvar>|Editing team]] is seeking your input on a proposal to codify some of these requirements in Wikipedia's software.</translate> <translate><!--T:3--> This will make it easier to [[<tvar name=reply>mw:Talk pages project/replying</tvar>|reply to specific comments on talk pages]] and to use some other tools.</translate> <translate> <!--T:4--> You can find more details about what is being proposed, and why, below: </translate> * <translate><!--T:5--> What feedback the team is seeking:</translate> '''[[#Input: your feedback|<translate><!--T:6--> Input: your feedback</translate>]]''' * <translate><!--T:7--> Why this change is being proposed:</translate> '''[[#Background: why this change?|<translate><!--T:8--> Background: why this change?</translate>]]''' * <translate><!--T:9--> What change is being proposed:</translate> '''[[#Proposal: signature validation requirements|<translate><!--T:10--> Proposal: signature validation requirements</translate>]]''' * <translate><!--T:11--> How these changes could affect you:</translate> '''[[#Impact: effects of change|<translate><!--T:12--> Impact: effects of change</translate>]]''' __TOC__ {{anchor|Input: your feedback}} <translate> == Input: your feedback == <!--T:15--> <!--T:16--> The team wants your feedback about this proposal. <!--T:17--> Please post your comments about these questions [[<tvar name=talk>Talk:New requirements for user signatures</tvar>|'''on the talk page''']]:</translate> # '''<translate><!--T:18--> Would these signature validations create any problems on your wiki?</translate>''' # '''<translate><!--T:19--> What do you think the team should be aware of before making this change?</translate>''' # '''<translate><!--T:20--> What should be done about existing signatures that don't meet the new limits?</translate>''' <em><translate><!--T:21--> For example, should they be disallowed?</translate></em> <em><translate><!--T:22--> Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.</translate></em> {{anchor|Background: why this change?}} <translate> == Background: why this change? == <!--T:23--> <!--T:34--> In 2019, volunteers from [[<tvar name=1>mw:Talk pages consultation 2019/Participant group sign-up</tvar>|20 Wikimedia projects and usergroups]], along with staff from the Wikimedia Foundation, participated in the [[<tvar name=2>mw:Talk_pages_consultation_2019</tvar>|Talk pages consultation]]. It was an effort to define better tools for on-wiki communication. <!--T:35--> One of the outcomes of this consultation was [[<tvar name=1>mw:Talk_pages_consultation_2019/Phase_1_report#Replying</tvar>|a request for an easier way to reply to specific comments]] on talk pages. <!--T:36--> In order for [[<tvar name=1>mw:Talk_pages_project/replying</tvar>|this feature]] to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them. </translate> <translate><!--T:37--> The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself.</translate> <translate><!--T:38--> This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.</translate> <translate> <!--T:39--> This additional consistency in the format of signatures would improve existing features, like [[<tvar name=1>mw:Help:Notifications/Types#Mentions</tvar>|"mention" notifications]], which are only sent if the signature can be detected in your edit. </translate> {{anchor|Proposal: signature validation requirements}} <translate> == Proposal: signature validation requirements (2020) == <!--T:24--> </translate> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' <translate><!--T:13--> If no significant obstacles are identified, this change could happen in April 2020.</translate> <translate><!--T:14--> If the team needs to make significant changes as a result of your feedback, then it will take longer.</translate> <translate><!--T:75--> The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</translate> {{Highlight|1=<big><translate><!--T:76--> Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</translate></big>|color=yellow}} <translate> === Disallow some invalid HTML and other [[<tvar name=linter>mw:Help:Extension:Linter</tvar>|Linter]] errors === <!--T:25--> </translate> {{Tracked|T140606}} <translate><!--T:77--> Most importantly, this change would disallow unclosed formatting tags, like <tvar name=open>{{tag|i|open}}</tvar> or the corresponding wikitext markup, <tvar name=italics><code><nowiki>''</nowiki></code></tvar>, without a matching closing tag (in this case, <tvar name=close>{{tag|i|close}}</tvar> or <tvar name=italicsClose><code><nowiki>''</nowiki></code></tvar>, respectively).</translate> <translate><!--T:86--> Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</translate> <translate> <!--T:78--> The check would also identify [[<tvar name=misnested-tag>Special:LintErrors/misnested-tag</tvar>|misnested tags]], like <tvar name=example><syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight></tvar> (either both of the <tvar name=i><code>i</code></tvar>, or both of the <tvar name=b><code>b</code></tvar>, tags should be on the outside), and [[<tvar name=stripped-tag>Special:LintErrors/stripped-tag</tvar>|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). <!--T:79--> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like <tvar name=tt>{{tag|tt}}</tvar> and <tvar name=font>{{tag|font}}</tvar>. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. <!--T:80--> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[<tvar name=Linter>mw:Help:Extension:Linter#Documentation of lint issues</tvar>|this address]]. <!--T:81--> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. === Require a link to user page, talk page or contributions === <!--T:26--> </translate> {{Tracked|T237700}} <translate><!--T:82--> Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</translate> <translate><!--T:87--> For example, [[<tvar name=mention>mw:Help:Notifications/Types#Mentions</tvar>|"mention" notifications]] are not sent, and forthcoming [[<tvar name=discussionTools>mw:Extension:DiscussionTools</tvar>|DiscussionTools]] will not allow replying to comments with these invalid signatures.</translate> <translate><!--T:88--> Gadgets and other tools that interact with signatures also may not work as expected.</translate> <translate><!--T:83--> This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</translate><ref><translate><!--T:84--> See examples listed on <tvar name=T237700>[[phab:T237700|T237700]]</tvar>.</translate></ref> <translate> === Disallow "nested" substitution in signature === <!--T:27--> </translate> {{Tracked|T230652}} <translate><!--T:85--> ''Some'' use of <tvar name=subst>[[subst:]]</tvar> markup and tildes would also be disallowed in signatures.</translate> <translate><!--T:89--> Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</translate> <translate><!--T:90--> All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</translate> <translate><!--T:91--> Simple subst: markup is still allowed.</translate> </div> <translate> == Additional proposal (2021) == <!--T:95--> === Disallow line breaks in signature === <!--T:96--> </translate> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} <translate> == Impact: effects of change == <!--T:28--> === What would happen to existing signatures? === <!--T:29--> </translate> <translate><!--T:40--> Any existing signatures that would become invalid under the new rules are still allowed (''[[<tvar name=clause>:en:Grandfather_clause</tvar>|grandfathered in]]'').</translate> <translate><!--T:41--> When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</translate> <translate><!--T:42--> But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</translate> <translate><!--T:43--> We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</translate> <translate><!--T:44--> If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</translate> <translate> === When might these changes take place? === <!--T:30--> </translate> <translate><!--T:53--> Please comment before 31 March 2020.</translate> <translate><!--T:54--> The Editing team will make decisions about this project in early April.</translate> <translate><!--T:55--> The results will be posted on the talk page.</translate> <translate> <!--T:45--> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. === How will we know what changes are happening? === <!--T:31--> <!--T:46--> We'll include another notice in <tvar name=technews>[[m:Tech/News]]</tvar> when this change is about to be deployed. === What might the signature validation errors look like? === <!--T:32--> <!--T:47--> The HTML/lint errors include links to existing documentation about lint errors, such as <tvar name=lint>[[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]]</tvar>, and a button to highlight the problematic part of the signature. <!--T:48--> The required link errors include example wikitext syntax to use. </translate> <gallery mode="packed" caption="<translate nowrap><!--T:49--> Example errors</translate>"> File:MediaWiki preferences - existing user signature invalid.png|<translate><!--T:50--> Warning shown when the existing user signature is invalid (has lint errors).</translate> File:MediaWiki preferences - new user signature invalid 1.png|<translate><!--T:51--> Error shown when the new user signature is invalid (has a lint error).</translate> File:MediaWiki preferences - new user signature invalid 2.png|<translate><!--T:52--> Error shown when the new user signature is invalid (doesn't contain a required link).</translate> </gallery> <translate> == Outcome == <!--T:57--> ===Original proposal=== <!--T:92--> <!--T:58--> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </translate> # <translate><!--T:56--> Disallow some invalid HTML and other [[<tvar name=linter>mw:Help:Extension:Linter</tvar>|Linter]] errors</translate> #:<translate><!--T:59--> The scope of these changes will be reduced.</translate> <translate><!--T:60--> [[<tvar name=misnested>Special:LintErrors/misnested-tag</tvar>|Misnested]] and [[<tvar name=stripped>Special:LintErrors/stripped-tag</tvar>|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like <tvar name=tt>{{tag|tt}}</tvar> and <tvar name=font>{{tag|font}}</tvar> will not be banned at this time.</translate> <translate><!--T:61--> This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</translate> # <translate><!--T:62--> Require a link to user page, talk page or contributions</translate> #:<translate><!--T:63--> This will be implemented as originally planned.</translate> #:<translate><!--T:64--> For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</translate> <translate><!--T:65--> Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</translate> <translate><!--T:66--> This is for technical reasons.</translate> # <translate><!--T:67--> Disallow "nested" substitution in signature</translate> #:<translate><!--T:68--> This will be implemented as originally planned.</translate> <translate> <!--T:69--> The process for implementing this change is: </translate> * {{done}} <translate><!--T:70--> A general announcement will be made in [[<tvar name=TechNews>m:Tech/News</tvar>|Tech News]] when the new requirements are deployed.</translate> * {{done}} <translate><!--T:71--> Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</translate> * {{in progress}} <translate><!--T:72--> Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</translate> * <translate><!--T:73--> Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</translate> <translate> <!--T:74--> Third-party wikis will be able to enable this change manually. ===2021 proposal=== <!--T:93--> <!--T:94--> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., <tvar name=1>{{tag|br|single}}</tvar> and <tvar name=2>{{tag|p|open}}</tvar>) are disallowed. == Notes == <!--T:33--> </translate> <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] ikgiqqk9q9d0dox3o3uv21qzxtehjx5 Translations:New requirements for user signatures/2/en 1198 1067323 5386339 3694191 2022-07-28T13:22:19Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki The [[$1|Editing team]] is seeking your input on a proposal to codify some of these requirements in Wikipedia's software. k9t4tjbkfm4rqzhuxdc7wm1gzsj8qkw New requirements for user signatures/en 0 1067355 5386340 5325337 2022-07-28T13:22:24Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> Many wikis have requirements for custom user signatures. The [[Special:MyLanguage/Editing team|Editing team]] is seeking your input on a proposal to codify some of these requirements in Wikipedia's software. This will make it easier to [[mw:Talk pages project/replying|reply to specific comments on talk pages]] and to use some other tools. You can find more details about what is being proposed, and why, below: * What feedback the team is seeking: '''[[#Input: your feedback|Input: your feedback]]''' * Why this change is being proposed: '''[[#Background: why this change?|Background: why this change?]]''' * What change is being proposed: '''[[#Proposal: signature validation requirements|Proposal: signature validation requirements]]''' * How these changes could affect you: '''[[#Impact: effects of change|Impact: effects of change]]''' __TOC__ {{anchor|Input: your feedback}} == Input: your feedback == The team wants your feedback about this proposal. Please post your comments about these questions [[Talk:New requirements for user signatures|'''on the talk page''']]: # '''Would these signature validations create any problems on your wiki?''' # '''What do you think the team should be aware of before making this change?''' # '''What should be done about existing signatures that don't meet the new limits?''' <em>For example, should they be disallowed?</em> <em>Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.</em> {{anchor|Background: why this change?}} == Background: why this change? == In 2019, volunteers from [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia projects and usergroups]], along with staff from the Wikimedia Foundation, participated in the [[mw:Talk_pages_consultation_2019|Talk pages consultation]]. It was an effort to define better tools for on-wiki communication. One of the outcomes of this consultation was [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|a request for an easier way to reply to specific comments]] on talk pages. In order for [[mw:Talk_pages_project/replying|this feature]] to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them. The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself. This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations. This additional consistency in the format of signatures would improve existing features, like [[mw:Help:Notifications/Types#Mentions|"mention" notifications]], which are only sent if the signature can be detected in your edit. {{anchor|Proposal: signature validation requirements}} == Proposal: signature validation requirements (2020) == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' If no significant obstacles are identified, this change could happen in April 2020. If the team needs to make significant changes as a result of your feedback, then it will take longer. The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature. {{Highlight|1=<big>Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</big>|color=yellow}} === Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors === {{Tracked|T140606}} Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively). Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments. The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. === Require a link to user page, talk page or contributions === {{Tracked|T237700}} Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page. For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures. Gadgets and other tools that interact with signatures also may not work as expected. This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.<ref>See examples listed on [[phab:T237700|T237700]].</ref> === Disallow "nested" substitution in signature === {{Tracked|T230652}} ''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures. Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments. All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software. Simple subst: markup is still allowed. </div> == Additional proposal (2021) == === Disallow line breaks in signature === <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Impact: effects of change == === What would happen to existing signatures? === Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]''). When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid. But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it. We're looking for feedback as to whether you would like existing invalid signatures to be disallowed. If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures. === When might these changes take place? === Please comment before 31 March 2020. The Editing team will make decisions about this project in early April. The results will be posted on the talk page. If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. === How will we know what changes are happening? === We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. === What might the signature validation errors look like? === The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. The required link errors include example wikitext syntax to use. <gallery mode="packed" caption="Example errors"> File:MediaWiki preferences - existing user signature invalid.png|Warning shown when the existing user signature is invalid (has lint errors). File:MediaWiki preferences - new user signature invalid 1.png|Error shown when the new user signature is invalid (has a lint error). File:MediaWiki preferences - new user signature invalid 2.png|Error shown when the new user signature is invalid (doesn't contain a required link). </gallery> == Outcome == ===Original proposal=== The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. # Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors #:The scope of these changes will be reduced. [[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time. This decision does not prejudice any future decision for or against removing these obsolete HTML tags. # Require a link to user page, talk page or contributions #:This will be implemented as originally planned. #:For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages. Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid. This is for technical reasons. # Disallow "nested" substitution in signature #:This will be implemented as originally planned. The process for implementing this change is: * {{done}} A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed. * {{done}} Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain. * {{in progress}} Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months. * Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead. Third-party wikis will be able to enable this change manually. ===2021 proposal=== The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. == Notes == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 3uqoikbd1zubqknpqixasghymokn4p4 New requirements for user signatures/zh 0 1067628 5386354 5325350 2022-07-28T13:22:35Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> 許多維基對於使用者自訂簽名有一些要求。 <span class="mw-translate-fuzzy">[[Editing team|編輯團隊]]正在徵求您對該計畫的意見,以將其編寫到維基百科的軟體中。</span> 這樣能夠讓[[mw:Talk pages project/replying|在討論頁面上回复特定留言]]及使用其他一些工具更加方便。 您可以在下面找到建議內容及其原因的詳細資訊: * 團隊正在尋求什麼反饋: '''[[#Input: your feedback|意見:您的反饋]]''' * 為什麼提出此更改: '''[[#Background: why this change?|背景:為何更改?]]''' * 提出了什麼更改: '''[[#Proposal: signature validation requirements|計畫:簽名驗證要求]]''' * 這些更改會怎麼影響您: '''[[#Impact: effects of change|影響:變化的影響]]''' __TOC__ {{anchor|Input: your feedback}} == 意見:您的反饋 == 團隊想要您對此提案的任何反饋。 請您[[Talk:New requirements for user signatures|'''在討論頁''']]發表有關這些問題的留言。 # '''簽名驗證會在您的維基上造成任何問題嗎?''' # '''您認為團隊在進行此更改之前應該注意些什麼?''' # '''不符合新限制的現有簽名應要如何處理?''' <em>例如,是否應禁止使用它們?</em> <em>請不要因上述問題而限制想法,團隊希望聽到您想分享的任何反饋。</em> {{anchor|Background: why this change?}} == 背景:為何更改? == 在2019年,來自[[mw:Talk pages consultation 2019/Participant group sign-up|20個維基媒體計畫和用戶組]]的志願者及維基媒體基金會的工作人員,參與了[[mw:Talk_pages_consultation_2019|討論頁諮詢]],為了定義維基上更好的交流工具。 這次諮詢的結果之一是[[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|請求回覆討論頁面上特定留言的更簡便方法]]。 為了使[[mw:Talk_pages_project/replying|此功能]]正常運作,該軟體需要簽名是「機器可讀的」以能夠更可靠地檢測使用者的留言並允許對其回覆。 問題是,儘管許多維基已經有必要的簽名要求,但是這些要求並未包含在軟體中。 這增加了有人設定破壞維基約定的簽名的可能性,且可能使人們更難以參與討論。 額外簽名格式一致性能改善現有功能,例如[[mw:Help:Notifications/Types#Mentions|「提及」通知]],僅在能夠從您的編輯中檢測到簽名時才發送通知。 {{anchor|Proposal: signature validation requirements}} == 計畫:簽名驗證要求 == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' 如果沒有發生重大阻礙,則可能在2020年4月進行此更改。 如果團隊需要根據您的反饋做出重大更改,則將需要更長的時間。 本章節介紹了三種提議的檢查方法,這些將應用於使用者在偏好設定中保存修改的簽名時。 {{Highlight|1=<big>根據編輯團隊的建議,'''現存的簽名將「不會」受到影響'''。</big>|color=yellow}} === 禁止一些無效的HTML和其他[[mw:Help:Extension:Linter|Linter]]錯誤 === {{Tracked|T140606}} 這個改變最重要的是禁止未關閉的格式化標籤,例如{{tag|i|open}}和相應的維基文本標記<code><nowiki>''</nowiki></code>,但沒有匹配的關閉標籤(在此例子中分別是{{tag|i|close}}或<code><nowiki>''</nowiki></code>)。 有無效標記的簽名的格式應用於後續留言時,會影響到整個討論頁面。 這個檢查也會識別[[Special:LintErrors/misnested-tag|未嵌套標籤]],例如<syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight>(兩個<code>i</code>或是兩個<code>b</code>標籤應該放置於外面),還有[[Special:LintErrors/stripped-tag|被忽略的標籤]],那些有關閉標籤但沒有對應的開啟標籤(與上面提到的「未關閉格式化標籤」相反)。 含有一些不太嚴重問題的簽名也被禁止,例如過時的HTML標籤,例如{{tag|tt}}和{{tag|font}}。儘管這些標籤不會立即引起問題,但是這可以防止這些過時代碼傳遞到新的wiki頁面,這對於清除Linter錯誤的編輯者來說是種困擾。 [[mw:Help:Extension:Linter#Documentation of lint issues|此位置]]提供了不被允許的語法功能完整列表,以及解釋如何更新和修復有Linter錯誤代碼的頁面連結。 未關閉的格式化標籤本來是應該由軟體來阻止,但由於目前的維基文本解析器的限制,這僅在某些狀況時有效。更強大的解決方法將借助[[Parsoid]]而變為可能。 === 要求連結到使用者頁面、討論頁或貢獻頁 === {{Tracked|T237700}} 當簽名不包含至少一個以下這些連結:連結到使用者頁面、使用者討論頁或貢獻頁,會導致各種工具無法運作。 例如將不會發出[[mw:Help:Notifications/Types#Mentions|'''提及'''通知]],即將發布的[[mw:Extension:DiscussionTools|討論工具]]將不允許回應這些有無效簽名的留言。 與簽名交互作用的小工具和其他工具也可能無法按預期運作。 此要求已在很多維基媒體的維基中作為方針存在很久,但還沒由MediaWiki軟體強制執行。<ref>見[[phab:T237700|T237700]]中列出的範例。</ref> === 在簽名中禁止“嵌套”的替換引用 === {{Tracked|T230652}} '''一些'''[[subst:]]標記和波浪號的使用方法也在簽名中不被允許。 以前可以使用這些功能來設定簽名,導致後續的編輯者名字出現在您的留言中。 長期以來大型維基一直由方針來禁止所有形式的偽造簽名,這種偽造簽名現在將由軟體來防止。 簡單的subst:標記仍然是允許的。 </div> == 附加請求 (2021) == === 在簽名中禁止換行符 === <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == 影響:變化的影響 == === 現有簽名會發生什麼改變? === 任何在新規則下無效的現存簽名將仍允許([[:en:Grandfather_clause|祖父條款]]) 當您查看偏好設定時將會看到警告消息。如果您嘗試更改簽名,新的簽名必須有效。 若您不修改它,當您簽名時仍會繼續使用舊的無效簽名,而且您能夠不受影響地修改其他偏好設定。 我們正在尋找您認為現存無效簽名是否要禁止的反饋。 如果禁止無效簽名,受影響的使用者在他們的留言簽名時將會插入預設簽名,直到他們修正自訂簽名。 === 這些更改何時會進行? === 請在2020年3月31日前留言。 編輯團隊將在4月初對此項目的做出相關決定。 結果將會發布在討論頁。 如果沒有發生阻礙,則可能在2020年4月進行此更改。如果團隊需要根據您的反饋做出重大更改,則會推遲此日期。 === 我們如何知道有哪些更改正在進行? === 要部署此更改時,我們將在[[m:Tech/News]]中再次發送通知。 === 簽名驗證錯誤看起來的樣子如何? === HTML/Lint錯誤包括了指向相關Lint錯誤現有文檔的連結(例如[[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]]),以及用來醒目標示簽名中含有問題部分的按鈕。 必要連結錯誤包含了可供使用的範例維基語法。 <gallery mode="packed" caption="範例錯誤"> File:MediaWiki preferences - existing user signature invalid.png|當現有的使用者簽名無效時所顯示的警告(含有Lint錯誤)。 File:MediaWiki preferences - new user signature invalid 1.png|當新的使用者簽名無效時所顯示的錯誤(含有Lint錯誤)。 File:MediaWiki preferences - new user signature invalid 2.png|當新的使用者簽名無效時所顯示的錯誤(沒有包含必要的連結)。 </gallery> == 結果 == ===原始提案=== 該提議被廣泛地接受。根據志願者的意見做了一些小改動,並澄清了幾點問題。 # 禁止一些無效的HTML和其他[[mw:Help:Extension:Linter|Linter]]錯誤 #:這些更改的範圍將縮小。 [[Special:LintErrors/misnested-tag|未嵌套]]和[[Special:LintErrors/stripped-tag|被忽略]]的標籤將被拒絕,一些低優先度錯誤的標籤仍被接受,特別來說過時的HTML標籤例如{{tag|tt}}和{{tag|font}}目前沒有被禁止。 該決定不影響未來是否移除這些過時HTML標籤的決定。 # 要求連結到使用者頁面、討論頁或貢獻頁 #:這將會依原始計畫來實施。 #:清楚來說,必須至少有一個本地直接連結(不是透過重新導向,例如從舊使用者名稱來的)到這些頁面之一。 因此,<code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code>這樣的簽名能被接受(一個本地連結,一個連結到其他wiki),但是'''只'''有連結到其他wiki和只有來自舊使用者名稱的重新導向的簽名將無效。 這是由於技術原因。 # 在簽名中禁止“嵌套”的替換引用 #:這將會依原始計畫來實施。 實施此更改的過程為: * {{done}} 當新要求部署時將在[[m:Tech/News|技術新聞]]中進行一般性的通知。 * {{done}} 當在伺服器上進行軟體更改後,使用者將再也無法保存無效的自訂簽名,然而現有的簽名會保留。 * {{in progress}} 鼓勵使用無效簽名的活躍編輯者去修改他們的簽名,這個過程可能會持續幾個月。 * 最終所有的簽名都需要符合要求,如果編輯者沒有更正他們的自訂簽名,則他們的自訂簽名將停止運作,而顯示預設簽名。 第三方wiki將能夠手動啟用此更改。 ===2021年的提案=== 不允许包含[[w:换行符|换行符]]与[[w:回车符|回车符]](但不包括它们对应的HTML代码,例如{{tag|br|single}}和{{tag|p|open}})。 == 注释 == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] q742e9ggnulkttlvdkgzw0n724p5to4 New requirements for user signatures/fr 0 1068875 5386343 5325339 2022-07-28T13:22:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> De nombreux wikis ont des règles encadrant les signatures personnalisées des utilisateurs. <span class="mw-translate-fuzzy">L'[[Editing team]] souhaite obtenir votre avis sur une proposition visant à codifier certains de ces besoins dans le logiciel de Wikipedia.</span> Il sera ainsi plus simple de [[mw:Talk pages project/replying|répondre aux messages spécifiques sur les pages de discussion]] et d'utiliser d'autres outils. Vous trouverez ci-dessous plus de détails sur ce qui est proposé et pourquoi : * Sur quoi l'équipe souhaite obtenir un avis : '''[[#Input: your feedback|Contribution : votre avis]]''' * Pourquoi ces changements sont proposés : '''[[#Background: why this change?|Contexte : pourquoi ces changements ?]]''' * Quels changements sont proposés : '''[[#Proposal: signature validation requirements|Proposition : conditions de validation d'une signature]]''' * Comment ces changements pourraient vous affecter : '''[[#Impact: effects of change|Incidence : effets du changement]]''' __TOC__ {{anchor|Input: your feedback}} == Entrées : vos commentaires == L'équipe souhaite connaître votre avis sur cette proposition. Veuillez partager vos remarques concernant ces questions [[Talk:New requirements for user signatures|'''sur la page de discussion''']] : # '''Ces conditions de validation d'une signature créeraient-elles des problèmes sur votre wiki ?''' # '''De quoi l'équipe devrait-elle être consciente avant de procéder à ce changement ?''' # '''Que faire des signatures existantes qui ne respectent pas les nouvelles conditions ?''' <em>Par exemple, doivent-elles être rejetées ?</em> <em>Ne vous sentez pas limité par les questions ci-dessus. L'équipe souhaite lire toutes les remarques que vous avez à partager.</em> {{anchor|Background: why this change?}} == Contexte : pourquoi ces changements ? == En 2019, les bénévoles des [[mw:Talk pages consultation 2019/Participant group sign-up|20 projets Wikimedia et des groupes d'utilisateurs]], ainsi que des employés de la Wikimedia Foundation, ont participé à la [[mw:Talk_pages_consultation_2019|consultation sur la communication]]. Il s'agissait de déterminer de meilleurs outils pour discuter. Cette consultation a notamment débouché sur la [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|demande d'un moyen plus facile pour répondre à des messages spécifiques]] sur les pages de discussion. Pour que cette [[mw:Talk_pages_project/replying|fonctionnalité]] fonctionne correctement, le logiciel doit disposer de signatures lisibles par le logiciel, afin de pouvoir détecter de manière fiable les messages des utilisateurs et permettre d'y répondre. Le problème est que, bien que de nombreux wikis aient déjà mis en place des règles pour les signatures, ces exigences ne sont pas vérifiées par le logiciel lui-même. Cela accroît les possibilités qu'une personne appose une signature qui enfreint les règles du wiki et pourrait rendre plus difficile la participation aux discussions. Cette cohérence supplémentaire dans le format des signatures améliorerait les fonctionnalités existantes, comme les [[mw:Help:Notifications/Types#Mentions|notifications]], qui ne sont envoyées que si votre signature peut être détectée dans votre message. {{anchor|Proposal: signature validation requirements}} == Proposition : critères de validité d'une signature (2020) == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Si aucun obstacle important n'est identifié, ce changement pourrait intervenir en avril 2020. Si l'équipe doit apporter des changements importants suite à vos avis, cela prendra plus de temps. Les trois vérifications proposées sont décrites dans cette section. Elles seraient appliquées aux signatures des utilisateurs dans les préférences lorsqu'un utilisateur enregistre une signature modifiée. {{Highlight|1=<big>Selon la proposition de l'équipe Editing '''les signatures existantes ne seront *PAS* affectées'''.</big>|color=yellow}} === Interdire certains usages invalides en HTML et ceux identifiés par les erreurs [[mw:Help:Extension:Linter|Linter]] === {{Tracked|T140606}} Plus important encore, ce changement interdirait les balises de formatage non fermées, comme {{tag|i|open}} ou la balise wikitext correspondante, <code><nowiki>''</nowiki></code>, sans balise de fermeture correspondante (dans ce cas, {{tag|i|close}} ou <code><nowiki>''</nowiki></code>, respectivement). Les signatures contenant une syntaxe invalide peuvent affecter la page de discussion entière, quand le formatage continue dans les commentaires suivants. La vérification identifierait également les [[Special:LintErrors/misnested-tag|balises mal imbriquées]], comme $exemple (les deux balises <code>i</code>, ou les deux balises <code>b</code>, devraient être à l'extérieur), et les [[Special:LintErrors/stripped-tag|balises tronquées]], qui sont des balises de fermeture sans balise d'ouverture correspondante (le contraire de la « balise de formatage non fermée » mentionnée ci-dessus). Les signatures qui contiennent des problèmes moins critiques seraient également refusées, par exemple les balises HTML obsolètes comme {{tag|tt}} et {{tag|font}}. Bien que ces balises ne causent pas de problèmes immédiats, cela préviendrait de la propagation de code obsolète aux nouvelles pages du wiki, ce qui est gênant pour les éditeurs qui doivent nettoyer les erreurs Linter. Une liste complète des fonctionnalités syntaxiques qui ne seraient pas autorisées, ainsi que les liens vers des pages qui expliquent comment mettre à jour ou corriger le code avec des erreurs de Linter, est disponible à [[mw:Help:Extension:Linter#Documentation of lint issues|cette adresse]]. Les balises de formatage non fermées étaient déjà censées être empêchées par le logiciel, mais en raison des limitations de l'analyseur de wikitext actuel, cela n'a fonctionné que dans certains cas. Une solution plus robuste est devenue possible grâce à [[Parsoid]]. === Exiger un lien vers la page de l'utilisateur, la page de discussion ou les contributions === {{Tracked|T237700}} Divers outils ne fonctionnent pas correctement lorsqu'une signature ne contient pas au moins un des liens suivants : un lien vers la page de l'utilisateur, la page de discussion de l'utilisateur ou la page des contributions. Par exemple, les notifications de type « [[mw:Help:Notifications/Types#Mentions| mention]] » ne sont pas envoyées, et les prochains [[mw:Extension:DiscussionTools|Outils de discussion]] ne permettront pas de répondre aux commentaires avec ces signatures non valides. Les gadgets et autres outils qui interagissent avec les signatures peuvent également ne pas fonctionner comme prévu. Cette exigence est présente depuis longtemps dans les politiques de nombreux wikis de Wikimedia, mais elle n'a pas été appliquée par le logiciel MediaWiki.<ref>Voir les exemples listés sur [[phab:T237700|T237700]].</ref> === Interdire la substitution « imbriquée » dans une signature === {{Tracked|T230652}} ''Certaines'' utilisations de la balise [[subst:]] et des tildes seraient également interdites dans les signatures. Auparavant, il était possible d'utiliser ces fonctionnalités pour définir une signature qui faisait apparaître en plus un nom d'éditeur sur vos commentaires. Toutes les formes de falsification de signature ont longtemps été interdites par la politique des grands wikis, et ce type de falsification sera désormais empêché dans les logiciels. L'utilisation unique de subst: est toujours autorisée. </div> == Propositions supplémentaires (2021) == === Supprimer les passages à la ligne dans la signature === <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Incidence : effets du changement == === Qu'adviendrait-il des signatures existantes ? === Toute signature existante qui deviendrait invalide en vertu des nouvelles règles est toujours autorisée (''[[:en:Grandfather_clause|clause d'antériorité]]''). En consultant vos préférences, vous verrez un message d'avertissement et si vous essayez de changer la signature, la nouvelle signature doit être valide. Mais si vous ne la modifiez pas, l'ancienne signature invalide continuera d'être utilisée lors de la signature de votre message, et vous pourrez modifier vos autres préférences sans que cela n'ait d'incidence. Nous aimerions savoir si vous souhaitez que les signatures invalides existantes soient interdites. Si une signature invalide est interdite, une signature par défaut serait insérée lorsque l'utilisateur signe ses messages, jusqu'à ce qu'il corrige sa signature personnalisée. === Quand ces changements pourraient-ils avoir lieu ? === Veuillez envoyer vos commentaires avant le 31 mars 2020. L'équipe d'Edition prendra ses décisions concernant ce projet début avril. Les résultats seront affichés sur la page de discussion. Si aucun problème important n'est identifié, ce changement n'interviendrait pas avant avril 2020. Cette date pourrait être repoussée si l'équipe doit implémenter des modifications importantes suite à la réception de votre avis. === Comment connaîtrons-nous les changements appliqués ? === Nous publierons un autre message dans le [[m:Tech/News]] lorsque ce changement sera sur le point d'être mis en œuvre. === À quoi peuvent ressembler les erreurs lors de la validation de la signature ? === Les erreurs HTML/Lint comprennent des liens vers la documentation existante, telle que [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], et un bouton pour mettre en évidence la partie problématique de la signature. L'erreur pour le lien requis dans la signature propose des exemples de syntaxe à utiliser. <gallery mode="packed" caption="Exemples d'erreurs"> File:MediaWiki preferences - existing user signature invalid.png|Avertissement affiché lorsque la signature de l'utilisateur existante n'est pas valide (contient des erreurs Lint). File:MediaWiki preferences - new user signature invalid 1.png|Erreur affichée lorsque la nouvelle signature de l'utilisateur n'est pas valide (contient une erreur Lint). File:MediaWiki preferences - new user signature invalid 2.png|Erreur affichée lorsque la nouvelle signature de l'utilisateur n'est pas valide (ne contient pas le lien requis). </gallery> == Résultats == === Proposition initiale === La proposition a été largement acceptée. En réponse aux commentaires des contributeurs, quelques petites modifications ont été apportées et quelques points ont été clarifiés. # Interdire certaines parties en HTML non valides ainsi que d'autres erreurs [[mw:Help:Extension:Linter| Linter]] #:L'objectif de ces modifications sera réduit. Les [[Special:LintErrors/misnested-tag|balises mal imbriquées]] et les [[Special:LintErrors/stripped-tag|balises vides]] seront rejetées. Certaines erreurs de faible priorité seront tout de même acceptées. Plus précisément, les balises HTML obsolètes comme {{tag|tt}} et {{tag|font}} ne seront pas interdites pour le moment. Cette décision ne préjuge pas de toute décision future en faveur ou en défaveur de la suppression de ces balises HTML obsolètes. # Nécessite un lien vers la page utilisateur, la page de discussion ou les contributions #:Ceci sera implémenté comme prévu initialement. #:Par souci de clarté, il doit y avoir au moins un lien local direct (et non une redirection, par exemple à partir d'un ancien nom d'utilisateur) vers l'une de ces pages. Ainsi, une signature comme <code><nowiki>[[Utilisateur:Exemple|Exemple]] ([[m:Discussion utilisateur:Exemple]])</nowiki></code> serait acceptable (un lien direct local, un lien vers un autre projet frère), mais une signature qui inclut <em>seulement</em> des liens vers un autre wiki, ou <em>seulement</em> des redirections à partir d'un ancien nom d'utilisateur sera invalide. Ceci, pour des raisons techniques. # Interdire la substitution « imbriquée » dans la signature #:Ceci sera implémenté comme prévu initialement. Le processus pour implémenter cette modification est : * {{done}} Une annonce générale sera faite dans une édition des [[m:Tech/News|Tech News]] lorsque les nouvelles exigences entreront en vigueur. * {{done}} Une fois le changement de logiciel effectué sur les serveurs, les contributeurs ne pourront plus enregistrer de signature personnalisée non valide. Toutefois, les signatures existantes seront conservées. * {{in progress}} Les contributeurs actifs dont les signatures ne sont pas valides seront encouragés à modifier leur signature. Ce processus prendra probablement quelques mois. * À terme, toutes les signatures devront être conformes. Si les contributeurs ne corrigent pas leurs signatures personnalisées, celles-ci cesseront de fonctionner et la signature par défaut apparaîtra à la place. Les wikis tiers pourront activer ce changement manuellement. === Proposition 2021 === Les caractères de rupture de ligne [[w:fr:Carriage return|retour chariot]] et [[w:Newline|ligne suivante]] (mais pas les balises HTML, comme {{tag|br|single}} ou {{tag|p|open}}) ne sont pas autorisés. == Notes == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] smautiukn3tp9t6b4el635mm0b02sfk 5386364 5386343 2022-07-28T13:24:05Z Shirayuki 472859 update wikitext text/x-wiki <languages/> De nombreux wikis ont des règles encadrant les signatures personnalisées des utilisateurs. L'[[Special:MyLanguage/Editing team|Editing team]] souhaite obtenir votre avis sur une proposition visant à codifier certains de ces besoins dans le logiciel de Wikipedia. Il sera ainsi plus simple de [[mw:Talk pages project/replying|répondre aux messages spécifiques sur les pages de discussion]] et d'utiliser d'autres outils. Vous trouverez ci-dessous plus de détails sur ce qui est proposé et pourquoi : * Sur quoi l'équipe souhaite obtenir un avis : '''[[#Input: your feedback|Contribution : votre avis]]''' * Pourquoi ces changements sont proposés : '''[[#Background: why this change?|Contexte : pourquoi ces changements ?]]''' * Quels changements sont proposés : '''[[#Proposal: signature validation requirements|Proposition : conditions de validation d'une signature]]''' * Comment ces changements pourraient vous affecter : '''[[#Impact: effects of change|Incidence : effets du changement]]''' __TOC__ {{anchor|Input: your feedback}} == Entrées : vos commentaires == L'équipe souhaite connaître votre avis sur cette proposition. Veuillez partager vos remarques concernant ces questions [[Talk:New requirements for user signatures|'''sur la page de discussion''']] : # '''Ces conditions de validation d'une signature créeraient-elles des problèmes sur votre wiki ?''' # '''De quoi l'équipe devrait-elle être consciente avant de procéder à ce changement ?''' # '''Que faire des signatures existantes qui ne respectent pas les nouvelles conditions ?''' <em>Par exemple, doivent-elles être rejetées ?</em> <em>Ne vous sentez pas limité par les questions ci-dessus. L'équipe souhaite lire toutes les remarques que vous avez à partager.</em> {{anchor|Background: why this change?}} == Contexte : pourquoi ces changements ? == En 2019, les bénévoles des [[mw:Talk pages consultation 2019/Participant group sign-up|20 projets Wikimedia et des groupes d'utilisateurs]], ainsi que des employés de la Wikimedia Foundation, ont participé à la [[mw:Talk_pages_consultation_2019|consultation sur la communication]]. Il s'agissait de déterminer de meilleurs outils pour discuter. Cette consultation a notamment débouché sur la [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|demande d'un moyen plus facile pour répondre à des messages spécifiques]] sur les pages de discussion. Pour que cette [[mw:Talk_pages_project/replying|fonctionnalité]] fonctionne correctement, le logiciel doit disposer de signatures lisibles par le logiciel, afin de pouvoir détecter de manière fiable les messages des utilisateurs et permettre d'y répondre. Le problème est que, bien que de nombreux wikis aient déjà mis en place des règles pour les signatures, ces exigences ne sont pas vérifiées par le logiciel lui-même. Cela accroît les possibilités qu'une personne appose une signature qui enfreint les règles du wiki et pourrait rendre plus difficile la participation aux discussions. Cette cohérence supplémentaire dans le format des signatures améliorerait les fonctionnalités existantes, comme les [[mw:Help:Notifications/Types#Mentions|notifications]], qui ne sont envoyées que si votre signature peut être détectée dans votre message. {{anchor|Proposal: signature validation requirements}} == Proposition : critères de validité d'une signature (2020) == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Si aucun obstacle important n'est identifié, ce changement pourrait intervenir en avril 2020. Si l'équipe doit apporter des changements importants suite à vos avis, cela prendra plus de temps. Les trois vérifications proposées sont décrites dans cette section. Elles seraient appliquées aux signatures des utilisateurs dans les préférences lorsqu'un utilisateur enregistre une signature modifiée. {{Highlight|1=<big>Selon la proposition de l'équipe Editing '''les signatures existantes ne seront *PAS* affectées'''.</big>|color=yellow}} === Interdire certains usages invalides en HTML et ceux identifiés par les erreurs [[mw:Help:Extension:Linter|Linter]] === {{Tracked|T140606}} Plus important encore, ce changement interdirait les balises de formatage non fermées, comme {{tag|i|open}} ou la balise wikitext correspondante, <code><nowiki>''</nowiki></code>, sans balise de fermeture correspondante (dans ce cas, {{tag|i|close}} ou <code><nowiki>''</nowiki></code>, respectivement). Les signatures contenant une syntaxe invalide peuvent affecter la page de discussion entière, quand le formatage continue dans les commentaires suivants. La vérification identifierait également les [[Special:LintErrors/misnested-tag|balises mal imbriquées]], comme $exemple (les deux balises <code>i</code>, ou les deux balises <code>b</code>, devraient être à l'extérieur), et les [[Special:LintErrors/stripped-tag|balises tronquées]], qui sont des balises de fermeture sans balise d'ouverture correspondante (le contraire de la « balise de formatage non fermée » mentionnée ci-dessus). Les signatures qui contiennent des problèmes moins critiques seraient également refusées, par exemple les balises HTML obsolètes comme {{tag|tt}} et {{tag|font}}. Bien que ces balises ne causent pas de problèmes immédiats, cela préviendrait de la propagation de code obsolète aux nouvelles pages du wiki, ce qui est gênant pour les éditeurs qui doivent nettoyer les erreurs Linter. Une liste complète des fonctionnalités syntaxiques qui ne seraient pas autorisées, ainsi que les liens vers des pages qui expliquent comment mettre à jour ou corriger le code avec des erreurs de Linter, est disponible à [[mw:Help:Extension:Linter#Documentation of lint issues|cette adresse]]. Les balises de formatage non fermées étaient déjà censées être empêchées par le logiciel, mais en raison des limitations de l'analyseur de wikitext actuel, cela n'a fonctionné que dans certains cas. Une solution plus robuste est devenue possible grâce à [[Parsoid]]. === Exiger un lien vers la page de l'utilisateur, la page de discussion ou les contributions === {{Tracked|T237700}} Divers outils ne fonctionnent pas correctement lorsqu'une signature ne contient pas au moins un des liens suivants : un lien vers la page de l'utilisateur, la page de discussion de l'utilisateur ou la page des contributions. Par exemple, les notifications de type « [[mw:Help:Notifications/Types#Mentions| mention]] » ne sont pas envoyées, et les prochains [[mw:Extension:DiscussionTools|Outils de discussion]] ne permettront pas de répondre aux commentaires avec ces signatures non valides. Les gadgets et autres outils qui interagissent avec les signatures peuvent également ne pas fonctionner comme prévu. Cette exigence est présente depuis longtemps dans les politiques de nombreux wikis de Wikimedia, mais elle n'a pas été appliquée par le logiciel MediaWiki.<ref>Voir les exemples listés sur [[phab:T237700|T237700]].</ref> === Interdire la substitution « imbriquée » dans une signature === {{Tracked|T230652}} ''Certaines'' utilisations de la balise [[subst:]] et des tildes seraient également interdites dans les signatures. Auparavant, il était possible d'utiliser ces fonctionnalités pour définir une signature qui faisait apparaître en plus un nom d'éditeur sur vos commentaires. Toutes les formes de falsification de signature ont longtemps été interdites par la politique des grands wikis, et ce type de falsification sera désormais empêché dans les logiciels. L'utilisation unique de subst: est toujours autorisée. </div> == Propositions supplémentaires (2021) == === Supprimer les passages à la ligne dans la signature === <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Incidence : effets du changement == === Qu'adviendrait-il des signatures existantes ? === Toute signature existante qui deviendrait invalide en vertu des nouvelles règles est toujours autorisée (''[[:en:Grandfather_clause|clause d'antériorité]]''). En consultant vos préférences, vous verrez un message d'avertissement et si vous essayez de changer la signature, la nouvelle signature doit être valide. Mais si vous ne la modifiez pas, l'ancienne signature invalide continuera d'être utilisée lors de la signature de votre message, et vous pourrez modifier vos autres préférences sans que cela n'ait d'incidence. Nous aimerions savoir si vous souhaitez que les signatures invalides existantes soient interdites. Si une signature invalide est interdite, une signature par défaut serait insérée lorsque l'utilisateur signe ses messages, jusqu'à ce qu'il corrige sa signature personnalisée. === Quand ces changements pourraient-ils avoir lieu ? === Veuillez envoyer vos commentaires avant le 31 mars 2020. L'équipe d'Edition prendra ses décisions concernant ce projet début avril. Les résultats seront affichés sur la page de discussion. Si aucun problème important n'est identifié, ce changement n'interviendrait pas avant avril 2020. Cette date pourrait être repoussée si l'équipe doit implémenter des modifications importantes suite à la réception de votre avis. === Comment connaîtrons-nous les changements appliqués ? === Nous publierons un autre message dans le [[m:Tech/News]] lorsque ce changement sera sur le point d'être mis en œuvre. === À quoi peuvent ressembler les erreurs lors de la validation de la signature ? === Les erreurs HTML/Lint comprennent des liens vers la documentation existante, telle que [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], et un bouton pour mettre en évidence la partie problématique de la signature. L'erreur pour le lien requis dans la signature propose des exemples de syntaxe à utiliser. <gallery mode="packed" caption="Exemples d'erreurs"> File:MediaWiki preferences - existing user signature invalid.png|Avertissement affiché lorsque la signature de l'utilisateur existante n'est pas valide (contient des erreurs Lint). File:MediaWiki preferences - new user signature invalid 1.png|Erreur affichée lorsque la nouvelle signature de l'utilisateur n'est pas valide (contient une erreur Lint). File:MediaWiki preferences - new user signature invalid 2.png|Erreur affichée lorsque la nouvelle signature de l'utilisateur n'est pas valide (ne contient pas le lien requis). </gallery> == Résultats == === Proposition initiale === La proposition a été largement acceptée. En réponse aux commentaires des contributeurs, quelques petites modifications ont été apportées et quelques points ont été clarifiés. # Interdire certaines parties en HTML non valides ainsi que d'autres erreurs [[mw:Help:Extension:Linter| Linter]] #:L'objectif de ces modifications sera réduit. Les [[Special:LintErrors/misnested-tag|balises mal imbriquées]] et les [[Special:LintErrors/stripped-tag|balises vides]] seront rejetées. Certaines erreurs de faible priorité seront tout de même acceptées. Plus précisément, les balises HTML obsolètes comme {{tag|tt}} et {{tag|font}} ne seront pas interdites pour le moment. Cette décision ne préjuge pas de toute décision future en faveur ou en défaveur de la suppression de ces balises HTML obsolètes. # Nécessite un lien vers la page utilisateur, la page de discussion ou les contributions #:Ceci sera implémenté comme prévu initialement. #:Par souci de clarté, il doit y avoir au moins un lien local direct (et non une redirection, par exemple à partir d'un ancien nom d'utilisateur) vers l'une de ces pages. Ainsi, une signature comme <code><nowiki>[[Utilisateur:Exemple|Exemple]] ([[m:Discussion utilisateur:Exemple]])</nowiki></code> serait acceptable (un lien direct local, un lien vers un autre projet frère), mais une signature qui inclut <em>seulement</em> des liens vers un autre wiki, ou <em>seulement</em> des redirections à partir d'un ancien nom d'utilisateur sera invalide. Ceci, pour des raisons techniques. # Interdire la substitution « imbriquée » dans la signature #:Ceci sera implémenté comme prévu initialement. Le processus pour implémenter cette modification est : * {{done}} Une annonce générale sera faite dans une édition des [[m:Tech/News|Tech News]] lorsque les nouvelles exigences entreront en vigueur. * {{done}} Une fois le changement de logiciel effectué sur les serveurs, les contributeurs ne pourront plus enregistrer de signature personnalisée non valide. Toutefois, les signatures existantes seront conservées. * {{in progress}} Les contributeurs actifs dont les signatures ne sont pas valides seront encouragés à modifier leur signature. Ce processus prendra probablement quelques mois. * À terme, toutes les signatures devront être conformes. Si les contributeurs ne corrigent pas leurs signatures personnalisées, celles-ci cesseront de fonctionner et la signature par défaut apparaîtra à la place. Les wikis tiers pourront activer ce changement manuellement. === Proposition 2021 === Les caractères de rupture de ligne [[w:fr:Carriage return|retour chariot]] et [[w:Newline|ligne suivante]] (mais pas les balises HTML, comme {{tag|br|single}} ou {{tag|p|open}}) ne sont pas autorisés. == Notes == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 5wdy8cgdy3wn2rpnygzccl8a3h6bcx9 Translations:New requirements for user signatures/2/fr 1198 1068877 5386363 3915458 2022-07-28T13:24:04Z Shirayuki 472859 update wikitext text/x-wiki L'[[$1|Editing team]] souhaite obtenir votre avis sur une proposition visant à codifier certains de ces besoins dans le logiciel de Wikipedia. ipnnt6yzjj424dd6celyu60dwiyf0fa New requirements for user signatures/de 0 1069037 5386341 5325336 2022-07-28T13:22:24Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> Viele Wikis haben Anforderungen an Benutzersignaturen. <span class="mw-translate-fuzzy">Das [[Editing team|Redaktionsteam]] bittet Sie um Ihre Meinung zu einem Vorschlag, einige dieser Anforderungen in der Wikipedia-Software zu implementieren.</span> Dies erleichtert es, [[mw:Talk pages project/replying|auf bestimmte Kommentare auf Diskussionsseiten zu antworten]] und einige andere Tools zu verwenden. Weitere Informationen darüber, was vorgeschlagen wird und warum, finden Sie unten: * Welches Feedback sich das Team wünscht: '''[[#Input: your feedback|Eingabe: Ihr Feedback]]''' * Warum diese Änderung vorgeschlagen wird: '''[[#Background: why this change?|Hintergrund: Warum diese Änderung?]]''' * Welche Änderung wird vorgeschlagen: '''[[#Proposal: signature validation requirements|Vorschlag: Anforderungen an die Gültigkeit der Signatur]]''' * Wie sich diese Änderungen auf Sie auswirken könnten: '''[[#Impact: effects of change|Auswirkungen: Auswirkungen von Veränderungen]]''' __TOC__ {{anchor|Input: your feedback}} Eingabe: Ihr Feedback Das Team wünscht sich Ihr Feedback zu diesem Vorschlag. Bitte posten Sie Ihre Kommentare zu diesen Fragen [[Talk:New requirements for user signatures|'''auf der Diskussionsseite''']]: # '''Würden diese Signaturüberprüfungen Probleme in Ihrem Wiki verursachen?''' # '''Was sollte das Team Ihrer Meinung nach beachten, bevor Sie diese Änderung vornehmen?''' # '''Was gilt es mit vorhandenen Signaturen zu tun, die die neuen Vorraussetzungen nicht erfüllen?''' <em>Sollten sie beispielsweise nicht zugelassen werden?</em> <em>Bitte fühlen Sie sich durch die obigen Fragen nicht eingeschränkt. Das Team möchte jedes Feedback hören, das Sie uns mitteilen möchten.</em> {{anchor|Background: why this change?}} Hintergrund: Warum diese Änderung? Im Jahr 2019 nahmen Freiwillige aus [[mw:Talk pages consultation 2019/Participant group sign-up|Wikimedia-Projekten und Benutzergruppen]] zusammen mit Mitarbeitern der Wikimedia Foundation an der [[mw:Talk_pages_consultation_2019|Konsultation zu Diskussionsseiten]] teil. Es wurde versucht, bessere Tools für die On-Wiki-Kommunikation zu definieren. Eines der Ergebnisse dieser Konsultation war [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|eine Anfrage nach einer einfacheren Möglichkeit, auf bestimmte Kommentare zu antworten]] auf Diskussionsseiten. Damit [[mw:Talk_pages_project/replying|diese Funktion]] gut funktioniert, benötigt die Software Signaturen, die "maschinenlesbar" sind, damit sie die Kommentare der Benutzer zuverlässig erkennen und auf sie antworten können. Das Problem ist, dass viele Wikis bereits über die erforderlichen Signaturanforderungen verfügen, diese Anforderungen jedoch nicht in der Software selbst enthalten sind. Dies erhöht die Wahrscheinlichkeit, dass jemand eine Signatur setzt, die gegen die Konventionen des Wikis verstößt, und erschwert möglicherweise die Teilnahme an Gesprächen. Diese zusätzliche Einheitlichkeit im Format der Signaturen würde vorhandene Funktionen wie [[mw:Help:Notifications/Types#Mentions|"Erwähnungen"]] verbessern, die nur gesendet werden, wenn die Signatur in Ihrer Bearbeitung erkannt werden kann. {{anchor|Proposal: signature validation requirements}} Vorschlag: Anforderungen an die Gültigkeit der Signatur <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Wenn keine wesentlichen Hindernisse festgestellt werden, könnte diese Änderung im April 2020 erfolgen. Wenn das Team aufgrund Ihres Feedbacks wesentliche Änderungen vornehmen muss, dauert es länger. Die drei vorgeschlagenen Abfragen werden in dieser Sektion beschrieben. Diese würden auf die Benutzer-Signaturen in den Eigenschaften angewandt, sobald ein Benutzer eine modifizierte Signatur speichert. {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} Ungültiges HTML und andere [[mw:Help:Extension:Linter|Linter]] Fehler nicht zulassen {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> Einen Link zur Benutzerseite, Diskussionsseite oder zu den Beiträgen verlangen {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> "Verschachtelte" Signaturen nicht zulassen {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} Auswirkungen: Auswirkungen von Veränderungen Was würde mit vorhandenen Signaturen passieren? Alle vorhandenen Signaturen, die nach den neuen Regeln ungültig werden würden, sind weiterhin zulässig (''[[:en:Grandfather_clause|grandfathered in]]''). Wenn Sie Ihre Einstellungen anzeigen, wird eine Warnmeldung angezeigt. Wenn Sie versuchen, die Signatur zu ändern, muss die neue gültig sein. Wenn Sie es jedoch nicht ändern, wird die alte ungültige Signatur beim Signieren weiterhin verwendet, und Sie können Ihre anderen Einstellungen ändern, ohne sie zu beeinflussen. Wir bitten um Feedback, ob vorhandene ungültige Signaturen nicht zugelassen werden sollen. Wenn ungültige Signaturen nicht zulässig sind, wird die Standardsignatur eingefügt, wenn betroffene Benutzer ihre Beiträge signieren, bis sie ihre personalisierten Signaturen korrigieren. Wann könnten diese Änderungen stattfinden? <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> Wenn keine Hindernisse identifiziert werden, würde diese Änderung frühestens im April 2020 erfolgen. Dieses Datum könnte verschoben werden, wenn das Team aufgrund Ihres Feedbacks wesentliche Änderungen vornehmen muss. Woher wissen wir, welche Veränderungen stattfinden? Wir werden über [[m:Tech/News]] informieren, wenn diese Änderung bereitgestellt werden soll. Wie könnten die Signaturvalidierungsfehler aussehen? Die HTML-/Linterrors enthalten Links zu vorhandener Dokumentation zu Linterrors wie [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]] und eine Schaltfläche zum Hervorheben des problematischen Teils der Signatur. Zu den erforderlichen Linkfehlern gehört die zu verwendende Beispiel-Wikitext-Syntax. <gallery mode="packed" caption="Beispielfehler"> File:MediaWiki preferences - existing user signature invalid.png|Warnung wird angezeigt, wenn die vorhandene Benutzersignatur ungültig ist (Lint errors aufweist). File:MediaWiki preferences - new user signature invalid 1.png|Fehler wird angezeigt, wenn die neue Benutzersignatur ungültig ist (einen Linterror enthält). File:MediaWiki preferences - new user signature invalid 2.png|Fehler wird angezeigt, wenn die neue Benutzersignatur ungültig ist (keinen erforderlichen Link enthält). </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Outcome == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Require a link to user page, talk page or contributions</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow "nested" substitution in signature</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The process for implementing this change is: </div> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> Anmerkungen <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] town7m5mowsc4a5xlu5xy5hewi5jghj 5386360 5386341 2022-07-28T13:23:27Z Shirayuki 472859 update wikitext text/x-wiki <languages/> Viele Wikis haben Anforderungen an Benutzersignaturen. Das [[Special:MyLanguage/Editing team|Redaktionsteam]] bittet Sie um Ihre Meinung zu einem Vorschlag, einige dieser Anforderungen in der Wikipedia-Software zu implementieren. Dies erleichtert es, [[mw:Talk pages project/replying|auf bestimmte Kommentare auf Diskussionsseiten zu antworten]] und einige andere Tools zu verwenden. Weitere Informationen darüber, was vorgeschlagen wird und warum, finden Sie unten: * Welches Feedback sich das Team wünscht: '''[[#Input: your feedback|Eingabe: Ihr Feedback]]''' * Warum diese Änderung vorgeschlagen wird: '''[[#Background: why this change?|Hintergrund: Warum diese Änderung?]]''' * Welche Änderung wird vorgeschlagen: '''[[#Proposal: signature validation requirements|Vorschlag: Anforderungen an die Gültigkeit der Signatur]]''' * Wie sich diese Änderungen auf Sie auswirken könnten: '''[[#Impact: effects of change|Auswirkungen: Auswirkungen von Veränderungen]]''' __TOC__ {{anchor|Input: your feedback}} Eingabe: Ihr Feedback Das Team wünscht sich Ihr Feedback zu diesem Vorschlag. Bitte posten Sie Ihre Kommentare zu diesen Fragen [[Talk:New requirements for user signatures|'''auf der Diskussionsseite''']]: # '''Würden diese Signaturüberprüfungen Probleme in Ihrem Wiki verursachen?''' # '''Was sollte das Team Ihrer Meinung nach beachten, bevor Sie diese Änderung vornehmen?''' # '''Was gilt es mit vorhandenen Signaturen zu tun, die die neuen Vorraussetzungen nicht erfüllen?''' <em>Sollten sie beispielsweise nicht zugelassen werden?</em> <em>Bitte fühlen Sie sich durch die obigen Fragen nicht eingeschränkt. Das Team möchte jedes Feedback hören, das Sie uns mitteilen möchten.</em> {{anchor|Background: why this change?}} Hintergrund: Warum diese Änderung? Im Jahr 2019 nahmen Freiwillige aus [[mw:Talk pages consultation 2019/Participant group sign-up|Wikimedia-Projekten und Benutzergruppen]] zusammen mit Mitarbeitern der Wikimedia Foundation an der [[mw:Talk_pages_consultation_2019|Konsultation zu Diskussionsseiten]] teil. Es wurde versucht, bessere Tools für die On-Wiki-Kommunikation zu definieren. Eines der Ergebnisse dieser Konsultation war [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|eine Anfrage nach einer einfacheren Möglichkeit, auf bestimmte Kommentare zu antworten]] auf Diskussionsseiten. Damit [[mw:Talk_pages_project/replying|diese Funktion]] gut funktioniert, benötigt die Software Signaturen, die "maschinenlesbar" sind, damit sie die Kommentare der Benutzer zuverlässig erkennen und auf sie antworten können. Das Problem ist, dass viele Wikis bereits über die erforderlichen Signaturanforderungen verfügen, diese Anforderungen jedoch nicht in der Software selbst enthalten sind. Dies erhöht die Wahrscheinlichkeit, dass jemand eine Signatur setzt, die gegen die Konventionen des Wikis verstößt, und erschwert möglicherweise die Teilnahme an Gesprächen. Diese zusätzliche Einheitlichkeit im Format der Signaturen würde vorhandene Funktionen wie [[mw:Help:Notifications/Types#Mentions|"Erwähnungen"]] verbessern, die nur gesendet werden, wenn die Signatur in Ihrer Bearbeitung erkannt werden kann. {{anchor|Proposal: signature validation requirements}} Vorschlag: Anforderungen an die Gültigkeit der Signatur <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Wenn keine wesentlichen Hindernisse festgestellt werden, könnte diese Änderung im April 2020 erfolgen. Wenn das Team aufgrund Ihres Feedbacks wesentliche Änderungen vornehmen muss, dauert es länger. Die drei vorgeschlagenen Abfragen werden in dieser Sektion beschrieben. Diese würden auf die Benutzer-Signaturen in den Eigenschaften angewandt, sobald ein Benutzer eine modifizierte Signatur speichert. {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} Ungültiges HTML und andere [[mw:Help:Extension:Linter|Linter]] Fehler nicht zulassen {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> Einen Link zur Benutzerseite, Diskussionsseite oder zu den Beiträgen verlangen {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> "Verschachtelte" Signaturen nicht zulassen {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} Auswirkungen: Auswirkungen von Veränderungen Was würde mit vorhandenen Signaturen passieren? Alle vorhandenen Signaturen, die nach den neuen Regeln ungültig werden würden, sind weiterhin zulässig (''[[:en:Grandfather_clause|grandfathered in]]''). Wenn Sie Ihre Einstellungen anzeigen, wird eine Warnmeldung angezeigt. Wenn Sie versuchen, die Signatur zu ändern, muss die neue gültig sein. Wenn Sie es jedoch nicht ändern, wird die alte ungültige Signatur beim Signieren weiterhin verwendet, und Sie können Ihre anderen Einstellungen ändern, ohne sie zu beeinflussen. Wir bitten um Feedback, ob vorhandene ungültige Signaturen nicht zugelassen werden sollen. Wenn ungültige Signaturen nicht zulässig sind, wird die Standardsignatur eingefügt, wenn betroffene Benutzer ihre Beiträge signieren, bis sie ihre personalisierten Signaturen korrigieren. Wann könnten diese Änderungen stattfinden? <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> Wenn keine Hindernisse identifiziert werden, würde diese Änderung frühestens im April 2020 erfolgen. Dieses Datum könnte verschoben werden, wenn das Team aufgrund Ihres Feedbacks wesentliche Änderungen vornehmen muss. Woher wissen wir, welche Veränderungen stattfinden? Wir werden über [[m:Tech/News]] informieren, wenn diese Änderung bereitgestellt werden soll. Wie könnten die Signaturvalidierungsfehler aussehen? Die HTML-/Linterrors enthalten Links zu vorhandener Dokumentation zu Linterrors wie [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]] und eine Schaltfläche zum Hervorheben des problematischen Teils der Signatur. Zu den erforderlichen Linkfehlern gehört die zu verwendende Beispiel-Wikitext-Syntax. <gallery mode="packed" caption="Beispielfehler"> File:MediaWiki preferences - existing user signature invalid.png|Warnung wird angezeigt, wenn die vorhandene Benutzersignatur ungültig ist (Lint errors aufweist). File:MediaWiki preferences - new user signature invalid 1.png|Fehler wird angezeigt, wenn die neue Benutzersignatur ungültig ist (einen Linterror enthält). File:MediaWiki preferences - new user signature invalid 2.png|Fehler wird angezeigt, wenn die neue Benutzersignatur ungültig ist (keinen erforderlichen Link enthält). </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Outcome == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Require a link to user page, talk page or contributions</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow "nested" substitution in signature</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The process for implementing this change is: </div> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> Anmerkungen <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] d07n30acffcjr712r1jf1gr8wqq9mmt Translations:New requirements for user signatures/2/de 1198 1069040 5386359 3700394 2022-07-28T13:23:26Z Shirayuki 472859 update wikitext text/x-wiki Das [[$1|Redaktionsteam]] bittet Sie um Ihre Meinung zu einem Vorschlag, einige dieser Anforderungen in der Wikipedia-Software zu implementieren. 4d9s14dgyaisneavq6edyoms708ksje New requirements for user signatures/ja 0 1070110 5386345 5325340 2022-07-28T13:22:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> 利用者の署名を取り入れるウィキは多く、それぞれ固有の要件を設けています。 <span class="mw-translate-fuzzy">[[Special:MyLanguage/Editing team|編集機能チーム]]では署名要件をコード化してウィキペディアのソフトウェアに埋め込むという案につき、 皆さんからのご意見ご感想を募集中です。</span> この措置が実現すると、[[mw:Talk pages project/replying|トークページで特定のコメントへの返信する]]ことが楽になり、また他のツールの利便性も高まります。 提案の詳細とその理由は下記でご紹介します: * 皆さんからお聞きしたいこと: '''[[#Input: your feedback|投稿:ご意見ご感想]]''' * この改訂の提案理由: '''[[#Background: why this change?|背景情報:なぜこれを変更?]]''' * 提案された改訂点: '''[[#Proposal: signature validation requirements|提案:署名確認の要件]]''' * 皆さんへの影響: '''[[#Impact: effects of change|効果:改訂の影響]]''' __TOC__ {{anchor|Input: your feedback}} == 入力: フィードバック == 皆さんからこのプロジェクトにぜひご意見ご感想をお聞かせください。 次の質問の回答とコメントの投稿先は、[[Talk:New requirements for user signatures|'''トークページ''']]です: # '''もし署名確認要件が導入されると、皆さんのウィキでどのような不都合がありますか?''' # '''この改訂実施に先立ち、チームが知っておくべきことはありますか?''' # '''現在の署名が、改訂案の要件に見合わない場合、どんな対策をすればよいですか?''' <em>たとえば使用禁止にしますか?</em> <em>上記の質問は議論の糸口であり、ほかの話題も受け付けています。皆さんがこれは発言しておきたいという内容を、ぜひお聞かせください。</em> {{anchor|Background: why this change?}} == 背景: この変更の理由 == [[mw:Talk pages consultation 2019/Participant group sign-up|ウィキメディアのプロジェクト群ならびに利用者グループのボランティア参加者20名]]とウィキメディア財団職員は2019年、[[mw:Talk_pages_consultation_2019|トークページの協議]]に参加ました。これはオンウィキのコミュニケーションにもっと適したツールとは何にか、定義する努力の一環です。 この協議から得た成果のひとつが、トークページで[[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|特定のコメントに対してもっと楽に返信したい]]という声でした。 [[mw:Talk_pages_project/replying|この機能]]がきちんと作動するにはソフトウェアが処理できる「機械可読」な署名を要件として、それを使って利用者の特定のコメント検出の信頼性を高め、返信へとつなぐ必要があります。 障害は、すでに多くのウィキで署名要件を取り入れているものの、ソフトウェア本体にその要件を組み込んでいない点です。 そのため、もしウィキの慣例を破る署名が使われた場合、可能性としてですが、ほかの人が協議に参加する妨害がされるという事態が増えるかもしれないのです。 署名の書式の統一性を高めることは既存の機能の改善にもつながり、たとえば[[mw:Help:Notifications/Types#Mentions|「言及」の通知]]は編集箇所の署名を検出できた場合にのみ、送信されるものだからです。 {{anchor|Proposal: signature validation requirements}} == 提案: 署名検証の要件 == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' この改訂は特段の障害がない限り、2020年4月にも実施される可能性があります。 皆さんからのご意見に従って特段の修正が必要な場合、実装時期が延びる可能性があります。 提言された3点の修正はこの節で説明します。これらは個人設定において利用者が修正済みの署名を保存するときに適用を受けます。 {{Highlight|1=<big>編集機能チームの提言では、 '''既存の署名には影響 *なし* とされています'''。</big>|color=yellow}} === 無効な HTML およびその他の [[mw:Help:Extension:Linter|Linter]] エラーを許可しない === {{Tracked|T140606}} 最重要ポイントは、この変更によって書式タグの「閉じる」ほうが欠けたままでは使えなくなり、{{tag|i|open}}、<code><nowiki>''</nowiki></code>あるいはそれに対応するウィキ文で「閉じる」タグが必須です(後者の場合は {{tag|i|close}} または <code><nowiki>''</nowiki></code>のこと)。 不適格なマークアップを含む署名は、連続するコメントにタグの不備が影響することから、それを記入した議論のページ全体に影響を及ぼしかねません。 チェック機能により[[Special:LintErrors/misnested-tag|タグの入れ子のエラー]]も検出し、<syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> がその例で(2個の <code>i</code> タグあるいは2個の <code>b</code>タグは外側に書くべき)、[[Special:LintErrors/stripped-tag|露出したタグ]]つまり「閉じる」タグはあるのに「開く」タグが欠けている場合も検出します(つまり前述の「閉じ忘れの書式タグ」の反対バージョン)。 もっと深刻度が低いエラーを含む署名も、当然、許可されません。たとえば廃止された HTML の{{tag|tt}}や{{tag|font}}などです。これらは直近に問題を引き起こさなくても、この段階で不許可にすると、ウィキの新規ページに記述されるかもしれない廃止済みコードを除去することで、リントエラーの掃除をする編集者の負担を減らします。 許可されなくなる構文の特性は、リンターエラーのあるコードの更新や修正の説明を添えて、[[mw:Help:Extension:Linter#Documentation of lint issues|こちらのアドレス]]に総覧がまとめてあります。 書式タグで「閉じる」タグが欠けている場合、すでにソフトウェアが防止しているはずでしたが、現状のウィキ文パーサに限界があり、ソフトウェアによる予防措置は作動する状態が限定されています。[[Parsoid]]の導入により、堅牢な自動処理が可能になりました。 === 利用者ページ、トークページもしくは編集履歴のリンクは必須 === {{Tracked|T237700}} さまざまなツールの正常な機能を妨げないためには、署名に以下のリンクを最低1件含む必要があります。すなわちその利用者の利用者ページ、利用者トークページ、投稿記録ページ。 一例として[[mw:Help:Notifications/Types#Mentions|「言及」の通知]]を発信せず、今後の[[mw:Extension:DiscussionTools|議論用ツール]]では無効な署名ではコメントに対する返信を禁じる予定です。 またガジェットその他のツールで署名と連動するものも、期待される挙動が妨げられる可能性があります。 この要件は、多くのウィキメディア・ウィキの方針で長い間、提示されており、それでもメディアウィキのソフトウェアによる処置は徹底してきませんでした。<ref>例の一覧は [[phab:T237700|T237700]] をご参照ください。</ref> === 署名に「入れ子の」代用を許可しない === {{Tracked|T230652}} ''一部の''[[subst:]] マークアップやチルダ記号「~」の使い方を署名で禁止する可能性があります。 以前はこれらの機能を使い、利用者のコメントに署名すると二次的な編集者名を表示することができました。 署名の詐称はどのような形態であれ、ずいぶん前から大手のウィキで禁止されており、現状ではソフトウェアを使ってこれらの詐称を予防します。 簡単な subst:マークアップは今後も利用可能。 </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == 影響: 改訂の効果 == === 既存の署名はどうなりますか? === 既存の署名のうち、新しい要件のもとで無効となるものは現状では容認されます(''[[:en:Grandfather_clause|新しい条件の適用免除]]'')。 ご自分の個人設定を開いた宗、これに関する警告メッセージが表示された場合に既存の署名を変更すると、有効な署名は変更したほうに置き換えられます。 ただここで修正しない場合には、署名をするときにこれまでどおりの表記を使うことができ、その他の個人設定の項目を変更しても署名に影響しません。 既存の署名は使用禁止にするかどうか、ご意見ご感想をお聞かせください。 もし適切でない署名を許可しない場合、その影響を受けた利用者本人が特別の設定の既定をした署名を修正するまで、代わりに当該する利用者の既定の署名が表示されます。 === この改訂はいつ実施しますか? === コメント募集は2020年3月31日までを想定しています。 編集機能チームはこのプロジェクトの結論を4月初めに出そうとしています。 結果はトークページにて発表します。 特段の障害が発生しない限り、この改訂の実施は2020年4月初旬より早まることはありません。皆さんからのフィードバックを受け、チームが特段の修正を行う必要が生じた場合、左記の日程を延期する可能性があります。 === 改訂が行われたかどうか、判断するには? === この改訂の実装前に、[[m:Tech/News]] に再度、告知を載せてお知らせします。 === 署名要件に不適合だった場合、どんなエラー警告を表示しますか? === HTML/lintのエラーに対して、リントの間違いを解説する既存のページへのリンク、たとえば[[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]]を示し、付帯のボタンを押すと、署名のどの部分がエラーか強調表示させます。 必要なリンクが不足したというエラーには、ウィキ文の構文例が表示されます。 <gallery mode="packed" caption="エラーの例"> File:MediaWiki preferences - existing user signature invalid.png|警告表示:既存の利用者署名が無効な場合(リントのエラー)。 File:MediaWiki preferences - new user signature invalid 1.png|エラー表示:新しい利用者署名が無効な場合(リントのエラー)。 File:MediaWiki preferences - new user signature invalid 2.png|エラー表示:新しい利用者署名が無効な場合(必要なリンクが足りないなど)。 </gallery> == 結果 == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> 提案は多くの賛同を得ました。ボランティアの皆さんから集まったコメントに対応し、いくつか小さな変更をほどこし、不明瞭だった点を明白に変えました。 # 無効な HTML や [[mw:Help:Extension:Linter|Linter]] エラーは不許可 #:これらの変更の範囲は縮小されるはずです。 [[Special:LintErrors/misnested-tag|入れ子のエラー]]ならびに[[Special:LintErrors/stripped-tag|リンクが露出した]]タグは却下されます。優先度の低いエラーは、依然として合格となります。特記すべきは{{tag|tt}}や{{tag|font}}など廃止された HTML タグは、今回は禁止対象ではありません。 この決定はこれら使われなくなったHTML の除去について、将来、反対または賛成する決定をなんら妨げるものではありません。 # 利用者ページ、そのトークページもしくは編集履歴のリンクを必須とする #:本来の計画どおり、反映されます。 #:明白性を期すなら、それらのページと結ぶローカルの直接リンク(古い利用者名からなどリダイレクトは不可)が1件以上、存在しなければなりません。 すなわち、<code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code>という署名が仮にあったとすると、これは容認され(ローカルのリンク1件プラス他のウィキへのリンク1件)、他のウィキへのリンク<em>しかない</em>署名や、古い利用者名からのリダイレクト<em>しかない</em>署名は無効です。 原因は技術的な問題です。 # 署名に「入れ子の」代用を許可しない #:本来の計画どおり、反映されます。 変更を反映する手順は次のとおりです。 * {{done}} 新規の要件が実装されたら、[[m:Tech/News|技術ニュース]]に一般的なお知らせとして掲載します。 * {{done}} サーバ上にソフトウェアの変更を反映した段階で、利用者は無効なカスタム署名を保存できなくなります。しかしながら、既存の署名は削除されません。 * {{in progress}} 活動中の編集者で無効な署名をお持ちの場合は、変更をお勧めします。その手続き終了には数ヵ月かかる可能性があります。 * 最終的には、すべての署名が例外なく新しい要件に適合する必要があります。カスタム署名の修正に応じない編集者は、その署名は機能しなくなり、既定の署名が代入されます。 サードパーティのウィキでは手動でこの変更を反映してください。 <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == 注記 == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] fnk58dxp5as4ph0digv5q8n2wj5jlkv 5386356 5386345 2022-07-28T13:22:48Z Shirayuki 472859 update wikitext text/x-wiki <languages/> 利用者の署名を取り入れるウィキは多く、それぞれ固有の要件を設けています。 [[Special:MyLanguage/Editing team|編集機能チーム]]では署名要件をコード化してウィキペディアのソフトウェアに埋め込むという案につき、 皆さんからのご意見ご感想を募集中です。 この措置が実現すると、[[mw:Talk pages project/replying|トークページで特定のコメントへの返信する]]ことが楽になり、また他のツールの利便性も高まります。 提案の詳細とその理由は下記でご紹介します: * 皆さんからお聞きしたいこと: '''[[#Input: your feedback|投稿:ご意見ご感想]]''' * この改訂の提案理由: '''[[#Background: why this change?|背景情報:なぜこれを変更?]]''' * 提案された改訂点: '''[[#Proposal: signature validation requirements|提案:署名確認の要件]]''' * 皆さんへの影響: '''[[#Impact: effects of change|効果:改訂の影響]]''' __TOC__ {{anchor|Input: your feedback}} == 入力: フィードバック == 皆さんからこのプロジェクトにぜひご意見ご感想をお聞かせください。 次の質問の回答とコメントの投稿先は、[[Talk:New requirements for user signatures|'''トークページ''']]です: # '''もし署名確認要件が導入されると、皆さんのウィキでどのような不都合がありますか?''' # '''この改訂実施に先立ち、チームが知っておくべきことはありますか?''' # '''現在の署名が、改訂案の要件に見合わない場合、どんな対策をすればよいですか?''' <em>たとえば使用禁止にしますか?</em> <em>上記の質問は議論の糸口であり、ほかの話題も受け付けています。皆さんがこれは発言しておきたいという内容を、ぜひお聞かせください。</em> {{anchor|Background: why this change?}} == 背景: この変更の理由 == [[mw:Talk pages consultation 2019/Participant group sign-up|ウィキメディアのプロジェクト群ならびに利用者グループのボランティア参加者20名]]とウィキメディア財団職員は2019年、[[mw:Talk_pages_consultation_2019|トークページの協議]]に参加ました。これはオンウィキのコミュニケーションにもっと適したツールとは何にか、定義する努力の一環です。 この協議から得た成果のひとつが、トークページで[[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|特定のコメントに対してもっと楽に返信したい]]という声でした。 [[mw:Talk_pages_project/replying|この機能]]がきちんと作動するにはソフトウェアが処理できる「機械可読」な署名を要件として、それを使って利用者の特定のコメント検出の信頼性を高め、返信へとつなぐ必要があります。 障害は、すでに多くのウィキで署名要件を取り入れているものの、ソフトウェア本体にその要件を組み込んでいない点です。 そのため、もしウィキの慣例を破る署名が使われた場合、可能性としてですが、ほかの人が協議に参加する妨害がされるという事態が増えるかもしれないのです。 署名の書式の統一性を高めることは既存の機能の改善にもつながり、たとえば[[mw:Help:Notifications/Types#Mentions|「言及」の通知]]は編集箇所の署名を検出できた場合にのみ、送信されるものだからです。 {{anchor|Proposal: signature validation requirements}} == 提案: 署名検証の要件 == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' この改訂は特段の障害がない限り、2020年4月にも実施される可能性があります。 皆さんからのご意見に従って特段の修正が必要な場合、実装時期が延びる可能性があります。 提言された3点の修正はこの節で説明します。これらは個人設定において利用者が修正済みの署名を保存するときに適用を受けます。 {{Highlight|1=<big>編集機能チームの提言では、 '''既存の署名には影響 *なし* とされています'''。</big>|color=yellow}} === 無効な HTML およびその他の [[mw:Help:Extension:Linter|Linter]] エラーを許可しない === {{Tracked|T140606}} 最重要ポイントは、この変更によって書式タグの「閉じる」ほうが欠けたままでは使えなくなり、{{tag|i|open}}、<code><nowiki>''</nowiki></code>あるいはそれに対応するウィキ文で「閉じる」タグが必須です(後者の場合は {{tag|i|close}} または <code><nowiki>''</nowiki></code>のこと)。 不適格なマークアップを含む署名は、連続するコメントにタグの不備が影響することから、それを記入した議論のページ全体に影響を及ぼしかねません。 チェック機能により[[Special:LintErrors/misnested-tag|タグの入れ子のエラー]]も検出し、<syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> がその例で(2個の <code>i</code> タグあるいは2個の <code>b</code>タグは外側に書くべき)、[[Special:LintErrors/stripped-tag|露出したタグ]]つまり「閉じる」タグはあるのに「開く」タグが欠けている場合も検出します(つまり前述の「閉じ忘れの書式タグ」の反対バージョン)。 もっと深刻度が低いエラーを含む署名も、当然、許可されません。たとえば廃止された HTML の{{tag|tt}}や{{tag|font}}などです。これらは直近に問題を引き起こさなくても、この段階で不許可にすると、ウィキの新規ページに記述されるかもしれない廃止済みコードを除去することで、リントエラーの掃除をする編集者の負担を減らします。 許可されなくなる構文の特性は、リンターエラーのあるコードの更新や修正の説明を添えて、[[mw:Help:Extension:Linter#Documentation of lint issues|こちらのアドレス]]に総覧がまとめてあります。 書式タグで「閉じる」タグが欠けている場合、すでにソフトウェアが防止しているはずでしたが、現状のウィキ文パーサに限界があり、ソフトウェアによる予防措置は作動する状態が限定されています。[[Parsoid]]の導入により、堅牢な自動処理が可能になりました。 === 利用者ページ、トークページもしくは編集履歴のリンクは必須 === {{Tracked|T237700}} さまざまなツールの正常な機能を妨げないためには、署名に以下のリンクを最低1件含む必要があります。すなわちその利用者の利用者ページ、利用者トークページ、投稿記録ページ。 一例として[[mw:Help:Notifications/Types#Mentions|「言及」の通知]]を発信せず、今後の[[mw:Extension:DiscussionTools|議論用ツール]]では無効な署名ではコメントに対する返信を禁じる予定です。 またガジェットその他のツールで署名と連動するものも、期待される挙動が妨げられる可能性があります。 この要件は、多くのウィキメディア・ウィキの方針で長い間、提示されており、それでもメディアウィキのソフトウェアによる処置は徹底してきませんでした。<ref>例の一覧は [[phab:T237700|T237700]] をご参照ください。</ref> === 署名に「入れ子の」代用を許可しない === {{Tracked|T230652}} ''一部の''[[subst:]] マークアップやチルダ記号「~」の使い方を署名で禁止する可能性があります。 以前はこれらの機能を使い、利用者のコメントに署名すると二次的な編集者名を表示することができました。 署名の詐称はどのような形態であれ、ずいぶん前から大手のウィキで禁止されており、現状ではソフトウェアを使ってこれらの詐称を予防します。 簡単な subst:マークアップは今後も利用可能。 </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == 影響: 改訂の効果 == === 既存の署名はどうなりますか? === 既存の署名のうち、新しい要件のもとで無効となるものは現状では容認されます(''[[:en:Grandfather_clause|新しい条件の適用免除]]'')。 ご自分の個人設定を開いた宗、これに関する警告メッセージが表示された場合に既存の署名を変更すると、有効な署名は変更したほうに置き換えられます。 ただここで修正しない場合には、署名をするときにこれまでどおりの表記を使うことができ、その他の個人設定の項目を変更しても署名に影響しません。 既存の署名は使用禁止にするかどうか、ご意見ご感想をお聞かせください。 もし適切でない署名を許可しない場合、その影響を受けた利用者本人が特別の設定の既定をした署名を修正するまで、代わりに当該する利用者の既定の署名が表示されます。 === この改訂はいつ実施しますか? === コメント募集は2020年3月31日までを想定しています。 編集機能チームはこのプロジェクトの結論を4月初めに出そうとしています。 結果はトークページにて発表します。 特段の障害が発生しない限り、この改訂の実施は2020年4月初旬より早まることはありません。皆さんからのフィードバックを受け、チームが特段の修正を行う必要が生じた場合、左記の日程を延期する可能性があります。 === 改訂が行われたかどうか、判断するには? === この改訂の実装前に、[[m:Tech/News]] に再度、告知を載せてお知らせします。 === 署名要件に不適合だった場合、どんなエラー警告を表示しますか? === HTML/lintのエラーに対して、リントの間違いを解説する既存のページへのリンク、たとえば[[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]]を示し、付帯のボタンを押すと、署名のどの部分がエラーか強調表示させます。 必要なリンクが不足したというエラーには、ウィキ文の構文例が表示されます。 <gallery mode="packed" caption="エラーの例"> File:MediaWiki preferences - existing user signature invalid.png|警告表示:既存の利用者署名が無効な場合(リントのエラー)。 File:MediaWiki preferences - new user signature invalid 1.png|エラー表示:新しい利用者署名が無効な場合(リントのエラー)。 File:MediaWiki preferences - new user signature invalid 2.png|エラー表示:新しい利用者署名が無効な場合(必要なリンクが足りないなど)。 </gallery> == 結果 == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> 提案は多くの賛同を得ました。ボランティアの皆さんから集まったコメントに対応し、いくつか小さな変更をほどこし、不明瞭だった点を明白に変えました。 # 無効な HTML や [[mw:Help:Extension:Linter|Linter]] エラーは不許可 #:これらの変更の範囲は縮小されるはずです。 [[Special:LintErrors/misnested-tag|入れ子のエラー]]ならびに[[Special:LintErrors/stripped-tag|リンクが露出した]]タグは却下されます。優先度の低いエラーは、依然として合格となります。特記すべきは{{tag|tt}}や{{tag|font}}など廃止された HTML タグは、今回は禁止対象ではありません。 この決定はこれら使われなくなったHTML の除去について、将来、反対または賛成する決定をなんら妨げるものではありません。 # 利用者ページ、そのトークページもしくは編集履歴のリンクを必須とする #:本来の計画どおり、反映されます。 #:明白性を期すなら、それらのページと結ぶローカルの直接リンク(古い利用者名からなどリダイレクトは不可)が1件以上、存在しなければなりません。 すなわち、<code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code>という署名が仮にあったとすると、これは容認され(ローカルのリンク1件プラス他のウィキへのリンク1件)、他のウィキへのリンク<em>しかない</em>署名や、古い利用者名からのリダイレクト<em>しかない</em>署名は無効です。 原因は技術的な問題です。 # 署名に「入れ子の」代用を許可しない #:本来の計画どおり、反映されます。 変更を反映する手順は次のとおりです。 * {{done}} 新規の要件が実装されたら、[[m:Tech/News|技術ニュース]]に一般的なお知らせとして掲載します。 * {{done}} サーバ上にソフトウェアの変更を反映した段階で、利用者は無効なカスタム署名を保存できなくなります。しかしながら、既存の署名は削除されません。 * {{in progress}} 活動中の編集者で無効な署名をお持ちの場合は、変更をお勧めします。その手続き終了には数ヵ月かかる可能性があります。 * 最終的には、すべての署名が例外なく新しい要件に適合する必要があります。カスタム署名の修正に応じない編集者は、その署名は機能しなくなり、既定の署名が代入されます。 サードパーティのウィキでは手動でこの変更を反映してください。 <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == 注記 == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 44jek77dirq3b7c5ke37wsczx4ng6lp Translations:Manual:Installation guide/11/cs 1198 1070831 5387293 4994718 2022-07-28T21:57:56Z Baris6161TURK 17188421 wikitext text/x-wiki Další programy vyžadují miniatury obrázku. $1 (vyžaduje VisualEditor) a i jiné služby mají své vlastní požadavky. 9avpc5jfomfsqu9dso7m7pi1w3qw0k3 Translations:Manual:Installation requirements/8/cs 1198 1070849 5386511 4815131 2022-07-28T14:49:00Z ENeRZet 17359278 wikitext text/x-wiki Pokud používáte Linux, je nejlepší nainstalovat webový server ''Apache'', ''PHP'' a databázový server ''MariaDB'' pomocí správce balíčků. Na [https://www.debian.org/ Debian] a [https://www.ubuntu.com/ Ubuntu] proveďte následující: t8g3tm9rdeue3u1usaasi1h632ael9v Translations:Manual:Installation requirements/48/cs 1198 1070853 5386547 3705886 2022-07-28T14:56:27Z ENeRZet 17359278 wikitext text/x-wiki Někteří uživatelé považují za užitečné nainstalovat další software '''control panel''', jako je [$url phpMyAdmin] (MySQL/MariaDB) nebo [$url2 phpPgAdmin] (PostgreSQL), který jim pomůže spravovat databázový server. 7fai30rpc3ya4cscvffqqjf8n03fysu Groups/cs 0 1071676 5387355 5190121 2022-07-28T22:11:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Skupiny MediaWiki''' organizují aktivity komunit s otevřeným zdrojovým kódem v rámci specifických témat a geografických oblastí. Jsou to [[meta:Special:MyLanguage/Wikimedia user groups|skupiny uživatelů Wikimedie]], které se shodují na úrovni koordinace v kontextu MediaWiki. Proto rozšiřují kapacitu [[wmf:|nadace Wikimedia Foundation]] v [[Events|událostech]], [[Volunteer coordination and outreach/Training materials|školeních, dobrovolnických koordinacích a informačních a školicích materiálech]]. V propagační a jiné technické činnosti ve prospěch Wikipedie, hnutí Wikimedie a software MediaWiki. <span class="mw-translate-fuzzy">Skupiny MediaWiki jsou otevřeny členům [[Special:MyLanguage/How to contribute|přispívajícím různými specializacemi]] a úrovněmi odborných znalostí.</span> Čím plodnější a rozmanitější, tím lepší. Vítáni jsou i netechničtí uživatelé ochotní přispívat a učit se! Všechny skupiny se zavazují k [[wmf:Friendly space policy|pravidlům přátelského prostředí]]. Skupiny MediaWiki mohou [[Groups/Wikimedia support|podporovat]] nadaci Wikimedia Foundation v různých formách. == Tematické skupiny == Tematické skupiny MediaWiki spolupracují se svými logickými protějšky v širší komunitě [[w:FLOSS|FLOSS]]. Jsou to globální, online spolupracující skupiny. * Jsou v kontaktu s komunitami se stejným zaměřením. * Účastní se akcí se stejnými tématy. * Podporují související školicí a informační činnosti. * Pomáhají vylepšovat související dokumentaci na wikimedia.org. * Spolupracují se souvisejícími vývojovými týmy. * Nakonec se někteří z nich setkají na [//wikimania.wikimedia.org/ Wikimania]. == Místní skupiny == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Místní skupiny MediaWiki spolupracují s [[meta:Special:MyLanguage/Wikimedia Chapters|odnožemi Wikimedie]], například [[w:Wikipedia:Meetup|formou setkání Wikipedie]] a s dalšími místními komunitami souvisejícími s Wikimedií, svobodným softwarem, svobodnou kulturou... . Jejich zaměření spočívá v osobních aktivitách: * Organizování místních událostí: setkání, školení, hackfesty ... Tyto události dodržují [[wmf:Friendly_space_policy|WMF pravidla přátelského prostředí]]. * Účastní se na akcích pořádaných v jejich oblasti. * Distribuce merchandisingu. * Propagování místních přispěvatelů do celosvětových aktivit MediaWiki a Wikimedie. <div class="mw-translate-fuzzy"> Také pro neanglicky mluvící skupiny: * Lokalizace dokumentace a softwaru podle procesů [[Special:MyLanguage/translatewiki.net|translatewiki.net]]. </div> Místní skupiny musí být skutečně místními. Základní body jako např. Recife, Mnichov nebo Petrohrad jsou lepší než Brazílie, Německo nebo Rusko. <span class="mw-translate-fuzzy">Pokud vám chybí kanál pro regionální koordinaci, zvažte [[meta:Mailing lists#Create a new list|žádost o vytvoření]] [[meta:Mailing_lists/Overview#Regional_mailing_lists|regionálního seznamu adresátů]] anebo [[meta:Seznamy adresátů/Overview#Local|místního mailing seznamu]].</span> == Vytvoření skupiny == Nepotřebujeme, aby jste byli ve skupině, jen vy sami. Chcete-li získat schválení, musíte mít alespoň tři přispěvatele. Chcete-li vytvořit svou skupinu MediaWiki, podívejte se na [[Groups/Proposals|návrhy skupin]]. [[Category:MediaWiki Communication{{#translation:}}]] feremkwxl4899yy932hy1612vix31n3 5387372 5387355 2022-07-28T22:12:15Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Skupiny MediaWiki''' organizují aktivity komunit s otevřeným zdrojovým kódem v rámci specifických témat a geografických oblastí. Jsou to [[meta:Special:MyLanguage/Wikimedia user groups|skupiny uživatelů Wikimedie]], které se shodují na úrovni koordinace v kontextu MediaWiki. Proto rozšiřují kapacitu [[wmf:|nadace Wikimedia Foundation]] v [[Events|událostech]], [[Volunteer coordination and outreach/Training materials|školeních, dobrovolnických koordinacích a informačních a školicích materiálech]]. V propagační a jiné technické činnosti ve prospěch Wikipedie, hnutí Wikimedie a software MediaWiki. Skupiny MediaWiki jsou otevřeny členům [[Special:MyLanguage/How to contribute|přispívajícím různými specializacemi]] a úrovněmi odborných znalostí. Čím plodnější a rozmanitější, tím lepší. Vítáni jsou i netechničtí uživatelé ochotní přispívat a učit se! Všechny skupiny se zavazují k [[wmf:Friendly space policy|pravidlům přátelského prostředí]]. Skupiny MediaWiki mohou [[Groups/Wikimedia support|podporovat]] nadaci Wikimedia Foundation v různých formách. == Tematické skupiny == Tematické skupiny MediaWiki spolupracují se svými logickými protějšky v širší komunitě [[w:FLOSS|FLOSS]]. Jsou to globální, online spolupracující skupiny. * Jsou v kontaktu s komunitami se stejným zaměřením. * Účastní se akcí se stejnými tématy. * Podporují související školicí a informační činnosti. * Pomáhají vylepšovat související dokumentaci na wikimedia.org. * Spolupracují se souvisejícími vývojovými týmy. * Nakonec se někteří z nich setkají na [//wikimania.wikimedia.org/ Wikimania]. == Místní skupiny == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Místní skupiny MediaWiki spolupracují s [[meta:Special:MyLanguage/Wikimedia Chapters|odnožemi Wikimedie]], například [[w:Wikipedia:Meetup|formou setkání Wikipedie]] a s dalšími místními komunitami souvisejícími s Wikimedií, svobodným softwarem, svobodnou kulturou... . Jejich zaměření spočívá v osobních aktivitách: * Organizování místních událostí: setkání, školení, hackfesty ... Tyto události dodržují [[wmf:Friendly_space_policy|WMF pravidla přátelského prostředí]]. * Účastní se na akcích pořádaných v jejich oblasti. * Distribuce merchandisingu. * Propagování místních přispěvatelů do celosvětových aktivit MediaWiki a Wikimedie. <div class="mw-translate-fuzzy"> Také pro neanglicky mluvící skupiny: * Lokalizace dokumentace a softwaru podle procesů [[Special:MyLanguage/translatewiki.net|translatewiki.net]]. </div> Místní skupiny musí být skutečně místními. Základní body jako např. Recife, Mnichov nebo Petrohrad jsou lepší než Brazílie, Německo nebo Rusko. <span class="mw-translate-fuzzy">Pokud vám chybí kanál pro regionální koordinaci, zvažte [[meta:Mailing lists#Create a new list|žádost o vytvoření]] [[meta:Mailing_lists/Overview#Regional_mailing_lists|regionálního seznamu adresátů]] anebo [[meta:Seznamy adresátů/Overview#Local|místního mailing seznamu]].</span> == Vytvoření skupiny == Nepotřebujeme, aby jste byli ve skupině, jen vy sami. Chcete-li získat schválení, musíte mít alespoň tři přispěvatele. Chcete-li vytvořit svou skupinu MediaWiki, podívejte se na [[Groups/Proposals|návrhy skupin]]. [[Category:MediaWiki Communication{{#translation:}}]] kdv3ccarxc5xtc6fw64kr6i25lcjc3e 5387393 5387372 2022-07-28T22:14:39Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''Skupiny MediaWiki''' organizují aktivity komunit s otevřeným zdrojovým kódem v rámci specifických témat a geografických oblastí. Jsou to [[meta:Special:MyLanguage/Wikimedia user groups|skupiny uživatelů Wikimedie]], které se shodují na úrovni koordinace v kontextu MediaWiki. Proto rozšiřují kapacitu [[wmf:|nadace Wikimedia Foundation]] v [[Events|událostech]], [[Volunteer coordination and outreach/Training materials|školeních, dobrovolnických koordinacích a informačních a školicích materiálech]]. V propagační a jiné technické činnosti ve prospěch Wikipedie, hnutí Wikimedie a software MediaWiki. Skupiny MediaWiki jsou otevřeny členům [[Special:MyLanguage/How to contribute|přispívajícím různými specializacemi]] a úrovněmi odborných znalostí. Čím plodnější a rozmanitější, tím lepší. Vítáni jsou i netechničtí uživatelé ochotní přispívat a učit se! Všechny skupiny se zavazují k [[wmf:Friendly space policy|pravidlům přátelského prostředí]]. Skupiny MediaWiki mohou [[Groups/Wikimedia support|podporovat]] nadaci Wikimedia Foundation v různých formách. == Tematické skupiny == Tematické skupiny MediaWiki spolupracují se svými logickými protějšky v širší komunitě [[w:FLOSS|FLOSS]]. Jsou to globální, online spolupracující skupiny. * Jsou v kontaktu s komunitami se stejným zaměřením. * Účastní se akcí se stejnými tématy. * Podporují související školicí a informační činnosti. * Pomáhají vylepšovat související dokumentaci na wikimedia.org. * Spolupracují se souvisejícími vývojovými týmy. * Nakonec se někteří z nich setkají na [//wikimania.wikimedia.org/ Wikimania]. == Místní skupiny == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Místní skupiny MediaWiki spolupracují s [[meta:Special:MyLanguage/Wikimedia Chapters|odnožemi Wikimedie]], například [[w:Wikipedia:Meetup|formou setkání Wikipedie]] a s dalšími místními komunitami souvisejícími s Wikimedií, svobodným softwarem, svobodnou kulturou... . Jejich zaměření spočívá v osobních aktivitách: * Organizování místních událostí: setkání, školení, hackfesty ... Tyto události dodržují [[wmf:Friendly_space_policy|WMF pravidla přátelského prostředí]]. * Účastní se na akcích pořádaných v jejich oblasti. * Distribuce merchandisingu. * Propagování místních přispěvatelů do celosvětových aktivit MediaWiki a Wikimedie. Také pro neanglicky mluvící skupiny: * Lokalizace dokumentace a softwaru podle procesů [[Special:MyLanguage/translatewiki.net|translatewiki.net]]. Místní skupiny musí být skutečně místními. Základní body jako např. Recife, Mnichov nebo Petrohrad jsou lepší než Brazílie, Německo nebo Rusko. <span class="mw-translate-fuzzy">Pokud vám chybí kanál pro regionální koordinaci, zvažte [[meta:Mailing lists#Create a new list|žádost o vytvoření]] [[meta:Mailing_lists/Overview#Regional_mailing_lists|regionálního seznamu adresátů]] anebo [[meta:Seznamy adresátů/Overview#Local|místního mailing seznamu]].</span> == Vytvoření skupiny == Nepotřebujeme, aby jste byli ve skupině, jen vy sami. Chcete-li získat schválení, musíte mít alespoň tři přispěvatele. Chcete-li vytvořit svou skupinu MediaWiki, podívejte se na [[Groups/Proposals|návrhy skupin]]. [[Category:MediaWiki Communication{{#translation:}}]] f4ij2b7mh9n55z9mbt3w9auwrink6cd Translations:Groups/4/cs 1198 1071680 5387371 3709992 2022-07-28T22:12:14Z Shirayuki 472859 update wikitext text/x-wiki Skupiny MediaWiki jsou otevřeny členům [[$1|přispívajícím různými specializacemi]] a úrovněmi odborných znalostí. qi4tcr1viifdqg0gvm8ic7194n3cjm3 Translations:Groups/25/cs 1198 1071708 5387391 3710086 2022-07-28T22:14:39Z Shirayuki 472859 update wikitext text/x-wiki Také pro neanglicky mluvící skupiny: * Lokalizace dokumentace a softwaru podle procesů $1. 70ze2zb4syvd9bwbn1ijjp8ub664hai Extension:EventLogging/ru 102 1072180 5387148 5381730 2022-07-28T21:07:44Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides a framework for logging analytics events</span> |version = <span lang="en" dir="ltr" class="mw-content-ltr">continuous updates</span> |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} <div lang="en" dir="ltr" class="mw-content-ltr"> The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Features == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">EventLogging supports client-side logging from JavaScript and server-side logging from PHP.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Logging behavior can be dynamically configured using {{ll|Extension:EventStreamConfig}}.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The extension does not include any back-end code for transporting, parsing, or loading these events.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A separate service, [[wikitech:Event Platform/EventGate|EventGate]], implements this functionality and deals with inserting events into Kafka.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The details of these components are specific to Wikimedia Foundation's configuration.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == EventLogging at Wikimedia == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Wikimedia Foundation uses the EventLogging extension as part of a [[wikitech:Analytics/Systems/EventLogging|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[m:Special:MyLanguage/Privacy policy|privacy policy]] and [[m:Special:MyLanguage/Data retention guidelines|data retention guidelines]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This page is about general use of the EventLogging extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Wikimedia Foundation uses EventLogging with WMF specific backend components and [https://schema.wikimedia.org/#!/ schema repositories].</span> <span lang="en" dir="ltr" class="mw-content-ltr">For Wikimedia specific and maintained documentation, see [[wikitech:Analytics/Systems/EventLogging]] and [[wikitech:Event Platform]].</span> ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Configuring the schema location === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, the extension will look for schemas on [[m:Special:MyLanguage/Meta-Wiki|Meta-Wiki]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The relevant default settings are:</span> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</span> <span lang="en" dir="ltr" class="mw-content-ltr">E.g. to use the <code>Schema</code> namespace of the local wiki, set</span> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">(and ensure the user account that will create the schemas is [[Special:MyLanguage/Manual:Autoconfirmed users|autoconfirmed]]).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Logging events using EventLogging == </div> * {{ll|Extension:EventLogging/Guide}} - <span lang="en" dir="ltr" class="mw-content-ltr">to developing and deploying EventLogging schemas, and more</span> * {{ll|Extension:EventLogging/Programming}} - <span lang="en" dir="ltr" class="mw-content-ltr">tips and suggestions for developers writing code to log events</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Developing the EventLogging extension == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Developer setup === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Using Docker ==== </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Using mediawiki-vagrant ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you develop using mediawiki-vagrant, everything you need is encapsulated in the <code>eventlogging</code> role.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable it, run:</span> <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== For JavaScript development ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">If working on the JavaScript client, you'll need to install dependencies with <code>npm install</code> from the folder you're developing in.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then you can use <code>npm test</code> to run ESLint for example.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The "How to run tests" section below points out how to see JavaScript test results.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> When adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to run tests ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There are PHP tests, Python tests, and JavaScript tests. </div> <span lang="en" dir="ltr" class="mw-content-ltr">To run JavaScript tests, visit Special:JavaScriptTest/qunit on your development wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(See {{ll|Manual:JavaScript unit testing}}.)</span> <span lang="en" dir="ltr" class="mw-content-ltr">To run PHP tests, we use PHPUnit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Make sure it is installed, then:</span> <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] mrddles1vtek8hrku6kf0lz1v4h16fk Translations:Extension:Cargo/5/de 1198 1076015 5387029 3722450 2022-07-28T19:53:39Z ThisCarthing 17456337 wikitext text/x-wiki Es ist vom Konzept her ähnlich wie die Erweiterung $1, bietet aber eine Reihe von Vorteilen, einschließlich der einfachen Installation und Nutzung. df2puw48dq7okfvecnzmyu7ogjqmeb9 Translations:Help:Templates/31/cs 1198 1082004 5386377 5091938 2022-07-28T13:26:03Z ENeRZet 17359278 wikitext text/x-wiki Šablonu, například s názvem $tmpl, použijete proto aby tahle poznámka vypadala stejně všude tam, kde se použije. 111lwpn9lubpbwxkwu350jh3unzougg Translations:Help:Templates/34/cs 1198 1082010 5386380 5091952 2022-07-28T13:28:51Z ENeRZet 17359278 wikitext text/x-wiki Když se šablona používá na stránce, oddělují se parametry znakem "svislítko" ($pipe). MediaWiki identifikuje parametry předané šabloně třemi způsoby: podle pozice, čísla nebo jména. pjdpo9t2u7pfyp88vcqc8l3azgcwyks Translations:Help:Templates/178/cs 1198 1082045 5386392 5084607 2022-07-28T13:41:04Z ENeRZet 17359278 wikitext text/x-wiki zobrazí se: 510eiyt5hbo47tzfy4kqylwkrw59ynh Translations:Help:Templates/151/cs 1198 1082162 5386403 5092361 2022-07-28T13:47:23Z ENeRZet 17359278 wikitext text/x-wiki <pre><nowiki>{{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}}</nowiki></pre> cicce5oksezqa06td6ylvxdosm1qbii Translations:Help:Templates/153/cs 1198 1082164 5386409 5092373 2022-07-28T13:50:01Z ENeRZet 17359278 wikitext text/x-wiki Výhodou použití pojmenovaných parametrů ve vaší šabloně, kromě toho, že lze předat parametry v jiném pořadí, je i to, že je kód šablony snáze pochopitelný, a to i při použití mnoha parametrů. m0uax7j0yvmesii94rq3yyjsjmweme6 Manual:Combating spam/cs 100 1083296 5387471 5214845 2022-07-28T22:40:14Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Stejně jako všechny současné dynamické webové stránky jsou wikis běžným cílem pro spammery, kteří chtějí propagovat produkty nebo webové stránky. MediaWiki nabízí řadu funkcí určených k [[Special:MyLanguage/Manual:Combating vandalism|boji proti vandalismu obecně]]. Na této stránce se konkrétně zabýváme [[m:Wiki spam|wiki spamem]], který je často automatizovaný. == Přehled == Běžné nástroje používané v boji proti spamu wiki obvykle spadají do těchto kategorií: * Vyžadování přihlášení a nebo CAPTCHA u určitých operací, jako jsou úpravy, přidávání externích odkazů nebo vytváření nových uživatelů * Blokování úprav ze známých IP adres ze seznamu zakázaných nebo z adres IP, na nichž běží otevřené servery proxy * Blokování úprav, které přidávají konkrétní nechtěná klíčová slova nebo externí odkazy * Blokování specifických vzorů uživatelského jména a názvu stránky, které spamboty běžně používají * Blokování úprav novými nebo anonymními uživateli na konkrétních často cílených stránkách * Whitelisting (seznam povolených) známých editorů (jako jsou administrátoři, pravidelní přispěvatelé) a zároveň omezení pro nové nebo anonymní uživatele * Vyčištění skriptů nebo hromadné mazání ({{ll|Extension:Nuke}}) stávajících příspěvků z nedávno zakázaných spambotů Běžně se používá kombinace různých metod ve snaze udržet počet úprav spamu, robotů a otevřených proxy na minimu a zároveň omezit míru narušení způsobeného legitimním uživatelům webu. Mnoho těchto funkcí není ve výchozím nastavení aktivováno. Pokud na serveru nebo hostiteli instalujete instalaci MediaWiki, pak jste jediný, kdo může provést potřebné změny konfigurace! V každém případě požádejte své uživatele, aby vám pomohli [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|hlídat na wiki spam]] (a udělejte to sami), ale v dnešní době může spam snadno přemoci malé wiki komunity. Pomáhá trochu zvýšit tlak. Také byste si měli uvědomit, že žádné z těchto řešení nelze považovat za zcela odolné proti spamu. Efektivní praxí je pravidelně kontrolovat "{{int|recentchanges}}" ([[Special:RecentChanges]]). == Nejrychlejší řešení nejprve vyzkoušejte == Boj proti spamu by neměl být příliš tvrdý. Pokud chcete rychle a výrazně omezit spam, zkuste nejprve tyto kroky. * Nainstalujte rozšíření [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] a zablokujte známé adresy IP spamu. * Nainstalujte a nastavte základní rozšíření antivandalismu (již bylo dodáno s [[Special:MyLanguage/Download| poslední verzí]]), zejména {{ll|Extension:ConfirmEdit}}. * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Nakonfigurujte QuestyCaptcha]] a v případě potřeby [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|změňte výchozí nastavení]] pro vaši wiki. * Zapněte {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, což může být použito pro blokování specifických akcí, jako editování či zakládání účtů, pro open proxy, servery sítě Tor či VPN. Pokud problémy přetrvávají, přečtěte si další část této stránky, kde najdete další řešení, a pošlete zprávu na [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]]. == Základy nastavení antispamu == {{anchor|CAPTCHA}} === CAPTCHA === Jednou z běžnějších metod vyřazování automatických podání je použití [[w:CAPTCHA|CAPTCHA]]. Systému, který se snaží odlišit lidi od automatizovaných systémů tím, že požádá uživatele, aby vyřešil úkol, který je pro stroje obtížný. Rozšíření {{ll|Extension:ConfirmEdit|ConfirmEdit}} pro MediaWiki poskytuje rozšiřitelný rámec [[CAPTCHA]], který lze spustit na řadě událostí, včetně * všech úprav * úprav přidávajících nové, nerozpoznané externí odkazy * registrace uživatele Rozšíření se dodává se standardním testem, jedná se však o referenční implementaci a není určeno k produkčnímu použití. Operátorům Wiki, kteří instalují ConfirmEdit na veřejné wiki, se doporučuje používat jeden z modulů CAPTCHA obsažených v rozšíření (celkem jich je pět). Nejodolnější CAPTCHA, které jsou dnes k dispozici, jsou vaše vlastní otázky QuestyCaptcha. Přizpůsobte je přímo publiku vaší wiki a pravidelně je aktualizujete. ReCaptcha je v současné době poražen většinou spammerů <ref> Příklad: «Automaticky řeší captchas: GSA Captcha Breaker + Mega Ocr (řeší Recaptcha!)» Říká senukexcr. </ref>; Asirra CAPTCHA, která žádá uživatele, aby rozlišil kočky a psy, je pro uživatele obzvláště nepříjemná, ale může být účinná. Je důležité si uvědomit, že CAPTCHA mohou blokovat nejenom nežádoucí roboty. Pokud skript není schopen projít CAPTCHA, pak to také může být čtečka obrazovky nebo jiný software nebo pomoc používaná nevidomými nebo zrakově postiženými. Jednou z možností v CAPTCHA, widgetu "reCAPTCHA", je v takových případech alternativní zvukový CAPTCHA - ale někteří uživatelé počítačů selhávají při testech poslechu a čtení, takže to není úplně dobré řešení. Měli byste zvážit důsledky takové překážky a případně poskytnout alternativní prostředky pro postižené uživatele k vytváření účtů a přispívání, což je v některých jurisdikcích zákonný požadavek.<ref> Například [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Sekce 508 Standardy pro elektronické a informační technologie] </ref> Vaše wiki také nebude zcela chráněna proti spamu; [[w:CAPTCHA|podle Wikipedie]] "Spameři platí asi 0,80 až 1,20 $ za každých 1 000 vyřešených CAPTCHA společnostem zaměstnávajícím lidské řešitele v Bangladéši, Číně, Indii a mnoha dalších rozvojových zemích." Z tohoto důvodu by měl být kombinován s jinými mechanismy. ===rel="nofollow"=== Ve výchozí konfiguraci MediaWiki přidává <code>rel="nofollow"</code> k externím odkazům na wiki stránkách, což znamená, že jsou dodávány uživatelem. Mohou obsahovat spam. Proto by neměly být používány k ovlivňování algoritmů pro hodnocení stránek. Tento atribut ctí oblíbené vyhledávací nástroje, například [http://www.google.com Google]. Toto chování můžete vypnout na celém webu pomocí {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} nebo na základě jmenného prostoru pomocí konfigurační proměnné {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}}. Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. == Rutina antispamu: opatření na míru == Každý spammer je jiný. I když všichni vypadají nudně podobně. Pokud obecná protiopatření nestačí, použijte před extrémními kroky nástroje, které vám umožní řešit konkrétní problémy, které máte. {{anchor|Individual page protection}} === Ochrana jednotlivých stránek === Spamboty často opakovaně zasáhnou stejnou stránku. Běžné vzory pozorované u pagenů vytvořených pomocí spambotů zahrnují diskusní stránku, často mimo hlavní prostor (např. Category_talk: jsou málo používány, takže si vytvoří společné cíle) a další diskusní stránky. Nejvíce jsou zneužívány úpravy na wiki, které k úpravám nevyžadují registraci. Pocházejí z anonymních zdrojů. Blokováním úprav na těchto konkrétních stránkách, komukoli jinému než zavedeným uživatelům, může zabránit opětovnému vytvoření spamových výpisů. Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === Filtr zneužívání === {{ll|Extension:AbuseFilter}} (filtr zneužití) umožňuje privilegovaným uživatelům vytvářet pravidla zacílená na konkrétní typ spamu, který vaše wiki přijímá. Může pomoci automaticky zabránit akci nebo blokovat uživatele. Může prozkoumat mnoho vlastností úprav. Například uživatelské jméno, věk uživatele, přidaný text, přidané odkazy atd. Nejúčinnější je v případech, kdy máte jednoho nebo více kvalifikovaných administrátorů, kteří jsou ochotni vám pomoci v boji proti spamu. Filtr zneužití může být účinný i proti spammerům podporovaným člověkem, ale vyžaduje nepřetržitou údržbu, aby reagoval na nové typy útoků. Příklady boje proti automatickému spamu lze nalézt v [[Manual:Combating spam/AbuseFilter examples|Příručce:Příklady boje proti spamu / Příklady filtru zneužití]]. === Seznam spamů (SpamBlacklist)=== Výše uvedený přístup bude příliš těžkopádný, pokud se pokusíte blokovat větší množství spamových adres URL. Lepším přístupem je dlouhá černá listina identifikující mnoho známých spamových adres URL. Populární rozšíření pro MediaWiki je rozšíření {{ll|Extension:SpamBlacklist|SpamBlacklist}}, které blokuje úpravy, které přidávají na stránky adresy URL uvedené na černé listině: Umožňuje vytvoření takovéhoto seznamu na wiki s pomocí privilegovaných uživatelů a umožňuje použití seznamů získaných z externích zdrojů (ve výchozím nastavení , používá rozsáhlý [[m:Spam blacklist]]). Rozšíření {{ll|Extension:TitleBlacklist|TitleBlacklist}} (̝černá listina spamů) může být také užitečné, jako prostředek k zabránění opětovného vytvoření konkrétních skupin stránek, které používají 'bots k výpisu odkazových spamů. === Otevřené proxy === Otevřený server proxy je nebezpečný zejména proto, že se používá jako způsob, jak obejít protiopatření zaměřená na konkrétního narušitele. Viz také [[m:No open proxies|Žádné otevřené servery proxy]]. Existují někteří roboti, např. na Wikimedia wikis, detekující a blokující otevřené IP proxy. Jejich kód často není veřejný. Většina takových bloků, když si všimnete zneužití, se provádí ručně. Je proto důležité vědět, zda zneužívající IP je otevřený proxy server nebo něco jiného, aby se rozhodlo, jak se s tím vypořádat. Zejména, pokud se jedná o adresu IP používanou registrovaným uživatelem, získanou pomocí rozšíření {{ll|Extension:CheckUser|CheckUser}}. <div class="mw-translate-fuzzy"> Několik rozšíření, zejména rozšíření [[Special:MyLanguage/Extension:Tor block|Tor block]], blokuje řadu otevřených proxy serverů. </div> Od verze 1.22 je k dispozici {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}}, pro zvýšení účinnosti bloků. == Tvrdá opatření == Následující opatření jsou určena pro technicky zdatnější systémové správce, kteří vědí, co dělají: Je těžší je správně nastavit a monitorovat. Pokud jsou implementovány špatně, mohou být příliš staré na to, aby byly stále účinné, nebo dokonce pro vaši wiki kontraproduktivní. === $wgSpamRegex === MediaWiki poskytuje prostředky k filtrování textu úprav za účelem blokování nežádoucích doplňků prostřednictvím konfigurační proměnné <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code>. Můžete ji použít k blokování dalších úryvků textu nebo značek spojených s běžnými útoky na spam. Obvykle se používá k vyloučení adres URL (nebo částí adres URL), na které nechcete uživatele odkazovat. Uživatelé dostanou vysvětlující zprávu uvádějící, která část jejich upravovaného textu není povolena. {{ll|Extension:SpamRegex}} umožňuje editaci této proměnné na wiki. <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> Tím se zabrání jakékoli zmínce o 'online kasinu' nebo 'buy-viagra' nebo 'adipex' nebo 'phentermine'. '/i' na konci způsobí, že na případné vyhledávání nebude citlivý. Blokuje také úpravy, které se pokouší přidat skryté nebo přetékající prvky, což je běžný "trik" používaný při mnoha hromadných útocích, které se pokouší skrýt spam před diváky. === Změny konfigurace Apache === Kromě změny konfigurace MediaWiki, pokud používáte MediaWiki na Apache, můžete provést změny v konfiguraci webového serveru Apache, abyste zabránili spamu. Tato nastavení jsou obvykle umístěna do konfiguračního souboru virtuálního hostitele nebo do souboru s názvem [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] na stejném místě jako LocalSettings.php (Upozorňujeme, že pokud máte sdíleného webového hostitele, musí povolit AllowOverride, aby vám umožnil použití souboru .htaccess). ==== Filtrování podle agenta uživatele ==== Když na své wiki zablokujete spamera, prohledejte protokol přístupu svého webu podle IP adresy a zjistěte, který řetězec uživatelského agenta daná IP adresa poskytla. Například: :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> Tím se vrátí chyba 403 Zakázané na jakoukoli adresu IP s uživatelským agentem, který odpovídá zadanému regulárnímu výrazu. Dbejte na to, abyste v řetězci uživatelského agenta vynechali všechny nezbytné znaky regulárního výrazu, například . ( ) - se zpětnými lomítky (\). Chcete-li spárovat prázdné uživatelské agenty, stačí použít "^$". I když je řetězec agenta spammeru používán skutečnými prohlížeči, pokud je starý nebo málokdy se vyskytující, můžete použít pravidla přepsání k přesměrování uživatelů na chybovou stránku a doporučit jim, aby aktualizovali svůj prohlížeč: <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> ==== Zabránění blokovaným spammerům ve spotřebovávání zdrojů ==== Trvalý spammer nebo ten s poškozeným skriptem se může i nadále pokoušet spamovat vaši wiki poté, co byla zablokována, a zbytečně tak spotřebovávat zdroje. Přidáním pragmy [http://httpd.apache.org/docs/2.2/howto/access.html deny from], jako je následující, do souboru <code>.htaccess</code>, můžete jim zabránit v načítání stránek vůbec a místo toho vrátit 403 Zakázaná chyba: <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> === Černé seznamy adres IP === Většina nejproblematičtějších spamů přijímaných na webech MediaWiki pochází z adres, které ostatní webmasteři dlouho nazývají bot nebo otevřené proxy servery, ačkoli pro to existují pouze neoficiální důkazy. Tito roboti obvykle generují velké množství automatických registrací na webech fóra, komentují spam na blogu a vandalismus na stránkách wikis: Nejčastěji linkspam, ačkoli existující obsah je někdy prázdný, doplněný náhodnými blábolícími znaky nebo upravován takovým způsobem, aby rozbil stávající Unicode text. Poměrně jednoduchý [[#CAPTCHA|CAPTCHA]] může problém významně snížit, protože může blokovat vytvoření [[#Individual page protection|určitých často nevyžádaných stránek]]. Tato opatření však problém nevylučují a zpřísnění bezpečnosti pro všechny uživatele v určitém okamžiku způsobí nepohodlí legitimních přispěvatelů. Může být vhodnější namísto spoléhání se výhradně na CAPTCHA nebo jiná preventivní opatření, která ovlivňují všechny uživatele, zaměřit se konkrétně na IP adresy, o nichž již ostatní mistři stránek vědí, že jsou útočištěm net.abuse. Mnoho seznamů je již k dispozici, například [http://www.stopforumspam.com/downloads stopforumspam.com] obsahuje seznam "All IPs in CSV" (všech IP v CSV), který (od února 2012) obsahuje asi 200 000 IP známých spambotů. ==== Využití procesoru CPU a přetížení ==== Uvědomte si, že když se při pokusech o úpravy nebo zobrazení stránek provádí mnoho kontrol, roboti mohou snadno přetížit vaši wiki a narušit ji více, než pokud by nebyla chráněna. Sledujte náklady na ochranu svých zdrojů. ==== DNSBL ==== Můžete nastavit MediaWiki, aby zkontrolovala každou editovací IP adresu proti jednomu nebo více DNSBL (blacklistům založeným na DNS), což nevyžaduje žádnou údržbu, ale mírně zvyšuje latenci úprav. Například můžete přidat tento řádek do LocalSettings.php a blokovat tak mnoho otevřených proxy serverů a známých spammerů: <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. ==== Špatné chování a projekt HoneyPot ==== Špatné chování je první obranná linie blokující všechny požadavky známých spammerů identifikovaných pomocí HTTP hlaviček, IP adresy a dalších metadat. Je k dispozici jako rozšíření MediaWiki, viz {{ll|Extension:Bad Behavior}}. Pro maximální účinnost by měla být kombinována s [http://www.projecthoneypot.org/httpbl.php http:BL API Key], které můžete získat na [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], distribuovaného projektu sledování spamu. Chcete-li se připojit k projektu HoneyPot, musíte do svého webového serveru přidat veřejně přístupný soubor a pomocí následujícího kódu rozšíření ve vašem LocalSettings.php (nebo přiloženém souboru PHP) vložit odkaz na každou stránku: {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> Nastavte $wgHoneyPotPath na cestu stránky honeypot v LocalSettings.php (např. "/ciralix.php"). Můžete změnit podobu výše uvedeného odkazu na kteroukoli z alternativ navržených v Project HoneyPot. Možná se budete muset přihlásit do Project HoneyPot, abyste viděli tyto alternativní způsoby, jak učinit odkazy honeypot neviditelné pro člověka.[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] Jakmile se zaregistrujete, zvolte Services&rarr;HTTP Blacklist, abyste získali http:BL API Key, a vložte svůj klíč do nastavení Bad Behavior's.ini. ==== $wgProxyList ==== {{Warning|1=Tato konkrétní technika, pokud je seznam IP velký, podstatně zvýší dobu načítání stránky a zatížení serveru. Používejte ji opatrně.}} Proměnnou {{wg|ProxyList}} můžete nastavit na seznamu IP, které chcete zakázat. Tento lze pravidelně naplňovat z externího zdroje pomocí skriptu cron, jako je například následující: <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> Poté nastavíte v LocalSettings.php: <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> Možná budete chtít uložit tyto příkazy do souboru nazvaného např. <code>updateBannedIPs.sh</code>, takže jej můžete spouštět pravidelně. Můžete také použít řešení '''pouze pro PHP''' (PHP-only) a stáhnout ip-list ze stopforumspamu. Za tímto účelem zkontrolujte dostupný skript PHP [http://www.pschmidt.it/vim_source/updateBanned_php.txt zde]. Pokud tak učiníte a pro ukládání do mezipaměti používáte mezipaměť APC, možná budete muset zvýšit velikost apc.shm_size ve vašem php.ini, abyste se přizpůsobili tak velkému seznamu. Právě jste zakázali sto čtyřicet tisíc spammerů. Doufejme, že to nebude mít žádný rušivý účinek na vaše legitimní uživatele. Řekli jste "adieu" mnoha nejhorším známým spammerům na internetu. Dobrý riddance! To by mělo problém trochu uklidnit. Alespoň na chvíli… ==== Honeypots, DNS BLs and HTTP BLs ==== 140 000 mrtvých spammerů. Není to špatné, ale jakýkoli správný [[w:Bastard Operator From Hell|BOFH]] by se v tuto chvíli nudil a dychtivě by hledal 140 001 IP spamů, který by se náhodně zablokoval. A proč ne? Naštěstí jsou k dispozici dynamicky aktualizované seznamy spambotů, otevřených proxy serverů a dalších problémových IP adres. Mnohé také umožňují automatickou kontrolu uživatelských jmen nebo emailových adres (pro přihlášené uživatele) proti stejným blacklistům. Jednou formou černé listiny, kterou mohou správci MediaWiki znát, je DNS BL. Seznam serverů DNS hostovaný na serveru doménových jmen je databáze adres IP. Hledání adresy určuje, zda IP, která se pokouší zaregistrovat nebo upravit, je již známým zdrojem zneužití sítě. Možnosti {{wg|EnableDnsBlacklist}} a {{wg|DnsBlacklistUrls}} v MediaWiki poskytují primitivní příklad přístupu k černé listině DNS. Nastavte následující nastavení v {{ll|Manual:LocalSettings.php|LocalSettings.php}} a IP adresy uvedené jako HTTP spam jsou blokovány: <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> Černá listina DNS funguje takto: * Wiki obdrží žádost o úpravu nebo registraci nového uživatele z nějaké náhodné adresy IP (například ve formátu '123.45.67.89'). * Čtyři bajty IP adresy jsou umístěny v obráceném pořadí, poté následuje název požadovaného serveru černé listiny DNS. * Výsledná adresa je vyžadována ze serveru pro doménové jméno (v tomto příkladu '89.67.45.123.zen.spamhaus.org.' a '89.67.45.123.dnsbl.tornevall.org.'). * Server není nalezen (NXDOMAIN), pokud adresa není na černé listině. Pokud je na některém z blacklistů, je úprava blokována. Vyhledávání v externě hostované černé listině obvykle přidává ne více než několik sekund k času potřebnému k uložení úprav. Na rozdíl od nastavení $1, které musí být načteno na každé stránce čtené nebo zapisované, se použití černé listiny DNS provádí pouze během registrace nebo úprav stránek. Tím není ovlivněna rychlost, jakou může systém obsluhovat požadavky na čtení stránky (většinu vašeho provozu). Na rozdíl od nastavení {{wg|ProxyKey}}, které musí být načteno na každé stránce čtené nebo zapisované, se použití černé listiny DNS provádí pouze během registrace nebo úprav stránek. Tím není ovlivněna rychlost, jakou může systém obsluhovat požadavky na čtení stránky (většinu vašeho provozu). Zatímco původní SORBS byl primárně určen pro řešení otevřených webových proxy a emailového spamu, existují i ​​jiné seznamy specifické pro webový spam (fóra, komentáře k blogům, úpravy wiki), které mohou být proto vhodnější: * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] funguje velmi podobným způsobem jako SORBS DNSBL, ale zacílí na otevřené proxy a spam ve webové podobě. Většina jeho obsahu je konsolidována z jiných existujících seznamů zneužívajících IP. * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] se konkrétně zaměřuje na roboty, kteří shromažďují emailové adresy z webových stránek pro hromadné seznamy emailů, zanechávají komentářový spam nebo se pokoušejí ukrást hesla pomocí útoků ze slovníku. Vyžaduje uživatelský registr u projecthoneypot.org pro 12místný klíč API. Pokud by tento klíč (například) byl 'myapitestkey', vyhledávání by jinak vypadalo jako '89.67.45.123.http.dnsbl.sorbs.net.' nebo '89.67.45.123.opm.tornevall.org.' bude muset být 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.'. * Seznamy povolených webů mohou identifikovat emailové adresy a informace o uživateli spamu i přes jednoduchou adresu IP, ale neexistuje standardní formát pro odpověď ze serveru se seznamem HTTP. Například žádost o [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] by vrátila "Y|IP|4", pokud je adresa na černé listině ('N' nebo prázdná, pokud je v pořádku), zatímco webová žádost o [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] by vrátila "ip yes 2009-04-16 23:11:19 41" pokud je adresa na blacklistu (čas, datum a počet lze ignorovat) nebo prázdná, pokud je adresa v pořádku. Bez jediného standardního formátu, kterým server černé listiny odpovídá na dotaz, neexistuje v balíčku MediaWiki integrovaná podpora pro většinu online seznamů známých spambotů. Neschopnost určit více než jeden server černé listiny dále omezuje užitečnost vestavěných možností $1 a $2. Od $rev bylo MediaWiki schopno kontrolovat více DNSBL definováním $3 jako pole. Neschopnost určit více než jeden server černé listiny dále omezuje užitečnost vestavěných možností {{wg|EnableDnsBlacklist}} a {{wg|DnsBlacklistUrls}}. Od [[rev:58061]] bylo MediaWiki schopno kontrolovat více DNSBL definováním <code>$wgDnsBlacklistUrls</code> jako pole. Většina operátorů černých listin poskytuje velmi omezenou softwarovou podporu (často cílenou na aplikace jiné než wiki, jako je phpBB nebo Wordpress). Protože stejné spamboty vytvářejí podobné problémy na většině webů s otevřeným obsahem, nejhorší pachatelé útočící na weby MediaWiki budou také usilovně cílit na tisíce webů bez wiki se spamem v komentářích blogu, příspěvcích na fóru a v knihách návštěv. Automatický dotaz na více webů na černé listině je proto již široce používán při ochraně různých jiných forem webů s otevřeným obsahem a jména spambotů, řad a IP adres jsou již nyní příliš dobře známá. Zdá se, že za velkým procentem celkového problému je relativně malý počet spambotů. I v případě, že administrátoři nepřijímají zajatce, existuje vzor, ve kterém stejná spambotová IP, která před sekundou zveřejnila linkspam na wiki, spamuje blogové komentáře někde jinde a bude mít spamovací příspěvky na fóru pár sekund od nynějška na místě vzdáleném půl světa. To si pořádně zapamatujte. Jeden sdílený externí záznam na černé listině může umlčet jednoho problematického 'robota' od zveřejnění na tisících webů. Tím se výrazně snižuje počet jednotlivých IP adres, které je třeba ručně blokovat a to vždy na jedné wiki a na jednom fóru, místními administrátory. ==== Ale co je to s honeypoty? ==== Některé weby zabývající se nevyžádanou poštou, například projecthoneypot.org, poskytují kód, kterým jste vyzváni k zahrnutí na své vlastní webové stránky. Stránky obvykle obsahují jednu nebo více jedinečných, náhodných a skrytých emailových adres nebo odkazů, které nejsou určeny pro vaše lidské návštěvníky, ale pro spamboty. Při každém zobrazení stránky se vložené adresy automaticky změní, což umožňuje, aby jednotlivé části spamu byly přímo a přesvědčivě přiřazeny k IP adrese robotů, kteří získávali adresy z vašich stránek. IP adresa, kterou robot použil k prohlížení vašich stránek, je automaticky předána provozovatelům černé listiny. Odkaz na falešný 'komentář' nebo 'knihu návštěv' je často skrytý jako past do robotů, kteří odesílají spam do webových formulářů. Viz [[w:Honeypot_(computing)|Honeypot (computing)]]. Jakmile bude adresa spammeru známa, bude přidána na černé listiny (viz výše), takže vy i ostatní budete mít v budoucnu na svých stránkách o jednoho nežádoucího robotického návštěvníka méně. Zatímco skripty a servery černé listiny mohou automatizovat většinu úkolů identifikace a řešení spambotových IP adres, většina webů na černé listině poskytuje odkazy na webové stránky, na kterých lze ručně vyhledat informace o IP adrese nebo nahlásit zneužívající IP jako spambot. Může být vhodné zahrnout některé z těchto odkazů na speciální: Blokové stránky vaší wiki pro pohodlí administrátorů vašeho webu. ==== Další seznamy proxy a spambotů IPs==== Zpravidla zadáním adresy libovolného robota nebo otevřeného proxy serveru do vyhledávače se vrátí mnoho seznamů, na kterých byly tyto zneužívající adresy IP již nahlášeny. V některých případech budou tyto seznamy součástí antispamových webů. V jiných bude web obhajující používání otevřených proxy obsahovat nejen proxy, který byl zneužíván k spamování vaší instalace wiki, ale stovky dalších proxy serverů, také otevřených pro zneužití. Je také možné blokovat registrace wiki z anonymizovaných zdrojů, jako je Tor proxy (Tor Project - torproject.org), od uživatelů bugmenotů nebo z emailových adres (uvedených na undisposable.net) určených pouze pro jednorázové použití. Seznamy blacklistů najdete také v [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] a spamfaq.net. Nezapomeňte, že seznamy určené ke snižování množství nevyžádaných emailů, pokud jsou nainstalovány, aby blokovaly spam na wiki nebo jiných webových formulářích, generují mnoho falešných poplachů. Automatické použití seznamu, který například zablokuje všechny známé bloky IP adres dynamického uživatele, může způsobit, že vaše wiki nebude použitelná. Propojení na blacklistové weby IP ze stránky [[Special:Blockip]] vaší wiki (jako výhodu pro administrátory, kteří chtějí ručně zkontrolovat, zda je problémová adresa již známým 'botem'): # Přidejte jeden řádek do {{ll|Manual:LocalSettings.php|LocalSettings.php}} a nastavte: <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # Přidejte následující text do [[MediaWiki:Blockiptext]], který chcete zobrazit: "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" Na stránku, ze které administrátoři žádají o zablokování IP, přidá pozvánku na "zkontrolovat tuto IP adresu: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Spam Forum". IP adresa je dostačující informace pro komentáře k Project Honeypot proti spambotům. Stop Forum Spam je méně vhodný pro hlášení problémů anon-IP, protože vyžaduje uživatelské jméno, IP a email, pod kterým se problémový robot pokouší zaregistrovat na vašich stránkách. Zásady a možnosti jiných webů souvisejících s černými listinami se mohou lišit. Upozorňujeme, že blokování adresy odesílání spamu na váš web není stejné jako blokování adres URL [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specifickými externími odkazy]], které jsou [[Extension:SpamRegex|spammed]] v upraveném textu. Udělejte obojí. Oba přístupy se používají v kombinaci, jako prostředek k doplnění (ale nikoli nahrazení) dalších nástrojů proti spamu, jako jsou [[Extension:TitleBlacklist|titul nebo blacklisty uživatelských jmen]] a [[Extension:ConfirmEdit|testy]], které se pokoušejí určit, zda je editace prováděná člověkem nebo robotem (captchas, [[Extension:Bad Behavior|Bad Behavior]] nebo [[Extension:AkismetKlik|Akismet]]) mohou být velmi efektivní prostředky k oddělení spambotů od skutečných, živých lidských návštěvníků. == Pokud spam vyhrál bitvu == Stále můžete vyhrát válku! MediaWiki vám k tomu nabízí nástroje. Prostě upevněte své pozice, dokud nebudete připraveni znovu zaútočit. Viz {{ll|Manual:Combating vandalism}}, a zejména [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict edit]]. Další nástroje bez podpory MediaWiki najdete v části ''Externí odkazy''. == Další nápady == Tato stránka obsahuje seznam funkcí, které jsou aktuálně zahrnuty nebo dostupné jako záplaty. Na [[Talk:Anti-spam features|diskusní stránce]] najdete mnoho dalších nápadů pro funkce, které by mohly být přidány MediaWiki nebo které jsou ve vývoji. == Související odkazy == *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === Rozšíření === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} ==== Seskupené v instalačním programu ==== Standardní tarball dostupný pro [[download]] nyní obsahuje většinu hlavních anti-spam rozšíření, včetně následujících: *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === Nastavení === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} === Externí odkazy === * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] 4pnbdry9o7l6gnu281nj8p55j4w6akn 5387484 5387471 2022-07-28T22:40:48Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{RightTOC}} Stejně jako všechny současné dynamické webové stránky jsou wikis běžným cílem pro spammery, kteří chtějí propagovat produkty nebo webové stránky. MediaWiki nabízí řadu funkcí určených k [[Special:MyLanguage/Manual:Combating vandalism|boji proti vandalismu obecně]]. Na této stránce se konkrétně zabýváme [[m:Wiki spam|wiki spamem]], který je často automatizovaný. == Přehled == Běžné nástroje používané v boji proti spamu wiki obvykle spadají do těchto kategorií: * Vyžadování přihlášení a nebo CAPTCHA u určitých operací, jako jsou úpravy, přidávání externích odkazů nebo vytváření nových uživatelů * Blokování úprav ze známých IP adres ze seznamu zakázaných nebo z adres IP, na nichž běží otevřené servery proxy * Blokování úprav, které přidávají konkrétní nechtěná klíčová slova nebo externí odkazy * Blokování specifických vzorů uživatelského jména a názvu stránky, které spamboty běžně používají * Blokování úprav novými nebo anonymními uživateli na konkrétních často cílených stránkách * Whitelisting (seznam povolených) známých editorů (jako jsou administrátoři, pravidelní přispěvatelé) a zároveň omezení pro nové nebo anonymní uživatele * Vyčištění skriptů nebo hromadné mazání ({{ll|Extension:Nuke}}) stávajících příspěvků z nedávno zakázaných spambotů Běžně se používá kombinace různých metod ve snaze udržet počet úprav spamu, robotů a otevřených proxy na minimu a zároveň omezit míru narušení způsobeného legitimním uživatelům webu. Mnoho těchto funkcí není ve výchozím nastavení aktivováno. Pokud na serveru nebo hostiteli instalujete instalaci MediaWiki, pak jste jediný, kdo může provést potřebné změny konfigurace! V každém případě požádejte své uživatele, aby vám pomohli [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|hlídat na wiki spam]] (a udělejte to sami), ale v dnešní době může spam snadno přemoci malé wiki komunity. Pomáhá trochu zvýšit tlak. Také byste si měli uvědomit, že žádné z těchto řešení nelze považovat za zcela odolné proti spamu. Efektivní praxí je pravidelně kontrolovat "{{int|recentchanges}}" ([[Special:RecentChanges]]). == Nejrychlejší řešení nejprve vyzkoušejte == Boj proti spamu by neměl být příliš tvrdý. Pokud chcete rychle a výrazně omezit spam, zkuste nejprve tyto kroky. * Nainstalujte rozšíření [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] a zablokujte známé adresy IP spamu. * Nainstalujte a nastavte základní rozšíření antivandalismu (již bylo dodáno s [[Special:MyLanguage/Download| poslední verzí]]), zejména {{ll|Extension:ConfirmEdit}}. * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Nakonfigurujte QuestyCaptcha]] a v případě potřeby [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|změňte výchozí nastavení]] pro vaši wiki. * Zapněte {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, což může být použito pro blokování specifických akcí, jako editování či zakládání účtů, pro open proxy, servery sítě Tor či VPN. Pokud problémy přetrvávají, přečtěte si další část této stránky, kde najdete další řešení, a pošlete zprávu na [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]]. == Základy nastavení antispamu == {{anchor|CAPTCHA}} === CAPTCHA === Jednou z běžnějších metod vyřazování automatických podání je použití [[w:CAPTCHA|CAPTCHA]]. Systému, který se snaží odlišit lidi od automatizovaných systémů tím, že požádá uživatele, aby vyřešil úkol, který je pro stroje obtížný. Rozšíření {{ll|Extension:ConfirmEdit|ConfirmEdit}} pro MediaWiki poskytuje rozšiřitelný rámec [[CAPTCHA]], který lze spustit na řadě událostí, včetně * všech úprav * úprav přidávajících nové, nerozpoznané externí odkazy * registrace uživatele Rozšíření se dodává se standardním testem, jedná se však o referenční implementaci a není určeno k produkčnímu použití. Operátorům Wiki, kteří instalují ConfirmEdit na veřejné wiki, se doporučuje používat jeden z modulů CAPTCHA obsažených v rozšíření (celkem jich je pět). Nejodolnější CAPTCHA, které jsou dnes k dispozici, jsou vaše vlastní otázky QuestyCaptcha. Přizpůsobte je přímo publiku vaší wiki a pravidelně je aktualizujete. ReCaptcha je v současné době poražen většinou spammerů <ref> Příklad: «Automaticky řeší captchas: GSA Captcha Breaker + Mega Ocr (řeší Recaptcha!)» Říká senukexcr. </ref>; Asirra CAPTCHA, která žádá uživatele, aby rozlišil kočky a psy, je pro uživatele obzvláště nepříjemná, ale může být účinná. Je důležité si uvědomit, že CAPTCHA mohou blokovat nejenom nežádoucí roboty. Pokud skript není schopen projít CAPTCHA, pak to také může být čtečka obrazovky nebo jiný software nebo pomoc používaná nevidomými nebo zrakově postiženými. Jednou z možností v CAPTCHA, widgetu "reCAPTCHA", je v takových případech alternativní zvukový CAPTCHA - ale někteří uživatelé počítačů selhávají při testech poslechu a čtení, takže to není úplně dobré řešení. Měli byste zvážit důsledky takové překážky a případně poskytnout alternativní prostředky pro postižené uživatele k vytváření účtů a přispívání, což je v některých jurisdikcích zákonný požadavek.<ref> Například [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Sekce 508 Standardy pro elektronické a informační technologie] </ref> Vaše wiki také nebude zcela chráněna proti spamu; [[w:CAPTCHA|podle Wikipedie]] "Spameři platí asi 0,80 až 1,20 $ za každých 1 000 vyřešených CAPTCHA společnostem zaměstnávajícím lidské řešitele v Bangladéši, Číně, Indii a mnoha dalších rozvojových zemích." Z tohoto důvodu by měl být kombinován s jinými mechanismy. ===rel="nofollow"=== Ve výchozí konfiguraci MediaWiki přidává <code>rel="nofollow"</code> k externím odkazům na wiki stránkách, což znamená, že jsou dodávány uživatelem. Mohou obsahovat spam. Proto by neměly být používány k ovlivňování algoritmů pro hodnocení stránek. Tento atribut ctí oblíbené vyhledávací nástroje, například [http://www.google.com Google]. Toto chování můžete vypnout na celém webu pomocí {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} nebo na základě jmenného prostoru pomocí konfigurační proměnné {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}}. Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. == Rutina antispamu: opatření na míru == Každý spammer je jiný. I když všichni vypadají nudně podobně. Pokud obecná protiopatření nestačí, použijte před extrémními kroky nástroje, které vám umožní řešit konkrétní problémy, které máte. {{anchor|Individual page protection}} === Ochrana jednotlivých stránek === Spamboty často opakovaně zasáhnou stejnou stránku. Běžné vzory pozorované u pagenů vytvořených pomocí spambotů zahrnují diskusní stránku, často mimo hlavní prostor (např. Category_talk: jsou málo používány, takže si vytvoří společné cíle) a další diskusní stránky. Nejvíce jsou zneužívány úpravy na wiki, které k úpravám nevyžadují registraci. Pocházejí z anonymních zdrojů. Blokováním úprav na těchto konkrétních stránkách, komukoli jinému než zavedeným uživatelům, může zabránit opětovnému vytvoření spamových výpisů. Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === Filtr zneužívání === {{ll|Extension:AbuseFilter}} (filtr zneužití) umožňuje privilegovaným uživatelům vytvářet pravidla zacílená na konkrétní typ spamu, který vaše wiki přijímá. Může pomoci automaticky zabránit akci nebo blokovat uživatele. Může prozkoumat mnoho vlastností úprav. Například uživatelské jméno, věk uživatele, přidaný text, přidané odkazy atd. Nejúčinnější je v případech, kdy máte jednoho nebo více kvalifikovaných administrátorů, kteří jsou ochotni vám pomoci v boji proti spamu. Filtr zneužití může být účinný i proti spammerům podporovaným člověkem, ale vyžaduje nepřetržitou údržbu, aby reagoval na nové typy útoků. Příklady boje proti automatickému spamu lze nalézt v [[Manual:Combating spam/AbuseFilter examples|Příručce:Příklady boje proti spamu / Příklady filtru zneužití]]. === Seznam spamů (SpamBlacklist)=== Výše uvedený přístup bude příliš těžkopádný, pokud se pokusíte blokovat větší množství spamových adres URL. Lepším přístupem je dlouhá černá listina identifikující mnoho známých spamových adres URL. Populární rozšíření pro MediaWiki je rozšíření {{ll|Extension:SpamBlacklist|SpamBlacklist}}, které blokuje úpravy, které přidávají na stránky adresy URL uvedené na černé listině: Umožňuje vytvoření takovéhoto seznamu na wiki s pomocí privilegovaných uživatelů a umožňuje použití seznamů získaných z externích zdrojů (ve výchozím nastavení , používá rozsáhlý [[m:Spam blacklist]]). Rozšíření {{ll|Extension:TitleBlacklist|TitleBlacklist}} (̝černá listina spamů) může být také užitečné, jako prostředek k zabránění opětovného vytvoření konkrétních skupin stránek, které používají 'bots k výpisu odkazových spamů. === Otevřené proxy === Otevřený server proxy je nebezpečný zejména proto, že se používá jako způsob, jak obejít protiopatření zaměřená na konkrétního narušitele. Viz také [[m:No open proxies|Žádné otevřené servery proxy]]. Existují někteří roboti, např. na Wikimedia wikis, detekující a blokující otevřené IP proxy. Jejich kód často není veřejný. Většina takových bloků, když si všimnete zneužití, se provádí ručně. Je proto důležité vědět, zda zneužívající IP je otevřený proxy server nebo něco jiného, aby se rozhodlo, jak se s tím vypořádat. Zejména, pokud se jedná o adresu IP používanou registrovaným uživatelem, získanou pomocí rozšíření {{ll|Extension:CheckUser|CheckUser}}. Několik rozšíření, zejména rozšíření {{ll|Extension:Tor block|Tor block}}, blokuje řadu otevřených proxy serverů. Od verze 1.22 je k dispozici {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}}, pro zvýšení účinnosti bloků. == Tvrdá opatření == Následující opatření jsou určena pro technicky zdatnější systémové správce, kteří vědí, co dělají: Je těžší je správně nastavit a monitorovat. Pokud jsou implementovány špatně, mohou být příliš staré na to, aby byly stále účinné, nebo dokonce pro vaši wiki kontraproduktivní. === $wgSpamRegex === MediaWiki poskytuje prostředky k filtrování textu úprav za účelem blokování nežádoucích doplňků prostřednictvím konfigurační proměnné <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code>. Můžete ji použít k blokování dalších úryvků textu nebo značek spojených s běžnými útoky na spam. Obvykle se používá k vyloučení adres URL (nebo částí adres URL), na které nechcete uživatele odkazovat. Uživatelé dostanou vysvětlující zprávu uvádějící, která část jejich upravovaného textu není povolena. {{ll|Extension:SpamRegex}} umožňuje editaci této proměnné na wiki. <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> Tím se zabrání jakékoli zmínce o 'online kasinu' nebo 'buy-viagra' nebo 'adipex' nebo 'phentermine'. '/i' na konci způsobí, že na případné vyhledávání nebude citlivý. Blokuje také úpravy, které se pokouší přidat skryté nebo přetékající prvky, což je běžný "trik" používaný při mnoha hromadných útocích, které se pokouší skrýt spam před diváky. === Změny konfigurace Apache === Kromě změny konfigurace MediaWiki, pokud používáte MediaWiki na Apache, můžete provést změny v konfiguraci webového serveru Apache, abyste zabránili spamu. Tato nastavení jsou obvykle umístěna do konfiguračního souboru virtuálního hostitele nebo do souboru s názvem [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] na stejném místě jako LocalSettings.php (Upozorňujeme, že pokud máte sdíleného webového hostitele, musí povolit AllowOverride, aby vám umožnil použití souboru .htaccess). ==== Filtrování podle agenta uživatele ==== Když na své wiki zablokujete spamera, prohledejte protokol přístupu svého webu podle IP adresy a zjistěte, který řetězec uživatelského agenta daná IP adresa poskytla. Například: :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> Tím se vrátí chyba 403 Zakázané na jakoukoli adresu IP s uživatelským agentem, který odpovídá zadanému regulárnímu výrazu. Dbejte na to, abyste v řetězci uživatelského agenta vynechali všechny nezbytné znaky regulárního výrazu, například . ( ) - se zpětnými lomítky (\). Chcete-li spárovat prázdné uživatelské agenty, stačí použít "^$". I když je řetězec agenta spammeru používán skutečnými prohlížeči, pokud je starý nebo málokdy se vyskytující, můžete použít pravidla přepsání k přesměrování uživatelů na chybovou stránku a doporučit jim, aby aktualizovali svůj prohlížeč: <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> ==== Zabránění blokovaným spammerům ve spotřebovávání zdrojů ==== Trvalý spammer nebo ten s poškozeným skriptem se může i nadále pokoušet spamovat vaši wiki poté, co byla zablokována, a zbytečně tak spotřebovávat zdroje. Přidáním pragmy [http://httpd.apache.org/docs/2.2/howto/access.html deny from], jako je následující, do souboru <code>.htaccess</code>, můžete jim zabránit v načítání stránek vůbec a místo toho vrátit 403 Zakázaná chyba: <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> === Černé seznamy adres IP === Většina nejproblematičtějších spamů přijímaných na webech MediaWiki pochází z adres, které ostatní webmasteři dlouho nazývají bot nebo otevřené proxy servery, ačkoli pro to existují pouze neoficiální důkazy. Tito roboti obvykle generují velké množství automatických registrací na webech fóra, komentují spam na blogu a vandalismus na stránkách wikis: Nejčastěji linkspam, ačkoli existující obsah je někdy prázdný, doplněný náhodnými blábolícími znaky nebo upravován takovým způsobem, aby rozbil stávající Unicode text. Poměrně jednoduchý [[#CAPTCHA|CAPTCHA]] může problém významně snížit, protože může blokovat vytvoření [[#Individual page protection|určitých často nevyžádaných stránek]]. Tato opatření však problém nevylučují a zpřísnění bezpečnosti pro všechny uživatele v určitém okamžiku způsobí nepohodlí legitimních přispěvatelů. Může být vhodnější namísto spoléhání se výhradně na CAPTCHA nebo jiná preventivní opatření, která ovlivňují všechny uživatele, zaměřit se konkrétně na IP adresy, o nichž již ostatní mistři stránek vědí, že jsou útočištěm net.abuse. Mnoho seznamů je již k dispozici, například [http://www.stopforumspam.com/downloads stopforumspam.com] obsahuje seznam "All IPs in CSV" (všech IP v CSV), který (od února 2012) obsahuje asi 200 000 IP známých spambotů. ==== Využití procesoru CPU a přetížení ==== Uvědomte si, že když se při pokusech o úpravy nebo zobrazení stránek provádí mnoho kontrol, roboti mohou snadno přetížit vaši wiki a narušit ji více, než pokud by nebyla chráněna. Sledujte náklady na ochranu svých zdrojů. ==== DNSBL ==== Můžete nastavit MediaWiki, aby zkontrolovala každou editovací IP adresu proti jednomu nebo více DNSBL (blacklistům založeným na DNS), což nevyžaduje žádnou údržbu, ale mírně zvyšuje latenci úprav. Například můžete přidat tento řádek do LocalSettings.php a blokovat tak mnoho otevřených proxy serverů a známých spammerů: <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. ==== Špatné chování a projekt HoneyPot ==== Špatné chování je první obranná linie blokující všechny požadavky známých spammerů identifikovaných pomocí HTTP hlaviček, IP adresy a dalších metadat. Je k dispozici jako rozšíření MediaWiki, viz {{ll|Extension:Bad Behavior}}. Pro maximální účinnost by měla být kombinována s [http://www.projecthoneypot.org/httpbl.php http:BL API Key], které můžete získat na [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], distribuovaného projektu sledování spamu. Chcete-li se připojit k projektu HoneyPot, musíte do svého webového serveru přidat veřejně přístupný soubor a pomocí následujícího kódu rozšíření ve vašem LocalSettings.php (nebo přiloženém souboru PHP) vložit odkaz na každou stránku: {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> Nastavte $wgHoneyPotPath na cestu stránky honeypot v LocalSettings.php (např. "/ciralix.php"). Můžete změnit podobu výše uvedeného odkazu na kteroukoli z alternativ navržených v Project HoneyPot. Možná se budete muset přihlásit do Project HoneyPot, abyste viděli tyto alternativní způsoby, jak učinit odkazy honeypot neviditelné pro člověka.[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] Jakmile se zaregistrujete, zvolte Services&rarr;HTTP Blacklist, abyste získali http:BL API Key, a vložte svůj klíč do nastavení Bad Behavior's.ini. ==== $wgProxyList ==== {{Warning|1=Tato konkrétní technika, pokud je seznam IP velký, podstatně zvýší dobu načítání stránky a zatížení serveru. Používejte ji opatrně.}} Proměnnou {{wg|ProxyList}} můžete nastavit na seznamu IP, které chcete zakázat. Tento lze pravidelně naplňovat z externího zdroje pomocí skriptu cron, jako je například následující: <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> Poté nastavíte v LocalSettings.php: <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> Možná budete chtít uložit tyto příkazy do souboru nazvaného např. <code>updateBannedIPs.sh</code>, takže jej můžete spouštět pravidelně. Můžete také použít řešení '''pouze pro PHP''' (PHP-only) a stáhnout ip-list ze stopforumspamu. Za tímto účelem zkontrolujte dostupný skript PHP [http://www.pschmidt.it/vim_source/updateBanned_php.txt zde]. Pokud tak učiníte a pro ukládání do mezipaměti používáte mezipaměť APC, možná budete muset zvýšit velikost apc.shm_size ve vašem php.ini, abyste se přizpůsobili tak velkému seznamu. Právě jste zakázali sto čtyřicet tisíc spammerů. Doufejme, že to nebude mít žádný rušivý účinek na vaše legitimní uživatele. Řekli jste "adieu" mnoha nejhorším známým spammerům na internetu. Dobrý riddance! To by mělo problém trochu uklidnit. Alespoň na chvíli… ==== Honeypots, DNS BLs and HTTP BLs ==== 140 000 mrtvých spammerů. Není to špatné, ale jakýkoli správný [[w:Bastard Operator From Hell|BOFH]] by se v tuto chvíli nudil a dychtivě by hledal 140 001 IP spamů, který by se náhodně zablokoval. A proč ne? Naštěstí jsou k dispozici dynamicky aktualizované seznamy spambotů, otevřených proxy serverů a dalších problémových IP adres. Mnohé také umožňují automatickou kontrolu uživatelských jmen nebo emailových adres (pro přihlášené uživatele) proti stejným blacklistům. Jednou formou černé listiny, kterou mohou správci MediaWiki znát, je DNS BL. Seznam serverů DNS hostovaný na serveru doménových jmen je databáze adres IP. Hledání adresy určuje, zda IP, která se pokouší zaregistrovat nebo upravit, je již známým zdrojem zneužití sítě. Možnosti {{wg|EnableDnsBlacklist}} a {{wg|DnsBlacklistUrls}} v MediaWiki poskytují primitivní příklad přístupu k černé listině DNS. Nastavte následující nastavení v {{ll|Manual:LocalSettings.php|LocalSettings.php}} a IP adresy uvedené jako HTTP spam jsou blokovány: <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> Černá listina DNS funguje takto: * Wiki obdrží žádost o úpravu nebo registraci nového uživatele z nějaké náhodné adresy IP (například ve formátu '123.45.67.89'). * Čtyři bajty IP adresy jsou umístěny v obráceném pořadí, poté následuje název požadovaného serveru černé listiny DNS. * Výsledná adresa je vyžadována ze serveru pro doménové jméno (v tomto příkladu '89.67.45.123.zen.spamhaus.org.' a '89.67.45.123.dnsbl.tornevall.org.'). * Server není nalezen (NXDOMAIN), pokud adresa není na černé listině. Pokud je na některém z blacklistů, je úprava blokována. Vyhledávání v externě hostované černé listině obvykle přidává ne více než několik sekund k času potřebnému k uložení úprav. Na rozdíl od nastavení $1, které musí být načteno na každé stránce čtené nebo zapisované, se použití černé listiny DNS provádí pouze během registrace nebo úprav stránek. Tím není ovlivněna rychlost, jakou může systém obsluhovat požadavky na čtení stránky (většinu vašeho provozu). Na rozdíl od nastavení {{wg|ProxyKey}}, které musí být načteno na každé stránce čtené nebo zapisované, se použití černé listiny DNS provádí pouze během registrace nebo úprav stránek. Tím není ovlivněna rychlost, jakou může systém obsluhovat požadavky na čtení stránky (většinu vašeho provozu). Zatímco původní SORBS byl primárně určen pro řešení otevřených webových proxy a emailového spamu, existují i ​​jiné seznamy specifické pro webový spam (fóra, komentáře k blogům, úpravy wiki), které mohou být proto vhodnější: * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] funguje velmi podobným způsobem jako SORBS DNSBL, ale zacílí na otevřené proxy a spam ve webové podobě. Většina jeho obsahu je konsolidována z jiných existujících seznamů zneužívajících IP. * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] se konkrétně zaměřuje na roboty, kteří shromažďují emailové adresy z webových stránek pro hromadné seznamy emailů, zanechávají komentářový spam nebo se pokoušejí ukrást hesla pomocí útoků ze slovníku. Vyžaduje uživatelský registr u projecthoneypot.org pro 12místný klíč API. Pokud by tento klíč (například) byl 'myapitestkey', vyhledávání by jinak vypadalo jako '89.67.45.123.http.dnsbl.sorbs.net.' nebo '89.67.45.123.opm.tornevall.org.' bude muset být 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.'. * Seznamy povolených webů mohou identifikovat emailové adresy a informace o uživateli spamu i přes jednoduchou adresu IP, ale neexistuje standardní formát pro odpověď ze serveru se seznamem HTTP. Například žádost o [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] by vrátila "Y|IP|4", pokud je adresa na černé listině ('N' nebo prázdná, pokud je v pořádku), zatímco webová žádost o [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] by vrátila "ip yes 2009-04-16 23:11:19 41" pokud je adresa na blacklistu (čas, datum a počet lze ignorovat) nebo prázdná, pokud je adresa v pořádku. Bez jediného standardního formátu, kterým server černé listiny odpovídá na dotaz, neexistuje v balíčku MediaWiki integrovaná podpora pro většinu online seznamů známých spambotů. Neschopnost určit více než jeden server černé listiny dále omezuje užitečnost vestavěných možností $1 a $2. Od $rev bylo MediaWiki schopno kontrolovat více DNSBL definováním $3 jako pole. Neschopnost určit více než jeden server černé listiny dále omezuje užitečnost vestavěných možností {{wg|EnableDnsBlacklist}} a {{wg|DnsBlacklistUrls}}. Od [[rev:58061]] bylo MediaWiki schopno kontrolovat více DNSBL definováním <code>$wgDnsBlacklistUrls</code> jako pole. Většina operátorů černých listin poskytuje velmi omezenou softwarovou podporu (často cílenou na aplikace jiné než wiki, jako je phpBB nebo Wordpress). Protože stejné spamboty vytvářejí podobné problémy na většině webů s otevřeným obsahem, nejhorší pachatelé útočící na weby MediaWiki budou také usilovně cílit na tisíce webů bez wiki se spamem v komentářích blogu, příspěvcích na fóru a v knihách návštěv. Automatický dotaz na více webů na černé listině je proto již široce používán při ochraně různých jiných forem webů s otevřeným obsahem a jména spambotů, řad a IP adres jsou již nyní příliš dobře známá. Zdá se, že za velkým procentem celkového problému je relativně malý počet spambotů. I v případě, že administrátoři nepřijímají zajatce, existuje vzor, ve kterém stejná spambotová IP, která před sekundou zveřejnila linkspam na wiki, spamuje blogové komentáře někde jinde a bude mít spamovací příspěvky na fóru pár sekund od nynějška na místě vzdáleném půl světa. To si pořádně zapamatujte. Jeden sdílený externí záznam na černé listině může umlčet jednoho problematického 'robota' od zveřejnění na tisících webů. Tím se výrazně snižuje počet jednotlivých IP adres, které je třeba ručně blokovat a to vždy na jedné wiki a na jednom fóru, místními administrátory. ==== Ale co je to s honeypoty? ==== Některé weby zabývající se nevyžádanou poštou, například projecthoneypot.org, poskytují kód, kterým jste vyzváni k zahrnutí na své vlastní webové stránky. Stránky obvykle obsahují jednu nebo více jedinečných, náhodných a skrytých emailových adres nebo odkazů, které nejsou určeny pro vaše lidské návštěvníky, ale pro spamboty. Při každém zobrazení stránky se vložené adresy automaticky změní, což umožňuje, aby jednotlivé části spamu byly přímo a přesvědčivě přiřazeny k IP adrese robotů, kteří získávali adresy z vašich stránek. IP adresa, kterou robot použil k prohlížení vašich stránek, je automaticky předána provozovatelům černé listiny. Odkaz na falešný 'komentář' nebo 'knihu návštěv' je často skrytý jako past do robotů, kteří odesílají spam do webových formulářů. Viz [[w:Honeypot_(computing)|Honeypot (computing)]]. Jakmile bude adresa spammeru známa, bude přidána na černé listiny (viz výše), takže vy i ostatní budete mít v budoucnu na svých stránkách o jednoho nežádoucího robotického návštěvníka méně. Zatímco skripty a servery černé listiny mohou automatizovat většinu úkolů identifikace a řešení spambotových IP adres, většina webů na černé listině poskytuje odkazy na webové stránky, na kterých lze ručně vyhledat informace o IP adrese nebo nahlásit zneužívající IP jako spambot. Může být vhodné zahrnout některé z těchto odkazů na speciální: Blokové stránky vaší wiki pro pohodlí administrátorů vašeho webu. ==== Další seznamy proxy a spambotů IPs==== Zpravidla zadáním adresy libovolného robota nebo otevřeného proxy serveru do vyhledávače se vrátí mnoho seznamů, na kterých byly tyto zneužívající adresy IP již nahlášeny. V některých případech budou tyto seznamy součástí antispamových webů. V jiných bude web obhajující používání otevřených proxy obsahovat nejen proxy, který byl zneužíván k spamování vaší instalace wiki, ale stovky dalších proxy serverů, také otevřených pro zneužití. Je také možné blokovat registrace wiki z anonymizovaných zdrojů, jako je Tor proxy (Tor Project - torproject.org), od uživatelů bugmenotů nebo z emailových adres (uvedených na undisposable.net) určených pouze pro jednorázové použití. Seznamy blacklistů najdete také v [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] a spamfaq.net. Nezapomeňte, že seznamy určené ke snižování množství nevyžádaných emailů, pokud jsou nainstalovány, aby blokovaly spam na wiki nebo jiných webových formulářích, generují mnoho falešných poplachů. Automatické použití seznamu, který například zablokuje všechny známé bloky IP adres dynamického uživatele, může způsobit, že vaše wiki nebude použitelná. Propojení na blacklistové weby IP ze stránky [[Special:Blockip]] vaší wiki (jako výhodu pro administrátory, kteří chtějí ručně zkontrolovat, zda je problémová adresa již známým 'botem'): # Přidejte jeden řádek do {{ll|Manual:LocalSettings.php|LocalSettings.php}} a nastavte: <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # Přidejte následující text do [[MediaWiki:Blockiptext]], který chcete zobrazit: "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" Na stránku, ze které administrátoři žádají o zablokování IP, přidá pozvánku na "zkontrolovat tuto IP adresu: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Spam Forum". IP adresa je dostačující informace pro komentáře k Project Honeypot proti spambotům. Stop Forum Spam je méně vhodný pro hlášení problémů anon-IP, protože vyžaduje uživatelské jméno, IP a email, pod kterým se problémový robot pokouší zaregistrovat na vašich stránkách. Zásady a možnosti jiných webů souvisejících s černými listinami se mohou lišit. Upozorňujeme, že blokování adresy odesílání spamu na váš web není stejné jako blokování adres URL [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specifickými externími odkazy]], které jsou [[Extension:SpamRegex|spammed]] v upraveném textu. Udělejte obojí. Oba přístupy se používají v kombinaci, jako prostředek k doplnění (ale nikoli nahrazení) dalších nástrojů proti spamu, jako jsou [[Extension:TitleBlacklist|titul nebo blacklisty uživatelských jmen]] a [[Extension:ConfirmEdit|testy]], které se pokoušejí určit, zda je editace prováděná člověkem nebo robotem (captchas, [[Extension:Bad Behavior|Bad Behavior]] nebo [[Extension:AkismetKlik|Akismet]]) mohou být velmi efektivní prostředky k oddělení spambotů od skutečných, živých lidských návštěvníků. == Pokud spam vyhrál bitvu == Stále můžete vyhrát válku! MediaWiki vám k tomu nabízí nástroje. Prostě upevněte své pozice, dokud nebudete připraveni znovu zaútočit. Viz {{ll|Manual:Combating vandalism}}, a zejména [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict edit]]. Další nástroje bez podpory MediaWiki najdete v části ''Externí odkazy''. == Další nápady == Tato stránka obsahuje seznam funkcí, které jsou aktuálně zahrnuty nebo dostupné jako záplaty. Na [[Talk:Anti-spam features|diskusní stránce]] najdete mnoho dalších nápadů pro funkce, které by mohly být přidány MediaWiki nebo které jsou ve vývoji. == Související odkazy == *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === Rozšíření === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} ==== Seskupené v instalačním programu ==== Standardní tarball dostupný pro [[download]] nyní obsahuje většinu hlavních anti-spam rozšíření, včetně následujících: *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === Nastavení === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} === Externí odkazy === * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] mz81i3b7nq0gpw4upwde1t39s791bz5 Translations:Manual:Combating spam/110/cs 1198 1083830 5387483 3747465 2022-07-28T22:40:47Z Shirayuki 472859 update wikitext text/x-wiki Několik rozšíření, zejména rozšíření $1, blokuje řadu otevřených proxy serverů. 92faqc3nsizl3y6o4st961twfvjft6h Extension:TemplateData/de 102 1090387 5386972 5378114 2022-07-28T19:49:42Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type of Parameter</span> |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] efix5epxzwv6ke7rik8khhprp0y2y1x 5386974 5386972 2022-07-28T19:49:44Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type of Parameter</span> |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] m07vrlb4pe3n8yesguz7nycc6onjffp 5386976 5386974 2022-07-28T19:49:48Z ThisCarthing 17456337 Created page with "Standard" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type of Parameter</span> |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] qm9e3a7cpia2q7hmo4rxbbwq2x6pok3 5386978 5386976 2022-07-28T19:49:53Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type of Parameter</span> |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 7ayi0lsbof08zwczgfi8fc28ktxh4u4 5386980 5386978 2022-07-28T19:49:58Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type of Parameter</span> |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 3zf9w0fi6ue83ybdmvzqi3h62xia1km 5386982 5386980 2022-07-28T19:50:13Z ThisCarthing 17456337 Created page with "Art des Parameter" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art des Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] eyuiq03m733r94ki3mro42opzk6egkd 5386984 5386982 2022-07-28T19:50:21Z ThisCarthing 17456337 wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] ja7p2cp9t8eprmpjiu4ucx64zd93fz0 5386986 5386984 2022-07-28T19:50:34Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] h599quwol503sipmc0ea93zby7wfe3e 5386988 5386986 2022-07-28T19:50:39Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] m1d8q7g4gn9c92fs02y4dd4m5n3telx 5386990 5386988 2022-07-28T19:50:43Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] cazlncgsr58sr7r6wgnzras7aalz07s 5386992 5386990 2022-07-28T19:50:47Z ThisCarthing 17456337 Created page with "Standard" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] dmbnpmo1bslrlwf4hwievhducl1t4d0 5386994 5386992 2022-07-28T19:50:54Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 909n0vbj4911rcmqd113ete8fevs0lb 5386996 5386994 2022-07-28T19:50:58Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] kr73xrcayyfl797aerlrnorkh70ir75 5386998 5386996 2022-07-28T19:51:02Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 3hk651ikd5krulkhftop2ghn9clbnpi 5387000 5386998 2022-07-28T19:51:07Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! <span lang="en" dir="ltr" class="mw-content-ltr">Value</span> |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 6ytzp7o2odww5ulohic8m46svk9cfhr 5387002 5387000 2022-07-28T19:51:10Z ThisCarthing 17456337 Created page with "Wert" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] pp8lx6eupe61zncnf25zw98aranpfo0 5387004 5387002 2022-07-28T19:51:29Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] qwpxwqco8tqzlhnm06nou043nxcw6ro 5387006 5387004 2022-07-28T19:51:33Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 9ghq4ks4d72plcwesde7nsxccra1d6y 5387009 5387006 2022-07-28T19:51:41Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] epirj47zbsudokgn8b8m5bt9mhns2pi 5387011 5387009 2022-07-28T19:51:49Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] olyln4ee76pfg3pfr0ocnmob9eq18sb 5387014 5387011 2022-07-28T19:51:53Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>title</code> | <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Key</span> !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] f01fsbg58c7xjkflru5c1zf3f70jgmy 5387016 5387014 2022-07-28T19:52:02Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>title</code> | Zeichenkette | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! Schlüssel !! <span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] qz9geu7wnbt8qu297ezc8848ro5is3j 5387018 5387016 2022-07-28T19:52:05Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>title</code> | Zeichenkette | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] <span lang="en" dir="ltr" class="mw-content-ltr">or</span> <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 0iu11ea4posx7i4xb6x18bpgfr4jmqk 5387020 5387018 2022-07-28T19:52:10Z ThisCarthing 17456337 Created page with "oder" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>title</code> | Zeichenkette | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 7tiw0uzmos219xyhrebpys23i5cko1s 5387022 5387020 2022-07-28T19:52:16Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>title</code> | Zeichenkette | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] jxyim6elxvn45u1oms14ayvr4416iis 5387024 5387022 2022-07-28T19:52:20Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>title</code> | Zeichenkette | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Variable</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] cpt1madxp14iboxz3q3cc861o0b2n6j 5387026 5387024 2022-07-28T19:52:26Z ThisCarthing 17456337 Created page with "Variable" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>title</code> | Zeichenkette | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! Variable ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] lh3745ywztztvy3fodbr6ebhu6nf9nz 5387028 5387026 2022-07-28T19:52:29Z ThisCarthing 17456337 Created page with "Standard" wikitext text/x-wiki <languages/> {{Bundled|1.35}} {{Extension |status = stable |image = Screenshot of TemplateData extension.png |type1 = tag |type2 = api |author = [[User:Krinkle|Timo Tijhof]], [[User:Mooeypoo|Moriel Schottlender]], [[User:Jdforrester (WMF)|James Forrester]], [[User:Trevor Parscal|Trevor Pascal]], [[User:Matma Rex|Bartosz Dziewoński]], Marielle Volz, ... |description = Ermöglicht Informationen über Templates zu speichern, abzurufen und zu visualisieren |update = Kontinuierliche Aktualisierungen |mediawiki = 1.25+ |compatibility policy = rel |php = 5.4+ |download = {{WikimediaDownload|TemplateData|phab=ETDA}} |needs-updatephp = No |readme = |phabricator = TemplateData |tags = {{tag|templatedata|open}} }} Die Erweiterung '''TemplateData''' stellt den Tag {{tag|templatedata|open}} und eine API zur Verfügung, die es Redakteuren ermöglicht zu bestimmen, wie die Templates aufgerufen werden sollen. Diese Informationen sind als schön formatierte Tabelle für die Endbenutzer und als JSON-API verfügbar. Dadurch können andere Programme (z. B. [[VisualEditor]]) Schnittstellen für die Arbeit mit Templates und ihren Parametern erstellen. Siehe {{ll|Help:TemplateData|Hilfe:TemplateData}} für eine detaillierte Hilfe. == Installation == {{ExtensionInstall |registration=required }} == Bearbeitung von Daten == Die TemplateData-Erweiterung funktioniert, indem ein {{tag|templatedata|open}}-Tag im Wikitext einer Vorlagenseite definiert wird (optional kann es auch von einer anderen Seite transkludiert werden). Dies ist so konzipiert, dass es mit dem in vielen Wikis üblichen Layout kompatibel ist, bei dem die Vorlagendokumentation auf einer separaten Seite eingebunden wird (ist aber nicht erforderlich). Der Inhalt des {{tag|templatedata|open}}-Tags muss gültiges JSON im unten beschriebenen Format sein; beachten Sie, dass '''alle Beschreibungen im Klartext''' sein müssen (innerhalb der Vorlagendaten wird kein Wikitext akzeptiert). Wenn ein {{tag|templatedata|open}}-Block auf einer Seite enthalten ist, führt die TemplateData-Erweiterung beim Speichern der Seite die folgenden Prüfungen durch: # Der Inhalt muss gültiges JSON sein; # Jedes Element innerhalb der JSON-Struktur muss vom erwarteten Typ sein, wie unten angegeben (z. B. Objekt, Array oder Primitiv); und # Für die Elemente, die eine bestimmte Liste möglicher Werte haben (z. B. <code>params.yourParameterName.type</code>), muss der Wert im JSON-Objekt einem dieser Werte entsprechen. <div lang="en" dir="ltr" class="mw-content-ltr"> If any of these checks fails, the server will not be permitted saving and an error message will be displayed above the edit page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For autovalue items, [[bugzilla:2700|bug 2700]] prevents <code>subst:</code> from working in any template that is added inside a {{tag|tag|open}}, including {{tag|ref|open}} and {{tag|gallery|open}} tags.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The TemplateData block will save correctly, but the resulting wikitext will not be parsed correctly when the template is used.</span> Beachten Sie, dass Sie nicht <code><nowiki>{{#tag:templatedata}}</nowiki></code> anstelle von {{tag|templatedata|open}} verwenden können. ===Format=== Nachfolgend sehen Sie eine visualisierte Version der JSON-Daten, wie sie auf der Vorlagenseite definiert und von {{tag|templatedata|content=}}-Tags umgeben sind. Die formale Spezifikation ist im TemplateData-Repository verfügbar. Die neueste Version finden Sie in [https://github.com/wikimedia/mediawiki-extensions-TemplateData/blob/master/Specification.md Specification.md]. {{anchor|TemplateData object|TemplateData Object}} ==== TemplateData-Objekt ==== Das TemplateData-Objekt ist ein "JSON-Wurzelelement", das in einem {{tag|templatedata|open}}-Element auf der Vorlagenseite enthalten ist. {| class="wikitable" |- ! Schlüssel ! Typ ! Beschreibung |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> | Eine kurze Beschreibung der Vorlage. '''Es muss im Klartext sein'''. Sobald sie ausgefüllt ist, kann sie bei der Bearbeitung einer einzelnen Vorlage als Beschriftung angezeigt werden und vielleicht auch in den Suchergebnissen, wenn Nutzer eine von vielen Vorlagen auswählen. Der Standardwert ist <code>null</code>. |- | <code>params</code> | Objekt, das [[#Param object|Param-Objekte]] enthält | Ein Objekt, das jeden Parameternamen der Vorlage einem entsprechenden [[#Param object|Param-Objekt]] zuordnet, das die Eigenschaften dieses Parameters beschreibt. |- | <code>paramOrder</code> | Array mit Zeichenfolgen für Parameternamen | Die logische Reihenfolge, in der die Parameter angezeigt werden sollen. Das Array enthält jeden Parameterschlüssel genau einmal. Jeder String muss ein gültiger Schlüssel im <code>params</code>-Objekt sein. |- | <code>sets</code> | Array mit <br/>[[#Set object|Set-Objekten]] | Ein Array mit Set-Spezifikationen. Ein Set ist eine Gruppe von Parametern, die zusammen verwendet werden sollten. Der Standardwert ist []. Beachten Sie, dass sich die <code>sets</code>-Funktionalität noch in der Entwicklung befindet. |- | <code>format</code> | Zeichenkette, entweder <code>inline</code> oder <code>block</code> | Wie die Wikitext-Darstellung der Vorlage gestaltet sein SOLLTE. Der Standardwert ist <code>inline</code>. <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Help:TemplateData#Custom_formats|#Custom_formats]] for other custom formats.</span> |- | <code>maps</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A [[#Maps object|Maps object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a simplified name of a third party consumer of the template data (i.e. [[Citoid]], [[Special:MyLanguage/Wikidata]], etc.) to an object that in turn maps a name of a consumer parameter to one or more corresponding names of template parameters.</span> |} {{anchor|Param object|Parameter Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Param object ==== </div> {| class="wikitable" |- ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>description</code> | [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> | <span lang="en" dir="ltr" class="mw-content-ltr">A brief description of the parameter, for users to know which to pick from an option list.</span> |- | <code>required</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is required for the template to work (true if this parameter '''must''' be specified).</span> |- | <code>suggested</code> | Wahrheitswert | style="text-align: center;" | <code>false</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is suggested for the template to be useful (true if this parameter '''should''' be specified).</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette | style="text-align: center;" | <code>false</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Whether the parameter is deprecated.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value can be a string of instructions giving the user guidance what instead can be done, or be simply <code>true</code>.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array containing strings</span> | style="text-align: center;" | <code>[]</code> || <span lang="en" dir="ltr" class="mw-content-ltr">List of aliases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alias is an alternative name for the parameter that may be used instead of (not in addition to) the primary name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Aliases are not documented in a separate Parameter object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If they need more information, they should be in their own property marked "deprecated".</span> |- | <code>default</code> || [[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The default value used by the template if no value is assigned to the parameter, or a description thereof.</span> |- | <code>autovalue</code> || Zeichenkette | style="text-align: center;" | <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">A dynamically-generated default value in wikitext, such as today's date or the editing user's name; this will often involve wikitext substitution, such as <code><nowiki>{{subst:CURRENTYEAR}}</nowiki></code>.</span> |- |<code>example</code> |[[#InterfaceText (string or object)|InterfaceText]] | style="text-align: center;" | <code>null</code> |<span lang="en" dir="ltr" class="mw-content-ltr">An example text for the parameter, to help users fill in the proper value.</span> |- | <code>type</code> || Zeichenkette | style="text-align: center;" | <code>"unknown"</code> || <span lang="en" dir="ltr" class="mw-content-ltr">The type of the parameter, for (soft) type hinting. One of:</span> {| class="wikitable" id="parameter types" |- ! <span lang="en" dir="ltr" class="mw-content-ltr">String Value</span> !! Art von Parameter |- | "unknown" || <span lang="en" dir="ltr" class="mw-content-ltr">Assumed type if not set</span> |- | "number" || <span lang="en" dir="ltr" class="mw-content-ltr">Any numerical value (without decimal points or thousand separators)</span> |- | "string" || <span lang="en" dir="ltr" class="mw-content-ltr">Any textual value. May contain line breaks.</span> |- | "line" || <span lang="en" dir="ltr" class="mw-content-ltr">Short text field – use for names, labels, and other short-form fields.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is supposed to be text that is not expected to contain line breaks.</span> |- | "boolean" || <span lang="en" dir="ltr" class="mw-content-ltr">A boolean value ('1' for true, '0' for false, '<nowiki/>' for unknown), see [[wikipedia:Three-valued logic|three-valued logic]].</span> |- | "date" || <span lang="en" dir="ltr" class="mw-content-ltr">A date in ISO 8601 format, e.g. "2014-05-09" or "2014-05-09T16:01:12Z"</span> |- | "url" || <span lang="en" dir="ltr" class="mw-content-ltr">A URL, including protocol, e.g. <nowiki>"http://www.example.org", "https://example.org", or "//example.org"</nowiki>.</span> |- | "wiki-page-name" || <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki page name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid page name which could be created.</span> |- | "wiki-file-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki file name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid file name which could be uploaded.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo.svg" not "File:Foo.svg" or "Bild:Foo.svg").</span> |- | "wiki-template-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki Template name for the current wiki.</span> |- | "wiki-user-name" | <span lang="en" dir="ltr" class="mw-content-ltr">A valid MediaWiki user name for the current wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Doesn't have to exist, but if not, should be a valid user name which could be created.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should not include the namespace (''e.g.'' "Foo" not "User:Foo" or "Usario:Foo").</span> |- | "content" || <span lang="en" dir="ltr" class="mw-content-ltr">Page content in wikitext, such as text style, links, images, ''etc.''</span> |- | {{nowrap|"unbalanced-wikitext"}} || <span lang="en" dir="ltr" class="mw-content-ltr">Raw wikitext that should not be treated as standalone content because it is unbalanced – for example, templates concatenating incomplete wikitext as a bigger whole, such as <code><nowiki>{{echo|before=<u>|after=</u>}}</nowiki></code></span> |} |- | <code>inherits</code> || <span lang="en" dir="ltr" class="mw-content-ltr">string</span> | style="text-align: center;" | <span lang="en" dir="ltr" class="mw-content-ltr">''none''</span> <br /> <span lang="en" dir="ltr" class="mw-content-ltr">substituted</span> || <span lang="en" dir="ltr" class="mw-content-ltr">The name key of another parameter (must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The current [[#Param object|Parameter Object]] will inherit properties from the specified [[#Param object|Parameter Object]], with local properties overriding the inherited ones.</span> |} {{anchor|Set object|Set Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Set object ==== </div> {| class="wikitable" id="Set" ! Schlüssel ! <span lang="en" dir="ltr" class="mw-content-ltr">Object or primitive type</span> ! Beschreibung |- | <code>label</code> | [[#InterfaceText (string or object)|InterfaceText]] | <span lang="en" dir="ltr" class="mw-content-ltr">A (very) brief name for the parameter set.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Try to keep under 20-ish characters.</span> |- | <code>params</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> | <span lang="en" dir="ltr" class="mw-content-ltr">One or more names of parameters to include in the set (each must be a valid key in the <code>params</code> object).</span> <span lang="en" dir="ltr" class="mw-content-ltr">A parameter may be in multiple sets.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not every parameter must be in a set.</span> |} {{anchor|Maps object|Maps Object}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Maps object ==== </div> {| class="wikitable" ! Schlüssel ! Typ ! Standard ! Beschreibung |- | <span lang="en" dir="ltr" class="mw-content-ltr">''name of consumer''</span> | <span lang="en" dir="ltr" class="mw-content-ltr">object</span> | style="text-align: center;" | {} | <span lang="en" dir="ltr" class="mw-content-ltr">An object that maps a ''name of a consumer'' to an object that in turn maps a ''name of a consumer parameter'' to one or more corresponding ''names of template parameters''.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''names of the template parameters'' can be specified either as a string (one name), an array of strings (several names), or an array of arrays of strings (several sets of names); each of these strings must be a valid key in the <code>params</code> object elsewhere in the same template's TemplateData. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A specific template parameter may be in multiple maps, and it may be used in the values of multiple keys in a given map, but not every template parameter ''must'' be in a map. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A shortened example from English Wikipedia's [[w:Template:Cite_news#TemplateData|Template:Cite_news#TemplateData]] illustrates the structure of a maps object. </div> <pre> { "proveit": { "main": "title", "textarea": [ "quote" ] }, "citoid": { "title": "title", "url": "url", "publisher": "publisher", "publicationTitle": "work", "date": "date", "ISSN": [ "issn" ], "ISBN": [ "isbn" ], "contributor": "others", "author": [ [ "first", "last" ], [ "first2", "last2" ], [ "first9", "last9" ] ], "editor": [ [ "editor-first", "editor-last" ] ] } } </pre> |} {{anchor|InterfaceText (string or object)}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== InterfaceText (string or object) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A free-form plain-text string (i.e. no wikitext or HTML) in the content-language of the wiki, or an object containing those strings keyed by language code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The default value for all InterfaceText fields is <code>null</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== String type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is a string, it must contain a non-localized string in the content language of the local wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===== Object type ===== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If it is an object, the object must have this mapping: </div> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Typ !! Beschreibung |- | style="text-align: center;" | ''<span lang="en" dir="ltr" class="mw-content-ltr">[[:en:List of Wikipedias|Wikipedia language code]]</span>'' || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the given language code.</span> |}<span lang="en" dir="ltr" class="mw-content-ltr">Example of object mapping:</span> {| class="wikitable" id="InterfaceText" style="width: 100%;" |- ! Schlüssel !! Wert |- | style="text-align: center;" | "en" || "Welcome to Wikipedia" |- | style="text-align: center;" | "de" || "Willkommen bei Wikipedia" |- | style="text-align: center;" | "fr" || "Bienvenue sur Wikipédia" |- | style="text-align: center;" | "nl" || "Welkom op Wikipedia" |- | style="text-align: center;" | "it" || "Benvenuti su Wikipedia" |- | style="text-align: center;" | "es" || "Bienvenidos a Wikipedia" |- | style="text-align: center;" | "ru" || "Добро пожаловать в Википедию" |} {{anchor|example}} === Beispiel === <div lang="en" dir="ltr" class="mw-content-ltr"> An example TemplateData structure as specified within wikitext on a template page. </div> <syntaxhighlight lang="javascript"><templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata></syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Below is how the above example would be displayed on the template page: </div> <div class="toccolours" style="margin: 2em; padding:1em 2em;"> <templatedata> { "description": "Label unsigned comments in a conversation.", "params": { "user": { "label": "User's name", "type": "wiki-user-name", "required": true, "description": "User name of person who forgot to sign their comment.", "aliases": ["1"] }, "date": { "label": "Date", "suggested": true, "description": { "en": "Timestamp of when the comment was posted, in YYYY-MM-DD format." }, "aliases": ["2"], "autovalue": "{{subst:#time:Y-m-d}}" }, "year": { "label": "Year", "type": "number" }, "month": { "label": "Month", "inherits": "year" }, "day": { "label": "Day", "inherits": "year" }, "comment": { "required": false } }, "sets": [ { "label": "Date", "params": ["year", "month", "day"] } ], "maps": { "ExampleConsumer": { "foo": "user", "bar": ["year", "month", "day"], "quux": [ "date", ["day", "month"], ["month", "year"], "year" ] } } } </templatedata> </div> == API == <span lang="en" dir="ltr" class="mw-content-ltr">See the generated help at [[Special:ApiHelp/templatedata]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">A sample invocation (formatted for human readability) is:</span> {{ApiEx | p1=action=templatedata | p2=titles=Template:Cite%20web | p3=format=json }} <span lang="en" dir="ltr" class="mw-content-ltr">This returns the template data for [[:en:Template:Cite web|Template:Cite web]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|templatedata}} block for this template is on its transcluded template documentation page, [[:en:Template:Cite web/doc]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Additions and changes to JSON as received from the API === </div> <span lang="en" dir="ltr" class="mw-content-ltr">The JSON structure provided in response to an API HTTP get request is significantly different than that which is defined in the {{tag|templatedata}} block.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In response to the API request, extension TemplateData makes the following changes to the JSON object:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Adds two [[#Wrapper Objects from API|wrapping objects]]: </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">An overall [[#Pages Object|Pages Object]] containing one or more [[#Page Object|Page Object]]s</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">An object with a numeric key: a [[#Page Object|Page Object]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Additions/changes to the actual [[#TemplateData Object|TemplateData Object]] </div> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>title</code> key with the name of the page from which the data was requested (e.g. "Template:Cite web").</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add the <code>sets</code> key</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Change all TemplateText occurrences that are just strings to objects with a single key for the current wiki's [[:en:List of Wikipedias|Wikipedia language code]]</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Remove all <code>inherits</code> keys.</span> *#* <span lang="en" dir="ltr" class="mw-content-ltr">Add all properties from parameter from which an inheritance is defined which are not superseded by explicitly defined keys in the inheritor's [[#Param object|Parameter Object]].</span> *# <span lang="en" dir="ltr" class="mw-content-ltr">Add default values for all keys in each [[#Param object|Parameter Object]] which have not been explicitly defined or inherited.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Visualised differences in a TemplateData JSON object delivered by the API=== </div> {| class="wikitable" id="Wrapper Objects from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wrapper objects added to JSON delivered by API</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">These are not defined in the JSON object enclosed by the {{tag|templatedata|open}} tags on the template page.</span></span> |- | {| class="wikitable" id="Pages Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">JSON Root</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>pages</code> | <span lang="en" dir="ltr" class="mw-content-ltr">[[#Page Object|Page Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The Page object (contains one key which is the page number).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If multiple pages were requested at one time there will be multiple Page Objects.</span> |} |- |<br/> {| class="wikitable" id="Page Object" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Page Object</span> |- ! Schlüssel !! Typ !! Beschreibung |- | {{nowrap|(<span lang="en" dir="ltr" class="mw-content-ltr">page number</span>)}} | <span lang="en" dir="ltr" class="mw-content-ltr">[[#TemplateData Object|TemplateData Object]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">The [[#TemplateData Object|TemplateData Object]] containing the information payload.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The key is a static page number for the template page from which the JSON data was requested.</span> |} |} {| class="wikitable" id="TemplateData Object Additions by API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">TemplateData Object (added by API)</span><br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">The following key is added to the root of the JSON object which is enclosed in {{tag|templatedata|open}} tags on the template page.</span></span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>title</code> | Zeichenkette | <span lang="en" dir="ltr" class="mw-content-ltr">The page name of the template (e.g. "Template:Cite web").</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">This key is ''not'' contained in the JSON structure on the template page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is added to the structure by the MediaWiki software in route to delivery via the API.</span> |- | <code>sets</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Array containing [[#Set object|Set Objects]]</span> | <span lang="en" dir="ltr" class="mw-content-ltr">An array containing set specifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A set is a group of parameters that should be used together.</span> <br/>''<span lang="en" dir="ltr" class="mw-content-ltr">If this does not exist on the template page it is added as an empty array to the structure provided by the API.</span>'' |} {| class="wikitable" id="Parameter Object from API" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Parameter Objects from API</span> |- ! Schlüssel !! Typ !! Beschreibung |- | <code>label</code> || [[#InterfaceText (string or object)|InterfaceText]] || <span lang="en" dir="ltr" class="mw-content-ltr">translated to [[#InterfaceText (string or object)|InterfaceText]] object, if not already in that format.</span> |- | <code>required</code> || Wahrheitswert || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>description</code> || [[#InterfaceText (string or object)|InterfaceText]] oder <code>null</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If defined as a string, converted to a [[#InterfaceText (string or object)|InterfaceText]] object.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, key is added with a <code>null</code> value.</span> |- | <code>deprecated</code> || Wahrheitswert oder Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default value of '''false''' added.</span> |- | <code>aliases</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Array of strings</span> || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, a default empty array is assigned (i.e. [] ).</span> |- | <code>default</code> || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "" is assigned.</span> |- | <code>type</code> || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">If not defined, default of "unknown" is assigned.</span> |- | <code>inherits</code> || {{removed-inline}} || <span lang="en" dir="ltr" class="mw-content-ltr">This key is removed and all inherited keys are added.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Keys defined for the current parameter take precedence and any keys not defined on either the current param, or the one from which it inherits are given the default value.</span> |} {| class="wikitable" id="InterfaceText" style="width: 100%;" |+ InterfraceText (Objekt oder <code>null</code>):<br/> <span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">An object containing strings keyed by language code.</span></span> |- ! Schlüssel !! Objekt oder<br />primitive Typ !! Beschreibung |- | colspan="3" style="text-align: center;font-weight:bold;" | Objekt <br/><span style="font-weight:normal;"><span lang="en" dir="ltr" class="mw-content-ltr">(containing localized strings by [[:en:List of Wikipedias|Wikipedia language code]])</span><br/><span lang="en" dir="ltr" class="mw-content-ltr">If a TemplateData field on the template page contains a string, not an object with localized strings, MediaWiki translates it into an InterfaceText Object with a string assigned to the key name of the source Wikipedia [[:en:List of Wikipedias|Wikipedia language code]].</span> Der Standardwert für alle InterfaceText-Felder ist <code>null</code></span> |- | style="text-align: center;" | (Sprachcode des Wikis) || Zeichenkette || <span lang="en" dir="ltr" class="mw-content-ltr">Localized string for use on the Wikipedia corresponding to the [[:en:List of Wikipedias|Wikipedia language code]].</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> === Example of JSON object provided by API === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The response to an API request for the TemplateData structure in the [[#example|Example]] section (above) can be seen: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In HTML format: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData&format=jsonfm </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * As delivered by the API: https://www.mediawiki.org/w/api.php?action=templatedata&titles=Extension:TemplateData </div> == Konfiguration == {| class="wikitable" ! Variable ! Standard ! Beschreibung |--- | <code>$wgTemplateDataUseGUI</code> | <code>true</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Experimental dialog interface to edit templatedata JSON</span> |} == Siehe auch == * {{ll|Extension:TemplateWizard}}&nbsp;– <span lang="en" dir="ltr" class="mw-content-ltr">user interface for selecting and inserting templates' wikitext, based on their TemplateData.</span> * [https://github.com/jeblad/TemplateData GitHub: jeblad/TemplateData] – <span lang="en" dir="ltr" class="mw-content-ltr">alternate version with some Lua functionality.</span> * [[m:Special:MyLanguage/Template:Translatable template|<span lang="en" dir="ltr" class="mw-content-ltr">Translatable template</span>]] {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|fandom=1|miraheze=1|mywikis=1|semantic core=1}} [[Category:Metadata{{#translation:}}]] 2c5uuilez6wdqm37tzi6ip4c8a7t4b6 Wikitext standard/cs 0 1100225 5387869 5274849 2022-07-29T10:33:04Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Historical|1=Většina textu na této stránce byla napsána v letech 2003-2006. Podívejte se na {{ll|Wikitext}} pro nejnovější stav úsilí o standardizaci wikitextu.}} <div class="mw-translate-fuzzy"> Jediný '''standard [[Special:MyLanguage/wikitext|wikitextu]]''' je velmi důležitý pro dlouhodobou stabilitu softwaru MediaWiki. Musíme popsat a formalizovat verzi [[meta:WikiReader#Wikipedia_1.0|1.0]] jazyka Wikitext na základě toho, co se v současné době používá. Jinými slovy by tato práce neměla (zatím) zahrnovat začlenění vylepšení nebo změny jazyka Wikitext. Vydání musí být stabilní a předvídatelné, aby ostatní vývojáři softwaru mohli pracovat se stejnou syntaxí značek a mohli si být jisti, že nebudou po určité pevné časové období, například rok, čelit náhodným nebo libovolným změnám. To naznačuje, že může existovat [[Special:MyLanguage/wikitext 2005|wikitext 2005]], [[Special:MyLanguage/wikitext 2006|wikitext 2006]] atd. </div> [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] sledoval, které weby Mediawiki dělají to nejlepší. Wikipedie nemusí být vždy nejvzdálenějším problémem, ani by její potřeby neměly nutně vždy převyšovat ostatní v úsilí o návrh softwaru Mediawiki. Například [[meta:Wikitravel|Wikitravel]] může být lepší v geografii a [[meta:Spacetime DTD|mapách]]. První užitečné mapové a podkladové datové standardy, jako je [[meta:Ecoregion DTD|ecoregion DTD]] a [[meta:Spacetime DTD|spacetime DTD]]. Může být snadnější na nich pracovat, pokud se jedná o více ústřední problémy. Jiné dílčí úkoly jako [[meta:Person DTD|Osobní DTD]] se mohou stát projekty WikiProjectů, které provádí disciplinovaná skupina učenců, kteří vědí nebo chtějí vědět vše o dokumentování lidí. == Úkoly == <div class="mw-translate-fuzzy"> # Napsat [[Special:MyLanguage/markup spec|znakový speciál]] # Napsat efektivní [[Special:MyLanguage/Alternative parsers|převaděč wikitextu do HTML]], abyste nahradili aktuální kód PHP. # Napsat sadu jednotkových testů k ověření správnosti převaděče Wikitextu na HTML. </div> === Úkoly související s XML === <div class="mw-translate-fuzzy"> # Napsat [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]], který může sloužit jako kanonický překlad Wikitextu <=> XML pro další zpracování pomocí nástrojů XML. ''Nebo použijte [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. # Napsat převaděč Wikitextu do XML. #* Vyhodnotit [http://www.tldp.org/wt2db/ wt2db]. #* Nebo použít [http://schematics.sourceforge.net WebBot], balíček PLT Scheme, který funguje jako Bot na MediaWiki a obsahuje parser k převodu WikiTextu na [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. </div> == Publikování standardu == Jasný standard může být publikován a podporován jinými wiki, jako je MoinMoinWiki (založená [[:en:Python_programming_language|python]]) a tikiwiki (viz [http://tikiwiki.sourceforge.net sourceforge]), které jsou velmi populární a rozšiřitelnější než mediawiki, což má vážné strukturální problémy I když mediawiki dokáže držet krok s těmito dalšími balíčky, musí být import případně export textu jednou z našich priorit, vzhledem k cílům tohoto projektu stát se centrálním úložištěm důvěryhodného textu GNU FDL pro všestranné použití. Činnosti [[meta:Wikimedia|Wikimedie]] by neměly být v žádném případě uvězněny nebo svázány s MediaWiki, pokud z tikiwiki nebo světa Pythonu dojde k drasticky lepšímu softwaru. A nakonec k tomu dojde. === Dlouhodobé plány === # Když se věci ustálí, řekněme [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], pak: # vytvoří konsorcium všech uživatelů, vývojářů různých typů softwaru, včetně systémů založených na [[meta:IRC/Channels|chatech]] a [[Special:MyLanguage/email|emailech]], které zahrnují funkce jako [[Special:MyLanguage/Trillian Instant Lookup|Trillian Okamžité vyhledávání]] - ne všichni uživatelé Wikipedie používají webový prohlížeč # dohodnou se na [[meta:Simple ideology of Wikitax|jednoduché ideologii Wikitaxu]] aby obsah vytvořený jinde usnadnil rychle se stát wiki stránkami # se vytvoří jednotný základní boot jako KnoppixTiki, který podporuje nový standard, takže jej lze použít pro jakýkoli druh ukládání dat jako v PIM # stabilizují a publikují se něco jako [[Special:MyLanguage/wikitext 2008|wikitext 2008]] jako skutečný RFC # zaměří se na[[Special:MyLanguage/wikitext 2009|wikitext 2009]] nebo [[Special:MyLanguage/wikitext 2010|wikitext 2010]] jako standard ITU Viz také: [[meta:Simple ideology of Wikitax|jednoduchá ideologie Wikitaxu]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|osobní DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] 67ttxap4uoq4ukwwmm4nhul0etov7xf 5387875 5387869 2022-07-29T10:33:58Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=Většina textu na této stránce byla napsána v letech 2003-2006. Podívejte se na {{ll|Wikitext}} pro nejnovější stav úsilí o standardizaci wikitextu.}} Jediný '''standard [[Special:MyLanguage/wikitext|wikitextu]]''' je velmi důležitý pro dlouhodobou stabilitu softwaru MediaWiki. Musíme popsat a formalizovat verzi [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] jazyka Wikitext na základě toho, co se v současné době používá. Jinými slovy by tato práce neměla (zatím) zahrnovat začlenění vylepšení nebo změny jazyka Wikitext. Vydání musí být stabilní a předvídatelné, aby ostatní vývojáři softwaru mohli pracovat se stejnou syntaxí značek a mohli si být jisti, že nebudou po určité pevné časové období, například rok, čelit náhodným nebo libovolným změnám. To naznačuje, že může existovat [[Special:MyLanguage/wikitext 2005|wikitext 2005]], [[Special:MyLanguage/wikitext 2006|wikitext 2006]] atd. [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] sledoval, které weby Mediawiki dělají to nejlepší. Wikipedie nemusí být vždy nejvzdálenějším problémem, ani by její potřeby neměly nutně vždy převyšovat ostatní v úsilí o návrh softwaru Mediawiki. Například [[meta:Wikitravel|Wikitravel]] může být lepší v geografii a [[meta:Spacetime DTD|mapách]]. První užitečné mapové a podkladové datové standardy, jako je [[meta:Ecoregion DTD|ecoregion DTD]] a [[meta:Spacetime DTD|spacetime DTD]]. Může být snadnější na nich pracovat, pokud se jedná o více ústřední problémy. Jiné dílčí úkoly jako [[meta:Person DTD|Osobní DTD]] se mohou stát projekty WikiProjectů, které provádí disciplinovaná skupina učenců, kteří vědí nebo chtějí vědět vše o dokumentování lidí. == Úkoly == <div class="mw-translate-fuzzy"> # Napsat [[Special:MyLanguage/markup spec|znakový speciál]] # Napsat efektivní [[Special:MyLanguage/Alternative parsers|převaděč wikitextu do HTML]], abyste nahradili aktuální kód PHP. # Napsat sadu jednotkových testů k ověření správnosti převaděče Wikitextu na HTML. </div> === Úkoly související s XML === <div class="mw-translate-fuzzy"> # Napsat [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]], který může sloužit jako kanonický překlad Wikitextu <=> XML pro další zpracování pomocí nástrojů XML. ''Nebo použijte [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. # Napsat převaděč Wikitextu do XML. #* Vyhodnotit [http://www.tldp.org/wt2db/ wt2db]. #* Nebo použít [http://schematics.sourceforge.net WebBot], balíček PLT Scheme, který funguje jako Bot na MediaWiki a obsahuje parser k převodu WikiTextu na [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. </div> == Publikování standardu == Jasný standard může být publikován a podporován jinými wiki, jako je MoinMoinWiki (založená [[:en:Python_programming_language|python]]) a tikiwiki (viz [http://tikiwiki.sourceforge.net sourceforge]), které jsou velmi populární a rozšiřitelnější než mediawiki, což má vážné strukturální problémy I když mediawiki dokáže držet krok s těmito dalšími balíčky, musí být import případně export textu jednou z našich priorit, vzhledem k cílům tohoto projektu stát se centrálním úložištěm důvěryhodného textu GNU FDL pro všestranné použití. Činnosti [[meta:Wikimedia|Wikimedie]] by neměly být v žádném případě uvězněny nebo svázány s MediaWiki, pokud z tikiwiki nebo světa Pythonu dojde k drasticky lepšímu softwaru. A nakonec k tomu dojde. === Dlouhodobé plány === # Když se věci ustálí, řekněme [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], pak: # vytvoří konsorcium všech uživatelů, vývojářů různých typů softwaru, včetně systémů založených na [[meta:IRC/Channels|chatech]] a [[Special:MyLanguage/email|emailech]], které zahrnují funkce jako [[Special:MyLanguage/Trillian Instant Lookup|Trillian Okamžité vyhledávání]] - ne všichni uživatelé Wikipedie používají webový prohlížeč # dohodnou se na [[meta:Simple ideology of Wikitax|jednoduché ideologii Wikitaxu]] aby obsah vytvořený jinde usnadnil rychle se stát wiki stránkami # se vytvoří jednotný základní boot jako KnoppixTiki, který podporuje nový standard, takže jej lze použít pro jakýkoli druh ukládání dat jako v PIM # stabilizují a publikují se něco jako [[Special:MyLanguage/wikitext 2008|wikitext 2008]] jako skutečný RFC # zaměří se na[[Special:MyLanguage/wikitext 2009|wikitext 2009]] nebo [[Special:MyLanguage/wikitext 2010|wikitext 2010]] jako standard ITU Viz také: [[meta:Simple ideology of Wikitax|jednoduchá ideologie Wikitaxu]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|osobní DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] od0iqiapgrhny7o6gw07orcmil2olv8 5387881 5387875 2022-07-29T10:36:16Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=Většina textu na této stránce byla napsána v letech 2003-2006. Podívejte se na {{ll|Wikitext}} pro nejnovější stav úsilí o standardizaci wikitextu.}} Jediný '''standard [[Special:MyLanguage/wikitext|wikitextu]]''' je velmi důležitý pro dlouhodobou stabilitu softwaru MediaWiki. Musíme popsat a formalizovat verzi [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] jazyka Wikitext na základě toho, co se v současné době používá. Jinými slovy by tato práce neměla (zatím) zahrnovat začlenění vylepšení nebo změny jazyka Wikitext. Vydání musí být stabilní a předvídatelné, aby ostatní vývojáři softwaru mohli pracovat se stejnou syntaxí značek a mohli si být jisti, že nebudou po určité pevné časové období, například rok, čelit náhodným nebo libovolným změnám. To naznačuje, že může existovat [[Special:MyLanguage/wikitext 2005|wikitext 2005]], [[Special:MyLanguage/wikitext 2006|wikitext 2006]] atd. [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] sledoval, které weby Mediawiki dělají to nejlepší. Wikipedie nemusí být vždy nejvzdálenějším problémem, ani by její potřeby neměly nutně vždy převyšovat ostatní v úsilí o návrh softwaru Mediawiki. Například [[meta:Wikitravel|Wikitravel]] může být lepší v geografii a [[meta:Spacetime DTD|mapách]]. První užitečné mapové a podkladové datové standardy, jako je [[meta:Ecoregion DTD|ecoregion DTD]] a [[meta:Spacetime DTD|spacetime DTD]]. Může být snadnější na nich pracovat, pokud se jedná o více ústřední problémy. Jiné dílčí úkoly jako [[meta:Person DTD|Osobní DTD]] se mohou stát projekty WikiProjectů, které provádí disciplinovaná skupina učenců, kteří vědí nebo chtějí vědět vše o dokumentování lidí. == Úkoly == # Napsat [[Special:MyLanguage/markup spec|znakový speciál]] # Napsat efektivní [[Special:MyLanguage/Alternative parsers|převaděč wikitextu do HTML]], abyste nahradili aktuální kód PHP. # Napsat sadu jednotkových testů k ověření správnosti převaděče Wikitextu na HTML. === Úkoly související s XML === <div class="mw-translate-fuzzy"> # Napsat [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]], který může sloužit jako kanonický překlad Wikitextu <=> XML pro další zpracování pomocí nástrojů XML. ''Nebo použijte [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. # Napsat převaděč Wikitextu do XML. #* Vyhodnotit [http://www.tldp.org/wt2db/ wt2db]. #* Nebo použít [http://schematics.sourceforge.net WebBot], balíček PLT Scheme, který funguje jako Bot na MediaWiki a obsahuje parser k převodu WikiTextu na [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. </div> == Publikování standardu == Jasný standard může být publikován a podporován jinými wiki, jako je MoinMoinWiki (založená [[:en:Python_programming_language|python]]) a tikiwiki (viz [http://tikiwiki.sourceforge.net sourceforge]), které jsou velmi populární a rozšiřitelnější než mediawiki, což má vážné strukturální problémy I když mediawiki dokáže držet krok s těmito dalšími balíčky, musí být import případně export textu jednou z našich priorit, vzhledem k cílům tohoto projektu stát se centrálním úložištěm důvěryhodného textu GNU FDL pro všestranné použití. Činnosti [[meta:Wikimedia|Wikimedie]] by neměly být v žádném případě uvězněny nebo svázány s MediaWiki, pokud z tikiwiki nebo světa Pythonu dojde k drasticky lepšímu softwaru. A nakonec k tomu dojde. === Dlouhodobé plány === # Když se věci ustálí, řekněme [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], pak: # vytvoří konsorcium všech uživatelů, vývojářů různých typů softwaru, včetně systémů založených na [[meta:IRC/Channels|chatech]] a [[Special:MyLanguage/email|emailech]], které zahrnují funkce jako [[Special:MyLanguage/Trillian Instant Lookup|Trillian Okamžité vyhledávání]] - ne všichni uživatelé Wikipedie používají webový prohlížeč # dohodnou se na [[meta:Simple ideology of Wikitax|jednoduché ideologii Wikitaxu]] aby obsah vytvořený jinde usnadnil rychle se stát wiki stránkami # se vytvoří jednotný základní boot jako KnoppixTiki, který podporuje nový standard, takže jej lze použít pro jakýkoli druh ukládání dat jako v PIM # stabilizují a publikují se něco jako [[Special:MyLanguage/wikitext 2008|wikitext 2008]] jako skutečný RFC # zaměří se na[[Special:MyLanguage/wikitext 2009|wikitext 2009]] nebo [[Special:MyLanguage/wikitext 2010|wikitext 2010]] jako standard ITU Viz také: [[meta:Simple ideology of Wikitax|jednoduchá ideologie Wikitaxu]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|osobní DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] 6mo9uu3oh3a5uz017hpopq7glkhuuwd 5387888 5387881 2022-07-29T10:37:57Z Shirayuki 472859 update wikitext text/x-wiki <languages /> {{Historical|1=Většina textu na této stránce byla napsána v letech 2003-2006. Podívejte se na {{ll|Wikitext}} pro nejnovější stav úsilí o standardizaci wikitextu.}} Jediný '''standard [[Special:MyLanguage/wikitext|wikitextu]]''' je velmi důležitý pro dlouhodobou stabilitu softwaru MediaWiki. Musíme popsat a formalizovat verzi [[meta:Special:MyLanguage/WikiReader#Wikipedia 1.0|1.0]] jazyka Wikitext na základě toho, co se v současné době používá. Jinými slovy by tato práce neměla (zatím) zahrnovat začlenění vylepšení nebo změny jazyka Wikitext. Vydání musí být stabilní a předvídatelné, aby ostatní vývojáři softwaru mohli pracovat se stejnou syntaxí značek a mohli si být jisti, že nebudou po určité pevné časové období, například rok, čelit náhodným nebo libovolným změnám. To naznačuje, že může existovat [[Special:MyLanguage/wikitext 2005|wikitext 2005]], [[Special:MyLanguage/wikitext 2006|wikitext 2006]] atd. [http://web.archive.org/web/20060725171208/http://www.metaweb.com/wiki/wiki.phtml?title=Wikitext_standard Metaweb] sledoval, které weby Mediawiki dělají to nejlepší. Wikipedie nemusí být vždy nejvzdálenějším problémem, ani by její potřeby neměly nutně vždy převyšovat ostatní v úsilí o návrh softwaru Mediawiki. Například [[meta:Wikitravel|Wikitravel]] může být lepší v geografii a [[meta:Spacetime DTD|mapách]]. První užitečné mapové a podkladové datové standardy, jako je [[meta:Ecoregion DTD|ecoregion DTD]] a [[meta:Spacetime DTD|spacetime DTD]]. Může být snadnější na nich pracovat, pokud se jedná o více ústřední problémy. Jiné dílčí úkoly jako [[meta:Person DTD|Osobní DTD]] se mohou stát projekty WikiProjectů, které provádí disciplinovaná skupina učenců, kteří vědí nebo chtějí vědět vše o dokumentování lidí. == Úkoly == # Napsat [[Special:MyLanguage/markup spec|znakový speciál]] # Napsat efektivní [[Special:MyLanguage/Alternative parsers|převaděč wikitextu do HTML]], abyste nahradili aktuální kód PHP. # Napsat sadu jednotkových testů k ověření správnosti převaděče Wikitextu na HTML. === Úkoly související s XML === # Napsat [[Special:MyLanguage/Markup spec/DTD|Wikitext DTD]], který může sloužit jako kanonický překlad Wikitextu <=> XML pro další zpracování pomocí nástrojů XML. ''Nebo použijte [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. # Napsat převaděč Wikitextu do XML. #* Vyhodnotit [http://www.tldp.org/wt2db/ wt2db]. #* Nebo použít [http://schematics.sourceforge.net WebBot], balíček PLT Scheme, který funguje jako Bot na MediaWiki a obsahuje parser k převodu WikiTextu na [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. == Publikování standardu == Jasný standard může být publikován a podporován jinými wiki, jako je MoinMoinWiki (založená [[:en:Python_programming_language|python]]) a tikiwiki (viz [http://tikiwiki.sourceforge.net sourceforge]), které jsou velmi populární a rozšiřitelnější než mediawiki, což má vážné strukturální problémy I když mediawiki dokáže držet krok s těmito dalšími balíčky, musí být import případně export textu jednou z našich priorit, vzhledem k cílům tohoto projektu stát se centrálním úložištěm důvěryhodného textu GNU FDL pro všestranné použití. Činnosti [[meta:Wikimedia|Wikimedie]] by neměly být v žádném případě uvězněny nebo svázány s MediaWiki, pokud z tikiwiki nebo světa Pythonu dojde k drasticky lepšímu softwaru. A nakonec k tomu dojde. === Dlouhodobé plány === # Když se věci ustálí, řekněme [[Special:MyLanguage/wikitext standard 2007|wikitext standard 2007]], pak: # vytvoří konsorcium všech uživatelů, vývojářů různých typů softwaru, včetně systémů založených na [[meta:IRC/Channels|chatech]] a [[Special:MyLanguage/email|emailech]], které zahrnují funkce jako [[Special:MyLanguage/Trillian Instant Lookup|Trillian Okamžité vyhledávání]] - ne všichni uživatelé Wikipedie používají webový prohlížeč # dohodnou se na [[meta:Simple ideology of Wikitax|jednoduché ideologii Wikitaxu]] aby obsah vytvořený jinde usnadnil rychle se stát wiki stránkami # se vytvoří jednotný základní boot jako KnoppixTiki, který podporuje nový standard, takže jej lze použít pro jakýkoli druh ukládání dat jako v PIM # stabilizují a publikují se něco jako [[Special:MyLanguage/wikitext 2008|wikitext 2008]] jako skutečný RFC # zaměří se na[[Special:MyLanguage/wikitext 2009|wikitext 2009]] nebo [[Special:MyLanguage/wikitext 2010|wikitext 2010]] jako standard ITU Viz také: [[meta:Simple ideology of Wikitax|jednoduchá ideologie Wikitaxu]], [[meta:Wikitext DTD|meta:Wikitext DTD]], [[meta:Person DTD|osobní DTD]], [[meta:Ecoregion DTD|meta:Ecoregion DTD]], [[meta:Spacetime DTD|meta:Spacetime DTD]] [[Category:Wikitext{{#translation:}}]] 8mok3zutwhotfh0t6ba1o4qsokrpq0u Translations:Wikitext standard/1/cs 1198 1100229 5387874 5274820 2022-07-29T10:33:57Z Shirayuki 472859 update wikitext text/x-wiki Jediný '''standard [[$1|wikitextu]]''' je velmi důležitý pro dlouhodobou stabilitu softwaru MediaWiki. Musíme popsat a formalizovat verzi [[$2|1.0]] jazyka Wikitext na základě toho, co se v současné době používá. Jinými slovy by tato práce neměla (zatím) zahrnovat začlenění vylepšení nebo změny jazyka Wikitext. Vydání musí být stabilní a předvídatelné, aby ostatní vývojáři softwaru mohli pracovat se stejnou syntaxí značek a mohli si být jisti, že nebudou po určité pevné časové období, například rok, čelit náhodným nebo libovolným změnám. To naznačuje, že může existovat [[$3|wikitext 2005]], [[$4|wikitext 2006]] atd. j0psqwhbp0yj63z9zbbsjo8511o1hpt Translations:Wikitext standard/4/cs 1198 1100233 5387880 5274830 2022-07-29T10:36:15Z Shirayuki 472859 update wikitext text/x-wiki # Napsat [[$1|znakový speciál]] # Napsat efektivní [[$2|převaděč wikitextu do HTML]], abyste nahradili aktuální kód PHP. # Napsat sadu jednotkových testů k ověření správnosti převaděče Wikitextu na HTML. inq2yjd9z3j3mtov3f2hx7z2269d0dg Translations:Wikitext standard/6/cs 1198 1100235 5387887 5274836 2022-07-29T10:37:56Z Shirayuki 472859 update wikitext text/x-wiki # Napsat [[$1|Wikitext DTD]], který může sloužit jako kanonický překlad Wikitextu <=> XML pro další zpracování pomocí nástrojů XML. ''Nebo použijte [http://schematics.sourceforge.net/wikitext.xsd.zip this XML Schema]''. # Napsat převaděč Wikitextu do XML. #* Vyhodnotit [http://www.tldp.org/wt2db/ wt2db]. #* Nebo použít [http://schematics.sourceforge.net WebBot], balíček PLT Scheme, který funguje jako Bot na MediaWiki a obsahuje parser k převodu WikiTextu na [http://schematics.sourceforge.net/wikitext.xsd.zip given XML Schema]. 3nfivej6u553lr2fo1kpy2mvfq2py0u Wikimedia Product/eo 0 1103448 5387573 5358191 2022-07-29T03:25:41Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Kontribuantoj</span>]] * [[Readers|<span style="color:#2aa198">Legantoj</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Traprodukte == * [[Special:MyLanguage/Product Principles|Produktaj Principoj]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|Gvidnormoj pri Teknika Kunlaborado]]) * [[Special:MyLanguage/Design/Statement of purpose|Aserto de Celo pri Dezajno]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|Dateno kaj esplorada informo por produktoj]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === Programoj === * [[m:Special:MyLanguage/Communications/Audience research|Esplorado pri la Spektantoj]] * [[m:Special:MyLanguage/Community health initiative|Komunuma Saneca Iniciato]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|Spertoj de Novaj Redaktantoj]] (2017–2018) * [[m:Special:MyLanguage/New Readers|Novaj Legantoj]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|Strukturita Dateno en Komunejo]] === Projektaj Paĝoj === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|Celo de Ĉiujara Plano: Nova Enhavo]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|Redaktaj Funkcioj ĉe Android]] * [[Special:MyLanguage/Content translation/V2|Enhava Tradukado, V2]] * [[Special:MyLanguage/Growth/Growth team updates|Kresko]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|Redaktado per iOS]] * [[Special:MyLanguage/VisualEditor on mobile|Vidbaza poŝaparata redaktado]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|Pli bona uzado de Dateno]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|Dezirlisto]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|Subteno de malgrandaj uzantogrupoj]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|Teknikaj iloj por programaj kaj eventaj organizantoj]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''Celo de Ĉiujara Plano: Kontraŭĝenaj Iloj''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|Raporta sistemo]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''Celo de Ĉiujara Plano: Vikidatumoj''']] '''Aliaĵoj:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|Unuigo de sintaksanaliziloj]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|Studo pri Movadaj Organizantoj]] (2019) == Metrikoj == <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == Teamoj pri produkto == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === Kontribuantoj === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * Taskotabuloj ĉe Phabricator: [[phab:tag/contributors-team/|#Contributors-Team]] (malofte uzata) * Paĝo: [[Special:MyLanguage/Contributors|Kontribuantoj]] * Teamoj: ====== Kontraŭĝenaj Iloj ====== * Taskotabulo ĉe Phabricator: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * Paĝo: [[Special:MyLanguage/Anti-Harassment Tools|Kontraŭĝenaj Iloj]] ====== Komunuma Tekniko ====== * [[phab:project/board/1274/|<span class="mw-translate-fuzzy">Taskotabulo ĉe Phabricator:</span>]] * Paĝo: [[m:Special:MyLanguage/Community Tech|Komunuma Tekniko]] ====== Redaktado ====== * Taskotabuloj ĉe Phabricator: [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * Paĝo: [[Special:MyLanguage/Editing team|Redaktada teamo]] ====== Kresko ====== * Taskotabulo ĉe Phabricator: [[phab:project/board/1114/|#Growth-Team]] * Paĝo: [[Special:MyLanguage/Growth|Kresko]] ====== Lingvo ====== * Taskotabulo ĉe Phabricator: [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * Paĝo: [[Special:MyLanguage/Wikimedia Language engineering|Vikimedia Lingva inĝenierio]] === Legantoj === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * Paĝo: [[Special:MyLanguage/Readers|Legantoj]] * Taskotabulo ĉe Phabricator: [https://phabricator.wikimedia.org/tag/reading/ #reading] * Teamoj: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|Android]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|IOS]] ====== ====== [[Special:MyLanguage/Parsing|Sintaksanalizo]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|Produkta Infrastrukturo]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|Ĉiumonataj paĝovidoj, Majo 2013–Januaro 2019. File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === Teknika Programa Administrado === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> Paĝo: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|Teknika Programa Administrado]] Estro: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === Produkta Dezajno === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> Paĝo: [[Special:MyLanguage/Design#Product Design|Produkta Dezajno]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === Produktaj Analiziloj === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> Paĝo: [[Special:MyLanguage/Product Analytics|Produktaj Analiziloj]] Estro: Kate Zimmerman === Strategio pri Produkta Dezajno === <!--''[enkonduka teksto bezonata]''--> Paĝo: [[Special:MyLanguage/Design#Design Strategy|Strategio pri Produkta Dezajno]] Paĝo: Margeigh Novotny === Vikidatumoj === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * Paĝo: [[d:Wikidata:Main Page|Wikidata]] * Estro: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * Tasko- kaj cimo-tabulo ĉe Phabricator: [[phab:project/profile/71/|#wikidata]] * Diskutlisto: wikidata@lists.wikimedia.org {|class="wikitable" |+ Celoj de Vikidatuma Teamo |- !scope="row"| Fiska Jaro 2017 de Vikimedio Germanio | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 Jarkvarono 1: Januaro–Marto 2017] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 Jarkvarono 2: Aprilo–Junio] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf Jarkvarono 3: Julio–Septembro] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf Jarkvarono 4: Oktobro–Decembro] |- !scope="row"| Fiska Jaro 2016 de Vikimedio Germanio | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p Jarkvarono 1: Januaro–Marto 2016] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Jarkvarono 2: Aprilo–Junio] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Jarkvarono 3: Julio–Septembro] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Jarkvarono 4: Oktobro–Decembro] |} == Celoj == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Jarkvarono 1: Julio–Septembro 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Jarkvarono 2: Oktobro–Decembro 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Jarkvarono 3: Januaro–Marto 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Jarkvarono 4: Aprilo–Junio 2020]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Jarkvarono 1: Julio–Septembro 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Jarkvarono 2: Oktobro–Decembro 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Jarkvarono 3: Januaro–Marto 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Jarkvarono 4: Aprilo–Junio 2019]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Jarkvarono 1: Julio–Septembro 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Jarkvarono 2: Oktobro–Decembro 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Jarkvarono 3: Januaro–Marto 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Jarkvarono 4: Aprilo–Junio 2018]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Jarkvarono 1: Julio–Septembro 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Jarkvarono 2: Oktobro–Decembro 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Jarkvarono 3: Januaro–Marto 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Jarkvarono 4: Aprilo–Junio 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Jarkvarono 1: Julio–Septembro 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Jarkvarono 2: Oktobro–Decembro 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Jarkvarono 3: Januaro–Marto 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Jarkvarono 4: Aprilo–Junio 2016]] |} == Ĉiujaraj Planoj == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|Ĉiujara Plano por Produkto 2018–2019]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|Ĉiujara Plano por Produkto 2017–2018]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|Ĉiujara Plano por Produkto 2016–2017]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|Resumo de Produkto en 2016]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|Produkta & Teknika Revizio 2015]] [[Category:WMF Projects{{#translation:}}]] pwwkxtlng8iopxffli5t1gjuaabdb46 Translations:Help:TemplateData/401/cs 1198 1109121 5386216 3823494 2022-07-28T12:12:39Z ENeRZet 17359278 wikitext text/x-wiki * V aplikaci VisualEditoru a editoru wikitext 2017 nemá $1 žádný viditelný efekt. t4cqr2h0a2o9wh84578wpj4rl5e8v6s Translations:Help:TemplateData/410/cs 1198 1109130 5386214 4987697 2022-07-28T12:11:36Z ENeRZet 17359278 wikitext text/x-wiki * V aplikaci VisualEditoru a editoru wikitext 2017 $1 způsobí, že vstupní pole zobrazí v levé části pole ikonu externího odkazu (čtverec se šipkou směřující ven) a po kliknutí uživatele odešle v červené barvě hodnotu URL, která obsahuje platný internetový protokol (např. "$2", "$3" nebo "$4"), za kterým následuje nějaký text. 0ohrixrinbcem53w1gzkpu7by3m4u7g Translations:Help:TemplateData/417/cs 1198 1109138 5386210 3823533 2022-07-28T12:10:27Z ENeRZet 17359278 wikitext text/x-wiki V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. 6jr5hyndm2tfmh0ix3i86csm97o6sj3 Translations:Help:TemplateData/419/cs 1198 1109140 5386224 3823537 2022-07-28T12:15:16Z ENeRZet 17359278 wikitext text/x-wiki Hodnota $1 je určena pro jméno souboru hostované buď lokálně na wiki nebo na Wikimedia Commons. cvmj5og1qt2x3u2r1oeevhz5fd32khu Translations:Help:TemplateData/420/cs 1198 1109141 5386220 3823539 2022-07-28T12:13:12Z ENeRZet 17359278 wikitext text/x-wiki * V aplikaci VisualEditoru a editoru wikitext 2017 nemá $1 žádný viditelný efekt. t4cqr2h0a2o9wh84578wpj4rl5e8v6s Translations:Help:TemplateData/426/cs 1198 1109147 5386228 3823551 2022-07-28T12:17:34Z ENeRZet 17359278 wikitext text/x-wiki V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. 6jr5hyndm2tfmh0ix3i86csm97o6sj3 Translations:Help:TemplateData/427/cs 1198 1109148 5386230 3823553 2022-07-28T12:20:07Z ENeRZet 17359278 wikitext text/x-wiki Nemá žádný jiný viditelný efekt a nebrání vložení nešablony. 09ffhzngqcqni6h49uhrxwsm79o4htm Translations:Help:TemplateData/430/cs 1198 1109151 5386234 3823561 2022-07-28T12:21:01Z ENeRZet 17359278 wikitext text/x-wiki V aplikaci VisualEditoru a editoru wikitext 2017 navíc vynutí, aby obsah vstupního pole zůstal na jednom řádku. 6jr5hyndm2tfmh0ix3i86csm97o6sj3 Translations:Help:TemplateData/433/cs 1198 1109154 5386238 3823567 2022-07-28T12:21:37Z ENeRZet 17359278 wikitext text/x-wiki * V aplikaci VisualEditoru a editoru wikitext 2017 nemá $1 žádný viditelný efekt. t4cqr2h0a2o9wh84578wpj4rl5e8v6s Translations:Help:TemplateData/436/cs 1198 1109191 5386244 3823750 2022-07-28T12:23:30Z ENeRZet 17359278 wikitext text/x-wiki * V aplikaci VisualEditoru a editoru wikitext 2017 nemá $1 žádný viditelný efekt. t4cqr2h0a2o9wh84578wpj4rl5e8v6s Translations:Help:TemplateData/439/cs 1198 1109195 5386205 4676462 2022-07-28T12:09:34Z ENeRZet 17359278 wikitext text/x-wiki * V aplikaci VisualEditor a editoru wikitext v roce 2017 přepíše $1 viditelné efekty $2. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. 2dhsn9xvxtsqqe265ohs0tvlkd804np 5386212 5386205 2022-07-28T12:11:18Z ENeRZet 17359278 wikitext text/x-wiki * V aplikaci VisualEditoru a editoru wikitext v roce 2017 přepíše $1 viditelné efekty $2. Pokud jsou oba nastaveny, nebude vstupní pole obsahovat ikonu URL ani červeně zvýrazněnou, pokud uživatel klepne na odchod, aniž by zadal platnou adresu URL. nvs2f21gd26c1b9jnd37uk995xq2hfw Translations:Help:TemplateData/388/cs 1198 1109205 5386246 3823780 2022-07-28T12:25:56Z ENeRZet 17359278 wikitext text/x-wiki Toto podtržítko slouží k označení minimální délky hodnoty ve znacích a může být opakováno, například $1. 6w96kvs1kn7xb1q34bd3dlfjyq9eqrv Translations:Help:TemplateData/396/cs 1198 1109225 5386249 5242992 2022-07-28T12:29:51Z ENeRZet 17359278 wikitext text/x-wiki Wikitext by měl splňovat minimálně $1, jinak dojde k neplatnosti formátového řetězce. clk3b1o43j7e1qa1ahrq8usg5nbnjsi 5386251 5386249 2022-07-28T12:30:14Z ENeRZet 17359278 wikitext text/x-wiki Wikitext by měl splňovat minimálně $1, jinak bude neplatný formátovací řetězec. mgxb1ii8044uuoenfvvctwl3k83g8zs Translations:Help:TemplateData/216/cs 1198 1109228 5386253 3823828 2022-07-28T12:30:59Z ENeRZet 17359278 wikitext text/x-wiki Formát řetězce rkcwdzuwbncisu899lz72czdrwgshtn Translations:Help:TemplateData/218/cs 1198 1109230 5386255 3823832 2022-07-28T12:31:39Z ENeRZet 17359278 wikitext text/x-wiki Inlin formátování 0je73gie0qmxs1zlc4m8y4xa6i5zr1a 5386257 5386255 2022-07-28T12:31:48Z ENeRZet 17359278 wikitext text/x-wiki Inline formátování mcu3gtqkidaytes4w107lhaz4mv5f04 Translations:Help:TemplateData/220/cs 1198 1109232 5386259 3823838 2022-07-28T12:32:50Z ENeRZet 17359278 wikitext text/x-wiki Žádná mezera před názvem parametru, každá šablona na samostatném řádku 2fga4i2qiysbyzk2z4vnfwgtm3p98uu Translations:Help:TemplateData/223/cs 1198 1109235 5386261 3823846 2022-07-28T12:33:58Z ENeRZet 17359278 wikitext text/x-wiki Znaky svislítka na konci předchozího řádku bqgl2kbxv208b3vathfvzbc0os7ou88 Translations:Help:TemplateData/225/cs 1198 1109237 5386263 3823850 2022-07-28T12:34:21Z ENeRZet 17359278 wikitext text/x-wiki Šablona na začátku řádku, parametry zarovnány podle odsazení, svislítko vpředu oaevpkr2tfb4zriq8rzr94h9z663gl1 Translations:Help:TemplateData/170/cs 1198 1109239 5386265 3823854 2022-07-28T12:35:05Z ENeRZet 17359278 wikitext text/x-wiki Můžete zkopírovat prázdnou boilerplate (předlohu) níže a přidat do šablony nová TemplateData. Zahrnuty jsou pouze nejběžnější značky. i2hkmcnby910dkwc4in49h0tlotkner Translations:Help:TemplateData/232/cs 1198 1109241 5386267 4987705 2022-07-28T12:35:42Z ENeRZet 17359278 wikitext text/x-wiki === $1 / Špatný formát JSON === ofhufxkj4rf8zx75gdj3x0j8cf49z9y Translations:New requirements for user signatures/2/ja 1198 1109245 5386355 3928968 2022-07-28T13:22:46Z Shirayuki 472859 update wikitext text/x-wiki [[$1|編集機能チーム]]では署名要件をコード化してウィキペディアのソフトウェアに埋め込むという案につき、 皆さんからのご意見ご感想を募集中です。 4enjjxgxpqglrk15b1nvq1a3ripr0nj Translations:Help:TemplateData/452/cs 1198 1109263 5386279 3823903 2022-07-28T12:41:43Z ENeRZet 17359278 wikitext text/x-wiki K této chybě dochází, pokud uvedete v $1 parametr, který není uveden v $2. f21b1ejug0rdqy3n047i6ye1f68g1sp Translations:Help:TemplateData/453/cs 1198 1109265 5386281 3823907 2022-07-28T12:43:15Z ENeRZet 17359278 wikitext text/x-wiki Číslo v hranatých závorkách odkazuje na chybějící parametr v $1. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože $1 je pole. 0 je první, 1 je druhý atd. 9nkin1vo6zb38cs8n8bq1dsgqneaso6 Translations:Help:TemplateData/455/cs 1198 1109268 5386288 3823913 2022-07-28T12:45:15Z ENeRZet 17359278 wikitext text/x-wiki Případně můžete tuto chybu odstranit odebráním objektu $1. qb4apfiabhixvyp5xlqxkvtf1nw09qg Translations:Help:TemplateData/176/cs 1198 1109274 5386333 3823927 2022-07-28T13:17:57Z ENeRZet 17359278 wikitext text/x-wiki V [[w:de:Template:TemplateData|šabloně dewiki TemplateData]] jsou data šablony zobrazena v rámečku a šablona je přidána do [[w:de:category:Vorlage:mit_TemplateData|kategorie]] šablon se šablonou data 7j6ko8m4gur37knniqgpk12ig9dswji Translations:Help:TemplateData/457/cs 1198 1109775 5386290 3825313 2022-07-28T12:45:52Z ENeRZet 17359278 wikitext text/x-wiki K této chybě dochází, pokud uvedete v $1 parametr, který není uveden v $2. f21b1ejug0rdqy3n047i6ye1f68g1sp Translations:Help:TemplateData/458/cs 1198 1109776 5386292 3825315 2022-07-28T12:46:17Z ENeRZet 17359278 wikitext text/x-wiki Číslo v hranatých závorkách odkazuje na chybějící parametr v $1. Odkazuje na jeho pořadí v sekvenci, ale to je o jednu méně, než je jeho skutečná pozice, protože $1 je pole. 0 je první, 1 je druhý atd. 9nkin1vo6zb38cs8n8bq1dsgqneaso6 Translations:Help:TemplateData/460/cs 1198 1109778 5386298 3825320 2022-07-28T12:47:27Z ENeRZet 17359278 wikitext text/x-wiki Případně můžete tuto chybu odstranit odebráním objektu $1. qb4apfiabhixvyp5xlqxkvtf1nw09qg Translations:Help:TemplateData/461/cs 1198 1109779 5386300 4987711 2022-07-28T12:48:02Z ENeRZet 17359278 wikitext text/x-wiki === Očekává se, že vlastnost "$1" bude typu $2. === nztfyzkpoviaikadoajpuql8beyethe Translations:Help:TemplateData/448/cs 1198 1109816 5386306 4987723 2022-07-28T12:50:55Z ENeRZet 17359278 wikitext text/x-wiki Chcete-li to vyřešit, ujistěte se, že hodnota po $5 se rovná $1 nebo $2 a že nedochází k pravopisným chybám. Pokud je to wikitext, ujistěte se, že obsahuje minimálně $3 a že v syntaxi nejsou chyby, které by normálně způsobily selhání šablony. Jako jsou duplicitní znaménka rovná se nebo chybějící nebo duplicitní složené závorky. Viz část [[$4|Vlastní formáty]] pro syntaxi vlastních formátů. rnfblwqo9dyk17oew1cgxalo4hnfzdi Translations:Help:TemplateData/450/cs 1198 1109818 5386308 3825439 2022-07-28T12:51:36Z ENeRZet 17359278 wikitext text/x-wiki Případně můžete tuto chybu odstranit odebráním objektu $1. qb4apfiabhixvyp5xlqxkvtf1nw09qg Translations:Help:TemplateData/471/cs 1198 1109831 5386316 4676508 2022-07-28T12:53:38Z ENeRZet 17359278 wikitext text/x-wiki Dochází k ní také v případě, že uvedete parametr v jakémkoli objektu TemplateData, který není parametrem daného objektu. Může to být způsobeno pravopisnými chybami nebo jste možná zapsali parametr jednoho objektu TemplateData pod jiný objekt, ke kterému nepatří. hbe6b9ws99gh5dinq9zexdoglt103q7 Translations:Help:TemplateData/492/cs 1198 1109833 5386320 3825447 2022-07-28T12:55:44Z ENeRZet 17359278 wikitext text/x-wiki Alternativně, pokud je neočekávaný parametr pod parametrem šablony uvnitř $1, uvidíte jeho název za "params.''parametername''." v chybě. 65uy9cqltggy11cg393vk0kt7poa80m Translations:Help:TemplateData/473/cs 1198 1109834 5386324 4676535 2022-07-28T12:56:38Z ENeRZet 17359278 wikitext text/x-wiki Chcete-li provést opravu, ujistěte se, že v názvech parametrů nejsou žádné pravopisné chyby a ujistěte se, že vaše parametry jsou umístěny správně. 99m7t6thmie7onhytoqowqek4gd8i9g Translations:Help:TemplateData/108/cs 1198 1109842 5386328 3825473 2022-07-28T13:03:32Z ENeRZet 17359278 wikitext text/x-wiki Seznam aktuálních chyb a požadavků na funkce je k dispozici [[$bugzilla|v nástroji pro sledování chyb Wikimedie]]. b7hp7w9aq7mq319xsyf8xvwtvk3dqk7 Translations:Help:TemplateData/173/cs 1198 1109845 5386331 3825481 2022-07-28T13:15:03Z ENeRZet 17359278 wikitext text/x-wiki Nástroj, který načte zdrojový wikikód šablony, pokusí se najít všechny použité parametry a vytvoří kostru dokumentu s uvedenými parametry. kaa2f99sh3o00g04emj5s6bdws96i4m Skin:MonoBook/hu 106 1110489 5386337 5307631 2022-07-28T13:19:25Z Shirayuki 472859 outdated wikitext text/x-wiki <languages/> <!-- this is a comment to generate a page image at ?action=info. You can remove it safely. --> {{Bundled|1.1|type=skin}} {{Skin |status = stable |name = MonoBook |image = Dantman-Skin-monobook.png |imagesize = 330 |license = GPL-2.0-or-later |compatibility policy = rel |download = {{WikimediaDownloadSkin|MonoBook}} |parameters = |mediawiki = 1.29+ |example = https://en.wikipedia.org/w/index.php?useskin=monobook |phabricator = MediaWiki-skins-MonoBook |hook1 = GetPreferences |hook2 = ResourceLoaderRegisterModules |newhook1 = MonoBookAfterContent |newhook2 = MonoBookAfterToolbox |newhook3 = MonoBookTemplateToolboxEnd |vagrant-role = monobook }} <span lang="en" dir="ltr" class="mw-content-ltr">'''MonoBook''' is a skin.</span> <span class="mw-translate-fuzzy"><nowiki /></span> It replaced the [[Skin:Standard|Standard]] skin as the default, and was in turn replaced by the [[Skin:Vector|Vector]] skin. <span class="mw-translate-fuzzy">A mobilkijelzőkhöz később elérhetővé vált a [[:hu:Reszponzív weboldal|reszponzív felület]] támogatása.</span> <span lang="en" dir="ltr" class="mw-content-ltr">With JavaScript deactivated on the mobile view, for example, the personal tools, page actions, and sidebar are located at the page bottom with anchored shortcuts from the top buttons which appear as clip art icons instead of text links.</span> The mobile view also reveals an anchored "[[#globalWrapper|to top]]" shortcut at the page bottom. == Telepítés == A felület szerepel a [[Special:MyLanguage/Download|letölthető MediaWiki-csomagban]]. Csak akkor szükséges külön telepítened, ha a MediaWikit eltérő módszerrel installáltad. {{SkinInstall |registration=required |vagrant=monobook }} <div lang="en" dir="ltr" class="mw-content-ltr"> == User settings == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The responsive styles for MonoBook can be disabled or enabled via a user preference: <code>monobook-responsive</code>, which defaults to true. </div> == Megjegyzések == Korábban a MonoBook volt a MediaWiki legnépszerűbb felülete. A {{ll|Wikipedia Usability Initiative}} munkájának köszönhetően 2010. május 13-ától ({{ll|MediaWiki 1.16}}, {{git|2833b07a7b833a17e0478125a00f15bc0158b8fb}}) az alapértelmezett felület a {{ll|Skin:Vector|nsp=0}} lett, melynek célja a használhatóság javítása és új szerkesztők bevonzása. A felület régebbi MediaWiki-verziót használó weboldalakon továbbra is alapértelmezés. A MonoBook fejlesztésével kapcsolatos információkért lásd az [[m:Special:MyLanguage/Layout design document|elrendezési leírást]] és a [[m:Special:MyLanguage/MediaWiki 1.3 comments and bug reports/Archive|MediaWiki 1.3-mal kapcsolatos visszajelzéseket és hibajelentéseket]]. MonoBook originally featured navigation tabs at the bottom of the content area in addition to the top, in resemblance to [[Skin:Nostalgia|Nostalgia]], the earliest skin.<ref>[[:File:Wp-lupo-talk-screenshot.png|2004 screenshot of ''Monobook'']]</ref> == Jelenlegi állapot == A MonoBookot [[meta:Special:MyLanguage/Turning off outdated skins#Why are you keeping these four skins?|2013]]-tól nem a Wikimédia Alapítvány, hanem önkéntes fejlesztők támogatják. A 2019-es állapot szerint négy, önkéntesek által támogatott felület használható: MonoBook, {{ll|Skin:Cologne Blue|nsp=0}}, {{ll|Skin:Modern|nsp=0}} és {{ll|Skin:Modern|nsp=0}}. {{OnWikimedia}} {{Used by|canasta=1|miraheze=1|mywikis=1|prowiki=1|semantic core=1}} == References == <references /> [[Category:Mobile skins{{#translation:}}]] 3zit85agqpido6bucv73yh3gza9aiau Editor/cs 0 1112401 5386457 5370842 2022-07-28T14:20:06Z ENeRZet 17359278 wikitext text/x-wiki <languages/> {{Disambiguation}} Možná hledáte: == Aktuální == {| class="wikitable sortable" |+Aktuální editační software na wiki Wikimedia !Editační nástroj !Snímek obrazovky !Rok !Základy !Poznámky |- |výchozí editor MediaWiki, což je HTML {{tag|textarea|open}} |[[File:Basic MediaWiki editor without toolbar.png|alt=Snímek obrazovky HTML textarea|center|frameless]] |2003 |Stolní a mobilní |Nemá panel nástrojů. Je vidět, když je zakázán JavaScript nebo když je zakázáno "{{int|Wikieditor-toolbar-preference}}" ve [[Special:Preferences#mw-prefsection-editing|{{int|preferences}}]]. |- |[[Special:MyLanguage/Extension:WikiEditor|Rozšíření:WikiEditor]] |[[File:VectorEditorBasic-en.png|alt=Snímek obrazovky WikiEditoru|center|frameless]] |2010 |Počítač |To je vidět, když je ve [[Special:Preferences#mw-prefsection-editing|{{int|preferences}}]] aktivován "{{int|Wikieditor-toolbar-preference}}". |- |[[Special:MyLanguage/VisualEditor|VisualEditor]] |[[File:VisualEditor toolbar and start of article.png|alt=Snímek obrazovky zobrazující vizuální režim VisualEditoru|center|frameless]] |2012 |Stolní a mobilní |Systém pro úpravu textů ve formátu RTF |- |[[Special:MyLanguage/2017 wikitext editor|Editor wikitextu 2017]] |[[File:2017 wikitext editor toolbar and start of article.png|alt=Snímek obrazovky zabudovaného režimu wikitext VisualEditor|center|frameless]] |2017 |Počítač |Režim v rámci {{ll|Extension:VisualEditor}} pro úpravu označení wiki. |- |[[Special:MyLanguage/Extension:Proofread Page|Korektura stránky]] |[[File:Proofread Page editor.png|center|frameless]] |2006 |Počítač |Používá se na [[S:|Wikisources]] |- |[[Special:MyLanguage/Extension:WikEd|wikEd]] |[[File:WikEd screenshot.png|alt=Snímek obrazovky wikEd|center|frameless]] |2006 |Počítač |Plně dobrovolně podporovaný editor wikitext. Toto je obecně spuštěno jako gadget nebo uživatelský skript, ale je spuštěno jako rozšíření na některých wiki bez Wikimedie. |- |[[Special:MyLanguage/Extension:CodeEditor|CodeEditor]] |[[File:CodeEditor extension screenshot.png|alt=Snímek obrazovky editoru kódu|center|frameless]] |2011 |Počítač |Používá se pro úpravy JavaScriptu a dalších kódových stránek. |- |wikitextový editor {{ll|Extension:MobileFrontend|nsp=0}} |[[File:Switching edit modes on Mobile Web 2014-11-04.png|alt=Snímek obrazovky editace wikitextu na mobilním webu|center|frameless]] |2013 |Mobilní | |- |[[Special:MyLanguage/Content translation|ContentTranslation]] |[[File:Content-Translation-Warning.png|alt=Snímek obrazovky editoru ContentTranslation|center|frameless]] |2014 |Počítač | |- |[[Special:MyLanguage/Structured_Discussions|Strukturované diskuse]] (dříve známé jako Flow) |[[File:Flow comment.png|alt=Ukázka komentáře a začátek odpovědi na toto téma ve Strukturovaných diskusích|center|frameless]] |2013 |Stolní a mobilní |Strukturované diskuse podporuje wikitext a vizuální režimy. |- |[[Talk pages project/New discussion|New Discussion Tool]] |[[File:New Discussion Tool v1.0.png|center|frameless]] |2020 |Počítač (brzy pro mobily) |Inline formulář pro zahájení diskuzí na nové diskusní stránce. Je vybavena jak režimy <code>Visual</code>, tak <code>Source</code>. |- | [[Talk pages project/Replying|Reply Tool]] |[[File:Screenshot of DiscussionTools toolbar in source.png|center|frameless]] |2020 |Počítač (brzy pro mobily) |Nástroj pro reakci na konkrétní komentáře diskusní stránky. Komentáře jsou automaticky podepsány a odsazeny. Je vybavena jak režimy <code>Visual</code>, tak <code>Source</code>. |- |Editor v aplikaci [[Special:MyLanguage/Wikimedia Apps/Android FAQ|Android]] |[[File:Device-2017-02-17-141705.png|alt=Snímek obrazovky editačního rozhraní v telefonu se systémem Android|center|frameless|249x249px]] |2014 |Mobilní | |- |Editor v aplikaci [[Special:MyLanguage/Wikimedia Apps/iOS FAQ|iOS]] |[[File:Wikipedia iOS Application Editor.PNG|alt=Snímek obrazovky editačního rozhraní v iPhone|center|frameless|249x249px]] |2014 |Mobilní | |- |[[Extension:TemplateData|TemplateData]] editor |[[File:TemplateData GUI editor new.png|center|frameless]] |2014 |Počítač | |- |[[voy:en:Project:Listing editor|Editor seznamů Wikivoyage]] |[[File:Wikivoyage-listing-editor-v2.1-wide.png|center|frameless]] |2013 |Počítač |Specializovaný editační nástroj založený na JavaScriptu pro vkládání jedné z několika šablon na Wikivoyage |- |} == Bývalé == {| class="wikitable sortable" |+Bývalý editační software na wiki Wikimedia |- !Editační nástroj !Snímek obrazovky !Rok !Základy !Poznámky |- |"Klasický" editor JavaScriptu z roku 2006, {{ll|Manual:EditPage.php}} |[[File:Edit toolbar - 2.png|alt=Snímek obrazovky z editoru wikitext 2006|center|frameless]] |2006–2018 |Počítač |Toto bylo vidět, když byla v letech 2006–2010 povolena preference "showtoolbar". Poté se to zobrazilo pouze uživatelům, kteří deaktivovali předvolbu "vylepšený panel nástrojů" (editor 2010). Tento editor byl [[phab:T30856|odstraněn]] v [[MediaWiki 1.32]]. Podobný panel nástrojů je k dispozici jako místní gadget podporovaný dobrovolníky u některých wiki. |- |Originální editor wikitextu MobileFrontend | |2012–2014 |Mobilní |Jednalo se o soubor specifických úprav pro stolní wikitextový editor. Již není nasazen. |- |} == Související stránky == * [[MediaWiki:Edittools]] – není součástí žádného editoru, ale objevuje se pod některými editačními prostředími * {{ll|Extension:CharInsert}} – není součástí žádného editoru, ale objevuje se pod některými editačními prostředími [[Category:Edit extensions{{#translation:}}| ]] [[Category:Edit{{#translation:}}| ]] 2sz2v9ffhnape8miyt99yxkmjlzcz0j Translations:Editor/46/cs 1198 1112440 5386456 4570784 2022-07-28T14:20:05Z ENeRZet 17359278 wikitext text/x-wiki wikitextový editor $1 366455m41xx648rwh4uni7jdprkmvyg Groups/tr 0 1114115 5387365 5190131 2022-07-28T22:11:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki grupları''' belirli konular ve coğrafi alanlar kapsamında açık kaynaklı topluluk etkinlikleri düzenlemektedir. Bunlar, [[meta:Special:MyLanguage/Wikimedia user groups|Wikimedia Kullanıcı Grupları]] MediaWiki bağlamında bir koordinasyon düzeyi üzerinde anlaşmaya varmıştır. Bu nedenle, [[Events|etkinlikler]], [[Volunteer coordination and outreach/Training materials|eğitim]], tanıtım ve Vikipedi'den yararlanan diğer teknik faaliyetlerde [[wmf:|Wikimedia Vakfı]] kapasitesini arttırırlar. Wikimedia hareketi ve MediaWiki yazılımı. <span class="mw-translate-fuzzy">MediaWiki Grupları [[Special:MyLanguage/How to contribute|farklı uzmanlıklar]] üyelerine ve uzmanlık düzeylerine açıktır.</span> Daha zengin ve daha çeşitli daha iyidir. Katkıda bulunmak ve öğrenmek isteyen teknik olmayan kullanıcılar da memnuniyetle karşılıyorlar! Tüm gruplar [[wmf:Friendly space policy|Samimi alan politikası]]'na bağlıdır. MediaWiki grupları, [[Groups/Wikimedia support|destek talep edebilir]] ve Wikimedia Vakfı'dan çeşitli biçimlerde bölümler alabilir. == Tematik gruplar == Tematik MediaWiki grupları, daha geniş [[:tr:Özgür ve açık kaynak kodlu yazılım|FLOSS]] topluluğundaki mantıksal meslektaşlarıyla işbirliği yapar. Çevrimiçi işbirliği yapan küresel gruplardır. * Aynı odak içindeki topluluklarla temas halindedirler. * Aynı konunun etkinliklerine katılırlar. * İlgili eğitim ve sosyal yardım faaliyetlerini teşvik ederler. * Wikimedia.org'daki ilgili belgelerin geliştirilmesine yardımcı olurlar. * İlgili geliştirme ekipleriyle işbirliği yaparlar. * Sonunda bazıları [//wikimania.wikimedia.org/ Wikimania]'da buluşuyor. == Yerel gruplar == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Yerel MediaWiki grupları [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia bölümleri]], [[:tr:Vikipedi:Buluşma|Vikipedi buluşmaları]] ve Wikimedia, özgür yazılım, özgür kültür ile ilgili diğer yerel topluluklarla işbirliği yapmaktadır. Odak noktaları yüz yüze faaliyetlerden oluşmaktadır: * Yerel etkinliklerin organizasyonu: buluşmalar, eğitim, bilgisayar korsanları ... Bu etkinlikler [[wmf:Friendly_space_policy|WMF Dostu alan politikası]]na uyar. * Kendi alanında düzenlenen etkinliklere katılım. * Ürün dağıtımı. * Yerel MediaWiki ve Wikimedia etkinliklerine yerel katkıda bulunanların tanıtımı. <div class="mw-translate-fuzzy"> Ayrıca İngilizce konuşmayan gruplar için: * [[Special:MyLanguage/translatewiki.net|translatewiki.net]] süreçlerini takiben belgelerin ve yazılımların yerelleştirilmesi. </div> Yerel gruplar gerçekten yerel olmalıdır. Başlangıç noktaları örn. Recife, Münih veya Saint Petersburg Brezilya, Almanya veya Rusya'dan daha iyidir. <span class="mw-translate-fuzzy">Bölgesel koordinasyon için bir kanalı kaçırırsanız, o zaman bir [[meta:Mailing_lists/Overview#Regional_mailing_lists|bölgesel posta listesi]] ve/veya [[meta:Mailing lists#Create a new list|yerel posta listesi]] için [[meta:Mailing lists/Overview#Local|oluşturulmasını talep etmeyi]] düşünün.</span> == Grup oluşturma == Bir grup önermek için kimseye ihtiyacınız yok, sadece kendiniz. Onayını almak için en az üç katılımcıya sahip olmalısınız. MediaWiki grubunuzu oluşturmak için daha fazla ayrıntı için [[Groups/Proposals]] sayfasına bakın. [[Category:MediaWiki Communication{{#translation:}}]] fffg33vc9mib6acsdboqjh9qxwcyele 5387382 5387365 2022-07-28T22:13:13Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki grupları''' belirli konular ve coğrafi alanlar kapsamında açık kaynaklı topluluk etkinlikleri düzenlemektedir. Bunlar, [[meta:Special:MyLanguage/Wikimedia user groups|Wikimedia Kullanıcı Grupları]] MediaWiki bağlamında bir koordinasyon düzeyi üzerinde anlaşmaya varmıştır. Bu nedenle, [[Events|etkinlikler]], [[Volunteer coordination and outreach/Training materials|eğitim]], tanıtım ve Vikipedi'den yararlanan diğer teknik faaliyetlerde [[wmf:|Wikimedia Vakfı]] kapasitesini arttırırlar. Wikimedia hareketi ve MediaWiki yazılımı. MediaWiki Grupları [[Special:MyLanguage/How to contribute|farklı uzmanlıklar]] üyelerine ve uzmanlık düzeylerine açıktır. Daha zengin ve daha çeşitli daha iyidir. Katkıda bulunmak ve öğrenmek isteyen teknik olmayan kullanıcılar da memnuniyetle karşılıyorlar! Tüm gruplar [[wmf:Friendly space policy|Samimi alan politikası]]'na bağlıdır. MediaWiki grupları, [[Groups/Wikimedia support|destek talep edebilir]] ve Wikimedia Vakfı'dan çeşitli biçimlerde bölümler alabilir. == Tematik gruplar == Tematik MediaWiki grupları, daha geniş [[:tr:Özgür ve açık kaynak kodlu yazılım|FLOSS]] topluluğundaki mantıksal meslektaşlarıyla işbirliği yapar. Çevrimiçi işbirliği yapan küresel gruplardır. * Aynı odak içindeki topluluklarla temas halindedirler. * Aynı konunun etkinliklerine katılırlar. * İlgili eğitim ve sosyal yardım faaliyetlerini teşvik ederler. * Wikimedia.org'daki ilgili belgelerin geliştirilmesine yardımcı olurlar. * İlgili geliştirme ekipleriyle işbirliği yaparlar. * Sonunda bazıları [//wikimania.wikimedia.org/ Wikimania]'da buluşuyor. == Yerel gruplar == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Yerel MediaWiki grupları [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia bölümleri]], [[:tr:Vikipedi:Buluşma|Vikipedi buluşmaları]] ve Wikimedia, özgür yazılım, özgür kültür ile ilgili diğer yerel topluluklarla işbirliği yapmaktadır. Odak noktaları yüz yüze faaliyetlerden oluşmaktadır: * Yerel etkinliklerin organizasyonu: buluşmalar, eğitim, bilgisayar korsanları ... Bu etkinlikler [[wmf:Friendly_space_policy|WMF Dostu alan politikası]]na uyar. * Kendi alanında düzenlenen etkinliklere katılım. * Ürün dağıtımı. * Yerel MediaWiki ve Wikimedia etkinliklerine yerel katkıda bulunanların tanıtımı. <div class="mw-translate-fuzzy"> Ayrıca İngilizce konuşmayan gruplar için: * [[Special:MyLanguage/translatewiki.net|translatewiki.net]] süreçlerini takiben belgelerin ve yazılımların yerelleştirilmesi. </div> Yerel gruplar gerçekten yerel olmalıdır. Başlangıç noktaları örn. Recife, Münih veya Saint Petersburg Brezilya, Almanya veya Rusya'dan daha iyidir. <span class="mw-translate-fuzzy">Bölgesel koordinasyon için bir kanalı kaçırırsanız, o zaman bir [[meta:Mailing_lists/Overview#Regional_mailing_lists|bölgesel posta listesi]] ve/veya [[meta:Mailing lists#Create a new list|yerel posta listesi]] için [[meta:Mailing lists/Overview#Local|oluşturulmasını talep etmeyi]] düşünün.</span> == Grup oluşturma == Bir grup önermek için kimseye ihtiyacınız yok, sadece kendiniz. Onayını almak için en az üç katılımcıya sahip olmalısınız. MediaWiki grubunuzu oluşturmak için daha fazla ayrıntı için [[Groups/Proposals]] sayfasına bakın. [[Category:MediaWiki Communication{{#translation:}}]] 76eqphee1nx5je2f16jh8o8gz43wqv0 5387386 5387382 2022-07-28T22:14:13Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{historical|'''See [[meta:Wikimedia user groups]] and [[Special Interest Groups]] instead.'''}} {{for|user groups on MediaWiki wikis|Manual:User rights}} [[File:Groups logo shiny.svg|{{dir|{{pagelang}}|left|right}}|200px]] '''MediaWiki grupları''' belirli konular ve coğrafi alanlar kapsamında açık kaynaklı topluluk etkinlikleri düzenlemektedir. Bunlar, [[meta:Special:MyLanguage/Wikimedia user groups|Wikimedia Kullanıcı Grupları]] MediaWiki bağlamında bir koordinasyon düzeyi üzerinde anlaşmaya varmıştır. Bu nedenle, [[Events|etkinlikler]], [[Volunteer coordination and outreach/Training materials|eğitim]], tanıtım ve Vikipedi'den yararlanan diğer teknik faaliyetlerde [[wmf:|Wikimedia Vakfı]] kapasitesini arttırırlar. Wikimedia hareketi ve MediaWiki yazılımı. MediaWiki Grupları [[Special:MyLanguage/How to contribute|farklı uzmanlıklar]] üyelerine ve uzmanlık düzeylerine açıktır. Daha zengin ve daha çeşitli daha iyidir. Katkıda bulunmak ve öğrenmek isteyen teknik olmayan kullanıcılar da memnuniyetle karşılıyorlar! Tüm gruplar [[wmf:Friendly space policy|Samimi alan politikası]]'na bağlıdır. MediaWiki grupları, [[Groups/Wikimedia support|destek talep edebilir]] ve Wikimedia Vakfı'dan çeşitli biçimlerde bölümler alabilir. == Tematik gruplar == Tematik MediaWiki grupları, daha geniş [[:tr:Özgür ve açık kaynak kodlu yazılım|FLOSS]] topluluğundaki mantıksal meslektaşlarıyla işbirliği yapar. Çevrimiçi işbirliği yapan küresel gruplardır. * Aynı odak içindeki topluluklarla temas halindedirler. * Aynı konunun etkinliklerine katılırlar. * İlgili eğitim ve sosyal yardım faaliyetlerini teşvik ederler. * Wikimedia.org'daki ilgili belgelerin geliştirilmesine yardımcı olurlar. * İlgili geliştirme ekipleriyle işbirliği yaparlar. * Sonunda bazıları [//wikimania.wikimedia.org/ Wikimania]'da buluşuyor. == Yerel gruplar == <div class="toccolours"> * [[Groups/San Francisco|San Francisco]] </div> Yerel MediaWiki grupları [[meta:Special:MyLanguage/Wikimedia chapters|Wikimedia bölümleri]], [[:tr:Vikipedi:Buluşma|Vikipedi buluşmaları]] ve Wikimedia, özgür yazılım, özgür kültür ile ilgili diğer yerel topluluklarla işbirliği yapmaktadır. Odak noktaları yüz yüze faaliyetlerden oluşmaktadır: * Yerel etkinliklerin organizasyonu: buluşmalar, eğitim, bilgisayar korsanları ... Bu etkinlikler [[wmf:Friendly_space_policy|WMF Dostu alan politikası]]na uyar. * Kendi alanında düzenlenen etkinliklere katılım. * Ürün dağıtımı. * Yerel MediaWiki ve Wikimedia etkinliklerine yerel katkıda bulunanların tanıtımı. Ayrıca İngilizce konuşmayan gruplar için: * [[Special:MyLanguage/translatewiki.net|translatewiki.net]] süreçlerini takiben belgelerin ve yazılımların yerelleştirilmesi. Yerel gruplar gerçekten yerel olmalıdır. Başlangıç noktaları örn. Recife, Münih veya Saint Petersburg Brezilya, Almanya veya Rusya'dan daha iyidir. <span class="mw-translate-fuzzy">Bölgesel koordinasyon için bir kanalı kaçırırsanız, o zaman bir [[meta:Mailing_lists/Overview#Regional_mailing_lists|bölgesel posta listesi]] ve/veya [[meta:Mailing lists#Create a new list|yerel posta listesi]] için [[meta:Mailing lists/Overview#Local|oluşturulmasını talep etmeyi]] düşünün.</span> == Grup oluşturma == Bir grup önermek için kimseye ihtiyacınız yok, sadece kendiniz. Onayını almak için en az üç katılımcıya sahip olmalısınız. MediaWiki grubunuzu oluşturmak için daha fazla ayrıntı için [[Groups/Proposals]] sayfasına bakın. [[Category:MediaWiki Communication{{#translation:}}]] 969o8hpbh862ylelssz5hs59t96fvkf Translations:Groups/4/tr 1198 1114119 5387381 3838150 2022-07-28T22:13:12Z Shirayuki 472859 update wikitext text/x-wiki MediaWiki Grupları [[$1|farklı uzmanlıklar]] üyelerine ve uzmanlık düzeylerine açıktır. kl6ja7i7ajm9xyrnwd3omyppnb27x3i Translations:Groups/25/tr 1198 1114202 5387385 3838438 2022-07-28T22:14:12Z Shirayuki 472859 update wikitext text/x-wiki Ayrıca İngilizce konuşmayan gruplar için: * $1 süreçlerini takiben belgelerin ve yazılımların yerelleştirilmesi. btzsie2qr4sme6brk2qx1lgncsybj1j UploadWizard/de 0 1115200 5386735 5385383 2022-07-28T18:51:37Z ThisCarthing 17456337 Created page with "Danke für deine Geduld und dein Verständnis :)" wikitext text/x-wiki <noinclude> <languages /> </noinclude><includeonly>{{Wikimedia engineering project information | name = UploadWizard | description = Eine Funktion, die das Hochladen von Dateien in [[:commons:|Wikimedia Commons]], die mit Wikipedia verknüpfte Medienbibliothek, vereinfacht. | start = 2015-01-01 | end = 2015-06-30 | group = [[Wikimedia Platform Engineering|Platform]] | EPM = [[User:RobLa-WMF|Rob Lanphier]] (engineering director) | team = [[User:GDubuc_%28WMF%29|Gilles Dubuc]], [[mw:User:Pginer|Pau Giner]], [[User:MarkTraceur|Mark Holmquist]], [[user:NeilK|Neil Kandalgaonkar]], [[mw:User:Keegan_(WMF)|Keegan Peterzell]], [[meta:User:Tgr|Gergő Tisza]] | previous = | next = | projectpage = UploadWizard | display = {{{display|}}} }}</includeonly> Der '''UploadWizard''' ist ein schrittweiser JavaScript-Assistent zum Hochladen von Multimediadateien auf eine MediaWiki-Website. Es ist als {{ll|Extension:UploadWizard}} erhältlich. {{TOC|align=right|limit=2}} == Gründe == <div lang="en" dir="ltr" class="mw-content-ltr"> The Upload Wizard aims to make it easier to contribute multimedia works to Wikimedia projects. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This tool is now widely used to upload images on Wikimedia Commons, the free media repository associated with Wikipedia; any media file shared on that site can be used in any Wikipedia page in any language.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Commons is curated by a multilingual community and recently reached 21 million files.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> More details about the origins of this project can be found in the [[Special:MyLanguage/UploadWizard/Archive|Upload Wizard archive page]]; the main feedback page is located at [[commons:Commons:Upload Wizard feedback|Commons:Upload Wizard feedback]]. </div> == Ziele == <div lang="en" dir="ltr" class="mw-content-ltr"> Here are some of our goals for Upload Wizard: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''engage more users''' to contribute media</span> * <span lang="en" dir="ltr" class="mw-content-ltr">provide a '''smoother experience''' for all</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''add more media''' content on our sites</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''fix critical bugs''', to make things work better</span> <span lang="en" dir="ltr" class="mw-content-ltr">In coming months, we propose to:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Plan & discuss''' improvements</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Solve '''bugs & technical debt'''</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Improve the '''user experience'''</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Incremental '''code refactoring'''</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Develop new '''modal tool''' for other uses</span> == Zeitplan == <div lang="en" dir="ltr" class="mw-content-ltr"> This is an estimated timeline based on our current work, as of January 2015. </div> ; <span lang="en" dir="ltr" class="mw-content-ltr">Q3 (Jan-Mar 2015)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Implement and deploy JS error logging to automatically capture errors affecting users</span> ; Q4 (Apr.-Juni 2015) * <span lang="en" dir="ltr" class="mw-content-ltr">Identify the main sources of the [http://multimedia-metrics.wmflabs.org/dashboards/uw# current drop-off] happening on the file step</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Significantly reduce the drop-off</span> == Benutzer == Zu unseren Hauptbenutzern für den Hochladeassistenten gehören: * neue Beitragende * erfahrende Beitragende <span lang="en" dir="ltr" class="mw-content-ltr">We will aim to support both user groups evenly, with an initial focus on Commons users - then contributors on Wikipedia and other sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that you must be registered and logged-in to use Upload Wizard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also aim to serve these secondary users:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">editors</span> * <span lang="en" dir="ltr" class="mw-content-ltr">campaign organizers</span> * Entwickler == Metriken == [[File:Upload Wizard Slides.pdf|thumb|400px|page=36]] [[File:Upload Wizard Slides.pdf|thumb|400px|page=37]] === Erste Metriken === Here are upload metrics for Upload Wizard from February 2014: (1) * 18k uploaders / month * 292k uploads / month It's worth noting that Upload Wizard represents: * 80% of all uploaders (14k per month, a lot more during Wiki Loves Monuments) * 56% of all uploads (141k per month, the rest are handled by bots and other uploads tools) For more info, click on the metrics graph thumbnails to the right. (1) Data from Wikimedia Commons in Feb 2014. Source: Wikimedia Foundation === Weitere Metriken === <div lang="en" dir="ltr" class="mw-content-ltr"> Here are key metrics we're considering to track the upload process: </div> * number of uploaders * number of uploads * upload drop-off rate * number of uploaded files used * number of uploaded files viewed We are starting development to collect more metrics data, and are tracking this work in these tickets: * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/541 Funnel Metrics for Upload Wizard (#541)] (in development for this sprint)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/609 Upload Wizard funnel metrics - basics (#609)] (done, but only 4 data points for now)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/305 Upload Wizard Metrics - Data collection 1: Major steps (#305)] (to be developed in coming weeks)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/603 Upload Wizard Metrics - Data Collection 2: Detailed Steps (#603)] (to be developed in coming weeks)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/587 Upload Wizard Metrics - Dashboards (#587)] (to be developed in coming weeks)</span> == Feedback == We are now reviewing hundreds of [[commons:Commons:Upload_Wizard_feedback|feedback posts]] and [[commons:Commons:Upload_help|help questions]] about Upload Wizard last year, which have been analyzed in [https://docs.google.com/a/wikimedia.org/spreadsheets/d/1AUKUODbKVQMtFgTbCm8l3Pee7l7xbpxf9idx_3PsCXE/edit#gid=0 this spreadsheet]. <div lang="en" dir="ltr" class="mw-content-ltr"> Here are some of the key issues reported: </div> * upload hangs * upload takes too long * issues with multiple files * confused by license forms * unclear prompts and error messages * problems with categories (e.g. can't search them) * issues with large files that don't load well * would like a progress bar during upload * want to add info while image loads * would like simple explanations * want other info templates == Benutzerfreundlichkeit == <div lang="en" dir="ltr" class="mw-content-ltr"> We have done a number of usability studies for Upload Wizard and plan to do more. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here are videos of some initial testing sessions: </div> * [https://www.usertesting.com/videos/AI1Psz9uNro?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T1] * [https://www.usertesting.com/videos/eM8j0rwubH0?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T2] * [https://www.usertesting.com/videos/pE4nRhgRmS0?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T3] * [https://www.usertesting.com/videos/katNyUV7qtw?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T4] We will consolidate these results when we run more user tests. For now, here are some [http://etherpad.wikimedia.org/p/design-multimedia-uploader preliminary observations and analysis of the current design] by our designer Pau Giner. <div lang="en" dir="ltr" class="mw-content-ltr"> == Current Workflow == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here are the main steps of the current workflow for Upload Wizard: </div> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Start</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Click on the Upload link</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Learn</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Reading the help infographic, click 'Continue'</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Select media files to upload, add more files if needed</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Rights</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Fill in author, source and license information</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Describe</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Fill in title, description, date or other info</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Use</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">copy code to add images to articles or share them with others</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To see how Upload Wizard currently works, [[commons:Special:UploadWizard|visit this page]] (must be logged in). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == New designs == </div> <span lang="en" dir="ltr" class="mw-content-ltr">Based on current feedback and usability tests, our designer Pau Giner has prepared some preliminary design ideas to help define our vision for Upload Wizard (see [[:File:Upload Wizard Slides.pdf|slides]] below).</span> <span lang="en" dir="ltr" class="mw-content-ltr">These are explorations and reflections about a more modern upload experience, but don't necessarily reflect what will be built, as more community consultation would be required.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Mockups==== </div> <gallery mode="nolines" perrow="3" widths="320px" heights="240px"> File:Upload Wizard Slides.pdf|page=11| File:Upload Wizard Slides.pdf|page=12| File:Upload Wizard Slides.pdf|page=13| File:Upload Wizard Slides.pdf|page=14| File:Upload Wizard Slides.pdf|page=15| File:Upload Wizard Slides.pdf|page=16| File:Upload Wizard Slides.pdf|page=17| File:Upload Wizard Slides.pdf|page=18| File:Upload Wizard Slides.pdf|page=19| File:Upload Wizard Slides.pdf|page=20| File:Upload Wizard Slides.pdf|page=21| File:Upload Wizard Slides.pdf|page=22| File:Upload Wizard Slides.pdf|page=23| File:Upload Wizard Slides.pdf|page=24| File:Upload Wizard Slides.pdf|page=25| </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> These mockups will be adjusted based on community feedback. </div> <span lang="en" dir="ltr" class="mw-content-ltr">These designs can be viewed together in [[:File:Upload Wizard Slides.pdf|these vision slides]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual screenshots will be added to this page soon.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Scenarios=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These first designs are based on these user scenarios: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Upload images to a page</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Upload a single image on a topic</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Upload multiple files on different topics</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Issues=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> They attempt to address these key issues: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Adding a picture to a page is disconnected</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Providing metadata is a big upfront effort</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Categorization is painful</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Multiple file upload</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Lack of aids for input</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Meaningless untranslatable titles</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Initial infographic is too verbose</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Help needed to understand licenses</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Upload button on Commons homepage is hard to find</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To learn more, check out [http://etherpad.wikimedia.org/p/design-multimedia-uploader these design notes] by our designer Pau Giner. </div> == Fehler == <div lang="en" dir="ltr" class="mw-content-ltr"> We keep track of Upload Wizard bugs [[phab:tag/mediawiki-extensions-uploadwizard/|in the bug tracker]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Over the years, many bugs have accumulated for this project, because Wikimedia Foundation did not have a dedicated team to address them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Now that the multimedia team has taken ownership of Upload Wizard, we will work diligently to fix the most important bugs first, then gradually resolve the rest of the relevant issues over time.</span> Danke für deine Geduld und dein Verständnis :) <span lang="en" dir="ltr" class="mw-content-ltr">If you find any technical bugs, please [https://phabricator.wikimedia.org/maniphest/task/create/?projects=MediaWiki-extensions-UploadWizard report them].</span> {{anchor|Compatibility}} == Kompatibilität == <div lang="en" dir="ltr" class="mw-content-ltr"> To be able to run UploadWizard, the user's browser must: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have [[w:JavaScript|JavaScript]] enabled</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Support [[w:ECMAScript#5th Edition|ECMAScript 5]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Support [[w:HTML5 File API|HTML5 File API]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Support [[w:MIME#Form-Data|form-data]] in [[w:XMLHttpRequest|XMLHttpRequest]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Otherwise, the standard MediaWiki file upload form is displayed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Supported browsers include Firefox 13+, Chrome 21+, Internet Explorer 10+, Safari 7+ and Opera 12+. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tasks == </div> [[phab:tag/mediawiki-extensions-uploadwizard/|https://phabricator.wikimedia.org/tag/mediawiki-extensions-uploadwizard/]] == Weitere Werkzeuge == <div lang="en" dir="ltr" class="mw-content-ltr"> Besides Upload Wizard, other upload tools are available to users, which are tracked at [[commons:Special:MyLanguage/Commons:Upload tools|commons:Commons:Upload tools]]. </div> [[Category:Multimedia{{#translation:}}]] oki0d8sfrqrux6un9ygv06xozm5e1bi 5386737 5386735 2022-07-28T18:51:42Z ThisCarthing 17456337 Created page with "== Aufgaben ==" wikitext text/x-wiki <noinclude> <languages /> </noinclude><includeonly>{{Wikimedia engineering project information | name = UploadWizard | description = Eine Funktion, die das Hochladen von Dateien in [[:commons:|Wikimedia Commons]], die mit Wikipedia verknüpfte Medienbibliothek, vereinfacht. | start = 2015-01-01 | end = 2015-06-30 | group = [[Wikimedia Platform Engineering|Platform]] | EPM = [[User:RobLa-WMF|Rob Lanphier]] (engineering director) | team = [[User:GDubuc_%28WMF%29|Gilles Dubuc]], [[mw:User:Pginer|Pau Giner]], [[User:MarkTraceur|Mark Holmquist]], [[user:NeilK|Neil Kandalgaonkar]], [[mw:User:Keegan_(WMF)|Keegan Peterzell]], [[meta:User:Tgr|Gergő Tisza]] | previous = | next = | projectpage = UploadWizard | display = {{{display|}}} }}</includeonly> Der '''UploadWizard''' ist ein schrittweiser JavaScript-Assistent zum Hochladen von Multimediadateien auf eine MediaWiki-Website. Es ist als {{ll|Extension:UploadWizard}} erhältlich. {{TOC|align=right|limit=2}} == Gründe == <div lang="en" dir="ltr" class="mw-content-ltr"> The Upload Wizard aims to make it easier to contribute multimedia works to Wikimedia projects. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This tool is now widely used to upload images on Wikimedia Commons, the free media repository associated with Wikipedia; any media file shared on that site can be used in any Wikipedia page in any language.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Commons is curated by a multilingual community and recently reached 21 million files.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> More details about the origins of this project can be found in the [[Special:MyLanguage/UploadWizard/Archive|Upload Wizard archive page]]; the main feedback page is located at [[commons:Commons:Upload Wizard feedback|Commons:Upload Wizard feedback]]. </div> == Ziele == <div lang="en" dir="ltr" class="mw-content-ltr"> Here are some of our goals for Upload Wizard: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">'''engage more users''' to contribute media</span> * <span lang="en" dir="ltr" class="mw-content-ltr">provide a '''smoother experience''' for all</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''add more media''' content on our sites</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''fix critical bugs''', to make things work better</span> <span lang="en" dir="ltr" class="mw-content-ltr">In coming months, we propose to:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''Plan & discuss''' improvements</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Solve '''bugs & technical debt'''</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Improve the '''user experience'''</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Incremental '''code refactoring'''</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Develop new '''modal tool''' for other uses</span> == Zeitplan == <div lang="en" dir="ltr" class="mw-content-ltr"> This is an estimated timeline based on our current work, as of January 2015. </div> ; <span lang="en" dir="ltr" class="mw-content-ltr">Q3 (Jan-Mar 2015)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Implement and deploy JS error logging to automatically capture errors affecting users</span> ; Q4 (Apr.-Juni 2015) * <span lang="en" dir="ltr" class="mw-content-ltr">Identify the main sources of the [http://multimedia-metrics.wmflabs.org/dashboards/uw# current drop-off] happening on the file step</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Significantly reduce the drop-off</span> == Benutzer == Zu unseren Hauptbenutzern für den Hochladeassistenten gehören: * neue Beitragende * erfahrende Beitragende <span lang="en" dir="ltr" class="mw-content-ltr">We will aim to support both user groups evenly, with an initial focus on Commons users - then contributors on Wikipedia and other sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that you must be registered and logged-in to use Upload Wizard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also aim to serve these secondary users:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">editors</span> * <span lang="en" dir="ltr" class="mw-content-ltr">campaign organizers</span> * Entwickler == Metriken == [[File:Upload Wizard Slides.pdf|thumb|400px|page=36]] [[File:Upload Wizard Slides.pdf|thumb|400px|page=37]] === Erste Metriken === Here are upload metrics for Upload Wizard from February 2014: (1) * 18k uploaders / month * 292k uploads / month It's worth noting that Upload Wizard represents: * 80% of all uploaders (14k per month, a lot more during Wiki Loves Monuments) * 56% of all uploads (141k per month, the rest are handled by bots and other uploads tools) For more info, click on the metrics graph thumbnails to the right. (1) Data from Wikimedia Commons in Feb 2014. Source: Wikimedia Foundation === Weitere Metriken === <div lang="en" dir="ltr" class="mw-content-ltr"> Here are key metrics we're considering to track the upload process: </div> * number of uploaders * number of uploads * upload drop-off rate * number of uploaded files used * number of uploaded files viewed We are starting development to collect more metrics data, and are tracking this work in these tickets: * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/541 Funnel Metrics for Upload Wizard (#541)] (in development for this sprint)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/609 Upload Wizard funnel metrics - basics (#609)] (done, but only 4 data points for now)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/305 Upload Wizard Metrics - Data collection 1: Major steps (#305)] (to be developed in coming weeks)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/603 Upload Wizard Metrics - Data Collection 2: Detailed Steps (#603)] (to be developed in coming weeks)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/587 Upload Wizard Metrics - Dashboards (#587)] (to be developed in coming weeks)</span> == Feedback == We are now reviewing hundreds of [[commons:Commons:Upload_Wizard_feedback|feedback posts]] and [[commons:Commons:Upload_help|help questions]] about Upload Wizard last year, which have been analyzed in [https://docs.google.com/a/wikimedia.org/spreadsheets/d/1AUKUODbKVQMtFgTbCm8l3Pee7l7xbpxf9idx_3PsCXE/edit#gid=0 this spreadsheet]. <div lang="en" dir="ltr" class="mw-content-ltr"> Here are some of the key issues reported: </div> * upload hangs * upload takes too long * issues with multiple files * confused by license forms * unclear prompts and error messages * problems with categories (e.g. can't search them) * issues with large files that don't load well * would like a progress bar during upload * want to add info while image loads * would like simple explanations * want other info templates == Benutzerfreundlichkeit == <div lang="en" dir="ltr" class="mw-content-ltr"> We have done a number of usability studies for Upload Wizard and plan to do more. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here are videos of some initial testing sessions: </div> * [https://www.usertesting.com/videos/AI1Psz9uNro?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T1] * [https://www.usertesting.com/videos/eM8j0rwubH0?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T2] * [https://www.usertesting.com/videos/pE4nRhgRmS0?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T3] * [https://www.usertesting.com/videos/katNyUV7qtw?back=%2Fdashboard%2Fstudies%3Fpage%3D3%23study_21394 T4] We will consolidate these results when we run more user tests. For now, here are some [http://etherpad.wikimedia.org/p/design-multimedia-uploader preliminary observations and analysis of the current design] by our designer Pau Giner. <div lang="en" dir="ltr" class="mw-content-ltr"> == Current Workflow == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here are the main steps of the current workflow for Upload Wizard: </div> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Start</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Click on the Upload link</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Learn</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Reading the help infographic, click 'Continue'</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Select media files to upload, add more files if needed</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Rights</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Fill in author, source and license information</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Describe</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">Fill in title, description, date or other info</span> * '''<span lang="en" dir="ltr" class="mw-content-ltr">Use</span>''' - <span lang="en" dir="ltr" class="mw-content-ltr">copy code to add images to articles or share them with others</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To see how Upload Wizard currently works, [[commons:Special:UploadWizard|visit this page]] (must be logged in). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == New designs == </div> <span lang="en" dir="ltr" class="mw-content-ltr">Based on current feedback and usability tests, our designer Pau Giner has prepared some preliminary design ideas to help define our vision for Upload Wizard (see [[:File:Upload Wizard Slides.pdf|slides]] below).</span> <span lang="en" dir="ltr" class="mw-content-ltr">These are explorations and reflections about a more modern upload experience, but don't necessarily reflect what will be built, as more community consultation would be required.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Mockups==== </div> <gallery mode="nolines" perrow="3" widths="320px" heights="240px"> File:Upload Wizard Slides.pdf|page=11| File:Upload Wizard Slides.pdf|page=12| File:Upload Wizard Slides.pdf|page=13| File:Upload Wizard Slides.pdf|page=14| File:Upload Wizard Slides.pdf|page=15| File:Upload Wizard Slides.pdf|page=16| File:Upload Wizard Slides.pdf|page=17| File:Upload Wizard Slides.pdf|page=18| File:Upload Wizard Slides.pdf|page=19| File:Upload Wizard Slides.pdf|page=20| File:Upload Wizard Slides.pdf|page=21| File:Upload Wizard Slides.pdf|page=22| File:Upload Wizard Slides.pdf|page=23| File:Upload Wizard Slides.pdf|page=24| File:Upload Wizard Slides.pdf|page=25| </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> These mockups will be adjusted based on community feedback. </div> <span lang="en" dir="ltr" class="mw-content-ltr">These designs can be viewed together in [[:File:Upload Wizard Slides.pdf|these vision slides]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual screenshots will be added to this page soon.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Scenarios=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These first designs are based on these user scenarios: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Upload images to a page</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Upload a single image on a topic</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Upload multiple files on different topics</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Issues=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> They attempt to address these key issues: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Adding a picture to a page is disconnected</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Providing metadata is a big upfront effort</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Categorization is painful</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Multiple file upload</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Lack of aids for input</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Meaningless untranslatable titles</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Initial infographic is too verbose</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Help needed to understand licenses</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Upload button on Commons homepage is hard to find</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To learn more, check out [http://etherpad.wikimedia.org/p/design-multimedia-uploader these design notes] by our designer Pau Giner. </div> == Fehler == <div lang="en" dir="ltr" class="mw-content-ltr"> We keep track of Upload Wizard bugs [[phab:tag/mediawiki-extensions-uploadwizard/|in the bug tracker]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Over the years, many bugs have accumulated for this project, because Wikimedia Foundation did not have a dedicated team to address them.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Now that the multimedia team has taken ownership of Upload Wizard, we will work diligently to fix the most important bugs first, then gradually resolve the rest of the relevant issues over time.</span> Danke für deine Geduld und dein Verständnis :) <span lang="en" dir="ltr" class="mw-content-ltr">If you find any technical bugs, please [https://phabricator.wikimedia.org/maniphest/task/create/?projects=MediaWiki-extensions-UploadWizard report them].</span> {{anchor|Compatibility}} == Kompatibilität == <div lang="en" dir="ltr" class="mw-content-ltr"> To be able to run UploadWizard, the user's browser must: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have [[w:JavaScript|JavaScript]] enabled</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Support [[w:ECMAScript#5th Edition|ECMAScript 5]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Support [[w:HTML5 File API|HTML5 File API]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Support [[w:MIME#Form-Data|form-data]] in [[w:XMLHttpRequest|XMLHttpRequest]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Otherwise, the standard MediaWiki file upload form is displayed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Supported browsers include Firefox 13+, Chrome 21+, Internet Explorer 10+, Safari 7+ and Opera 12+. </div> == Aufgaben == [[phab:tag/mediawiki-extensions-uploadwizard/|https://phabricator.wikimedia.org/tag/mediawiki-extensions-uploadwizard/]] == Weitere Werkzeuge == <div lang="en" dir="ltr" class="mw-content-ltr"> Besides Upload Wizard, other upload tools are available to users, which are tracked at [[commons:Special:MyLanguage/Commons:Upload tools|commons:Commons:Upload tools]]. </div> [[Category:Multimedia{{#translation:}}]] tkkargjw2ry8b88h50oaagg1v8xxohj Translations:Groups/4/ja 1198 1119778 5387369 4024798 2022-07-28T22:11:54Z Shirayuki 472859 update wikitext text/x-wiki MediaWiki グループには[[$1|それぞれの特性]]や技術その他の習熟度に関わらず、どなたでもご参加いただけます。 270qsh15otma8h2klv13bahajrn5in1 Translations:Groups/25/ja 1198 1119818 5387405 3857165 2022-07-28T22:15:10Z Shirayuki 472859 update wikitext text/x-wiki さらに英語以外の話者グループを対象とした活動を行う: * 説明文書とソフトウェアについて、$1 の手順に従った翻訳を実施。 4b5bhoceh1ea28ilw3vpqi57655pij2 Translations:Template:Empty section/2/en 1198 1120865 5387894 3859823 2022-07-29T10:40:30Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki You can help MediaWiki.org by expanding it. 83jm6piy7srm0peqbhm9llhzoyx6shh Template:Empty section/en 10 1120867 5387895 3859828 2022-07-29T10:40:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = {{notice|1=This section is empty. You can help MediaWiki.org by expanding it.}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> dl4mpwxcukfzbapqda8mduwsvjif1ub Template:Empty section/ja 10 1120869 5387900 3859832 2022-07-29T10:40:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = {{notice|1=この節は空です。 <span class="mw-translate-fuzzy">コンテンツを追加することで MediaWiki.org を支援してください。</span>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> c93j600q7hiwysbg8zafr3tlakhvoyv Template:Empty section/hu 10 1125204 5387899 3870680 2022-07-29T10:40:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = {{notice|1=Ez a szakasz üres. <span class="mw-translate-fuzzy">Te is segíthetsz bővíteni!</span>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> oplva7d3z69s5k90ngmfmvk13ogn7iq HHVM/tr 0 1128673 5387456 5240450 2022-07-28T22:32:11Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = MediaWiki için HHVM (HipHop Sanal Makinesi) desteği ve Wikimedia kümesine dağıtım | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span class="mw-translate-fuzzy">Daha kısa bir açıklama için [[Special:MyLanguage/HHVM/About|HHVM/Hakkında]] ve Aralık 2014 blog gönderisini HHVM, '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ Vikipedi'yi iki kat daha hızlı düzenlemeyi nasıl yaptığı]"''', faydaları ve dağıtım çalışmalarına bir bakış.</span> {{note|1=Eylül 2017'de Facebook, HHVM'nin gelecekte PHP uyumluluğu hedeflemeyeceğini duyurdu.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "HHVM'nin geleceği"]</ref> Tartışma sonrası<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM ve Zend uyuşmazlığı"] - ''wikitech-l''</ref> WMF, WMF üretim kümesini PHP 7'ye geçirmek için bir plan kabul etti. HHVM desteği MediaWiki'den düşürüldü. {{phabricator|T176209}} ve {{phabricator|T192166}} sayfalarına bakın.}} '''[[:tr:HHVM|HHVM]]''', 2014 yılında Wikimedia sunucularında dağıtılan bir PHP yorumlama aracıdır (somut olarak PHP bayt kodunu çalışma zamanında yerel talimatlarla derleyen sanal bir makinedir) ve yükleme süresini azaltır: oturum açtığınızda görüntülediğiniz tüm sayfaları ve oturum açmış olsanız da olmasanız da düzenlediğiniz sayfaları kaydetmek için. == Yol haritası == <span class="mw-translate-fuzzy">HHVM web sitelerinin [[Special:MyLanguage/Manual:What is MediaWiki|MediaWiki]] ([[:tr:PHP|PHP]] ile yazılmış) çalıştırması için yeni bir yoldur.</span> Bazen tam adı HipHop Sanal Makinesi ile bilinir ve tam zamanında bir derleyiciye (JIT) sahiptir. HHVM, oturum açmış kullanıcılar için sayfa görüntülemeyi hızlandırmalı ve ayrıca düzenlenmiş sayfaların tüm kullanıcılar için kaydedilmesini hızlandırmalıdır. Bu sayfa MediaWiki'de WikHop destekli HipHop desteği ve Wikimedia üretim vikilerine konuşlandırılmasıyla ilgili. Tarihsel olarak, HipHop derleyicisi Facebook tarafından dili hızlandırmak amacıyla PHP kodunu C++ derlemeyi içeren bir projeydi. Facebook o zamandan beri bu projeyi terk etti ve şimdi geliştirme çabaları bunun yerine HHVM'nin kendisine odaklanıyor. İşte 2014 yılında HHVM'yi üretim kümesine dağıtmanın genel planı: * Beta Kümesine dağıtım (şu anda devam eden çalışma, diğer çalışmalara paralel olarak) {{done}} * 21 Temmuz Haftası: üretimde birkaç işçiye dağıtım {{done}} * test.wikipedia.org uygulama sunucusuna konuşlandırma {{done}} * Uygulama sunucularının bir kısmına kısmi dağıtım sağlayan Varnish modülünü konuşlandırın {{Done}} * Az sayıda uygulama sunucusuna sınırlı dağıtım {{Done}} * Çoğu sunucu HHVM kullanana kadar dağıtımı daha fazla uygulama sunucusuna hızlandırın {{done}} * Hizmetlerin geri kalanına dağıtım {{done}} === HHVM çalışması === Phabricator: [[phabricator:project/board/79/|Açık görevler]], [[phabricator:project/board/79/query/all/|Tüm görevler]]. == Gerekçe == <span class="mw-translate-fuzzy">Yanıt süresindeki küçük gecikmelerin (örneğin saniyenin yarısının) bile web kullanıcısının tutulmasında keskin düşüşlere neden olabileceği iyi çalışılmış bir olgudur.<ref>[$radar "Bing ve Google Agree: Yavaş Sayfalar Kullanıcı Kaybediyor"] - Brady Forrest - ''O'Reilly Radar''</ref><ref>[$glinden Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer, Google'ın yanıt süresinde 0,4 saniyeden 0,9 saniyeye bir değişikliğin gelir ve trafikte% 20'lik bir düşüşe neden olduğunu belirtti.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> Sonuç olarak, Google ve Facebook gibi popüler web siteleri, site performans girişimlerine büyük ölçüde yatırım yapar ve sonuç olarak kısmen popüler kalır. <span class="mw-translate-fuzzy">Eskiden popüler siteler (Friendster gibi) bu konulara dikkat edilmemesinden dolayı acı çekti.<ref>"[$nytimes Wallflower at the Web Party]", New York Times, 15 Ekim 2006. Alıntı: "Kent Lindstrom, şimdi Friendster başkanı, kurulun şirketin bunalmış Web sitesinin yavaşlamasına neden olan teknik sorunları ele almadığını söyledi."</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> Vikipedi ve kardeş projeleri, hareketin misyonunu sürdürmesi için kullanılabilir ve duyarlı kalmalıdır. Facebook, büyük bir PHP kullanıcısı olarak bu sorunu fark etti ve bir çözüme büyük miktarda <ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> yatırım yaptı: [http://hhvm.com HHVM], PHP bayt kodunu çalışma zamanında yerel talimatlara derleyen sanal bir makine, Java ve C# tarafından hız avantajlarını elde etmek için kullanılan strateji. Bunun sitelerimizde de büyük performans iyileştirmeleri sağlayacağından eminiz. == HipHop son kullanıcılarımız için ne yapıyor? == MediaWiki, çalışma zamanında [[w:Interpreter (computing)|yorumlanmış]] bir dil olan PHP'de yazılmıştır. Birisi bir sayfayı her görüntülediğinde bu PHP kodunu çalıştırmanın yükü, bu PHP'yi çalıştırarak oluşturulan HTML'yi önbelleğe alan [[w:Varnish (software)|Varnish]] gibi bir yazılım çalıştıran önbellek sunucularının kullanımını gerektirir. <span class="mw-translate-fuzzy">Bir sayfanın her görüntülendiğinde PHP'nin çalışması gerekmez. Bu önbellekler yalnızca oturum açmamış kullanıcılara sunulur.<ref>Tanımı gereği, oturum açmış olan kullanıcılara statik önbellekten sayfalar sunulamaz; çünkü kendilerine sunulan sayfa, sayfanın sağ üst kısmında kullanıcı adı gibi kullanıcıya özgü HTML içermelidir. Bu, maalesef, oturum açmanın sitelerimizin sizin için ne kadar iyi performans gösterdiği konusunda somut bir azalmaya neden olduğu bir durum yaratır.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> Önbellekten etkilenmeyen ve bu nedenle PHP kodunun çalışma süresinden etkilenen eylemler şunları içerir: * Giriş yaparken görüntülediğiniz tüm sayfalar. * Giriş yapmış olsanız da olmasanız da düzenlediğiniz sayfaları kaydetme. Bu nedenle, MediaWiki'nin PHP kodu için harcanan süreyi azaltmak için yapabileceğimiz herhangi bir işlem, sitemizin oturum açma sürelerini, oturum açmış tüm kullanıcılarımız ve anonim olarak düzenleyen herkes için de azaltacaktır. HipHop, mevcut yorumcumuzdan daha hızlı, daha verimli bir PHP tercümanı olarak yazılmıştır ([[:en:Zend Engine|Zend]]). Umudumuz, HipHop'u Zend'in yerine uygulayarak, kullanıcılarımızın sitelerimizin performansında somut bir artış fark edeceğini umuyoruz. == HipHop ile ilgili geliştirme çalışmalarımız MediaWiki geliştiricilerini nasıl etkiliyor? == İlk çalışma alanımızda, Mart 2014'ün sonunda bitirilmesi nedeniyle, herkesin Zend yerine Beta Kümesi'nde HipHop kullanmayı seçebilmesini umuyoruz. Bu, herhangi bir zamanda devre dışı bırakılabilecek tamamen katılım esasına göre olacaktır. Bu, MediaWiki Core ekibinin sadece teorik performans artışlarını tahmin etmek yerine, mevcut test altyapımızı kullanarak Hipend'in performansını Zend'in performansına göre ölçmesini sağlayacaktır. Ayrıca, HipHop'u MediaWiki ile uyumlu hale getirmek için ne kadar çalışma gerektiğini görmemize yardımcı olacak bir geliştirme ortamı yaratacak ve bu nedenle HipHop'un tam bir yedek olarak üretime geçmesinin ne kadar süreceğini tahmin edelim. Diğer MediaWiki geliştiricileri için, HipHop'un bu şekilde konuşlandırılmasının sonucu, Beta Kümesini bir test ortamı olarak kullanıyorlarsa, yamalarının isterse Zend yerine HipHop kullanarak nasıl performans gösterdiğini test etmeyi önemsiz bulacaklarıdır. Ancak, çalışmamızın aksamasını en aza indirmek için, altyapının tercih edilen doğası, geliştiricilerin, istedikleri takdirde gelecekteki HipHop göçünden tamamen agnostik geliştirmeye devam edebilmelerini sağlayacaktır. == Ayrıca bakınız == * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} içinde HHVM kurulumu * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori, @Scale'de HHVM'ye geçiş hakkında sunum] * [https://www.youtube.com/watch?v=IKvILMSNNpk Üretimde HHVM: Wikimedia geliştiricileri anlamı] == Kaynakça ve dipnotlar == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] 9v05scac3lk4d1w6g8l8mnqvva8vjfd 5387459 5387456 2022-07-28T22:32:20Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = MediaWiki için HHVM (HipHop Sanal Makinesi) desteği ve Wikimedia kümesine dağıtım | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :Daha kısa bir açıklama için [[Special:MyLanguage/HHVM/About|HHVM/Hakkında]] ve Aralık 2014 blog gönderisini HHVM, '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ Vikipedi'yi iki kat daha hızlı düzenlemeyi nasıl yaptığı]"''', faydaları ve dağıtım çalışmalarına bir bakış. {{note|1=Eylül 2017'de Facebook, HHVM'nin gelecekte PHP uyumluluğu hedeflemeyeceğini duyurdu.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "HHVM'nin geleceği"]</ref> Tartışma sonrası<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM ve Zend uyuşmazlığı"] - ''wikitech-l''</ref> WMF, WMF üretim kümesini PHP 7'ye geçirmek için bir plan kabul etti. HHVM desteği MediaWiki'den düşürüldü. {{phabricator|T176209}} ve {{phabricator|T192166}} sayfalarına bakın.}} '''[[:tr:HHVM|HHVM]]''', 2014 yılında Wikimedia sunucularında dağıtılan bir PHP yorumlama aracıdır (somut olarak PHP bayt kodunu çalışma zamanında yerel talimatlarla derleyen sanal bir makinedir) ve yükleme süresini azaltır: oturum açtığınızda görüntülediğiniz tüm sayfaları ve oturum açmış olsanız da olmasanız da düzenlediğiniz sayfaları kaydetmek için. == Yol haritası == <span class="mw-translate-fuzzy">HHVM web sitelerinin [[Special:MyLanguage/Manual:What is MediaWiki|MediaWiki]] ([[:tr:PHP|PHP]] ile yazılmış) çalıştırması için yeni bir yoldur.</span> Bazen tam adı HipHop Sanal Makinesi ile bilinir ve tam zamanında bir derleyiciye (JIT) sahiptir. HHVM, oturum açmış kullanıcılar için sayfa görüntülemeyi hızlandırmalı ve ayrıca düzenlenmiş sayfaların tüm kullanıcılar için kaydedilmesini hızlandırmalıdır. Bu sayfa MediaWiki'de WikHop destekli HipHop desteği ve Wikimedia üretim vikilerine konuşlandırılmasıyla ilgili. Tarihsel olarak, HipHop derleyicisi Facebook tarafından dili hızlandırmak amacıyla PHP kodunu C++ derlemeyi içeren bir projeydi. Facebook o zamandan beri bu projeyi terk etti ve şimdi geliştirme çabaları bunun yerine HHVM'nin kendisine odaklanıyor. İşte 2014 yılında HHVM'yi üretim kümesine dağıtmanın genel planı: * Beta Kümesine dağıtım (şu anda devam eden çalışma, diğer çalışmalara paralel olarak) {{done}} * 21 Temmuz Haftası: üretimde birkaç işçiye dağıtım {{done}} * test.wikipedia.org uygulama sunucusuna konuşlandırma {{done}} * Uygulama sunucularının bir kısmına kısmi dağıtım sağlayan Varnish modülünü konuşlandırın {{Done}} * Az sayıda uygulama sunucusuna sınırlı dağıtım {{Done}} * Çoğu sunucu HHVM kullanana kadar dağıtımı daha fazla uygulama sunucusuna hızlandırın {{done}} * Hizmetlerin geri kalanına dağıtım {{done}} === HHVM çalışması === Phabricator: [[phabricator:project/board/79/|Açık görevler]], [[phabricator:project/board/79/query/all/|Tüm görevler]]. == Gerekçe == <span class="mw-translate-fuzzy">Yanıt süresindeki küçük gecikmelerin (örneğin saniyenin yarısının) bile web kullanıcısının tutulmasında keskin düşüşlere neden olabileceği iyi çalışılmış bir olgudur.<ref>[$radar "Bing ve Google Agree: Yavaş Sayfalar Kullanıcı Kaybediyor"] - Brady Forrest - ''O'Reilly Radar''</ref><ref>[$glinden Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer, Google'ın yanıt süresinde 0,4 saniyeden 0,9 saniyeye bir değişikliğin gelir ve trafikte% 20'lik bir düşüşe neden olduğunu belirtti.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> Sonuç olarak, Google ve Facebook gibi popüler web siteleri, site performans girişimlerine büyük ölçüde yatırım yapar ve sonuç olarak kısmen popüler kalır. <span class="mw-translate-fuzzy">Eskiden popüler siteler (Friendster gibi) bu konulara dikkat edilmemesinden dolayı acı çekti.<ref>"[$nytimes Wallflower at the Web Party]", New York Times, 15 Ekim 2006. Alıntı: "Kent Lindstrom, şimdi Friendster başkanı, kurulun şirketin bunalmış Web sitesinin yavaşlamasına neden olan teknik sorunları ele almadığını söyledi."</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> Vikipedi ve kardeş projeleri, hareketin misyonunu sürdürmesi için kullanılabilir ve duyarlı kalmalıdır. Facebook, büyük bir PHP kullanıcısı olarak bu sorunu fark etti ve bir çözüme büyük miktarda <ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> yatırım yaptı: [http://hhvm.com HHVM], PHP bayt kodunu çalışma zamanında yerel talimatlara derleyen sanal bir makine, Java ve C# tarafından hız avantajlarını elde etmek için kullanılan strateji. Bunun sitelerimizde de büyük performans iyileştirmeleri sağlayacağından eminiz. == HipHop son kullanıcılarımız için ne yapıyor? == MediaWiki, çalışma zamanında [[w:Interpreter (computing)|yorumlanmış]] bir dil olan PHP'de yazılmıştır. Birisi bir sayfayı her görüntülediğinde bu PHP kodunu çalıştırmanın yükü, bu PHP'yi çalıştırarak oluşturulan HTML'yi önbelleğe alan [[w:Varnish (software)|Varnish]] gibi bir yazılım çalıştıran önbellek sunucularının kullanımını gerektirir. <span class="mw-translate-fuzzy">Bir sayfanın her görüntülendiğinde PHP'nin çalışması gerekmez. Bu önbellekler yalnızca oturum açmamış kullanıcılara sunulur.<ref>Tanımı gereği, oturum açmış olan kullanıcılara statik önbellekten sayfalar sunulamaz; çünkü kendilerine sunulan sayfa, sayfanın sağ üst kısmında kullanıcı adı gibi kullanıcıya özgü HTML içermelidir. Bu, maalesef, oturum açmanın sitelerimizin sizin için ne kadar iyi performans gösterdiği konusunda somut bir azalmaya neden olduğu bir durum yaratır.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> Önbellekten etkilenmeyen ve bu nedenle PHP kodunun çalışma süresinden etkilenen eylemler şunları içerir: * Giriş yaparken görüntülediğiniz tüm sayfalar. * Giriş yapmış olsanız da olmasanız da düzenlediğiniz sayfaları kaydetme. Bu nedenle, MediaWiki'nin PHP kodu için harcanan süreyi azaltmak için yapabileceğimiz herhangi bir işlem, sitemizin oturum açma sürelerini, oturum açmış tüm kullanıcılarımız ve anonim olarak düzenleyen herkes için de azaltacaktır. HipHop, mevcut yorumcumuzdan daha hızlı, daha verimli bir PHP tercümanı olarak yazılmıştır ([[:en:Zend Engine|Zend]]). Umudumuz, HipHop'u Zend'in yerine uygulayarak, kullanıcılarımızın sitelerimizin performansında somut bir artış fark edeceğini umuyoruz. == HipHop ile ilgili geliştirme çalışmalarımız MediaWiki geliştiricilerini nasıl etkiliyor? == İlk çalışma alanımızda, Mart 2014'ün sonunda bitirilmesi nedeniyle, herkesin Zend yerine Beta Kümesi'nde HipHop kullanmayı seçebilmesini umuyoruz. Bu, herhangi bir zamanda devre dışı bırakılabilecek tamamen katılım esasına göre olacaktır. Bu, MediaWiki Core ekibinin sadece teorik performans artışlarını tahmin etmek yerine, mevcut test altyapımızı kullanarak Hipend'in performansını Zend'in performansına göre ölçmesini sağlayacaktır. Ayrıca, HipHop'u MediaWiki ile uyumlu hale getirmek için ne kadar çalışma gerektiğini görmemize yardımcı olacak bir geliştirme ortamı yaratacak ve bu nedenle HipHop'un tam bir yedek olarak üretime geçmesinin ne kadar süreceğini tahmin edelim. Diğer MediaWiki geliştiricileri için, HipHop'un bu şekilde konuşlandırılmasının sonucu, Beta Kümesini bir test ortamı olarak kullanıyorlarsa, yamalarının isterse Zend yerine HipHop kullanarak nasıl performans gösterdiğini test etmeyi önemsiz bulacaklarıdır. Ancak, çalışmamızın aksamasını en aza indirmek için, altyapının tercih edilen doğası, geliştiricilerin, istedikleri takdirde gelecekteki HipHop göçünden tamamen agnostik geliştirmeye devam edebilmelerini sağlayacaktır. == Ayrıca bakınız == * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} içinde HHVM kurulumu * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori, @Scale'de HHVM'ye geçiş hakkında sunum] * [https://www.youtube.com/watch?v=IKvILMSNNpk Üretimde HHVM: Wikimedia geliştiricileri anlamı] == Kaynakça ve dipnotlar == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] 46bw7vwa6fglfsfxvwoxhoam8974zv6 5387463 5387459 2022-07-28T22:33:48Z Shirayuki 472859 update wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = MediaWiki için HHVM (HipHop Sanal Makinesi) desteği ve Wikimedia kümesine dağıtım | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :Daha kısa bir açıklama için [[Special:MyLanguage/HHVM/About|HHVM/Hakkında]] ve Aralık 2014 blog gönderisini HHVM, '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ Vikipedi'yi iki kat daha hızlı düzenlemeyi nasıl yaptığı]"''', faydaları ve dağıtım çalışmalarına bir bakış. {{note|1=Eylül 2017'de Facebook, HHVM'nin gelecekte PHP uyumluluğu hedeflemeyeceğini duyurdu.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "HHVM'nin geleceği"]</ref> Tartışma sonrası<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM ve Zend uyuşmazlığı"] - ''wikitech-l''</ref> WMF, WMF üretim kümesini PHP 7'ye geçirmek için bir plan kabul etti. HHVM desteği MediaWiki'den düşürüldü. {{phabricator|T176209}} ve {{phabricator|T192166}} sayfalarına bakın.}} '''[[:tr:HHVM|HHVM]]''', 2014 yılında Wikimedia sunucularında dağıtılan bir PHP yorumlama aracıdır (somut olarak PHP bayt kodunu çalışma zamanında yerel talimatlarla derleyen sanal bir makinedir) ve yükleme süresini azaltır: oturum açtığınızda görüntülediğiniz tüm sayfaları ve oturum açmış olsanız da olmasanız da düzenlediğiniz sayfaları kaydetmek için. == Yol haritası == HHVM web sitelerinin [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] ([[:tr:PHP|PHP]] ile yazılmış) çalıştırması için yeni bir yoldur. Bazen tam adı HipHop Sanal Makinesi ile bilinir ve tam zamanında bir derleyiciye (JIT) sahiptir. HHVM, oturum açmış kullanıcılar için sayfa görüntülemeyi hızlandırmalı ve ayrıca düzenlenmiş sayfaların tüm kullanıcılar için kaydedilmesini hızlandırmalıdır. Bu sayfa MediaWiki'de WikHop destekli HipHop desteği ve Wikimedia üretim vikilerine konuşlandırılmasıyla ilgili. Tarihsel olarak, HipHop derleyicisi Facebook tarafından dili hızlandırmak amacıyla PHP kodunu C++ derlemeyi içeren bir projeydi. Facebook o zamandan beri bu projeyi terk etti ve şimdi geliştirme çabaları bunun yerine HHVM'nin kendisine odaklanıyor. İşte 2014 yılında HHVM'yi üretim kümesine dağıtmanın genel planı: * Beta Kümesine dağıtım (şu anda devam eden çalışma, diğer çalışmalara paralel olarak) {{done}} * 21 Temmuz Haftası: üretimde birkaç işçiye dağıtım {{done}} * test.wikipedia.org uygulama sunucusuna konuşlandırma {{done}} * Uygulama sunucularının bir kısmına kısmi dağıtım sağlayan Varnish modülünü konuşlandırın {{Done}} * Az sayıda uygulama sunucusuna sınırlı dağıtım {{Done}} * Çoğu sunucu HHVM kullanana kadar dağıtımı daha fazla uygulama sunucusuna hızlandırın {{done}} * Hizmetlerin geri kalanına dağıtım {{done}} === HHVM çalışması === Phabricator: [[phabricator:project/board/79/|Açık görevler]], [[phabricator:project/board/79/query/all/|Tüm görevler]]. == Gerekçe == <span class="mw-translate-fuzzy">Yanıt süresindeki küçük gecikmelerin (örneğin saniyenin yarısının) bile web kullanıcısının tutulmasında keskin düşüşlere neden olabileceği iyi çalışılmış bir olgudur.<ref>[$radar "Bing ve Google Agree: Yavaş Sayfalar Kullanıcı Kaybediyor"] - Brady Forrest - ''O'Reilly Radar''</ref><ref>[$glinden Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer, Google'ın yanıt süresinde 0,4 saniyeden 0,9 saniyeye bir değişikliğin gelir ve trafikte% 20'lik bir düşüşe neden olduğunu belirtti.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> Sonuç olarak, Google ve Facebook gibi popüler web siteleri, site performans girişimlerine büyük ölçüde yatırım yapar ve sonuç olarak kısmen popüler kalır. <span class="mw-translate-fuzzy">Eskiden popüler siteler (Friendster gibi) bu konulara dikkat edilmemesinden dolayı acı çekti.<ref>"[$nytimes Wallflower at the Web Party]", New York Times, 15 Ekim 2006. Alıntı: "Kent Lindstrom, şimdi Friendster başkanı, kurulun şirketin bunalmış Web sitesinin yavaşlamasına neden olan teknik sorunları ele almadığını söyledi."</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> Vikipedi ve kardeş projeleri, hareketin misyonunu sürdürmesi için kullanılabilir ve duyarlı kalmalıdır. Facebook, büyük bir PHP kullanıcısı olarak bu sorunu fark etti ve bir çözüme büyük miktarda <ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> yatırım yaptı: [http://hhvm.com HHVM], PHP bayt kodunu çalışma zamanında yerel talimatlara derleyen sanal bir makine, Java ve C# tarafından hız avantajlarını elde etmek için kullanılan strateji. Bunun sitelerimizde de büyük performans iyileştirmeleri sağlayacağından eminiz. == HipHop son kullanıcılarımız için ne yapıyor? == MediaWiki, çalışma zamanında [[w:Interpreter (computing)|yorumlanmış]] bir dil olan PHP'de yazılmıştır. Birisi bir sayfayı her görüntülediğinde bu PHP kodunu çalıştırmanın yükü, bu PHP'yi çalıştırarak oluşturulan HTML'yi önbelleğe alan [[w:Varnish (software)|Varnish]] gibi bir yazılım çalıştıran önbellek sunucularının kullanımını gerektirir. <span class="mw-translate-fuzzy">Bir sayfanın her görüntülendiğinde PHP'nin çalışması gerekmez. Bu önbellekler yalnızca oturum açmamış kullanıcılara sunulur.<ref>Tanımı gereği, oturum açmış olan kullanıcılara statik önbellekten sayfalar sunulamaz; çünkü kendilerine sunulan sayfa, sayfanın sağ üst kısmında kullanıcı adı gibi kullanıcıya özgü HTML içermelidir. Bu, maalesef, oturum açmanın sitelerimizin sizin için ne kadar iyi performans gösterdiği konusunda somut bir azalmaya neden olduğu bir durum yaratır.</ref></span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> Önbellekten etkilenmeyen ve bu nedenle PHP kodunun çalışma süresinden etkilenen eylemler şunları içerir: * Giriş yaparken görüntülediğiniz tüm sayfalar. * Giriş yapmış olsanız da olmasanız da düzenlediğiniz sayfaları kaydetme. Bu nedenle, MediaWiki'nin PHP kodu için harcanan süreyi azaltmak için yapabileceğimiz herhangi bir işlem, sitemizin oturum açma sürelerini, oturum açmış tüm kullanıcılarımız ve anonim olarak düzenleyen herkes için de azaltacaktır. HipHop, mevcut yorumcumuzdan daha hızlı, daha verimli bir PHP tercümanı olarak yazılmıştır ([[:en:Zend Engine|Zend]]). Umudumuz, HipHop'u Zend'in yerine uygulayarak, kullanıcılarımızın sitelerimizin performansında somut bir artış fark edeceğini umuyoruz. == HipHop ile ilgili geliştirme çalışmalarımız MediaWiki geliştiricilerini nasıl etkiliyor? == İlk çalışma alanımızda, Mart 2014'ün sonunda bitirilmesi nedeniyle, herkesin Zend yerine Beta Kümesi'nde HipHop kullanmayı seçebilmesini umuyoruz. Bu, herhangi bir zamanda devre dışı bırakılabilecek tamamen katılım esasına göre olacaktır. Bu, MediaWiki Core ekibinin sadece teorik performans artışlarını tahmin etmek yerine, mevcut test altyapımızı kullanarak Hipend'in performansını Zend'in performansına göre ölçmesini sağlayacaktır. Ayrıca, HipHop'u MediaWiki ile uyumlu hale getirmek için ne kadar çalışma gerektiğini görmemize yardımcı olacak bir geliştirme ortamı yaratacak ve bu nedenle HipHop'un tam bir yedek olarak üretime geçmesinin ne kadar süreceğini tahmin edelim. Diğer MediaWiki geliştiricileri için, HipHop'un bu şekilde konuşlandırılmasının sonucu, Beta Kümesini bir test ortamı olarak kullanıyorlarsa, yamalarının isterse Zend yerine HipHop kullanarak nasıl performans gösterdiğini test etmeyi önemsiz bulacaklarıdır. Ancak, çalışmamızın aksamasını en aza indirmek için, altyapının tercih edilen doğası, geliştiricilerin, istedikleri takdirde gelecekteki HipHop göçünden tamamen agnostik geliştirmeye devam edebilmelerini sağlayacaktır. == Ayrıca bakınız == * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} içinde HHVM kurulumu * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori, @Scale'de HHVM'ye geçiş hakkında sunum] * [https://www.youtube.com/watch?v=IKvILMSNNpk Üretimde HHVM: Wikimedia geliştiricileri anlamı] == Kaynakça ve dipnotlar == <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] pr49opqeeolzn3097q2e20e393mkyef Translations:HHVM/28/tr 1198 1128675 5387458 3881240 2022-07-28T22:32:19Z Shirayuki 472859 update wikitext text/x-wiki Daha kısa bir açıklama için [[$1|HHVM/Hakkında]] ve Aralık 2014 blog gönderisini HHVM, '''"[$blog Vikipedi'yi iki kat daha hızlı düzenlemeyi nasıl yaptığı]"''', faydaları ve dağıtım çalışmalarına bir bakış. rpx7pdyo8cu3dotn4khyetjgg5b7n0x Translations:HHVM/5/tr 1198 1128682 5387462 4299821 2022-07-28T22:33:48Z Shirayuki 472859 update wikitext text/x-wiki HHVM web sitelerinin [[$1|MediaWiki]] ([[:tr:PHP|PHP]] ile yazılmış) çalıştırması için yeni bir yoldur. ay6prj2gjyycode1ie2v4beljxtoj3t Template:Empty section/fr 10 1132074 5387898 4186852 2022-07-29T10:40:32Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = {{notice|1=Cette section est vide. <span class="mw-translate-fuzzy">Vous pouvez aider MediaWiki.org en ajoutant du contenu.</span>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> 9qztatkrztf3d7rab3sz7m71m6ambsp New requirements for user signatures/pl 0 1134256 5386348 5325343 2022-07-28T13:22:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> Wiele wiki określa wymagania co do podpisów użytkowników. <span class="mw-translate-fuzzy">Zespół [[Editing team|Editing]] prosi o propozycje zakodowania niektórych tych wymagań do oprogramowania Wikipedii.</span> Umożliwi to łatwiejsze [[mw:Talk pages project/replying|odpowiadanie na poszczególne wypowiedzi na stronach dyskusji]] i korzystanie z niektórych innych narzędzi. Więcej szczegółów o tym, co zostało zaproponowane i dlaczego, znajduje się poniżej: * Jakich informacji zwrotnych oczekujemy: '''[[#Input: your feedback|Twoje zdanie]]''' * Dlaczego proponujemy zmiany: '''[[#Background: why this change?|Po co ta zmiana?]]''' * Jaka zmiana jest proponowana: '''[[#Proposal: signature validation requirements|Propozycja: wymagania co do określania poprawności podpisów]]''' * Jak te zmiany wpłyną na Ciebie: '''[[#Impact: effects of change|Wpływ: efekt zmian]]''' __TOC__ {{anchor|Input: your feedback}} == Twoje zdanie == Zespół nad tym pracujący oczekuje wypowiedzi na temat tej propozycji. Umieść odpowiedzi na poniższe pytania na [[Talk:New requirements for user signatures|'''stronie dyskusji''']]: # '''Czy omawiane tutaj nowe standardy podpisów użytkowników mogą powodować jakieś problemy na twojej wiki?''' # '''O czym nasz zespół powinien wiedzieć wprowadzając te zmiany?''' # '''Co powinno stać się z dotychczasowymi podpisami, które nie będą dopasowane do nowych wymagań?''' <em>Na przykład, czy powinny zostać zaniechane?</em> <em>Nie musisz ograniczać się wyłącznie do powyższych pytań. Nasz zespół chciałby usłyszeć każdą opinie, którą chciałbyś się podzielić.</em> {{anchor|Background: why this change?}} == Po co ta zmiana? == W roku 2019, wolontariusze z [[mw:Talk pages consultation 2019/Participant group sign-up|20 projektów Wikimedia i grup użytkowników]], wraz z pracownikami Wikimedia Foundation, uczestniczyli w [[mw:Talk_pages_consultation_2019|konsultacjach dotyczących stron dyskusji]]. Wysiłki miały na celu określenie lepszych narzędzi do komunikacji na wiki. Jednym z wniosków tej dyskusji było [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|zaproponowanie lepszego sposobu na umieszczanie odpowiedzi na poszczególne wypowiedzi]] na stronach dyskusji. Aby [[mw:Talk_pages_project/replying|ta funkcja]] działała poprawnie, oprogramowanie potrzebuje, aby podpisy były czytelne dla programów komputerowych, dzięki czemu może wykrywać poszczególne wypowiedzi i umożliwić odpowiadanie na nie. Problemem jest to, że mimo określenia zasad tworzenia podpisów na poszczególnych wiki, nie są one zakodowane w oprogramowaniu. Zwiększa to szanse, że ktoś zmieni swój podpis na taki, który złamie konwencję stosowaną na wiki i tym samym może utrudnić innym uczestnictwo w dyskusji. Uściślenie kwestii formatu podpisów pozwoli także na poprawienie dotychczasowych funkcji, na przykład [[mw:Help:Notifications/Types#Mentions|powiadomienia o wzmiance]], które działają tylko, jeżeli zostanie wykryte dodanie podpisu w edycji. {{anchor|Proposal: signature validation requirements}} == Propozycja: wymagania co do określania poprawności podpisów == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Jeżeli nie pojawią się przeszkody, ta zmiana powinna nastąpić w kwietniu 2020. Jeżeli będziemy chcieli dokonać bardziej znacznych zmian wywnioskowanych na podstawie waszych wypowiedzi, potrwa to dłużej. <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} === Odrzucanie nieprawidłowych znaczników HTML i innych błędów [[mw:Help:Extension:Linter|Linter]]a === {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> === Wymaganie linku do strony użytkownika, strony dyskusji lub wkładu === {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> === Odrzucanie zagnieżdżonej substutucji w podpisach === {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Wpływ: efekt zmian == === Co stanie się z dotychczasowymi podpisami? === Dotychczasowe podpisy, które będą niepoprawne w świetle nowych zasad, będą nadal dozwolone (''[[:en:Grandfather_clause|grandfathered in]]''). Podczas przeglądania ustawień, będzie widoczny komunikat ostrzegawczy. Podczas zmiany podpisu, nowy musi być już poprawny. Jeżeli jednak nie będzie on zmieniany, będzie nadal stosowany podczas podpisywania nowych wiadomości, a inne ustawienia będzie można nadal zmieniać. Oczekujemy na wypowiedź co do proponowanej zmiany. Jeżeli nieprawidłowe podpisy mają być odrzucane, przy podpisywaniu mają być wstawiane podpisy w domyślnej formie, dopóki użytkownik nie poprawi swojego dostosowanego podpisu. === Kiedy te zmiany nastąpią? === Komentarze prosimy umieszczać do 31 marca 2020. Zespół Editing podejmie decyzję na początku kwietnia. Rezultat zostanie umieszczony na stronie dyskusji. Jeżeli nie pojawią się przeszkody, ta zmiana powinna nastąpić w kwietniu 2020. Ta data może zostać przesunięta jeżeli zespół będzie musiał zaimplementować dodatkowe znaczne zmiany, jeżeli wynikną one z waszych wypowiedzi. === Jak dowiemy się o zmianach jakie mają nastąpić? === Umieścimy powiadomienie w [[m:Tech/News]], gdy ta zmiana będzie wdrażana. === Jak mogą wyglądać błędy sprawdzania poprawności podpisów? === Błędy HTML/lint zawierają linki do dokumentacji błędów lintera, na przykład [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], wraz z przyciskiem do podświetlania problematycznej części podpisu. Komunikaty o wymaganym linku będą podawać przykładowy wikikod do użycia. <gallery mode="packed" caption="Przykładowe komunikaty o błędach"> File:MediaWiki preferences - existing user signature invalid.png|Ostrzeżenie pokazywane gdy istniejący użytkownik ma nieprawidłowy podpis (błędy lintera). File:MediaWiki preferences - new user signature invalid 1.png|Błąd pokazywany, gdy nowy podpis użytkownika będzie nieprawidłowy (ma błąd lintera). File:MediaWiki preferences - new user signature invalid 2.png|Błąd pokazywany, gdy nowy podpis użytkownika będzie nieprawidłowy (nie będzie zawierał wymaganego linku) </gallery> == Wnioski == === Pierwotna propozycja === Propozycja została większościowo zaakceptowana. W odpowiedzi na sugestie wolontariuszy, wprowadzono kilka drobnych zmian i uściślono niektóre punkty. # Odrzucanie nieprawidłowych znaczników HTML i innych błędów [[mw:Help:Extension:Linter|Linter]]a #:Zakres tych zmian został ograniczony. [[Special:LintErrors/misnested-tag|Nieprawidłowo zagnieżdżone]] i [[Special:LintErrors/stripped-tag|niesparowane]] znaczniki HTML będą odrzucane. Niektóre błędy o niskim priorytecie będą wciąż przyjmowane. W szczególności nie będą odrzucane przestarzałe znaczniki HTML, takie jak {{tag|tt}} i {{tag|font}}. Ta decyzja nie przesądza jednak, że w przyszłości takie znaczniki będą usuwane albo i nie. # Wymaganie linku do strony użytkownika, strony dyskusji lub wkładu #:Zostanie wdrożone jak planowano. #:Dla jasności, musi znajdować się jeden lokalny link bezpośredni (nie przekierowanie, np. ze starej nazwy użytkownika) do jednej z tych stron. Czyli, podpis o treści <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> będzie akceptowany (jeden lokalny link i jeden link do innej wiki), ale podpisy zawierające <em>wyłącznie</em> linki do innych wiki lub <em>tylko</em> do przekierowań z poprzedniej nazwy użytkownika, będą nieprawidłowe. Jest to konieczne ze względów technicznych. # Odrzucanie zagnieżdżonej substutucji w podpisach #:Zostanie wdrożone jak planowano. Proces wdrażania tych zmian będzie przebiegał następująco: * {{done}} Ogłoszenie w [[m:Tech/News|Tech News]] po wdrożeniu nowych wymagań. * {{done}} Po wprowadzeniu zmiany w oprogramowaniu zainstalowanym na serwerach, użytkownicy nie będą mogli zapisywać w preferencjach nieprawidłowych podpisów. Dotychczas wprowadzone formaty podpisów będą pozostawione. * {{in progress}} Aktywni użytkownicy z niepoprawnymi podpisami będą zachęcani do ich zmiany. Ten proces może potrwać kilka miesięcy. * Ewentualnie, wszystkie podpisy będą musiały zostać dopasowane. Jeżeli użytkownicy nie poprawią swoich podpisów, ich podpisy nie będą działać, a w zamian będą stosowane domyślne. <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> === Propozycja z 2021 === <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == Uwagi == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] annfma73k3p50fajho69fzjq0nwtfjx 5386366 5386348 2022-07-28T13:24:30Z Shirayuki 472859 update wikitext text/x-wiki <languages/> Wiele wiki określa wymagania co do podpisów użytkowników. Zespół [[Special:MyLanguage/Editing team|Editing]] prosi o propozycje zakodowania niektórych tych wymagań do oprogramowania Wikipedii. Umożliwi to łatwiejsze [[mw:Talk pages project/replying|odpowiadanie na poszczególne wypowiedzi na stronach dyskusji]] i korzystanie z niektórych innych narzędzi. Więcej szczegółów o tym, co zostało zaproponowane i dlaczego, znajduje się poniżej: * Jakich informacji zwrotnych oczekujemy: '''[[#Input: your feedback|Twoje zdanie]]''' * Dlaczego proponujemy zmiany: '''[[#Background: why this change?|Po co ta zmiana?]]''' * Jaka zmiana jest proponowana: '''[[#Proposal: signature validation requirements|Propozycja: wymagania co do określania poprawności podpisów]]''' * Jak te zmiany wpłyną na Ciebie: '''[[#Impact: effects of change|Wpływ: efekt zmian]]''' __TOC__ {{anchor|Input: your feedback}} == Twoje zdanie == Zespół nad tym pracujący oczekuje wypowiedzi na temat tej propozycji. Umieść odpowiedzi na poniższe pytania na [[Talk:New requirements for user signatures|'''stronie dyskusji''']]: # '''Czy omawiane tutaj nowe standardy podpisów użytkowników mogą powodować jakieś problemy na twojej wiki?''' # '''O czym nasz zespół powinien wiedzieć wprowadzając te zmiany?''' # '''Co powinno stać się z dotychczasowymi podpisami, które nie będą dopasowane do nowych wymagań?''' <em>Na przykład, czy powinny zostać zaniechane?</em> <em>Nie musisz ograniczać się wyłącznie do powyższych pytań. Nasz zespół chciałby usłyszeć każdą opinie, którą chciałbyś się podzielić.</em> {{anchor|Background: why this change?}} == Po co ta zmiana? == W roku 2019, wolontariusze z [[mw:Talk pages consultation 2019/Participant group sign-up|20 projektów Wikimedia i grup użytkowników]], wraz z pracownikami Wikimedia Foundation, uczestniczyli w [[mw:Talk_pages_consultation_2019|konsultacjach dotyczących stron dyskusji]]. Wysiłki miały na celu określenie lepszych narzędzi do komunikacji na wiki. Jednym z wniosków tej dyskusji było [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|zaproponowanie lepszego sposobu na umieszczanie odpowiedzi na poszczególne wypowiedzi]] na stronach dyskusji. Aby [[mw:Talk_pages_project/replying|ta funkcja]] działała poprawnie, oprogramowanie potrzebuje, aby podpisy były czytelne dla programów komputerowych, dzięki czemu może wykrywać poszczególne wypowiedzi i umożliwić odpowiadanie na nie. Problemem jest to, że mimo określenia zasad tworzenia podpisów na poszczególnych wiki, nie są one zakodowane w oprogramowaniu. Zwiększa to szanse, że ktoś zmieni swój podpis na taki, który złamie konwencję stosowaną na wiki i tym samym może utrudnić innym uczestnictwo w dyskusji. Uściślenie kwestii formatu podpisów pozwoli także na poprawienie dotychczasowych funkcji, na przykład [[mw:Help:Notifications/Types#Mentions|powiadomienia o wzmiance]], które działają tylko, jeżeli zostanie wykryte dodanie podpisu w edycji. {{anchor|Proposal: signature validation requirements}} == Propozycja: wymagania co do określania poprawności podpisów == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Jeżeli nie pojawią się przeszkody, ta zmiana powinna nastąpić w kwietniu 2020. Jeżeli będziemy chcieli dokonać bardziej znacznych zmian wywnioskowanych na podstawie waszych wypowiedzi, potrwa to dłużej. <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} === Odrzucanie nieprawidłowych znaczników HTML i innych błędów [[mw:Help:Extension:Linter|Linter]]a === {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> === Wymaganie linku do strony użytkownika, strony dyskusji lub wkładu === {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> === Odrzucanie zagnieżdżonej substutucji w podpisach === {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Wpływ: efekt zmian == === Co stanie się z dotychczasowymi podpisami? === Dotychczasowe podpisy, które będą niepoprawne w świetle nowych zasad, będą nadal dozwolone (''[[:en:Grandfather_clause|grandfathered in]]''). Podczas przeglądania ustawień, będzie widoczny komunikat ostrzegawczy. Podczas zmiany podpisu, nowy musi być już poprawny. Jeżeli jednak nie będzie on zmieniany, będzie nadal stosowany podczas podpisywania nowych wiadomości, a inne ustawienia będzie można nadal zmieniać. Oczekujemy na wypowiedź co do proponowanej zmiany. Jeżeli nieprawidłowe podpisy mają być odrzucane, przy podpisywaniu mają być wstawiane podpisy w domyślnej formie, dopóki użytkownik nie poprawi swojego dostosowanego podpisu. === Kiedy te zmiany nastąpią? === Komentarze prosimy umieszczać do 31 marca 2020. Zespół Editing podejmie decyzję na początku kwietnia. Rezultat zostanie umieszczony na stronie dyskusji. Jeżeli nie pojawią się przeszkody, ta zmiana powinna nastąpić w kwietniu 2020. Ta data może zostać przesunięta jeżeli zespół będzie musiał zaimplementować dodatkowe znaczne zmiany, jeżeli wynikną one z waszych wypowiedzi. === Jak dowiemy się o zmianach jakie mają nastąpić? === Umieścimy powiadomienie w [[m:Tech/News]], gdy ta zmiana będzie wdrażana. === Jak mogą wyglądać błędy sprawdzania poprawności podpisów? === Błędy HTML/lint zawierają linki do dokumentacji błędów lintera, na przykład [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], wraz z przyciskiem do podświetlania problematycznej części podpisu. Komunikaty o wymaganym linku będą podawać przykładowy wikikod do użycia. <gallery mode="packed" caption="Przykładowe komunikaty o błędach"> File:MediaWiki preferences - existing user signature invalid.png|Ostrzeżenie pokazywane gdy istniejący użytkownik ma nieprawidłowy podpis (błędy lintera). File:MediaWiki preferences - new user signature invalid 1.png|Błąd pokazywany, gdy nowy podpis użytkownika będzie nieprawidłowy (ma błąd lintera). File:MediaWiki preferences - new user signature invalid 2.png|Błąd pokazywany, gdy nowy podpis użytkownika będzie nieprawidłowy (nie będzie zawierał wymaganego linku) </gallery> == Wnioski == === Pierwotna propozycja === Propozycja została większościowo zaakceptowana. W odpowiedzi na sugestie wolontariuszy, wprowadzono kilka drobnych zmian i uściślono niektóre punkty. # Odrzucanie nieprawidłowych znaczników HTML i innych błędów [[mw:Help:Extension:Linter|Linter]]a #:Zakres tych zmian został ograniczony. [[Special:LintErrors/misnested-tag|Nieprawidłowo zagnieżdżone]] i [[Special:LintErrors/stripped-tag|niesparowane]] znaczniki HTML będą odrzucane. Niektóre błędy o niskim priorytecie będą wciąż przyjmowane. W szczególności nie będą odrzucane przestarzałe znaczniki HTML, takie jak {{tag|tt}} i {{tag|font}}. Ta decyzja nie przesądza jednak, że w przyszłości takie znaczniki będą usuwane albo i nie. # Wymaganie linku do strony użytkownika, strony dyskusji lub wkładu #:Zostanie wdrożone jak planowano. #:Dla jasności, musi znajdować się jeden lokalny link bezpośredni (nie przekierowanie, np. ze starej nazwy użytkownika) do jednej z tych stron. Czyli, podpis o treści <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> będzie akceptowany (jeden lokalny link i jeden link do innej wiki), ale podpisy zawierające <em>wyłącznie</em> linki do innych wiki lub <em>tylko</em> do przekierowań z poprzedniej nazwy użytkownika, będą nieprawidłowe. Jest to konieczne ze względów technicznych. # Odrzucanie zagnieżdżonej substutucji w podpisach #:Zostanie wdrożone jak planowano. Proces wdrażania tych zmian będzie przebiegał następująco: * {{done}} Ogłoszenie w [[m:Tech/News|Tech News]] po wdrożeniu nowych wymagań. * {{done}} Po wprowadzeniu zmiany w oprogramowaniu zainstalowanym na serwerach, użytkownicy nie będą mogli zapisywać w preferencjach nieprawidłowych podpisów. Dotychczas wprowadzone formaty podpisów będą pozostawione. * {{in progress}} Aktywni użytkownicy z niepoprawnymi podpisami będą zachęcani do ich zmiany. Ten proces może potrwać kilka miesięcy. * Ewentualnie, wszystkie podpisy będą musiały zostać dopasowane. Jeżeli użytkownicy nie poprawią swoich podpisów, ich podpisy nie będą działać, a w zamian będą stosowane domyślne. <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> === Propozycja z 2021 === <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == Uwagi == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] q6y0s4vyvn1qffsae6mlpzdhmd70z24 Translations:Manual:Installation guide/11/ar 1198 1134969 5387294 4700828 2022-07-28T21:58:11Z Baris6161TURK 17188421 wikitext text/x-wiki يتطلب تصغير الصور برامج إضافية. كما أن $1 (أساسي لتشغيل المحرر المرئي) وخدمات أخرى لها متطلباتها الخاصة. sm2j5gvp1qs27izhgaxy42sgofuhyz1 Translations:New requirements for user signatures/2/pl 1198 1136244 5386365 3905863 2022-07-28T13:24:29Z Shirayuki 472859 update wikitext text/x-wiki Zespół [[$1|Editing]] prosi o propozycje zakodowania niektórych tych wymagań do oprogramowania Wikipedii. rdleu6oth655ecd0v189ipifa2meuw3 Template:Empty section/tr 10 1144007 5387901 3927573 2022-07-29T10:40:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = {{notice|1=Bu bölüm boştur. <span class="mw-translate-fuzzy">MediaWiki.org'a içerik ekleyerek yardımcı olabilirsiniz.</span>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> kzb981yat0vwckci8o918xowpmgjam2 Translations:Manual:Installation guide/11/id 1198 1144732 5387295 4700844 2022-07-28T21:58:22Z Baris6161TURK 17188421 wikitext text/x-wiki Pembuatan ''thumbnail'' gambar dan $texvc memerlukan program-program tambahan. $1 (dibutuhkan oleh VisualEditor) dan layanan-layanan lainnya memiliki persyaratan mereka masing-masing. ohh91f7rgwm2t68npuxnuy8ywkd6p8z New requirements for user signatures/vi 0 1149486 5386352 5325348 2022-07-28T13:22:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> Nhiều wiki có các quy tắc về các chữ ký thành viên tùy biến. <span class="mw-translate-fuzzy">[[Editing team|Nhóm phát triển sửa đổi]] đang cần bạn cho ý kiến về đề nghị chuyển một số quy tắc này sang mã nguồn trong phần mềm của Wikipedia.</span> Thay đổi này sẽ làm cho người ta có thể [[mw:Talk pages project/replying|trả lời các lời nhận xét riêng trong trang thảo luận]] một cách dễ dàng hơn và sử dụng một số công cụ khác. Bên dưới có thêm chi tiết về đề nghị và lý do: * Nhóm đang cần các thông tin phản hồi sau: '''[[#Input: your feedback|Phản hồi: Phản hồi của bạn]]''' * Tại sao đề nghị thay đổi này: '''[[#Background: why this change?|Bối cảnh: tại sao cần thay đổi?]]''' * Các thay đổi được đề nghị: '''[[#Proposal: signature validation requirements|Đề nghị: các quy tắc phê chuẩn chữ ký]]''' * Các ảnh hưởng đến bạn: '''[[#Impact: effects of change|Ảnh hưởng: ảnh hướng của các thay đổi]]''' __TOC__ {{anchor|Input: your feedback}} == Phản hồi: phản hồi của bạn == <div lang="en" dir="ltr" class="mw-content-ltr"> The team wants your feedback about this proposal. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please post your comments about these questions [[Talk:New requirements for user signatures|'''on the talk page''']]: </div> # '''<span lang="en" dir="ltr" class="mw-content-ltr">Would these signature validations create any problems on your wiki?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What do you think the team should be aware of before making this change?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What should be done about existing signatures that don't meet the new limits?</span>''' <em><span lang="en" dir="ltr" class="mw-content-ltr">For example, should they be disallowed?</span></em> <em><span lang="en" dir="ltr" class="mw-content-ltr">Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.</span></em> {{anchor|Background: why this change?}} == Bối cảnh: tại sao cần thay đổi? == <div lang="en" dir="ltr" class="mw-content-ltr"> In 2019, volunteers from [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia projects and usergroups]], along with staff from the Wikimedia Foundation, participated in the [[mw:Talk_pages_consultation_2019|Talk pages consultation]]. It was an effort to define better tools for on-wiki communication. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One of the outcomes of this consultation was [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|a request for an easier way to reply to specific comments]] on talk pages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order for [[mw:Talk_pages_project/replying|this feature]] to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This additional consistency in the format of signatures would improve existing features, like [[mw:Help:Notifications/Types#Mentions|"mention" notifications]], which are only sent if the signature can be detected in your edit. </div> {{anchor|Proposal: signature validation requirements}} == Đề nghị: các quy tắc phê chuẩn chữ ký == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Nếu không gặp trở ngại lớn, thay đổi này có thể xảy ra vào tháng 4 năm 2020. Nếu nhóm cần thực hiện các thay đổi lớn do lời phản hồi của các bạn, quá trình này cũng có thể tốn thêm thì giờ. <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} === Không cho phép một số trường hợp HTML hư hỏng và lỗi [[mw:Help:Extension:Linter|Linter]] khác === {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> === Bắt buộc liên kết đến trang cá nhân, trang thảo luận cá nhân, hoặc danh sách đóng góp === {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> === Không cho phép nhúng “lồng” trong chữ ký === {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Ảnh hưởng: các ảnh hưởng của thay đổi == === Các chữ ký hiện tại được ảnh hưởng như thế nào? === <span lang="en" dir="ltr" class="mw-content-ltr">Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]'').</span> <span lang="en" dir="ltr" class="mw-content-ltr">When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</span> === Các thay đổi này xảy ra lúc nào? === <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. </div> === Chúng ta sẽ nhận ra các thay đổi như thế nào? === <div lang="en" dir="ltr" class="mw-content-ltr"> We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. </div> === Các lỗi phê chuẩn chữ ký xuất hiện như thế nào? === <div lang="en" dir="ltr" class="mw-content-ltr"> The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The required link errors include example wikitext syntax to use. </div> <gallery mode="packed" caption="Lỗi ví dụ"> File:MediaWiki preferences - existing user signature invalid.png|Cảnh báo này xuất hiện nếu chữ ký hiện tại của thành viên là không hợp lệ, tức có lỗi định dạng (''linting error''). File:MediaWiki preferences - new user signature invalid 1.png|Lỗi này xuất hiện nếu chữ ký mới của thành viên là không hợp lệ vì có lỗi định dạng. File:MediaWiki preferences - new user signature invalid 2.png|Lỗi này xuất hiện nếu chữ ký mới của thành viên là không hợp lệ vì thiếu một liên kết được bắt buộc. </gallery> == Kết quả == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> Phần lớn đề nghị được cộng đồng chấp thuận. Do các lời nhận xét của người tình nguyện, nhóm phát triển đã thực hiện một số thay đổi nhỏ và làm rõ một số điểm. # Không cho phép một số trường hợp HTML hư hỏng và lỗi [[mw:Help:Extension:Linter|Linter]] khác #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # Bắt buộc liên kết đến trang cá nhân, trang thảo luận cá nhân, hoặc danh sách đóng góp #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # Không cho phép nhúng “lồng” trong chữ ký #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> Quá trình thực hiện thay đổi này là: * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == Ghi chú == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 5hy5hlkg1jlam7k61vkwgshot8e9s0l 5386376 5386352 2022-07-28T13:25:33Z Shirayuki 472859 update wikitext text/x-wiki <languages/> Nhiều wiki có các quy tắc về các chữ ký thành viên tùy biến. [[Special:MyLanguage/Editing team|Nhóm phát triển sửa đổi]] đang cần bạn cho ý kiến về đề nghị chuyển một số quy tắc này sang mã nguồn trong phần mềm của Wikipedia. Thay đổi này sẽ làm cho người ta có thể [[mw:Talk pages project/replying|trả lời các lời nhận xét riêng trong trang thảo luận]] một cách dễ dàng hơn và sử dụng một số công cụ khác. Bên dưới có thêm chi tiết về đề nghị và lý do: * Nhóm đang cần các thông tin phản hồi sau: '''[[#Input: your feedback|Phản hồi: Phản hồi của bạn]]''' * Tại sao đề nghị thay đổi này: '''[[#Background: why this change?|Bối cảnh: tại sao cần thay đổi?]]''' * Các thay đổi được đề nghị: '''[[#Proposal: signature validation requirements|Đề nghị: các quy tắc phê chuẩn chữ ký]]''' * Các ảnh hưởng đến bạn: '''[[#Impact: effects of change|Ảnh hưởng: ảnh hướng của các thay đổi]]''' __TOC__ {{anchor|Input: your feedback}} == Phản hồi: phản hồi của bạn == <div lang="en" dir="ltr" class="mw-content-ltr"> The team wants your feedback about this proposal. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please post your comments about these questions [[Talk:New requirements for user signatures|'''on the talk page''']]: </div> # '''<span lang="en" dir="ltr" class="mw-content-ltr">Would these signature validations create any problems on your wiki?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What do you think the team should be aware of before making this change?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What should be done about existing signatures that don't meet the new limits?</span>''' <em><span lang="en" dir="ltr" class="mw-content-ltr">For example, should they be disallowed?</span></em> <em><span lang="en" dir="ltr" class="mw-content-ltr">Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.</span></em> {{anchor|Background: why this change?}} == Bối cảnh: tại sao cần thay đổi? == <div lang="en" dir="ltr" class="mw-content-ltr"> In 2019, volunteers from [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia projects and usergroups]], along with staff from the Wikimedia Foundation, participated in the [[mw:Talk_pages_consultation_2019|Talk pages consultation]]. It was an effort to define better tools for on-wiki communication. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One of the outcomes of this consultation was [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|a request for an easier way to reply to specific comments]] on talk pages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order for [[mw:Talk_pages_project/replying|this feature]] to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This additional consistency in the format of signatures would improve existing features, like [[mw:Help:Notifications/Types#Mentions|"mention" notifications]], which are only sent if the signature can be detected in your edit. </div> {{anchor|Proposal: signature validation requirements}} == Đề nghị: các quy tắc phê chuẩn chữ ký == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Nếu không gặp trở ngại lớn, thay đổi này có thể xảy ra vào tháng 4 năm 2020. Nếu nhóm cần thực hiện các thay đổi lớn do lời phản hồi của các bạn, quá trình này cũng có thể tốn thêm thì giờ. <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} === Không cho phép một số trường hợp HTML hư hỏng và lỗi [[mw:Help:Extension:Linter|Linter]] khác === {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> === Bắt buộc liên kết đến trang cá nhân, trang thảo luận cá nhân, hoặc danh sách đóng góp === {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> === Không cho phép nhúng “lồng” trong chữ ký === {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Ảnh hưởng: các ảnh hưởng của thay đổi == === Các chữ ký hiện tại được ảnh hưởng như thế nào? === <span lang="en" dir="ltr" class="mw-content-ltr">Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]'').</span> <span lang="en" dir="ltr" class="mw-content-ltr">When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</span> === Các thay đổi này xảy ra lúc nào? === <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. </div> === Chúng ta sẽ nhận ra các thay đổi như thế nào? === <div lang="en" dir="ltr" class="mw-content-ltr"> We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. </div> === Các lỗi phê chuẩn chữ ký xuất hiện như thế nào? === <div lang="en" dir="ltr" class="mw-content-ltr"> The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The required link errors include example wikitext syntax to use. </div> <gallery mode="packed" caption="Lỗi ví dụ"> File:MediaWiki preferences - existing user signature invalid.png|Cảnh báo này xuất hiện nếu chữ ký hiện tại của thành viên là không hợp lệ, tức có lỗi định dạng (''linting error''). File:MediaWiki preferences - new user signature invalid 1.png|Lỗi này xuất hiện nếu chữ ký mới của thành viên là không hợp lệ vì có lỗi định dạng. File:MediaWiki preferences - new user signature invalid 2.png|Lỗi này xuất hiện nếu chữ ký mới của thành viên là không hợp lệ vì thiếu một liên kết được bắt buộc. </gallery> == Kết quả == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> Phần lớn đề nghị được cộng đồng chấp thuận. Do các lời nhận xét của người tình nguyện, nhóm phát triển đã thực hiện một số thay đổi nhỏ và làm rõ một số điểm. # Không cho phép một số trường hợp HTML hư hỏng và lỗi [[mw:Help:Extension:Linter|Linter]] khác #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # Bắt buộc liên kết đến trang cá nhân, trang thảo luận cá nhân, hoặc danh sách đóng góp #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # Không cho phép nhúng “lồng” trong chữ ký #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> Quá trình thực hiện thay đổi này là: * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == Ghi chú == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 0ziz6hvo6azqmtw0e16e33bineylhho Translations:New requirements for user signatures/2/vi 1198 1149488 5386375 3942381 2022-07-28T13:25:32Z Shirayuki 472859 update wikitext text/x-wiki [[$1|Nhóm phát triển sửa đổi]] đang cần bạn cho ý kiến về đề nghị chuyển một số quy tắc này sang mã nguồn trong phần mềm của Wikipedia. osakke3e8ff0vfglffkvehfhp4v0kw4 New requirements for user signatures/fi 0 1149610 5386344 5325338 2022-07-28T13:22:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> Monissa wikeissä on rajoituksia mukautetuille allekirjoitukselle. <span class="mw-translate-fuzzy">[[Editing team|Editing-tiimi]] pyytää palautettasi ehdotukseen osan näiden vaatimusten lisäämiseksi Wikipedian ohjelmistoon.</span> Tämä tekee [[mw:Talk pages project/replying|tiettyihin kommentteihin vastaamisen]] ja muiden työkalujen käyttämisen helpommaksi. Voit lukea lisää ehdotuksesta ja sen perusteluista alapuolella. * Mitä palautetta tiimi pyytää: '''[[#Input: your feedback|Palaute: Sinun mielipiteesi]]''' * Miksi tätä ehdotetaan: '''[[#Background: why this change?|Tausta: miksi tämä muutos?]]''' * Mitä muutoksia esitetään: '''[[#Proposal: signature validation requirements|Ehdotus: allekirjoitusten vaatimukset]]''' * Miten nämä muutokset vaikuttavat sinuun: '''[[#Impact: effects of change|Vaikutus: muutosten vaikutukset]]''' __TOC__ {{anchor|Input: your feedback}} ==Palaute: Sinun mielipiteesi== Tiimi haluaa palautteesi ehdotukseen liittyen. Kerro kommenttisi näihin kysymyksiin [[Talk:New requirements for user signatures|'''keskustelusivulla''']]: # '''Aiheuttaisivatko nämä muutokset ongelmia wikissäsi?''' # '''Mitä tiimin tulee tietää mielestäsi ennen muutoksen toteuttamista?''' # '''Mitä pitäisi tehdä allekirjoituksille jotka eivät täytä vaatimuksia?''' <em>Esimerkiksi: pitäisikö ne kieltää?</em> <em>Älä rajoita itseäsi ylläoleviin kysymyksiin. Tiimi haluaa kuulla kaiken palautteen jota sinulla on.</em> {{anchor|Background: why this change?}} ==Tausta: miksi tämä muutos?== Vuoden 2019 aikana vapaaehtoiset [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia-projektista ja -yhteisöstä]] sekä Wikimedia Foundationin henkilökuntaa osallistuivat [[mw:Talk_pages_consultation_2019|Talk pages consultation-projektiin]]. Sen tarkoituksena oli kehittää parempia työkaluja Wikin sisäiseen kommunikointiin. Yksi tämän projektin tulos oli [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|pyyntö helpommalle tavalle vastata tiettyihin kommentteihin]] keskustelusivuilla. Jotta [[mw:Talk_pages_project/replying|tämä ominaisuus]] toimisi hyvin, ohjelmiston tulee pystyä konelukemaan käyttäjien allekirjoitukset, jotta se voi luotettavasti tunnistaa eri käyttäjien kommentit ja sallia niihin vastaaminen. Ongelma on se, että vaikka monilla wikeillä on tarvittavat tarvittavat allekirjoitusten vaatimukset käytäntöinä, näitä vaatimuksia ei ole sisällytetty itse ohjelmistoon. Tämä lisää sitä mahdollisuutta, että käyttäjän allekirjoitus rikkoo käytäntöjä ja mahdollisesti tekee keskusteluihin osallistumisesta vaikeampaa. Uudet vaatimukset allekirjoitusten muotoilussa voisivat myös parantaa olemassa olevia ominaisuuksia, kuten [[mw:Help:Notifications/Types#Mentions|''maininta''-ilmoituksia]], jotka lähetetään vain silloin, kun muokkauksessasi on allekirjoitus. {{anchor|Proposal: signature validation requirements}} == Ehdotus: allekirjoitusten vaatimukset == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Jos isoja esteitä ei esiinny, nämä muutokset voisivat tapahtua huhtikuussa 2020. Jos tiimi joutuu tekemään isompia muutoksia palautteesi perusteella, muutoksen toteuttamisessa menee pitempään. <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors === </div> {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Require a link to user page, talk page or contributions === </div> {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow "nested" substitution in signature === </div> {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Impact: effects of change == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What would happen to existing signatures? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]'').</span> <span lang="en" dir="ltr" class="mw-content-ltr">When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === When might these changes take place? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How will we know what changes are happening? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What might the signature validation errors look like? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The required link errors include example wikitext syntax to use. </div> <gallery mode="packed" caption="Example errors"> File:MediaWiki preferences - existing user signature invalid.png|<span lang="en" dir="ltr" class="mw-content-ltr">Warning shown when the existing user signature is invalid (has lint errors).</span> File:MediaWiki preferences - new user signature invalid 1.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (has a lint error).</span> File:MediaWiki preferences - new user signature invalid 2.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (doesn't contain a required link).</span> </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Outcome == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Require a link to user page, talk page or contributions</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow "nested" substitution in signature</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The process for implementing this change is: </div> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Notes == </div> <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] mq8ncjf9cmoai6wcxd1lt9oel2ye9p6 5386362 5386344 2022-07-28T13:23:38Z Shirayuki 472859 update wikitext text/x-wiki <languages/> Monissa wikeissä on rajoituksia mukautetuille allekirjoitukselle. [[Special:MyLanguage/Editing team|Editing-tiimi]] pyytää palautettasi ehdotukseen osan näiden vaatimusten lisäämiseksi Wikipedian ohjelmistoon. Tämä tekee [[mw:Talk pages project/replying|tiettyihin kommentteihin vastaamisen]] ja muiden työkalujen käyttämisen helpommaksi. Voit lukea lisää ehdotuksesta ja sen perusteluista alapuolella. * Mitä palautetta tiimi pyytää: '''[[#Input: your feedback|Palaute: Sinun mielipiteesi]]''' * Miksi tätä ehdotetaan: '''[[#Background: why this change?|Tausta: miksi tämä muutos?]]''' * Mitä muutoksia esitetään: '''[[#Proposal: signature validation requirements|Ehdotus: allekirjoitusten vaatimukset]]''' * Miten nämä muutokset vaikuttavat sinuun: '''[[#Impact: effects of change|Vaikutus: muutosten vaikutukset]]''' __TOC__ {{anchor|Input: your feedback}} ==Palaute: Sinun mielipiteesi== Tiimi haluaa palautteesi ehdotukseen liittyen. Kerro kommenttisi näihin kysymyksiin [[Talk:New requirements for user signatures|'''keskustelusivulla''']]: # '''Aiheuttaisivatko nämä muutokset ongelmia wikissäsi?''' # '''Mitä tiimin tulee tietää mielestäsi ennen muutoksen toteuttamista?''' # '''Mitä pitäisi tehdä allekirjoituksille jotka eivät täytä vaatimuksia?''' <em>Esimerkiksi: pitäisikö ne kieltää?</em> <em>Älä rajoita itseäsi ylläoleviin kysymyksiin. Tiimi haluaa kuulla kaiken palautteen jota sinulla on.</em> {{anchor|Background: why this change?}} ==Tausta: miksi tämä muutos?== Vuoden 2019 aikana vapaaehtoiset [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia-projektista ja -yhteisöstä]] sekä Wikimedia Foundationin henkilökuntaa osallistuivat [[mw:Talk_pages_consultation_2019|Talk pages consultation-projektiin]]. Sen tarkoituksena oli kehittää parempia työkaluja Wikin sisäiseen kommunikointiin. Yksi tämän projektin tulos oli [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|pyyntö helpommalle tavalle vastata tiettyihin kommentteihin]] keskustelusivuilla. Jotta [[mw:Talk_pages_project/replying|tämä ominaisuus]] toimisi hyvin, ohjelmiston tulee pystyä konelukemaan käyttäjien allekirjoitukset, jotta se voi luotettavasti tunnistaa eri käyttäjien kommentit ja sallia niihin vastaaminen. Ongelma on se, että vaikka monilla wikeillä on tarvittavat tarvittavat allekirjoitusten vaatimukset käytäntöinä, näitä vaatimuksia ei ole sisällytetty itse ohjelmistoon. Tämä lisää sitä mahdollisuutta, että käyttäjän allekirjoitus rikkoo käytäntöjä ja mahdollisesti tekee keskusteluihin osallistumisesta vaikeampaa. Uudet vaatimukset allekirjoitusten muotoilussa voisivat myös parantaa olemassa olevia ominaisuuksia, kuten [[mw:Help:Notifications/Types#Mentions|''maininta''-ilmoituksia]], jotka lähetetään vain silloin, kun muokkauksessasi on allekirjoitus. {{anchor|Proposal: signature validation requirements}} == Ehdotus: allekirjoitusten vaatimukset == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Jos isoja esteitä ei esiinny, nämä muutokset voisivat tapahtua huhtikuussa 2020. Jos tiimi joutuu tekemään isompia muutoksia palautteesi perusteella, muutoksen toteuttamisessa menee pitempään. <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors === </div> {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Require a link to user page, talk page or contributions === </div> {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow "nested" substitution in signature === </div> {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Impact: effects of change == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What would happen to existing signatures? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]'').</span> <span lang="en" dir="ltr" class="mw-content-ltr">When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === When might these changes take place? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How will we know what changes are happening? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What might the signature validation errors look like? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The required link errors include example wikitext syntax to use. </div> <gallery mode="packed" caption="Example errors"> File:MediaWiki preferences - existing user signature invalid.png|<span lang="en" dir="ltr" class="mw-content-ltr">Warning shown when the existing user signature is invalid (has lint errors).</span> File:MediaWiki preferences - new user signature invalid 1.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (has a lint error).</span> File:MediaWiki preferences - new user signature invalid 2.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (doesn't contain a required link).</span> </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Outcome == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Require a link to user page, talk page or contributions</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow "nested" substitution in signature</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The process for implementing this change is: </div> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Notes == </div> <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] sik6zglug5yzlk6qkghu7ez6z58jnqr Translations:New requirements for user signatures/2/fi 1198 1149643 5386361 3942883 2022-07-28T13:23:38Z Shirayuki 472859 update wikitext text/x-wiki [[$1|Editing-tiimi]] pyytää palautettasi ehdotukseen osan näiden vaatimusten lisäämiseksi Wikipedian ohjelmistoon. 6xbt3psfr2ges6vshxa2feosh7xkdo8 New requirements for user signatures/pt 0 1149855 5386349 5325344 2022-07-28T13:22:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> Diversas wikis têm exigências para a personalização das assinaturas dos utilizadores. <span class="mw-translate-fuzzy">A [[Editing team|Equipe de Edição]] está buscando sua opinião sobre uma proposta para por alguns desses requisitos na Wikipedia.</span> Facilitando [[mw:Talk pages project/replying|responder a comentários específicos]] nas páginas de discussão e usar algumas outras ferramentas. Para mais detalhes sobre o que está sendo proposto, e por que, veja abaixo: * Que retorno a equipe está buscando: '''[[#Input: your feedback|Entrada: sua avaliação]]''' * Porque está mudança está sendo proposta: '''[[#Background: why this change?|Bastidores: porque está mudando?]]''' * Qual mudança está sendo proposta: '''[[#Proposal: signature validation requirements|Proposta: requisitos de validação de assinatura]]''' * Como essas mudanças pode afetar você: '''[[#Impact: effects of change|Impacto: efeitos da mudança]]''' __TOC__ {{anchor|Input: your feedback}} == Entrada: sua avaliação == <div lang="en" dir="ltr" class="mw-content-ltr"> The team wants your feedback about this proposal. </div> Por favor, poste seu comentário sobre essas questões [[Talk:New requirements for user signatures|'''neste debate''']]: # '''<span lang="en" dir="ltr" class="mw-content-ltr">Would these signature validations create any problems on your wiki?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What do you think the team should be aware of before making this change?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What should be done about existing signatures that don't meet the new limits?</span>''' <em><span lang="en" dir="ltr" class="mw-content-ltr">For example, should they be disallowed?</span></em> <em><span lang="en" dir="ltr" class="mw-content-ltr">Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.</span></em> {{anchor|Background: why this change?}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Background: why this change? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In 2019, volunteers from [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia projects and usergroups]], along with staff from the Wikimedia Foundation, participated in the [[mw:Talk_pages_consultation_2019|Talk pages consultation]]. It was an effort to define better tools for on-wiki communication. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One of the outcomes of this consultation was [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|a request for an easier way to reply to specific comments]] on talk pages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order for [[mw:Talk_pages_project/replying|this feature]] to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This additional consistency in the format of signatures would improve existing features, like [[mw:Help:Notifications/Types#Mentions|"mention" notifications]], which are only sent if the signature can be detected in your edit. </div> {{anchor|Proposal: signature validation requirements}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Proposal: signature validation requirements (2020) == </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Se não forem identificados obstáculos significativos, essa mudança poderá ocorrer em abril de 2020. <span lang="en" dir="ltr" class="mw-content-ltr">If the team needs to make significant changes as a result of your feedback, then it will take longer.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors === </div> {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Require a link to user page, talk page or contributions === </div> {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow "nested" substitution in signature === </div> {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Impact: effects of change == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What would happen to existing signatures? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]'').</span> <span lang="en" dir="ltr" class="mw-content-ltr">When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === When might these changes take place? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How will we know what changes are happening? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What might the signature validation errors look like? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The required link errors include example wikitext syntax to use. </div> <gallery mode="packed" caption="Example errors"> File:MediaWiki preferences - existing user signature invalid.png|<span lang="en" dir="ltr" class="mw-content-ltr">Warning shown when the existing user signature is invalid (has lint errors).</span> File:MediaWiki preferences - new user signature invalid 1.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (has a lint error).</span> File:MediaWiki preferences - new user signature invalid 2.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (doesn't contain a required link).</span> </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Outcome == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Require a link to user page, talk page or contributions</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow "nested" substitution in signature</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The process for implementing this change is: </div> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Notes == </div> <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 5o2arhsqjqcqo3et8jzkfkpz1jxm1rf 5386368 5386349 2022-07-28T13:24:40Z Shirayuki 472859 update wikitext text/x-wiki <languages/> Diversas wikis têm exigências para a personalização das assinaturas dos utilizadores. A [[Special:MyLanguage/Editing team|Equipe de Edição]] está buscando sua opinião sobre uma proposta para por alguns desses requisitos na Wikipedia. Facilitando [[mw:Talk pages project/replying|responder a comentários específicos]] nas páginas de discussão e usar algumas outras ferramentas. Para mais detalhes sobre o que está sendo proposto, e por que, veja abaixo: * Que retorno a equipe está buscando: '''[[#Input: your feedback|Entrada: sua avaliação]]''' * Porque está mudança está sendo proposta: '''[[#Background: why this change?|Bastidores: porque está mudando?]]''' * Qual mudança está sendo proposta: '''[[#Proposal: signature validation requirements|Proposta: requisitos de validação de assinatura]]''' * Como essas mudanças pode afetar você: '''[[#Impact: effects of change|Impacto: efeitos da mudança]]''' __TOC__ {{anchor|Input: your feedback}} == Entrada: sua avaliação == <div lang="en" dir="ltr" class="mw-content-ltr"> The team wants your feedback about this proposal. </div> Por favor, poste seu comentário sobre essas questões [[Talk:New requirements for user signatures|'''neste debate''']]: # '''<span lang="en" dir="ltr" class="mw-content-ltr">Would these signature validations create any problems on your wiki?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What do you think the team should be aware of before making this change?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What should be done about existing signatures that don't meet the new limits?</span>''' <em><span lang="en" dir="ltr" class="mw-content-ltr">For example, should they be disallowed?</span></em> <em><span lang="en" dir="ltr" class="mw-content-ltr">Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.</span></em> {{anchor|Background: why this change?}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Background: why this change? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In 2019, volunteers from [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia projects and usergroups]], along with staff from the Wikimedia Foundation, participated in the [[mw:Talk_pages_consultation_2019|Talk pages consultation]]. It was an effort to define better tools for on-wiki communication. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One of the outcomes of this consultation was [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|a request for an easier way to reply to specific comments]] on talk pages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order for [[mw:Talk_pages_project/replying|this feature]] to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This additional consistency in the format of signatures would improve existing features, like [[mw:Help:Notifications/Types#Mentions|"mention" notifications]], which are only sent if the signature can be detected in your edit. </div> {{anchor|Proposal: signature validation requirements}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Proposal: signature validation requirements (2020) == </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Se não forem identificados obstáculos significativos, essa mudança poderá ocorrer em abril de 2020. <span lang="en" dir="ltr" class="mw-content-ltr">If the team needs to make significant changes as a result of your feedback, then it will take longer.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors === </div> {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Require a link to user page, talk page or contributions === </div> {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow "nested" substitution in signature === </div> {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Impact: effects of change == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What would happen to existing signatures? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]'').</span> <span lang="en" dir="ltr" class="mw-content-ltr">When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === When might these changes take place? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How will we know what changes are happening? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What might the signature validation errors look like? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The required link errors include example wikitext syntax to use. </div> <gallery mode="packed" caption="Example errors"> File:MediaWiki preferences - existing user signature invalid.png|<span lang="en" dir="ltr" class="mw-content-ltr">Warning shown when the existing user signature is invalid (has lint errors).</span> File:MediaWiki preferences - new user signature invalid 1.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (has a lint error).</span> File:MediaWiki preferences - new user signature invalid 2.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (doesn't contain a required link).</span> </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Outcome == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Require a link to user page, talk page or contributions</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow "nested" substitution in signature</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The process for implementing this change is: </div> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Notes == </div> <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 80l0c40fpapt2pistv0luysxa9xi7sk New requirements for user signatures/uk 0 1149859 5386353 5325349 2022-07-28T13:22:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> На багатьох вікі є певні вимоги до користувацьких підписів. <span class="mw-translate-fuzzy">[[Editing team|Команда з редагування]] потребує ваших відгуків щодо пропозиції кодифікувати деякі з цих вимог в програмному забезпеченні Вікіпедії.</span> Це полегшить [[mw:Talk pages project/replying|додавання відповідей на конкретні коментарі на сторінках обговорень]] і використання деяких інших інструментів. Ви можете знайти більше подробиць про те, що і для чого пропонується, нижче: * Яких відгуків потребує команда: '''[[#Input: your feedback|Введення: ваш відгук]]''' * Чому пропонується ця зміна: '''[[#Background: why this change?|Передісторія: чому така зміна?]]''' * Яка зміна пропонується: '''[[#Proposal: signature validation requirements|Пропозиція: вимоги до підтвердження підпису]]''' * Як ці зміни могли б вплинути на вас: '''[[#Impact: effects of change|Наслідки: ефекти зміни]]''' __TOC__ {{anchor|Input: your feedback}} == Введення: ваш відгук == Команда бажає отримати ваш відгук про цю пропозицію. Будь ласка, залишіть свої коментарі до цих питань [[Talk:New requirements for user signatures|'''на сторінці обговорення''']]: # '''Чи зумовить валідація підписів проблеми на вашій вікі?''' # '''На що, на вашу думку, повинна звернути увагу команда перед внесенням змін?''' # '''Як слід вчинити з вже наявними підписами, які не відповідають новим обмеженням?''' <em>Наприклад, чи потрібно їх заборонити?</em> <em>Просимо не обмежувати себе вищенаведеними питаннями. Команда хотіла б почути всі думки, якими ви можете поділитися.</em> {{anchor|Background: why this change?}} == Передісторія: чому така зміна? == У 2019 році добровольці з [[mw:Talk pages consultation 2019/Participant group sign-up|20 проєктів Вікімедіа та груп користувачів]], спільно з працівниками Фонду Вікімедіа, взяли участь в [[mw:Talk_pages_consultation_2019|консультації про сторінки обговорення]]. Це був захід з визначення кращих засобів спілкування на вікі. Одним з наслідків цієї консультації був [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|запит на полегшення відповіді на конкретні коментарі]] на сторінках обговорень. Для забезпечення правильної роботи [[mw:Talk_pages_project/replying|цієї можливості]], програмне забезпечення мусить працювати з «машино-читабельними» підписами, щоб точно знаходити коментарі користувачів і давати змогу відповідати на них. Проблема в тому, що, хоч на багатьох вікі вже існують вимоги до підписів, ці вимоги не включені в саме програмне забезпечення. Це збільшує шанс появи підписів, які порушують правила вікі, а в перспективі — ускладнять участь в обговореннях. Ця додаткова послідовність форматування підписів покращила б наявні можливості, наприклад [[mw:Help:Notifications/Types#Mentions|сповіщення про «згадки»]], які надсилаються лише тоді, коли у вашому редагуванні можна виявити підпис. {{anchor|Proposal: signature validation requirements}} == Пропозиція: вимоги до підтвердження підпису (2020) == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Якщо не виявиться значних перешкод, зміна відбудеться в квітні 2020 року. Якщо команда буде змушена внести значні зміни як результат ваших відгуків, то це потребуватиме більше часу. В цьому розділі описано три запропоновані критерії. Вони застосовуватимуться до користувацьких підписів у Налаштуваннях, коли користувач зберігатиме відредагований підпис. {{Highlight|1=<big>За пропозицією Команди з редагування '''наявні підписи *НЕ БУДУТЬ* зачеплені'''.</big>|color=yellow}} === Заборона неді1йсної HTML та інших помилок [[mw:Help:Extension:Linter|Linter]] === {{Tracked|T140606}} Перш за все, ця зміна заборонить незакриті теги форматування, наприклад {{tag|i|open}} або відповідну розмітку вікі-тексту, <code><nowiki>''</nowiki></code>, без парного закриваючого тегу (в цьому випадку, {{tag|i|close}} або <code><nowiki>''</nowiki></code>, відповідно). Підписи, що містять недійсну розмітку, можуть датися взнаки всій сторінці обговорення, оскільки форматування пошириться на подальші коментарі. Критерій також виявлятиме [[Special:LintErrors/misnested-tag|неправильне вкладання тегів]], як-от <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (або обидва теги <code>i</code>, або обидва теги <code>b</code> мають бути назовні), і [[Special:LintErrors/stripped-tag|непарні теги]], закриваючі теги без відповідних відкриваючих тегів (протилежність «незакритих тегів форматування», згаданих вище). Підписи, які містять менш критичні помилки, також будуть заборонені, як-от застарілі теги HTML {{tag|tt}} і {{tag|font}}. Хоча вони безпосередньо не викликають проблем, така заборона зупинить поширення застарілого коду на нові вікі-сторінки, яке дратує редакторів, що прибирають помилки Linter. Повний список можливостей синтаксису, які буде заборонено, разом з посиланнями на сторінки пояснень, як оновити або виправити код з помилками Linter, доступний за [[mw:Help:Extension:Linter#Documentation of lint issues|цією адресою]]. Програмне забезпечення мало б вже нині запобігати появі незакритих тегів форматування, але через обмеження нинішнього парсера вікітексту це працювало в небагатьох випадках. Більш надійний засіб став можливим завдяки [[Parsoid]]. === Обов'язкове посилання на сторінку користувача, сторінку обговорення або внеску === {{Tracked|T237700}} Багато інструментів не працюють належним чином, якщо підпис не містить хоча б одного з наступних посилань: на сторінку користувача, сторінку обговорення користувача, або сторінку внеску користувача. Наприклад, [[mw:Help:Notifications/Types#Mentions|сповіщення про «згадки»]] не надсилаються, а очікуване невдовзі розширення [[mw:Extension:DiscussionTools|DiscussionTools]] не зможе відповідати на коментарі з такими некоректними підписами. Гаджети та інші інструменти, які взаємодіють з підписами, також можуть працювати неочікуваним чином. Ця вимога давно присутня в багатьох правилах проєктів Вікімедіа, але MediaWiki досі не забезпечує її обов'язкове виконання.<ref>Див. список прикладів у [[phab:T237700|T237700]].</ref> === Заборона «вкладених» підстановок у підписах === {{Tracked|T230652}} ''Деякі'' використання розмітки [[subst:]] і тильд також будуть заборонені в підписах. До цього можна було використовувати ці можливості для створення підпису, який підставляв у ваш коментар ім'я наступного редактора. Усі форми фальсифікації підписів давно заборонені правилами великих вікі, і цьому виду фальсифікації віднині буде запобігати програмне забезпечення. Проста розмітка subst: і далі дозволятиметься. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Наслідки: ефекти зміни == == Що буде з наявними підписами? == Всі наявні підписи, які стануть некоректними за новими правилами, залишаться дозволеними (''[[:en:Grandfather_clause|зворотньої дії немає]]''). При перегляді ваших налаштувань ви побачите попередження про це, і якщо ви пробуєте відредагувати ваш підпис, результат має бути коректним. Але якщо ви його не редагуватимете, старий некоректний підпис і далі використовуватиметься, і ви зможете змінювати інші налаштування, оминаючи його. Ми чекаємо на відгуки щодо заборони вже наявних некоректних підписів. Якщо некоректні підписи буде заборонено, то в коментарі зачеплених користувачів буде додаватися підпис за замовчанням, доки вони не виправлять свої користувацькі підписи. === Коли можуть відбутися ці зміни? === Будь ласка, залиште коментар до 31 березня 2020 року. Команда з редагувань прийме рішення щодо цього проєкту на початку квітня. Результати буде опубліковано на сторінці обговорення. Якщо не буде виявлено значних перешкод, зміни відбудуться не раніше квітня 2020 року. Цей термін може бути відкладено, якщо команда буде змушена внести значні зміни в результаті ваших відгуків. === Як ми дізнаватимемося, які зміни відбудуться? === Ми зробимо оповіщення в [[m:Tech/News]], коли цю зміну скоро буде реалізовано. === Як можуть виглядати помилки перевірки підпису? === Помилки HTML/lint включатимуть посилання на наявну документацію про помилки lint, як-от [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], і кнопку для підсвітки проблемної частини підпису. Помилки обов'язкового посилання включатимуть приклад вікітексту для використання. <gallery mode="packed" caption="Приклади помилок"> File:MediaWiki preferences - existing user signature invalid.png|Попередження, яке відображається, коли наявний підпис користувача некоректний (містить помилки lint). File:MediaWiki preferences - new user signature invalid 1.png|Помилка, яка відображається, коли новий підпис користувача некоректний (містить помилку lint). File:MediaWiki preferences - new user signature invalid 2.png|Помилка, яка відображається, коли новий підпис користувача некоректний (не містить обов'язкового посилання). </gallery> == Результат == === Оригінальна пропозиція === Пропозиція була загалом прийнята. У відповідь на коментарі добровольців було зроблено декілька незначних змін і прояснено деякі моменти. # Заборона недійсної HTML та інших помилок [[mw:Help:Extension:Linter|Linter]] #:Масштаб цих змін буде зменшено. [[Special:LintErrors/misnested-tag|Неправильно вкладені]] й [[Special:LintErrors/stripped-tag|непарні]] теги буде заборонено. Деякі помилки з низьким пріоритетом залишаться прийнятними. Зокрема, застарілі теги HTML на зразок {{tag|tt}} і {{tag|font}} поки що не заборонятимуться. Це рішення не впливатиме на майбутні рішення за чи проти усунення цих застарілих тегів HTML. # Обов'язкове посилання на сторінку користувача, сторінку обговорення або внеску #:Реалізація відбудеться згідно початкового плану. #:Для ясності, підпис має містити хоча б одне пряме посилання (не через перенаправлення, наприклад, зі старого імені користувача) на одну з цих сторінок. Таким чином, підпис <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> буде прийнятним (одне локальне посилання, одне посилання на іншу вікі), але підпис, який містить <em>тільки</em> посилання на іншу вікі, або <em>тільки</em> перенаправлення зі старого імені користувача, буде некоректним. Додано з технічних причин. # Заборона «вкладених» підстановок у підписах #:Реалізація відбудеться згідно початкового плану. Процес реалізації цієї зміни наступний: * {{done}} Загальне оголошення буде зроблено в [[m:Tech/News|технічних новинах]], коли нові вимоги буде реалізовано. * {{done}} Як тільки програмне забезпечення буде модифіковано на серверах, користувачі більше не зможуть зберігати некоректні користувацькі підписи. Втім, вже наявні підписи буде збережено. * {{in progress}} Активних користувачів з некоректними підписами заохочуватимуть змінити їхні підписи. Очікується, що цей процес триватиме кілька місяців. * З часом всі підписи будуть узгоджені. Якщо користувачі не виправлять свої користувацькі підписи, тоді ці підписи припинять працювати, а замість них з'являтиметься підпис за замовчуванням. Сторонні вікі зможуть ввести цю зміну самостійно. === Пропозиція 2021 року === Символи [[:uk:Повернення каретки|повернення каретки]] та [[:uk:Символ нового рядка|переведення рядка]] (але не HTML-коди для них, наприклад, {{tag|br|single}} і {{tag|p|open}}) заборонені. == Примітки == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] gcbqo672zittun9zng4vo60c5neh5e1 5386374 5386353 2022-07-28T13:25:23Z Shirayuki 472859 update wikitext text/x-wiki <languages/> На багатьох вікі є певні вимоги до користувацьких підписів. [[Special:MyLanguage/Editing team|Команда з редагування]] потребує ваших відгуків щодо пропозиції кодифікувати деякі з цих вимог в програмному забезпеченні Вікіпедії. Це полегшить [[mw:Talk pages project/replying|додавання відповідей на конкретні коментарі на сторінках обговорень]] і використання деяких інших інструментів. Ви можете знайти більше подробиць про те, що і для чого пропонується, нижче: * Яких відгуків потребує команда: '''[[#Input: your feedback|Введення: ваш відгук]]''' * Чому пропонується ця зміна: '''[[#Background: why this change?|Передісторія: чому така зміна?]]''' * Яка зміна пропонується: '''[[#Proposal: signature validation requirements|Пропозиція: вимоги до підтвердження підпису]]''' * Як ці зміни могли б вплинути на вас: '''[[#Impact: effects of change|Наслідки: ефекти зміни]]''' __TOC__ {{anchor|Input: your feedback}} == Введення: ваш відгук == Команда бажає отримати ваш відгук про цю пропозицію. Будь ласка, залишіть свої коментарі до цих питань [[Talk:New requirements for user signatures|'''на сторінці обговорення''']]: # '''Чи зумовить валідація підписів проблеми на вашій вікі?''' # '''На що, на вашу думку, повинна звернути увагу команда перед внесенням змін?''' # '''Як слід вчинити з вже наявними підписами, які не відповідають новим обмеженням?''' <em>Наприклад, чи потрібно їх заборонити?</em> <em>Просимо не обмежувати себе вищенаведеними питаннями. Команда хотіла б почути всі думки, якими ви можете поділитися.</em> {{anchor|Background: why this change?}} == Передісторія: чому така зміна? == У 2019 році добровольці з [[mw:Talk pages consultation 2019/Participant group sign-up|20 проєктів Вікімедіа та груп користувачів]], спільно з працівниками Фонду Вікімедіа, взяли участь в [[mw:Talk_pages_consultation_2019|консультації про сторінки обговорення]]. Це був захід з визначення кращих засобів спілкування на вікі. Одним з наслідків цієї консультації був [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|запит на полегшення відповіді на конкретні коментарі]] на сторінках обговорень. Для забезпечення правильної роботи [[mw:Talk_pages_project/replying|цієї можливості]], програмне забезпечення мусить працювати з «машино-читабельними» підписами, щоб точно знаходити коментарі користувачів і давати змогу відповідати на них. Проблема в тому, що, хоч на багатьох вікі вже існують вимоги до підписів, ці вимоги не включені в саме програмне забезпечення. Це збільшує шанс появи підписів, які порушують правила вікі, а в перспективі — ускладнять участь в обговореннях. Ця додаткова послідовність форматування підписів покращила б наявні можливості, наприклад [[mw:Help:Notifications/Types#Mentions|сповіщення про «згадки»]], які надсилаються лише тоді, коли у вашому редагуванні можна виявити підпис. {{anchor|Proposal: signature validation requirements}} == Пропозиція: вимоги до підтвердження підпису (2020) == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Якщо не виявиться значних перешкод, зміна відбудеться в квітні 2020 року. Якщо команда буде змушена внести значні зміни як результат ваших відгуків, то це потребуватиме більше часу. В цьому розділі описано три запропоновані критерії. Вони застосовуватимуться до користувацьких підписів у Налаштуваннях, коли користувач зберігатиме відредагований підпис. {{Highlight|1=<big>За пропозицією Команди з редагування '''наявні підписи *НЕ БУДУТЬ* зачеплені'''.</big>|color=yellow}} === Заборона неді1йсної HTML та інших помилок [[mw:Help:Extension:Linter|Linter]] === {{Tracked|T140606}} Перш за все, ця зміна заборонить незакриті теги форматування, наприклад {{tag|i|open}} або відповідну розмітку вікі-тексту, <code><nowiki>''</nowiki></code>, без парного закриваючого тегу (в цьому випадку, {{tag|i|close}} або <code><nowiki>''</nowiki></code>, відповідно). Підписи, що містять недійсну розмітку, можуть датися взнаки всій сторінці обговорення, оскільки форматування пошириться на подальші коментарі. Критерій також виявлятиме [[Special:LintErrors/misnested-tag|неправильне вкладання тегів]], як-от <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (або обидва теги <code>i</code>, або обидва теги <code>b</code> мають бути назовні), і [[Special:LintErrors/stripped-tag|непарні теги]], закриваючі теги без відповідних відкриваючих тегів (протилежність «незакритих тегів форматування», згаданих вище). Підписи, які містять менш критичні помилки, також будуть заборонені, як-от застарілі теги HTML {{tag|tt}} і {{tag|font}}. Хоча вони безпосередньо не викликають проблем, така заборона зупинить поширення застарілого коду на нові вікі-сторінки, яке дратує редакторів, що прибирають помилки Linter. Повний список можливостей синтаксису, які буде заборонено, разом з посиланнями на сторінки пояснень, як оновити або виправити код з помилками Linter, доступний за [[mw:Help:Extension:Linter#Documentation of lint issues|цією адресою]]. Програмне забезпечення мало б вже нині запобігати появі незакритих тегів форматування, але через обмеження нинішнього парсера вікітексту це працювало в небагатьох випадках. Більш надійний засіб став можливим завдяки [[Parsoid]]. === Обов'язкове посилання на сторінку користувача, сторінку обговорення або внеску === {{Tracked|T237700}} Багато інструментів не працюють належним чином, якщо підпис не містить хоча б одного з наступних посилань: на сторінку користувача, сторінку обговорення користувача, або сторінку внеску користувача. Наприклад, [[mw:Help:Notifications/Types#Mentions|сповіщення про «згадки»]] не надсилаються, а очікуване невдовзі розширення [[mw:Extension:DiscussionTools|DiscussionTools]] не зможе відповідати на коментарі з такими некоректними підписами. Гаджети та інші інструменти, які взаємодіють з підписами, також можуть працювати неочікуваним чином. Ця вимога давно присутня в багатьох правилах проєктів Вікімедіа, але MediaWiki досі не забезпечує її обов'язкове виконання.<ref>Див. список прикладів у [[phab:T237700|T237700]].</ref> === Заборона «вкладених» підстановок у підписах === {{Tracked|T230652}} ''Деякі'' використання розмітки [[subst:]] і тильд також будуть заборонені в підписах. До цього можна було використовувати ці можливості для створення підпису, який підставляв у ваш коментар ім'я наступного редактора. Усі форми фальсифікації підписів давно заборонені правилами великих вікі, і цьому виду фальсифікації віднині буде запобігати програмне забезпечення. Проста розмітка subst: і далі дозволятиметься. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Наслідки: ефекти зміни == == Що буде з наявними підписами? == Всі наявні підписи, які стануть некоректними за новими правилами, залишаться дозволеними (''[[:en:Grandfather_clause|зворотньої дії немає]]''). При перегляді ваших налаштувань ви побачите попередження про це, і якщо ви пробуєте відредагувати ваш підпис, результат має бути коректним. Але якщо ви його не редагуватимете, старий некоректний підпис і далі використовуватиметься, і ви зможете змінювати інші налаштування, оминаючи його. Ми чекаємо на відгуки щодо заборони вже наявних некоректних підписів. Якщо некоректні підписи буде заборонено, то в коментарі зачеплених користувачів буде додаватися підпис за замовчанням, доки вони не виправлять свої користувацькі підписи. === Коли можуть відбутися ці зміни? === Будь ласка, залиште коментар до 31 березня 2020 року. Команда з редагувань прийме рішення щодо цього проєкту на початку квітня. Результати буде опубліковано на сторінці обговорення. Якщо не буде виявлено значних перешкод, зміни відбудуться не раніше квітня 2020 року. Цей термін може бути відкладено, якщо команда буде змушена внести значні зміни в результаті ваших відгуків. === Як ми дізнаватимемося, які зміни відбудуться? === Ми зробимо оповіщення в [[m:Tech/News]], коли цю зміну скоро буде реалізовано. === Як можуть виглядати помилки перевірки підпису? === Помилки HTML/lint включатимуть посилання на наявну документацію про помилки lint, як-от [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], і кнопку для підсвітки проблемної частини підпису. Помилки обов'язкового посилання включатимуть приклад вікітексту для використання. <gallery mode="packed" caption="Приклади помилок"> File:MediaWiki preferences - existing user signature invalid.png|Попередження, яке відображається, коли наявний підпис користувача некоректний (містить помилки lint). File:MediaWiki preferences - new user signature invalid 1.png|Помилка, яка відображається, коли новий підпис користувача некоректний (містить помилку lint). File:MediaWiki preferences - new user signature invalid 2.png|Помилка, яка відображається, коли новий підпис користувача некоректний (не містить обов'язкового посилання). </gallery> == Результат == === Оригінальна пропозиція === Пропозиція була загалом прийнята. У відповідь на коментарі добровольців було зроблено декілька незначних змін і прояснено деякі моменти. # Заборона недійсної HTML та інших помилок [[mw:Help:Extension:Linter|Linter]] #:Масштаб цих змін буде зменшено. [[Special:LintErrors/misnested-tag|Неправильно вкладені]] й [[Special:LintErrors/stripped-tag|непарні]] теги буде заборонено. Деякі помилки з низьким пріоритетом залишаться прийнятними. Зокрема, застарілі теги HTML на зразок {{tag|tt}} і {{tag|font}} поки що не заборонятимуться. Це рішення не впливатиме на майбутні рішення за чи проти усунення цих застарілих тегів HTML. # Обов'язкове посилання на сторінку користувача, сторінку обговорення або внеску #:Реалізація відбудеться згідно початкового плану. #:Для ясності, підпис має містити хоча б одне пряме посилання (не через перенаправлення, наприклад, зі старого імені користувача) на одну з цих сторінок. Таким чином, підпис <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> буде прийнятним (одне локальне посилання, одне посилання на іншу вікі), але підпис, який містить <em>тільки</em> посилання на іншу вікі, або <em>тільки</em> перенаправлення зі старого імені користувача, буде некоректним. Додано з технічних причин. # Заборона «вкладених» підстановок у підписах #:Реалізація відбудеться згідно початкового плану. Процес реалізації цієї зміни наступний: * {{done}} Загальне оголошення буде зроблено в [[m:Tech/News|технічних новинах]], коли нові вимоги буде реалізовано. * {{done}} Як тільки програмне забезпечення буде модифіковано на серверах, користувачі більше не зможуть зберігати некоректні користувацькі підписи. Втім, вже наявні підписи буде збережено. * {{in progress}} Активних користувачів з некоректними підписами заохочуватимуть змінити їхні підписи. Очікується, що цей процес триватиме кілька місяців. * З часом всі підписи будуть узгоджені. Якщо користувачі не виправлять свої користувацькі підписи, тоді ці підписи припинять працювати, а замість них з'являтиметься підпис за замовчуванням. Сторонні вікі зможуть ввести цю зміну самостійно. === Пропозиція 2021 року === Символи [[:uk:Повернення каретки|повернення каретки]] та [[:uk:Символ нового рядка|переведення рядка]] (але не HTML-коди для них, наприклад, {{tag|br|single}} і {{tag|p|open}}) заборонені. == Примітки == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] i41p26wyy84wozp46dlmthehhu8pjby Translations:New requirements for user signatures/2/uk 1198 1149861 5386373 3943689 2022-07-28T13:25:22Z Shirayuki 472859 update wikitext text/x-wiki [[$1|Команда з редагування]] потребує ваших відгуків щодо пропозиції кодифікувати деякі з цих вимог в програмному забезпеченні Вікіпедії. mkuwpqhc738p0dqi7ellxn9jdvvsvjs New requirements for user signatures/ko 0 1150258 5386346 5325341 2022-07-28T13:22:28Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <span lang="en" dir="ltr" class="mw-content-ltr">Many wikis have requirements for custom user signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Editing team|Editing team]] is seeking your input on a proposal to codify some of these requirements in Wikipedia's software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will make it easier to [[mw:Talk pages project/replying|reply to specific comments on talk pages]] and to use some other tools.</span> 제안되는 내용과 그 이유에 대한 자세한 내용은 아래에서 확인하세요: * 팀이 추구하는 피드백: '''[[#Input: your feedback|<span lang="en" dir="ltr" class="mw-content-ltr">Input: your feedback</span>]]''' * <span lang="en" dir="ltr" class="mw-content-ltr">Why this change is being proposed:</span> '''[[#Background: why this change?|<span lang="en" dir="ltr" class="mw-content-ltr">Background: why this change?</span>]]''' * <span lang="en" dir="ltr" class="mw-content-ltr">What change is being proposed:</span> '''[[#Proposal: signature validation requirements|<span lang="en" dir="ltr" class="mw-content-ltr">Proposal: signature validation requirements</span>]]''' * <span lang="en" dir="ltr" class="mw-content-ltr">How these changes could affect you:</span> '''[[#Impact: effects of change|<span lang="en" dir="ltr" class="mw-content-ltr">Impact: effects of change</span>]]''' __TOC__ {{anchor|Input: your feedback}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Input: your feedback == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The team wants your feedback about this proposal. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please post your comments about these questions [[Talk:New requirements for user signatures|'''on the talk page''']]: </div> # '''<span lang="en" dir="ltr" class="mw-content-ltr">Would these signature validations create any problems on your wiki?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What do you think the team should be aware of before making this change?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What should be done about existing signatures that don't meet the new limits?</span>''' <em><span lang="en" dir="ltr" class="mw-content-ltr">For example, should they be disallowed?</span></em> <em><span lang="en" dir="ltr" class="mw-content-ltr">Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.</span></em> {{anchor|Background: why this change?}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Background: why this change? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In 2019, volunteers from [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia projects and usergroups]], along with staff from the Wikimedia Foundation, participated in the [[mw:Talk_pages_consultation_2019|Talk pages consultation]]. It was an effort to define better tools for on-wiki communication. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One of the outcomes of this consultation was [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|a request for an easier way to reply to specific comments]] on talk pages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order for [[mw:Talk_pages_project/replying|this feature]] to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This additional consistency in the format of signatures would improve existing features, like [[mw:Help:Notifications/Types#Mentions|"mention" notifications]], which are only sent if the signature can be detected in your edit. </div> {{anchor|Proposal: signature validation requirements}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Proposal: signature validation requirements (2020) == </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' <span lang="en" dir="ltr" class="mw-content-ltr">If no significant obstacles are identified, this change could happen in April 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the team needs to make significant changes as a result of your feedback, then it will take longer.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors === </div> {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Require a link to user page, talk page or contributions === </div> {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow "nested" substitution in signature === </div> {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Impact: effects of change == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What would happen to existing signatures? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]'').</span> <span lang="en" dir="ltr" class="mw-content-ltr">When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === When might these changes take place? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How will we know what changes are happening? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What might the signature validation errors look like? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The required link errors include example wikitext syntax to use. </div> <gallery mode="packed" caption="Example errors"> File:MediaWiki preferences - existing user signature invalid.png|<span lang="en" dir="ltr" class="mw-content-ltr">Warning shown when the existing user signature is invalid (has lint errors).</span> File:MediaWiki preferences - new user signature invalid 1.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (has a lint error).</span> File:MediaWiki preferences - new user signature invalid 2.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (doesn't contain a required link).</span> </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Outcome == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Require a link to user page, talk page or contributions</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow "nested" substitution in signature</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The process for implementing this change is: </div> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == 각주 == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] a44a0vkuj6ym523ttrzedo2g9bboe9p Translations:New requirements for user signatures/2/pt 1198 1152662 5386367 3953146 2022-07-28T13:24:39Z Shirayuki 472859 update wikitext text/x-wiki A [[$1|Equipe de Edição]] está buscando sua opinião sobre uma proposta para por alguns desses requisitos na Wikipedia. 3u92kq2pwdo9dwtumqa7iyptibv7nk9 Template:Empty section/ar 10 1160978 5387896 3977073 2022-07-29T10:40:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = {{notice|1=هذا القسم فارغ. <span class="mw-translate-fuzzy">يمكنك مساعدة موقع MediaWiki.org بإضافة محتوى إليه.</span>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> llq1dumkc06qm627y649pk75acdgtn2 New requirements for user signatures/ar 0 1166008 5386342 5325335 2022-07-28T13:22:24Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> كثير من الويكيات بها متطلبات لتخصيص التوقيع. <span class="mw-translate-fuzzy">يبحث [[Editing team|فريق التحرير]] لتشفير بعض هذه المتطلبات في برنامج ويكيبيديا.</span> سيسهل ذلك [[mw:Talk pages project/replying|الرد على تعليقات محددة في صفحات النقاش]] واستخدام بعض الأدوات الأخرى. ستجد تفاصيل أكثر عما سيجري، ولماذا، أدناه: * ما التغذية الخلفية (الآراء) التي يريدها الفريق: '''[[#Input: your feedback|أدخل: تغذيتك الخلفية (رأيك)]]''' * لماذا يجرى تنفيذ هذا التغيير: '''[[#Background: why this change?|خلفية: لماذا هذا التغيير؟]]''' * ما هو التغيير المقترح؟ '''[[#Proposal: signature validation requirements|مقترح: متطلبات التحقق من صحة التوقيع]]''' * كيف ستؤثر هذه التغييرات عليك: '''[[#Impact: effects of change|الأثر: آثار التغيير]]''' __TOC__ {{anchor|Input: your feedback}} ==أدخل: تغذيتك الخلفية (رأيك)== يحتاج الفريق لتعليقاتكم حول هذا المقترح. من فضلك اكتب تعليقك حول هذه الأسئلة في [[Talk:New requirements for user signatures|'''صفحة النقاش''']]: # '''هل تؤدي عمليات التحقق من صحة التوقيع هذه إلى حدوث أي مشاكل في الويكي الخاص بك؟''' # '''ما الذي يجب أن يكون الفريق على دراية به قبل إجراء هذا التغيير؟''' # '''ما الذي يجب فعله بشأن التوقيعات الحالية التي لا تتوافق مع المتطلبات الجديدة؟''' <em>على سبيل المثال ، هل يجب منعها؟</em> <em>من فضلك لا تتقيد بالأسئلة أعلاه. يريد الفريق سماع أي تعليقات يمكنك إضافتها.</em> {{anchor|Background: why this change?}} ==خلفية: لماذا هذا التغيير؟== في 2019، قام متطوعون من [[mw:Talk pages consultation 2019/Participant group sign-up|20 مشروع ويكيميديا ومجموعات المستخدمين]] مع عاملين من مؤسسة ويكيميديا بالمشاركة في [[mw:Talk_pages_consultation_2019|نقاش للتشاور]]. كان ذلك محاولة لتحديد أدوات أفضل للتواصل على الويكي. كان أحد مخرجات هذا التشاور [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|طلب لطريقة أسهل للرد على تعليقات محددة]] على صفحات النقاش. لجعل [[mw:Talk_pages_project/replying|هذه الخاصية]] تعمل جيدا، يحتاج البرنامج إلى أن تكون التوقيعات "قابلة للقراءة آليًا"، حتى يتمكن من الكشف بشكل موثوق عن تعليقات المستخدمين والسماح بالرد عليها. كانت المشكلة هي أنه في حين أن العديد من مواقع الويكي لديها بالفعل متطلبات التوقيع اللازمة، فإن هذه المتطلبات ليست مدرجة في البرنامج نفسه. وهذا يزيد من احتمالات قيام شخص ما بتعيين توقيع يخالف اصطلاحات الويكي ويحتمل أن يزيد من صعوبة مشاركة الأشخاص في المحادثات. سيؤدي هذا التناسق الإضافي في تنسيق التوقيعات إلى تحسين الميزات الحالية، مثل [[mw:Help:Notifications/Types#Mentions|إعلام "التنبيهات"]]، التي يتم إرسالها فقط إذا كان من الممكن الكشف عن التوقيع في تعديلك. {{anchor|Proposal: signature validation requirements}} ==مقترح: متطلبات التحقق من صحة التوقيع== <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' إذا لم يتم تحديد عوائق كبيرة ، فقد يحدث هذا التغيير في أبريل 2020. إذا كان الفريق بحاجة إلى إجراء تغييرات كبيرة نتيجة لتعليقاتكم، فسيستغرق الأمر وقتًا أطول. الاختبارات الثلاثة المقترحة موضحة في هذا القسم. سيتم تطبيق هذه على توقيعات المستخدم في التفضيلات عندما يقوم المستخدم بحفظ توقيع معدل. {{Highlight|1=<big>وفق اقتراح فريق التحرير "لن تتأثر التوقيعات الحالية".</big>|color=yellow}} ===تم إيقاف بعض تعبيرات HTML غير المناسبة وبعض أخطاء [[mw:Help:Extension:Linter|لنت]]=== {{Tracked|T140606}} أهم الأمور هو أن هذا التغيير قد ينتج عنه منع وسوم التنسيق غير المغلقة، مثل {{tag|i|open}} أو ما يقابله في ترميز نصوص الويكي، <code><nowiki>''</nowiki></code>، دون وجود وسم إغلاق ملائم (في هذه الحالة هو {{tag|i|close}} أو <code><nowiki>''</nowiki></code> بالترتيب). قد تؤثر التوقيعات التي تحتوي على ترميز غير صالح على كامل صفحة النقاش، حينما يستمر التنسيق نحو التعليقات التالية. كما أن التحقق يحدد أيضا [[Special:LintErrors/misnested-tag|الوسوم المدمجة خطأ]]، مثل <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (سواء كان ذلك من أجل <code>i</code> أو من أجل كلا من <code>b</code> يجب أن تكون الوسوم في الخارج)، وكذلك [[Special:LintErrors/stripped-tag|الوسوم الناقصة]] أي تلك الوسوم الختامية التي لا يوجد لها وسم افتتاحي (نقيض «وسوم التنسيق غير المغلقة» المذكورة سالفا). سيتم أيضًا رفض التوقيعات التي تحتوي على بعض المشكلات الأقل خطورة، على سبيل المثال، علامات HTML القديمة مثل {{tag|tt}} و{{tag|font}}. في حين أن هذه لا تسبب مشاكل فورية، فإن القيام بذلك من شأنه أن يمنع انتشار التعليمات البرمجية القديمة إلى صفحات ويكي الجديدة، وهو أمر مزعج للمحررين الذين يقومون بتنظيف أخطاء Linter. تتوفر قائمة كاملة بميزات بناء الجملة التي لن يُسمح بها، جنبًا إلى جنب مع روابط للصفحات التي تشرح كيفية تحديث أو إصلاح التعليمات البرمجية بأخطاء Linter، على [[mw:Help:Extension:Linter#Documentation of lint issues|هذا العنوان]]. كان من المفترض بالفعل أن يتم منع علامات التنسيق غير المغلقة بواسطة البرنامج، ولكن نظرًا لقيود محلل نص ويكي نص الحالي، فقد نجح هذا فقط في بعض الحالات. أصبح الحل الأكثر قوة ممكنًا بفضل [[Parsoid]]. ===تتطلب رابطًا لصفحة المستخدم أو صفحة النقاش أو المساهمات=== {{Tracked|T237700}} لا تعمل الأدوات المختلفة بشكل صحيح عندما لا يحتوي التوقيع على واحد على الأقل من الروابط التالية: رابط إلى صفحة المستخدم الخاصة بالمستخدم أو صفحة نقاش المستخدم أو صفحة المساهمات. <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> كان هذا المطلب موجودًا لفترة طويلة في العديد من سياسات ويكيميديا ​​ويكيميديا​​، لكن لم يتم تطبيقه بواسطة برنامج ميدياويكي.<ref>راجع الأمثلة المدرجة في [[phab:T237700|T237700]].</ref> ===منع التعويضات المتداخلة "nested" في التوقيع=== {{Tracked|T230652}} استخدام ''بعض'' لعلامات [[subst:]] والتيلدا سيكون أيضًا غير مسموح به في التوقيعات. <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} ==الأثر: آثار التغيير== === ما الذي سيحدث للتوقيعات الحالية؟ === لا يزال مسموحًا بأي توقيعات حالية قد تصبح غير صالحة بموجب القواعد الجديدة (''[[:en:Grandfather_clause|جد في]]''). عند عرض تفضيلاتك، سترى رسالة تحذير حول هذا الأمر، وإذا حاولت تغيير التوقيع، فيجب أن يكون التوقيع الجديد صالحًا. ولكن إذا لم تقم بتغييره، فسيستمر استخدام التوقيع القديم غير الصحيح عند التوقيع، وستتمكن من تغيير تفضيلاتك الأخرى دون التأثير عليه. نحن نبحث عن ملاحظات حول ما إذا كنت ترغب في عدم السماح بالتوقيعات غير الصالحة. إذا تم رفض التوقيعات غير الصالحة، فسيتم إدراج التوقيع الافتراضي عندما يوقع المستخدمون المتأثرون تعليقاتهم، حتى يصححوا توقيعاتهم الشخصية. === متى سيجري تنفيذ هذه التغييرات؟ === يرجى التعليق قبل 31 مارس 2020. سيتخذ فريق التحرير قرارات بشأن هذا المشروع في أوائل أبريل. سيتم نشر النتائج على صفحة الحديث. إذا لم يتم تحديد أي عقبات، فلن يحدث هذا التغيير في موعد لا يتجاوز أبريل 2020. ويمكن تأجيل هذا التاريخ إذا احتاج الفريق إلى تنفيذ تغييرات كبيرة نتيجة لملاحظاتك. === كيف سنعرف بحدوث التغييرات؟=== سنقوم بتضمين إشعار آخر في [[m:Tech/News]] عندما يكون هذا التغيير على وشك أن يتم نشره. === كيف تبدو أخطاء التحقق من التوقيع؟ === تتضمن أخطاء HTML/lint ارتباطات إلى الوثائق الموجودة حول أخطاء النسالة، مثل [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]]، وزرًا لتمييز الجزء الإشكالي من التوقيع. تتضمن أخطاء الارتباط المطلوبة أمثلة على صيغة نص ويكي لاستخدامها. <gallery mode="packed" caption="أمثلة للأخطاء:"> File:MediaWiki preferences - existing user signature invalid.png|يظهر التحذير عندما يكون توقيع المستخدم الحالي غير صالح (به أخطاء النسالة). File:MediaWiki preferences - new user signature invalid 1.png|يظهر الخطأ عندما يكون توقيع المستخدم الجديد غير صالح (به خطأ نسبي). File:MediaWiki preferences - new user signature invalid 2.png|يظهر الخطأ عندما يكون توقيع المستخدم الجديد غير صالح (لا يحتوي على ارتباط مطلوب). </gallery> == النتائج == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> تم قبول الاقتراح إلى حد كبير. استجابة لتعليقات المتطوعين، تم إجراء بعض التغييرات الصغيرة وتم توضيح بعض النقاط. # تم إيقاف بعض تعبيرات HTML غير المناسبة وبعض أخطاء [[mw:Help:Extension:Linter|لنت]] #:سيتم تقليل نطاق هذه التغييرات. التعبيرات [[Special:LintErrors/misnested-tag|المتداخلة]] و [[Special:LintErrors/stripped-tag|stripped]] سيجري رفضها. بعض الأخطاء قليلة الأهمية يمكن قبولها. خاصة HTML tags مثل {{tag|tt}} و {{tag|font}} لن يجري منعها هذه المرة. لا يخل هذا القرار بأي قرار مستقبلي بشأن إزالة علامات HTML القديمة هذه أو ضد إزالتها. # تتطلب رابطًا لصفحة المستخدم أو صفحة النقاش أو المساهمات #:سيجري تنفيذه كما كان مخطط له في الأصل. #:للتوضيح، يجب أن يكون هناك رابط مباشر محلي واحد على الأقل (وليس عن طريق تحويلة، على سبيل المثال من اسم المستخدم القديم) إلى إحدى تلك الصفحات. وبالتالي، فإن توقيعًا مثل <code><nowiki>[[مستخدم:مثال|مثال]] ([[m:نقاش المستخدم:مثال]])</nowiki></code> سيكون مقبولًا (رابط واحد محلي، رابط واحد إلى ويكي أخرى)، ولكن توقيعًا يتضمن <em>فقط</em> روابط إلى ويكي أخرى أو <em>فقط</em> تحويلة من اسم مستخدم سابق لن يكون مقبولًا. وهذا لأسباب تقنية. # منع التعويضات المتداخلة "nested" في التوقيع #:سيجري تنفيذه كما كان مخطط له في الأصل. طريقة تنفيذ هذا التغيير: * {{done}} سيوضع إعلان عام في [[m:Tech/News|Tech News]] يوضح وقت تنفيذ المتطلبات الجديدة. * {{done}} بمجرد إجراء تغيير البرنامج على الخوادم، لن يتمكن المستخدمون بعدها من حفظ التوقيعات المخصصة غير الصالحة. ومع ذلك، ستبقى التوقيعات الموجودة. * {{in progress}} سيتم تشجيع المحررين النشطين الذين لهم توقيعات غير صالحة على تغيير توقيعاتهم. من المحتمل أن تستغرق هذه العملية بضعة أشهر. * في النهاية، يجب أن تتوافق جميع التوقيعات. إذا لم يقم المحررون بتصحيح التوقيعات المخصصة الخاصة بهم، فسوف يتوقف عمل التوقيعات المخصصة الخاصة بهم، وسيظهر التوقيع الافتراضي بدلاً من ذلك. ستتمكن مواقع ويكي التابعة لجهات خارجية من تمكين هذا التغيير يدويًا. <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == ملاحظات == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] ndax5oqw2vbcbmd7dn79reg0mi2eped 5386358 5386342 2022-07-28T13:23:14Z Shirayuki 472859 update wikitext text/x-wiki <languages/> كثير من الويكيات بها متطلبات لتخصيص التوقيع. يبحث [[Special:MyLanguage/Editing team|فريق التحرير]] لتشفير بعض هذه المتطلبات في برنامج ويكيبيديا. سيسهل ذلك [[mw:Talk pages project/replying|الرد على تعليقات محددة في صفحات النقاش]] واستخدام بعض الأدوات الأخرى. ستجد تفاصيل أكثر عما سيجري، ولماذا، أدناه: * ما التغذية الخلفية (الآراء) التي يريدها الفريق: '''[[#Input: your feedback|أدخل: تغذيتك الخلفية (رأيك)]]''' * لماذا يجرى تنفيذ هذا التغيير: '''[[#Background: why this change?|خلفية: لماذا هذا التغيير؟]]''' * ما هو التغيير المقترح؟ '''[[#Proposal: signature validation requirements|مقترح: متطلبات التحقق من صحة التوقيع]]''' * كيف ستؤثر هذه التغييرات عليك: '''[[#Impact: effects of change|الأثر: آثار التغيير]]''' __TOC__ {{anchor|Input: your feedback}} ==أدخل: تغذيتك الخلفية (رأيك)== يحتاج الفريق لتعليقاتكم حول هذا المقترح. من فضلك اكتب تعليقك حول هذه الأسئلة في [[Talk:New requirements for user signatures|'''صفحة النقاش''']]: # '''هل تؤدي عمليات التحقق من صحة التوقيع هذه إلى حدوث أي مشاكل في الويكي الخاص بك؟''' # '''ما الذي يجب أن يكون الفريق على دراية به قبل إجراء هذا التغيير؟''' # '''ما الذي يجب فعله بشأن التوقيعات الحالية التي لا تتوافق مع المتطلبات الجديدة؟''' <em>على سبيل المثال ، هل يجب منعها؟</em> <em>من فضلك لا تتقيد بالأسئلة أعلاه. يريد الفريق سماع أي تعليقات يمكنك إضافتها.</em> {{anchor|Background: why this change?}} ==خلفية: لماذا هذا التغيير؟== في 2019، قام متطوعون من [[mw:Talk pages consultation 2019/Participant group sign-up|20 مشروع ويكيميديا ومجموعات المستخدمين]] مع عاملين من مؤسسة ويكيميديا بالمشاركة في [[mw:Talk_pages_consultation_2019|نقاش للتشاور]]. كان ذلك محاولة لتحديد أدوات أفضل للتواصل على الويكي. كان أحد مخرجات هذا التشاور [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|طلب لطريقة أسهل للرد على تعليقات محددة]] على صفحات النقاش. لجعل [[mw:Talk_pages_project/replying|هذه الخاصية]] تعمل جيدا، يحتاج البرنامج إلى أن تكون التوقيعات "قابلة للقراءة آليًا"، حتى يتمكن من الكشف بشكل موثوق عن تعليقات المستخدمين والسماح بالرد عليها. كانت المشكلة هي أنه في حين أن العديد من مواقع الويكي لديها بالفعل متطلبات التوقيع اللازمة، فإن هذه المتطلبات ليست مدرجة في البرنامج نفسه. وهذا يزيد من احتمالات قيام شخص ما بتعيين توقيع يخالف اصطلاحات الويكي ويحتمل أن يزيد من صعوبة مشاركة الأشخاص في المحادثات. سيؤدي هذا التناسق الإضافي في تنسيق التوقيعات إلى تحسين الميزات الحالية، مثل [[mw:Help:Notifications/Types#Mentions|إعلام "التنبيهات"]]، التي يتم إرسالها فقط إذا كان من الممكن الكشف عن التوقيع في تعديلك. {{anchor|Proposal: signature validation requirements}} ==مقترح: متطلبات التحقق من صحة التوقيع== <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' إذا لم يتم تحديد عوائق كبيرة ، فقد يحدث هذا التغيير في أبريل 2020. إذا كان الفريق بحاجة إلى إجراء تغييرات كبيرة نتيجة لتعليقاتكم، فسيستغرق الأمر وقتًا أطول. الاختبارات الثلاثة المقترحة موضحة في هذا القسم. سيتم تطبيق هذه على توقيعات المستخدم في التفضيلات عندما يقوم المستخدم بحفظ توقيع معدل. {{Highlight|1=<big>وفق اقتراح فريق التحرير "لن تتأثر التوقيعات الحالية".</big>|color=yellow}} ===تم إيقاف بعض تعبيرات HTML غير المناسبة وبعض أخطاء [[mw:Help:Extension:Linter|لنت]]=== {{Tracked|T140606}} أهم الأمور هو أن هذا التغيير قد ينتج عنه منع وسوم التنسيق غير المغلقة، مثل {{tag|i|open}} أو ما يقابله في ترميز نصوص الويكي، <code><nowiki>''</nowiki></code>، دون وجود وسم إغلاق ملائم (في هذه الحالة هو {{tag|i|close}} أو <code><nowiki>''</nowiki></code> بالترتيب). قد تؤثر التوقيعات التي تحتوي على ترميز غير صالح على كامل صفحة النقاش، حينما يستمر التنسيق نحو التعليقات التالية. كما أن التحقق يحدد أيضا [[Special:LintErrors/misnested-tag|الوسوم المدمجة خطأ]]، مثل <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (سواء كان ذلك من أجل <code>i</code> أو من أجل كلا من <code>b</code> يجب أن تكون الوسوم في الخارج)، وكذلك [[Special:LintErrors/stripped-tag|الوسوم الناقصة]] أي تلك الوسوم الختامية التي لا يوجد لها وسم افتتاحي (نقيض «وسوم التنسيق غير المغلقة» المذكورة سالفا). سيتم أيضًا رفض التوقيعات التي تحتوي على بعض المشكلات الأقل خطورة، على سبيل المثال، علامات HTML القديمة مثل {{tag|tt}} و{{tag|font}}. في حين أن هذه لا تسبب مشاكل فورية، فإن القيام بذلك من شأنه أن يمنع انتشار التعليمات البرمجية القديمة إلى صفحات ويكي الجديدة، وهو أمر مزعج للمحررين الذين يقومون بتنظيف أخطاء Linter. تتوفر قائمة كاملة بميزات بناء الجملة التي لن يُسمح بها، جنبًا إلى جنب مع روابط للصفحات التي تشرح كيفية تحديث أو إصلاح التعليمات البرمجية بأخطاء Linter، على [[mw:Help:Extension:Linter#Documentation of lint issues|هذا العنوان]]. كان من المفترض بالفعل أن يتم منع علامات التنسيق غير المغلقة بواسطة البرنامج، ولكن نظرًا لقيود محلل نص ويكي نص الحالي، فقد نجح هذا فقط في بعض الحالات. أصبح الحل الأكثر قوة ممكنًا بفضل [[Parsoid]]. ===تتطلب رابطًا لصفحة المستخدم أو صفحة النقاش أو المساهمات=== {{Tracked|T237700}} لا تعمل الأدوات المختلفة بشكل صحيح عندما لا يحتوي التوقيع على واحد على الأقل من الروابط التالية: رابط إلى صفحة المستخدم الخاصة بالمستخدم أو صفحة نقاش المستخدم أو صفحة المساهمات. <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> كان هذا المطلب موجودًا لفترة طويلة في العديد من سياسات ويكيميديا ​​ويكيميديا​​، لكن لم يتم تطبيقه بواسطة برنامج ميدياويكي.<ref>راجع الأمثلة المدرجة في [[phab:T237700|T237700]].</ref> ===منع التعويضات المتداخلة "nested" في التوقيع=== {{Tracked|T230652}} استخدام ''بعض'' لعلامات [[subst:]] والتيلدا سيكون أيضًا غير مسموح به في التوقيعات. <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} ==الأثر: آثار التغيير== === ما الذي سيحدث للتوقيعات الحالية؟ === لا يزال مسموحًا بأي توقيعات حالية قد تصبح غير صالحة بموجب القواعد الجديدة (''[[:en:Grandfather_clause|جد في]]''). عند عرض تفضيلاتك، سترى رسالة تحذير حول هذا الأمر، وإذا حاولت تغيير التوقيع، فيجب أن يكون التوقيع الجديد صالحًا. ولكن إذا لم تقم بتغييره، فسيستمر استخدام التوقيع القديم غير الصحيح عند التوقيع، وستتمكن من تغيير تفضيلاتك الأخرى دون التأثير عليه. نحن نبحث عن ملاحظات حول ما إذا كنت ترغب في عدم السماح بالتوقيعات غير الصالحة. إذا تم رفض التوقيعات غير الصالحة، فسيتم إدراج التوقيع الافتراضي عندما يوقع المستخدمون المتأثرون تعليقاتهم، حتى يصححوا توقيعاتهم الشخصية. === متى سيجري تنفيذ هذه التغييرات؟ === يرجى التعليق قبل 31 مارس 2020. سيتخذ فريق التحرير قرارات بشأن هذا المشروع في أوائل أبريل. سيتم نشر النتائج على صفحة الحديث. إذا لم يتم تحديد أي عقبات، فلن يحدث هذا التغيير في موعد لا يتجاوز أبريل 2020. ويمكن تأجيل هذا التاريخ إذا احتاج الفريق إلى تنفيذ تغييرات كبيرة نتيجة لملاحظاتك. === كيف سنعرف بحدوث التغييرات؟=== سنقوم بتضمين إشعار آخر في [[m:Tech/News]] عندما يكون هذا التغيير على وشك أن يتم نشره. === كيف تبدو أخطاء التحقق من التوقيع؟ === تتضمن أخطاء HTML/lint ارتباطات إلى الوثائق الموجودة حول أخطاء النسالة، مثل [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]]، وزرًا لتمييز الجزء الإشكالي من التوقيع. تتضمن أخطاء الارتباط المطلوبة أمثلة على صيغة نص ويكي لاستخدامها. <gallery mode="packed" caption="أمثلة للأخطاء:"> File:MediaWiki preferences - existing user signature invalid.png|يظهر التحذير عندما يكون توقيع المستخدم الحالي غير صالح (به أخطاء النسالة). File:MediaWiki preferences - new user signature invalid 1.png|يظهر الخطأ عندما يكون توقيع المستخدم الجديد غير صالح (به خطأ نسبي). File:MediaWiki preferences - new user signature invalid 2.png|يظهر الخطأ عندما يكون توقيع المستخدم الجديد غير صالح (لا يحتوي على ارتباط مطلوب). </gallery> == النتائج == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> تم قبول الاقتراح إلى حد كبير. استجابة لتعليقات المتطوعين، تم إجراء بعض التغييرات الصغيرة وتم توضيح بعض النقاط. # تم إيقاف بعض تعبيرات HTML غير المناسبة وبعض أخطاء [[mw:Help:Extension:Linter|لنت]] #:سيتم تقليل نطاق هذه التغييرات. التعبيرات [[Special:LintErrors/misnested-tag|المتداخلة]] و [[Special:LintErrors/stripped-tag|stripped]] سيجري رفضها. بعض الأخطاء قليلة الأهمية يمكن قبولها. خاصة HTML tags مثل {{tag|tt}} و {{tag|font}} لن يجري منعها هذه المرة. لا يخل هذا القرار بأي قرار مستقبلي بشأن إزالة علامات HTML القديمة هذه أو ضد إزالتها. # تتطلب رابطًا لصفحة المستخدم أو صفحة النقاش أو المساهمات #:سيجري تنفيذه كما كان مخطط له في الأصل. #:للتوضيح، يجب أن يكون هناك رابط مباشر محلي واحد على الأقل (وليس عن طريق تحويلة، على سبيل المثال من اسم المستخدم القديم) إلى إحدى تلك الصفحات. وبالتالي، فإن توقيعًا مثل <code><nowiki>[[مستخدم:مثال|مثال]] ([[m:نقاش المستخدم:مثال]])</nowiki></code> سيكون مقبولًا (رابط واحد محلي، رابط واحد إلى ويكي أخرى)، ولكن توقيعًا يتضمن <em>فقط</em> روابط إلى ويكي أخرى أو <em>فقط</em> تحويلة من اسم مستخدم سابق لن يكون مقبولًا. وهذا لأسباب تقنية. # منع التعويضات المتداخلة "nested" في التوقيع #:سيجري تنفيذه كما كان مخطط له في الأصل. طريقة تنفيذ هذا التغيير: * {{done}} سيوضع إعلان عام في [[m:Tech/News|Tech News]] يوضح وقت تنفيذ المتطلبات الجديدة. * {{done}} بمجرد إجراء تغيير البرنامج على الخوادم، لن يتمكن المستخدمون بعدها من حفظ التوقيعات المخصصة غير الصالحة. ومع ذلك، ستبقى التوقيعات الموجودة. * {{in progress}} سيتم تشجيع المحررين النشطين الذين لهم توقيعات غير صالحة على تغيير توقيعاتهم. من المحتمل أن تستغرق هذه العملية بضعة أشهر. * في النهاية، يجب أن تتوافق جميع التوقيعات. إذا لم يقم المحررون بتصحيح التوقيعات المخصصة الخاصة بهم، فسوف يتوقف عمل التوقيعات المخصصة الخاصة بهم، وسيظهر التوقيع الافتراضي بدلاً من ذلك. ستتمكن مواقع ويكي التابعة لجهات خارجية من تمكين هذا التغيير يدويًا. <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == ملاحظات == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] o63hxqn3iz0ds2dyw1c0285ffcfxpe2 Translations:New requirements for user signatures/2/ar 1198 1166012 5386357 3989970 2022-07-28T13:23:13Z Shirayuki 472859 update wikitext text/x-wiki يبحث [[$1|فريق التحرير]] لتشفير بعض هذه المتطلبات في برنامج ويكيبيديا. plqvehaljadawc4od4ufomkbyacn4vl Template:InstallationNav/sv 10 1169231 5387210 5384797 2022-07-28T21:17:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=Anpassa}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] 1qd92bkmsknsitxkqeszdd6tt8kj7m9 Extension:FileImporter/Data/gl.wikipedia 102 1176956 5387513 4876986 2022-07-28T23:58:39Z Estevoaei 44695 /* Good */ wikitext text/x-wiki *en: This data is used by FileImporter to transfer images from [[:gl:|Galician Wikipedia]] to Commons. *gl: Estes datos son utilizados por CommonsHelper2 para a transferencia de ficheiros da [[:gl:|Galipedia]] a Commons. == Categories == === Bad === The presence of any of these categories should prevent a transfer to Commons. == Templates == === Good === At least one of these templates needs to be present to greenlight transfer to Commons (can be lowercase) * Cc-by * Cc-2.1 * Cc-by-2.0 * Cc-by-2.5 * Cc-by-3.0 * Cc-by-sa * cc-by-sa-1.0 * Cc-by-sa-2.0 * Cc-by-sa-2.1-es * Cc-by-sa-2.5 * Cc-by-sa-2.5-es * Cc-by-sa-2.5,2.0,1.0 * Cc-by-sa-3.0 * Cc-by-sa-3.0,2.5,2.0,1.0 * Cc-by-sa-4.0 * Cc-sa * Cc-zero * CopyrightABr * GFDL-propia * PD-autor * PD-antiga * PD-FLGov * PD-formas simples * PD-ineligible * PD-MNGov * PD-Pre1978 * PD-propia * PD-shape * PD-signature * PD-SpanishGov * PD-text * PD-US * PD-US-patent * PD-USGov * PD-USGov-AID * PD-USGov-Atlas * PD-USGov-CIA * PD-USGov-CIA-WF * PD-USGov-Congress * PD-USGov-Congress-Bio * PD-USGov-DHS * PD-USGov-DHS-CG * PD-USGov-DOC * PD-USGov-DOC-Census * PD-USGov-DOC-NOAA * PD-USGov-DOE * PD-USGov-DOJ * PD-USGov-DOL * PD-USGov-DOT * PD-USGov-DOT-FAA * PD-USGov-EPA * PD-USGov-Education * PD-USGov-FBI * PD-USGov-FDA * PD-USGov-FEMA * PD-USGov-FSA * PD-USGov-HHS * PD-USGov-HHS-CDC * PD-USGov-HHS-NIH * PD-USGov-Interior * PD-USGov-Interior-BLM * PD-USGov-Interior-FWS * PD-USGov-Interior-HABS * PD-USGov-Interior-NPS * PD-USGov-Interior-USBR * PD-USGov-Interior-USGS * PD-USGov-Interior-USGS-Minerals * PD-USGov-Military * PD-USGov-Military * PD-USGov-Military-Air Force * PD-USGov-Military-Air Force Auxiliary * PD-USGov-Military-Air National Guard * PD-USGov-Military-Army * PD-USGov-Military-Army National Guard * PD-USGov-Military-Army-USACE * PD-USGov-Military-Army-USACMH * PD-USGov-Military-Army-USAIOH * PD-USGov-Military-Army-USAMHI * PD-USGov-Military-Award * PD-USGov-Military-Badge * PD-USGov-Military-DVIC * PD-USGov-Military-JCS * PD-USGov-Military-Marines * PD-USGov-Military-Navy * PD-USGov-NASA * PD-USGov-NCBI-scienceprimer * PD-USGov-NRO * PD-USGov-NSA * PD-USGov-NTSB * PD-USGov-OWI * PD-USGov-POTUS * PD-USGov-State * PD-USGov-TVA * PD-USGov-Treasury * PD-USGov-USDA * PD-USGov-USDA-ARS * PD-USGov-USDA-FS * PD-USGov-USDA-NRCS * PD-USGov-VA * PD-USGov-WPA * PD-WorldWind * PD-art-US * attribution * bsd * bsdu * gfdl * gfdl-self * gfdl-self-with-disclaimers * gfdl-user * gfdl-user-w * GFDL-user-w * gfdl-with-disclaimers * gpl * lgpl * money-US * pd-britishgov * pd-nasa * pd-old * pd-pdphoto.org * pd-romaniagov * pd-ru-exempt * pd-self * pd-textlogo * pd-ukgov * pd-us * pd-user * NoRightsReserved * Mover para o Commons * PD-release * PD-porque * SemDireitosReservados * PD-USGov-USGS * Wikipedia-CapturaPantalla * Wikipedia-screenshot === Bad === The presence of any of these templates should prevent a transfer to Commons (can be lowercase) * NoCommons * Do not move to Commons === Remove === These templates will be removed during transfer. * ! * !! * Dated maintenance category * DMC * File other * Move to Commons * Move to wikimedia commons * Movetocommons * Move-to-commons * Mover para o Commons * NoCommons * Rename media * To Commons * Copy to Wikimedia Commons * Non verificada * Usuario:MGA73/Sandbox4 === Transfer === * Use <code>; LOCAL_TEMPLATE : COMMONS_TEMPLATE | COMMONS_PARAMETER=LOCAL_PARAMETER | COMMONS_PARAMETER=LOCAL_PARAMETER </code> and so on * Local parameters can be 1, 2, 3... for unnamed parameters; this will not work for Commons parameters * Prefix commons parameter with "@" to have it language-tagged : <nowiki>{{de|Zeug}}</nowiki> ;Information:Information|@Description=Description|Source=Source|Author=Author|Date=Date|Permission=Permission|other_versions=other_versions ;información:Information|@Description=descrición|Source=fonte|Author=autor|Date=data|Permission=licenza|Other_versions=outras versións ;Self:Self|Author=Autor ;Attribution:Attribution only license ;GFDL ou cc-by-sa-3.0,2.5,2.0,1.0:GFDL|+migration=redundant}}{{cc-by-sa-3.0,2.5,2.0,1.0| ;PD-propia:PD-self ;GFDL-propia:GFDL-self ;FlickrRevisada:Flickrreview}}{{FlickrRevisada| == Information == === Description === Headline of the Description (e.g. Summary): * Summary * Resumo: * Resumo === Licensing === Headline of the Licensing (e.g. Licensing): * Licensing * Licenza: * Licenza == Source wiki info == You can define which template should be added to the file on the source wiki to signal that it has been moved to Commons. This definition is done on [[d:Q5611625|Wikidata]]. Please do not add this info here. 2d6vyo1ec55bz90ikb4eymympe0ceol 5387704 5387513 2022-07-29T06:07:13Z Estevoaei 44695 /* Good */ wikitext text/x-wiki *en: This data is used by FileImporter to transfer images from [[:gl:|Galician Wikipedia]] to Commons. *gl: Estes datos son utilizados por CommonsHelper2 para a transferencia de ficheiros da [[:gl:|Galipedia]] a Commons. == Categories == === Bad === The presence of any of these categories should prevent a transfer to Commons. == Templates == === Good === At least one of these templates needs to be present to greenlight transfer to Commons (can be lowercase) * CapturaPantalla * Cc-by * Cc-2.1 * Cc-by-2.0 * Cc-by-2.5 * Cc-by-3.0 * Cc-by-sa * cc-by-sa-1.0 * Cc-by-sa-2.0 * Cc-by-sa-2.1-es * Cc-by-sa-2.5 * Cc-by-sa-2.5-es * Cc-by-sa-2.5,2.0,1.0 * Cc-by-sa-3.0 * Cc-by-sa-3.0,2.5,2.0,1.0 * Cc-by-sa-4.0 * Cc-sa * Cc-zero * CopyrightABr * GFDL-propia * PD-autor * PD-antiga * PD-FLGov * PD-formas simples * PD-ineligible * PD-MNGov * PD-Pre1978 * PD-propia * PD-shape * PD-signature * PD-SpanishGov * PD-text * PD-US * PD-US-patent * PD-USGov * PD-USGov-AID * PD-USGov-Atlas * PD-USGov-CIA * PD-USGov-CIA-WF * PD-USGov-Congress * PD-USGov-Congress-Bio * PD-USGov-DHS * PD-USGov-DHS-CG * PD-USGov-DOC * PD-USGov-DOC-Census * PD-USGov-DOC-NOAA * PD-USGov-DOE * PD-USGov-DOJ * PD-USGov-DOL * PD-USGov-DOT * PD-USGov-DOT-FAA * PD-USGov-EPA * PD-USGov-Education * PD-USGov-FBI * PD-USGov-FDA * PD-USGov-FEMA * PD-USGov-FSA * PD-USGov-HHS * PD-USGov-HHS-CDC * PD-USGov-HHS-NIH * PD-USGov-Interior * PD-USGov-Interior-BLM * PD-USGov-Interior-FWS * PD-USGov-Interior-HABS * PD-USGov-Interior-NPS * PD-USGov-Interior-USBR * PD-USGov-Interior-USGS * PD-USGov-Interior-USGS-Minerals * PD-USGov-Military * PD-USGov-Military * PD-USGov-Military-Air Force * PD-USGov-Military-Air Force Auxiliary * PD-USGov-Military-Air National Guard * PD-USGov-Military-Army * PD-USGov-Military-Army National Guard * PD-USGov-Military-Army-USACE * PD-USGov-Military-Army-USACMH * PD-USGov-Military-Army-USAIOH * PD-USGov-Military-Army-USAMHI * PD-USGov-Military-Award * PD-USGov-Military-Badge * PD-USGov-Military-DVIC * PD-USGov-Military-JCS * PD-USGov-Military-Marines * PD-USGov-Military-Navy * PD-USGov-NASA * PD-USGov-NCBI-scienceprimer * PD-USGov-NRO * PD-USGov-NSA * PD-USGov-NTSB * PD-USGov-OWI * PD-USGov-POTUS * PD-USGov-State * PD-USGov-TVA * PD-USGov-Treasury * PD-USGov-USDA * PD-USGov-USDA-ARS * PD-USGov-USDA-FS * PD-USGov-USDA-NRCS * PD-USGov-VA * PD-USGov-WPA * PD-WorldWind * PD-art-US * attribution * bsd * bsdu * gfdl * gfdl-self * gfdl-self-with-disclaimers * gfdl-user * gfdl-user-w * GFDL-user-w * gfdl-with-disclaimers * gpl * lgpl * money-US * pd-britishgov * pd-nasa * pd-old * pd-pdphoto.org * pd-romaniagov * pd-ru-exempt * pd-self * pd-textlogo * pd-ukgov * pd-us * pd-user * NoRightsReserved * Mover para o Commons * PD-release * PD-porque * SemDireitosReservados * PD-USGov-USGS * Wikipedia-CapturaPantalla * Wikipedia-screenshot === Bad === The presence of any of these templates should prevent a transfer to Commons (can be lowercase) * NoCommons * Do not move to Commons === Remove === These templates will be removed during transfer. * ! * !! * Dated maintenance category * DMC * File other * Move to Commons * Move to wikimedia commons * Movetocommons * Move-to-commons * Mover para o Commons * NoCommons * Rename media * To Commons * Copy to Wikimedia Commons * Non verificada * Usuario:MGA73/Sandbox4 === Transfer === * Use <code>; LOCAL_TEMPLATE : COMMONS_TEMPLATE | COMMONS_PARAMETER=LOCAL_PARAMETER | COMMONS_PARAMETER=LOCAL_PARAMETER </code> and so on * Local parameters can be 1, 2, 3... for unnamed parameters; this will not work for Commons parameters * Prefix commons parameter with "@" to have it language-tagged : <nowiki>{{de|Zeug}}</nowiki> ;Information:Information|@Description=Description|Source=Source|Author=Author|Date=Date|Permission=Permission|other_versions=other_versions ;información:Information|@Description=descrición|Source=fonte|Author=autor|Date=data|Permission=licenza|Other_versions=outras versións ;Self:Self|Author=Autor ;Attribution:Attribution only license ;GFDL ou cc-by-sa-3.0,2.5,2.0,1.0:GFDL|+migration=redundant}}{{cc-by-sa-3.0,2.5,2.0,1.0| ;PD-propia:PD-self ;GFDL-propia:GFDL-self ;FlickrRevisada:Flickrreview}}{{FlickrRevisada| == Information == === Description === Headline of the Description (e.g. Summary): * Summary * Resumo: * Resumo === Licensing === Headline of the Licensing (e.g. Licensing): * Licensing * Licenza: * Licenza == Source wiki info == You can define which template should be added to the file on the source wiki to signal that it has been moved to Commons. This definition is done on [[d:Q5611625|Wikidata]]. Please do not add this info here. dbg7byp55d9j4ixirhycnm8qrhjo2ef 5387721 5387704 2022-07-29T06:18:29Z Estevoaei 44695 /* Good */ wikitext text/x-wiki *en: This data is used by FileImporter to transfer images from [[:gl:|Galician Wikipedia]] to Commons. *gl: Estes datos son utilizados por CommonsHelper2 para a transferencia de ficheiros da [[:gl:|Galipedia]] a Commons. == Categories == === Bad === The presence of any of these categories should prevent a transfer to Commons. == Templates == === Good === At least one of these templates needs to be present to greenlight transfer to Commons (can be lowercase) * CapturaPantalla * Cc-by * Cc-2.1 * Cc-by-2.0 * Cc-by-2.5 * Cc-by-3.0 * Cc-by-sa * cc-by-sa-1.0 * Cc-by-sa-2.0 * Cc-by-sa-2.1-es * Cc-by-sa-2.5 * Cc-by-sa-2.5-es * Cc-by-sa-2.5,2.0,1.0 * Cc-by-sa-3.0 * Cc-by-sa-3.0,2.5,2.0,1.0 * Cc-by-sa-4.0 * Cc-sa * Cc-zero * CopyrightABr * FreeScreenshot * GFDL-propia * PD-autor * PD-antiga * PD-FLGov * PD-formas simples * PD-ineligible * PD-MNGov * PD-Pre1978 * PD-propia * PD-shape * PD-signature * PD-SpanishGov * PD-text * PD-US * PD-US-patent * PD-USGov * PD-USGov-AID * PD-USGov-Atlas * PD-USGov-CIA * PD-USGov-CIA-WF * PD-USGov-Congress * PD-USGov-Congress-Bio * PD-USGov-DHS * PD-USGov-DHS-CG * PD-USGov-DOC * PD-USGov-DOC-Census * PD-USGov-DOC-NOAA * PD-USGov-DOE * PD-USGov-DOJ * PD-USGov-DOL * PD-USGov-DOT * PD-USGov-DOT-FAA * PD-USGov-EPA * PD-USGov-Education * PD-USGov-FBI * PD-USGov-FDA * PD-USGov-FEMA * PD-USGov-FSA * PD-USGov-HHS * PD-USGov-HHS-CDC * PD-USGov-HHS-NIH * PD-USGov-Interior * PD-USGov-Interior-BLM * PD-USGov-Interior-FWS * PD-USGov-Interior-HABS * PD-USGov-Interior-NPS * PD-USGov-Interior-USBR * PD-USGov-Interior-USGS * PD-USGov-Interior-USGS-Minerals * PD-USGov-Military * PD-USGov-Military * PD-USGov-Military-Air Force * PD-USGov-Military-Air Force Auxiliary * PD-USGov-Military-Air National Guard * PD-USGov-Military-Army * PD-USGov-Military-Army National Guard * PD-USGov-Military-Army-USACE * PD-USGov-Military-Army-USACMH * PD-USGov-Military-Army-USAIOH * PD-USGov-Military-Army-USAMHI * PD-USGov-Military-Award * PD-USGov-Military-Badge * PD-USGov-Military-DVIC * PD-USGov-Military-JCS * PD-USGov-Military-Marines * PD-USGov-Military-Navy * PD-USGov-NASA * PD-USGov-NCBI-scienceprimer * PD-USGov-NRO * PD-USGov-NSA * PD-USGov-NTSB * PD-USGov-OWI * PD-USGov-POTUS * PD-USGov-State * PD-USGov-TVA * PD-USGov-Treasury * PD-USGov-USDA * PD-USGov-USDA-ARS * PD-USGov-USDA-FS * PD-USGov-USDA-NRCS * PD-USGov-VA * PD-USGov-WPA * PD-WorldWind * PD-art-US * attribution * bsd * bsdu * gfdl * gfdl-self * gfdl-self-with-disclaimers * gfdl-user * gfdl-user-w * GFDL-user-w * gfdl-with-disclaimers * gpl * lgpl * money-US * pd-britishgov * pd-nasa * pd-old * pd-pdphoto.org * pd-romaniagov * pd-ru-exempt * pd-self * pd-textlogo * pd-ukgov * pd-us * pd-user * NoRightsReserved * Mover para o Commons * PD-release * PD-porque * SemDireitosReservados * PD-USGov-USGS * Wikipedia-CapturaPantalla * Wikipedia-screenshot === Bad === The presence of any of these templates should prevent a transfer to Commons (can be lowercase) * NoCommons * Do not move to Commons === Remove === These templates will be removed during transfer. * ! * !! * Dated maintenance category * DMC * File other * Move to Commons * Move to wikimedia commons * Movetocommons * Move-to-commons * Mover para o Commons * NoCommons * Rename media * To Commons * Copy to Wikimedia Commons * Non verificada * Usuario:MGA73/Sandbox4 === Transfer === * Use <code>; LOCAL_TEMPLATE : COMMONS_TEMPLATE | COMMONS_PARAMETER=LOCAL_PARAMETER | COMMONS_PARAMETER=LOCAL_PARAMETER </code> and so on * Local parameters can be 1, 2, 3... for unnamed parameters; this will not work for Commons parameters * Prefix commons parameter with "@" to have it language-tagged : <nowiki>{{de|Zeug}}</nowiki> ;Information:Information|@Description=Description|Source=Source|Author=Author|Date=Date|Permission=Permission|other_versions=other_versions ;información:Information|@Description=descrición|Source=fonte|Author=autor|Date=data|Permission=licenza|Other_versions=outras versións ;Self:Self|Author=Autor ;Attribution:Attribution only license ;GFDL ou cc-by-sa-3.0,2.5,2.0,1.0:GFDL|+migration=redundant}}{{cc-by-sa-3.0,2.5,2.0,1.0| ;PD-propia:PD-self ;GFDL-propia:GFDL-self ;FlickrRevisada:Flickrreview}}{{FlickrRevisada| == Information == === Description === Headline of the Description (e.g. Summary): * Summary * Resumo: * Resumo === Licensing === Headline of the Licensing (e.g. Licensing): * Licensing * Licenza: * Licenza == Source wiki info == You can define which template should be added to the file on the source wiki to signal that it has been moved to Commons. This definition is done on [[d:Q5611625|Wikidata]]. Please do not add this info here. 7voyeu65jdnq5qt2k0c9kzxe1ngzwx8 5387722 5387721 2022-07-29T06:18:51Z Estevoaei 44695 /* Good */ wikitext text/x-wiki *en: This data is used by FileImporter to transfer images from [[:gl:|Galician Wikipedia]] to Commons. *gl: Estes datos son utilizados por CommonsHelper2 para a transferencia de ficheiros da [[:gl:|Galipedia]] a Commons. == Categories == === Bad === The presence of any of these categories should prevent a transfer to Commons. == Templates == === Good === At least one of these templates needs to be present to greenlight transfer to Commons (can be lowercase) * CapturaPantalla * Cc-by * Cc-2.1 * Cc-by-2.0 * Cc-by-2.5 * Cc-by-3.0 * Cc-by-sa * cc-by-sa-1.0 * Cc-by-sa-2.0 * Cc-by-sa-2.1-es * Cc-by-sa-2.5 * Cc-by-sa-2.5-es * Cc-by-sa-2.5,2.0,1.0 * Cc-by-sa-3.0 * Cc-by-sa-3.0,2.5,2.0,1.0 * Cc-by-sa-4.0 * Cc-sa * Cc-zero * CopyrightABr * Free screenshot * GFDL-propia * PD-autor * PD-antiga * PD-FLGov * PD-formas simples * PD-ineligible * PD-MNGov * PD-Pre1978 * PD-propia * PD-shape * PD-signature * PD-SpanishGov * PD-text * PD-US * PD-US-patent * PD-USGov * PD-USGov-AID * PD-USGov-Atlas * PD-USGov-CIA * PD-USGov-CIA-WF * PD-USGov-Congress * PD-USGov-Congress-Bio * PD-USGov-DHS * PD-USGov-DHS-CG * PD-USGov-DOC * PD-USGov-DOC-Census * PD-USGov-DOC-NOAA * PD-USGov-DOE * PD-USGov-DOJ * PD-USGov-DOL * PD-USGov-DOT * PD-USGov-DOT-FAA * PD-USGov-EPA * PD-USGov-Education * PD-USGov-FBI * PD-USGov-FDA * PD-USGov-FEMA * PD-USGov-FSA * PD-USGov-HHS * PD-USGov-HHS-CDC * PD-USGov-HHS-NIH * PD-USGov-Interior * PD-USGov-Interior-BLM * PD-USGov-Interior-FWS * PD-USGov-Interior-HABS * PD-USGov-Interior-NPS * PD-USGov-Interior-USBR * PD-USGov-Interior-USGS * PD-USGov-Interior-USGS-Minerals * PD-USGov-Military * PD-USGov-Military * PD-USGov-Military-Air Force * PD-USGov-Military-Air Force Auxiliary * PD-USGov-Military-Air National Guard * PD-USGov-Military-Army * PD-USGov-Military-Army National Guard * PD-USGov-Military-Army-USACE * PD-USGov-Military-Army-USACMH * PD-USGov-Military-Army-USAIOH * PD-USGov-Military-Army-USAMHI * PD-USGov-Military-Award * PD-USGov-Military-Badge * PD-USGov-Military-DVIC * PD-USGov-Military-JCS * PD-USGov-Military-Marines * PD-USGov-Military-Navy * PD-USGov-NASA * PD-USGov-NCBI-scienceprimer * PD-USGov-NRO * PD-USGov-NSA * PD-USGov-NTSB * PD-USGov-OWI * PD-USGov-POTUS * PD-USGov-State * PD-USGov-TVA * PD-USGov-Treasury * PD-USGov-USDA * PD-USGov-USDA-ARS * PD-USGov-USDA-FS * PD-USGov-USDA-NRCS * PD-USGov-VA * PD-USGov-WPA * PD-WorldWind * PD-art-US * attribution * bsd * bsdu * gfdl * gfdl-self * gfdl-self-with-disclaimers * gfdl-user * gfdl-user-w * GFDL-user-w * gfdl-with-disclaimers * gpl * lgpl * money-US * pd-britishgov * pd-nasa * pd-old * pd-pdphoto.org * pd-romaniagov * pd-ru-exempt * pd-self * pd-textlogo * pd-ukgov * pd-us * pd-user * NoRightsReserved * Mover para o Commons * PD-release * PD-porque * SemDireitosReservados * PD-USGov-USGS * Wikipedia-CapturaPantalla * Wikipedia-screenshot === Bad === The presence of any of these templates should prevent a transfer to Commons (can be lowercase) * NoCommons * Do not move to Commons === Remove === These templates will be removed during transfer. * ! * !! * Dated maintenance category * DMC * File other * Move to Commons * Move to wikimedia commons * Movetocommons * Move-to-commons * Mover para o Commons * NoCommons * Rename media * To Commons * Copy to Wikimedia Commons * Non verificada * Usuario:MGA73/Sandbox4 === Transfer === * Use <code>; LOCAL_TEMPLATE : COMMONS_TEMPLATE | COMMONS_PARAMETER=LOCAL_PARAMETER | COMMONS_PARAMETER=LOCAL_PARAMETER </code> and so on * Local parameters can be 1, 2, 3... for unnamed parameters; this will not work for Commons parameters * Prefix commons parameter with "@" to have it language-tagged : <nowiki>{{de|Zeug}}</nowiki> ;Information:Information|@Description=Description|Source=Source|Author=Author|Date=Date|Permission=Permission|other_versions=other_versions ;información:Information|@Description=descrición|Source=fonte|Author=autor|Date=data|Permission=licenza|Other_versions=outras versións ;Self:Self|Author=Autor ;Attribution:Attribution only license ;GFDL ou cc-by-sa-3.0,2.5,2.0,1.0:GFDL|+migration=redundant}}{{cc-by-sa-3.0,2.5,2.0,1.0| ;PD-propia:PD-self ;GFDL-propia:GFDL-self ;FlickrRevisada:Flickrreview}}{{FlickrRevisada| == Information == === Description === Headline of the Description (e.g. Summary): * Summary * Resumo: * Resumo === Licensing === Headline of the Licensing (e.g. Licensing): * Licensing * Licenza: * Licenza == Source wiki info == You can define which template should be added to the file on the source wiki to signal that it has been moved to Commons. This definition is done on [[d:Q5611625|Wikidata]]. Please do not add this info here. 2j9wchv95wqzh6kh5ro3098qzzhfa03 Manual:Combating spam/de-formal 100 1183953 5387472 5255694 2022-07-28T22:40:15Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Wie alle aktuellen dynamischen Websites sind Wikis ein häufiges Ziel für Spammer, die Produkte oder Websites bewerben möchten. MediaWiki bietet eine Reihe von Funktionen zur [[Special:MyLanguage/Manual:Combating vandalism|Bekämpfung von Vandalismus im Allgemeinen]]. Auf dieser Seite beschäftigen wir uns speziell mit [[m:Wiki spam|Wiki-Spam]]. == Überblick == Übliche Tools zur Bekämpfung von Wiki-Spam fallen normalerweise in folgende Kategorien: * Erfordern einer Anmeldung und/oder eines CAPTCHA für bestimmte Vorgänge, z. B. Bearbeitungen, Hinzufügen externer Links oder Erstellen neuer Benutzer * Blockieren von Bearbeitungen von bekannten IP-Adressen auf der schwarzen Liste oder IPs, auf denen Proxys ausgeführt werden * Blockieren von Bearbeitungen, die bestimmte unerwünschte Schlüsselwörter oder externe Links hinzufügen * Blockieren von bestimmten Benutzernamen und Seitentiteln, die häufig von Spambots verwendet werden * Blockieren von Bearbeitungen durch neue oder anonyme Benutzer für bestimmte, häufig anvisierte Seiten * Whitelisting von bekannten Redakteuren (wie Admins, regelmäßige Mitwirkende) und Einschränkungen für neue oder anonyme Benutzer * Bereinigungsskripte oder Massenlöschung ({{ll|Extension:Nuke}}) vorhandener Posts von kürzlich gesperrten Spambots Normalerweise wird eine Kombination verschiedener Methoden verwendet, um die Anzahl der Spam-, Roboter- und Open-Proxy-Bearbeitungen so gering wie möglich zu halten und gleichzeitig die Anzahl der Störungen zu begrenzen, die für rechtmäßige Benutzer der Website verursacht werden. Beachten Sie, dass viele dieser Funktionen standardmäßig nicht aktiviert sind. Wenn Sie eine MediaWiki-Installation auf deinem Server/Host ausführen, können nur Sie die erforderlichen Konfigurationsänderungen vornehmen! Bitten Sie Ihre Benutzer auf jeden Fall, zu helfen, [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|auf Wiki-Spam zu achten]] (und tun Sie dies selbst). Es hilft, die Messlatte etwas höher zu legen. <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> Das regelmäßige Überprüfen von "{{int|recentchanges}}" ([[Special:RecentChanges]]) ist eine effektive Maßnahme. == Schnellste Lösungen zum Ausprobieren == Spam zu bekämpfen sollte nicht zu schwer sein. Wenn Sie Spam schnell und drastisch reduzieren möchten, versuchen Sie zunächst diese Schritte. * Installieren Sie die [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]]-Erweiterung, um bekannte Spammer-IPs zu blockieren. * Installieren und richten Sie grundlegende Antivandalismus-Erweiterungen ein (bereits in den [[Special:MyLanguage/Download|letzten Versionen]] eingebaut), insbesondere {{ll|Extension:ConfirmEdit}}. <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam setup basics== </div> {{anchor|CAPTCHA}} === CAPTCHA === <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> * alle Bearbeitungen * Bearbeitungen, die neue, unerkannte externe Links hinzufügen * Benutzerregistrierung <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} ===Schutz einzelner Seiten=== <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. === Missbrauchsfilter === <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> === Offene Proxies === <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Apache configuration changes === </div> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> == Weitere Ideen == <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==See also== </div> *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. === Erweiterungen === *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users === Einstellungen === * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} === Weblinks === * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] bl4v408x9pbsspp7d43penuetfce2pi Wikimedia Product/uz 0 1194160 5387598 5358216 2022-07-29T03:26:07Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Xissadorlar</span>]] * [[Readers|<span style="color:#2aa198">O'quvchilar</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == Mahsulot Haqida == * [[Special:MyLanguage/Product Principles|Mahsulot Tamoyillari]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|Texnik Hamkorlik Bo'yicha Qo'llanma]]) * [[Special:MyLanguage/Design/Statement of purpose|Maqsadni Loyihalashtirish Bayonoti]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == Maqsadlar == {|class="wikitable" |- !scope="row"| 2019-2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: Iyul-Sentyabr 2019]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: Oktyabr-Dekabr 2019]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: Yanvar-Mart 2020]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: Aprel-Iyun 2020]]--> |- !scope="row"| 2018-2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: Iyul-Sentyabr 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: Oktyabr-Dekabr 2018]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: Yanvar-Mart 2019]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: Aprel-Iyun 2019]] |- !scope="row"| 2017-2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: Iyul-Sentyabr 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: Oktyabr-Dekabr 2017]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: Yanvar-Mart 2018]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: Aprel-Iyun 2018]] |- !scope="row"| 2016-2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: Iyul-Sentyabr 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: Oktyabr-Dekabr 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: Yanvar-Mart 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: Aprel-Iyun 2017]] |- !scope="row"| 2015-2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: Iyul-Sentyabr 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: Oktyabr-Dekabr 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: Yanvar-Mart 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: Aprel-Iyun 2016]] |} == Yillik yo'l xaritasi == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|2018-2019 yilgi mahsulot uchun yillik reja]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|2017-2018 yilgi mahsulot uchun yillik reja]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|2016-2017 yilgi mahsulot uchun yillik reja]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|2016 yilgi mahsulot haqida qisqacha ma'lumot]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|2015 yilgi mahsulot va texnologiyalar sharhi]] [[Category:WMF Projects{{#translation:}}]] hiy2ozq68wv7ilhhxctfgzwp63qfzfs Wikimedia Performance Team/Multi-DC MediaWiki 0 1211094 5386610 5358468 2022-07-28T16:31:58Z Krinkle 135822 /* CentralAuth storage */ wikitext text/x-wiki {{Tracked|T270223}} '''Multi-DC MediaWiki''' (also known as, ''Active-active MediaWiki'') is a cross-cutting project driven by the [[Wikimedia Performance Team|Performance Team]] to give MediaWiki the ability to serve read requests from multiple datacenters. Currently, MediaWiki is deployed at Wikimedia Foundation to serve requests from the primary datacenter only. Having MediaWiki deployed and actively serving from two or more datacenters during normal operations, ensures higher resilience in case of a datacenter failure, removes most switchover costs and complexity, and eases regular maintenance. It also brings a promise of future performance potential, and has throughout its developed brought about various performance improvements due to restructuring how business logic is implemented and naturally requiring more async or event-driven solutions. == Remaining work == The project was formalised via the [[Requests for comment/Multi datacenter strategy for MediaWiki|Multi-DC strategy RFC]] in 2015. Since then, Aaron Schulz has driven the effort of improving, upgrading, and porting the various production systems around MediaWiki to work in an active-active context with multiple datacenters serving MediaWiki web requests. You can see [[phab:T88445|the history of subtasks on Phabricator]]. This document focuses on remaining work left as of December 2020 – the major blockers left before enabling the active-active serving of MediaWiki. === ChronologyProtector === [[Manual:ChronologyProtector|ChronologyProtector]] is the system ensuring that editors see the result of their own actions in subsequent interactions. The remaining work is deciding where and how to store the data going forward, to deploy any infra and software changes as needed, and to enable these. * Lead: Performance Team (Timo). * In collaboration with [[Wikimedia Site Reliability Engineering#Service Operations|SRE Service Operations]]. * Task: [[phab:T254634|T254634]] Updates: * [[phab:T254634#6433868|September 2020]]: an architectural solution has been decided on and the Performance Team, in collaboration with [[Wikimedia Site Reliability Engineering#Service Operations|Service Operations]], will migrate ChronologyProtector to a new data storage (either Memcached or Redis), during Oct-Dec 2020 (FY 2020-2021 Q2). *[[phab:T254634#6832141|February 2021]]: code simplification and backend configuration for Multi-DC ChronologyProtector have been implemented and deployed to production for all wikis. *March 2021: Documented [https://doc.wikimedia.org/mediawiki-core/master/php/classWikimedia_1_1Rdbms_1_1ChronologyProtector.html#ChronologyProtector-storage-requirements CP store requirements] for third-parties. *March 2021: Task closed. *{{Done}} === Session storage === The session store holds temporary data required for authenticating and authorization procedures such as logging in, creating accounts, and security checks before actions such as editing pages. The older data storage system has various short-comings beyond mere incompatibility with a multi-DC operation. Even in our current single-DC deployment the annual switchovers are cumbersome, and a replacement has been underway for some time. The remaining work is to finish the the data storage migration from Redis (non-replicated) to [[Kask]] (Cassandra-based). * Lead: <s>[[Core Platform Team]] (Eric Evans),</s> Performance Team (Tim, Timo). * Past tasks: [[phab:T206010|RFC T206010]], [[phab:T206016|T206016]]. * Current tasks: [[phab:T270225|T270225]] (core logic). Updates: * 2018-2020 ([[phab:T206016|T206016]]): Develop and deploy Kask, gradually roll out to all Beta and production wikis. * Dec 2020: Performance Team realize that requirements appear unmet, citing multiple unresolved "TODOs" in the code for primary requirements, internally inconsistent claims about service interface. [[phab:T270225|T270225]] * Jan 2021: CPT triages task from Inbox. * Feb 2021: CPT moves task to "''Platform Engineering Roadmap > Later''". * March 2021: Future optimisation identified by Tim (two-level session storage) - [[phab:T277834|T277834]]. * July 2022: Performance take over [[phab:T270225|T270225]] within the limited scope of completing Multi-DC needs. {{To do}}: * Fulfil or explain away the unresolved TODOs at [[phab:T270225|T270225]]. * Straighten out internally inconsistent interface guruntees at [[phab:T270225|T270225]]. === CentralAuth storage === A special kind of session storage for the central login system and cross-wiki "auto login" and "stay logged in" mechanism. The last part of that work, [[phab:T254422|migrating]] [[Extension:CentralAuth|CentralAuth]] sessions, is currently scheduled for completion in Oct-Dec 2020 (2020-2021 Q2). * Lead: <s>[[Core Platform Team]] (Bill Pirkle),</s> Performance Team (Tim, Timo). * Task: [[phab:T267270|T267270]] Updates: * Nov 2020: Initial assessment done by CPT. * Jan 2021: Assessment concluded. * Feb 2021: Assessment re-opened. * Jul 2022: Decided on Kask-sessions (Cassandra) as backend. Should not be separate from core sessions. TTL mismatch considered a bug and also fixed by Tim. [[phab:T313496|T313496]] {{To do}}: * Document CA interface requirements and expectations. === Main Stash store === The [[wikitech:Redis|Redis cluster]] previously used for session storage is also host to other miscellaneous application data through the [[Manual:Caching#Main stash|Main Stash]] interface. This has different needs than session storage which become more prominent in a multi-DC deployment which make it unsuitable for Cassandra/Kask. The remaining work is to survey the consumers and needs of Main Stash, decide how to accomodate them going forward. E.g. would it help if we migrated some of its consumers elsewhere and have a simpler replacement for the rest? Also: carry out any software and infra changes as needed. * Lead: [[Wikimedia Site Reliability Engineering#Data Persistence|SRE Data Persistence Team]] (Manuel). * In collaboration with [[Wikimedia Performance Team|Performance Team]] (Tim, Aaron) * Task: [[phab:T212129|T212129]] Updates: * June 2020: The plan is to move this data to a new small MariaDB cluster. This project requires fixing "makeGlobalKey"" in SqlBagOStuff, and new hardware. This is being procured and set up in Q2 2020-2021 by the Data Persistence Team. The Performance Team will take care of migrating the Main Stash as soon as the new database cluster is available, i.e. between Oct 2020 and Mar 2021 (FY 2020-2021 Q2 or Q3). * July 2020: SqlBagOStuff now supports makeGlobalKey and can work with separate DB connections outside the local wiki. - [[phab:T229062|T229062]] * Sep 2020: Hardware procurement submitted. Oct 2020: Procurement approved as part of larger order. Dec 2020: Hardware arrived. - [[phab:T264584|T264584]] * Jan 2021: Hardware racked and being provisioned. - [[phab:T269324|T269324]] *Feb 2021: MySQL service online and replication configured. - [[phab:T269324|T269324]] *June 2022: Test config in production. *June 222: Enable on all wikis. *{{Done}} === MariaDB cross-datacenter secure writes === MediaWiki being active-active means that writes still only go to the primary datacenter, however a fallback is required for edge cases where a write is attempted in a secondary datacenter. In order to preserve our users' privacy, [[phab:T134809|writes need to be sent encrypted across datacenters]]. Multiple solutions are being considered, but a decision has yet to be made on which one will be implemented. This work will be a collaboration between the [[Wikimedia Site Reliability Engineering#Data Persistence|Data Persistence Team]] and the [[Wikimedia Performance Team|Performance Team]]. We hope for it to happen during fiscal year 2020-2021. * Lead: [[Wikimedia Site Reliability Engineering#Data Persistence|SRE Data Persistence Team]] (Manuel). * In collaboration with [[Wikimedia Performance Team|Performance Team]] (Tim, Timo, Aaron). * Task: [[phab:T134809|T134809]] Updates: * July 2020: Potential solutions evoked so far: Connect with TLS to MariaDB from PHP directly, ProxySQL, dumb TCP tunnel, Envoy as TCP tunnel?, HAProxy in TCP mode. * Dec 2020: Leaning toward a tunnel approach, ProxySQL would take too long to set up and test from scratch. * May 2022: Decision is reached, led by Tim. TLS connection to be established directly from MediaWiki without additional proxies or tunnels. * May 2022: Configuration written. * June 2022: MariaDB-TLS tested and enabled for all wikis. * {{Done}} === ResourceLoader file dependency store === Currently written to a core wiki table using a primary DB connection, must be structured such that writes are done within a secondary DC and then replicated. The plain is to migrate it toward the Main Stash instead. * Lead: Performance Team (Timo, Aaron). * Task: [[phab:T113916|T113916]] Updates: * July 2019: Implement DepStore abstraction, decoupled from using primary DB, and now includes a KeyValue implementation that supports Main Stash. * May 2020: Rolled out to Beta Cluster and mediawiki.org. * June 2022: MainStashDB went live. Roll out to group0 wikis. * July 2022: Gradually rolled out to all wikis (details on task). *{{Done}} === CDN routing === Remaining work is to agree on the MW requirements, and then write, test and deploy the traffic routing configuration. * Lead: Performance Team (Tim, Aaron, Timo). * In collaboration with SRE Traffic and SRE Service Ops. * Task: [[phab:T91820|T91820 (implement CDN switch)]], [[phab:T279664|T279664 (plan gradual rollout)]] Updates: * May 2020: Aaron and Timo have thought through all relevant scenarioes and drafted the requirements at [[phab:T91820|T91820]]. * June 2020: Audit confirms that relevant routing cookies and headers are in place on the MW side. * May 2022: Traffic routing logic being developed by Tim. * June 2022: ATS routing logic deployed to Beta and prod, no-op but enabled. * {{Done}} == History == For notes from 2015-2016, see [[Requests for comment/Multi datacenter strategy for MediaWiki/Progress|Multi datacenter strategy for MediaWiki/Progress]]. oacbt6zk7zd28v75fr200zcwd4h2xoz Translations:Extension:Cargo/20/de 1198 1220697 5387031 4143762 2022-07-28T19:54:03Z ThisCarthing 17456337 wikitext text/x-wiki Cargo wurde getestet und funktioniert mit den Datenbanksystemen MySQL und PostgreSQL. 113qdn0238jt5f9ag4gfck9rd1egpxe Translations:Extension:Cargo/21/de 1198 1220698 5387033 4469269 2022-07-28T19:55:31Z ThisCarthing 17456337 wikitext text/x-wiki Theoretisch unterstützt es auch SQLite, aber es wurde mit SQLite nicht gut getestet und es funktioniert möglicherweise nicht. ii7e6gjr6aqfzz8y3t3igqujg2y6kw9 Reading/Web/Desktop Improvements/Updates/zh 0 1223384 5387659 5324185 2022-07-29T04:24:10Z Chubit 17346826 Created page with "==== $1:页面标题/标签切换 ====" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] <span lang="en" dir="ltr" class="mw-content-ltr">We are deploying one of our latest updates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The page title will be displayed above the tabs such as {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}}, or {{int:cactions}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">With this change, we are improving two things.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First, we are making it clear that the items in the tabs are related to the the page that's being viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] rr3y7fhxk4qv1w435tfk52s36vkzfqt 5387661 5387659 2022-07-29T04:24:27Z Chubit 17346826 Created page with "我们正在部署我们的最新更新之一。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 <span lang="en" dir="ltr" class="mw-content-ltr">The page title will be displayed above the tabs such as {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}}, or {{int:cactions}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">With this change, we are improving two things.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First, we are making it clear that the items in the tabs are related to the the page that's being viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] rfb3i4fkqt0nbwaxx75a93xum7rtae6 5387663 5387661 2022-07-29T04:24:36Z Chubit 17346826 Created page with "页面标题将显示在选项卡上方,例如$1、$2、$3、$4或$5。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 <span lang="en" dir="ltr" class="mw-content-ltr">With this change, we are improving two things.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First, we are making it clear that the items in the tabs are related to the the page that's being viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 3g2eqftlghq1v9jn2446v1hod3nb2fr 5387665 5387663 2022-07-29T04:24:53Z Chubit 17346826 Created page with "通过这一变化,我们正在改进两件事。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 <span lang="en" dir="ltr" class="mw-content-ltr">First, we are making it clear that the items in the tabs are related to the the page that's being viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 5y0qkd74ujdakn7zszsu6k7gx1pwj4b 5387667 5387665 2022-07-29T04:24:59Z Chubit 17346826 Created page with "首先,我们要明确标签中的项目与正在查看的页面相关。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 2le47ab7yx9zr2zrx8iwh38ck5n8qpm 5387669 5387667 2022-07-29T04:25:05Z Chubit 17346826 Created page with "当我们将页面标题放在首位时,这一点变得很明显。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 29ghib22khr4jww6p5ij6006x8j782g 5387671 5387669 2022-07-29T04:25:24Z Chubit 17346826 Created page with "此更改还使[[$1|切换语言]]更容易。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] luz5mrsgg9sy8qhot98rtungjwje7f9 5387673 5387671 2022-07-29T04:25:32Z Chubit 17346826 Created page with "它将语言按钮移到页面顶部更显眼的位置。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] qfmh7hu94uqep8yu0wy2hw5mwfnxlfq 5387675 5387673 2022-07-29T04:25:40Z Chubit 17346826 Created page with "[[$1|了解有关Phabricator的更多信息]]。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 [[phab:T303549|了解有关Phabricator的更多信息]]。 <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] boyteexlq0zjcr7b0tn9uo3s4y64fr0 5387677 5387675 2022-07-29T04:25:46Z Chubit 17346826 Created page with "我们一直在逐步引入这种变化。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 [[phab:T303549|了解有关Phabricator的更多信息]]。 我们一直在逐步引入这种变化。 <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] jmdt19xtg2m15y3zvos9ik857lclfzd 5387679 5387677 2022-07-29T04:26:03Z Chubit 17346826 Created page with "自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[$1|早期采用者wiki]]都可以使用它。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 [[phab:T303549|了解有关Phabricator的更多信息]]。 我们一直在逐步引入这种变化。 自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|早期采用者wiki]]都可以使用它。 <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] dmglf6chzw302jdyvk7utwhjy23c6oc 5387681 5387679 2022-07-29T04:26:14Z Chubit 17346826 Created page with "在7月4日这一周,所有早期采用者wiki上都将显示更改。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 [[phab:T303549|了解有关Phabricator的更多信息]]。 我们一直在逐步引入这种变化。 自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|早期采用者wiki]]都可以使用它。 在7月4日这一周,所有早期采用者wiki上都将显示更改。 <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 7ve1fhj03v6sgm07tu56hfiy4auebxo 5387683 5387681 2022-07-29T04:26:37Z Chubit 17346826 Created page with "除此之外,我们的下一个办公时间将是7月26日而不是7月12日。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 [[phab:T303549|了解有关Phabricator的更多信息]]。 我们一直在逐步引入这种变化。 自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|早期采用者wiki]]都可以使用它。 在7月4日这一周,所有早期采用者wiki上都将显示更改。 除此之外,我们的下一个办公时间将是7月26日而不是7月12日。 <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] gvqd1j5g79ze0pfzx36zu5nttilrbwg 5387685 5387683 2022-07-29T04:26:49Z Chubit 17346826 Created page with "这将使我们能够准备有关使Vector 2022成为更多wiki的默认设置的沟通。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 [[phab:T303549|了解有关Phabricator的更多信息]]。 我们一直在逐步引入这种变化。 自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|早期采用者wiki]]都可以使用它。 在7月4日这一周,所有早期采用者wiki上都将显示更改。 除此之外,我们的下一个办公时间将是7月26日而不是7月12日。 这将使我们能够准备有关使Vector 2022成为更多wiki的默认设置的沟通。 <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] iyuv860f43tu7narr8vwmqd1rzhgzhz 5387687 5387685 2022-07-29T04:26:55Z Chubit 17346826 Created page with "我们还在努力为未来的办公时间提供更好的语言支持。" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 [[phab:T303549|了解有关Phabricator的更多信息]]。 我们一直在逐步引入这种变化。 自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|早期采用者wiki]]都可以使用它。 在7月4日这一周,所有早期采用者wiki上都将显示更改。 除此之外,我们的下一个办公时间将是7月26日而不是7月12日。 这将使我们能够准备有关使Vector 2022成为更多wiki的默认设置的沟通。 我们还在努力为未来的办公时间提供更好的语言支持。 <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] eko0odzt11i96ayul54i2ci4kcfs2u2 5387689 5387687 2022-07-29T04:27:09Z Chubit 17346826 Created page with "更多信息即将推出!" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == 最近更新 == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}:页面标题/标签切换 ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] 我们正在部署我们的最新更新之一。 页面标题将显示在选项卡上方,例如{{int:talk}}、{{int:skin-view-view}}、{{int:skin-view-edit}}、{{int:skin-view-history}}或{{int:cactions}}。 通过这一变化,我们正在改进两件事。 首先,我们要明确标签中的项目与正在查看的页面相关。 当我们将页面标题放在首位时,这一点变得很明显。 此更改还使[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|切换语言]]更容易。 它将语言按钮移到页面顶部更显眼的位置。 [[phab:T303549|了解有关Phabricator的更多信息]]。 我们一直在逐步引入这种变化。 自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|早期采用者wiki]]都可以使用它。 在7月4日这一周,所有早期采用者wiki上都将显示更改。 除此之外,我们的下一个办公时间将是7月26日而不是7月12日。 这将使我们能够准备有关使Vector 2022成为更多wiki的默认设置的沟通。 我们还在努力为未来的办公时间提供更好的语言支持。 更多信息即将推出! ==== {{ym|2022|04}}:提供目录 ==== 我们已经部署了新的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|目录]]。 它使获取页面内容的上下文和导航页面变得更容易,而无需滚动到顶部。 它目前可供三组用户使用。 首先,所有使用Vector 2022并且不在我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|试点维基]]上的人。 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户。 下周,我们将对其余试点wiki的目录进行A/B测试。 我们想检查滚动到页面顶部的需求是否减少。 在此之前,我们为读者和编辑准备了一系列[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|原型测试]]。 要了解更多关于我们如何根据反馈开发该功能的信息,请参阅项目页面。 现在,我们正在根据第二段中提到的用户反馈开发该功能。 尤其是: * 较窄屏幕上的ToC。 我们已将ToC当前隐藏的阈值提高到1000像素。 (有关更多上下文,请参阅[[phab:T306904|T306904]])。 这是为了让在更窄的屏幕上阅读更舒适。 不过,这是一个临时修复。 关于最佳解决方案的讨论将在[[phab:T306660|T306660]]中继续。 到4月底/5月初,我们希望就我们对那里提出的选项的偏好有明确的下一步措施。 * 我们开始着手减少1000像素到1200像素之间的屏幕边距。 这将使目录更小,并为文本创造更多空间。 我们将在[[phab:T307004|T307004]]中跟踪这一点,并且可能会在几天内准备好实施。 ==== {{ym|2022|03}}:开发目录 ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] 我们的[[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|第三次原型测试]]的结果显示了对[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|拟议目录]]的压倒性支持。 基于此,团队专注于开发此功能。 新的目录将是持久的——用户可以随时访问它。 它还将使您更容易理解页面的上下文。 除此之外,还可以导航到页面的不同部分,而无需一直滚动到顶部。 我们预计在4月上半月将新目录部署到我们的试点wiki。 <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == 其他更新 == ==== {{ym|2022|03}}:页面工具反馈 ==== 该团队正在开始研究页面工具(有时称为文章工具)。 我们的目标是更容易区分侧边栏中各个项目的用途。 我们目前正在收集有关我们提议的原型的反馈。 我们期待着听到您的想法! 请访问我们的[[Reading/Web/Desktop Improvements/Fourth prototype testing|原型测试页面]]并填写表格。 ==== {{ym|2022|03}}:粘性标题确认减少滚动到页面顶部的需要==== [[File:Sticky header logged in.png|thumb]] 从2022年1月5日到1月31日,我们进行了[[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|A/B 测试]]。 我们想评估部署粘性标头的影响。 该测试在我们的22个试点wiki上运行。 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题。 对照组中的用户看到了旧功能。 AB检验的主要目的是检验我们的假设。 我们一直期望粘性标题会减少滚动到页面顶部的需要。 总体而言,与对照组(没有粘性标题)相比,我们看到治疗组(使用新的粘性标题)的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%。 在剩下的7个试点wiki上,活动太少,我们将它们排除在外。 结果表明我们的假设是正确的。 将粘性标题添加到页面显着减少了滚动到页面顶部的需要。 [https://jenniferwang-wmf.github.io/Web_sticky_header/ 阅读完整报告]。 ==== {{ym|2022|01}}:更多试点维基 ==== 桌面改进是另外12个wiki的默认设置。 最重要的是:摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki。 除此之外,我们还启用了维基媒体基金会相关维基的更改:维基媒体基金会治理维基、协作维基和战略维基。 目前,有近30个试点wiki。 其中,有不同文字和大小的维基,写在各大洲,由社区和基金会共同运行。 我们希望很快,至少有一个维基文库将被添加到该列表中。 ==== {{ym|2021|12}}:粘性标题开发 ==== [[File:Sticky header logged in.png|thumb|登录用户的粘性标题]] 该团队一直致力于构建[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|粘性标题]]。 它将允许登录用户访问整个页面的重要功能(搜索、讨论页、历史记录页、语言切换等)。 我们已经完成了第一版粘性标题的开发。 现在,我们预计在1月底之前将A/B测试部署到[[Special:MyLanguage/Reading/Web/Desktop Improvements/Frequently asked questions#Which wikis these changes are default turned on?|试点维基]]。 标题基于我们[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|用户测试]]的结果和志愿者对[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|原型测试]]的回答。 ==== {{ym|2021|12}}:语言切换迭代 ==== 今年早些时候,我们将[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|语言按钮]]移到了页面顶部更方便的位置。 但是,我们的A/B测试结果表明,在以下情况下可能难以发现按钮的新位置: * 对于习惯了语言切换功能的先前位置的用户 * 适用于倾向于在多个wiki之间切换语言的用户。在后一种情况下,这会造成语言切换功能在不同位置可用的情况,具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分。 为了改善这些问题,我们正在更改新的语言按钮。 我们的目标是在所有场景中更容易找到。 我们希望在2022年1月发布这些改进。 ==== {{ym|2021|12}}:目录的原型测试 ==== 在接下来的几个月中,我们的主要重点将是使目录持久化。 目前,目录仅在页面顶部可用。 当超出页面顶部时,很难获得整篇文章或页面的上下文,或者导航到各个部分。 我们希望使目录更容易在页面中导航,以及理解其上下文。 我们将在接下来的几周内发布我们的研究、进一步的文档和模型。 同时,我们欢迎您[[Special:MyLanguage/Reading/Web/Desktop_Improvements/Third_prototype_testing|在此页面上向我们提供有关我们当前原型的反馈]]。 {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] lnapysq094936im7q127g0jfg5ej3sy Translations:Reading/Web/Desktop Improvements/151/es 1198 1236132 5387439 5271561 2022-07-28T22:19:06Z Zapipedia (WMF) 17560702 wikitext text/x-wiki Han pasado 12 años desde que se implementó la skin predeterminada actual de Wikimedia ([[$1|Vector]]). j39tygiyd3oav2lx0t4nqea95jogwy8 Template:InstallationNav/bn 10 1240790 5387186 5384773 2022-07-28T21:17:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Installing MediaWiki/sv 100 1244931 5387508 5384979 2022-07-28T22:45:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki can be difficult to install if you do not have any experience with Apache (web server software), PHP and MySQL/MariaDB (database).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Se även == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] 9y5nr820ctz4jtxtkn8f79e5htcxcjj Manual:Installing MediaWiki/fi 100 1257112 5387494 5384967 2022-07-28T22:45:20Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki can be difficult to install if you do not have any experience with Apache (web server software), PHP and MySQL/MariaDB (database).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> == Lataa MediaWiki-ohjelmisto == <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} ==Lataa tiedostot palvelimellesi== <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div class="mw-translate-fuzzy"> == Luo tietokanta == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser (sitten syötä salasana) createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} == Suorita asennusskripti == <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> == Pysy ajan tasalla! == <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Katso myös == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] ft31fstulfbhsqu4nslkhe2tvmzurd5 New requirements for user signatures/pt-br 0 1261999 5386350 5325347 2022-07-28T13:22:32Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> Diversas wikis têm exigências para a personalização das assinaturas dos usuários. <span class="mw-translate-fuzzy">A [[Editing team|Equipe de Edição]] está buscando sua opinião sobre uma proposta para por alguns desses requisitos na Wikipedia.</span> Facilitando [[mw:Talk pages project/replying|responder a comentários específicos]] nas páginas de discussão e usar algumas outras ferramentas. Para mais detalhes sobre o que está sendo proposto, e por que, veja abaixo: * Que retorno a equipe está buscando: '''[[#Input: your feedback|Entrada: sua avaliação]]''' * Porque está mudança está sendo proposta: '''[[#Background: why this change?|Bastidores: porque está mudando?]]''' * Qual mudança está sendo proposta: '''[[#Proposal: signature validation requirements|Proposta: requisitos de validação de assinatura]]''' * Como essas mudanças pode afetar você: '''[[#Impact: effects of change|Impacto: efeitos da mudança]]''' __TOC__ {{anchor|Input: your feedback}} == Entrada: sua avaliação == A equipe deseja seu feedback sobre esta proposta. Por favor, poste seu comentário sobre essas perguntas [[Talk:New requirements for user signatures|'''nessa página de discussão''']]: # '''Essas validações de assinatura criariam problemas em sua wiki?''' # '''O que você acha que a equipe deve estar ciente antes de fazer essa alteração?''' # '''O que deve ser feito com as assinaturas existentes que não atendem aos novos limites?''' <em>Por exemplo, eles devem ser proibidos?</em> <em>Por favor, não se sinta limitado pelas perguntas acima. A equipe deseja ouvir qualquer feedback que você queira compartilhar.</em> {{anchor|Background: why this change?}} == Bastidores: porque está mudando? == Em 2019, voluntários de [[mw:Talk pages consultation 2019/Participant group sign-up|20 projetos e grupos de usuários da Wikimedia]], junto com a equipe da Fundação Wikimedia, participaram doa [[mw:Talk_pages_consultation_2019|consulta de páginas de discussão]]. Foi um esforço para definir melhores ferramentas para comunicação na wiki. Um dos resultados desta consulta foi [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|um pedido de uma maneira mais fácil de responder a comentários específicos]] nas páginas de discussão. Para que [[mw:Talk_pages_project/replying|este recurso]] funcione bem, o software precisa de assinaturas para ser "legível por máquina", para que possa detectar os comentários dos usuários de forma confiável e permitir respondê-los. O problema é que, embora muitas wikis já tenham os requisitos de assinatura necessários em vigor, esses requisitos não estão incluídos no próprio software. Isso aumenta as chances de alguém definir uma assinatura que quebre as convenções da wiki e, potencialmente, torne mais difícil para as pessoas participarem das conversas. Essa consistência adicional no formato das assinaturas melhoraria os recursos existentes, como [[mw:Help:Notifications/Types#Mentions|notificações de "menção"]], que são enviados apenas se a assinatura puder ser detectada em sua edição. {{anchor|Proposal: signature validation requirements}} == Proposta: requisitos de validação de assinatura == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Se não forem identificados obstáculos significativos, essa mudança poderá ocorrer em abril de 2020. Se a equipe precisar fazer mudanças significativas como resultado de seu feedback, demorará mais. As três verificações propostas são descritas nesta seção. Eles seriam aplicados às assinaturas do usuário em Preferências quando um usuário salvasse uma assinatura modificada. {{Highlight|1=<big>De acordo com a proposta da equipe de edição '''as assinaturas existentes *NÃO* serão afetadas'''.</big>|color=yellow}} === Proibir alguns erros de HTML inválido e outros erros [[mw:Help:Extension:Linter|Linter]] === {{Tracked|T140606}} Mais importante, essa mudança não permitiria tags de formatação não fechadas, como {{tag|i|open}} ou a marcação wikitexto correspondente, <code><nowiki>''</nowiki></code>, sem uma etiqueta de fechamento correspondente (neste caso, {{tag|i|close}} ou <code><nowiki>''</nowiki></code>, respectivamente). As assinaturas contendo marcação inválida podem afetar toda a página de discussão, quando a formatação continua nos comentários subsequentes. A verificação também identificaria [[Special:LintErrors/misnested-tag|etiquetas misnested]], como <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (as etiquetas <code>i</code> ou <code>b</code> devem estar do lado de fora), e [[Special:LintErrors/stripped-tag|etiquetas removidas]], que são etiquetas de fechamento sem uma tag de abertura correspondente (o oposto da "etiqueta de formatação não fechada" listada acima). As assinaturas que contêm alguns problemas menos críticos também não seriam permitidas, por exemplo, tags HTML obsoletas como {{tag|tt}} e {{tag|font}}. Embora isso não cause problemas imediatos, fazer isso evitaria a propagação de código obsoleto para novas páginas da wiki, o que é um aborrecimento para os editores que estão limpando erros do Linter. Uma lista completa de recursos de sintaxe que não seriam permitidos, junto com links para páginas que explicam como atualizar ou corrigir o código com erros Linter, está disponível [[mw:Help:Extension:Linter#Documentation of lint issues|nesse endereço]]. As etiquetas de formatação não fechadas já deveriam ser evitadas pelo software, mas devido às limitações do analisador wikitexto atual, isso funcionou apenas em alguns casos. Uma solução mais robusta tornou-se possível graças a [[Parsoid]]. === Exigir um link para a página do usuário, página de discussão ou contribuições === {{Tracked|T237700}} Várias ferramentas não funcionam corretamente quando uma assinatura não contém pelo menos um dos seguintes links: um link para a página do usuário do usuário, página de discussão do usuário ou página de contribuições. Por exemplo, [[mw:Help:Notifications/Types#Mentions|notificações de "menção"]] não são enviados, e próximos [[mw:Extension:DiscussionTools|DiscussionTools]] não permitirá responder a comentários com essas assinaturas inválidas. Gadgets e outras ferramentas que interagem com assinaturas também podem não funcionar como esperado. Este requisito está presente há muito tempo nas políticas de muitas wikis da Wikimedia, mas não foi imposto pelo software MediaWiki.<ref>Veja os exemplos listados em [[phab:T237700|T237700]].</ref> === Não permitir a substituição "aninhada" na assinatura === {{Tracked|T230652}} ''Algum'' uso de marcação [[subst:]] e tis também não seria permitido nas assinaturas. Anteriormente, era possível usar esses recursos para definir uma assinatura que faria com que o nome de um editor subsequente fosse colocado em seus comentários. Todas as formas de falsificação de assinaturas foram proibidas há muito tempo pela política das wikis maiores e esse tipo de falsificação agora será evitado no software. Subst simples: marcação simples ainda é permitida. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Impacto: efeitos da mudança == === O que aconteceria com as assinaturas existentes? === Quaisquer assinaturas existentes que se tornariam inválidas sob as novas regras ainda são permitidas (''[[:en:Grandfather_clause|grandfathered in]]''). Ao visualizar suas preferências, você verá uma mensagem de aviso sobre isso e, se tentar alterar a assinatura, a nova deve ser válida. Mas se você não alterá-la, a antiga assinatura inválida continuará a ser usada quando você assinar, e você poderá alterar suas outras preferências sem afetá-la. Estamos procurando um feedback sobre se você deseja que as assinaturas inválidas existentes sejam rejeitadas. Se assinaturas inválidas não forem permitidas, a assinatura padrão será inserida quando os usuários afetados assinarem seus comentários, até que corrijam suas assinaturas personalizadas. === Quando essas mudanças podem ocorrer? === Comente antes de 31 de março de 2020. A equipe de edição tomará decisões sobre este projeto no início de abril. Os resultados serão publicados na página de discussão. Se nenhum obstáculo for identificado, essa mudança não acontecerá antes de abril de 2020. Essa data pode ser adiada se a equipe precisar implementar mudanças significativas como resultado de seu feedback. === Como saberemos quais mudanças estão acontecendo? === Incluiremos outro aviso em [[m:Tech/News]] quando essa mudança estiver prestes a ser implementada. === Como podem ser os erros de validação de assinatura? === Os erros de HTML/lint incluem links para documentação existente sobre erros de lint, como [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], e um botão para destacar a parte problemática da assinatura. Os erros de link necessários incluem sintaxe de wikitexto de exemplo a ser usada. <gallery mode="packed" caption="Erros de exemplo"> File:MediaWiki preferences - existing user signature invalid.png|Aviso mostrado quando a assinatura do usuário existente é inválida (contém erros de lint). File:MediaWiki preferences - new user signature invalid 1.png|Erro mostrado quando a nova assinatura do usuário é inválida (tem um erro de lint). File:MediaWiki preferences - new user signature invalid 2.png|Erro mostrado quando a nova assinatura do usuário é inválida (não contém um link obrigatório). </gallery> == Resultado == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> A proposta foi amplamente aceita. Em resposta aos comentários dos voluntários, algumas pequenas mudanças foram feitas e alguns pontos foram esclarecidos. # Proibir alguns HTML inválidos e outros erros de [[mw:Help:Extension:Linter|Linter]] #:O escopo dessas mudanças será reduzido. As etiquetas [[Special:LintErrors/misnested-tag|Misnested]] e [[Special:LintErrors/stripped-tag|stripped]] será rejeitado. Alguns erros de baixa prioridade ainda serão aceitos. Especificamente, etiquetas de HTML obsoletas como {{tag|tt}} e {{tag|font}} não serão banidas neste momento. Esta decisão não prejudica qualquer decisão futura a favor ou contra a remoção dessas etiquetas HTML obsoletas. # Exigir um link para a página do usuário, página de discussão ou contribuições #:Isso será implementado conforme planejado originalmente. #:Para maior clareza, deve haver pelo menos um link direto local (não por meio de um redirecionamento, por exemplo, do nome de usuário antigo) para uma dessas páginas. Assim, uma assinatura de <code><nowiki>[[User:Example|Exemplo]] ([[m:User talk:Example]])</nowiki></code> seria aceitável (um link local, um link para outra wiki), mas uma assinatura que inclui links <em>somente</em> para outra wiki, ou <em>only</em> redirecionamentos de um nome de usuário anterior serão inválidos. Isso ocorre por motivos técnicos. # Não permitir a substituição "aninhada" na assinatura #:Isso será implementado conforme planejado originalmente. O processo para implementar essa mudança é: * {{done}} Um anúncio geral será feito nas [[m:Tech/News|novidades técnicas]] quando os novos requisitos são implantados. * {{done}} Uma vez que a mudança de software tenha sido feita nos servidores, os usuários não poderão mais salvar assinaturas personalizadas inválidas. No entanto, as assinaturas existentes permanecerão. * {{in progress}} Editores ativos com assinaturas inválidas serão incentivados a alterar suas assinaturas. Este processo provavelmente levará alguns meses. * Eventualmente, todas as assinaturas precisarão estar em conformidade. Se os editores não corrigirem suas assinaturas customizadas, então suas assinaturas customizadas irão parar de funcionar e a assinatura padrão aparecerá em seu lugar. As wikis de terceiros poderão ativar essa alteração manualmente. <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == Notas == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] omb2dwk19kt9eokenx0p3o7y44rvixp 5386370 5386350 2022-07-28T13:25:01Z Shirayuki 472859 update wikitext text/x-wiki <languages/> Diversas wikis têm exigências para a personalização das assinaturas dos usuários. A [[Special:MyLanguage/Editing team|Equipe de Edição]] está buscando sua opinião sobre uma proposta para por alguns desses requisitos na Wikipedia. Facilitando [[mw:Talk pages project/replying|responder a comentários específicos]] nas páginas de discussão e usar algumas outras ferramentas. Para mais detalhes sobre o que está sendo proposto, e por que, veja abaixo: * Que retorno a equipe está buscando: '''[[#Input: your feedback|Entrada: sua avaliação]]''' * Porque está mudança está sendo proposta: '''[[#Background: why this change?|Bastidores: porque está mudando?]]''' * Qual mudança está sendo proposta: '''[[#Proposal: signature validation requirements|Proposta: requisitos de validação de assinatura]]''' * Como essas mudanças pode afetar você: '''[[#Impact: effects of change|Impacto: efeitos da mudança]]''' __TOC__ {{anchor|Input: your feedback}} == Entrada: sua avaliação == A equipe deseja seu feedback sobre esta proposta. Por favor, poste seu comentário sobre essas perguntas [[Talk:New requirements for user signatures|'''nessa página de discussão''']]: # '''Essas validações de assinatura criariam problemas em sua wiki?''' # '''O que você acha que a equipe deve estar ciente antes de fazer essa alteração?''' # '''O que deve ser feito com as assinaturas existentes que não atendem aos novos limites?''' <em>Por exemplo, eles devem ser proibidos?</em> <em>Por favor, não se sinta limitado pelas perguntas acima. A equipe deseja ouvir qualquer feedback que você queira compartilhar.</em> {{anchor|Background: why this change?}} == Bastidores: porque está mudando? == Em 2019, voluntários de [[mw:Talk pages consultation 2019/Participant group sign-up|20 projetos e grupos de usuários da Wikimedia]], junto com a equipe da Fundação Wikimedia, participaram doa [[mw:Talk_pages_consultation_2019|consulta de páginas de discussão]]. Foi um esforço para definir melhores ferramentas para comunicação na wiki. Um dos resultados desta consulta foi [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|um pedido de uma maneira mais fácil de responder a comentários específicos]] nas páginas de discussão. Para que [[mw:Talk_pages_project/replying|este recurso]] funcione bem, o software precisa de assinaturas para ser "legível por máquina", para que possa detectar os comentários dos usuários de forma confiável e permitir respondê-los. O problema é que, embora muitas wikis já tenham os requisitos de assinatura necessários em vigor, esses requisitos não estão incluídos no próprio software. Isso aumenta as chances de alguém definir uma assinatura que quebre as convenções da wiki e, potencialmente, torne mais difícil para as pessoas participarem das conversas. Essa consistência adicional no formato das assinaturas melhoraria os recursos existentes, como [[mw:Help:Notifications/Types#Mentions|notificações de "menção"]], que são enviados apenas se a assinatura puder ser detectada em sua edição. {{anchor|Proposal: signature validation requirements}} == Proposta: requisitos de validação de assinatura == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Se não forem identificados obstáculos significativos, essa mudança poderá ocorrer em abril de 2020. Se a equipe precisar fazer mudanças significativas como resultado de seu feedback, demorará mais. As três verificações propostas são descritas nesta seção. Eles seriam aplicados às assinaturas do usuário em Preferências quando um usuário salvasse uma assinatura modificada. {{Highlight|1=<big>De acordo com a proposta da equipe de edição '''as assinaturas existentes *NÃO* serão afetadas'''.</big>|color=yellow}} === Proibir alguns erros de HTML inválido e outros erros [[mw:Help:Extension:Linter|Linter]] === {{Tracked|T140606}} Mais importante, essa mudança não permitiria tags de formatação não fechadas, como {{tag|i|open}} ou a marcação wikitexto correspondente, <code><nowiki>''</nowiki></code>, sem uma etiqueta de fechamento correspondente (neste caso, {{tag|i|close}} ou <code><nowiki>''</nowiki></code>, respectivamente). As assinaturas contendo marcação inválida podem afetar toda a página de discussão, quando a formatação continua nos comentários subsequentes. A verificação também identificaria [[Special:LintErrors/misnested-tag|etiquetas misnested]], como <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (as etiquetas <code>i</code> ou <code>b</code> devem estar do lado de fora), e [[Special:LintErrors/stripped-tag|etiquetas removidas]], que são etiquetas de fechamento sem uma tag de abertura correspondente (o oposto da "etiqueta de formatação não fechada" listada acima). As assinaturas que contêm alguns problemas menos críticos também não seriam permitidas, por exemplo, tags HTML obsoletas como {{tag|tt}} e {{tag|font}}. Embora isso não cause problemas imediatos, fazer isso evitaria a propagação de código obsoleto para novas páginas da wiki, o que é um aborrecimento para os editores que estão limpando erros do Linter. Uma lista completa de recursos de sintaxe que não seriam permitidos, junto com links para páginas que explicam como atualizar ou corrigir o código com erros Linter, está disponível [[mw:Help:Extension:Linter#Documentation of lint issues|nesse endereço]]. As etiquetas de formatação não fechadas já deveriam ser evitadas pelo software, mas devido às limitações do analisador wikitexto atual, isso funcionou apenas em alguns casos. Uma solução mais robusta tornou-se possível graças a [[Parsoid]]. === Exigir um link para a página do usuário, página de discussão ou contribuições === {{Tracked|T237700}} Várias ferramentas não funcionam corretamente quando uma assinatura não contém pelo menos um dos seguintes links: um link para a página do usuário do usuário, página de discussão do usuário ou página de contribuições. Por exemplo, [[mw:Help:Notifications/Types#Mentions|notificações de "menção"]] não são enviados, e próximos [[mw:Extension:DiscussionTools|DiscussionTools]] não permitirá responder a comentários com essas assinaturas inválidas. Gadgets e outras ferramentas que interagem com assinaturas também podem não funcionar como esperado. Este requisito está presente há muito tempo nas políticas de muitas wikis da Wikimedia, mas não foi imposto pelo software MediaWiki.<ref>Veja os exemplos listados em [[phab:T237700|T237700]].</ref> === Não permitir a substituição "aninhada" na assinatura === {{Tracked|T230652}} ''Algum'' uso de marcação [[subst:]] e tis também não seria permitido nas assinaturas. Anteriormente, era possível usar esses recursos para definir uma assinatura que faria com que o nome de um editor subsequente fosse colocado em seus comentários. Todas as formas de falsificação de assinaturas foram proibidas há muito tempo pela política das wikis maiores e esse tipo de falsificação agora será evitado no software. Subst simples: marcação simples ainda é permitida. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Impacto: efeitos da mudança == === O que aconteceria com as assinaturas existentes? === Quaisquer assinaturas existentes que se tornariam inválidas sob as novas regras ainda são permitidas (''[[:en:Grandfather_clause|grandfathered in]]''). Ao visualizar suas preferências, você verá uma mensagem de aviso sobre isso e, se tentar alterar a assinatura, a nova deve ser válida. Mas se você não alterá-la, a antiga assinatura inválida continuará a ser usada quando você assinar, e você poderá alterar suas outras preferências sem afetá-la. Estamos procurando um feedback sobre se você deseja que as assinaturas inválidas existentes sejam rejeitadas. Se assinaturas inválidas não forem permitidas, a assinatura padrão será inserida quando os usuários afetados assinarem seus comentários, até que corrijam suas assinaturas personalizadas. === Quando essas mudanças podem ocorrer? === Comente antes de 31 de março de 2020. A equipe de edição tomará decisões sobre este projeto no início de abril. Os resultados serão publicados na página de discussão. Se nenhum obstáculo for identificado, essa mudança não acontecerá antes de abril de 2020. Essa data pode ser adiada se a equipe precisar implementar mudanças significativas como resultado de seu feedback. === Como saberemos quais mudanças estão acontecendo? === Incluiremos outro aviso em [[m:Tech/News]] quando essa mudança estiver prestes a ser implementada. === Como podem ser os erros de validação de assinatura? === Os erros de HTML/lint incluem links para documentação existente sobre erros de lint, como [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], e um botão para destacar a parte problemática da assinatura. Os erros de link necessários incluem sintaxe de wikitexto de exemplo a ser usada. <gallery mode="packed" caption="Erros de exemplo"> File:MediaWiki preferences - existing user signature invalid.png|Aviso mostrado quando a assinatura do usuário existente é inválida (contém erros de lint). File:MediaWiki preferences - new user signature invalid 1.png|Erro mostrado quando a nova assinatura do usuário é inválida (tem um erro de lint). File:MediaWiki preferences - new user signature invalid 2.png|Erro mostrado quando a nova assinatura do usuário é inválida (não contém um link obrigatório). </gallery> == Resultado == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Original proposal=== </div> A proposta foi amplamente aceita. Em resposta aos comentários dos voluntários, algumas pequenas mudanças foram feitas e alguns pontos foram esclarecidos. # Proibir alguns HTML inválidos e outros erros de [[mw:Help:Extension:Linter|Linter]] #:O escopo dessas mudanças será reduzido. As etiquetas [[Special:LintErrors/misnested-tag|Misnested]] e [[Special:LintErrors/stripped-tag|stripped]] será rejeitado. Alguns erros de baixa prioridade ainda serão aceitos. Especificamente, etiquetas de HTML obsoletas como {{tag|tt}} e {{tag|font}} não serão banidas neste momento. Esta decisão não prejudica qualquer decisão futura a favor ou contra a remoção dessas etiquetas HTML obsoletas. # Exigir um link para a página do usuário, página de discussão ou contribuições #:Isso será implementado conforme planejado originalmente. #:Para maior clareza, deve haver pelo menos um link direto local (não por meio de um redirecionamento, por exemplo, do nome de usuário antigo) para uma dessas páginas. Assim, uma assinatura de <code><nowiki>[[User:Example|Exemplo]] ([[m:User talk:Example]])</nowiki></code> seria aceitável (um link local, um link para outra wiki), mas uma assinatura que inclui links <em>somente</em> para outra wiki, ou <em>only</em> redirecionamentos de um nome de usuário anterior serão inválidos. Isso ocorre por motivos técnicos. # Não permitir a substituição "aninhada" na assinatura #:Isso será implementado conforme planejado originalmente. O processo para implementar essa mudança é: * {{done}} Um anúncio geral será feito nas [[m:Tech/News|novidades técnicas]] quando os novos requisitos são implantados. * {{done}} Uma vez que a mudança de software tenha sido feita nos servidores, os usuários não poderão mais salvar assinaturas personalizadas inválidas. No entanto, as assinaturas existentes permanecerão. * {{in progress}} Editores ativos com assinaturas inválidas serão incentivados a alterar suas assinaturas. Este processo provavelmente levará alguns meses. * Eventualmente, todas as assinaturas precisarão estar em conformidade. Se os editores não corrigirem suas assinaturas customizadas, então suas assinaturas customizadas irão parar de funcionar e a assinatura padrão aparecerá em seu lugar. As wikis de terceiros poderão ativar essa alteração manualmente. <div lang="en" dir="ltr" class="mw-content-ltr"> ===2021 proposal=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == Notas == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] owvgy3ql9rcx2tqcll11zxpqy1i0vps Translations:New requirements for user signatures/2/pt-br 1198 1262001 5386369 4294624 2022-07-28T13:25:01Z Shirayuki 472859 update wikitext text/x-wiki A [[$1|Equipe de Edição]] está buscando sua opinião sobre uma proposta para por alguns desses requisitos na Wikipedia. 3u92kq2pwdo9dwtumqa7iyptibv7nk9 Extension:SpamBlacklist/de 102 1270458 5386930 5378054 2022-07-28T19:45:38Z ThisCarthing 17456337 Created page with "=== Leistung ===" wikitext text/x-wiki <languages/> {{bundled|1.21}} {{Extension |status = stable |type = page action |username = Tim Starling |author = Tim Starling |image = SpamBlacklist.gif |description = Stellt einen Regex-basierten Spam-Filter bereit |version = Laufende Aktualisierungen |php = |update = |mediawiki = 1.31+ |compatibility policy = rel |download = {{WikimediaDownload|SpamBlacklist}} |readme = {{git file|action=raw|project=mediawiki/extensions/SpamBlacklist|file=README|text=README}} |changelog = |phabricator = MediaWiki-extensions-SpamBlacklist |pagedrive1 = true }} {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">A proposal to rename this extension is discussed at {{Phab|T254649}}.</span>}} Die Erweiterung '''SpamBlacklist''' verhindert Bearbeitungen in denen URLs vorkommen, deren Domains zu Regulären Ausdrücken passen, die in spezifizierten Dateien oder Wiki-Seiten definiert sind. Außerdem wird die Registrierung von Benutzern mit speziellen E-Mail Adressen gesperrt. Wenn versucht wird, eine Seite zu speichern, prüft die Erweiterung den Text gegen eine (potentiell große) Liste illegaler Hostnamen. Wird ein Treffer gefunden, zeigt die Erweiterung dem Benutzer eine Fehlermeldung und verweigert das abspeichern der Seite. == Installation und Einrichtung == === Installation === {{ExtensionInstall |repo-name=SpamBlacklist |custom-steps=* [[#Setting the blacklist|Konfiguration der Blockliste nach Bedarf]] |registration=required }} ===Einrichtung der Blockliste=== Die folgenden lokalen Seiten werden unabhängig von zusätzlichen Quellen immer verwendet: * [[MediaWiki:Spam-blacklist]] * [[MediaWiki:Spam-whitelist]] * [[MediaWiki:Email-blacklist]] * [[MediaWiki:Email-whitelist]] Die Voreinstellung für eine zusätzliche Quelle einer Blockliste ist die Wikimedia Spam-Blackliste auf Meta-Wiki ('''[[m:Special:MyLanguage/Spam blacklist|m:Spam block list]]'''). Standardmäßig nutzt die Erweiterung diese Liste und aktualisiert sie alle 10-15 Minuten. Für viele Wikis wird diese Liste ausreichen um die meisten Spam-Attacken zu verhindern. Seitdem die Blockliste von vielen großen Wikis verwendet wird, ist sie allerdings vergleichsweise konservativ in ihrem Blockierverhalten. <div lang="en" dir="ltr" class="mw-content-ltr"> The Wikimedia spam block list can only be edited by administrators; but you can suggest modifications to the block list at [[m:Talk:Spam blacklist]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can add other bad URLs on your own wiki. List them in the global variable <code>$wgBlacklistSettings</code> in {{ll|Manual:LocalSettings.php|LocalSettings.php}}. See examples below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> <code>$wgBlacklistSettings</code> is an two level array. Top level key is <code>spam</code> or <code>email</code>. They take an array with each value containing either a URL, a filename or a database location. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you use <code>$wgBlacklistSettings</code> in "LocalSettings.php", the default value of "<nowiki>[[m:Spam blacklist]]</nowiki>" will no longer be used - if you want that block list to be accessed, you will have to add it in manually, see examples below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Specifying a database location allows you to draw the block list from a page on your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The format of the database location specifier is ">DB: [db name] [title]". [db name] should exactly match the value of <code>$wgDBname</code> in {{ll|Manual:LocalSettings.php|LocalSettings.php}}. You should create the required page name [title] in the default namespace of your wiki. If you do this, it is strongly recommended that you protect the page from general editing. Besides the obvious danger that someone may add a regex that matches everything, please note that an attacker with the ability to input arbitrary regular expressions may be able to generate [[w:Segmentation fault|segfaults]] in the [[w:PCRE|PCRE library]]. </div> ==== Beispiele ==== <div lang="en" dir="ltr" class="mw-content-ltr"> If you want to, for instance, use the English-language Wikipedia's spam block list in addition to the standard Meta-Wiki one, you could call the following in {{ll|Manual:LocalSettings.php|LocalSettings.php}}, AFTER <code>wfLoadExtension( 'SpamBlacklist' );</code> call: </div> <syntaxhighlight lang="php"> $wgBlacklistSettings = [ 'spam' => [ 'files' => [ "https://meta.wikimedia.org/w/index.php?title=Spam_blacklist&action=raw&sb_ver=1", "https://en.wikipedia.org/w/index.php?title=MediaWiki:Spam-blacklist&action=raw&sb_ver=1" ], ], ]; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is an example of an entirely local set of block lists: the administrator is using the {{ll|Extension:SpamBlacklist/update script|update script}} to generate a local file called "wikimedia_blacklist" that holds a copy of the Meta-Wiki blacklist, and has an additional block list on the wiki page "My spam block list": </div> <syntaxhighlight lang="php"> $wgBlacklistSettings = [ 'spam' => [ 'files' => [ "$IP/extensions/SpamBlacklist/wikimedia_blacklist", // Wikimedia's list // database title 'DB: wikidb My_spam_block_list', ], ], ]; </syntaxhighlight> === Protokollierung === <span lang="en" dir="ltr" class="mw-content-ltr">By default, the extension does not log hits into the [[Special:Log/spamblacklist|spam blacklist log]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable logging set <syntaxhighlight lang=php inline>$wgLogSpamBlacklistHits = true;</syntaxhighlight>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use the <code>spamblacklist</code> user right to control access to the logs.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Every signed-in user can view the logs by default.</span> ==== Problemfälle ==== <div lang="en" dir="ltr" class="mw-content-ltr"> ====Backtrack Limit==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you encounter issues with the block list, you may want to increase the backtrack limit. However on the other hand, this can reduce your security against DOS attacks, as the backtrack limit is a performance limit: </div> <syntaxhighlight lang="php"> // Bump the Perl Compatible Regular Expressions backtrack memory limit // (PHP 5.3.x default, 1000K, is too low for SpamBlacklist) ini_set( 'pcre.backtrack_limit', '8M' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Hardened Wikis==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The SpamBlacklist will not allow editing if the wiki is hardened. Hardening includes limiting <code>open_basedir</code> so that <code>curl</code> is not on-path, and setting <code>allow_url_fopen=Off</code> in <code>php.ini</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the hardened case, SpamBlacklist will cause an exception when Guzzle attempts to make a network request. The Guzzle exception message is, ''GuzzleHttp requires cURL, the allow_url_fopen ini setting, or a custom HTTP handler.'' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ====User Filtering==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The SpamBlacklist will filter all users by default, including Sysops, administrators and bots. Also see [[phab:T36928|Phabricator issue T36928]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Safe list=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">A corresponding safe list can be maintained by editing the [[MediaWiki:Spam-whitelist]] page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is useful if you would like to override certain entries from another wiki's block list that you are using.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia wikis, for instance, sometimes [[m:Use of the spam blacklist for purposes other than combatting spam|use the spam block list for purposes other than combating spam]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It is questionable how effective the Wikimedia spam block lists are at keeping spam off of third-party wikis. Some spam might be targeted only at [[Wikimedia]] wikis, or only at third-party wikis, which would make Wikimedia's blacklist of little help to said third-party wikis in those cases. Also, some third-party wikis might prefer that users be allowed to cite [[w:Wikipedia:Identifying_reliable_sources#Questionable_and_self-published_sources|sources that are not considered reliable on Wikipedia]], or that Wikipedia has considered so ideologically offensive as to warrant blocking. Sometimes what one wiki considers useless spam, another wiki might consider useful. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Users may not always realize that, when a link is rejected as spammy, it does not necessarily mean that the individual wiki they are editing has specifically chosen to ban that URL. Therefore, wiki system administrators may want to edit the {{ll|Manual:System messages}} at [[MediaWiki:Spamprotectiontext]] and/or [[MediaWiki:Spamprotectionmatch]] on your wiki to invite users to make suggestions at [[MediaWiki talk:Spam-whitelist]] for pages that should be added by a {{ll|Manual:Administrators}} to the safe list. For example, you could put, for MediaWiki:Spamprotectiontext: </div> :<span lang="en" dir="ltr" class="mw-content-ltr">The text you wanted to save was blocked by the spam filter. This is probably caused by a link to a blacklisted external site. <nowiki>{{SITENAME}}</nowiki> maintains <nowiki>[[MediaWiki:Spam-blacklist|its own block list]]</nowiki>; however, most blocking is done by means of <nowiki>[[metawikimedia:Spam-blacklist|Meta-Wiki's block list]]</nowiki>, so this block should not necessarily be construed as an indication that <nowiki>{{SITENAME}}</nowiki> made a decision to block this particular text (or URL). If you would like this text (or URL) to be added to <nowiki>[[MediaWiki:Spam-whitelist|the local spam safe list]]</nowiki>, so that <nowiki>{{SITENAME}}</nowiki> users will not be blocked from adding it to pages, please make a request at <nowiki>[[MediaWiki talk:Spam-whitelist]]</nowiki>. A <nowiki>[[Project:Sysops|sysop]]</nowiki> will then respond on that page with a decision as to whether it should be listed as safe.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Notes== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * This extension examines only new external links added by wiki editors. </div> <span lang="en" dir="ltr" class="mw-content-ltr">To check user agents, add [[Extension:Bad Behavior|Bad Behaviour]] or [[Extension:AkismetKlik|Akismet]]</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the various tools for [[manual:combating spam|combating spam]] on MediaWiki use different methods to spot [[Extension:AbuseFilter|abuse]], the safeguards are best used in combination.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * The [[Extension:SpamBlacklist/update script]] is a cron script that can automate updates from shared block lists. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you are using memcached, you will also have to delete the <code>spam_blacklist_regexes</code> key (for example, using <code>maintenance/mcc.php</code>).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * There're no way to let some users override spam block list. See [[bugzilla:34928]]. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Block list syntax=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you would like to create a block list of your own, or modify an existing one, here is the syntax: </div> <span lang="en" dir="ltr" class="mw-content-ltr">Everything on a line after a '#' character is ignored (for comments).</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other strings are regex fragments which will only match inside URLs.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ;Notes: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Do not add "http://"; this would fail, since the regex will match ''after'' "http://" (or "https://") inside URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Furthermore "www" is unneeded, since the regex will match any subdomains. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By giving "www\." explicitly one can match specific subdomains.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * The <code>(?<=//|\.)</code> and <code>$</code> anchors match the beginning and end of the domain name, ''not'' the beginning and end of the URL. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The regular anchor <code>^</code> won't be of any use.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Slashes don't need to be escaped by backslashes, this will be done automatically by the script. </div> ; Beispiel: <div lang="en" dir="ltr" class="mw-content-ltr"> The following line will block all URLs that contain the string "example.com", except where it is immediately preceded or followed by a letter or a number. </div> <nowiki>\bexample\.com\b</nowiki> <div lang="en" dir="ltr" class="mw-content-ltr"> These are blocked: </div> * <nowiki>http://www.example.com</nowiki> * <nowiki>http://www.this-example.com</nowiki> * <nowiki>http://www.google.de/search?q=example.com</nowiki> <div lang="en" dir="ltr" class="mw-content-ltr"> These are not blocked: </div> * <nowiki>http://www.goodexample.com</nowiki> * <nowiki>http://www.google.de/search?q=example.commodity</nowiki> === Leistung === <span lang="en" dir="ltr" class="mw-content-ltr">The extension creates a single regex statement which looks like <code><nowiki>/https?:\/\/[a-z0-9\-.]*(line 1|line 2|line 3|....)/Si</nowiki></code> (where all slashes within the lines are escaped automatically).</span> <span lang="en" dir="ltr" class="mw-content-ltr">It saves this in a small "loader" file to avoid loading all the code on every page view.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page view performance will not be affected even if you're not using a [[w:Byte-code|bytecode]] cache although using a cache is strongly recommended for any MediaWiki installation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The regex match itself generally adds an insignificant overhead to page saves (on the order of 100ms in our experience).</span> <span lang="en" dir="ltr" class="mw-content-ltr">However, loading the spam file from disk or the database, and constructing the regex, may take a significant amount of time depending on your hardware.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you find that enabling this extension slows down saves excessively, try installing a supported bytecode cache.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This extension will cache the constructed regex if such a system is present.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If you're sharing a server and cache with several wikis, you may improve your cache performance by modifying getSharedBlacklists and clearCache in SpamBlacklist_body.php to use {{wg|SharedUploadDBname}} (or a specific DB if you do not have a shared upload DB) rather than {{wg|DBname}}. Be sure to get all references! The regexes from the separate MediaWiki:Spam-blacklist and MediaWiki:Spam-whitelist pages on each wiki will still be applied. </div> {{anchor|External block list servers (RBL's)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External block list servers (RBL's) === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In its standard form, this extension requires that the block list be constructed manually. While regular expression wildcards are permitted, and a block list originated on one wiki may be re-used by many others, there is still some effort required to add new patterns in response to spam or remove patterns which generate false-positives. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of this effort may be reduced by supplementing the spam regex with lists of known domains advertised in spam email. The regex will catch common patterns (like "casino-" or "-viagra") while the external block list server will automatically update with names of specific sites being promoted through spam. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In the filter() function in SpamBlacklist_body.php, approximately halfway between the file start and end, are the lines: </div> <syntaxhighlight lang="php"> # Do the match wfDebugLog( 'SpamBlacklist', "Checking text against " . count( $blacklists ) . " regexes: " . implode( ', ', $blacklists ) . "\n" ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Directly above this section (which does the actual regex test on the extracted links), one could add additional code to check the external RBL servers: </div> <syntaxhighlight lang="php"> # Do RBL checks $retVal = false; $wgAreBelongToUs = ['l1.apews.org.', 'multi.surbl.org.', 'multi.uribl.com.']; foreach( $addedLinks as $link ) { $link_url=parse_url($link); $link_url=$link_url['host']; if ($link_url) { foreach( $wgAreBelongToUs as $base ) { $host = "$link_url.$base"; $ipList = gethostbynamel( $host ); if( $ipList ) { wfDebug( "RBL match: Hostname $host is {$ipList[0]}, it's spam says $base!\n" ); $ip = wfGetIP(); wfDebugLog( 'SpamBlacklistHit', "$ip caught submitting spam: {$link_url} per RBL {$base}\n" ); $retVal = $link_url . ' (blacklisted by ' . $base .')'; wfProfileOut( $fname ); return $retVal; } } } } # if no match found on RBL server, continue normally with regex tests... </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> This ensures that, if an edit contains URLs from already blocked spam domains, an error is returned to the user indicating which link cannot be saved due to its appearance on an external spam block list. If nothing is found, the remaining regex tests are allowed to run normally, so that any manually-specified 'suspicious pattern' in the URL may be identified and blocked. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that the RBL servers list just the base domain names - not the full URL path - so <nowiki>http://example.com/casino-viagra-lottery.html</nowiki> will trigger RBL only if "example.com" itself were blocked by name by the external server. The regex, however, would be able to block on any of the text in the URL and path, from "example" to "lottery" and everything in between. Both approaches carry some risk of false-positives - the regex because of the use of wildcard expressions, and the external RBL as these servers are often created for other purposes - such as control of abusive spam email - and may include domains which are not engaged in forum, wiki, blog or guestbook comment spam ''per se''. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Other spam-fighting tools== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There are various helpful manuals on mediawiki.org on combating spam and other vandalism: </div> * {{ll|Anti-spam features}} - includes link to the built-in {{ll|Manual:$wgSpamRegex|$wgSpamRegex}} anti-spam mechanism. * {{ll|Manual:Combating spam|nsp=0}} * {{ll|Manual:Combating vandalism|nsp=0}} <div lang="en" dir="ltr" class="mw-content-ltr"> Other anti-spam, anti-vandalism extensions include: </div> * {{ll|Extension:ConfirmEdit|nsp=0}} * {{ll|Extension:Bad Behavior|nsp=0}} * [[m:Special:Prefixindex/MediaWiki talk:Spam|Systemnachrichten]] == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> * Compatible blocklist (this is just a tiny sampling; there are many more) </div> ** [[m:Spam blacklist|<span lang="en" dir="ltr" class="mw-content-ltr">Meta-Wiki block list</span>]] <!-- two of them are enough --> <div lang="en" dir="ltr" class="mw-content-ltr"> * Other resources </div> ** {{ll|Extension:SpamBlacklist/update script|Update script}} {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|miraheze=1|prowiki=1|semantic core=1}} [[Category:API extensions{{#translation:}}]] [[Category:Edit extensions{{#translation:}}]] [[Category:Spam management extensions{{#translation:}}]] [[Category:Extensions for data exchange with other wikis{{#translation:}}]] kfluu4se5kngiv8b8g9c6z3vwq0rug5 Translations:Help:Templates/192/cs 1198 1282622 5386405 5092363 2022-07-28T13:47:48Z ENeRZet 17359278 wikitext text/x-wiki {{Thankyou|signature=Tonda|Reason=to že jsi tím, kým jsi|reason=tohle zobrazím, protože u identifikátorů záleží na psaní velkých a malých písmen}} smw8zbni54oi48of6w1ck60fthyrxu9 Wikimedia Product/bn 0 1290167 5387570 5358187 2022-07-29T03:25:37Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">অবদানকারীগণ</span>]] * [[Readers|<span style="color:#2aa198">পাঠকগণ</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == পণ্য জুড়ে == * [[Special:MyLanguage/Product Principles|পণ্য নীতিগুলি]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (পূর্বে: [[Special:MyLanguage/Technical Collaboration Guidance|কারিগরি সহযোগিতা গাইডেন্স]]) * [[Special:MyLanguage/Design/Statement of purpose|ডিজাইন উদ্দেশ্য বিবৃতি]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|পণ্যগুলির জন্য ডেটা এবং গবেষণা সম্পর্কিত তথ্য]] * [[Special:MyLanguage/Wikimedia Research/Showcase|মাসিক গবেষণা শোকেস]] === কার্যক্রম === * [[m:Special:MyLanguage/Communications/Audience research|শ্রোতা গবেষণা]] * [[m:Special:MyLanguage/Community health initiative|সম্প্রদায় স্বাস্থ্য উদ্যোগ]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|নতুন সম্পাদক অভিজ্ঞতা]] (2017–2018) * [[m:Special:MyLanguage/New Readers|নতুন পাঠকগণ]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === প্রকল্প পাতা === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|বিষয়বস্তু অনুবাদ, ভি২]] * [[Special:MyLanguage/Growth/Growth team updates|বৃদ্ধি]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|আইওএস সম্পাদনা]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''অন্যান্য:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === অবদানকারীগণ === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * পৃষ্ঠা: [[Special:MyLanguage/Contributors|অবদানকারীগণ]] * দল: ====== হয়রানি-বিরোধী সরঞ্জাম ====== * ফেব্রিকেটর টাস্ক বোর্ড: [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * পৃষ্ঠা: [[Special:MyLanguage/Anti-Harassment Tools|হয়রানি-বিরোধী সরঞ্জাম]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * পৃষ্ঠা: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== সম্পাদনা ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * পৃষ্ঠা: [[Special:MyLanguage/Editing team|সম্পাদনা দল]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * পৃষ্ঠা: [[Special:MyLanguage/Growth|বৃদ্ধি]] ====== ভাষা ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * পৃষ্ঠা: [[Special:MyLanguage/Wikimedia Language engineering|উইকিমিডিয়া ভাষা প্রকৌশল]] === পাঠক === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * পৃষ্ঠা: [[Special:MyLanguage/Readers|পাঠক]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * দল: ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|অ্যান্ড্রয়েড]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|আইওএস]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === কারিগরি প্রোগ্রাম পরিচালনা === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> পৃষ্ঠা: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|কারিগরি প্রোগ্রাম পরিচালনা]] অধিনায়ক: [[m:User:Ggellerman (WMF)|Grace Gellerman]] === পণ্যের নকশা === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> পৃষ্ঠা: [[Special:MyLanguage/Design#Product Design|পণ্যের নকশা]] পরিচালক: [[User:MNovotny_(WMF)|Margeigh Novotny]] === পণ্য বিশ্লেষণ === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> পৃষ্ঠা: [[Special:MyLanguage/Product Analytics|পণ্য বিশ্লেষণ]] অধিনায়ক: Kate Zimmerman === পণ্য নকশা কৌশল === <!--''[এখানে অন্তর্ভুক্ত পাঠ্য]''--> পৃষ্ঠা: [[Special:MyLanguage/Design#Design Strategy|পণ্য নকশা কৌশল]] অধিনায়ক: Margeigh Novotny === উইকিউপাত্ত === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * পৃষ্ঠা: [[d:Wikidata:Main Page|Wikidata]] * অধিনায়ক: [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * ফ্যাব্রিকেটর বাগ এবং কার্য বোর্ড: [[phab:project/profile/71/|#wikidata]] * আলোচনার তালিকা: wikidata@lists.wikimedia.org {|class="wikitable" |+ উইকিউপাত্ত দলের লক্ষ্যসমূহ |- !scope="row"| ডাব্লিউএমডিই অর্থবছর ২০১৭ | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 কিউ১: জানুয়ারি–মার্চ ২০১৭] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 কিউ২: এপ্রিল–জুন] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf কিউ৩: জুলাই–সেপ্টেম্বর] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf কিউ৪: অক্টোবর–ডিসেম্বর] |- !scope="row"| ডাব্লিউএমডিই অর্থবছর ২০১৬ | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p কিউ১: জানুয়ারি–মার্চ ২০১৬] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p কিউ২: এপ্রিল–জুন] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p কিউ৩: জুলাই–সেপ্টেম্বর] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p কিউ৪: অক্টোবর–ডিসেম্বর] |} == উদ্দেশ্যগুলি == {|class="wikitable" |- !scope="row"| ২০১৯–২০২০ | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|কিউ১: জুলাই–সেপ্টেম্বর ২০১৯]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|কিউ২: অক্টোবর–ডিসেম্বর ২০১৯]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|কিউ৩: জানুয়ারি–মার্চ ২০২০]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|কিউ৪: এপ্রিল–জুন ২০২০]]--> |- !scope="row"| ২০১৮–২০১৯ | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|কিউ১: জুলাই–সেপ্টেম্বর ২০১৮]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|কিউ২: অক্টোবর–ডিসেম্বর ২০১৮]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|কিউ৩: জানুয়ারি–মার্চ ২০১৯]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|কিউ৪: এপ্রিল–জুন ২০১৯]] |- !scope="row"| ২০১৭–২০১৮ | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|কিউ১: জুলাই–সেপ্টেম্বর ২০১৭]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|কিউ২: অক্টোবর–ডিসেম্বর ২০১৭]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|কিউ৩: জানুয়ারি–মার্চ ২০১৮]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|কিউ৪: এপ্রিল–জুন ২০১৮]] |- !scope="row"| ২০১৬–২০১৭ | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|কিউ১: জুলাই–সেপ্টেম্বর ২০১৬]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|কিউ২: অক্টোবর–ডিসেম্বর ২০১৬]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|কিউ৩: জানুয়ারি–মার্চ ২০১৭]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|কিউ৪: এপ্রিল–জুন ২০১৭]] |- !scope="row"| ২০১৫–২০১৬ | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|কিউ১: জুলাই–সেপ্টেম্বর ২০১৫]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|কিউ২: অক্টোবর–ডিসেম্বর ২০১৫]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|কিউ৩: জানুয়ারি–মার্চ ২০১৬]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|কিউ৪: এপ্রিল–জুন ২০১৬]] |} == বার্ষিক রোডম্যাপ == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|২০১৬ পণ্য সংক্ষিপ্তসার]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|২০১৫ পণ্য ও প্রযুক্তি পর্যালোচনা]] [[Category:WMF Projects{{#translation:}}]] 2gbdvxfishr51iprw5cmyk63f15esjq New requirements for user signatures/sv 0 1292206 5386351 5325346 2022-07-28T13:22:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> Många wikier har krav på anpassade användarsignaturer. <span class="mw-translate-fuzzy">[[Editing team|Redigeringsteamet]] vill höra dina åsikter på ett förslag för att kodifiera vissa av kraven i Wikipedias programvara.</span> Detta kommer göra det enklare att [[mw:Talk pages project/replying|svara på enskilda kommentarer på diskussionssidor]] och använda vissa andra verktyg. Du hittar mer information om vad förslaget innebär, och varför, nedan: * Vilken sorts återkoppling teamet vill ha: '''[[#Input: your feedback|Intryck: dina åsikter]]''' * Varför föreslogs denna ändring: '''[[#Background: why this change?|Bakgrund: varför denna ändring?]]''' * Vilken ändring som föreslagits: '''[[#Proposal: signature validation requirements|Förslag: krav på att bekräfta signaturer]]''' * Hur dessa ändringar skulle kunna påverka dig: '''[[#Impact: effects of change|Påverkan: ändringens påverkan]]''' __TOC__ {{anchor|Input: your feedback}} == Intryck: dina åsikter == Teamet vill höra dina åsikter om förslaget. Kommentera gärna på dessa frågor [[Talk:New requirements for user signatures|'''på diskussionssidan''']]: # '''Skulle dessa krav skapa några problem på din wiki?''' # '''Vad tycker du teamet borde vara uppmärksamma på innan de utför ändringarna?''' # '''Vad ska man göra med befintliga signaturer som inte uppfyller de nya begränsningarna?''' <em>Bör de, till exempel, förbjudas?</em> <em>Känn dig inte begränsad av frågorna ovan. Teamet vill höra vad du tycker.</em> {{anchor|Background: why this change?}} == Bakgrund: varför denna ändring? == 2019 deltog volontärer från [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimediaprojekt och användargrupper]], tillsammans med medarbetare från Wikimedia Foundation, i [[mw:Talk_pages_consultation_2019|utfrågningen om diskussionssidorna]]. Det var ett samarbete för att definiera bättre verktyg för att kommunicera med på wikier. Ett av resultaten av utfrågningen var [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|en efterfrågan av ett enklare sätt att svara på specifika kommentarer]] på diskussionssidor. För att [[mw:Talk_pages_project/replying|denna funktion]] ska fungera bra, kräver verktyget att signaturer är "maskinläsbara", så att den pålitligt kan upptäcka kommentarer och svara på dem. Problemet är att, trots att flera wikier redan har de nödvändiga signaturkraven på plats, ingår inte dessa krav i själva programvaran. Detta ökar risken att någon kommer ange en signatur som bryter mot wikins bestämmelser och kan försvåra för andra att delta i konversationer. Denna enhetlighet i signaturers format kommer förbättra befintliga funktioner, som [[mw:Help:Notifications/Types#Mentions|"nämnande"-aviseringar]] som bara skickas om signaturen kan upptäckas i en redigering. {{anchor|Proposal: signature validation requirements}} == Förslag: krav på att bekräfta signaturer == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Har inga märkbara hinder identifierats skulle ändringarna kunna träda i kraft april 2020. Om teamet behöver göra större betydliga ändringar som ett resultat av er återkoppling kommer detta ta längre tid. De tre föreslagna lösningarna beskrivs i det här avsnittet. Detta skulle tillämpas på användarsignaturer i inställningarna när en användare sparar en modifierad signatur. {{Highlight|1=<big>Under redigeringsteamets förslag '''kommer *INTE* befintliga signaturer påverkas'''.</big>|color=yellow}} === Förbjud viss ogiltig HTML och andra [[mw:Help:Extension:Linter|Linter]]-fel === {{Tracked|T140606}} Viktigast av allt, denna ändring kommer förbjuda öppna formateringstaggar, som {{tag|i|open}} eller motsvarande källkodsmarkering, <code><nowiki>''</nowiki></code>, utan en tillhörande stängande tagg (i det här fallet, {{tag|i|close}} eller <code><nowiki>''</nowiki></code>, respektive). Signaturer som innehåller ogiltig markering kan påverka hela diskussionssidan, när formateringen fortsätter in i nästföljande kommentar. Lösningen kommer dessutom identifiera [[Special:LintErrors/misnested-tag|felkapslade taggar]], som <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (antingen båda <code>i</code>, eller båda <code>b</code>, taggar borde vara på utsidan), och [[Special:LintErrors/stripped-tag|strippade taggar]], vilka stänger taggar utan en motsvarande öppnande tagg (motsatsen till "öppna formateringstaggar" listade ovan). Signaturer som innehåller vissa mindre allvarliga problem kommer också förbjudas, t.ex. föråldrade HTML-taggar som {{tag|tt}} och {{tag|font}}. Trots att dessa inte orsakar några direkta besvär skulle detta förhindra folk från att sprida föråldrad kod till nya wikisidor, vilket är irriterande för användare som rensar upp Linter-fel. En fullständig lista över syntaxfunktioner som skulle förbjudas, samt länkar till sidor som förklarar hur man uppdaterar eller fixar koden med Linter-fel, finns tillgänglig [[Linter|här]]. Programvaran ska egentligen redan förbjuda formateringstaggar, men på grund av begränsningar i den nuvarande wikitextparser fungerar det bara ibland. En stabilare lösning har möjliggjorts tack vare [[Parsoid]]. === Kräv en länk till användarsidan, diskussionssidan eller bidrag === {{Tracked|T237700}} Diverse verktyg fungerar inte ordentligt när en signatur inte innehåller åtminstone en av följande länkar: en länk till användarens användarsida, användardiskussion eller bidragssida. Till exempel skickas [[mw:Help:Notifications/Types#Mentions|"omnämningar"]], inkommande [[mw:Extension:DiscussionTools|DiscussionTools]] kommer inte låta en kommentera med dessa ogiltiga signaturer. Finesser och andra verktyg som samverkar som signaturer kanske inte heller fungerar som de ska. Detta krav har tidigare funnits en längre tid i flera av policyerna på Wikimedias wikier, men har inte tillämpats av MediaWikis programvara.<ref>Se exempel listade på [[phab:T237700|T237700]].</ref> === Förbjud "kapslad" ersättning i signaturer === {{Tracked|T230652}} ''Viss'' användning av [[subst:]]-markering och tilde-tecken kommer också förbjudas i signaturer. Tidigare var det möjligt att använda dessa funktioner för att ange en signatur som fick nästa användares namn att placeras på dina kommentarer. Alla former av förfalskning av signaturer har länge förbjudits av policy på större wikier, och denna typ av förfalskning kommer nu förbjudas av programvaran. Enkel ersättning: markering tillåts fortfarande. </div> == Ytterligare förslag (2021) == === Förbjud radbrytningar i signaturer === <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Påverkan: ändringens påverkan == === Vad kommer hända med befintliga signaturer? === Alla befintliga signaturer som skulle bli ogiltiga med de nya reglerna kommer fortfarande tillåtas (''[[:sv:Övergångsbestämmelse|övergångsbestämmelse]]''). När du läser dina inställningar, kommer du se ett varningsmeddelande om detta, om du försöker ändra signaturen, måste den nya vara giltig. Men om du inte kan ändra den, kommer den gamla signaturen fortsätta användas när du signerar, och du kommer kunna ändra dina andra inställningar utan att den påverkas. Vi vill höra om du tycker att befintliga signaturer ska förbjudas eller inte. Om ogiltiga signaturer förbjuds, kommer standardsignaturen att användas för påverkade användare när de signerar sina kommentarer, tills de rättar sina personliga signaturer. === När kommer ändringarna äga rum? === Var god kommentera innan 31 mars 2020. Redigeringsteamet kommer ta ett beslut om projektet i tidigt april. Resultaten kommer offentliggöras på diskussionssidan. Om inga hinder identifieras kommer ändringarna äga rum tidigare en april 2020. Datumet kan senareläggas om teamet behöver genomföra betydande ändringar som ett resultat av er återkoppling. === Vet vi vilka ändringar som kommer hända? === Vi kommer skriva en notis i [[m:Tech/News]] när denna ändring håller på att rullas ut. === Hur kan signatursfel se ut? === HTML/lint-fel innefattar länkar till befintlig dokumentation om lint-fel, som [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]] och en knapp för att markera problematiska delar av signaturen. De obligatoriska länkfelen innehåller exempelsyntax av wikitext att använda. <gallery mode="packed" caption="Exempelfel"> File:MediaWiki preferences - existing user signature invalid.png|Varning som visas när den befintliga användarsignaturen är ogiltig (har lint-fel). File:MediaWiki preferences - new user signature invalid 1.png|Fel som visas när den nya användarsignaturen är ogiltig (har ett lint-fel) File:MediaWiki preferences - new user signature invalid 2.png|Fel som visas när den nya användarsignaturen är ogiltig (innehåller inte en krävd länk). </gallery> == Resultat == === Ursprungliga förslaget === Förslaget har i stort accepterats. Som svar på kommentarer från volontärer har några få ändringar gjorts och några punkter förtydligades. # Förbjud viss ogiltig HTML och andra [[mw:Help:Extension:Linter|Linter]]-fel #:Omfattningen av dessa ändringar kommer minska. [[Special:LintErrors/misnested-tag|Felkapslade]] och [[Special:LintErrors/stripped-tag|strippade]] taggar kommer avvisas. Vissa lågprioriterade fel kommer fortfarande accepteras. Speciellt föråldrade HTML-taggar som {{tag|tt}} och $front kommer inte förbjudas för tillfället. Beslutet påverkar inte framtida beslut för eller mot att ta bort dessa föråldrade HTML-taggar. # Kräv en länk till användarsida, diskussionssida eller bidrag #:Detta kommer tillämpas som planerat. #:För tydlighetens skulle, det måste finnas minst en lokal direkt länk (inte via en omdirigering, t.ex. från gammalt användarnamn) till en av de sidorna. Därav kommer en signatur på <code><nowiki>[[Användare:Exempel|Exempel]] ([[m:User talk:Exempel]])</nowiki></code> accepteras (en lokal länk, en länk till en annan wiki), men en signatur som <em>bara</em> länkar till en annan wiki, <em>bara</em> omdirigerar till ett tidigare användarnamn, kommer vara otiltigt. Detta beror på tekniska skäl. # Förbjud "kapslad" ersättning i signaturer #:Detta kommer tillämpas som planerat. Processen för att tillämpa ändringarna är: * {{done}} Ett allmänt förkunnande kommer göras på [[m:Tech/News|Tekniska nyheter]] när de nya kraven har rullats ut. * {{done}} När programvaruändringen utförts på servrarna, kommer användare inte längre kunna spara ogiltiga signaturer. Däremot kommer befintliga signaturer bli kvar. * {{in progress}} Aktiva användare med ogiltiga signaturer kommer uppmanas ändra sina signaturer. Denna process kommer förmodligen ta några månader. * I slutändan kommer alla signaturer behöva anpassa sig. Om användare inte rättar sina anpassade signaturer, kommer deras anpassade signaturer sluta fungera, och standardsignaturen kommer användas istället. Tredjepartswikier kommer kunna aktivera det här manuellt. === 2021-års förslag === Radbrytningstecken [[w:Carriage return|vagnretur]] och [[w:Newline|nyrad]] (men inte HTML-koderna för dem, t.ex. {{tag|br|single}} och {{tag|p|open}}) är ej tillåtna. == Fotnoter == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 2430g7irvvr5kkhvisleldobwgrxtrd 5386372 5386351 2022-07-28T13:25:13Z Shirayuki 472859 update wikitext text/x-wiki <languages/> Många wikier har krav på anpassade användarsignaturer. [[Special:MyLanguage/Editing team|Redigeringsteamet]] vill höra dina åsikter på ett förslag för att kodifiera vissa av kraven i Wikipedias programvara. Detta kommer göra det enklare att [[mw:Talk pages project/replying|svara på enskilda kommentarer på diskussionssidor]] och använda vissa andra verktyg. Du hittar mer information om vad förslaget innebär, och varför, nedan: * Vilken sorts återkoppling teamet vill ha: '''[[#Input: your feedback|Intryck: dina åsikter]]''' * Varför föreslogs denna ändring: '''[[#Background: why this change?|Bakgrund: varför denna ändring?]]''' * Vilken ändring som föreslagits: '''[[#Proposal: signature validation requirements|Förslag: krav på att bekräfta signaturer]]''' * Hur dessa ändringar skulle kunna påverka dig: '''[[#Impact: effects of change|Påverkan: ändringens påverkan]]''' __TOC__ {{anchor|Input: your feedback}} == Intryck: dina åsikter == Teamet vill höra dina åsikter om förslaget. Kommentera gärna på dessa frågor [[Talk:New requirements for user signatures|'''på diskussionssidan''']]: # '''Skulle dessa krav skapa några problem på din wiki?''' # '''Vad tycker du teamet borde vara uppmärksamma på innan de utför ändringarna?''' # '''Vad ska man göra med befintliga signaturer som inte uppfyller de nya begränsningarna?''' <em>Bör de, till exempel, förbjudas?</em> <em>Känn dig inte begränsad av frågorna ovan. Teamet vill höra vad du tycker.</em> {{anchor|Background: why this change?}} == Bakgrund: varför denna ändring? == 2019 deltog volontärer från [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimediaprojekt och användargrupper]], tillsammans med medarbetare från Wikimedia Foundation, i [[mw:Talk_pages_consultation_2019|utfrågningen om diskussionssidorna]]. Det var ett samarbete för att definiera bättre verktyg för att kommunicera med på wikier. Ett av resultaten av utfrågningen var [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|en efterfrågan av ett enklare sätt att svara på specifika kommentarer]] på diskussionssidor. För att [[mw:Talk_pages_project/replying|denna funktion]] ska fungera bra, kräver verktyget att signaturer är "maskinläsbara", så att den pålitligt kan upptäcka kommentarer och svara på dem. Problemet är att, trots att flera wikier redan har de nödvändiga signaturkraven på plats, ingår inte dessa krav i själva programvaran. Detta ökar risken att någon kommer ange en signatur som bryter mot wikins bestämmelser och kan försvåra för andra att delta i konversationer. Denna enhetlighet i signaturers format kommer förbättra befintliga funktioner, som [[mw:Help:Notifications/Types#Mentions|"nämnande"-aviseringar]] som bara skickas om signaturen kan upptäckas i en redigering. {{anchor|Proposal: signature validation requirements}} == Förslag: krav på att bekräfta signaturer == <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' Har inga märkbara hinder identifierats skulle ändringarna kunna träda i kraft april 2020. Om teamet behöver göra större betydliga ändringar som ett resultat av er återkoppling kommer detta ta längre tid. De tre föreslagna lösningarna beskrivs i det här avsnittet. Detta skulle tillämpas på användarsignaturer i inställningarna när en användare sparar en modifierad signatur. {{Highlight|1=<big>Under redigeringsteamets förslag '''kommer *INTE* befintliga signaturer påverkas'''.</big>|color=yellow}} === Förbjud viss ogiltig HTML och andra [[mw:Help:Extension:Linter|Linter]]-fel === {{Tracked|T140606}} Viktigast av allt, denna ändring kommer förbjuda öppna formateringstaggar, som {{tag|i|open}} eller motsvarande källkodsmarkering, <code><nowiki>''</nowiki></code>, utan en tillhörande stängande tagg (i det här fallet, {{tag|i|close}} eller <code><nowiki>''</nowiki></code>, respektive). Signaturer som innehåller ogiltig markering kan påverka hela diskussionssidan, när formateringen fortsätter in i nästföljande kommentar. Lösningen kommer dessutom identifiera [[Special:LintErrors/misnested-tag|felkapslade taggar]], som <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (antingen båda <code>i</code>, eller båda <code>b</code>, taggar borde vara på utsidan), och [[Special:LintErrors/stripped-tag|strippade taggar]], vilka stänger taggar utan en motsvarande öppnande tagg (motsatsen till "öppna formateringstaggar" listade ovan). Signaturer som innehåller vissa mindre allvarliga problem kommer också förbjudas, t.ex. föråldrade HTML-taggar som {{tag|tt}} och {{tag|font}}. Trots att dessa inte orsakar några direkta besvär skulle detta förhindra folk från att sprida föråldrad kod till nya wikisidor, vilket är irriterande för användare som rensar upp Linter-fel. En fullständig lista över syntaxfunktioner som skulle förbjudas, samt länkar till sidor som förklarar hur man uppdaterar eller fixar koden med Linter-fel, finns tillgänglig [[Linter|här]]. Programvaran ska egentligen redan förbjuda formateringstaggar, men på grund av begränsningar i den nuvarande wikitextparser fungerar det bara ibland. En stabilare lösning har möjliggjorts tack vare [[Parsoid]]. === Kräv en länk till användarsidan, diskussionssidan eller bidrag === {{Tracked|T237700}} Diverse verktyg fungerar inte ordentligt när en signatur inte innehåller åtminstone en av följande länkar: en länk till användarens användarsida, användardiskussion eller bidragssida. Till exempel skickas [[mw:Help:Notifications/Types#Mentions|"omnämningar"]], inkommande [[mw:Extension:DiscussionTools|DiscussionTools]] kommer inte låta en kommentera med dessa ogiltiga signaturer. Finesser och andra verktyg som samverkar som signaturer kanske inte heller fungerar som de ska. Detta krav har tidigare funnits en längre tid i flera av policyerna på Wikimedias wikier, men har inte tillämpats av MediaWikis programvara.<ref>Se exempel listade på [[phab:T237700|T237700]].</ref> === Förbjud "kapslad" ersättning i signaturer === {{Tracked|T230652}} ''Viss'' användning av [[subst:]]-markering och tilde-tecken kommer också förbjudas i signaturer. Tidigare var det möjligt att använda dessa funktioner för att ange en signatur som fick nästa användares namn att placeras på dina kommentarer. Alla former av förfalskning av signaturer har länge förbjudits av policy på större wikier, och denna typ av förfalskning kommer nu förbjudas av programvaran. Enkel ersättning: markering tillåts fortfarande. </div> == Ytterligare förslag (2021) == === Förbjud radbrytningar i signaturer === <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} == Påverkan: ändringens påverkan == === Vad kommer hända med befintliga signaturer? === Alla befintliga signaturer som skulle bli ogiltiga med de nya reglerna kommer fortfarande tillåtas (''[[:sv:Övergångsbestämmelse|övergångsbestämmelse]]''). När du läser dina inställningar, kommer du se ett varningsmeddelande om detta, om du försöker ändra signaturen, måste den nya vara giltig. Men om du inte kan ändra den, kommer den gamla signaturen fortsätta användas när du signerar, och du kommer kunna ändra dina andra inställningar utan att den påverkas. Vi vill höra om du tycker att befintliga signaturer ska förbjudas eller inte. Om ogiltiga signaturer förbjuds, kommer standardsignaturen att användas för påverkade användare när de signerar sina kommentarer, tills de rättar sina personliga signaturer. === När kommer ändringarna äga rum? === Var god kommentera innan 31 mars 2020. Redigeringsteamet kommer ta ett beslut om projektet i tidigt april. Resultaten kommer offentliggöras på diskussionssidan. Om inga hinder identifieras kommer ändringarna äga rum tidigare en april 2020. Datumet kan senareläggas om teamet behöver genomföra betydande ändringar som ett resultat av er återkoppling. === Vet vi vilka ändringar som kommer hända? === Vi kommer skriva en notis i [[m:Tech/News]] när denna ändring håller på att rullas ut. === Hur kan signatursfel se ut? === HTML/lint-fel innefattar länkar till befintlig dokumentation om lint-fel, som [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]] och en knapp för att markera problematiska delar av signaturen. De obligatoriska länkfelen innehåller exempelsyntax av wikitext att använda. <gallery mode="packed" caption="Exempelfel"> File:MediaWiki preferences - existing user signature invalid.png|Varning som visas när den befintliga användarsignaturen är ogiltig (har lint-fel). File:MediaWiki preferences - new user signature invalid 1.png|Fel som visas när den nya användarsignaturen är ogiltig (har ett lint-fel) File:MediaWiki preferences - new user signature invalid 2.png|Fel som visas när den nya användarsignaturen är ogiltig (innehåller inte en krävd länk). </gallery> == Resultat == === Ursprungliga förslaget === Förslaget har i stort accepterats. Som svar på kommentarer från volontärer har några få ändringar gjorts och några punkter förtydligades. # Förbjud viss ogiltig HTML och andra [[mw:Help:Extension:Linter|Linter]]-fel #:Omfattningen av dessa ändringar kommer minska. [[Special:LintErrors/misnested-tag|Felkapslade]] och [[Special:LintErrors/stripped-tag|strippade]] taggar kommer avvisas. Vissa lågprioriterade fel kommer fortfarande accepteras. Speciellt föråldrade HTML-taggar som {{tag|tt}} och $front kommer inte förbjudas för tillfället. Beslutet påverkar inte framtida beslut för eller mot att ta bort dessa föråldrade HTML-taggar. # Kräv en länk till användarsida, diskussionssida eller bidrag #:Detta kommer tillämpas som planerat. #:För tydlighetens skulle, det måste finnas minst en lokal direkt länk (inte via en omdirigering, t.ex. från gammalt användarnamn) till en av de sidorna. Därav kommer en signatur på <code><nowiki>[[Användare:Exempel|Exempel]] ([[m:User talk:Exempel]])</nowiki></code> accepteras (en lokal länk, en länk till en annan wiki), men en signatur som <em>bara</em> länkar till en annan wiki, <em>bara</em> omdirigerar till ett tidigare användarnamn, kommer vara otiltigt. Detta beror på tekniska skäl. # Förbjud "kapslad" ersättning i signaturer #:Detta kommer tillämpas som planerat. Processen för att tillämpa ändringarna är: * {{done}} Ett allmänt förkunnande kommer göras på [[m:Tech/News|Tekniska nyheter]] när de nya kraven har rullats ut. * {{done}} När programvaruändringen utförts på servrarna, kommer användare inte längre kunna spara ogiltiga signaturer. Däremot kommer befintliga signaturer bli kvar. * {{in progress}} Aktiva användare med ogiltiga signaturer kommer uppmanas ändra sina signaturer. Denna process kommer förmodligen ta några månader. * I slutändan kommer alla signaturer behöva anpassa sig. Om användare inte rättar sina anpassade signaturer, kommer deras anpassade signaturer sluta fungera, och standardsignaturen kommer användas istället. Tredjepartswikier kommer kunna aktivera det här manuellt. === 2021-års förslag === Radbrytningstecken [[w:Carriage return|vagnretur]] och [[w:Newline|nyrad]] (men inte HTML-koderna för dem, t.ex. {{tag|br|single}} och {{tag|p|open}}) är ej tillåtna. == Fotnoter == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] a68kkz4neent2kkidy7ywhg2ulbezya Translations:New requirements for user signatures/2/sv 1198 1292212 5386371 4414818 2022-07-28T13:25:12Z Shirayuki 472859 update wikitext text/x-wiki [[$1|Redigeringsteamet]] vill höra dina åsikter på ett förslag för att kodifiera vissa av kraven i Wikipedias programvara. 892dxe6qfi63ay9g5yfomatviozjz3d Help:Extension:Translate/Components/de 12 1292648 5386810 4562695 2022-07-28T19:15:12Z ThisCarthing 17456337 Created page with "=== Nachrichtengruppen ===" wikitext text/x-wiki <languages/> {{Extension-Translate}} Die Übersetzungserweiterung lässt sich auf viele Arten erweitern. Die einfachste Möglichkeit, um die Übersetzungserweiterung zu ergänzen, ist, neue Dateiformate (Link auf Abschnitt) oder neue Nachrichtengruppen (Link auf Abschnitt) zu unterstützen. Manchmal ist es auch sinnvoll, eine neue Nachrichtenprüfung zu schreiben (Link auf Abschnitt) oder die Übersetzungserweiterung durch Hooks zu erweitern (Link auf Abschnitt). Manchmal reicht es aus, die vorhandene {{ll|Help:Extension:Translate/API#Web-API|Web-API}} zu nutzen. Zusätzlich zu den bereits erwähnten Konzepten gibt es viele weitere, wichtige Konzepte und Klassen der Übersetzungserweiterung, die nützlich sind, um die Übersetzungserweiterung zu verändern. Diese Seite soll umfassend und detailliert alle Komponenten der Übersetzungserweiterung erläutern. == Primäre erweiterbare Komponenten == === WebAPI === * detaillierte Dokumentation der [[Special:Help:Extension:Translate/API|API]] Zusätzlich zu Hooks und Oberflächen, die nur über PHP-Code genutzt werden können, bietet die WebAPI Zugriff auf viele Nachrichtengruppen und Informationen und Aktionen rund um das Thema Übersetzen. Sie basiert auf dem [[Special:MyLanguage/API:Main page|MediaWiki-API-Framework]] und unterstützt viele Ausgabeformate wie JSON und XML. === Dateiformatunterstützung (FFS) === * ''Detaillierte Dokumentation der [[Special:MyLanguage/Help:Extension:Translate/File format support|Dateiformatunterstützung]]'' * ''Anleitung zum Schreiben von [[Special:MyLanguage/Help:Extension:Translate/File format support tutorial|Dateiformatunterstützungsklassen]]'' Die Übersetzungserweiterung unterstützt die Übersetzung von Nicht-Wiki-Inhalten wie Software-Nachrichten über Dateiformatunterstützungsklassen (FFS). Diese Klassen implementieren die FFS-Oberfläche und abstrahieren das Parsen und Generieren von Dateiinhalten. Die FFS-Klassen werden von der FileBasedMessageGroup-Klasse über die [[Special:MyLanguage/Help:Extension:Translate/Group configuration|YAML-Konfigurationsdateien]] genutzt. === Nachrichtengruppen === * ''In-depth documentation about [[Special:MyLanguage/Help:Extension:Translate/Message groups|message groups]]'' Message groups bring together a collection of messages. They come in various types: translatable pages, SVG files or software interface messages stored in various file formats. Each message group instance has a unique identifier, name and description. In the code message groups are primarily referenced by their identifier, while the <code>MessageGroups</code> class can be used to get the instances for a given id. Message groups can also control many translation process related actions like allowed translation languages and the message group workflow states. Usually these behaviors fallback to the global defaults. The two primary ways to register message groups to Translate are the [[Special:MyLanguage/Help:Extension:Translate/Hooks|TranslatePostInitGroups hook]] and [[Special:MyLanguage/Help:Extension:Translate/Group configuration example|YAML configuration]]. <div lang="en" dir="ltr" class="mw-content-ltr"> === Translation aids (helpers) === </div> * ''In-depth documentation about [[Special:MyLanguage/Help:Extension:Translate/Translation aids|translation aids]]'' Translation aids are little modules that provide helpful and necessary information for the translator when translating. Different aids can provide suggestions from translation memory and machine translation, documentation about the message or even such a basic thing as the message definition – the text that needs to be translated. Translate comes with many aid classes. Currently there is no hook to add new classes. Each class that extends the TranslationAid class only needs to implement one method called getData. It should return the information in structured format (nested arrays), which is then exposed via ApiQueryTranslationAids WebAPI module. In addition to the aid class, changes are needed to actually use the provided data in the translation editor(s). One special case of translation aids are machine translation services. See the next section. <div lang="en" dir="ltr" class="mw-content-ltr"> === Web services === </div> Adding more machine translation services can easily be done by extending the TranslationWebService class. See the webservices subdirectory for examples. You will need some basic information to implement such a class: * URL for the service * What language pairs are supported * Whether they use language codes that differ from the codes used in MediaWiki * Whether the service needs an API key When you have this information, it is straightforward to write the mapCode, doPairs and doRequest methods. You should use the TranslationWebServiceException to signal errors. The errors are automatically logged and tracked, and if the service goes down, it will automatically be suspended to avoid unnecessary requests to it. The suggestions will automatically be displayed in the translation editor via the MachineTranslationAid class and the ApiQueryTranslationAids WebAPI module. See also $wgTranslateTranslationServices to see how those services are registered. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message checkers === </div> * ''[[Special:MyLanguage/Help:Extension:Translate/Group configuration|How to define checkers for file based message groups]]'' We use computers to catch simple errors in translations, like unbalanced parenthesis or failing to use a variable placeholder. These checkers can emit warnings that are displayed in the translation editor (constantly updating). Any warning present in saved translation will also mark the translation as outdated (fuzzy in jargon). Each message group determines which checks it uses. <div lang="en" dir="ltr" class="mw-content-ltr"> == Other core components == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Message collection === </div> Message collection provides access to the list of messages for a message group. It is used to load a set of languages for certain group in a certain language. It provides paging and filtering functionality. There is currently a limitation that all messages in a collection must be in the same namespace. This prevents the creation of aggregate groups that include groups which have messages in different namespaces. Here is short a example of how to use message collection to load all Finnish translations of group ''core'' and print the first ten of them: <syntaxhighlight lang=php> $group = MessageGroups::getGroup( 'core' ); $collection = $group->initCollection( 'fi' ); $collection->filter( 'ignored' ); $collection->filter( 'translated', false ); $collection->loadTranslations(); $collection->slice( 0, 10 ); foreach ( $collection->keys() as $mkey => $title ) { echo $title->getPrefixedText() . ': '; echo $collection[$mkey]->translation() . "\n\n"; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> === Message === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Utility classes == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Font finder === </div> When rendering bitmap graphics, suitable fonts are needed for each language or script. To solve this problem, the FCFontFinder class was written. It uses the <code>fc-match</code> command of the package <code>fontconfig</code> (so this doesn't work on Windows) to find a suitable font. Many additional fonts should be installed on the server to make this useful. It can either return a path to a font file or the name of the font, whichever is more suitable. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message group cache === </div> The messages of file-based message groups are stored in CDB files. Each language of each group has its own CDB cache file. The reason for cache files are twofold. First they provide constant and efficient access to message data avoiding the potentially expensive parsing of files in various places. For example the list of message keys for each group can be loaded efficiently when rebuilding a message index. The second reason is that the cache files are used together with the translations in the wiki to process external message changes. Having a snapshot of the state of translations in files and wiki (hopefully consistent at that point) allows us to automatically deduct whether something has been changed in the wiki or externally and make intelligent choices, leaving only real conflicts (messages changed both externally and on the wiki since last snapshot) to be resolved by the translation administrator. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message group utilities === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Message index === </div> Message index is a reverse map of all known messages. It provides efficient answer to the questions ''is this a known message'' and ''what groups does this message belong to''. It needs to be fast for single and multiple message key lookups. Multiple different backends are implemented, with different trade-offs. *Serialized file is fast to parse, but don't provide random access and is very memory inefficient when the number of keys grow. *CDB file takes more disk space, but provides random access and reasonably fast lookups, while loading everything into memory is slower. *Database backend provides efficient random access and full load with the expense of little slower individual lookups. It also doesn't need to write to any files avoiding any permission problems. *Also memory backend (memcached, apc) is provided, which could be useful alternatives to database backend in multiple server setups to reduce database contention. Message index does not support incremental rebuilds. Thus rebuilding the index gets relatively resource intensive when the number of message groups and message keys increase. Depending on the message group, this might involve parsing files or doing database queries and loading the definitions, which can take a lot of memory. The message index rebuilding is triggered in various places in Translate, and by default it is executed immediately during the request. As it gets slower, it can be delayed via the MediaWiki job queue and run outside of web requests. === Message table === === Metadata table === === Revtag === === Stats code === === String matcher/mangler === === Ttmserver (translation memory) === * ''In-depth documentation at [[Special:MyLanguage/Help:Extension:Translate/Translation_memories|Translation memories]].'' * ''Blog post of history of this feature at [http://laxstrom.name/blag/2012/09/07/translation-memory-all-wikimedia-wikis/ Niklas' blog].'' Ttmserver is the name of translation memory interface. It supports multiple backends for inserting and querying translation suggestions. The code is located under <code>ttmserver</code> directory. === Misc stuff: RC integration, preferences, toolbox, jobs === == Repository layout == Files in the root of the repository include: * Standard MediaWiki extensions files like <code>Translate.php</code>, translations and some documentation files like <code>hooks.txt</code> and <code>README</code> which includes change notes. * Major translate classes like <code>MessageCollection</code> and <code>Message</code> and some misc utilities not yet moved under utils. Rest of the code is under subdirectories. Major parts have their own subdirectories each: * <code>api</code> for WebAPI code * <code>ffs</code> for file format support code * <code>messagegroups</code> for message groups * <code>scripts</code> for command line scripts * <code>tag</code> for page translation code * <code>ttmserver</code> for translation memory code * <code>specials</code> for all special pages * <code>tests</code> for all PHP unit tests Most of the code is under utils. Some additional folders for non-code: * <code>data</code> for miscellaneous data files * <code>libs</code> for bundled library dependencies * <code>resources</code> for all css, scripts and images * <code>sql</code> for all SQL table definitions [[Category:Extension:Translate{{#translation:}}]] 0yxrakpjqofxcvad765lyphcmss6476 5386812 5386810 2022-07-28T19:15:23Z ThisCarthing 17456337 Created page with "=== Nachricht ===" wikitext text/x-wiki <languages/> {{Extension-Translate}} Die Übersetzungserweiterung lässt sich auf viele Arten erweitern. Die einfachste Möglichkeit, um die Übersetzungserweiterung zu ergänzen, ist, neue Dateiformate (Link auf Abschnitt) oder neue Nachrichtengruppen (Link auf Abschnitt) zu unterstützen. Manchmal ist es auch sinnvoll, eine neue Nachrichtenprüfung zu schreiben (Link auf Abschnitt) oder die Übersetzungserweiterung durch Hooks zu erweitern (Link auf Abschnitt). Manchmal reicht es aus, die vorhandene {{ll|Help:Extension:Translate/API#Web-API|Web-API}} zu nutzen. Zusätzlich zu den bereits erwähnten Konzepten gibt es viele weitere, wichtige Konzepte und Klassen der Übersetzungserweiterung, die nützlich sind, um die Übersetzungserweiterung zu verändern. Diese Seite soll umfassend und detailliert alle Komponenten der Übersetzungserweiterung erläutern. == Primäre erweiterbare Komponenten == === WebAPI === * detaillierte Dokumentation der [[Special:Help:Extension:Translate/API|API]] Zusätzlich zu Hooks und Oberflächen, die nur über PHP-Code genutzt werden können, bietet die WebAPI Zugriff auf viele Nachrichtengruppen und Informationen und Aktionen rund um das Thema Übersetzen. Sie basiert auf dem [[Special:MyLanguage/API:Main page|MediaWiki-API-Framework]] und unterstützt viele Ausgabeformate wie JSON und XML. === Dateiformatunterstützung (FFS) === * ''Detaillierte Dokumentation der [[Special:MyLanguage/Help:Extension:Translate/File format support|Dateiformatunterstützung]]'' * ''Anleitung zum Schreiben von [[Special:MyLanguage/Help:Extension:Translate/File format support tutorial|Dateiformatunterstützungsklassen]]'' Die Übersetzungserweiterung unterstützt die Übersetzung von Nicht-Wiki-Inhalten wie Software-Nachrichten über Dateiformatunterstützungsklassen (FFS). Diese Klassen implementieren die FFS-Oberfläche und abstrahieren das Parsen und Generieren von Dateiinhalten. Die FFS-Klassen werden von der FileBasedMessageGroup-Klasse über die [[Special:MyLanguage/Help:Extension:Translate/Group configuration|YAML-Konfigurationsdateien]] genutzt. === Nachrichtengruppen === * ''In-depth documentation about [[Special:MyLanguage/Help:Extension:Translate/Message groups|message groups]]'' Message groups bring together a collection of messages. They come in various types: translatable pages, SVG files or software interface messages stored in various file formats. Each message group instance has a unique identifier, name and description. In the code message groups are primarily referenced by their identifier, while the <code>MessageGroups</code> class can be used to get the instances for a given id. Message groups can also control many translation process related actions like allowed translation languages and the message group workflow states. Usually these behaviors fallback to the global defaults. The two primary ways to register message groups to Translate are the [[Special:MyLanguage/Help:Extension:Translate/Hooks|TranslatePostInitGroups hook]] and [[Special:MyLanguage/Help:Extension:Translate/Group configuration example|YAML configuration]]. <div lang="en" dir="ltr" class="mw-content-ltr"> === Translation aids (helpers) === </div> * ''In-depth documentation about [[Special:MyLanguage/Help:Extension:Translate/Translation aids|translation aids]]'' Translation aids are little modules that provide helpful and necessary information for the translator when translating. Different aids can provide suggestions from translation memory and machine translation, documentation about the message or even such a basic thing as the message definition – the text that needs to be translated. Translate comes with many aid classes. Currently there is no hook to add new classes. Each class that extends the TranslationAid class only needs to implement one method called getData. It should return the information in structured format (nested arrays), which is then exposed via ApiQueryTranslationAids WebAPI module. In addition to the aid class, changes are needed to actually use the provided data in the translation editor(s). One special case of translation aids are machine translation services. See the next section. <div lang="en" dir="ltr" class="mw-content-ltr"> === Web services === </div> Adding more machine translation services can easily be done by extending the TranslationWebService class. See the webservices subdirectory for examples. You will need some basic information to implement such a class: * URL for the service * What language pairs are supported * Whether they use language codes that differ from the codes used in MediaWiki * Whether the service needs an API key When you have this information, it is straightforward to write the mapCode, doPairs and doRequest methods. You should use the TranslationWebServiceException to signal errors. The errors are automatically logged and tracked, and if the service goes down, it will automatically be suspended to avoid unnecessary requests to it. The suggestions will automatically be displayed in the translation editor via the MachineTranslationAid class and the ApiQueryTranslationAids WebAPI module. See also $wgTranslateTranslationServices to see how those services are registered. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message checkers === </div> * ''[[Special:MyLanguage/Help:Extension:Translate/Group configuration|How to define checkers for file based message groups]]'' We use computers to catch simple errors in translations, like unbalanced parenthesis or failing to use a variable placeholder. These checkers can emit warnings that are displayed in the translation editor (constantly updating). Any warning present in saved translation will also mark the translation as outdated (fuzzy in jargon). Each message group determines which checks it uses. <div lang="en" dir="ltr" class="mw-content-ltr"> == Other core components == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Message collection === </div> Message collection provides access to the list of messages for a message group. It is used to load a set of languages for certain group in a certain language. It provides paging and filtering functionality. There is currently a limitation that all messages in a collection must be in the same namespace. This prevents the creation of aggregate groups that include groups which have messages in different namespaces. Here is short a example of how to use message collection to load all Finnish translations of group ''core'' and print the first ten of them: <syntaxhighlight lang=php> $group = MessageGroups::getGroup( 'core' ); $collection = $group->initCollection( 'fi' ); $collection->filter( 'ignored' ); $collection->filter( 'translated', false ); $collection->loadTranslations(); $collection->slice( 0, 10 ); foreach ( $collection->keys() as $mkey => $title ) { echo $title->getPrefixedText() . ': '; echo $collection[$mkey]->translation() . "\n\n"; } </syntaxhighlight> === Nachricht === <div lang="en" dir="ltr" class="mw-content-ltr"> == Utility classes == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Font finder === </div> When rendering bitmap graphics, suitable fonts are needed for each language or script. To solve this problem, the FCFontFinder class was written. It uses the <code>fc-match</code> command of the package <code>fontconfig</code> (so this doesn't work on Windows) to find a suitable font. Many additional fonts should be installed on the server to make this useful. It can either return a path to a font file or the name of the font, whichever is more suitable. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message group cache === </div> The messages of file-based message groups are stored in CDB files. Each language of each group has its own CDB cache file. The reason for cache files are twofold. First they provide constant and efficient access to message data avoiding the potentially expensive parsing of files in various places. For example the list of message keys for each group can be loaded efficiently when rebuilding a message index. The second reason is that the cache files are used together with the translations in the wiki to process external message changes. Having a snapshot of the state of translations in files and wiki (hopefully consistent at that point) allows us to automatically deduct whether something has been changed in the wiki or externally and make intelligent choices, leaving only real conflicts (messages changed both externally and on the wiki since last snapshot) to be resolved by the translation administrator. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message group utilities === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Message index === </div> Message index is a reverse map of all known messages. It provides efficient answer to the questions ''is this a known message'' and ''what groups does this message belong to''. It needs to be fast for single and multiple message key lookups. Multiple different backends are implemented, with different trade-offs. *Serialized file is fast to parse, but don't provide random access and is very memory inefficient when the number of keys grow. *CDB file takes more disk space, but provides random access and reasonably fast lookups, while loading everything into memory is slower. *Database backend provides efficient random access and full load with the expense of little slower individual lookups. It also doesn't need to write to any files avoiding any permission problems. *Also memory backend (memcached, apc) is provided, which could be useful alternatives to database backend in multiple server setups to reduce database contention. Message index does not support incremental rebuilds. Thus rebuilding the index gets relatively resource intensive when the number of message groups and message keys increase. Depending on the message group, this might involve parsing files or doing database queries and loading the definitions, which can take a lot of memory. The message index rebuilding is triggered in various places in Translate, and by default it is executed immediately during the request. As it gets slower, it can be delayed via the MediaWiki job queue and run outside of web requests. === Message table === === Metadata table === === Revtag === === Stats code === === String matcher/mangler === === Ttmserver (translation memory) === * ''In-depth documentation at [[Special:MyLanguage/Help:Extension:Translate/Translation_memories|Translation memories]].'' * ''Blog post of history of this feature at [http://laxstrom.name/blag/2012/09/07/translation-memory-all-wikimedia-wikis/ Niklas' blog].'' Ttmserver is the name of translation memory interface. It supports multiple backends for inserting and querying translation suggestions. The code is located under <code>ttmserver</code> directory. === Misc stuff: RC integration, preferences, toolbox, jobs === == Repository layout == Files in the root of the repository include: * Standard MediaWiki extensions files like <code>Translate.php</code>, translations and some documentation files like <code>hooks.txt</code> and <code>README</code> which includes change notes. * Major translate classes like <code>MessageCollection</code> and <code>Message</code> and some misc utilities not yet moved under utils. Rest of the code is under subdirectories. Major parts have their own subdirectories each: * <code>api</code> for WebAPI code * <code>ffs</code> for file format support code * <code>messagegroups</code> for message groups * <code>scripts</code> for command line scripts * <code>tag</code> for page translation code * <code>ttmserver</code> for translation memory code * <code>specials</code> for all special pages * <code>tests</code> for all PHP unit tests Most of the code is under utils. Some additional folders for non-code: * <code>data</code> for miscellaneous data files * <code>libs</code> for bundled library dependencies * <code>resources</code> for all css, scripts and images * <code>sql</code> for all SQL table definitions [[Category:Extension:Translate{{#translation:}}]] sp4tgu9meg8sdcmxw3ouiqq72uz4xrk 5386814 5386812 2022-07-28T19:15:37Z ThisCarthing 17456337 Created page with "== Weitere Kernkomponenten ==" wikitext text/x-wiki <languages/> {{Extension-Translate}} Die Übersetzungserweiterung lässt sich auf viele Arten erweitern. Die einfachste Möglichkeit, um die Übersetzungserweiterung zu ergänzen, ist, neue Dateiformate (Link auf Abschnitt) oder neue Nachrichtengruppen (Link auf Abschnitt) zu unterstützen. Manchmal ist es auch sinnvoll, eine neue Nachrichtenprüfung zu schreiben (Link auf Abschnitt) oder die Übersetzungserweiterung durch Hooks zu erweitern (Link auf Abschnitt). Manchmal reicht es aus, die vorhandene {{ll|Help:Extension:Translate/API#Web-API|Web-API}} zu nutzen. Zusätzlich zu den bereits erwähnten Konzepten gibt es viele weitere, wichtige Konzepte und Klassen der Übersetzungserweiterung, die nützlich sind, um die Übersetzungserweiterung zu verändern. Diese Seite soll umfassend und detailliert alle Komponenten der Übersetzungserweiterung erläutern. == Primäre erweiterbare Komponenten == === WebAPI === * detaillierte Dokumentation der [[Special:Help:Extension:Translate/API|API]] Zusätzlich zu Hooks und Oberflächen, die nur über PHP-Code genutzt werden können, bietet die WebAPI Zugriff auf viele Nachrichtengruppen und Informationen und Aktionen rund um das Thema Übersetzen. Sie basiert auf dem [[Special:MyLanguage/API:Main page|MediaWiki-API-Framework]] und unterstützt viele Ausgabeformate wie JSON und XML. === Dateiformatunterstützung (FFS) === * ''Detaillierte Dokumentation der [[Special:MyLanguage/Help:Extension:Translate/File format support|Dateiformatunterstützung]]'' * ''Anleitung zum Schreiben von [[Special:MyLanguage/Help:Extension:Translate/File format support tutorial|Dateiformatunterstützungsklassen]]'' Die Übersetzungserweiterung unterstützt die Übersetzung von Nicht-Wiki-Inhalten wie Software-Nachrichten über Dateiformatunterstützungsklassen (FFS). Diese Klassen implementieren die FFS-Oberfläche und abstrahieren das Parsen und Generieren von Dateiinhalten. Die FFS-Klassen werden von der FileBasedMessageGroup-Klasse über die [[Special:MyLanguage/Help:Extension:Translate/Group configuration|YAML-Konfigurationsdateien]] genutzt. === Nachrichtengruppen === * ''In-depth documentation about [[Special:MyLanguage/Help:Extension:Translate/Message groups|message groups]]'' Message groups bring together a collection of messages. They come in various types: translatable pages, SVG files or software interface messages stored in various file formats. Each message group instance has a unique identifier, name and description. In the code message groups are primarily referenced by their identifier, while the <code>MessageGroups</code> class can be used to get the instances for a given id. Message groups can also control many translation process related actions like allowed translation languages and the message group workflow states. Usually these behaviors fallback to the global defaults. The two primary ways to register message groups to Translate are the [[Special:MyLanguage/Help:Extension:Translate/Hooks|TranslatePostInitGroups hook]] and [[Special:MyLanguage/Help:Extension:Translate/Group configuration example|YAML configuration]]. <div lang="en" dir="ltr" class="mw-content-ltr"> === Translation aids (helpers) === </div> * ''In-depth documentation about [[Special:MyLanguage/Help:Extension:Translate/Translation aids|translation aids]]'' Translation aids are little modules that provide helpful and necessary information for the translator when translating. Different aids can provide suggestions from translation memory and machine translation, documentation about the message or even such a basic thing as the message definition – the text that needs to be translated. Translate comes with many aid classes. Currently there is no hook to add new classes. Each class that extends the TranslationAid class only needs to implement one method called getData. It should return the information in structured format (nested arrays), which is then exposed via ApiQueryTranslationAids WebAPI module. In addition to the aid class, changes are needed to actually use the provided data in the translation editor(s). One special case of translation aids are machine translation services. See the next section. <div lang="en" dir="ltr" class="mw-content-ltr"> === Web services === </div> Adding more machine translation services can easily be done by extending the TranslationWebService class. See the webservices subdirectory for examples. You will need some basic information to implement such a class: * URL for the service * What language pairs are supported * Whether they use language codes that differ from the codes used in MediaWiki * Whether the service needs an API key When you have this information, it is straightforward to write the mapCode, doPairs and doRequest methods. You should use the TranslationWebServiceException to signal errors. The errors are automatically logged and tracked, and if the service goes down, it will automatically be suspended to avoid unnecessary requests to it. The suggestions will automatically be displayed in the translation editor via the MachineTranslationAid class and the ApiQueryTranslationAids WebAPI module. See also $wgTranslateTranslationServices to see how those services are registered. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message checkers === </div> * ''[[Special:MyLanguage/Help:Extension:Translate/Group configuration|How to define checkers for file based message groups]]'' We use computers to catch simple errors in translations, like unbalanced parenthesis or failing to use a variable placeholder. These checkers can emit warnings that are displayed in the translation editor (constantly updating). Any warning present in saved translation will also mark the translation as outdated (fuzzy in jargon). Each message group determines which checks it uses. == Weitere Kernkomponenten == <div lang="en" dir="ltr" class="mw-content-ltr"> === Message collection === </div> Message collection provides access to the list of messages for a message group. It is used to load a set of languages for certain group in a certain language. It provides paging and filtering functionality. There is currently a limitation that all messages in a collection must be in the same namespace. This prevents the creation of aggregate groups that include groups which have messages in different namespaces. Here is short a example of how to use message collection to load all Finnish translations of group ''core'' and print the first ten of them: <syntaxhighlight lang=php> $group = MessageGroups::getGroup( 'core' ); $collection = $group->initCollection( 'fi' ); $collection->filter( 'ignored' ); $collection->filter( 'translated', false ); $collection->loadTranslations(); $collection->slice( 0, 10 ); foreach ( $collection->keys() as $mkey => $title ) { echo $title->getPrefixedText() . ': '; echo $collection[$mkey]->translation() . "\n\n"; } </syntaxhighlight> === Nachricht === <div lang="en" dir="ltr" class="mw-content-ltr"> == Utility classes == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Font finder === </div> When rendering bitmap graphics, suitable fonts are needed for each language or script. To solve this problem, the FCFontFinder class was written. It uses the <code>fc-match</code> command of the package <code>fontconfig</code> (so this doesn't work on Windows) to find a suitable font. Many additional fonts should be installed on the server to make this useful. It can either return a path to a font file or the name of the font, whichever is more suitable. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message group cache === </div> The messages of file-based message groups are stored in CDB files. Each language of each group has its own CDB cache file. The reason for cache files are twofold. First they provide constant and efficient access to message data avoiding the potentially expensive parsing of files in various places. For example the list of message keys for each group can be loaded efficiently when rebuilding a message index. The second reason is that the cache files are used together with the translations in the wiki to process external message changes. Having a snapshot of the state of translations in files and wiki (hopefully consistent at that point) allows us to automatically deduct whether something has been changed in the wiki or externally and make intelligent choices, leaving only real conflicts (messages changed both externally and on the wiki since last snapshot) to be resolved by the translation administrator. <div lang="en" dir="ltr" class="mw-content-ltr"> === Message group utilities === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Message index === </div> Message index is a reverse map of all known messages. It provides efficient answer to the questions ''is this a known message'' and ''what groups does this message belong to''. It needs to be fast for single and multiple message key lookups. Multiple different backends are implemented, with different trade-offs. *Serialized file is fast to parse, but don't provide random access and is very memory inefficient when the number of keys grow. *CDB file takes more disk space, but provides random access and reasonably fast lookups, while loading everything into memory is slower. *Database backend provides efficient random access and full load with the expense of little slower individual lookups. It also doesn't need to write to any files avoiding any permission problems. *Also memory backend (memcached, apc) is provided, which could be useful alternatives to database backend in multiple server setups to reduce database contention. Message index does not support incremental rebuilds. Thus rebuilding the index gets relatively resource intensive when the number of message groups and message keys increase. Depending on the message group, this might involve parsing files or doing database queries and loading the definitions, which can take a lot of memory. The message index rebuilding is triggered in various places in Translate, and by default it is executed immediately during the request. As it gets slower, it can be delayed via the MediaWiki job queue and run outside of web requests. === Message table === === Metadata table === === Revtag === === Stats code === === String matcher/mangler === === Ttmserver (translation memory) === * ''In-depth documentation at [[Special:MyLanguage/Help:Extension:Translate/Translation_memories|Translation memories]].'' * ''Blog post of history of this feature at [http://laxstrom.name/blag/2012/09/07/translation-memory-all-wikimedia-wikis/ Niklas' blog].'' Ttmserver is the name of translation memory interface. It supports multiple backends for inserting and querying translation suggestions. The code is located under <code>ttmserver</code> directory. === Misc stuff: RC integration, preferences, toolbox, jobs === == Repository layout == Files in the root of the repository include: * Standard MediaWiki extensions files like <code>Translate.php</code>, translations and some documentation files like <code>hooks.txt</code> and <code>README</code> which includes change notes. * Major translate classes like <code>MessageCollection</code> and <code>Message</code> and some misc utilities not yet moved under utils. Rest of the code is under subdirectories. Major parts have their own subdirectories each: * <code>api</code> for WebAPI code * <code>ffs</code> for file format support code * <code>messagegroups</code> for message groups * <code>scripts</code> for command line scripts * <code>tag</code> for page translation code * <code>ttmserver</code> for translation memory code * <code>specials</code> for all special pages * <code>tests</code> for all PHP unit tests Most of the code is under utils. Some additional folders for non-code: * <code>data</code> for miscellaneous data files * <code>libs</code> for bundled library dependencies * <code>resources</code> for all css, scripts and images * <code>sql</code> for all SQL table definitions [[Category:Extension:Translate{{#translation:}}]] rtyxhmkdkzj5wplzblm1q7e3053korw Manual:Pywikibot/category.py/en 100 1298284 5387847 5299628 2022-07-29T10:19:57Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} == Syntax == The syntax is: python pwb.py category action [-option] where action can be one of the following. {| class="wikitable |- | <code>add</code> || mass-add a category to a list of pages |- | <code>remove</code> || remove category tag from all pages in a category |- | <code>move</code> || move all pages in a category to another category |- | <code>tidy</code> || tidy up a category by moving its articles into subcategories |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || show a tree of subcategories of a given category |- | <code>listify</code> || make a list of all of the articles that are in a category |} and option can be one of the following. === Options for <code>add</code> action === {| class="wikitable" |- | <code>-person</code> || sort persons by their last name |- | <code>-create</code> || If a page doesn't exist, do not skip it, create it instead |- | <code>-redirect</code> || Follow redirects |} For this action, [[#page_generators|page generator options]] are supported. === Options for <code>listify</code> action === * -overwrite - This overwrites the current page with the list even if something is already there. * -showimages - This displays images rather than linking them in the list. * -talkpages - This outputs the links to talk pages of the pages to be listified in addition to the pages themselves. === Options for <code>remove</code> action === * -nodelsum - This specifies not to use the custom edit summary as the deletion reason. Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English. === Options for <code>move</code> action === {| class="wikitable" | -hist || Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category. |- | -nodelete || Don't delete the old category after move |- | -nowb || Don't update the wikibase repository |- | -allowsplit || If that option is not set, it only moves the talk and main page together. |- | -mvtogether || Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist. |- | -keepsortkey | Use sortKey of the old category also for the new category. If not specified, sortKey is removed. An alternative method to keep sortKey is to use -inplace option. |} === Options for <code>tidy</code> action === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | Filter the articles in the specified namespaces. Separate multiple namespace numbers or names with commas. Examples: -ns:0,2,4 -ns:Help,MediaWiki |} === Options for several actions === {| class="wikitable" | -rebuild || reset the database |- | -from: | The category to move from (for the move option) Also, the category to remove from in the remove option Also, the category to make a list of in the listify option See note below table. |- | -to: | The category to move to (for the move option) Also, the name of the list to make in the listify option See note below table. |- | -batch || Don't prompt to delete emptied categories (do it automatically). |- | -summary: || Pick a custom edit summary for the bot. |- | -inplace || Use this flag to change categories in place rather than rearranging them. |- | -recurse || Recurse through all subcategories of categories. |- | -pagesonly || While removing pages from a category, keep the subpage links and do not remove them |- | -match || Only work on pages whose titles match the given regex (for move and remove actions). |- | -depth: || The max depth limit beyond which no subcategories will be listed. |} {{note|1= For options ''-from'' and ''-to'': If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters. For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>. For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent. For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>. This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case. For example, to create a new category from a list of persons, type: python pwb.py category add -person and follow the on-screen instructions. Or to do it all from the command-line, use the following syntax: python pwb.py category move -from:US -to:"United States" This will move all pages in the category US to the category United States. }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} == See also == * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] g34o16m50p6v817wwi4kv1n87wwnuuc Manual:Pywikibot/category.py/tr 100 1298353 5387853 5299635 2022-07-29T10:20:02Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} == Sözdizimi == Sözdizimi: python pwb.py category action [-option] eylem şunlardan biri olabilir: {| class="wikitable |- | <code>add</code> || bir sayfa listesine toplu olarak bir kategori ekleyin |- | <code>remove</code> || kategori etiketini bir kategorideki tüm sayfalardan kaldırın |- | <code>move</code> || bir kategorideki tüm sayfaları başka bir kategoriye taşı |- | <code>tidy</code> || maddelerini alt kategorilere taşıyarak bir kategoriyi düzenleyin |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || belirli bir kategorinin alt kategorilerinin bir ağacını göster |- | <code>listify</code> || bir kategorideki tüm maddelerin bir listesini yapın |} ve seçenek şunlardan biri olabilir: === "<code>add</code>" işlemi için seçenekler: === {| class="wikitable" |- | <code>-person</code> || kişileri soyadlarına göre sırala |- | <code>-create</code> || bir sayfa yoksa, atlamayın, onun yerine oluşturun |- | <code>-redirect</code> || Yönlendirmeleri takip edin |} Bu eylem için [[#page_generators|sayfa oluşturucu seçenekleri]] desteklenmektedir. === <code>listify</code> işlemi için seçenekler: === * -overwrite - Bu, zaten orada bir şey olsa bile listeyle mevcut sayfanın üzerine yazar. * -showimages - Bu, onları listeye bağlamak yerine görüntüler. * -talkpages - Bu, sayfaların kendisine ek olarak, listelenecek sayfaların tartışma sayfalarının bağlantılarını çıkarır. === "<code>remove</code>" işlemi için seçenekler: === * -nodelsum - Bu, silme nedeni olarak özel düzenleme özetinin kullanılmamasını belirtir. Bunun yerine, İngilizce "Category was disbanded" olan dil için varsayılan silme nedenini kullanır. "<code>move</code>" işlemi için seçenekler: {| class="wikitable" | -hist || Kaynak kategorisinin ayrıntılı sayfa geçmişini içeren hedef kategorinin konuşma sayfasında güzel bir vikitablosu oluşturur. |- | -nodelete || Taşındıktan sonra eski kategoriyi silmeyin |- | -nowb || Wikibase feposunu güncellemeyin |- | -allowsplit || Bu seçenek ayarlanmadıysa, yalnızca tartışma ve ana sayfayı birlikte taşır. |- | -mvtogether || Yalnızca hedef sayfa (ve -allowsplit ayarlanmamışsa tartışma sayfası) yoksa bir kategorinin sayfalarını/alt kategorilerini taşıyın. |- | -keepsortkey | Yeni kategori için de eski kategorinin sortKey'i kullanın. Belirtilmezse sortKey kaldırılır. SortKey'i tutmanın alternatif bir yöntemi -inplace seçeneğini kullanmaktır. |} === "<code>tidy</code>" işlemi için seçenekler: === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | Maddeleri belirtilen ad alanlarında filtreleyin. Birden çok ad alanı numarasını veya adı virgülle ayırın. Örnekler: -ns:0,2,4 -ns:Help,MediaWiki |} === "$1" işlemi için seçenekler: === {| class="wikitable" | -rebuild || veritabanını sıfırla |- | -from: | Taşınacak kategori (move seçeneği için) Ayrıca, remove seçeneğinde kaldırılacak kategori Ayrıca, listify seçeneğinde liste yapılacak kategori <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | Taşınacak kategori (move seçeneği için) Ayrıca, listify seçeneğinde yapılacak listenin adı <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || Boşaltılan kategorileri silmenizi istemeyin (otomatik olarak yapın). |- | -summary: || Bot için özel bir düzenleme özeti seçin. |- | -inplace || Kategorileri yeniden düzenlemek yerine yerinde değiştirmek için bu işareti kullanın. |- | -recurse || Tüm alt kategorilerde tekrarlayın. |- | -pagesonly || Bir kategoriden sayfaları kaldırırken, alt sayfa bağlantılarını saklayın ve kaldırmayın. |- | -match || Yalnızca başlıkları verilen düzenli ifadeyle eşleşen sayfalarda çalışın (move ve remove eylemleri için). |- | -depth: || Alt kategorilerin listelenmeyeceği maksimum derinlik sınırı. |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> Kategori adlarında boşluklar varsa, adların ayrı parametreler olarak ele alınmaması için kabuğunuzda özel bir sözdizimi kullanmanız gerekebilir. Örneğin, BASH'de tek tırnak kullanın, ör. <code>-from:'Polar bears'</code>. <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> ''tidy'' ve ''tree'' eylemleri için bot, kategori yapısını yerel olarak <code>category.dump</code> içinde saklayacaktır. Bu, zamandan ve sunucu yükünden tasarruf sağlar, ancak bu verileri daha sonra kullanırsa güncelliğini yitirebilir; bu durumda <code>-rebuild</code> parametresini kullanın. Örneğin, bir kişi listesinden yeni bir kategori oluşturmak için şunu yazın: python pwb.py category add -person ve ekrandaki talimatları izleyin. Veya hepsini komut satırından yapmak için aşağıdaki sözdizimini kullanın: python pwb.py category move -from:US -to:"United States" Bu, US kategorisindeki tüm sayfaları United States kategorisine taşıyacaktır. }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} == Ayrıca bakınız == * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] pwmu2gatnoxk11ezalh05zgkjaw3rbj Manual:Pywikibot/category.py/pl 100 1303547 5387850 5299633 2022-07-29T10:20:00Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Syntax == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The syntax is: </div> python pwb.py category action [-option] <div lang="en" dir="ltr" class="mw-content-ltr"> where action can be one of the following. </div> {| class="wikitable |- | <code>add</code> || <span lang="en" dir="ltr" class="mw-content-ltr">mass-add a category to a list of pages</span> |- | <code>remove</code> || <span lang="en" dir="ltr" class="mw-content-ltr">remove category tag from all pages in a category</span> |- | <code>move</code> || <span lang="en" dir="ltr" class="mw-content-ltr">move all pages in a category to another category</span> |- | <code>tidy</code> || <span lang="en" dir="ltr" class="mw-content-ltr">tidy up a category by moving its articles into subcategories</span> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <span lang="en" dir="ltr" class="mw-content-ltr">show a tree of subcategories of a given category</span> |- | <code>listify</code> || <span lang="en" dir="ltr" class="mw-content-ltr">make a list of all of the articles that are in a category</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> and option can be one of the following. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>add</code> action</span> === {| class="wikitable" |- | <code>-person</code> || <span lang="en" dir="ltr" class="mw-content-ltr">sort persons by their last name</span> |- | <code>-create</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If a page doesn't exist, do not skip it, create it instead</span> |- | <code>-redirect</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Follow redirects</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> For this action, [[#page_generators|page generator options]] are supported. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>listify</code> action</span> === * -overwrite - <span lang="en" dir="ltr" class="mw-content-ltr">This overwrites the current page with the list even if something is already there.</span> * -showimages - <span lang="en" dir="ltr" class="mw-content-ltr">This displays images rather than linking them in the list.</span> * -talkpages - <span lang="en" dir="ltr" class="mw-content-ltr">This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>remove</code> action</span> === * -nodelsum - <span lang="en" dir="ltr" class="mw-content-ltr">This specifies not to use the custom edit summary as the deletion reason.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Options for <code>move</code> action === </div> {| class="wikitable" | -hist || <span lang="en" dir="ltr" class="mw-content-ltr">Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</span> |- | -nodelete || <span lang="en" dir="ltr" class="mw-content-ltr">Don't delete the old category after move</span> |- | -nowb || <span lang="en" dir="ltr" class="mw-content-ltr">Don't update the wikibase repository</span> |- | -allowsplit || <span lang="en" dir="ltr" class="mw-content-ltr">If that option is not set, it only moves the talk and main page together.</span> |- | -mvtogether || <span lang="en" dir="ltr" class="mw-content-ltr">Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist.</span> |- | -keepsortkey | <span lang="en" dir="ltr" class="mw-content-ltr">Use sortKey of the old category also for the new category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not specified, sortKey is removed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alternative method to keep sortKey is to use -inplace option.</span> |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>tidy</code> action</span> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Filter the articles in the specified namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Separate multiple namespace numbers or names with commas.</span> Przykłady: -ns:0,2,4 -ns:Help,MediaWiki |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for several actions</span> === {| class="wikitable" | -rebuild || <span lang="en" dir="ltr" class="mw-content-ltr">reset the database</span> |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} == Zobacz też == * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] ihc2m8x0sqx7a4s1w8kgbtxuxtim76i Extension:NaylorAMS 102 1312983 5387466 5224462 2022-07-28T22:36:17Z MyWikis-JeffreyWang 17412845 wikitext text/x-wiki <languages/> {{PluggableAuth Plugin}} {{Extension|templatemode = |name = NaylorAMS |status = stable |type1 = user identity |type2 = |hook1 = |hook2 = |newhook1 = |newhook2 = |username = |author = [[User:MyWikis-JeffreyWang|Jeffrey Wang]] for MyWikis LLC |maintainer = [https://www.mywikis.com MyWikis LLC] |description = <translate><!--T:1--> Allows authentication using Naylor Association Management Software (Timberlake)</translate> |image = |imagesize = |version = 0.1.0 |update = |version preview = |update preview = |compatibility policy = master |mediawiki = 1.31+ |php = 7.0+ |needs-updatephp = no |composer = |table1 = |table2 = |license = GPL-2.0 |download = {{WikimediaDownload}}{{GithubDownload|mywikis|NaylorAMS|mastertarball=1}} |readme = {{git file|project=mediawiki/extensions/NaylorAMS|file=README|branch=HEAD|text=README}} |changelog = |example = |namespace = |parameters = <!-- configuration parameters, for use in LocalSettings.php --> |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |phabricator = |vagrant-role = }} The '''Naylor AMS''' extension extends {{ll|Extension:PluggableAuth|PluggableAuth}} to provide authentication for organizations using [https://www.naylor.com/member-management-solutions/association-management-software/ Naylor Association Management Software] (codename Timberlake). This extension will take the username, first and last name, and email address of a user from your organization's Naylor database and create a local MediaWiki account with the same username, email, and full name if one doesn't exist; otherwise, if a user with the same username exists, it logs them back into the local MediaWiki account. <translate> == Installation == <!--T:2--> </translate> {{Note|1=This extension requires {{ll|Extension:PluggableAuth|PluggableAuth}} 5.x to be installed first.}} The PHP cURL extension is required for this MediaWiki extension. {{ExtensionInstall |download-link = [https://github.com/mywikis/NaylorAMS/archive/main.tar.gz Download] |registration = required }} <translate> == Configuration parameters == <!--T:3--> </translate> For more information about these terms, please refer to the [https://masie.membershipsoftware.org/files/Naylor%20API%20Documentation.pdf Naylor AMS API documentation]. ; $wgNaylorAMS_BaseUrl : The base URL for your login system, provided by Naylor. Do not add a trailing slash at the end of the string. ('''required''') ; $wgNaylorAMS_SecurityKey : The security key provided by Naylor. ('''required''') ; $wgNaylorAMS_UsernameDenyList : An array of strings, with each string containing a local username. Used to prevent login via SSO to local-only accounts. Case sensitive; needs to follow MediaWiki username conventions. By default, the log in button says "Log in with Naylor AMS". To change the label, edit MediaWiki:Naylorams-loginbtn-text. <translate> == Disclaimer == <!--T:4--> </translate> This extension is ''not'' maintained by Naylor, nor has it been sponsored by Naylor. It was written by and is maintained by [https://www.mywikis.com/ MyWikis LLC] for the purpose of serving its customers who use Naylor AMS. In addition, the extension is currently not compatible with PluggableAuth 6.0 and above. Use the latest version of PluggableAuth 5.x in the meantime. <translate> == See also == <!--T:5--> </translate> * {{ll|Extension:PluggableAuth}} * {{ll|Extension:SimpleSAMLphp}} * {{ll|Extension:LDAPAuthentication2}} {{Used by|mywikis=1}} [[Category:Extensions by MyWikis{{#translation:}}]] [[Category:PluggableAuth plugins{{#translation:}}]] pynz3edxbgfcdyd0euv0x8naktz5xin Growth/FAQ 0 1316145 5387695 5378628 2022-07-29T05:43:34Z Meghmollar2017 11918785 /* Who can be a mentor? */ wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''<translate><!--T:1--> Welcome to the Growth team Frequently Asked Questions (FAQ).</translate>''' <translate><!--T:2--> We hope you will find the information you need. However, if it is not the case, [[<tvar name="1">Talk:Growth</tvar>|let us know]].</translate> ''<translate><!--T:3--> Note for translators: this page is updated regularly, which may impact your work. We are doing our best to avoid these disturbances.</translate>'' <translate> == General == <!--T:4--> </translate> {{Anchor|features}} <translate> === Which features are you working on? === <!--T:5--> </translate> * <translate><!--T:6--> [[<tvar name="1">Special:MyLanguage/Growth/Feature summary#NH</tvar>|'''Newcomer homepage''']]: a new special page, the best place for a newcomer to get started. It includes:</translate> ** <translate><!--T:7--> [[<tvar name="1">Special:MyLanguage/Growth/Feature summary#NT</tvar>|'''Newcomer tasks''']]: a feed of task suggestions that help newcomers learn to edit. Newcomers have been making [[<tvar name="2">NEWTEA</tvar>|productive edits]] through this feed! [[<tvar name="3">Help:Growth/Tools/Suggested edits</tvar>|Know more about this tool]].</translate> ** <translate><!--T:8--> '''Mentorship module''' [optional module]: each newcomers has a direct link to an experienced user. This way, they can ask questions about editing Wikipedia, less the need to find where to ask for assistance.</translate> ** <translate><!--T:9--> '''Impact module''': the user sees how many pages views articles they edit received.</translate> * <translate><!--T:10--> [[<tvar name="1">Special:MyLanguage/Growth/Feature summary#HP</tvar>|'''Help panel''']]: a platform to provide resources to newcomers while they are editing. If they choose one of the suggested tasks on the newcomer homepage, they are guided step-by-step on the process of editing.</translate> * <translate><!--T:11--> '''[[<tvar name="1">Growth/Understanding first day</tvar>|Welcome Survey]]''': communities can know why newcomers create an account on Wikipedia.</translate> <translate><!--T:12--> You can have a look at '''[[<tvar name="1">Special:MyLanguage/Growth/Feature summary</tvar>|our features summary]]''' to know more about it. === On which wikis Growth features have been deployed? === <!--T:183--> <!--T:184--> You can find a list of wikis on our [[<tvar name="1">Special:MyLanguage/Growth/Deployment table</tvar>|Deployment table]]. This page lists features activation per wiki as well. </translate> {{anchor|NEWTEA}} <translate> === Are Growth features effective? === <!--T:185--> <!--T:13--> [[<tvar name="1">NEWTEA</tvar>|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in:</translate> * <translate><!--T:14--> the probability that newcomers make their first article edit (+11.6%)</translate> * <translate><!--T:15--> the probability that they are retained as editors</translate> * <translate><!--T:16--> the number of edits they make during their first couple of weeks on the wiki (+22%)</translate> <translate><!--T:17--> We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features.</translate> <translate><!--T:225--> This deployment has been achieved in October 2021.</translate> {{anchor|translate}} <translate> === The interface is partially translated. How can I change this? === <!--T:18--> </translate> [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <translate><!--T:247--> Interface translations are hosted at translatewiki.net.</translate>] <translate><!--T:20--> It takes up to one week to see new translations being deployed. <!--T:21--> Special pages names require a special process. For the following strings, [[<tvar name="1">Talk:Growth</tvar>|please contact us]] directly with the translations: <tvar name="2"><code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code></tvar>. </translate> {{anchor|enable|test}} <translate> === Can I test the features? === <!--T:22--> <!--T:23--> [[<tvar name="1">Growth/Deployment table</tvar>|On wikis where the Growth features are available]], and also on <tvar name="2">[https://test.wikipedia.org test.wikipedia.org]</tvar>, go to your [[<tvar name="3">Special:Preferences#mw-prefsection-personal</tvar>|user preferences]] on one of these wikis and then: </translate> * <translate><!--T:24--> enable the '''Help panel''' in the ''<tvar name="1">{{int|prefs-editing}}</tvar>'' tab.</translate> * <translate><!--T:25--> enable the '''Newcomer homepage''' in the ''<tvar name="1">{{int|prefs-personal}}</tvar>'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''.</translate> <translate><!--T:26--> Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work.</translate> {{anchor|get}} <translate> === How can my wiki get the features? === <!--T:27--> <!--T:28--> The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[<tvar name="1">#features</tvar>|these features]], with the following conditions. <!--T:29--> As detailed on [[<tvar name="1">Special:MyLanguage/Growth/Communities#Our%20focus</tvar>|our focus]], we will work with the following wikis by order of priority: </translate> # <translate><!--T:30--> Wikipedias in the set of our '''[[<tvar name="2">#pilot</tvar>|pilot wikis]]''' – we address all the feedback they give us.</translate> # <translate><!--T:31--> Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.</translate> # <translate><!--T:32--> All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</translate> <translate> === Do you plan to deploy the features outside of Wikipedia? === <!--T:226--> </translate> <translate><!--T:228--> We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</translate> <translate><!--T:229--> Please contact us [[<tvar name="1">Talk:Growth</tvar>|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project.</translate> <translate> <!--T:227--> We are considering working with [[<tvar name="1">Growth/Communities/Wikisource</tvar>|Wikisource communities]]. </translate> {{anchor|pilot|ambassador}} <translate> === Can you clarify what "Pilot wikis", "Control group wikis" and "Ambassadors" are? === <!--T:186--> <!--T:187--> '''Pilot wikis''' are wikis who have a close collaboration with the Growth team. They are involved in projects definitions and early review of the projects. They also test all prototypes first. The Growth team can contact some other wikis for some of these steps. <!--T:188--> As of <tvar name=2>{{ymd|2022|3|1}}</tvar>, our pilot wikis are: <tvar name="1">{{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}</tvar>. <!--T:239--> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[<tvar name="1">Special:MyLanguage/Growth/FAQ#ABtest</tvar>|under an A/B test process]]. <!--T:240--> As of <tvar name=2>{{ymd|2022|3|1}}</tvar>, the control group is composed of the Pilot wikis listed above, plus the following wikis: <tvar name="1">{{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}</tvar>. <!--T:189--> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". <!--T:190--> Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. === Can I use the Growth features on mobile ? On the official apps (iOS, Android)? === <!--T:175--> <!--T:176--> Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). == Access to the features == <!--T:33--> </translate> {{anchor|ABtest}} <translate> === How can new accounts get the features? === <!--T:34--> <!--T:36--> On wikis [[<tvar name="1">Growth/Deployment table</tvar>|where the Growth features have been deployed]], and where no [[<tvar name="2">A/B testing</tvar>|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. <!--T:35--> On wikis [[<tvar name="1">Growth/Deployment table</tvar>|where the Growth features have been deployed]], and where an [[<tvar name="2">A/B testing</tvar>|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences.</translate> <translate><!--T:241--> Wikis concerned by this A/B test are: <tvar name="1">{{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}</tvar>. === How can existing accounts get the features? === <!--T:37--> <!--T:38--> On wikis [[<tvar name="1">Growth/Deployment table</tvar>|where the Growth features have been deployed]], anyone can find the features [[<tvar name="2">#enable</tvar>|in their Preferences]]. === I host a workshop. How can I control if my students get the features when they create an account? === <!--T:39--> <!--T:40--> It is possible to have a link parameter to control access to the features: </translate> * <translate><!--T:41--> <tvar name="1"><code>Special:CreateAccount?geEnabled=1</code></tvar> will force Growth features at account creation</translate> * <translate><!--T:42--> <tvar name="1"><code>Special:CreateAccount?geEnabled=0</code></tvar> will force the default experience at account creation</translate> <translate> <!--T:43--> Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[<tvar name="1">Talk:Growth</tvar>|Please let us know]] if you plan to use these parameters. </translate> {{anchor|Homepage}} <translate> == Homepage == <!--T:44--> </translate> ''<translate><!--T:45--> The following items are only valid for the wikis [[<tvar name="1">Growth/Deployment table</tvar>|where the Growth features have been deployed]].</translate>'' <translate> === How to access the Homepage? === <!--T:46--> <!--T:47--> If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. <!--T:48--> If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. === My email is requested, or my email is displayed at the top of the Homepage. Why? === <!--T:49--> <!--T:50--> We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[<tvar name="1">Special:MyLanguage/Help:Notifications</tvar>|notifications]], like when they are mentioned by other users on wiki. <!--T:51--> The email address won't be visible by other users. Communication with other users all happen on the wiki. === The help links displayed on the homepage are not relevant. How to change them? === <!--T:177--> <!--T:178--> These links are [[<tvar name="1">#HP</tvar>|the same as on the Help panel]]. <!--T:179--> An admin can change these links using <tvar name="1"><code>Special:EditGrowthConfig</code></tvar>. <!--T:180--> We can assist you in this task. [[<tvar name="1">Talk:Growth</tvar>|Please contact us]] with your request; please provide a link to the community discussion that led to this change. == Suggested edits == <!--T:52--> === How does Suggested Edits work ? === <!--T:168--> ==== How topics and tasks are suggested? ==== <!--T:53--> <!--T:54--> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. <!--T:55--> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. <!--T:56--> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. <!--T:57--> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. <!--T:58--> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. === SuggestedEdits' supervision and troubleshooting === <!--T:169--> ==== Can I monitor which articles have been edited as Suggested edits? ==== <!--T:89--> <!--T:90--> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. ==== How to monitor which topics or which tasks need more articles? ==== <!--T:87--> <!--T:88--> Please use <tvar name="1"><code>Special:NewcomerTasksInfo</code></tvar>. ==== I don't have any task for a given combination. Is it normal? ==== <!--T:59--> <!--T:60--> Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. ==== A user uses the tools in an nonconstructive way. What can I do? ==== <!--T:95--> <!--T:96--> Overall, users make [[<tvar name="1">#NEWTEA</tvar>|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. <!--T:97--> The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: </translate> # <translate><!--T:98--> try to understand what the use tries to do,</translate> # <translate><!--T:99--> contact this user, explain the situation, ask them for details and guide them to a different path if it exists,</translate> # <translate><!--T:100--> if the nonconstructive behavior persists, then block the user.</translate> <translate> <!--T:101--> If repetitive and similar nonconstructive edits are made at your wiki, [[<tvar name="1">Talk:Growth</tvar>|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== <!--T:102--> <!--T:103--> Have you activated the Help panel in your preferences? If yes, [[<tvar name="1">Talk:Growth</tvar>|please let us know about this issue]]. </translate> {{anchor|config}} <translate> === Suggested edits configuration === <!--T:170--> ==== How to provide more tasks for newcomers? ==== <!--T:61--> <!--T:62--> Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: </translate> {| class="wikitable" !'''<translate><!--T:63--> Task</translate>''' !<translate><!--T:64--> Level of difficulty</translate> !<translate><!--T:65--> Goal of the task</translate> |- |<translate><!--T:66--> Copyedit article</translate> |<translate><!--T:67--> easy</translate> |<translate><!--T:68--> fix spelling, grammar and tone</translate> |- |<translate><!--T:69--> Add Links</translate> |<translate><!--T:70--> easy</translate> |<translate><!--T:71--> add links between articles</translate> |- |<translate><!--T:72--> Update article</translate> |<translate><!--T:73--> medium</translate> |<translate><!--T:74--> bring existing articles up-to-date</translate> |- |<translate><!--T:75--> Add References</translate> |<translate><!--T:76--> medium</translate> |<translate><!--T:77--> find sources for existing articles</translate> |- |<translate><!--T:78--> Expand article</translate> |<translate><!--T:79--> hard</translate> |<translate><!--T:80--> expand stubs to become sourced articles</translate> |} <translate> <!--T:81--> Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: </translate> * <translate><!--T:82--> Add other templates that match the definition of the task to <tvar name="1"><code>Special:EditGrowthConfig</code></tvar> on your wiki</translate> * <translate><!--T:83--> Add maintenance templates to more articles on your wiki.</translate> <translate> <!--T:84--> Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== <!--T:85--> <!--T:86--> It is not possible at the moment. [[<tvar name="1">Talk:Growth</tvar>|Please let us know]] about your potential project. === Structured tasks - Add a link === <!--T:172--> </translate> ''<translate><!--T:92--> The following items are only valid for the wikis [[<tvar name="1">Special:MyLanguage/Growth/Deployment table</tvar>|where ''Structured tasks - Add a link'' has been deployed]].</translate>'' <translate> ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== <!--T:191--> </translate> <translate><!--T:192--> "Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</translate> <translate><!--T:193--> Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</translate> <translate><!--T:194--> As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</translate> <translate><!--T:195--> Users have to decide if a link should be added or not added. These links are suggested by a machine.</translate> <translate> ==== Which wikis have Structured tasks - Add a link ? ==== <!--T:173--> <!--T:174--> You can find the list in the [[<tvar name="1">Special:MyLanguage/Growth/Deployment table</tvar>|deployment table]]. ==== What is the accuracy of Structured tasks - Add a link predictions? ==== <!--T:91--> <!--T:93--> The predictions are, on average, accurate at 70%. <!--T:94--> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. ==== Is there a limitation to the number of articles one can edit per day? ==== <!--T:231--> </translate> <translate><!--T:232--> We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</translate> <translate><!--T:233--> As a consequence, we have setup some quality gates.</translate> <translate><!--T:234--> As of January 2022, a user can edit up to 25 articles per day.</translate> <translate> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== <!--T:260--> <!--T:261--> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[<tvar name="1">:m:Special:MyLanguage/User:Jon Harald Søby/diffedit</tvar>|Diffedit]] to just edit this one wrong link. === Structured tasks - Add an image === <!--T:196--> </translate> ''<translate><!--T:197--> This project is a work in progress, into development stages. You can know more about this project by visiting [[<tvar name="1">Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image</tvar>|its project page]].</translate>'' <translate> ==== What is the purpose of "Structured tasks - Add an image"? ==== <!--T:198--> <!--T:199--> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. ==== Which rules define the work done by "Structured tasks - Add an image"? ==== <!--T:200--> <!--T:201--> We have several rules: </translate> * <translate><!--T:202--> Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</translate> * <translate><!--T:203--> Only articles where no image is displayed are taken into consideration for images addition.</translate> * <translate><!--T:204--> Articles with an infobox but no image aren't taken into consideration for now.</translate> <translate> ==== Which types of users have been contacted to test this new concept ==== <!--T:205--> <!--T:206--> During the design process, several types users have been involved. </translate> * <translate><!--T:207--> During the definition process: Growth team members (which include several active wiki editors) and our [[<tvar name="1">#ambassadors</tvar>|Ambassadors]] (at this time of the process: <tvar name="2">{{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}</tvar>).</translate> * <translate><!--T:208--> To test early prototypes, we focused on the two types of editors our features target.</translate> ** <translate><!--T:209--> people who aren't wiki editors (using UserTesting.com, in English and Spanish)</translate> ** <translate><!--T:210--> experienced users involved in newcomers' first steps, coming from [[<tvar name="1">#pilot</tvar>|our pilot wikis]] so as people from Spanish Wikipedia.</translate> {{anchor|HP}} <translate> == Help panel == <!--T:181--> === We want to change some links displayed on the Help panel. How to do it? === <!--T:104--> <!--T:171--> An admin can change these links using <tvar name="1"><code>Special:EditGrowthConfig</code></tvar>. <!--T:105--> We can assist you in this task. [[<tvar name="1">Talk:Growth</tvar>|Please contact us]] with your request; please provide a link to the community discussion that led to this change. <!--T:182--> These links are [[<tvar name="1">#Homepage</tvar>|also used on the Homepage]]. === Where does questions posted using the Help panel goes? === <!--T:212--> <!--T:213--> By default, these questions go the the local Help desk. <!--T:214--> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </translate> * <translate><!--T:215--> new messages should go the newcomer's mentors,</translate> * <translate><!--T:216--> new messages should be posted at the help desk.</translate> <translate> <!--T:217--> An admin can change this configuration using <tvar name="1"><code>Special:EditGrowthConfig</code></tvar>. === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === <!--T:218--> </translate> <translate><!--T:219--> We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New).</translate> <translate><!--T:220--> As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page. </translate> {{anchor|mentoring}} <translate> == Configuration of the features == <!--T:248--> === We would like to change something on the configuration of the Growth features. How can we do it? === <!--T:249--> </translate> <translate><!--T:250--> At your wiki, any admin can edit the configuration page (<tvar name="1"><code>Special:EditGrowthConfig</code></tvar>).</translate> <translate><!--T:251--> Of course, be sure that the change is based on a community consensus.</translate> <translate><!--T:252--> [[<tvar name="1">Talk:Growth</tvar>|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</translate> <translate><!--T:253--> Sharing your feedback with us will help improve the Growth features.</translate> {{anchor|add-link-config}} <translate> === I changed the configuration for "Add links between articles" in <tvar name="1">Special:EditGrowthConfig</tvar>, but it isn't working. === <!--T:254--> </translate> <translate><!--T:268--> Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</translate> <translate><!--T:269--> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. <!--T:258--> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. <!--T:270--> See <tvar name="1">[[Phab:T313642|T313642]]</tvar> for plans to improve this situation. == Configuration and operation of the mentoring system == <!--T:106--> === My wiki doesn't have the Growth mentoring system. How can I set it up? === <!--T:107--> <!--T:211--> The next steps are a summary of the process. The full process is described on [[<tvar name="1">Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create</tvar>|this dedicated page]]. <!--T:108--> First, you need to check if the Growth tools are [[<tvar name="1">Growth/Deployment table</tvar>|deployed at your wiki]]. If it is not yet the case, please see [[<tvar name="2">#get</tvar>|how to get the features]]. <!--T:109--> Then, you have to find some other mentors to volunteer. <!--T:110--> All mentors have to sign-up on a specific page, using [[<tvar name="1">Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create</tvar>|a specific syntax]]. <!--T:111--> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[<tvar name="1">D:Q14339834</tvar>|this Wikidata item]]. <!--T:112--> At your wiki, an admin has to add the mentor list to the configuration page (<tvar name="1"><code>Special:EditGrowthConfig</code></tvar>). === How many mentors does a wiki need? === <!--T:113--> <!--T:114--> Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. <!--T:115--> We recommend to have at least 3 mentors. === Who can be a mentor? === <!--T:262--> <!--T:263--> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. <!--T:264--> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors.</translate> <translate><!--T:265--> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). === How mentors are assigned to newcomers? === <!--T:116--> <!--T:117--> Each new account receives a mentor randomly taken from a list of volunteers. === How many messages does a mentor receive per week? === <!--T:118--> <!--T:119--> It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. <!--T:120--> On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. === Have you considered to assign a mentor only to people who already made some edits? === <!--T:121--> <!--T:122--> We don't know what each newcomer needs. [[<tvar name="1">Special:MyLanguage/New Editor Experiences</tvar>|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. </translate> {{anchor|existing}} <translate> === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === <!--T:123--> <!--T:124--> We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[<tvar name="1">d:Q3919128</tvar>|listed on Wikidata]]. <!--T:125--> It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: </translate> '''<translate><!--T:126--> Replace your mentoring system with the new one</translate>''' <translate><!--T:127--> If your mentoring system hasn't much success, it could be replaced by the Growth team features.</translate> '''<translate><!--T:128--> Have both systems working together</translate>''' <translate><!--T:129--> You can imagine to have two roles:</translate> * <translate><!--T:130--> Growth mentoring takes care of the newcomers basic questions,</translate> * <translate><!--T:131--> The existing mentoring can take care of newcomers who are more involved.</translate> <translate> <!--T:132--> In this case, you might have to locally translate the interface for Growth features using your own terms. === Where can I signup as a mentor ? === <!--T:133--> <!--T:134--> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[<tvar name="1">D:Q14339834</tvar>|this Wikidata item]]. </translate> <translate><!--T:135--> Your community may have defined some conditions to become a mentor.</translate> <translate><!--T:266--> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</translate> <translate><!--T:267--> We suggest to use the autopatrolled level (500 edits and 90 days of presence).</translate> {{anchor|mentorsyntax}} <translate> === How do I introduce myself as a mentor? === <!--T:136--> <!--T:137--> When you sign up to become a mentor, the following syntax must be used, with: </translate> <code>* <nowiki>[[</nowiki><translate><!--T:138--> User:Username</translate><nowiki>]]</nowiki>|<translate><!--T:139--> Description</translate></code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|<translate><!--T:140--> Read more about this</translate>]] {{anchor|reassign}} <translate> === Can we reassign a newcomer to a different mentor? === <!--T:141--> <!--T:142--> Yes, it is possible using <tvar name="1"><code>Special:ClaimMentee</code></tvar>. </translate> {{anchor|pause}} <translate> === As a mentor, I have to pause my mentorship activity. How can I do it? === <!--T:242--> <!--T:243--> You can go to <tvar name="1">[[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]]</tvar> and pause your activity. </translate> {{anchor|quit}} <translate> === As a mentor, I would like to quit mentorship. How can I do it? === <!--T:244--> <!--T:245--> You can go to <tvar name="1"><code>Special:QuitMentorship</code></tvar> and quit from there.</translate> <translate><!--T:246--> This link is accessible from your [[<tvar name="1">Special:MyLanguage/Growth/Mentor dashboard</tvar>|Mentor dashboard]]. === A mentor just quit. Can we reassign all their newcomer to different mentors? === <!--T:143--> <!--T:144--> You can use <tvar name="1"><code>Special:ClaimMentee</code></tvar> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[<tvar name="2">Talk:Growth</tvar>|please contact us]] directly. </translate> {{anchor|magicword}} <translate> === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === <!--T:146--> <!--T:147--> Type the magic word <tvar name="1"><code><nowiki>{{#mentor:Foo}}</nowiki></code></tvar> in a wikitext page, and preview. "<tvar name="2">Foo</tvar>" has to be replaced by the username you target. This will display the name of <tvar name="3">Foo</tvar>'s mentor. <!--T:148--> This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. <!--T:149--> [[<tvar name="1">#reassign</tvar>|If the mentor changes]], then the magic word picks the new mentor's name. <!--T:150--> You can "<tvar name="1">[[Special:MyLanguage/Help:Substitution|subst:]]</tvar>" this message if needed: <tvar name="2"><code><nowiki>{{subst:#mentor:Foo}}</nowiki></code></tvar>. <tvar name="3">Foo</tvar>'s mentor will then be saved as wikitext. === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === <!--T:151--> <!--T:152--> Have you updated <tvar name="1"><code>Special:EditGrowthConfig</code></tvar> with the new page name? == Interactions between mentors and newcomers == <!--T:153--> </translate> {{Anchor|questions}} <translate> === What kinds of questions do newcomers ask? === <!--T:154--> <!--T:155--> From the observations we have made, questions are mostly about basic editing. <!--T:156--> Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. <!--T:157--> Based on communities experiences, the Growth team worked [[<tvar name="1">Special:MyLanguage/Growth/Communities/How to interact with newcomers</tvar>|on a guide for mentors]] who have to reply to these questions. === Newcomers haven't replied to my messages. Why? === <!--T:158--> <!--T:159--> Two possible cases there: </translate> * <translate><!--T:160--> Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages.</translate> * <translate><!--T:161--> Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page.</translate> <translate> === Who can I ask if my mentor is not responding to me? === <!--T:162--> <!--T:163--> If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. === Can I ask to have a different mentor ? === <!--T:164--> <!--T:165--> You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[<tvar name="1">#reassign</tvar>|make the change]]. === As a mentor, how can I monitor the newcomers assigned to me? === <!--T:166--> <!--T:167--> We are currently working on a [[<tvar name="1">Growth/Mentor dashboard</tvar>|Mentor dashboard]].</translate> <translate><!--T:230--> It is available at all Wikipedias where [[<tvar name="1">special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create</tvar>|a list of mentors has been created and activated]]. === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === <!--T:221--> </translate> <translate><!--T:222--> At wikis where the mentor dashboard is deployed, a new filter is available for mentors.</translate> <translate><!--T:223--> They can monitor their mentees' activity in Watchlist and RecentChanges.</translate> <translate><!--T:224--> For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[<tvar name="1">mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list</tvar>|not listed as mentors]].</translate> <translate> === A very experienced user is one of my mentees. Why? === <!--T:235--> <!--T:236--> For technical reasons, we assign a mentor to everyone, including experienced users. === Are all my mentees assigned to me being visible in my list of mentees? === <!--T:237--> <!--T:238--> Your list will only display users who have turned the Homepage on. </translate> jhlgfcp5dpyrq0vtzwzo4kw2deb2nbh Translations:Manual:Installing MediaWiki/116/ja 1198 1321193 5387243 4502575 2022-07-28T21:32:45Z Shirayuki 472859 update wikitext text/x-wiki ==さらなる環境設定== 2v3tolv8opcelpqmsq0aqd8jc5h3xfh Template:InstallationNav/fi 10 1324211 5387198 5384784 2022-07-28T21:17:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Extension:EasyTimeline/de 102 1326947 5386915 5370561 2022-07-28T19:43:17Z ThisCarthing 17456337 Created page with "Siehe unten" wikitext text/x-wiki <languages /> {{Extension |type1 = tag |status = stable |author = [[w:User:Erik Zachte|Erik Zachte]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds {{tag|timeline|open}} tag for creating timelines</span> |download = {{WikimediaDownload|timeline}} |needs-updatephp = no |changelog = {{git file|action=summary|project=mediawiki/extensions/timeline|branch=HEAD|text=CHANGELOG}} |phabricator = EasyTimeline |pagedrive1 = true |example = [[#charts-examples|Siehe unten]] |translate = ext-timeline }} :''Andere Sprachen:'' [[Extension:EasyTimeline/ar|ar]] [[:de:Hilfe:Zeitleisten|de]] [[:es:Ayuda:Cronologías|es]] [[:eu:Laguntza:Denbora lerroak|eu]] [[:fr:Aide:Frise chronologique|fr]] [[:id:Wikipedia:Timeline|id]] [[:it:Aiuto:Timeline|it]] [[Extension:EasyTimeline/ja|ja]] [[:nl:Help:EasyTimeline|nl]] [[:pt:Wikipedia:EasyTimeline|pt]] [[Extension:EasyTimeline/tr|tr]] [[:zh:Help:简易时间线语法|zh]] <div lang="en" dir="ltr" class="mw-content-ltr"> The '''EasyTimeline''' extension produces an embedded image from wikitext. The image can be a one-dimensional diagram (horizontally or vertically), or a two-dimensional one. </div> <span lang="en" dir="ltr" class="mw-content-ltr">See the help page on [[Special:MyLanguage/Extension:EasyTimeline/installation|installing EasyTimeline]] on your wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://infodisiac.com/Wikipedia/EasyTimeline/Introduction.htm this page on EasyTimeline] or play with it at [[testwiki:EasyTimeline|test.wikipedia.org]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See the help page on [[Special:MyLanguage/Extension:EasyTimeline/syntax|using the syntax provided by this extension]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There is a [[phab:T137291|long-term effort]] to get the {{ll|Extension:Graph|Graph}} extension to replace this extension. </div> == Voraussetzungen == <div lang="en" dir="ltr" class="mw-content-ltr"> This extension requires the following programs installed on the server: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:Ploticus|Ploticus]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:perl|perl]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:XnView|NConvert]] (Windows only) </div> {{anchor|charts-examples}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Charts examples== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Several examples of what is possible. For more extensive examples see </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Timeline WWII - Pacific Theater|WW II - Pacific Theatre]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Timeline of aircraft carriers of the United States Navy|:en:Timeline of aircraft carriers of the United States Navy]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Timeline History of Computing|History of Computing]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:de:Vorlage:Zeitleiste Tour-de-France-Sieger|Tour-de-France Sieger]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Vocal and instrumental pitch ranges|Vocal and instrumental pitch ranges]] (a nice example of a diagram that is not a timeline at all) - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Complete timeline of Macintosh models|Complete timeline of Macintosh models]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Simpler timelines: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Template:Extinction events graphical timeline|:en:Template:Extinction events graphical timeline]] - horizontal, uses [[w:Template:Horizontal timeline|w:Template:Horizontal timeline]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Talk:Invention_of_radio/Archive_1#Timeline.2C_Players|:en:Talk:Invention_of_radio/Archive_1#Timeline.2C_Players]] - horizontal with arrows </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Template:Early evolution of the light bulb|:en:Template:Early evolution of the light bulb]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Invention of radio#Radio invention timeline|:en:Invention of radio#Radio invention timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Gaius_Marius#Timeline|:en:Gaius_Marius#Timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:User:Syed Atif Nazir/Template:Imam timeline|:en:User:Syed Atif Nazir/Template:Imam timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [https://de.wikipedia.org/w/index.php?title=Aurich&oldid=171331690#Einwohnerentwicklung Population developement] - horizontal </div> <table><tr> <td valign=top> <timeline> ImageSize = width:160 height:550 PlotArea = width:50 height:530 left:50 bottom:10 DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> </td> <td>&nbsp;&nbsp;</td> <td valign=top> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:phanerozoic value:rgb(0.435,0.85,0.866) id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:neogene value:rgb(1,0.901,0.098) id:paleogene value:rgb(0.992,0.603,0.321) id:mesozoic value:rgb(0.403,0.772,0.792) id:cretaceous value:rgb(0.498,0.776,0.306) id:jurassic value:rgb(0.203,0.698,0.788) id:triassic value:rgb(0.505,0.168,0.572) id:paleozoic value:rgb(0.6,0.752,0.552) id:permian value:rgb(0.941,0.25,0.156) id:carboniferous value:rgb(0.403,0.647,0.6) id:devonian value:rgb(0.796,0.549,0.215) id:silurian value:rgb(0.702,0.882,0.713) id:ordovician value:rgb(0,0.572,0.439) id:cambrian value:rgb(0.496,0.627,0.337) id:proterozoic value:rgb(0.968,0.207,0.388) id:neoproterozoic value:rgb(0.996,0.701,0.258) id:ediacaran value:rgb(0.996,0.85,0.415) id:cryogenian value:rgb(0.996,0.8,0.36) id:tonian value:rgb(0.996,0.75,0.305) id:mesoproterozoic value:rgb(0.996,0.705,0.384) id:stenian value:rgb(0.996,0.85,0.604) id:ectasian value:rgb(0.996,0.8,0.541) id:calymmian value:rgb(0.996,0.75,0.478) id:paleoproterozoic value:rgb(0.968,0.263,0.44) id:statherian value:rgb(0.968,0.459,0.655) id:orosirian value:rgb(0.968,0.408,0.596) id:rhyacian value:rgb(0.968,0.357,0.537) id:siderian value:rgb(0.968,0.306,0.478) id:archean value:rgb(0.996,0.157,0.498) id:neoarchean value:rgb(0.976,0.608,0.757) id:mesoarchean value:rgb(0.968,0.408,0.662) id:paleoarchean value:rgb(0.96,0.266,0.624) id:eoarchean value:rgb(0.902,0.114,0.549) id:hadean value:rgb(0.717,0,0.494) id:black value:black id:white value:white Period = from:-4567 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:500 start:-4500 ScaleMinor = unit:year increment:100 start:-4500 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:eon at: 0 align:right $markred at: -542 align:left $markred shift:(2,3) from: -542 till: 0 text:[[Special:MyLanguage/Phanerozoic|Phanerozoic]] color:phanerozoic from: -2500 till: -542 text:[[Special:MyLanguage/Proterozoic|Proterozoic]] color:proterozoic from: -4000 till: -2500 text:[[Special:MyLanguage/Archean|Archean]] color:archean from: start till: -4000 text:[[Special:MyLanguage/Hadean|Hadean]] color:hadean bar:era from: -65.5 till: 0 text:[[Special:MyLanguage/Cenozoic|C]] color:cenozoic from: -251 till: -65.5 text:[[Special:MyLanguage/Mesozoic|Meso]] color:mesozoic from: -542 till: -251 text:[[Special:MyLanguage/Paleozoic|Paleozoic]] color:paleozoic from: -1000 till: -542 text:[[Special:MyLanguage/Neoproterozoic|Neoproterozoic]] color:neoproterozoic from: -1600 till: -1000 text:[[Special:MyLanguage/Mesoproterozoic|Mesoproterozoic]] color:mesoproterozoic from: -2500 till: -1600 text:[[Special:MyLanguage/Paleoproterozoic|Paleoproterozoic]] color:paleoproterozoic from: -2800 till: -2500 text:[[Special:MyLanguage/Neoarchean|Neoarch]] color:neoarchean from: -3200 till: -2800 text:[[Special:MyLanguage/Mesoarchean|Mesoarch]] color:mesoarchean from: -3600 till: -3200 text:[[Special:MyLanguage/Paleoarchean|Paleoarch]] color:paleoarchean from: -4000 till: -3600 text:[[Special:MyLanguage/Eoarchean|Eoarchean]] color:eoarchean from: start till: -4000 color:white bar:period fontsize:6 from: -2.6 till: 0 color:quaternary from: -23.03 till: -2.6 color:neogene from: -65.5 till: -23.03 color:paleogene from: -145.5 till: -65.5 color:cretaceous from: -199.6 till: -145.5 color:jurassic from: -251 till: -199.6 color:triassic from: -299 till: -251 color:permian from: -359.2 till: -299 color:carboniferous from: -416 till: -359.2 color:devonian from: -443.7 till: -416 color:silurian from: -488.3 till: -443.7 color:ordovician from: -542 till: -488.3 color:cambrian from: -635 till: -542 text:[[Special:MyLanguage/Ediacaran|Ed.]] color:ediacaran from: -850 till: -635 text:[[Special:MyLanguage/Cryogenian|Cryo]] color:cryogenian from: -1000 till: -850 text:[[Special:MyLanguage/Tonian|Tonian]] color:tonian from: -1200 till: -1000 text:[[Special:MyLanguage/Stenian|Stenian]] color:stenian from: -1400 till: -1200 text:[[Special:MyLanguage/Ectasian|Ectasian]] color:ectasian from: -1600 till: -1400 text:[[Special:MyLanguage/Calymmian|Calymm]] color:calymmian from: -1800 till: -1600 text:[[Special:MyLanguage/Statherian|Stather]] color:statherian from: -2050 till: -1800 text:[[Special:MyLanguage/Orosirian|Orosirian]] color:orosirian from: -2300 till: -2050 text:[[Special:MyLanguage/Rhyacian|Rhyacian]] color:rhyacian from: -2500 till: -2300 text:[[Special:MyLanguage/Siderian|Siderian]] color:siderian from: start till: -2500 color:white </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:phanerozoic value:rgb(0.435,0.85,0.866) id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:neogene value:rgb(1,0.901,0.098) id:paleogene value:rgb(0.992,0.603,0.321) id:mesozoic value:rgb(0.403,0.772,0.792) id:cretaceous value:rgb(0.498,0.776,0.306) id:jurassic value:rgb(0.203,0.698,0.788) id:triassic value:rgb(0.505,0.168,0.572) id:paleozoic value:rgb(0.6,0.752,0.552) id:permian value:rgb(0.941,0.25,0.156) id:carboniferous value:rgb(0.403,0.647,0.6) id:devonian value:rgb(0.796,0.549,0.215) id:silurian value:rgb(0.702,0.882,0.713) id:ordovician value:rgb(0,0.572,0.439) id:cambrian value:rgb(0.496,0.627,0.337) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-542 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:100 start:-500 ScaleMinor = unit:year increment:10 start:-540 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:eon at: 0 align:right $markred at: -542 align:left $markred shift:(2,3) from: -542 till: 0 text:[[Special:MyLanguage/Phanerozoic|Phanerozoic]] color:phanerozoic bar:era at: 0 align:right $markgreen at: -65.5 align:left $markgreen shift:(2,3) from: -65.5 till: 0 text:[[Special:MyLanguage/Cenozoic|Cenozoic]] color:cenozoic from: -251 till: -65.5 text:[[Special:MyLanguage/Mesozoic|Mesozoic]] color:mesozoic from: -542 till: -251 text:[[Special:MyLanguage/Paleozoic|Paleozoic]] color:paleozoic bar:period fontsize:8 from: -2.588 till: 0 text:[[Special:MyLanguage/Quaternary|Q.]] color:quaternary from: -23.03 till: -2.588 text:[[Special:MyLanguage/Neogene|Neo]] color:neogene from: -65.5 till: -23.03 text:[[Special:MyLanguage/Paleogene|Paleogene]] color:paleogene from: -145.5 till: -65.5 text:[[Special:MyLanguage/Cretaceous|Cretaceous]] color:cretaceous from: -199.6 till: -145.5 text:[[Special:MyLanguage/Jurassic|Jurassic]] color:jurassic from: -251.4 till: -199.6 text:[[Special:MyLanguage/Triassic|Triassic]] color:triassic from: -299 till: -251.4 text:[[Special:MyLanguage/Permian|Permian]] color:permian from: -359.2 till: -299 text:[[Special:MyLanguage/Carboniferous|Carboniferous]] color:carboniferous from: -416 till: -359.2 text:[[Special:MyLanguage/Devonian|Devonian]] color:devonian from: -443.7 till: -416 text:[[Special:MyLanguage/Silurian|Silurian]] color:silurian from: -488.3 till: -443.7 text:[[Special:MyLanguage/Ordovician|Ordovician]] color:ordovician from: -542 till: -488.3 text:[[Cambrian] color:cambrian </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:holocene value:rgb(0.996,0.949,0.878) id:pleistocene value:rgb(1,0.949,0.678) id:neogene value:rgb(1,0.901,0.098) id:pliocene value:rgb(1,1,0.6) id:miocene value:rgb(1,1,0) id:paleogene value:rgb(0.992,0.603,0.321) id:oligocene value:rgb(0.992,0.752,0.478) id:eocene value:rgb(0.992,0.705,0.423) id:paleocene value:rgb(0.992,0.654,0.372) id:cambrian value:rgb(0.496,0.627,0.337) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-65.5 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:10 start:-60 ScaleMinor = unit:year increment:1 start:-65 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:era at: 0 align:right $markgreen at: start align:left $markgreen shift:(2,3) from:start till: 0 text:[[Cenozoic|Cambrian]] color:cambrian </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:holocene value:rgb(0.996,0.949,0.878) id:pleistocene value:rgb(1,0.949,0.678) id:neogene value:rgb(1,0.901,0.098) id:pliocene value:rgb(1,1,0.6) id:miocene value:rgb(1,1,0) id:paleogene value:rgb(0.992,0.603,0.321) id:oligocene value:rgb(0.992,0.752,0.478) id:eocene value:rgb(0.992,0.705,0.423) id:paleocene value:rgb(0.992,0.654,0.372) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-65.5 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:10 start:-60 ScaleMinor = unit:year increment:1 start:-65 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:era at: 0 align:right $markgreen at: start align:left $markgreen shift:(2,3) from:start till: 0 text:[[Special:MyLanguage/Cenozoic|Cenozoic]] color:cenozoic bar:period from: -2.588 till: 0 text:[[Special:MyLanguage/Quaternary|Q.]] color:quaternary from: -23.03 till: -2.588 text:[[Special:MyLanguage/Neogene|Neogene]] color:neogene from: start till: -23.03 text:[[Special:MyLanguage/Paleogene|Paleogene]] color:paleogene bar:epoch from: -0.1 till: 0 text:[[Special:MyLanguage/Holocene|H]] color:holocene from: -2.588 till: -0.1 text:[[Special:MyLanguage/Pleistocene|P]] color:pleistocene from: -5.332 till: -2.588 text:[[Special:MyLanguage/Pliocene|Pliocene]] color:pliocene fontsize:7 from: -23.03 till: -5.332 text:[[Special:MyLanguage/Miocene|Miocene]] color:miocene from: -33.9 till: -23.03 text:[[Special:MyLanguage/Oligocene|Oligocene]] color:oligocene from: -55.8 till: -33.9 text:[[Special:MyLanguage/Eocene|Eocene]] color:eocene from: start till: -55.8 text:[[Special:MyLanguage/Paleocene|Paleocene]] color:paleocene </timeline> </td></tr> <tr><td colspan=3 align=left>{{Wikimedia Growth}}</td></tr> </table> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Code example== </div> :''Siehe auch:'' {{ll|Extension:EasyTimeline/syntax}} <timeline> # All measures are in pixels ImageSize = width:160 height:550 PlotArea = left:50 right:0 bottom:10 top:10 AlignBars = justify DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef~Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> <div lang="en" dir="ltr" class="mw-content-ltr"> Just to show you that the script syntax is reasonably intuitive, here is the script for the image above: Soviet Leaders. </div> <syntaxhighlight lang="moin"> <timeline> # All measures are in pixels ImageSize = width:160 height:550 PlotArea = left:50 right:0 bottom:10 top:10 AlignBars = justify DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef~Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Double and single brackets can be used like on wikipedia, language prefix is possible, e.g. <syntaxhighlight lang="moin" inline>[[de:foo|more about foo]]</syntaxhighlight>. Single brackets for external links are also supported. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Great timelines elsewhere== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here are two great sites that may serve as inspiration, it would be very easy to recreate most of those timelines verbatim and with roughly similar layout with EasyTimeline (not yet with images but that may change), but I'm afraid that would be 'not done'. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[http://www.hyperhistory.com/online_n2/History_n2/a.html Hyperhistory] e.g. click on button 'people' left, then on 'special lifelines', right. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *I hope we will have a set like [http://chaos1.hypermart.net/fullsize.htm] in a years time (click on ''full size image'' for any map), possibly even with images. The main effort will be to gather all info without snatching everything from here (most of these maps are based exclusively on data from Britannica). </div> ==Unicode== <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline does not yet support unicode. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Aug 2004: Minimal UTF-8 support has been added, meaning that EasyTimeline now recognizes UTF-8 encoded characters. However support for directionality and complex scripts is very lacking. The default font may not have glyphs for all characters. An alternate font can be specified via <code>$wgTimelineFontFile</code> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SVG to PNG=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To show texts correctly for RTL languages (like Arabic, Persian, Hebrew,...) you can use {{tmpl|0={{tag|timeline|params={{attr|method|"svg2png"}}|content=$1}}|timeline code here}} instead of {{tmpl|0={{tag|timeline|content=$1}}|timeline code here}}. it shows timeline as png but the links will be disabled. </div> == Tipps == <div lang="en" dir="ltr" class="mw-content-ltr"> For first time users EasyTimeline may not seem that easy at all. As with all script languages it takes some getting used to. Also the syntax description may be a bit bewildering due to its sheer size. Fortunately many elements of the script language are optional. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The 'Easy' in EasyTimeline conveys the message that once a timeline exists it is not so hard to understand, enhance or correct. Also translating for use on another Wikipedia it is pretty straightforward. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Tips: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * See some [[#charts-examples|chart examples]] to find something you could pick and edit for your own stuff </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *Put each timeline on a separate Template page: this makes it easier to edit, faster to preview, possible to include it in several pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Using the current date== </div> <span lang="en" dir="ltr" class="mw-content-ltr">To use the current date make sure the table opens with <code><nowiki>{{#tag:timeline|</nowiki></code> and closes with <code><nowiki>}}</nowiki></code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then the current date can be inserted using magic words.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example <code><nowiki>{{#time: d/m/Y }}</nowiki></code> or <code><nowiki>{{CURRENTDAY2}}/{{CURRENTMONTH2}}/{{CURRENTYEAR}}</nowiki></code> will both yield the date in format dd/mm/yyyy.</span> == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> *[[Special:MyLanguage/Extension:EasyTimeline/syntax|EasyTimeline Coding]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *Presentation about EasyTimeline at Wikimania 2005 ([[m:Transwiki:Wikimania05/Workshop-EZ1|abstract]], [http://upload.wikimedia.org/wikipedia/commons/9/90/Wikimania_2005_Presentation_EasyTimeline.pdf slides], [http://upload.wikimedia.org/wikipedia/commons/7/78/Wikimania_2005_Presentation_Easytimeline_Speaker_Notes.pdf speaker notes]) </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[m:WikiTimeScale|m:WikiTimeScale]] as a proposal for realizing timescales for wikipedia articles externally. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[w:Template:Simple Horizontal timeline|w:Template:Simple Horizontal timeline]] An easier timeline to use on Wikipedia. </div> *{{ll|Extension:Graph}} ==Installation== <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Special:MyLanguage/Extension:EasyTimeline/installation|/installation]] </div> == Externe Links == * [http://www.simile-widgets.org <span lang="en" dir="ltr" class="mw-content-ltr">SIMILE Widgets</span>] - DHTML-based AJAXy widget for visualizing time-based events {{OnWikimedia}} {{Used by|fandom=1}} lx08ciigsz6p6ihsxhqqfutltz1o6zv 5386917 5386915 2022-07-28T19:43:28Z ThisCarthing 17456337 Created page with "Tipps" wikitext text/x-wiki <languages /> {{Extension |type1 = tag |status = stable |author = [[w:User:Erik Zachte|Erik Zachte]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds {{tag|timeline|open}} tag for creating timelines</span> |download = {{WikimediaDownload|timeline}} |needs-updatephp = no |changelog = {{git file|action=summary|project=mediawiki/extensions/timeline|branch=HEAD|text=CHANGELOG}} |phabricator = EasyTimeline |pagedrive1 = true |example = [[#charts-examples|Siehe unten]] |translate = ext-timeline }} :''Andere Sprachen:'' [[Extension:EasyTimeline/ar|ar]] [[:de:Hilfe:Zeitleisten|de]] [[:es:Ayuda:Cronologías|es]] [[:eu:Laguntza:Denbora lerroak|eu]] [[:fr:Aide:Frise chronologique|fr]] [[:id:Wikipedia:Timeline|id]] [[:it:Aiuto:Timeline|it]] [[Extension:EasyTimeline/ja|ja]] [[:nl:Help:EasyTimeline|nl]] [[:pt:Wikipedia:EasyTimeline|pt]] [[Extension:EasyTimeline/tr|tr]] [[:zh:Help:简易时间线语法|zh]] <div lang="en" dir="ltr" class="mw-content-ltr"> The '''EasyTimeline''' extension produces an embedded image from wikitext. The image can be a one-dimensional diagram (horizontally or vertically), or a two-dimensional one. </div> <span lang="en" dir="ltr" class="mw-content-ltr">See the help page on [[Special:MyLanguage/Extension:EasyTimeline/installation|installing EasyTimeline]] on your wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://infodisiac.com/Wikipedia/EasyTimeline/Introduction.htm this page on EasyTimeline] or play with it at [[testwiki:EasyTimeline|test.wikipedia.org]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See the help page on [[Special:MyLanguage/Extension:EasyTimeline/syntax|using the syntax provided by this extension]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There is a [[phab:T137291|long-term effort]] to get the {{ll|Extension:Graph|Graph}} extension to replace this extension. </div> == Voraussetzungen == <div lang="en" dir="ltr" class="mw-content-ltr"> This extension requires the following programs installed on the server: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:Ploticus|Ploticus]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:perl|perl]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:XnView|NConvert]] (Windows only) </div> {{anchor|charts-examples}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Charts examples== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Several examples of what is possible. For more extensive examples see </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Timeline WWII - Pacific Theater|WW II - Pacific Theatre]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Timeline of aircraft carriers of the United States Navy|:en:Timeline of aircraft carriers of the United States Navy]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Timeline History of Computing|History of Computing]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:de:Vorlage:Zeitleiste Tour-de-France-Sieger|Tour-de-France Sieger]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Vocal and instrumental pitch ranges|Vocal and instrumental pitch ranges]] (a nice example of a diagram that is not a timeline at all) - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Complete timeline of Macintosh models|Complete timeline of Macintosh models]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Simpler timelines: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Template:Extinction events graphical timeline|:en:Template:Extinction events graphical timeline]] - horizontal, uses [[w:Template:Horizontal timeline|w:Template:Horizontal timeline]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Talk:Invention_of_radio/Archive_1#Timeline.2C_Players|:en:Talk:Invention_of_radio/Archive_1#Timeline.2C_Players]] - horizontal with arrows </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Template:Early evolution of the light bulb|:en:Template:Early evolution of the light bulb]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Invention of radio#Radio invention timeline|:en:Invention of radio#Radio invention timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Gaius_Marius#Timeline|:en:Gaius_Marius#Timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:User:Syed Atif Nazir/Template:Imam timeline|:en:User:Syed Atif Nazir/Template:Imam timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [https://de.wikipedia.org/w/index.php?title=Aurich&oldid=171331690#Einwohnerentwicklung Population developement] - horizontal </div> <table><tr> <td valign=top> <timeline> ImageSize = width:160 height:550 PlotArea = width:50 height:530 left:50 bottom:10 DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> </td> <td>&nbsp;&nbsp;</td> <td valign=top> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:phanerozoic value:rgb(0.435,0.85,0.866) id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:neogene value:rgb(1,0.901,0.098) id:paleogene value:rgb(0.992,0.603,0.321) id:mesozoic value:rgb(0.403,0.772,0.792) id:cretaceous value:rgb(0.498,0.776,0.306) id:jurassic value:rgb(0.203,0.698,0.788) id:triassic value:rgb(0.505,0.168,0.572) id:paleozoic value:rgb(0.6,0.752,0.552) id:permian value:rgb(0.941,0.25,0.156) id:carboniferous value:rgb(0.403,0.647,0.6) id:devonian value:rgb(0.796,0.549,0.215) id:silurian value:rgb(0.702,0.882,0.713) id:ordovician value:rgb(0,0.572,0.439) id:cambrian value:rgb(0.496,0.627,0.337) id:proterozoic value:rgb(0.968,0.207,0.388) id:neoproterozoic value:rgb(0.996,0.701,0.258) id:ediacaran value:rgb(0.996,0.85,0.415) id:cryogenian value:rgb(0.996,0.8,0.36) id:tonian value:rgb(0.996,0.75,0.305) id:mesoproterozoic value:rgb(0.996,0.705,0.384) id:stenian value:rgb(0.996,0.85,0.604) id:ectasian value:rgb(0.996,0.8,0.541) id:calymmian value:rgb(0.996,0.75,0.478) id:paleoproterozoic value:rgb(0.968,0.263,0.44) id:statherian value:rgb(0.968,0.459,0.655) id:orosirian value:rgb(0.968,0.408,0.596) id:rhyacian value:rgb(0.968,0.357,0.537) id:siderian value:rgb(0.968,0.306,0.478) id:archean value:rgb(0.996,0.157,0.498) id:neoarchean value:rgb(0.976,0.608,0.757) id:mesoarchean value:rgb(0.968,0.408,0.662) id:paleoarchean value:rgb(0.96,0.266,0.624) id:eoarchean value:rgb(0.902,0.114,0.549) id:hadean value:rgb(0.717,0,0.494) id:black value:black id:white value:white Period = from:-4567 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:500 start:-4500 ScaleMinor = unit:year increment:100 start:-4500 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:eon at: 0 align:right $markred at: -542 align:left $markred shift:(2,3) from: -542 till: 0 text:[[Special:MyLanguage/Phanerozoic|Phanerozoic]] color:phanerozoic from: -2500 till: -542 text:[[Special:MyLanguage/Proterozoic|Proterozoic]] color:proterozoic from: -4000 till: -2500 text:[[Special:MyLanguage/Archean|Archean]] color:archean from: start till: -4000 text:[[Special:MyLanguage/Hadean|Hadean]] color:hadean bar:era from: -65.5 till: 0 text:[[Special:MyLanguage/Cenozoic|C]] color:cenozoic from: -251 till: -65.5 text:[[Special:MyLanguage/Mesozoic|Meso]] color:mesozoic from: -542 till: -251 text:[[Special:MyLanguage/Paleozoic|Paleozoic]] color:paleozoic from: -1000 till: -542 text:[[Special:MyLanguage/Neoproterozoic|Neoproterozoic]] color:neoproterozoic from: -1600 till: -1000 text:[[Special:MyLanguage/Mesoproterozoic|Mesoproterozoic]] color:mesoproterozoic from: -2500 till: -1600 text:[[Special:MyLanguage/Paleoproterozoic|Paleoproterozoic]] color:paleoproterozoic from: -2800 till: -2500 text:[[Special:MyLanguage/Neoarchean|Neoarch]] color:neoarchean from: -3200 till: -2800 text:[[Special:MyLanguage/Mesoarchean|Mesoarch]] color:mesoarchean from: -3600 till: -3200 text:[[Special:MyLanguage/Paleoarchean|Paleoarch]] color:paleoarchean from: -4000 till: -3600 text:[[Special:MyLanguage/Eoarchean|Eoarchean]] color:eoarchean from: start till: -4000 color:white bar:period fontsize:6 from: -2.6 till: 0 color:quaternary from: -23.03 till: -2.6 color:neogene from: -65.5 till: -23.03 color:paleogene from: -145.5 till: -65.5 color:cretaceous from: -199.6 till: -145.5 color:jurassic from: -251 till: -199.6 color:triassic from: -299 till: -251 color:permian from: -359.2 till: -299 color:carboniferous from: -416 till: -359.2 color:devonian from: -443.7 till: -416 color:silurian from: -488.3 till: -443.7 color:ordovician from: -542 till: -488.3 color:cambrian from: -635 till: -542 text:[[Special:MyLanguage/Ediacaran|Ed.]] color:ediacaran from: -850 till: -635 text:[[Special:MyLanguage/Cryogenian|Cryo]] color:cryogenian from: -1000 till: -850 text:[[Special:MyLanguage/Tonian|Tonian]] color:tonian from: -1200 till: -1000 text:[[Special:MyLanguage/Stenian|Stenian]] color:stenian from: -1400 till: -1200 text:[[Special:MyLanguage/Ectasian|Ectasian]] color:ectasian from: -1600 till: -1400 text:[[Special:MyLanguage/Calymmian|Calymm]] color:calymmian from: -1800 till: -1600 text:[[Special:MyLanguage/Statherian|Stather]] color:statherian from: -2050 till: -1800 text:[[Special:MyLanguage/Orosirian|Orosirian]] color:orosirian from: -2300 till: -2050 text:[[Special:MyLanguage/Rhyacian|Rhyacian]] color:rhyacian from: -2500 till: -2300 text:[[Special:MyLanguage/Siderian|Siderian]] color:siderian from: start till: -2500 color:white </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:phanerozoic value:rgb(0.435,0.85,0.866) id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:neogene value:rgb(1,0.901,0.098) id:paleogene value:rgb(0.992,0.603,0.321) id:mesozoic value:rgb(0.403,0.772,0.792) id:cretaceous value:rgb(0.498,0.776,0.306) id:jurassic value:rgb(0.203,0.698,0.788) id:triassic value:rgb(0.505,0.168,0.572) id:paleozoic value:rgb(0.6,0.752,0.552) id:permian value:rgb(0.941,0.25,0.156) id:carboniferous value:rgb(0.403,0.647,0.6) id:devonian value:rgb(0.796,0.549,0.215) id:silurian value:rgb(0.702,0.882,0.713) id:ordovician value:rgb(0,0.572,0.439) id:cambrian value:rgb(0.496,0.627,0.337) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-542 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:100 start:-500 ScaleMinor = unit:year increment:10 start:-540 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:eon at: 0 align:right $markred at: -542 align:left $markred shift:(2,3) from: -542 till: 0 text:[[Special:MyLanguage/Phanerozoic|Phanerozoic]] color:phanerozoic bar:era at: 0 align:right $markgreen at: -65.5 align:left $markgreen shift:(2,3) from: -65.5 till: 0 text:[[Special:MyLanguage/Cenozoic|Cenozoic]] color:cenozoic from: -251 till: -65.5 text:[[Special:MyLanguage/Mesozoic|Mesozoic]] color:mesozoic from: -542 till: -251 text:[[Special:MyLanguage/Paleozoic|Paleozoic]] color:paleozoic bar:period fontsize:8 from: -2.588 till: 0 text:[[Special:MyLanguage/Quaternary|Q.]] color:quaternary from: -23.03 till: -2.588 text:[[Special:MyLanguage/Neogene|Neo]] color:neogene from: -65.5 till: -23.03 text:[[Special:MyLanguage/Paleogene|Paleogene]] color:paleogene from: -145.5 till: -65.5 text:[[Special:MyLanguage/Cretaceous|Cretaceous]] color:cretaceous from: -199.6 till: -145.5 text:[[Special:MyLanguage/Jurassic|Jurassic]] color:jurassic from: -251.4 till: -199.6 text:[[Special:MyLanguage/Triassic|Triassic]] color:triassic from: -299 till: -251.4 text:[[Special:MyLanguage/Permian|Permian]] color:permian from: -359.2 till: -299 text:[[Special:MyLanguage/Carboniferous|Carboniferous]] color:carboniferous from: -416 till: -359.2 text:[[Special:MyLanguage/Devonian|Devonian]] color:devonian from: -443.7 till: -416 text:[[Special:MyLanguage/Silurian|Silurian]] color:silurian from: -488.3 till: -443.7 text:[[Special:MyLanguage/Ordovician|Ordovician]] color:ordovician from: -542 till: -488.3 text:[[Cambrian] color:cambrian </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:holocene value:rgb(0.996,0.949,0.878) id:pleistocene value:rgb(1,0.949,0.678) id:neogene value:rgb(1,0.901,0.098) id:pliocene value:rgb(1,1,0.6) id:miocene value:rgb(1,1,0) id:paleogene value:rgb(0.992,0.603,0.321) id:oligocene value:rgb(0.992,0.752,0.478) id:eocene value:rgb(0.992,0.705,0.423) id:paleocene value:rgb(0.992,0.654,0.372) id:cambrian value:rgb(0.496,0.627,0.337) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-65.5 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:10 start:-60 ScaleMinor = unit:year increment:1 start:-65 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:era at: 0 align:right $markgreen at: start align:left $markgreen shift:(2,3) from:start till: 0 text:[[Cenozoic|Cambrian]] color:cambrian </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:holocene value:rgb(0.996,0.949,0.878) id:pleistocene value:rgb(1,0.949,0.678) id:neogene value:rgb(1,0.901,0.098) id:pliocene value:rgb(1,1,0.6) id:miocene value:rgb(1,1,0) id:paleogene value:rgb(0.992,0.603,0.321) id:oligocene value:rgb(0.992,0.752,0.478) id:eocene value:rgb(0.992,0.705,0.423) id:paleocene value:rgb(0.992,0.654,0.372) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-65.5 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:10 start:-60 ScaleMinor = unit:year increment:1 start:-65 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:era at: 0 align:right $markgreen at: start align:left $markgreen shift:(2,3) from:start till: 0 text:[[Special:MyLanguage/Cenozoic|Cenozoic]] color:cenozoic bar:period from: -2.588 till: 0 text:[[Special:MyLanguage/Quaternary|Q.]] color:quaternary from: -23.03 till: -2.588 text:[[Special:MyLanguage/Neogene|Neogene]] color:neogene from: start till: -23.03 text:[[Special:MyLanguage/Paleogene|Paleogene]] color:paleogene bar:epoch from: -0.1 till: 0 text:[[Special:MyLanguage/Holocene|H]] color:holocene from: -2.588 till: -0.1 text:[[Special:MyLanguage/Pleistocene|P]] color:pleistocene from: -5.332 till: -2.588 text:[[Special:MyLanguage/Pliocene|Pliocene]] color:pliocene fontsize:7 from: -23.03 till: -5.332 text:[[Special:MyLanguage/Miocene|Miocene]] color:miocene from: -33.9 till: -23.03 text:[[Special:MyLanguage/Oligocene|Oligocene]] color:oligocene from: -55.8 till: -33.9 text:[[Special:MyLanguage/Eocene|Eocene]] color:eocene from: start till: -55.8 text:[[Special:MyLanguage/Paleocene|Paleocene]] color:paleocene </timeline> </td></tr> <tr><td colspan=3 align=left>{{Wikimedia Growth}}</td></tr> </table> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Code example== </div> :''Siehe auch:'' {{ll|Extension:EasyTimeline/syntax}} <timeline> # All measures are in pixels ImageSize = width:160 height:550 PlotArea = left:50 right:0 bottom:10 top:10 AlignBars = justify DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef~Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> <div lang="en" dir="ltr" class="mw-content-ltr"> Just to show you that the script syntax is reasonably intuitive, here is the script for the image above: Soviet Leaders. </div> <syntaxhighlight lang="moin"> <timeline> # All measures are in pixels ImageSize = width:160 height:550 PlotArea = left:50 right:0 bottom:10 top:10 AlignBars = justify DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef~Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Double and single brackets can be used like on wikipedia, language prefix is possible, e.g. <syntaxhighlight lang="moin" inline>[[de:foo|more about foo]]</syntaxhighlight>. Single brackets for external links are also supported. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Great timelines elsewhere== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here are two great sites that may serve as inspiration, it would be very easy to recreate most of those timelines verbatim and with roughly similar layout with EasyTimeline (not yet with images but that may change), but I'm afraid that would be 'not done'. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[http://www.hyperhistory.com/online_n2/History_n2/a.html Hyperhistory] e.g. click on button 'people' left, then on 'special lifelines', right. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *I hope we will have a set like [http://chaos1.hypermart.net/fullsize.htm] in a years time (click on ''full size image'' for any map), possibly even with images. The main effort will be to gather all info without snatching everything from here (most of these maps are based exclusively on data from Britannica). </div> ==Unicode== <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline does not yet support unicode. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Aug 2004: Minimal UTF-8 support has been added, meaning that EasyTimeline now recognizes UTF-8 encoded characters. However support for directionality and complex scripts is very lacking. The default font may not have glyphs for all characters. An alternate font can be specified via <code>$wgTimelineFontFile</code> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SVG to PNG=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To show texts correctly for RTL languages (like Arabic, Persian, Hebrew,...) you can use {{tmpl|0={{tag|timeline|params={{attr|method|"svg2png"}}|content=$1}}|timeline code here}} instead of {{tmpl|0={{tag|timeline|content=$1}}|timeline code here}}. it shows timeline as png but the links will be disabled. </div> == Tipps == <div lang="en" dir="ltr" class="mw-content-ltr"> For first time users EasyTimeline may not seem that easy at all. As with all script languages it takes some getting used to. Also the syntax description may be a bit bewildering due to its sheer size. Fortunately many elements of the script language are optional. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The 'Easy' in EasyTimeline conveys the message that once a timeline exists it is not so hard to understand, enhance or correct. Also translating for use on another Wikipedia it is pretty straightforward. </div> Tipps <div lang="en" dir="ltr" class="mw-content-ltr"> * See some [[#charts-examples|chart examples]] to find something you could pick and edit for your own stuff </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *Put each timeline on a separate Template page: this makes it easier to edit, faster to preview, possible to include it in several pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Using the current date== </div> <span lang="en" dir="ltr" class="mw-content-ltr">To use the current date make sure the table opens with <code><nowiki>{{#tag:timeline|</nowiki></code> and closes with <code><nowiki>}}</nowiki></code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then the current date can be inserted using magic words.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example <code><nowiki>{{#time: d/m/Y }}</nowiki></code> or <code><nowiki>{{CURRENTDAY2}}/{{CURRENTMONTH2}}/{{CURRENTYEAR}}</nowiki></code> will both yield the date in format dd/mm/yyyy.</span> == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> *[[Special:MyLanguage/Extension:EasyTimeline/syntax|EasyTimeline Coding]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *Presentation about EasyTimeline at Wikimania 2005 ([[m:Transwiki:Wikimania05/Workshop-EZ1|abstract]], [http://upload.wikimedia.org/wikipedia/commons/9/90/Wikimania_2005_Presentation_EasyTimeline.pdf slides], [http://upload.wikimedia.org/wikipedia/commons/7/78/Wikimania_2005_Presentation_Easytimeline_Speaker_Notes.pdf speaker notes]) </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[m:WikiTimeScale|m:WikiTimeScale]] as a proposal for realizing timescales for wikipedia articles externally. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[w:Template:Simple Horizontal timeline|w:Template:Simple Horizontal timeline]] An easier timeline to use on Wikipedia. </div> *{{ll|Extension:Graph}} ==Installation== <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Special:MyLanguage/Extension:EasyTimeline/installation|/installation]] </div> == Externe Links == * [http://www.simile-widgets.org <span lang="en" dir="ltr" class="mw-content-ltr">SIMILE Widgets</span>] - DHTML-based AJAXy widget for visualizing time-based events {{OnWikimedia}} {{Used by|fandom=1}} 32v75osxuk6cp3e52oqfr5l7rnzyovg 5386919 5386917 2022-07-28T19:43:32Z ThisCarthing 17456337 wikitext text/x-wiki <languages /> {{Extension |type1 = tag |status = stable |author = [[w:User:Erik Zachte|Erik Zachte]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds {{tag|timeline|open}} tag for creating timelines</span> |download = {{WikimediaDownload|timeline}} |needs-updatephp = no |changelog = {{git file|action=summary|project=mediawiki/extensions/timeline|branch=HEAD|text=CHANGELOG}} |phabricator = EasyTimeline |pagedrive1 = true |example = [[#charts-examples|Siehe unten]] |translate = ext-timeline }} :''Andere Sprachen:'' [[Extension:EasyTimeline/ar|ar]] [[:de:Hilfe:Zeitleisten|de]] [[:es:Ayuda:Cronologías|es]] [[:eu:Laguntza:Denbora lerroak|eu]] [[:fr:Aide:Frise chronologique|fr]] [[:id:Wikipedia:Timeline|id]] [[:it:Aiuto:Timeline|it]] [[Extension:EasyTimeline/ja|ja]] [[:nl:Help:EasyTimeline|nl]] [[:pt:Wikipedia:EasyTimeline|pt]] [[Extension:EasyTimeline/tr|tr]] [[:zh:Help:简易时间线语法|zh]] <div lang="en" dir="ltr" class="mw-content-ltr"> The '''EasyTimeline''' extension produces an embedded image from wikitext. The image can be a one-dimensional diagram (horizontally or vertically), or a two-dimensional one. </div> <span lang="en" dir="ltr" class="mw-content-ltr">See the help page on [[Special:MyLanguage/Extension:EasyTimeline/installation|installing EasyTimeline]] on your wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://infodisiac.com/Wikipedia/EasyTimeline/Introduction.htm this page on EasyTimeline] or play with it at [[testwiki:EasyTimeline|test.wikipedia.org]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See the help page on [[Special:MyLanguage/Extension:EasyTimeline/syntax|using the syntax provided by this extension]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There is a [[phab:T137291|long-term effort]] to get the {{ll|Extension:Graph|Graph}} extension to replace this extension. </div> == Voraussetzungen == <div lang="en" dir="ltr" class="mw-content-ltr"> This extension requires the following programs installed on the server: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:Ploticus|Ploticus]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:perl|perl]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:XnView|NConvert]] (Windows only) </div> {{anchor|charts-examples}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Charts examples== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Several examples of what is possible. For more extensive examples see </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Timeline WWII - Pacific Theater|WW II - Pacific Theatre]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Timeline of aircraft carriers of the United States Navy|:en:Timeline of aircraft carriers of the United States Navy]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Timeline History of Computing|History of Computing]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:de:Vorlage:Zeitleiste Tour-de-France-Sieger|Tour-de-France Sieger]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Vocal and instrumental pitch ranges|Vocal and instrumental pitch ranges]] (a nice example of a diagram that is not a timeline at all) - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Complete timeline of Macintosh models|Complete timeline of Macintosh models]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Simpler timelines: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Template:Extinction events graphical timeline|:en:Template:Extinction events graphical timeline]] - horizontal, uses [[w:Template:Horizontal timeline|w:Template:Horizontal timeline]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Talk:Invention_of_radio/Archive_1#Timeline.2C_Players|:en:Talk:Invention_of_radio/Archive_1#Timeline.2C_Players]] - horizontal with arrows </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Template:Early evolution of the light bulb|:en:Template:Early evolution of the light bulb]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Invention of radio#Radio invention timeline|:en:Invention of radio#Radio invention timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Gaius_Marius#Timeline|:en:Gaius_Marius#Timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:User:Syed Atif Nazir/Template:Imam timeline|:en:User:Syed Atif Nazir/Template:Imam timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [https://de.wikipedia.org/w/index.php?title=Aurich&oldid=171331690#Einwohnerentwicklung Population developement] - horizontal </div> <table><tr> <td valign=top> <timeline> ImageSize = width:160 height:550 PlotArea = width:50 height:530 left:50 bottom:10 DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> </td> <td>&nbsp;&nbsp;</td> <td valign=top> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:phanerozoic value:rgb(0.435,0.85,0.866) id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:neogene value:rgb(1,0.901,0.098) id:paleogene value:rgb(0.992,0.603,0.321) id:mesozoic value:rgb(0.403,0.772,0.792) id:cretaceous value:rgb(0.498,0.776,0.306) id:jurassic value:rgb(0.203,0.698,0.788) id:triassic value:rgb(0.505,0.168,0.572) id:paleozoic value:rgb(0.6,0.752,0.552) id:permian value:rgb(0.941,0.25,0.156) id:carboniferous value:rgb(0.403,0.647,0.6) id:devonian value:rgb(0.796,0.549,0.215) id:silurian value:rgb(0.702,0.882,0.713) id:ordovician value:rgb(0,0.572,0.439) id:cambrian value:rgb(0.496,0.627,0.337) id:proterozoic value:rgb(0.968,0.207,0.388) id:neoproterozoic value:rgb(0.996,0.701,0.258) id:ediacaran value:rgb(0.996,0.85,0.415) id:cryogenian value:rgb(0.996,0.8,0.36) id:tonian value:rgb(0.996,0.75,0.305) id:mesoproterozoic value:rgb(0.996,0.705,0.384) id:stenian value:rgb(0.996,0.85,0.604) id:ectasian value:rgb(0.996,0.8,0.541) id:calymmian value:rgb(0.996,0.75,0.478) id:paleoproterozoic value:rgb(0.968,0.263,0.44) id:statherian value:rgb(0.968,0.459,0.655) id:orosirian value:rgb(0.968,0.408,0.596) id:rhyacian value:rgb(0.968,0.357,0.537) id:siderian value:rgb(0.968,0.306,0.478) id:archean value:rgb(0.996,0.157,0.498) id:neoarchean value:rgb(0.976,0.608,0.757) id:mesoarchean value:rgb(0.968,0.408,0.662) id:paleoarchean value:rgb(0.96,0.266,0.624) id:eoarchean value:rgb(0.902,0.114,0.549) id:hadean value:rgb(0.717,0,0.494) id:black value:black id:white value:white Period = from:-4567 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:500 start:-4500 ScaleMinor = unit:year increment:100 start:-4500 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:eon at: 0 align:right $markred at: -542 align:left $markred shift:(2,3) from: -542 till: 0 text:[[Special:MyLanguage/Phanerozoic|Phanerozoic]] color:phanerozoic from: -2500 till: -542 text:[[Special:MyLanguage/Proterozoic|Proterozoic]] color:proterozoic from: -4000 till: -2500 text:[[Special:MyLanguage/Archean|Archean]] color:archean from: start till: -4000 text:[[Special:MyLanguage/Hadean|Hadean]] color:hadean bar:era from: -65.5 till: 0 text:[[Special:MyLanguage/Cenozoic|C]] color:cenozoic from: -251 till: -65.5 text:[[Special:MyLanguage/Mesozoic|Meso]] color:mesozoic from: -542 till: -251 text:[[Special:MyLanguage/Paleozoic|Paleozoic]] color:paleozoic from: -1000 till: -542 text:[[Special:MyLanguage/Neoproterozoic|Neoproterozoic]] color:neoproterozoic from: -1600 till: -1000 text:[[Special:MyLanguage/Mesoproterozoic|Mesoproterozoic]] color:mesoproterozoic from: -2500 till: -1600 text:[[Special:MyLanguage/Paleoproterozoic|Paleoproterozoic]] color:paleoproterozoic from: -2800 till: -2500 text:[[Special:MyLanguage/Neoarchean|Neoarch]] color:neoarchean from: -3200 till: -2800 text:[[Special:MyLanguage/Mesoarchean|Mesoarch]] color:mesoarchean from: -3600 till: -3200 text:[[Special:MyLanguage/Paleoarchean|Paleoarch]] color:paleoarchean from: -4000 till: -3600 text:[[Special:MyLanguage/Eoarchean|Eoarchean]] color:eoarchean from: start till: -4000 color:white bar:period fontsize:6 from: -2.6 till: 0 color:quaternary from: -23.03 till: -2.6 color:neogene from: -65.5 till: -23.03 color:paleogene from: -145.5 till: -65.5 color:cretaceous from: -199.6 till: -145.5 color:jurassic from: -251 till: -199.6 color:triassic from: -299 till: -251 color:permian from: -359.2 till: -299 color:carboniferous from: -416 till: -359.2 color:devonian from: -443.7 till: -416 color:silurian from: -488.3 till: -443.7 color:ordovician from: -542 till: -488.3 color:cambrian from: -635 till: -542 text:[[Special:MyLanguage/Ediacaran|Ed.]] color:ediacaran from: -850 till: -635 text:[[Special:MyLanguage/Cryogenian|Cryo]] color:cryogenian from: -1000 till: -850 text:[[Special:MyLanguage/Tonian|Tonian]] color:tonian from: -1200 till: -1000 text:[[Special:MyLanguage/Stenian|Stenian]] color:stenian from: -1400 till: -1200 text:[[Special:MyLanguage/Ectasian|Ectasian]] color:ectasian from: -1600 till: -1400 text:[[Special:MyLanguage/Calymmian|Calymm]] color:calymmian from: -1800 till: -1600 text:[[Special:MyLanguage/Statherian|Stather]] color:statherian from: -2050 till: -1800 text:[[Special:MyLanguage/Orosirian|Orosirian]] color:orosirian from: -2300 till: -2050 text:[[Special:MyLanguage/Rhyacian|Rhyacian]] color:rhyacian from: -2500 till: -2300 text:[[Special:MyLanguage/Siderian|Siderian]] color:siderian from: start till: -2500 color:white </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:phanerozoic value:rgb(0.435,0.85,0.866) id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:neogene value:rgb(1,0.901,0.098) id:paleogene value:rgb(0.992,0.603,0.321) id:mesozoic value:rgb(0.403,0.772,0.792) id:cretaceous value:rgb(0.498,0.776,0.306) id:jurassic value:rgb(0.203,0.698,0.788) id:triassic value:rgb(0.505,0.168,0.572) id:paleozoic value:rgb(0.6,0.752,0.552) id:permian value:rgb(0.941,0.25,0.156) id:carboniferous value:rgb(0.403,0.647,0.6) id:devonian value:rgb(0.796,0.549,0.215) id:silurian value:rgb(0.702,0.882,0.713) id:ordovician value:rgb(0,0.572,0.439) id:cambrian value:rgb(0.496,0.627,0.337) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-542 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:100 start:-500 ScaleMinor = unit:year increment:10 start:-540 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:eon at: 0 align:right $markred at: -542 align:left $markred shift:(2,3) from: -542 till: 0 text:[[Special:MyLanguage/Phanerozoic|Phanerozoic]] color:phanerozoic bar:era at: 0 align:right $markgreen at: -65.5 align:left $markgreen shift:(2,3) from: -65.5 till: 0 text:[[Special:MyLanguage/Cenozoic|Cenozoic]] color:cenozoic from: -251 till: -65.5 text:[[Special:MyLanguage/Mesozoic|Mesozoic]] color:mesozoic from: -542 till: -251 text:[[Special:MyLanguage/Paleozoic|Paleozoic]] color:paleozoic bar:period fontsize:8 from: -2.588 till: 0 text:[[Special:MyLanguage/Quaternary|Q.]] color:quaternary from: -23.03 till: -2.588 text:[[Special:MyLanguage/Neogene|Neo]] color:neogene from: -65.5 till: -23.03 text:[[Special:MyLanguage/Paleogene|Paleogene]] color:paleogene from: -145.5 till: -65.5 text:[[Special:MyLanguage/Cretaceous|Cretaceous]] color:cretaceous from: -199.6 till: -145.5 text:[[Special:MyLanguage/Jurassic|Jurassic]] color:jurassic from: -251.4 till: -199.6 text:[[Special:MyLanguage/Triassic|Triassic]] color:triassic from: -299 till: -251.4 text:[[Special:MyLanguage/Permian|Permian]] color:permian from: -359.2 till: -299 text:[[Special:MyLanguage/Carboniferous|Carboniferous]] color:carboniferous from: -416 till: -359.2 text:[[Special:MyLanguage/Devonian|Devonian]] color:devonian from: -443.7 till: -416 text:[[Special:MyLanguage/Silurian|Silurian]] color:silurian from: -488.3 till: -443.7 text:[[Special:MyLanguage/Ordovician|Ordovician]] color:ordovician from: -542 till: -488.3 text:[[Cambrian] color:cambrian </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:holocene value:rgb(0.996,0.949,0.878) id:pleistocene value:rgb(1,0.949,0.678) id:neogene value:rgb(1,0.901,0.098) id:pliocene value:rgb(1,1,0.6) id:miocene value:rgb(1,1,0) id:paleogene value:rgb(0.992,0.603,0.321) id:oligocene value:rgb(0.992,0.752,0.478) id:eocene value:rgb(0.992,0.705,0.423) id:paleocene value:rgb(0.992,0.654,0.372) id:cambrian value:rgb(0.496,0.627,0.337) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-65.5 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:10 start:-60 ScaleMinor = unit:year increment:1 start:-65 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:era at: 0 align:right $markgreen at: start align:left $markgreen shift:(2,3) from:start till: 0 text:[[Cenozoic|Cambrian]] color:cambrian </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:holocene value:rgb(0.996,0.949,0.878) id:pleistocene value:rgb(1,0.949,0.678) id:neogene value:rgb(1,0.901,0.098) id:pliocene value:rgb(1,1,0.6) id:miocene value:rgb(1,1,0) id:paleogene value:rgb(0.992,0.603,0.321) id:oligocene value:rgb(0.992,0.752,0.478) id:eocene value:rgb(0.992,0.705,0.423) id:paleocene value:rgb(0.992,0.654,0.372) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-65.5 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:10 start:-60 ScaleMinor = unit:year increment:1 start:-65 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:era at: 0 align:right $markgreen at: start align:left $markgreen shift:(2,3) from:start till: 0 text:[[Special:MyLanguage/Cenozoic|Cenozoic]] color:cenozoic bar:period from: -2.588 till: 0 text:[[Special:MyLanguage/Quaternary|Q.]] color:quaternary from: -23.03 till: -2.588 text:[[Special:MyLanguage/Neogene|Neogene]] color:neogene from: start till: -23.03 text:[[Special:MyLanguage/Paleogene|Paleogene]] color:paleogene bar:epoch from: -0.1 till: 0 text:[[Special:MyLanguage/Holocene|H]] color:holocene from: -2.588 till: -0.1 text:[[Special:MyLanguage/Pleistocene|P]] color:pleistocene from: -5.332 till: -2.588 text:[[Special:MyLanguage/Pliocene|Pliocene]] color:pliocene fontsize:7 from: -23.03 till: -5.332 text:[[Special:MyLanguage/Miocene|Miocene]] color:miocene from: -33.9 till: -23.03 text:[[Special:MyLanguage/Oligocene|Oligocene]] color:oligocene from: -55.8 till: -33.9 text:[[Special:MyLanguage/Eocene|Eocene]] color:eocene from: start till: -55.8 text:[[Special:MyLanguage/Paleocene|Paleocene]] color:paleocene </timeline> </td></tr> <tr><td colspan=3 align=left>{{Wikimedia Growth}}</td></tr> </table> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Code example== </div> :''Siehe auch:'' {{ll|Extension:EasyTimeline/syntax}} <timeline> # All measures are in pixels ImageSize = width:160 height:550 PlotArea = left:50 right:0 bottom:10 top:10 AlignBars = justify DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef~Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> <div lang="en" dir="ltr" class="mw-content-ltr"> Just to show you that the script syntax is reasonably intuitive, here is the script for the image above: Soviet Leaders. </div> <syntaxhighlight lang="moin"> <timeline> # All measures are in pixels ImageSize = width:160 height:550 PlotArea = left:50 right:0 bottom:10 top:10 AlignBars = justify DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef~Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Double and single brackets can be used like on wikipedia, language prefix is possible, e.g. <syntaxhighlight lang="moin" inline>[[de:foo|more about foo]]</syntaxhighlight>. Single brackets for external links are also supported. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Great timelines elsewhere== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here are two great sites that may serve as inspiration, it would be very easy to recreate most of those timelines verbatim and with roughly similar layout with EasyTimeline (not yet with images but that may change), but I'm afraid that would be 'not done'. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[http://www.hyperhistory.com/online_n2/History_n2/a.html Hyperhistory] e.g. click on button 'people' left, then on 'special lifelines', right. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *I hope we will have a set like [http://chaos1.hypermart.net/fullsize.htm] in a years time (click on ''full size image'' for any map), possibly even with images. The main effort will be to gather all info without snatching everything from here (most of these maps are based exclusively on data from Britannica). </div> ==Unicode== <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline does not yet support unicode. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Aug 2004: Minimal UTF-8 support has been added, meaning that EasyTimeline now recognizes UTF-8 encoded characters. However support for directionality and complex scripts is very lacking. The default font may not have glyphs for all characters. An alternate font can be specified via <code>$wgTimelineFontFile</code> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SVG to PNG=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To show texts correctly for RTL languages (like Arabic, Persian, Hebrew,...) you can use {{tmpl|0={{tag|timeline|params={{attr|method|"svg2png"}}|content=$1}}|timeline code here}} instead of {{tmpl|0={{tag|timeline|content=$1}}|timeline code here}}. it shows timeline as png but the links will be disabled. </div> == Tipps == <div lang="en" dir="ltr" class="mw-content-ltr"> For first time users EasyTimeline may not seem that easy at all. As with all script languages it takes some getting used to. Also the syntax description may be a bit bewildering due to its sheer size. Fortunately many elements of the script language are optional. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The 'Easy' in EasyTimeline conveys the message that once a timeline exists it is not so hard to understand, enhance or correct. Also translating for use on another Wikipedia it is pretty straightforward. </div> Tipps: <div lang="en" dir="ltr" class="mw-content-ltr"> * See some [[#charts-examples|chart examples]] to find something you could pick and edit for your own stuff </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *Put each timeline on a separate Template page: this makes it easier to edit, faster to preview, possible to include it in several pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Using the current date== </div> <span lang="en" dir="ltr" class="mw-content-ltr">To use the current date make sure the table opens with <code><nowiki>{{#tag:timeline|</nowiki></code> and closes with <code><nowiki>}}</nowiki></code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then the current date can be inserted using magic words.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example <code><nowiki>{{#time: d/m/Y }}</nowiki></code> or <code><nowiki>{{CURRENTDAY2}}/{{CURRENTMONTH2}}/{{CURRENTYEAR}}</nowiki></code> will both yield the date in format dd/mm/yyyy.</span> == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> *[[Special:MyLanguage/Extension:EasyTimeline/syntax|EasyTimeline Coding]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *Presentation about EasyTimeline at Wikimania 2005 ([[m:Transwiki:Wikimania05/Workshop-EZ1|abstract]], [http://upload.wikimedia.org/wikipedia/commons/9/90/Wikimania_2005_Presentation_EasyTimeline.pdf slides], [http://upload.wikimedia.org/wikipedia/commons/7/78/Wikimania_2005_Presentation_Easytimeline_Speaker_Notes.pdf speaker notes]) </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[m:WikiTimeScale|m:WikiTimeScale]] as a proposal for realizing timescales for wikipedia articles externally. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[w:Template:Simple Horizontal timeline|w:Template:Simple Horizontal timeline]] An easier timeline to use on Wikipedia. </div> *{{ll|Extension:Graph}} ==Installation== <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Special:MyLanguage/Extension:EasyTimeline/installation|/installation]] </div> == Externe Links == * [http://www.simile-widgets.org <span lang="en" dir="ltr" class="mw-content-ltr">SIMILE Widgets</span>] - DHTML-based AJAXy widget for visualizing time-based events {{OnWikimedia}} {{Used by|fandom=1}} owvls2dg6qffgbolzw5zxnqzwhyy4fp 5386921 5386919 2022-07-28T19:43:45Z ThisCarthing 17456337 Created page with "Siehe [[$1|/installation]]" wikitext text/x-wiki <languages /> {{Extension |type1 = tag |status = stable |author = [[w:User:Erik Zachte|Erik Zachte]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds {{tag|timeline|open}} tag for creating timelines</span> |download = {{WikimediaDownload|timeline}} |needs-updatephp = no |changelog = {{git file|action=summary|project=mediawiki/extensions/timeline|branch=HEAD|text=CHANGELOG}} |phabricator = EasyTimeline |pagedrive1 = true |example = [[#charts-examples|Siehe unten]] |translate = ext-timeline }} :''Andere Sprachen:'' [[Extension:EasyTimeline/ar|ar]] [[:de:Hilfe:Zeitleisten|de]] [[:es:Ayuda:Cronologías|es]] [[:eu:Laguntza:Denbora lerroak|eu]] [[:fr:Aide:Frise chronologique|fr]] [[:id:Wikipedia:Timeline|id]] [[:it:Aiuto:Timeline|it]] [[Extension:EasyTimeline/ja|ja]] [[:nl:Help:EasyTimeline|nl]] [[:pt:Wikipedia:EasyTimeline|pt]] [[Extension:EasyTimeline/tr|tr]] [[:zh:Help:简易时间线语法|zh]] <div lang="en" dir="ltr" class="mw-content-ltr"> The '''EasyTimeline''' extension produces an embedded image from wikitext. The image can be a one-dimensional diagram (horizontally or vertically), or a two-dimensional one. </div> <span lang="en" dir="ltr" class="mw-content-ltr">See the help page on [[Special:MyLanguage/Extension:EasyTimeline/installation|installing EasyTimeline]] on your wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://infodisiac.com/Wikipedia/EasyTimeline/Introduction.htm this page on EasyTimeline] or play with it at [[testwiki:EasyTimeline|test.wikipedia.org]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See the help page on [[Special:MyLanguage/Extension:EasyTimeline/syntax|using the syntax provided by this extension]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There is a [[phab:T137291|long-term effort]] to get the {{ll|Extension:Graph|Graph}} extension to replace this extension. </div> == Voraussetzungen == <div lang="en" dir="ltr" class="mw-content-ltr"> This extension requires the following programs installed on the server: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:Ploticus|Ploticus]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:perl|perl]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[w:XnView|NConvert]] (Windows only) </div> {{anchor|charts-examples}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Charts examples== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Several examples of what is possible. For more extensive examples see </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Timeline WWII - Pacific Theater|WW II - Pacific Theatre]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Timeline of aircraft carriers of the United States Navy|:en:Timeline of aircraft carriers of the United States Navy]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Timeline History of Computing|History of Computing]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:de:Vorlage:Zeitleiste Tour-de-France-Sieger|Tour-de-France Sieger]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Vocal and instrumental pitch ranges|Vocal and instrumental pitch ranges]] (a nice example of a diagram that is not a timeline at all) - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:en:Template:Complete timeline of Macintosh models|Complete timeline of Macintosh models]] - horizontal </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Simpler timelines: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Template:Extinction events graphical timeline|:en:Template:Extinction events graphical timeline]] - horizontal, uses [[w:Template:Horizontal timeline|w:Template:Horizontal timeline]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Talk:Invention_of_radio/Archive_1#Timeline.2C_Players|:en:Talk:Invention_of_radio/Archive_1#Timeline.2C_Players]] - horizontal with arrows </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Template:Early evolution of the light bulb|:en:Template:Early evolution of the light bulb]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Invention of radio#Radio invention timeline|:en:Invention of radio#Radio invention timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:Gaius_Marius#Timeline|:en:Gaius_Marius#Timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [[:en:User:Syed Atif Nazir/Template:Imam timeline|:en:User:Syed Atif Nazir/Template:Imam timeline]] - vertical </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ** [https://de.wikipedia.org/w/index.php?title=Aurich&oldid=171331690#Einwohnerentwicklung Population developement] - horizontal </div> <table><tr> <td valign=top> <timeline> ImageSize = width:160 height:550 PlotArea = width:50 height:530 left:50 bottom:10 DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> </td> <td>&nbsp;&nbsp;</td> <td valign=top> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:phanerozoic value:rgb(0.435,0.85,0.866) id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:neogene value:rgb(1,0.901,0.098) id:paleogene value:rgb(0.992,0.603,0.321) id:mesozoic value:rgb(0.403,0.772,0.792) id:cretaceous value:rgb(0.498,0.776,0.306) id:jurassic value:rgb(0.203,0.698,0.788) id:triassic value:rgb(0.505,0.168,0.572) id:paleozoic value:rgb(0.6,0.752,0.552) id:permian value:rgb(0.941,0.25,0.156) id:carboniferous value:rgb(0.403,0.647,0.6) id:devonian value:rgb(0.796,0.549,0.215) id:silurian value:rgb(0.702,0.882,0.713) id:ordovician value:rgb(0,0.572,0.439) id:cambrian value:rgb(0.496,0.627,0.337) id:proterozoic value:rgb(0.968,0.207,0.388) id:neoproterozoic value:rgb(0.996,0.701,0.258) id:ediacaran value:rgb(0.996,0.85,0.415) id:cryogenian value:rgb(0.996,0.8,0.36) id:tonian value:rgb(0.996,0.75,0.305) id:mesoproterozoic value:rgb(0.996,0.705,0.384) id:stenian value:rgb(0.996,0.85,0.604) id:ectasian value:rgb(0.996,0.8,0.541) id:calymmian value:rgb(0.996,0.75,0.478) id:paleoproterozoic value:rgb(0.968,0.263,0.44) id:statherian value:rgb(0.968,0.459,0.655) id:orosirian value:rgb(0.968,0.408,0.596) id:rhyacian value:rgb(0.968,0.357,0.537) id:siderian value:rgb(0.968,0.306,0.478) id:archean value:rgb(0.996,0.157,0.498) id:neoarchean value:rgb(0.976,0.608,0.757) id:mesoarchean value:rgb(0.968,0.408,0.662) id:paleoarchean value:rgb(0.96,0.266,0.624) id:eoarchean value:rgb(0.902,0.114,0.549) id:hadean value:rgb(0.717,0,0.494) id:black value:black id:white value:white Period = from:-4567 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:500 start:-4500 ScaleMinor = unit:year increment:100 start:-4500 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:eon at: 0 align:right $markred at: -542 align:left $markred shift:(2,3) from: -542 till: 0 text:[[Special:MyLanguage/Phanerozoic|Phanerozoic]] color:phanerozoic from: -2500 till: -542 text:[[Special:MyLanguage/Proterozoic|Proterozoic]] color:proterozoic from: -4000 till: -2500 text:[[Special:MyLanguage/Archean|Archean]] color:archean from: start till: -4000 text:[[Special:MyLanguage/Hadean|Hadean]] color:hadean bar:era from: -65.5 till: 0 text:[[Special:MyLanguage/Cenozoic|C]] color:cenozoic from: -251 till: -65.5 text:[[Special:MyLanguage/Mesozoic|Meso]] color:mesozoic from: -542 till: -251 text:[[Special:MyLanguage/Paleozoic|Paleozoic]] color:paleozoic from: -1000 till: -542 text:[[Special:MyLanguage/Neoproterozoic|Neoproterozoic]] color:neoproterozoic from: -1600 till: -1000 text:[[Special:MyLanguage/Mesoproterozoic|Mesoproterozoic]] color:mesoproterozoic from: -2500 till: -1600 text:[[Special:MyLanguage/Paleoproterozoic|Paleoproterozoic]] color:paleoproterozoic from: -2800 till: -2500 text:[[Special:MyLanguage/Neoarchean|Neoarch]] color:neoarchean from: -3200 till: -2800 text:[[Special:MyLanguage/Mesoarchean|Mesoarch]] color:mesoarchean from: -3600 till: -3200 text:[[Special:MyLanguage/Paleoarchean|Paleoarch]] color:paleoarchean from: -4000 till: -3600 text:[[Special:MyLanguage/Eoarchean|Eoarchean]] color:eoarchean from: start till: -4000 color:white bar:period fontsize:6 from: -2.6 till: 0 color:quaternary from: -23.03 till: -2.6 color:neogene from: -65.5 till: -23.03 color:paleogene from: -145.5 till: -65.5 color:cretaceous from: -199.6 till: -145.5 color:jurassic from: -251 till: -199.6 color:triassic from: -299 till: -251 color:permian from: -359.2 till: -299 color:carboniferous from: -416 till: -359.2 color:devonian from: -443.7 till: -416 color:silurian from: -488.3 till: -443.7 color:ordovician from: -542 till: -488.3 color:cambrian from: -635 till: -542 text:[[Special:MyLanguage/Ediacaran|Ed.]] color:ediacaran from: -850 till: -635 text:[[Special:MyLanguage/Cryogenian|Cryo]] color:cryogenian from: -1000 till: -850 text:[[Special:MyLanguage/Tonian|Tonian]] color:tonian from: -1200 till: -1000 text:[[Special:MyLanguage/Stenian|Stenian]] color:stenian from: -1400 till: -1200 text:[[Special:MyLanguage/Ectasian|Ectasian]] color:ectasian from: -1600 till: -1400 text:[[Special:MyLanguage/Calymmian|Calymm]] color:calymmian from: -1800 till: -1600 text:[[Special:MyLanguage/Statherian|Stather]] color:statherian from: -2050 till: -1800 text:[[Special:MyLanguage/Orosirian|Orosirian]] color:orosirian from: -2300 till: -2050 text:[[Special:MyLanguage/Rhyacian|Rhyacian]] color:rhyacian from: -2500 till: -2300 text:[[Special:MyLanguage/Siderian|Siderian]] color:siderian from: start till: -2500 color:white </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:phanerozoic value:rgb(0.435,0.85,0.866) id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:neogene value:rgb(1,0.901,0.098) id:paleogene value:rgb(0.992,0.603,0.321) id:mesozoic value:rgb(0.403,0.772,0.792) id:cretaceous value:rgb(0.498,0.776,0.306) id:jurassic value:rgb(0.203,0.698,0.788) id:triassic value:rgb(0.505,0.168,0.572) id:paleozoic value:rgb(0.6,0.752,0.552) id:permian value:rgb(0.941,0.25,0.156) id:carboniferous value:rgb(0.403,0.647,0.6) id:devonian value:rgb(0.796,0.549,0.215) id:silurian value:rgb(0.702,0.882,0.713) id:ordovician value:rgb(0,0.572,0.439) id:cambrian value:rgb(0.496,0.627,0.337) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-542 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:100 start:-500 ScaleMinor = unit:year increment:10 start:-540 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:eon at: 0 align:right $markred at: -542 align:left $markred shift:(2,3) from: -542 till: 0 text:[[Special:MyLanguage/Phanerozoic|Phanerozoic]] color:phanerozoic bar:era at: 0 align:right $markgreen at: -65.5 align:left $markgreen shift:(2,3) from: -65.5 till: 0 text:[[Special:MyLanguage/Cenozoic|Cenozoic]] color:cenozoic from: -251 till: -65.5 text:[[Special:MyLanguage/Mesozoic|Mesozoic]] color:mesozoic from: -542 till: -251 text:[[Special:MyLanguage/Paleozoic|Paleozoic]] color:paleozoic bar:period fontsize:8 from: -2.588 till: 0 text:[[Special:MyLanguage/Quaternary|Q.]] color:quaternary from: -23.03 till: -2.588 text:[[Special:MyLanguage/Neogene|Neo]] color:neogene from: -65.5 till: -23.03 text:[[Special:MyLanguage/Paleogene|Paleogene]] color:paleogene from: -145.5 till: -65.5 text:[[Special:MyLanguage/Cretaceous|Cretaceous]] color:cretaceous from: -199.6 till: -145.5 text:[[Special:MyLanguage/Jurassic|Jurassic]] color:jurassic from: -251.4 till: -199.6 text:[[Special:MyLanguage/Triassic|Triassic]] color:triassic from: -299 till: -251.4 text:[[Special:MyLanguage/Permian|Permian]] color:permian from: -359.2 till: -299 text:[[Special:MyLanguage/Carboniferous|Carboniferous]] color:carboniferous from: -416 till: -359.2 text:[[Special:MyLanguage/Devonian|Devonian]] color:devonian from: -443.7 till: -416 text:[[Special:MyLanguage/Silurian|Silurian]] color:silurian from: -488.3 till: -443.7 text:[[Special:MyLanguage/Ordovician|Ordovician]] color:ordovician from: -542 till: -488.3 text:[[Cambrian] color:cambrian </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:holocene value:rgb(0.996,0.949,0.878) id:pleistocene value:rgb(1,0.949,0.678) id:neogene value:rgb(1,0.901,0.098) id:pliocene value:rgb(1,1,0.6) id:miocene value:rgb(1,1,0) id:paleogene value:rgb(0.992,0.603,0.321) id:oligocene value:rgb(0.992,0.752,0.478) id:eocene value:rgb(0.992,0.705,0.423) id:paleocene value:rgb(0.992,0.654,0.372) id:cambrian value:rgb(0.496,0.627,0.337) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-65.5 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:10 start:-60 ScaleMinor = unit:year increment:1 start:-65 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:era at: 0 align:right $markgreen at: start align:left $markgreen shift:(2,3) from:start till: 0 text:[[Cenozoic|Cambrian]] color:cambrian </timeline> <timeline> ImageSize = width:800 height:100 PlotArea = left:65 right:15 bottom:20 top:5 AlignBars = justify Colors = id:cenozoic value:rgb(0.949,0.976,0.113) id:quaternary value:rgb(0.976,0.976,0.498) id:holocene value:rgb(0.996,0.949,0.878) id:pleistocene value:rgb(1,0.949,0.678) id:neogene value:rgb(1,0.901,0.098) id:pliocene value:rgb(1,1,0.6) id:miocene value:rgb(1,1,0) id:paleogene value:rgb(0.992,0.603,0.321) id:oligocene value:rgb(0.992,0.752,0.478) id:eocene value:rgb(0.992,0.705,0.423) id:paleocene value:rgb(0.992,0.654,0.372) id:black value:black id:white value:white id:darkgreen value:rgb(0,0.35,0) Period = from:-65.5 till:0 TimeAxis = orientation:horizontal ScaleMajor = unit:year increment:10 start:-60 ScaleMinor = unit:year increment:1 start:-65 Define $markred = text:"*" textcolor:red shift:(0,3) fontsize:10 Define $markgreen = text:"*" textcolor:darkgreen shift:(0,3) fontsize:10 PlotData= align:center textcolor:black fontsize:8 mark:(line,black) width:25 shift:(0,-5) bar:era at: 0 align:right $markgreen at: start align:left $markgreen shift:(2,3) from:start till: 0 text:[[Special:MyLanguage/Cenozoic|Cenozoic]] color:cenozoic bar:period from: -2.588 till: 0 text:[[Special:MyLanguage/Quaternary|Q.]] color:quaternary from: -23.03 till: -2.588 text:[[Special:MyLanguage/Neogene|Neogene]] color:neogene from: start till: -23.03 text:[[Special:MyLanguage/Paleogene|Paleogene]] color:paleogene bar:epoch from: -0.1 till: 0 text:[[Special:MyLanguage/Holocene|H]] color:holocene from: -2.588 till: -0.1 text:[[Special:MyLanguage/Pleistocene|P]] color:pleistocene from: -5.332 till: -2.588 text:[[Special:MyLanguage/Pliocene|Pliocene]] color:pliocene fontsize:7 from: -23.03 till: -5.332 text:[[Special:MyLanguage/Miocene|Miocene]] color:miocene from: -33.9 till: -23.03 text:[[Special:MyLanguage/Oligocene|Oligocene]] color:oligocene from: -55.8 till: -33.9 text:[[Special:MyLanguage/Eocene|Eocene]] color:eocene from: start till: -55.8 text:[[Special:MyLanguage/Paleocene|Paleocene]] color:paleocene </timeline> </td></tr> <tr><td colspan=3 align=left>{{Wikimedia Growth}}</td></tr> </table> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Code example== </div> :''Siehe auch:'' {{ll|Extension:EasyTimeline/syntax}} <timeline> # All measures are in pixels ImageSize = width:160 height:550 PlotArea = left:50 right:0 bottom:10 top:10 AlignBars = justify DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef~Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> <div lang="en" dir="ltr" class="mw-content-ltr"> Just to show you that the script syntax is reasonably intuitive, here is the script for the image above: Soviet Leaders. </div> <syntaxhighlight lang="moin"> <timeline> # All measures are in pixels ImageSize = width:160 height:550 PlotArea = left:50 right:0 bottom:10 top:10 AlignBars = justify DateFormat = yyyy Period = from:1917 till:1991 TimeAxis = orientation:vertical ScaleMajor = unit:year increment:5 start:1920 # there is no automatic collision detection, # so shift texts up or down manually to avoid overlap Define $dx = 25 # shift text to right side of bar PlotData= bar:Leaders color:red width:25 mark:(line,white) align:left fontsize:S from:start till:1924 shift:($dx,15) text:Vladimir~Ilyich~[[Special:MyLanguage/Lenin|Lenin]] from:1924 till:1953 shift:($dx,5) text:[[Special:MyLanguage/Stalin|Josef~Stalin]] from:1953 till:1964 shift:($dx,5) text:Nikita~[[Special:MyLanguage/Khrushchev|Khrushchev]] from:1964 till:1982 shift:($dx,5) text:Leonid~[[Special:MyLanguage/Brezhnev|Brezhnev]] from:1982 till:1984 shift:($dx,-12) text:Yuri~[[Special:MyLanguage/Andropov|Andropov]] from:1984 till:1985 shift:($dx,4) text:Konstantin~[[Special:MyLanguage/Chernenko|Chernenko]] fontsize:XS from:1985 till:end shift:($dx,10) text:Mikhail~[[Special:MyLanguage/Gorbachev|Gorbachev]] </timeline> </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Double and single brackets can be used like on wikipedia, language prefix is possible, e.g. <syntaxhighlight lang="moin" inline>[[de:foo|more about foo]]</syntaxhighlight>. Single brackets for external links are also supported. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Great timelines elsewhere== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here are two great sites that may serve as inspiration, it would be very easy to recreate most of those timelines verbatim and with roughly similar layout with EasyTimeline (not yet with images but that may change), but I'm afraid that would be 'not done'. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[http://www.hyperhistory.com/online_n2/History_n2/a.html Hyperhistory] e.g. click on button 'people' left, then on 'special lifelines', right. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *I hope we will have a set like [http://chaos1.hypermart.net/fullsize.htm] in a years time (click on ''full size image'' for any map), possibly even with images. The main effort will be to gather all info without snatching everything from here (most of these maps are based exclusively on data from Britannica). </div> ==Unicode== <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline does not yet support unicode. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Aug 2004: Minimal UTF-8 support has been added, meaning that EasyTimeline now recognizes UTF-8 encoded characters. However support for directionality and complex scripts is very lacking. The default font may not have glyphs for all characters. An alternate font can be specified via <code>$wgTimelineFontFile</code> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SVG to PNG=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To show texts correctly for RTL languages (like Arabic, Persian, Hebrew,...) you can use {{tmpl|0={{tag|timeline|params={{attr|method|"svg2png"}}|content=$1}}|timeline code here}} instead of {{tmpl|0={{tag|timeline|content=$1}}|timeline code here}}. it shows timeline as png but the links will be disabled. </div> == Tipps == <div lang="en" dir="ltr" class="mw-content-ltr"> For first time users EasyTimeline may not seem that easy at all. As with all script languages it takes some getting used to. Also the syntax description may be a bit bewildering due to its sheer size. Fortunately many elements of the script language are optional. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The 'Easy' in EasyTimeline conveys the message that once a timeline exists it is not so hard to understand, enhance or correct. Also translating for use on another Wikipedia it is pretty straightforward. </div> Tipps: <div lang="en" dir="ltr" class="mw-content-ltr"> * See some [[#charts-examples|chart examples]] to find something you could pick and edit for your own stuff </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *Put each timeline on a separate Template page: this makes it easier to edit, faster to preview, possible to include it in several pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Using the current date== </div> <span lang="en" dir="ltr" class="mw-content-ltr">To use the current date make sure the table opens with <code><nowiki>{{#tag:timeline|</nowiki></code> and closes with <code><nowiki>}}</nowiki></code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then the current date can be inserted using magic words.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example <code><nowiki>{{#time: d/m/Y }}</nowiki></code> or <code><nowiki>{{CURRENTDAY2}}/{{CURRENTMONTH2}}/{{CURRENTYEAR}}</nowiki></code> will both yield the date in format dd/mm/yyyy.</span> == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> *[[Special:MyLanguage/Extension:EasyTimeline/syntax|EasyTimeline Coding]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *Presentation about EasyTimeline at Wikimania 2005 ([[m:Transwiki:Wikimania05/Workshop-EZ1|abstract]], [http://upload.wikimedia.org/wikipedia/commons/9/90/Wikimania_2005_Presentation_EasyTimeline.pdf slides], [http://upload.wikimedia.org/wikipedia/commons/7/78/Wikimania_2005_Presentation_Easytimeline_Speaker_Notes.pdf speaker notes]) </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *[[m:WikiTimeScale|m:WikiTimeScale]] as a proposal for realizing timescales for wikipedia articles externally. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[w:Template:Simple Horizontal timeline|w:Template:Simple Horizontal timeline]] An easier timeline to use on Wikipedia. </div> *{{ll|Extension:Graph}} ==Installation== Siehe [[Special:MyLanguage/Extension:EasyTimeline/installation|/installation]] == Externe Links == * [http://www.simile-widgets.org <span lang="en" dir="ltr" class="mw-content-ltr">SIMILE Widgets</span>] - DHTML-based AJAXy widget for visualizing time-based events {{OnWikimedia}} {{Used by|fandom=1}} mc96rksywvqx00qi6keowdsomfjkdyn Template:InstallationNav/el 10 1328141 5387194 5384780 2022-07-28T21:17:28Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=<span lang="en" dir="ltr" class="mw-content-ltr">Customize</span>}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] t70q07v13r8fozu7qderazbxel125s6 Manual:Pywikibot/category.py/ru 100 1331207 5387855 5299634 2022-07-29T10:20:02Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} == Синтаксис == Синтаксис вызова скрипта таков: python pwb.py category action [-option] и действие может быть одним из следующих: {| class="wikitable |- | <code>add</code> || массовое добавление категории в страницы из списка |- | <code>remove</code> || удалить тэг категории из всех страниц в категории |- | <code>move</code> || переместить все страницы в категории в другую категорию |- | <code>tidy</code> || расчистить категорию, переместив статьи в подкатегории |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || показать дерево подкатегорий данной категории |- | <code>listify</code> || сформировать список статей в категории |} и опция может быть одной из следующих: === Опции для действия «<code>add</code>» === {| class="wikitable" |- | <code>-person</code> || сортировать персоналии по фамилии |- | <code>-create</code> || Если страница не существует, не пропускать её, а создавать |- | <code>-redirect</code> || Следовать по редиректам |} Для этого действия, доступны следующие опции [[#page_generators|генератора страниц]]»: === Опции для действия «<code>listify</code>» === * -overwrite - Перезаписывать текущую страницу содержимым списка, даже если она непуста. * -showimages - Отображать изображения, а не давать ссылки на них. * -talkpages - Добавляет в список ссылки на страницы обсуждения в дополнение к ссылкам на сами страницы. === Опции для действия «<code>remove</code>» === * -nodelsum - Указывает не использовать произвольное описание в качестве причины удаления. Вместо этого используется причина удаления по умолчанию (в английском языке — «Category was disbanded»). === Опции для действия «<code>move</code>» === {| class="wikitable" | -hist || Создавать оформленную таблицу на странице обсуждения категорию с историей категории-источника. |- | -nodelete || Не удалять старую категорию после переноса |- | -nowb || Не обновлять репозиторий Wikibase |- | -allowsplit || Если опция не установлена, переименовываются только основная страница и её обсуждение. |- | -mvtogether || Перемещать страницы/подкатегории в категории, только если не существует целевая страница (и страница обсуждения, если не установлено -allowsplit). |- | -keepsortkey | Использовать ключ сортировки старой категории и для новой категории. Если не указано, ключ сортировки удаляется. Другой способ сохранить ключ сортировки — использовать опцию <code>-inplace</code> |} === Опции для действия «<code>tidy</code>» === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | Фильтровать страницы в указанном пространстве имён. Разделяйте множественные номера пространств имён запятыми. Примеры: -ns:0,2,4 -ns:Help,MediaWiki |} === Опции для нескольких действий === {| class="wikitable" | -rebuild || сбросить базу данных |- | -from: | Категория, из которой перемещаются страницы (для опции move) Также категория, из которой удаляются страницы (для опции remove) Также категория, на основе которой создаётся список (для опции listify) См. примечание под таблицей. |- | -to: | Категория, в которую перемещаются страницы (для опции move) Также имя создаваемого списка (для опции listify) См. примечание под таблицей. |- | -batch || Не запрашивать подтверждения удаления опустошённой категории (производить удаление автоматически). |- | -summary: || Выбрать произвольное описание правки. |- | -inplace || Изменять категории на месте без пересортировки. |- | -recurse || Проходить рекурсивно по всем подкатегориям категорий. |- | -pagesonly || При удалении страниц из категории сохранять ссылки на подстраницы и не удалять их. |- | -match || Работать только по страницам, чьи заголовки соответствуют указанному регулярному выражению (для действий move и remove). |- | -depth: || Максимальная глубина, за пределами которой подкатегории не обрабатываются. |} {{note|1= Для опций ''-from'' и ''-to'': Если в именах категорий содержатся пробелы, вам следует использовать специальный синтаксис в вашей командной строке, чтобы слова не воспринимались как отдельные параметры. Например, BASH использует одинарные кавычки, <code>-from:'Polar bears'</code>. Для категорий с двоеточием в названии необходимо явным образом указать префикс пространства имён <code>category:</code> или его локализованный эквивалент. Для действий ''tidy'' и ''tree'' бот сохраняет структуру категорий локально в <code>category.dump</code>. Это экономит время и нагрузку на сервер, но при повторном использовании данные уже могут устареть; в этом случае используйте параметр <code>-rebuild</code>. Например, чтобы создать новую категорию из списка персоналий, введите: python pwb.py category add -person и следуйте инструкциям на экране. Или, чтобы сделать это из командной строки, используйте следующий синтаксис: python pwb.py category move -from:US -to:"United States" Это перенесёт все страницы из категории US в категорию United States. }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} == См. также == * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] ij79seraedbx7bd0m4mghyjul493ebj Manual:Pywikibot/category.py/ja 100 1331254 5387852 5299630 2022-07-29T10:19:59Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} == 構文 == 構文は以下の通りです: python pwb.py category action [-option] <div lang="en" dir="ltr" class="mw-content-ltr"> where action can be one of the following. </div> {| class="wikitable |- | <code>add</code> || <span lang="en" dir="ltr" class="mw-content-ltr">mass-add a category to a list of pages</span> |- | <code>remove</code> || <span lang="en" dir="ltr" class="mw-content-ltr">remove category tag from all pages in a category</span> |- | <code>move</code> || <span lang="en" dir="ltr" class="mw-content-ltr">move all pages in a category to another category</span> |- | <code>tidy</code> || <span lang="en" dir="ltr" class="mw-content-ltr">tidy up a category by moving its articles into subcategories</span> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <span lang="en" dir="ltr" class="mw-content-ltr">show a tree of subcategories of a given category</span> |- | <code>listify</code> || <span lang="en" dir="ltr" class="mw-content-ltr">make a list of all of the articles that are in a category</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> and option can be one of the following. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>add</code> action</span> === {| class="wikitable" |- | <code>-person</code> || <span lang="en" dir="ltr" class="mw-content-ltr">sort persons by their last name</span> |- | <code>-create</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If a page doesn't exist, do not skip it, create it instead</span> |- | <code>-redirect</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Follow redirects</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> For this action, [[#page_generators|page generator options]] are supported. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>listify</code> action</span> === * -overwrite - <span lang="en" dir="ltr" class="mw-content-ltr">This overwrites the current page with the list even if something is already there.</span> * -showimages - <span lang="en" dir="ltr" class="mw-content-ltr">This displays images rather than linking them in the list.</span> * -talkpages - <span lang="en" dir="ltr" class="mw-content-ltr">This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>remove</code> action</span> === * -nodelsum - <span lang="en" dir="ltr" class="mw-content-ltr">This specifies not to use the custom edit summary as the deletion reason.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Options for <code>move</code> action === </div> {| class="wikitable" | -hist || <span lang="en" dir="ltr" class="mw-content-ltr">Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</span> |- | -nodelete || <span lang="en" dir="ltr" class="mw-content-ltr">Don't delete the old category after move</span> |- | -nowb || <span lang="en" dir="ltr" class="mw-content-ltr">Don't update the wikibase repository</span> |- | -allowsplit || <span lang="en" dir="ltr" class="mw-content-ltr">If that option is not set, it only moves the talk and main page together.</span> |- | -mvtogether || <span lang="en" dir="ltr" class="mw-content-ltr">Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist.</span> |- | -keepsortkey | <span lang="en" dir="ltr" class="mw-content-ltr">Use sortKey of the old category also for the new category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not specified, sortKey is removed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alternative method to keep sortKey is to use -inplace option.</span> |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>tidy</code> action</span> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Filter the articles in the specified namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Separate multiple namespace numbers or names with commas.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Examples:</span> -ns:0,2,4 -ns:Help,MediaWiki |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for several actions</span> === {| class="wikitable" | -rebuild || <span lang="en" dir="ltr" class="mw-content-ltr">reset the database</span> |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} == 関連項目 == * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] iqc2qtd03t4yp7czbsgmjud6ifm1t2t Growth/Team/Chores 0 1331559 5387514 5385664 2022-07-29T00:22:27Z Etonkovidova 1850810 wikitext text/x-wiki This page documents the current state of chores as defined in [[Growth/Team/Chore list|the chore list]] (see also [[Growth/Team/Chore list#Team norms|team norms]]). === Rotations === We rotate this at the beginning of each month, last rotated '''Jul 6'''. ==== Engineering chores ==== * Monday - * Tuesday - Gergő * Wednesday - Sergio * Thursday - Elena * Friday - Kosta === Engineering === {| class="wikitable" |+ !Chore !Status !Notes !Last review |- | colspan="4" |'''Logs''' |- |[https://logstash.wikimedia.org/app/dashboards#/view/AWl4jlZ78aQffZ3Ho7BV Logstash] |⚠️ | {{PhabT|211798}} {{PhabT|303175}} {{Phabricator|T227294}} |[[User:Etonkovidova|Etonkovidova]] 00:22, 29 July 2022 (UTC) |- |[https://logstash.wikimedia.org/app/dashboards#/view/271f0b50-d5cd-11eb-81e9-e1226573bad4?_g=(filters%3A!()%2CrefreshInterval%3A(pause%3A!t%2Cvalue%3A300000)%2Ctime%3A(from%3Anow-1d%2Cto%3Anow)) Logstash client errors] |⚠️ | {{PhabT|T309360}} {{PhabT|T292257}} |[[User:Etonkovidova|Etonkovidova]] 00:22, 29 July 2022 (UTC) |- |[https://logstash.wikimedia.org/app/dashboards#/view/41cae700-bfbe-11eb-85b7-9d1831ce7631 EventLogging validation errors] |✅ | |[[User:Etonkovidova|Etonkovidova]] 00:22, 29 July 2022 (UTC) |- |[https://logstash.wikimedia.org/app/dashboards#/view/6027a870-7ffc-11eb-8ab2-63c7f3b019fc?_g=(filters%3A!()%2CrefreshInterval%3A(pause%3A!t%2Cvalue%3A0)%2Ctime%3A(from%3Anow-24h%2Cto%3Anow)) Link recommendation] |⚠️ | {{Phabricator|T296334}} |[[User:Etonkovidova|Etonkovidova]] 00:22, 29 July 2022 (UTC) |- | '''Triage / Tidy''' |- |[[phab:project/board/1114/|Rapid triage inbox tasks #growth-team]] ([[Growth/Team/Chore list#Triage / Tidy|help]]) |✅ | |[[User:Etonkovidova|Etonkovidova]] 00:22, 29 July 2022 (UTC) |- |[[phab:project/board/1114/|Process three tasks from "Needs discussion/analysis" column]] ([[Growth/Team/Chore list#Processing the Needs Discussion / Analysis column|help]]) |✅ |{{PhabT|311433}} |[[User:Etonkovidova|Etonkovidova]] 00:22, 29 July 2022 (UTC) |- |'''Performance''' |- |[https://grafana.wikimedia.org/d/CI6JRnLMz/linkrecommendation?orgId=1&from=now-2d&to=now Link recommendation service] |⚠️ |{{Phabricator|T303177}} |[[User:Etonkovidova|Etonkovidova]] 00:22, 29 July 2022 (UTC) |- | [https://grafana.wikimedia.org/d/vGq7hbnMz/special-homepage-and-suggested-edits?orgId=1&from=now-2d&to=now Special:Homepage / Suggested Edits] |✅ | |[[User:Etonkovidova|Etonkovidova]] 00:22, 29 July 2022 (UTC) |- |'''Product key performance indicators (KPIs)''' | | | |- |See product KPIs table below. |🚧 |Don't edit the Product KPIs table below; these should be done by other members of the team, but engineers should review and leave comments in the notes section in the Product KPIs table if something seems off. | |} === Product KPIs === '''Rotations''' (draft) * Monday - Benoît * Tuesday - Rita * Wednesday - Marshall / Product manager * Thursday - Dennis * Friday - Morten {| class="wikitable" |+(not yet implemented, see T286366) !Chore !Status !Notes !Last review |- | colspan="4" |'''Edit counts''' |- |[https://grafana.wikimedia.org/d/bSDW0wJ7z/growth-team-product-kpis?orgId=1&from=now-7d&to=now Newcomer tasks, clicks on Special:Homepage] |✅ | |[[User:KHarlan (WMF)|KHarlan (WMF)]] ([[User talk:KHarlan (WMF)|talk]]) 12:42, 21 January 2022 (UTC) |- |[https://grafana.wikimedia.org/d/bSDW0wJ7z/growth-team-product-kpis?orgId=1&from=now-7d&to=now Newcomer tasks, saves] |✅ | |[[User:KHarlan (WMF)|KHarlan (WMF)]] ([[User talk:KHarlan (WMF)|talk]]) 12:42, 21 January 2022 (UTC) |- |[https://grafana.wikimedia.org/d/bSDW0wJ7z/growth-team-product-kpis?orgId=1&from=now-7d&to=now Newcomer tasks, reverted edits] |✅ | |[[User:KHarlan (WMF)|KHarlan (WMF)]] ([[User talk:KHarlan (WMF)|talk]]) 12:42, 21 January 2022 (UTC) |- | '''Account creation''' |- |Accounts created that are opted into Growth features |🚧 | | |- |Accounts opted into variants |🚧 | | |- |'''Mentorship / question asking''' |- |Questions asked to mentor from help panel |🚧 | | |- |Questions asked to mentor from homepage |🚧 | | |} == Helpers == Status fields: {| class="wikitable" |✅ |is fine |- |⚠️ |needs attention |- |🚨 |is on fire |- |🎉 |For your attention but positive |} Last updated (Use four tildes to autosign) Link someone's username in the edit-summary to ping them! This will send them an Echo notification! Please list your preferred ping username below: Participants: * [[User:KHarlan (WMF)]] * [[User:Tgr_(WMF)]] * [[User:Etonkovidova]] * [[User:SGimeno (WMF)]] 1cmw10yx7drldytnzv4ejquvg0n014i Wikimedia Product/fa 0 1338921 5387575 5358192 2022-07-29T03:25:44Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span></span>]] * [[Readers|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Readers</span></span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|ویرایش آی‌او‌اس]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * صفحه: [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * صفحه: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * صفحه: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * صفحه: [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * صفحه: [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== زبان ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * صفحه: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * صفحه: [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|اندروید]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|آی‌او‌اس]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> صفحه: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> صفحه: [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> صفحه: [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> صفحه: [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === ویکی‌داده === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * صفحه: [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Goals</span> == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2017–2018</span> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2016–2017</span> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] d159um0hxp0vslrd2mm7y12nhkzsitn Manual:Installing third-party tools/de 100 1341911 5387819 5377080 2022-07-29T09:28:37Z Revibot 1724693 Bot: Fixing double redirect to [[Manual:Installing MediaWiki/de]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/de]] d5kmxqmeba5eoob88wqnq12eaf1a6rj Manual:Pywikibot/category.py/fr 100 1345539 5387848 5299629 2022-07-29T10:19:58Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} == Syntaxe == La syntaxe est : python pwb.py category action [-option] où ''action'' est une des valeurs suivantes : {| class="wikitable |- | <code>add</code> || ajoute en rafale une catégorie à une liste de pages |- | <code>remove</code> || supprime la balise de catégorie sur toutes les pages d'une catégorie donnée |- | <code>move</code> || affecte toutes les pages d'une catégorie donnée dans une autre catégorie |- | <code>tidy</code> || classe une catégorie en plaçant ses articles dans des sous-catégories |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || affiche l'arbre des sous-catégories d'une catégorie donnée |- | <code>listify</code> || fait une liste de tous les articles présents dans une catégorie |} et ''option'' une des valeurs suivantes. === Options pour l'action <code>add</code> === {| class="wikitable" |- | <code>-person</code> || trie les personnes en fonction de leur nom de famille |- | <code>-create</code> || si une page n'existe pas, il ne faut pas la sauter mais la créer. |- | <code>-redirect</code> || suivre les redirections |} Pour cette action, les [[#page_generators|options de génération de page]] sont reconnues. === Options pour l'action <code>listify</code> === * -overwrite - réécrase la page courante avec la liste, même s'il y a déjà quelque chose dessus. * -showimages - affiche les images plutôt que de les lier dans la liste. * -talkpages - affiche les liens vers les pages de discussion des pages à lister en plus des pages elles-mêmes. === Options pour l'action <code>remove</code> === * -nodelsum - indique de ne pas utiliser le résumé de modification utilisateur comme motif de la suppression. A la place, on utilise le motif de suppression par défaut de la langue, qui par exemple pour l'anglais vaut « Category was disbanded ». === Options pour l'action <code>move</code> === {| class="wikitable" | -hist || crée un joli tableau wiki sur la page de discussion de la catégorie cible contenant l'historique détaillée de la page de la catégorie source. |- | -nodelete || ne pas supprimer l'ancienne catégorie après le renommage |- | -nowb || ne pas mettre à jour le dépôt wikibase |- | -allowsplit || si cette option n'est pas initialisée, ne fait que renommer la page de discussion en même temps que la page principale. |- | -mvtogether || ne fait que renommer les pages / sous-categories d'une catégorie si la page cible n'existe pas (ni la page de discussion, si <code>-allowsplit</code> n'est pas utilisé). |- | -keepsortkey | Utiliser sortKey de l'ancienne catégorie également pour la nouvelle catégorie. Si non spécifié, sortKey est supprimé. Une méthode alternative pour garder sortKey est d'utiliser l'option <code>-inplace</code>. |} === Options pour l'action <code>tidy</code> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | Filtre les articles dans les espaces de noms spécifiés. Séparez les numéros et les noms des espaces de noms avec des virgules. Exemples : -ns:0,2,4 -ns:Help,MediaWiki |} === Options communes à plusieurs actions === {| class="wikitable" | -rebuild || réinitialise la base de données |- | -from: | catégorie d'origine (pour l'option <code>move</code>) C'est aussi la catégorie utilisée pour la suppression avec l'option <code>remove</code> C'est aussi la catégorie pour faire une liste avec l'option <code>listify</code> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | catégorie destination (pour l'option <code>move</code>) C'est aussi le nom de la liste à créer avec l'option <code>listify</code> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || ne pas demander à supprimer les catégories vides (le fait automatiquement). |- | -summary: || sélectionner un résumé de modification utilisateur pour le robot. |- | -inplace || utilisez cette option pour modifier les catégories en place plutôt que de les réorganiser. |- | -recurse || toutes les sous-catégories par récursivité sur les catégories. |- | -pagesonly || pendant le retrait des pages d'une catégorie garde les liens des sous-pages sans les supprimer |- | -match || ne fonctionne que sur les pages dont le titre vérifie l'expression régulière fournie (pour les actions <code>move</code> et <code>remove</code> ). |- | -depth: || profondeur maximale pour l'exploration des sous-catégories. |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> si les noms de catégorie comportent des caractères espace, vous devrez utiliser une syntaxe spéciale dans votre shell pour ne pas que ces noms soient considérés comme des paramètres séparés. <span class="mw-translate-fuzzy">Par exemple en BASH, utiliser les apostrophes simples, par exemple :</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span class="mw-translate-fuzzy">Pour les actions <code>tidy</code> et <code>tree</code>, le robot va enregistrer la structure de la catégorie localement dans <code>category.dump</code>.</span> Ceci économise le temps et la charge du serveur, mais s'il utilise ces données ultérieurement, elles peuvent être obsolètes ; utilisez le paramètre <code>-rebuild</code> dans ce cas. Par exemple, pour créer une nouvelle catégorie à partir d'une liste de personnes, entrez : python pwb.py category add -person et suivez les instructions à l'écran. Ou pour tout exécuter à partir de la ligne de commande, utilisez la syntaxe suivante : python pwb.py category move -from:US -to:"United States" Ceci va placer toutes les pages de la catégorie US dans la catégorie United States. }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} == Voir aussi == * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] tdseeunqucagz0y55j2befcx7wylwop Extension:LoginNotify/de 102 1348184 5386861 5373356 2022-07-28T19:29:09Z ThisCarthing 17456337 Created page with "Ablauf des Cookies." wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = user activity |username = Bawolff |author = Brian Wolff |description = Benutzer über verdächtige Anmeldungen benachrichtigen |image = LoginNotify_screenshot_for_meta_documentation.png |imagesize = 280px |version = |update = |mediawiki = |php = |composer = |table1 = |table2 = |license = MIT |download = {{WikimediaDownload}} |changelog = |example = |namespace = |parameters = |tags = |rights = |compatibility = |bugzilla = LoginNotify }} Die Erweiterung '''LoginNotify''' benachrichtigt Sie, wenn sich jemand bei Ihrem Konto anmeldet. Sie kann so konfiguriert werden, dass sie nach einer bestimmten Anzahl fehlgeschlagener Anmeldeversuche Warnungen ausgibt (Die Anzahl ist konfigurierbar und kann sich zwischen unbekannten IPs/Geräten und bekannten IPs/Geräten unterscheiden). Außerdem können Sie {{ll|Extension:Echo|nsp=0}}-Hinweise (die auch per E-Mail gesendet werden können) für erfolgreiche Anmeldungen von IPs erhalten, die Sie normalerweise nicht verwenden. Es kann optional in die {{ll|Extension:CheckUser|CheckUser}}-Erweiterung integriert werden, um festzustellen, ob die Anmeldung von einer IP-Adresse stammt, die Sie normalerweise nicht verwenden. Es kann auch ein Cookie setzen, um festzustellen, ob der Login von einem Gerät stammt, das Sie normalerweise benutzen. == Installation == <span lang="en" dir="ltr" class="mw-content-ltr">This extension requires the Echo extension to be installed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This extension can optionally integrate with the CheckUser extension if it is installed, but does not require it.</span> {{ExtensionInstall |registration=required |custom-steps=[[#Configuration|Konfiguriere nach Bedarf.]] |}} == Verwendung == <span lang="en" dir="ltr" class="mw-content-ltr">Once LoginNotify is installed, whenever a user logs into the wiki, their IP subnet is cached on the server and a cookie named <code>loginnotify_prevlogins</code> is stored in their browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These tokens, optionally along with CheckUser tables, are used to see if subsequent logins are coming from a known IP/device.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If {{ll|Extension:CentralAuth|CentralAuth}} and {{ll|Extension:CheckUser|CheckUser}} are installed, it will check the IP not only for the current wiki, but also the ten wikis where the user is most active. </div> {{anchor|Configuration}} == Konfiguration == <div lang="en" dir="ltr" class="mw-content-ltr"> Parameters that can be set (in "LocalSettings.php"): </div> {| class="wikitable" ! Name ! Beschreibung ! <span lang="en" dir="ltr" class="mw-content-ltr">Default</span> |- | <code>$wgLoginNotifyAttemptsKnownIP</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The number of failed login attempts to permit from a known IP before a notification is triggered.</span> | 10 |- | <code>$wgLoginNotifyAttemptsNewIP</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The number of failed login attempts to permit from a new IP before a notification is triggered.</span> | 3 |- | <code>$wgLoginNotifyExpiryKnownIP</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The time-to-live of the count of failed login attempts from a known IP (from the time of the first failed attempt).</span> | 604800 ({{int|Duration-days|7}}) |- | <code>$wgLoginNotifyExpiryNewIP</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The time-to-live of the count of failed login attempts from a new IP (from the time of the first failed attempt).</span> | 1209600 ({{int|Duration-days|14}}) |- | <code>$wgLoginNotifyCheckKnownIPs</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to trigger a notification after failed logins from known IPs.</span> | <code>true</code> |- | <code>$wgLoginNotifyEnableOnSuccess</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to trigger a notification after successful logins from unknown IPs.</span> | <code>true</code> |- | <code>$wgLoginNotifyEnableForPriv</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Set different default notification preferences for different user groups.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For user groups that have any of the user rights listed in this array, the preferences specified in Hooks:getOverridenOptions() are on by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">("Failed login attempts" web notifications and "Login from new computer" web notifications.)</span> | <code>[ "editinterface", "userrights" ]</code> |- | <code>$wgLoginNotifySecretKey</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Use this key instead of {{wg|SecretKey}} to generate the HMACs for the cookie.</span> | <code>null</code> |- | <code>$wgLoginNotifyCookieExpire</code> | Ablauf des Cookies. | 15552000 ({{int|Duration-days|180}}) |- | <code>$wgLoginNotifyCookieDomain</code> | <span lang="en" dir="ltr" class="mw-content-ltr">To allow sharing login cookies between sites on different subdomains, set this to the parent domain name.</span> | <code>null</code> |- | <code>$wgLoginNotifyMaxCookieRecords</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Maximum number of users (records) to track as having successfully logged in on a particular device.</span> | 6 |- | <code>$wgLoginNotifyCacheLoginIPExpiry</code> | <span lang="en" dir="ltr" class="mw-content-ltr">How long to cache IPs in memcache. Set to <code>false</code> to disable; set to <code>0</code> to cache forever.</span> | 5184000 ({{int|Duration-days|60}}) |} {{OnWikimedia}} {{Used by|bluespice=1|miraheze=1}} cwqwoxo3vs2m1c50e40zyhnagpvskgx Manual:Combating spam/es 100 1350833 5387473 5255696 2022-07-28T22:40:15Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} Como todos los sitios web dinámicos actuales, los wikis son un objetivo común para los spammers que desean promocionar productos o sitios web. MediaWiki ofrece una serie de características diseñadas para [[Special:MyLanguage/Manual:Combating vandalism|combat vandalism in general]]. En esta página tratamos específicamente con [[m: Wiki spam | wiki spam]], que a menudo está automatizado. <div lang="en" dir="ltr" class="mw-content-ltr"> == Overview == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Common tools used to combat wiki spam typically fall into these categories: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Requiring log in and/or a CAPTCHA on certain operations, such as edits, adding external links, or new user creation </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits from known blacklisted IP addresses or IPs running open proxies </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits which add specific unwanted keywords or external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking specific username and page title patterns commonly used by spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits by new or anonymous users to specific often-targeted pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Whitelisting known-good editors (such as admins, regular contributors) while placing restrictions on new or anonymous users </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Cleanup scripts or bulk deletion ({{ll|Extension:Nuke}}) of existing posts from recently-banned spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Note that many of these features are not activated by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</span> <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It helps to raise the bar a little.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Quickest solutions to try first== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Fighting spam should not be too hard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to quickly and drastically reduce spam, try these few steps first.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install the [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] extension to block known spammer IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam setup basics== </div> {{anchor|CAPTCHA}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===CAPTCHA=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * all edits </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * edits adding new, unrecognized external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * user registration </div> <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Individual page protection=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. <div lang="en" dir="ltr" class="mw-content-ltr"> === Abuse filter === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Open proxies === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Apache configuration changes === </div> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Other ideas == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==See also== </div> *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. <div lang="en" dir="ltr" class="mw-content-ltr"> === Extensions === </div> *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users <div lang="en" dir="ltr" class="mw-content-ltr"> === Settings === </div> * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External links === </div> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] jfnfmfxjop8nb79bguwnxnboj23y83h Manual:Installation guide/de-formal 100 1353080 5386642 5381277 2022-07-28T17:14:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/de-formal]] p7s44do802rnrfm8hakosyfzswwa7hz Manual:Pywikibot/category.py/bn 100 1363253 5387845 5299626 2022-07-29T10:19:55Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} == গঠন == গঠন এরকম python pwb.py category action [-option] Action এর বদলে ব্যবহার করতে পারেন- {| class="wikitable |- | <code>add</code> || <span lang="en" dir="ltr" class="mw-content-ltr">mass-add a category to a list of pages</span> |- | <code>remove</code> || <span lang="en" dir="ltr" class="mw-content-ltr">remove category tag from all pages in a category</span> |- | <code>move</code> || <span lang="en" dir="ltr" class="mw-content-ltr">move all pages in a category to another category</span> |- | <code>tidy</code> || <span lang="en" dir="ltr" class="mw-content-ltr">tidy up a category by moving its articles into subcategories</span> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <span lang="en" dir="ltr" class="mw-content-ltr">show a tree of subcategories of a given category</span> |- | <code>listify</code> || <span lang="en" dir="ltr" class="mw-content-ltr">make a list of all of the articles that are in a category</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> and option can be one of the following. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>add</code> action</span> === {| class="wikitable" |- | <code>-person</code> || <span lang="en" dir="ltr" class="mw-content-ltr">sort persons by their last name</span> |- | <code>-create</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If a page doesn't exist, do not skip it, create it instead</span> |- | <code>-redirect</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Follow redirects</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> For this action, [[#page_generators|page generator options]] are supported. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>listify</code> action</span> === * -overwrite - <span lang="en" dir="ltr" class="mw-content-ltr">This overwrites the current page with the list even if something is already there.</span> * -showimages - <span lang="en" dir="ltr" class="mw-content-ltr">This displays images rather than linking them in the list.</span> * -talkpages - <span lang="en" dir="ltr" class="mw-content-ltr">This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>remove</code> action</span> === * -nodelsum - <span lang="en" dir="ltr" class="mw-content-ltr">This specifies not to use the custom edit summary as the deletion reason.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Options for <code>move</code> action === </div> {| class="wikitable" | -hist || <span lang="en" dir="ltr" class="mw-content-ltr">Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</span> |- | -nodelete || <span lang="en" dir="ltr" class="mw-content-ltr">Don't delete the old category after move</span> |- | -nowb || <span lang="en" dir="ltr" class="mw-content-ltr">Don't update the wikibase repository</span> |- | -allowsplit || <span lang="en" dir="ltr" class="mw-content-ltr">If that option is not set, it only moves the talk and main page together.</span> |- | -mvtogether || <span lang="en" dir="ltr" class="mw-content-ltr">Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist.</span> |- | -keepsortkey | <span lang="en" dir="ltr" class="mw-content-ltr">Use sortKey of the old category also for the new category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not specified, sortKey is removed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alternative method to keep sortKey is to use -inplace option.</span> |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>tidy</code> action</span> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Filter the articles in the specified namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Separate multiple namespace numbers or names with commas.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Examples:</span> -ns:0,2,4 -ns:Help,MediaWiki |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for several actions</span> === {| class="wikitable" | -rebuild || <span lang="en" dir="ltr" class="mw-content-ltr">reset the database</span> |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] 5rbvtxxbowf6lmat30n3b9gzoxb98ev Manual:Installation guide/vi 100 1369706 5386675 5381112 2022-07-28T17:14:39Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/vi]] bntg7krwnze3xjivkw0jzxajd04yvhb 5386680 5386675 2022-07-28T17:17:48Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/vi]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Translations:Manual:Installation guide/11/vi 1198 1369725 5387296 4700882 2022-07-28T21:58:36Z Baris6161TURK 17188421 wikitext text/x-wiki Hình thumbnailing yêu cầu chương trình bổ sung. $1 (được yêu cầu bởi VisualEditor) và các dịch e81ylqqmybrz3pc5bzt2ygb9x1mbokj Reading/Web/Desktop Improvements/Updates/es 0 1379779 5387388 5324170 2022-07-28T22:14:19Z Zapipedia (WMF) 17560702 Created page with "==== $1: Título de la página/cambio de pestañas ====" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] <span lang="en" dir="ltr" class="mw-content-ltr">We are deploying one of our latest updates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The page title will be displayed above the tabs such as {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}}, or {{int:cactions}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">With this change, we are improving two things.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First, we are making it clear that the items in the tabs are related to the the page that's being viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] puvtvxxp0vwm00q6nyj2b196tpicrvn 5387390 5387388 2022-07-28T22:14:32Z Zapipedia (WMF) 17560702 Created page with "Estamos implementando una de nuestras últimas actualizaciones." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. <span lang="en" dir="ltr" class="mw-content-ltr">The page title will be displayed above the tabs such as {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}}, or {{int:cactions}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">With this change, we are improving two things.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First, we are making it clear that the items in the tabs are related to the the page that's being viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] sclw1cqrx4sob2altdhkagx91fd98zc 5387394 5387390 2022-07-28T22:14:40Z Zapipedia (WMF) 17560702 Created page with "El título de la página se mostrará encima de las pestañas como $1, $2, $3, $4 o $5." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. <span lang="en" dir="ltr" class="mw-content-ltr">With this change, we are improving two things.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First, we are making it clear that the items in the tabs are related to the the page that's being viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 4g7oo8nq5xcueb2jrmvk2ff1odrhnmt 5387396 5387394 2022-07-28T22:14:48Z Zapipedia (WMF) 17560702 Created page with "Con este cambio, mejoramos dos cosas." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. <span lang="en" dir="ltr" class="mw-content-ltr">First, we are making it clear that the items in the tabs are related to the the page that's being viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 103w9abx6wr9y430vl1ilww6s80aa45 5387401 5387396 2022-07-28T22:14:59Z Zapipedia (WMF) 17560702 Created page with "En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está viendo." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está viendo. <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 97jznz1j0oct99hzqslrt7xbh0zt3s9 5387404 5387401 2022-07-28T22:15:04Z Zapipedia (WMF) 17560702 wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. <span lang="en" dir="ltr" class="mw-content-ltr">It's becoming apparent when we put the page title first.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 9a68r6bjub9fwbhkq93y3wh15vkgphp 5387408 5387404 2022-07-28T22:15:16Z Zapipedia (WMF) 17560702 Created page with "Se hace evidente cuando ponemos el título de la página en primer lugar." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. <span lang="en" dir="ltr" class="mw-content-ltr">This change also makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] rgeqo5do4p0rrxpikvmygc5y5n4fbcf 5387412 5387408 2022-07-28T22:15:24Z Zapipedia (WMF) 17560702 Created page with "Este cambio también facilita el [[$1|cambio de idioma]]." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. <span lang="en" dir="ltr" class="mw-content-ltr">It moved the language button into an even more prominent position at the top of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] nfi7erfg6nzh80fegpf51y39qhlstnr 5387416 5387412 2022-07-28T22:15:34Z Zapipedia (WMF) 17560702 Created page with "Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. <span lang="en" dir="ltr" class="mw-content-ltr">[[phab:T303549|Learn more on Phabricator]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] koqcfneldc16spp873nvw0dnqp767c7 5387420 5387416 2022-07-28T22:15:43Z Zapipedia (WMF) 17560702 Created page with "[[$1|Descubre más en Phabricator]]." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. <span lang="en" dir="ltr" class="mw-content-ltr">We have been introducing this change in small steps.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 26cefbrlobzl6uy98iv4jnbmfrtwhpk 5387422 5387420 2022-07-28T22:15:52Z Zapipedia (WMF) 17560702 Created page with "Hemos ido introduciendo este cambio en pequeños pasos." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. <span lang="en" dir="ltr" class="mw-content-ltr">Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|early adopter wikis]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] sl54ex98l4cuv14vbs6jrbx751fm493 5387424 5387422 2022-07-28T22:16:29Z Zapipedia (WMF) 17560702 Created page with "Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[$1|wikis early adopter]]." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. <span lang="en" dir="ltr" class="mw-content-ltr">During the week of July 4, the change will become visible on all the early adopter wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] ljztjb3wcijd6oainr4yb1nux3zfn00 5387426 5387424 2022-07-28T22:16:39Z Zapipedia (WMF) 17560702 Created page with "Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. <span lang="en" dir="ltr" class="mw-content-ltr">In addition to that, our next office hours will be on July 26 instead of July 12.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] bffubc1f5v6jqpabuibyh74hn09jr9l 5387428 5387426 2022-07-28T22:16:48Z Zapipedia (WMF) 17560702 Created page with "Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio. <span lang="en" dir="ltr" class="mw-content-ltr">This will allow us to prepare the communication about making Vector 2022 the default across more wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] qd6zp7dz9przchpdvkao6kzm17kylfi 5387430 5387428 2022-07-28T22:17:07Z Zapipedia (WMF) 17560702 Created page with "Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio. Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis. <span lang="en" dir="ltr" class="mw-content-ltr">We are also working on better language support for office hours in the future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] tkf8pzkeki2s2b5iw4ufo7jjp6gwldt 5387432 5387430 2022-07-28T22:17:31Z Zapipedia (WMF) 17560702 Created page with "También estamos trabajando para mejorar el apoyo lingüístico en los encuentros virtuales (horas de oficina) en el futuro." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio. Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis. También estamos trabajando para mejorar el apoyo lingüístico en los encuentros virtuales (horas de oficina) en el futuro. <span lang="en" dir="ltr" class="mw-content-ltr">More information on this coming soon!</span> ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 9ryqzjchg71rrxggpegkbwqhpb4cxcs 5387434 5387432 2022-07-28T22:17:42Z Zapipedia (WMF) 17560702 Created page with "¡Muy pronto te contaremos más!" wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio. Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis. También estamos trabajando para mejorar el apoyo lingüístico en los encuentros virtuales (horas de oficina) en el futuro. ¡Muy pronto te contaremos más! ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. <span lang="en" dir="ltr" class="mw-content-ltr">We are expecting to deploy the new table of contents to our pilot wikis in the first half of April.</span> <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] jcs08te7xnyan5e2wx7mow7aj0lgm8u 5387436 5387434 2022-07-28T22:17:55Z Zapipedia (WMF) 17560702 Created page with "Esperamos implantar el nuevo índice en nuestras wikis piloto en la primera quincena de abril." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio. Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis. También estamos trabajando para mejorar el apoyo lingüístico en los encuentros virtuales (horas de oficina) en el futuro. ¡Muy pronto te contaremos más! ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. Esperamos implantar el nuevo índice en nuestras wikis piloto en la primera quincena de abril. <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. <span lang="en" dir="ltr" class="mw-content-ltr">We hope that soon, at least one Wikisource will be added to that list.</span> ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] 3h803mnkc17ys6rtsqagfydpcy95mqi 5387438 5387436 2022-07-28T22:18:03Z Zapipedia (WMF) 17560702 Created page with "Esperamos que pronto, al menos un Wikisource se añada a esa lista." wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio. Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis. También estamos trabajando para mejorar el apoyo lingüístico en los encuentros virtuales (horas de oficina) en el futuro. ¡Muy pronto te contaremos más! ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. Esperamos implantar el nuevo índice en nuestras wikis piloto en la primera quincena de abril. <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Analise de herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. Esperamos que pronto, al menos un Wikisource se añada a esa lista. ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] hwkh844u904uydp5vxr6ayfydxds4r0 5387706 5387438 2022-07-29T06:08:31Z Zapipedia (WMF) 17560702 wikitext text/x-wiki <languages/> {{Reading/Web/Desktop Improvements/Header}} == Actualizaciones más recientes == <onlyinclude><!-- THE FOLLOWING PART WILL BE VISIBLE ON THE MAIN PAGE OF THE PROJECT. WHEN ADDING A NEW UPDATE, DON'T FORGET TO REMOVE THE OLDEST ONE FROM THIS SECTION ... <includeonly>''[[Reading/Web/Desktop Improvements/Updates#...|Read more]]''</includeonly><noinclude> ...</noinclude> -->{{anchor|Page title/tabs switch}} ==== {{ym|2022|07}}: Título de la página/cambio de pestañas ==== [[File:Page_title_&_tabs_switch_-_ca.png|350px|thumb]] Estamos implementando una de nuestras últimas actualizaciones. El título de la página se mostrará encima de las pestañas como {{int:talk}}, {{int:skin-view-view}}, {{int:skin-view-edit}}, {{int:skin-view-history}} o {{int:cactions}}. Con este cambio, mejoramos dos cosas. En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. Se hace evidente cuando ponemos el título de la página en primer lugar. Este cambio también facilita el [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|cambio de idioma]]. Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. [[phab:T303549|Descubre más en Phabricator]]. Hemos ido introduciendo este cambio en pequeños pasos. Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[Special:MyLanguage/Reading/Web/Desktop_Improvements#test-wikis|wikis early adopter]]. Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio. Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis. También estamos trabajando para mejorar el apoyo lingüístico en los encuentros virtuales (horas de oficina) en el futuro. ¡Muy pronto te contaremos más! ==== {{ym|2022|04}}: Índice de Contenidos disponible ==== Hemos desplegado el nueva [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]]. Facilita la contextualización de los contenidos de una página y la navegación por la misma sin necesidad de desplazarse hasta la parte superior. Actualmente está disponible para tres grupos de usuarios. En primer lugar, todos los que usan Vector 2022 y no forman parte de alguna de nuestras [[Special:MyLanguage/Reading/Web/Desktop Improvements#test-wikis|wikis piloto]]. Segundo y tercero: el 50% de los usuarios conectados a las Wikipedias hebrea y vasca. La semana que viene probaremos el índice de contenidos en el resto de nuestras wikis piloto. Nos gustaría comprobar si disminuye la necesidad de desplazarse hasta la parte superior de la página. Antes de todo eso, preparamos una serie de pruebas de [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents#prototype-editors|prototipo]] con lectores/as y editores/as. Para saber más sobre cómo hemos trabajado en la propuesta a partir de los comentarios recibidos, consulta la página del proyecto. Ahora, estamos trabajando en esta característica basándonos en los comentarios de los usuarios mencionados en el segundo párrafo. En concreto: * ToC en pantallas más estrechas. Hemos aumentado el umbral para el que la TdC se oculta actualmente a 1000px. (Consulta [[phab:T306904|T306904]] para más contexto). Esto fue para hacer más cómoda la lectura en pantallas más estrechas. Sin embargo, se trata de una solución temporal. La conversación sobre la mejor solución continuará en [[phab:T306660|T306660]]. A finales de abril/principios de mayo esperamos tener claros los próximos pasos sobre nuestra preferencia de las opciones allí presentadas. * Estamos empezando a trabajar en la reducción de los márgenes para las pantallas entre 1000px - 1200px. Esto hará que el índice sea más pequeño y creará más espacio para el texto. Haremos un seguimiento de esto en [[phab:T307004|T307004]] y probablemente tendremos la implementación lista dentro de unos días. ==== {{ym|2022|03}}:Desarrollo del índice de contenidos ==== [[File:Table of contents shown on English Wikipedia 02.webm|thumb]] Los resultados de nuestras pruebas [[Special:MyLanguage/Reading/Web/Desktop Improvements/Third prototype testing/Feedback|del tercer prototipo]] mostraron una fuerte aceptación del [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|índice de contenidos]] propuesto. A partir de ahí, el equipo se centró en desarrollar esta función. El nuevo índice de contenidos será persistente - los usuarios tendrán acceso a él en todo momento. Hará más fácil comprender el contexto de la página. Además, será posible navegar a diferentes partes de la página sin tener que desplazarse hasta la parte superior. Esperamos implantar el nuevo índice en nuestras wikis piloto en la primera quincena de abril. <!-- This needs to stay--> </onlyinclude><!-- THIS IS WHERE THE PART VISIBLE ON THE MAIN PAGE ENDS. WHEN ADDING A NEW UPDATE, DON'T FORGET TO DROP THE OLDEST ONE BELOW THIS LINE --> __TOC__ == Otras actualizaciones == ==== {{ym|2022|03}}: Feedback de las herramientas de la Página ==== El equipo está trabajando en las herramientas de página (a veces denominadas herramientas de artículo). Nuestro objetivo es que sea más fácil distinguir el propósito de los elementos individuales dentro de la barra lateral. Actualmente estamos recogiendo opiniones sobre nuestra propuesta de prototipo. Nos gustaría conocer tus opiniones sobre todo esto. Por favor, visita nuestra página [[Reading/Web/Desktop Improvements/Fourth prototype testing|prueba de prototipos]] y rellena el formulario. ==== {{ym|2022|03}}: Encabezado fijo confirmado reduciendo la necesidad de volver al principio de la página ==== [[File:Sticky header logged in.png|thumb]] De enero 5 a 31 de 2022, corremos un [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|prueba Un/B]]. Quisimos evaluar el impacto de desplegar el encabezamiento pegajoso. La prueba corrió sobre 22 piloto wikis. Usuarios conectados agregados al grupo de prueba con la nueva versión de diseño vieron la nueva función de encabezado fijo. Los usuarios del grupo de control vieron la antigua función. El objetivo principal de las pruebas A/B era verificar nuestra hipótesis. Esperábamos que el encabezado fijo disminuyera la necesidad de volver ao principio de la página. En general, vimos una media 15% disminución en rollos por sesión por usuarios conectados en el 15 piloto wikis en el grupo de tratamiento (con el encabezamiento pegajoso nuevo), comparado al grupo de control (sin el encabezamiento pegajoso). Los 7 wikis piloto restantes hubo poca actividad, por lo que eliminamos la función. Los resultados indican que nuestra hipótesis era correcta. Añadiendo el encabezamiento pegajoso a la página redujo la necesidad a rollo hasta arriba de la página significativamente. [https://jenniferwang-wmf.github.io/Web_sticky_header/ Lo informe lleno]. ==== {{ym|2022|01}}: Más wikis piloto ==== Las Mejoras de Escritorio son visibles por defecto en doce wikis. Son, sobre todo: las Wikipedias en árabe marroquí, indonesio, tailandés y vietnamita, Wikiquote en francés, Wikinews en portugués y polaco, Wikilibros en vietnamita y la wiki MediaWiki. Además de estos, hemos habilitado los cambios en los wikis relacionados con la Fundación Wikimedia: Wikimedia Foundation Governance wiki, Collab wiki y Strategy wiki. Actualmente, hay casi 30 wikis piloto. Entre ellas, hay wikis de diferentes guiones y tamaños, escritas en todos los continentes, y gestionadas tanto por las comunidades como por la Fundación. Esperamos que pronto, al menos un Wikisource se añada a esa lista. ==== {{ym|2021|12}}: Desarrollos de encabezado fijo ==== [[File:Sticky header logged in.png|thumb|Encabezado fijo para usuarios conectados]] El equipo ha estado trabajando en construir un [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Sticky_Header|encabezado fijo]]. Permitirá a los usuarios registrados tener acceso a funciones importantes (búsqueda, páginas de discusión, páginas del historial, cambio de idioma, etc.) en toda la página. Hemos completado el desarrollo de la primera versión de la cabecera fija. Ahora, esperamos desplegar una prueba A/B en las wikis piloto a finales de enero. La cabecera se basó en los resultados de nuestras [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Repository/Sticky_Header_and_Table_of_Contents_User_Testing|pruebas de usuarios]] y en las respuestas de los voluntarios a las [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Second_prototype_testing|pruebas de prototipos]]. ==== {{ym|2021|12}}: Iteración de cambio de idioma ==== A principios de este año, trasladamos el botón [[Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Language_switching|idioma]] a una ubicación más adecuada en la parte superior de la página. Sin embargo, los resultados de nuestra prueba A/B indicaron que la nueva ubicación del botón podría ser difícil de descubrir en los siguientes casos: * Para los usuarios que están acostumbrados a la ubicación anterior de la funcionalidad de cambio de idioma * Para los usuarios que tienden a cambiar de idioma en varias wikis. En este último caso, se creaba una situación en la que la funcionalidad de cambio de idioma estaba disponible en diferentes lugares dependiendo de la wiki utilizada y de si esa wikis formaba parte de las wikis piloto. Para mejorar estas cuestiones, estamos cambiando el nuevo botón de idioma. Nuestro objetivo es facilitar la búsqueda en todos los escenarios. Esperamos lanzar estas mejoras en enero de 2022. ==== {{ym|2021|12}}: Pruebas del prototipo de la tabla de contenidos ==== En los próximos meses, nos centraremos principalmente en que el índice de contenidos sea consistente. Actualmente, el índice de contenidos sólo está disponible en la parte superior de la página. Es difícil contextualizar un artículo o una página entera, o navegar a secciones individuales, cuando se está fuera de la parte superior de la página. Esperamos que el índice de contenidos facilite la navegación por una página, así como la comprensión de su contexto. En las próximas semanas publicaremos nuestra investigación, más documentación y prototipos. Mientras tanto, te invitamos a que nos des tu opinión sobre nuestro prototipo actual en esta página. {{:Reading/Web/Desktop Improvements/Updates/Oldest}} [[Category:Desktop Improvements{{#translation:}}]] nc38elv2pt0670ms6ogs63fnlswfp0c Manual:Pywikibot/category.py/zh 100 1388437 5387854 5299636 2022-07-29T10:20:02Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Syntax == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The syntax is: </div> python pwb.py category action [-option] <div lang="en" dir="ltr" class="mw-content-ltr"> where action can be one of the following. </div> {| class="wikitable |- | <code>add</code> || <span lang="en" dir="ltr" class="mw-content-ltr">mass-add a category to a list of pages</span> |- | <code>remove</code> || <span lang="en" dir="ltr" class="mw-content-ltr">remove category tag from all pages in a category</span> |- | <code>move</code> || <span lang="en" dir="ltr" class="mw-content-ltr">move all pages in a category to another category</span> |- | <code>tidy</code> || <span lang="en" dir="ltr" class="mw-content-ltr">tidy up a category by moving its articles into subcategories</span> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <span lang="en" dir="ltr" class="mw-content-ltr">show a tree of subcategories of a given category</span> |- | <code>listify</code> || <span lang="en" dir="ltr" class="mw-content-ltr">make a list of all of the articles that are in a category</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> and option can be one of the following. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>add</code> action</span> === {| class="wikitable" |- | <code>-person</code> || <span lang="en" dir="ltr" class="mw-content-ltr">sort persons by their last name</span> |- | <code>-create</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If a page doesn't exist, do not skip it, create it instead</span> |- | <code>-redirect</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Follow redirects</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> For this action, [[#page_generators|page generator options]] are supported. </div> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>listify</code> action</span> === * -overwrite - <span lang="en" dir="ltr" class="mw-content-ltr">This overwrites the current page with the list even if something is already there.</span> * -showimages - <span lang="en" dir="ltr" class="mw-content-ltr">This displays images rather than linking them in the list.</span> * -talkpages - <span lang="en" dir="ltr" class="mw-content-ltr">This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>remove</code> action</span> === * -nodelsum - <span lang="en" dir="ltr" class="mw-content-ltr">This specifies not to use the custom edit summary as the deletion reason.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Options for <code>move</code> action === </div> {| class="wikitable" | -hist || <span lang="en" dir="ltr" class="mw-content-ltr">Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</span> |- | -nodelete || <span lang="en" dir="ltr" class="mw-content-ltr">Don't delete the old category after move</span> |- | -nowb || <span lang="en" dir="ltr" class="mw-content-ltr">Don't update the wikibase repository</span> |- | -allowsplit || <span lang="en" dir="ltr" class="mw-content-ltr">If that option is not set, it only moves the talk and main page together.</span> |- | -mvtogether || <span lang="en" dir="ltr" class="mw-content-ltr">Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist.</span> |- | -keepsortkey | <span lang="en" dir="ltr" class="mw-content-ltr">Use sortKey of the old category also for the new category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not specified, sortKey is removed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alternative method to keep sortKey is to use -inplace option.</span> |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for <code>tidy</code> action</span> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Filter the articles in the specified namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Separate multiple namespace numbers or names with commas.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Examples:</span> -ns:0,2,4 -ns:Help,MediaWiki |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for several actions</span> === {| class="wikitable" | -rebuild || <span lang="en" dir="ltr" class="mw-content-ltr">reset the database</span> |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] 5a396zi19etbe5msq0dry2sfx3cvnrc Extension:Highlight Links in Category/zh 102 1388732 5387156 5345734 2022-07-28T21:08:01Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''Highlight Links in Category''' is an extension that adds a CSS class to links pointing to members of a category. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Installation== </div> {{ExtensionInstall|HighlightLinksInCategory|registration=required}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Configuration parameters== </div> ; $wgHighlightLinksInCategory : <span lang="en" dir="ltr" class="mw-content-ltr">This global is an array that configures which categories get an added CSS class. The keys are the Category names, which must include underscores instead of spaces. Do not include the Category: namespace. The value for each key is the CSS class you would like to add to that category. For example:</span> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want add more than one class, separate the class names with spaces, like </div> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can add as many of these as you want, but from a UX perspective it's probably not awesome to add 500 different style links. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If $wgHighlightLinksInCategory is not set or empty, this extension will do nothing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're running a wiki farm and need to turn it off on some wikis, set <syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight>; using {{phpi|false}} could lead to incorrect behavior.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Styling== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Simply add the styles you need for these links to MediaWiki:Common.css on your wiki. For example: </div> {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want one category to override another, you'll have to specify it with CSS. </div> {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> Or alternatively, you could have defined the original <code>a.templates</code> rule as <code>a.templates:not(.disambig)</code> instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There's also the link icon approach: </div> {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==User Toggles== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An easy way to set up toggling this highlighting on or off is to make a [[Extension:Gadgets|Gadget]] with CSS in it. Yes, this is a personalization extension that outsources the personalization part to other extensions; I can still sleep at night. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==How this works== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Right after MediaWiki determines which linked pages exist (to make redlinks), it runs the <code>GetLinkColours</code> hook (see LinkHolderArray.php).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As we have a list of all of the page ids which are linked on that page, we can run one database query to see which of these links are in the set of categories we want to highlight.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Because the query only happens on an index of the <code>categorylinks</code> table, it's reasonably fast.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then CSS classes are assigned based on the result, using the configuration values the user sets in <code>$wgHighlightLinksInCategory</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Explaining how CSS works is outside the scope of this document. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Known issues== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * CSS styles are not added in Flow, because it doesn't appear to call the GetLinkColors hook there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==See also== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:Category:LinkEnd extensions]] - which customize links in other ways </div> {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] 2792syml3p02spm46sc4ya7id5hvui0 Manual:Pywikibot/category.py/es 100 1391175 5387846 5299627 2022-07-29T10:19:56Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} == Sintaxis == La sintaxis es: python pwb.py category action [-option] donde la acción puede ser una de las siguientes. {| class="wikitable |- | <code>add</code> || agregar masivamente una categoría a una lista de páginas |- | <code>remove</code> || eliminar la etiqueta de categoría de todas las páginas de una categoría |- | <code>move</code> || mover todas las páginas de una categoría a otra categoría |- | <code>tidy</code> || ordenar una categoría moviendo sus artículos a subcategorías |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || mostrar un árbol de subcategorías de una categoría determinada |- | <code>listify</code> || hacer una lista de todos los artículos que están en una categoría |} y la opción puede ser una de las siguientes. === Opciones para la acción <code>add</code> === {| class="wikitable" |- | <code>-person</code> || ordenar a las personas por su apellido |- | <code>-create</code> || Si una página no existe, no la omitas, créala en su lugar |- | <code>-redirect</code> || Seguir redirecciones |} Para esta acción, se admiten las [[#page_generators|opciones del generador de páginas]]. === Opciones para la acción de <code>listify</code> === * -overwrite - Esto sobrescribe la página actual con la lista incluso si ya hay algo allí. * -showimages - Esto muestra imágenes en lugar de vincularlas en la lista. * -talkpages - Esto genera los enlaces a las páginas de discusión de las páginas que se enumerarán además de las páginas en sí. === Opciones para la acción de <code>remove</code> === * -nodelsum - Esto especifica que no se utilice el resumen de edición personalizado como motivo de eliminación. En su lugar, utiliza el motivo de eliminación predeterminado para el idioma, que es "Category was disbanded" en inglés. === Opciones para la acción de <code>move</code> === {| class="wikitable" | -hist || Crea una bonita wikitable en la página de discusión de la categoría de destino que contiene el historial detallado de la página de la categoría de origen. |- | -nodelete || No elimines la categoría anterior después de moverla |- | -nowb || No actualices el repositorio de wikibase |- | -allowsplit || Si esa opción no está configurada, solo mueve la discusión y la página principal juntas. |- | -mvtogether || Solo mueve las páginas/subcategorías de una categoría, si la página de destino (y la página de discusión, si no se establece -allowsplit) no existe. |- | -keepsortkey | Usa sortKey de la categoría anterior también para la nueva categoría. Si no se especifica, sortKey se elimina. Un método alternativo para mantener sortKey es usar la opción -inplace. |} === Opciones para la acción de <code>tidy</code> === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | Filtra los artículos en los espacios de nombres especificados. Separa varios nombres o números de espacios de nombres con comas. Ejemplos: -ns:0,2,4 -ns:Help,MediaWiki |} === Opciones para varias acciones === {| class="wikitable" | -rebuild || restablecer la base de datos |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= <span lang="en" dir="ltr" class="mw-content-ltr">For options ''-from'' and ''-to'':</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] pd50wtu86fobu77qd67qekkbxk63axe Reading/Web/Desktop Improvements/Updates/Talk to Web 0 1397135 5387101 5383444 2022-07-28T20:35:07Z SGrabarczuk (WMF) 9240933 typo wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <translate><!--T:30--> We have planned two types of meetings:</translate> * <translate><!--T:31--> '''The regular ones''' are for anyone interested in the project.</translate> <translate><!--T:32--> We share updates, gather feedback, and answer questions.</translate> <translate><!--T:33--> Anyone is equally welcomed.</translate> * <translate><!--T:34--> '''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</translate> <translate><!--T:35--> We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</translate> <translate><!--T:36--> Anyone is welcomed, too.</translate> '''<translate><!--T:37--> [<tvar name="link">https://wikimedia.zoom.us/j/5304280674</tvar> Click here to join] / [<tvar name="dial">https://wikimedia.zoom.us/u/kc2hamfYz9</tvar> dial by your location] / [<tvar name="notes">https://etherpad.wikimedia.org/p/web-team-office-hours</tvar> notes].</translate>''' <translate><!--T:38--> These links work for all the meetings except the one at Wikimania.</translate> <translate> == Timeline == <!--T:19--> </translate> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <translate><!--T:20--> regular meeting</translate></span> * {{ymd|2022|8|2}}, 17:00 UTC - <translate><!--T:26--> meeting with simultaneous interpretation in Russian</translate> * {{ymd|2022|8|4}}, 17:00 UTC - <translate><!--T:22--> meeting with simultaneous interpretation in Arabic</translate> * {{ymd|2022|8|4}}, 19:00 UTC - <translate><!--T:24--> meeting with simultaneous interpretation in Spanish</translate> * {{ymd|2022|8|13}}, 8:05 UTC - <translate><!--T:39--> Wikimania session about Vector 2022</translate> * {{ymd|2022|8|18}}, 10:00 UTC <translate><!--T:28--> (tentative)</translate> - <translate><!--T:29--> meeting with simultaneous interpretation in Chinese</translate> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <translate><!--T:27--> regular meeting</translate> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=<translate><!--T:18--> Archive</translate> |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 38nlzr9jpkwxsycmqht1mnaazz89gvd Reading/Web/Desktop Improvements/Updates/Talk to Web/en 0 1397154 5387109 5383448 2022-07-28T20:35:21Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} We have planned two types of meetings: * '''The regular ones''' are for anyone interested in the project. We share updates, gather feedback, and answer questions. Anyone is equally welcomed. * '''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities. We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis. Anyone is welcomed, too. '''[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].''' These links work for all the meetings except the one at Wikimania. == Timeline == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - regular meeting</span> * {{ymd|2022|8|2}}, 17:00 UTC - meeting with simultaneous interpretation in Russian * {{ymd|2022|8|4}}, 17:00 UTC - meeting with simultaneous interpretation in Arabic * {{ymd|2022|8|4}}, 19:00 UTC - meeting with simultaneous interpretation in Spanish * {{ymd|2022|8|13}}, 8:05 UTC - Wikimania session about Vector 2022 * {{ymd|2022|8|18}}, 10:00 UTC (tentative) - meeting with simultaneous interpretation in Chinese * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - regular meeting <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archive |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} po1fc8gi2sce9ctialftfaobohvcs1u Reading/Web/Desktop Improvements/Updates/Talk to Web/fr 0 1397156 5387111 5383453 2022-07-28T20:35:24Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archives |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} exnwdmqi7596p00cdf16nbiefceajxg Reading/Web/Desktop Improvements/Updates/Talk to Web/pl 0 1397180 5387118 5383459 2022-07-28T20:35:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> == Harmonogram == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - zwykłe spotkanie</span> * {{ymd|2022|8|2}}, 17:00 UTC - spotkanie z symultanicznym tłumaczeniem w języku rosyjskim * {{ymd|2022|8|4}}, 17:00 UTC - spotkanie z symultanicznym tłumaczeniem w języku arabskim * {{ymd|2022|8|4}}, 19:00 UTC - spotkanie z symultanicznym tłumaczeniem w języku hiszpańskim * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC (wstępnie) - spotkanie z symultanicznym tłumaczeniem w języku chińskim * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - zwykłe spotkanie <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archiwum |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 27mbg9ujyni856sb98q0ror6k26t4o3 Reading/Web/Desktop Improvements/Updates/Talk to Web/pt-br 0 1397190 5387119 5383593 2022-07-28T20:35:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} Planejamos dois tipos de reuniões: * '''Os regulares''' são para qualquer pessoa interessada no projeto. Compartilhamos atualizações, coletamos feedback e respondemos a perguntas. Qualquer pessoa é igualmente bem-vinda. * '''Aqueles com interpretação simultânea''' são dedicados a comunidades específicas da Wikimedia. Esperamos ver uma boa representação desses, e gostaríamos de nos concentrar no Vector 2022 em suas wikis. Qualquer pessoa também é bem-vinda. '''<span class="mw-translate-fuzzy">[https://wikimedia.zoom.us/j/5304280674 Clique aqui para participar] / [https://wikimedia.zoom.us/u/kc2hamfYz9 Discar a partir da sua localização] / [https://etherpad.wikimedia.org/p/web-team-office-hours notas].</span>''' Estes links funcionam para todas as reuniões, exceto a reunião no Wikimania. <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - reunião regular</span> * {{ymd|2022|8|2}}, 17:00 UTC - reunião com interpretação simultânea em russo * {{ymd|2022|8|4}}, 17:00 UTC - reunião com interpretação simultânea em árabe * {{ymd|2022|8|4}}, 19:00 UTC - reunião com interpretação simultânea em espanhol * {{ymd|2022|8|13}}, 8:05 UTC - Sessão do Wikimania sobre Vector 2022 * {{ymd|2022|8|18}}, 10:00 UTC (provisório) - reunião com interpretação simultânea em chinês * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - reunião regular <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Arquivos |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} o2iti1fz73h810of713ms4qpzn4wooa 5387128 5387119 2022-07-28T20:35:36Z SGrabarczuk (WMF) 9240933 wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} Planejamos dois tipos de reuniões: * '''Os regulares''' são para qualquer pessoa interessada no projeto. Compartilhamos atualizações, coletamos feedback e respondemos a perguntas. Qualquer pessoa é igualmente bem-vinda. * '''Aqueles com interpretação simultânea''' são dedicados a comunidades específicas da Wikimedia. Esperamos ver uma boa representação desses, e gostaríamos de nos concentrar no Vector 2022 em suas wikis. Qualquer pessoa também é bem-vinda. '''[https://wikimedia.zoom.us/j/5304280674 Clique aqui para participar] / [https://wikimedia.zoom.us/u/kc2hamfYz9 discar a partir da sua localização] / [https://etherpad.wikimedia.org/p/web-team-office-hours notas].''' Estes links funcionam para todas as reuniões, exceto a reunião no Wikimania. <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - reunião regular</span> * {{ymd|2022|8|2}}, 17:00 UTC - reunião com interpretação simultânea em russo * {{ymd|2022|8|4}}, 17:00 UTC - reunião com interpretação simultânea em árabe * {{ymd|2022|8|4}}, 19:00 UTC - reunião com interpretação simultânea em espanhol * {{ymd|2022|8|13}}, 8:05 UTC - Sessão do Wikimania sobre Vector 2022 * {{ymd|2022|8|18}}, 10:00 UTC (provisório) - reunião com interpretação simultânea em chinês * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - reunião regular <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Arquivos |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} qelr8f7r52tgbx2xcyug4rvrjlcvkl3 Reading/Web/Desktop Improvements/Updates/Talk to Web/bn 0 1397221 5387104 5383445 2022-07-28T20:35:16Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=আর্কাইভ |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 8he7wi0vhza2ctkoihyq8mjyxdtlu5h Reading/Web/Desktop Improvements/Updates/Talk to Web/ja 0 1397245 5387115 5383457 2022-07-28T20:35:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} 2種類のミーティングを以下のように計画しました。 * '''定例'''として、プロジェクトに関心のある皆さん全体を対象に開催。 議事は更新情報、フィードバックの聞き取り、質疑応答を予定します。 どなたでもご参加ください。 * '''同時通訳'''を手配する回とは、ウィキメディアの特定のコミュニティ対象で行います。 対象コミュニティからできるだけ多くの人に参加していただくことと、話題はその皆さんのウィキでベクター2022をどうするかに集中したい所存です。 こちらもどなたでもご参加ください。 '''<span class="mw-translate-fuzzy">[https://wikimedia.zoom.us/j/5304280674 参加登録はこちら] / [https://wikimedia.zoom.us/u/kc2hamfYz9 地域のダイヤルアップにつなぐ] / [https://etherpad.wikimedia.org/p/web-team-office-hours 注記]。</span>''' ここに挙げたリンクはどのミーティングの場合も使えますが、ウィキマニアは除外します。 == タイムライン == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - 定例</span> * {{ymd|2022|8|2}}, 17:00 UTC - 同時通訳、ロシア語 * {{ymd|2022|8|4}}, 17:00 UTC - 同時通訳、アラビア語 * {{ymd|2022|8|4}}, 19:00 UTC - 同時通訳、スペイン語 * {{ymd|2022|8|13}}, 8:05 UTC - ウィキマニアの集会、ベクター2022について * {{ymd|2022|8|18}}, 10:00 UTC (暫定) - 同時通訳、中国語 * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - 定例 <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=過去ログ |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 4k76irrc3s25iwit88nofesip0vdtnx 5387132 5387115 2022-07-28T20:35:51Z SGrabarczuk (WMF) 9240933 wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} 2種類のミーティングを以下のように計画しました。 * '''定例'''として、プロジェクトに関心のある皆さん全体を対象に開催。 議事は更新情報、フィードバックの聞き取り、質疑応答を予定します。 どなたでもご参加ください。 * '''同時通訳'''を手配する回とは、ウィキメディアの特定のコミュニティ対象で行います。 対象コミュニティからできるだけ多くの人に参加していただくことと、話題はその皆さんのウィキでベクター2022をどうするかに集中したい所存です。 こちらもどなたでもご参加ください。 '''[https://wikimedia.zoom.us/j/5304280674 参加登録はこちら] / [https://wikimedia.zoom.us/u/kc2hamfYz9 地域のダイヤルアップにつなぐ] / [https://etherpad.wikimedia.org/p/web-team-office-hours 注記]。''' ここに挙げたリンクはどのミーティングの場合も使えますが、ウィキマニアは除外します。 == タイムライン == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - 定例</span> * {{ymd|2022|8|2}}, 17:00 UTC - 同時通訳、ロシア語 * {{ymd|2022|8|4}}, 17:00 UTC - 同時通訳、アラビア語 * {{ymd|2022|8|4}}, 19:00 UTC - 同時通訳、スペイン語 * {{ymd|2022|8|13}}, 8:05 UTC - ウィキマニアの集会、ベクター2022について * {{ymd|2022|8|18}}, 10:00 UTC (暫定) - 同時通訳、中国語 * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - 定例 <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=過去ログ |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} qxn9eq6ee8unvbqs4jjy723rz64tbd7 Reading/Web/Desktop Improvements/Updates/Talk to Web/fa 0 1397314 5387110 5386118 2022-07-28T20:35:22Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} ما برای دو نوع جلسه برنامه‌ریزی کرده‌ایم: * '''جلسات منظم''' برای علاقه‌مندان به پروژه. در این جلسات، به‌روزرسانی‌ها را به اشتراک می‌گذاریم، بازخورد جمع‌آوری می‌کنیم و به سؤالات پاسخ می‌دهیم. از همه افراد به طور یکسان استقبال می‌شود. * '''آنهایی که به طور همزمان ترجمه می‌شوند''' که به کاربران یک ویکی‌مدیای خاص اختصاص داده شده‌اند. امیدواریم که بتوانیم ارائه خوبی از این جلسات ببینیم، مایلیم که در این ویکی‌ها بر روی وکتور ۲۰۲۲ تمرکز کنیم. از هر کسی هم استقبال می‌شود. '''<span class="mw-translate-fuzzy">[https://wikimedia.zoom.us/j/5304280674 برای عضویت اینجا را کلیک کنید] / [https://wikimedia.zoom.us/u/kc2hamfYz9 شماره‌گیری کنید] / [https://etherpad.wikimedia.org/p/web-team-office-hours یادداشت‌ها].</span>''' این پیوندها برای همه جلسات به جز جلسه ویکی‌مانیا کار می‌کنند. ==زمان‌بندی== * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - جلسه منظم</span> * {{ymd|2022|8|2}}, 17:00 UTC - جلسه با ترجمه همزمان به زبان روسی * {{ymd|2022|8|4}}, 17:00 UTC - جلسه با ترجمه همزمان به زبان عربی * {{ymd|2022|8|4}}, 19:00 UTC - جلسه با ترجمه همزمان به زبان اسپانیایی * {{ymd|2022|8|13}}, 8:05 UTC - جلسه ویکی‌مانیا درباره وکتور ۲۰۲۲ * {{ymd|2022|8|18}}, 10:00 UTC (آزمایشی) - جلسه با ترجمه همزمان به زبان چینی * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - جلسه منظم <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=بایگانی‌ها |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} jlatq27qxl6kafgpqqxxv5wlo81767p 5387131 5387110 2022-07-28T20:35:46Z SGrabarczuk (WMF) 9240933 wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} ما برای دو نوع جلسه برنامه‌ریزی کرده‌ایم: * '''جلسات منظم''' برای علاقه‌مندان به پروژه. در این جلسات، به‌روزرسانی‌ها را به اشتراک می‌گذاریم، بازخورد جمع‌آوری می‌کنیم و به سؤالات پاسخ می‌دهیم. از همه افراد به طور یکسان استقبال می‌شود. * '''آنهایی که به طور همزمان ترجمه می‌شوند''' که به کاربران یک ویکی‌مدیای خاص اختصاص داده شده‌اند. امیدواریم که بتوانیم ارائه خوبی از این جلسات ببینیم، مایلیم که در این ویکی‌ها بر روی وکتور ۲۰۲۲ تمرکز کنیم. از هر کسی هم استقبال می‌شود. '''[https://wikimedia.zoom.us/j/5304280674 برای عضویت اینجا را کلیک کنید] / [https://wikimedia.zoom.us/u/kc2hamfYz9 شماره‌گیری کنید] / [https://etherpad.wikimedia.org/p/web-team-office-hours یادداشت‌ها].''' این پیوندها برای همه جلسات به جز جلسه ویکی‌مانیا کار می‌کنند. ==زمان‌بندی== * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - جلسه منظم</span> * {{ymd|2022|8|2}}, 17:00 UTC - جلسه با ترجمه همزمان به زبان روسی * {{ymd|2022|8|4}}, 17:00 UTC - جلسه با ترجمه همزمان به زبان عربی * {{ymd|2022|8|4}}, 19:00 UTC - جلسه با ترجمه همزمان به زبان اسپانیایی * {{ymd|2022|8|13}}, 8:05 UTC - جلسه ویکی‌مانیا درباره وکتور ۲۰۲۲ * {{ymd|2022|8|18}}, 10:00 UTC (آزمایشی) - جلسه با ترجمه همزمان به زبان چینی * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - جلسه منظم <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=بایگانی‌ها |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} iqmn6isy43qx7vk9opja5yb3fhwjvq2 Reading/Web/Desktop Improvements/Updates/Talk to Web/ar 0 1397330 5387105 5383446 2022-07-28T20:35:17Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span class="mw-translate-fuzzy">[https://wikimedia.zoom.us/j/5304280674 اضغط هنا للانضمام] / [https://wikimedia.zoom.us/u/kc2hamfYz9 اتصل عبر موقعك] / [https://etherpad.wikimedia.org/p/web-team-office-hours ملاحظات الإجتماع].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=الأرشيف |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 9s0kt5eyizybjvf15pne4bmvd644rww Reading/Web/Desktop Improvements/Updates/Talk to Web/he 0 1397736 5387112 5383455 2022-07-28T20:35:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=ארכיון |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 4cf4na3dxlm0iedib19oml45pssz8ro New requirements for user signatures/nan 0 1405370 5386347 5325342 2022-07-28T13:22:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <span lang="en" dir="ltr" class="mw-content-ltr">Many wikis have requirements for custom user signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Editing team|Editing team]] is seeking your input on a proposal to codify some of these requirements in Wikipedia's software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will make it easier to [[mw:Talk pages project/replying|reply to specific comments on talk pages]] and to use some other tools.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find more details about what is being proposed, and why, below: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">What feedback the team is seeking:</span> '''[[#Input: your feedback|<span lang="en" dir="ltr" class="mw-content-ltr">Input: your feedback</span>]]''' * <span lang="en" dir="ltr" class="mw-content-ltr">Why this change is being proposed:</span> '''[[#Background: why this change?|<span lang="en" dir="ltr" class="mw-content-ltr">Background: why this change?</span>]]''' * <span lang="en" dir="ltr" class="mw-content-ltr">What change is being proposed:</span> '''[[#Proposal: signature validation requirements|<span lang="en" dir="ltr" class="mw-content-ltr">Proposal: signature validation requirements</span>]]''' * <span lang="en" dir="ltr" class="mw-content-ltr">How these changes could affect you:</span> '''[[#Impact: effects of change|<span lang="en" dir="ltr" class="mw-content-ltr">Impact: effects of change</span>]]''' __TOC__ {{anchor|Input: your feedback}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Input: your feedback == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The team wants your feedback about this proposal. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please post your comments about these questions [[Talk:New requirements for user signatures|'''on the talk page''']]: </div> # '''<span lang="en" dir="ltr" class="mw-content-ltr">Would these signature validations create any problems on your wiki?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What do you think the team should be aware of before making this change?</span>''' # '''<span lang="en" dir="ltr" class="mw-content-ltr">What should be done about existing signatures that don't meet the new limits?</span>''' <em><span lang="en" dir="ltr" class="mw-content-ltr">For example, should they be disallowed?</span></em> <em><span lang="en" dir="ltr" class="mw-content-ltr">Please do not feel limited by the questions above. The team wants to hear any feedback you have to share.</span></em> {{anchor|Background: why this change?}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Background: why this change? == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In 2019, volunteers from [[mw:Talk pages consultation 2019/Participant group sign-up|20 Wikimedia projects and usergroups]], along with staff from the Wikimedia Foundation, participated in the [[mw:Talk_pages_consultation_2019|Talk pages consultation]]. It was an effort to define better tools for on-wiki communication. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One of the outcomes of this consultation was [[mw:Talk_pages_consultation_2019/Phase_1_report#Replying|a request for an easier way to reply to specific comments]] on talk pages. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order for [[mw:Talk_pages_project/replying|this feature]] to work well, the software needs signatures to be "machine-readable", so it can reliably detect users' comments and allow replying to them. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The trouble is, while many wikis already have the necessary signature requirements in place, these requirements are not included in the software itself.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This increases the chances someone will set a signature that breaks the wiki's conventions and potentially, make it more difficult for people to participate in conversations.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This additional consistency in the format of signatures would improve existing features, like [[mw:Help:Notifications/Types#Mentions|"mention" notifications]], which are only sent if the signature can be detected in your edit. </div> {{anchor|Proposal: signature validation requirements}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Proposal: signature validation requirements (2020) == </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' <span lang="en" dir="ltr" class="mw-content-ltr">If no significant obstacles are identified, this change could happen in April 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the team needs to make significant changes as a result of your feedback, then it will take longer.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The three proposed checks are described in this section. These would be applied to user signatures in Preferences when a user saves a modified signature.</span> {{Highlight|1=<big><span lang="en" dir="ltr" class="mw-content-ltr">Under the Editing team's proposal '''existing signatures will *NOT* be affected'''.</span></big>|color=yellow}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors === </div> {{Tracked|T140606}} <span lang="en" dir="ltr" class="mw-content-ltr">Most importantly, this change would disallow unclosed formatting tags, like {{tag|i|open}} or the corresponding wikitext markup, <code><nowiki>''</nowiki></code>, without a matching closing tag (in this case, {{tag|i|close}} or <code><nowiki>''</nowiki></code>, respectively).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Signatures containing invalid markup can affect the entire discussion page, when the formatting continues into subsequent comments.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The check would also identify [[Special:LintErrors/misnested-tag|misnested tags]], like <syntaxhighlight lang=html inline><b>foo<i>bar</b></i></syntaxhighlight> (either both of the <code>i</code>, or both of the <code>b</code>, tags should be on the outside), and [[Special:LintErrors/stripped-tag|stripped tags]], which are closing tags without a corresponding opening tag (the opposite of the "unclosed formatting tag" listed above). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Signatures that contain some less critical problems would also be disallowed, e.g., obsolete HTML tags like {{tag|tt}} and {{tag|font}}. While these do not cause immediate issues, doing this would prevent the spread of obsolete code to new wiki pages, which is an annoyance for editors cleaning up Linter errors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A full list of syntax features that would not be allowed, along with links to pages that explain how to update or fix code with Linter errors, is available at [[mw:Help:Extension:Linter#Documentation of lint issues|this address]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Unclosed formatting tags were already supposed to be prevented by the software, but due to limitations of the current wikitext parser, this worked only in some cases. A more robust solution has become possible thanks to [[Parsoid]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Require a link to user page, talk page or contributions === </div> {{Tracked|T237700}} <span lang="en" dir="ltr" class="mw-content-ltr">Various tools don't work correctly when a signature does not contain at least one of the following links: a link to the user's user page, user talk page, or contributions page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [[mw:Help:Notifications/Types#Mentions|"mention" notifications]] are not sent, and forthcoming [[mw:Extension:DiscussionTools|DiscussionTools]] will not allow replying to comments with these invalid signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Gadgets and other tools that interact with signatures also may not work as expected.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requirement has been present for a long time in many Wikimedia wikis' policies, but it has not been enforced by the MediaWiki software.</span><ref><span lang="en" dir="ltr" class="mw-content-ltr">See examples listed on [[phab:T237700|T237700]].</span></ref> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow "nested" substitution in signature === </div> {{Tracked|T230652}} <span lang="en" dir="ltr" class="mw-content-ltr">''Some'' use of [[subst:]] markup and tildes would also be disallowed in signatures.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Previously, it was possible to use these features to set a signature that would cause a subsequent editor's name to be placed on your comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All forms of signature forgery have long been banned by policy at the larger wikis, and this type of forgery will now be prevented in software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Simple subst: markup is still allowed.</span> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Additional proposal (2021) == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Disallow line breaks in signature === </div> <div style="background-color: #F3F9FF; margin: 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;"> : ''This is an archived record of a previous proposal. <span style="color:red">'''Please do not modify it.'''</span> A summary of the conclusions reached is in the [[#Outcome]] section.'' {{tracked|T272322}} The signature must consist of a single line of wikitext. Line breaks can result in incorrect formatting when the signature is used in a nested comment. They can also cause problems with tools used on discussion pages. This affects the literal [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] characters, not {{tag|br|open}} and {{tag|p|open}}. At this time, you cannot add these characters to a custom signature in [[Special:Preferences]]. This proposal will prevent them from being added via a substituted signature template or by editing your preferences programatically. </div> {{anchor|Impact: effects of change}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Impact: effects of change == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What would happen to existing signatures? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Any existing signatures that would become invalid under the new rules are still allowed (''[[:en:Grandfather_clause|grandfathered in]]'').</span> <span lang="en" dir="ltr" class="mw-content-ltr">When viewing your preferences, you would see a warning message about this, and if you try to change the signature, the new one must be valid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">But if you don't change it, the old invalid signature will continue to be used when you sign, and you'll be able to change your other preferences without affecting it.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're looking for feedback as to whether you would like existing invalid signatures to be disallowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If invalid signatures are disallowed, the default signature would be inserted when affected users sign their comments, until they correct their personalized signatures.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === When might these changes take place? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Please comment before 31 March 2020.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Editing team will make decisions about this project in early April.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The results will be posted on the talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If no obstacles are identified, this change would happen no earlier than April 2020. This date could be pushed back if the team needs to implement significant changes as a result of your feedback. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How will we know what changes are happening? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We'll include another notice in [[m:Tech/News]] when this change is about to be deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === What might the signature validation errors look like? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The HTML/lint errors include links to existing documentation about lint errors, such as [[mw:Help:Extension:Linter/missing-end-tag|Help:Extension:Linter/missing-end-tag]], and a button to highlight the problematic part of the signature. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The required link errors include example wikitext syntax to use. </div> <gallery mode="packed" caption="Example errors"> File:MediaWiki preferences - existing user signature invalid.png|<span lang="en" dir="ltr" class="mw-content-ltr">Warning shown when the existing user signature is invalid (has lint errors).</span> File:MediaWiki preferences - new user signature invalid 1.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (has a lint error).</span> File:MediaWiki preferences - new user signature invalid 2.png|<span lang="en" dir="ltr" class="mw-content-ltr">Error shown when the new user signature is invalid (doesn't contain a required link).</span> </gallery> == Kiat-kó == ===Guân thê-àn=== <div lang="en" dir="ltr" class="mw-content-ltr"> The proposal was largely accepted. In response to comments from volunteers, a few small changes were made and a few points were clarified. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow some invalid HTML and other [[mw:Help:Extension:Linter|Linter]] errors</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">The scope of these changes will be reduced.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:LintErrors/misnested-tag|Misnested]] and [[Special:LintErrors/stripped-tag|stripped]] tags will be rejected. Some low-priority errors will still be accepted. Specifically, obsolete HTML tags like {{tag|tt}} and {{tag|font}} will not be banned at this time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This decision does not prejudice any future decision for or against removing these obsolete HTML tags.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Require a link to user page, talk page or contributions</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">For clarity, there must be at least one local direct link (not via a redirect, e.g. from old username) to one of those pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, a signature of <code><nowiki>[[User:Example|Example]] ([[m:User talk:Example]])</nowiki></code> would be acceptable (one local link, one link to another wiki), but a signature that includes <em>only</em> links to another wiki, or <em>only</em> redirects from a former username, will be invalid.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is for technical reasons.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Disallow "nested" substitution in signature</span> #:<span lang="en" dir="ltr" class="mw-content-ltr">This will be implemented as originally planned.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The process for implementing this change is: </div> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">A general announcement will be made in [[m:Tech/News|Tech News]] when the new requirements are deployed.</span> * {{done}} <span lang="en" dir="ltr" class="mw-content-ltr">Once the software change has been made on the servers, users will no longer be able to save invalid custom signatures. However, existing signatures will remain.</span> * {{in progress}} <span lang="en" dir="ltr" class="mw-content-ltr">Active editors with invalid signatures will be encouraged to change their signatures. This process will likely take some months.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Eventually, all signatures will need to conform. If editors do not correct their custom signatures, then their custom signatures will stop working, and the default signature will appear instead.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party wikis will be able to enable this change manually. </div> ===2021 thê-àn=== <div lang="en" dir="ltr" class="mw-content-ltr"> The line break characters [[w:Carriage return|carriage return]] and [[w:Newline|line feed]] (but not the HTML codes for them, e.g., {{tag|br|single}} and {{tag|p|open}}) are disallowed. </div> == Tsù-kái == <references /> [[Category:Requests for comment]] [[Category:Discussions{{#translation:}}]] [[Category:Talk pages project{{#translation:}}]] 14si7m838soa15m4ans4lad1pc4c6x1 Abstract Wikipedia team/Meetings plan 0 1407290 5386384 5361520 2022-07-28T13:35:50Z MShilova (WMF) 17566683 Changed the cadence of the Volunteers Corner meetings from weekly to monthly. wikitext text/x-wiki {{Draft}} == Team-wide meetings == Below is the list of the '''Abstract Wikipedia team-wide meetings''' each week, what they should be about and who would be expected at each: {| class="wikitable" |+Abstract Wikipedia Team meetings plan, as of 2022-05-24 ! rowspan="3" |Meeting ! rowspan="3" |Timing ! rowspan="3" |Purpose ! rowspan="3" |Agenda ! colspan="7" |Attendance |- !Product !Design !Management ! colspan="2" |Engineering !Community !Program |- !L !L !EM !L !* !L !L |- !Scrum of Scrums |Weekly |Meeting for the whole team to share blockers, help one another remove impediments and promote cross-worstream collaboration. | * Stress / happiness check-in * Review previous action items * Discuss urgent topics * Workstream-specifc items * Non-urgent items |✅ |✅ |✅ |✅ |✅ |✅ |✅ |- !Volunteers' Corner |Monthly (first Monday of the month) |Informal space for volunteers and the AW team members for pairing, code review, talking about what volunteers have achieved or how to approach a task, which task is best to pick up next, etc. | * Open agenda |✅ |〰️ |〰️ |✅ |〰️ |〰️ |〰️ |- !Social |Weekly |A "water-cooler" meeting / "un-meeting" where any and all of the team can talk socially about how things are going in their lives and anything else they'd like to share, to bond with each other. [Not recorded.] | |〰️ |〰️ |〰️ |〰️ |〰️ |〰️ |〰️ |- !Planning |Weekly |Ensure that the team is working on the right tasks at the right time. Re-work tasks' definitions to have clear descriptions, identify blockers and decision points, and set priority. '''Product:''' Set the relative priority of tasks and understand likely timelines. '''Design''': Ensure that design tasks are written and will be undertaken before any related engineering tasks start. '''Engineering''': Flag tasks that will need further technical work or discussion. | *Bring-up tasks that need re-thinking. *Triage incoming tasks, deciding if they should be done before launch/''etc.''. *Review outstanding tasks, especially those in the current phase and whether they are unclear, blocked, or insufficient. |✅ |〰️ |〰️ |✅ |〰️ |〰️ |〰️ |- !Engineering Check-In |Weekly |The engineering sub-team meet to show each other their current work, problems, and possible solutions. | *Go around the team discussing work and any issues encountered. *Discuss any forthcoming major or interesting engineering tasks and how we might accomplish them *Discuss other matters arising. |〰️ |〰️ |〰️ |✅ |✅ |〰️ |〰️ |- !Retro |Monthly |The team gets together to talk about what's working well, what's not working well, what we can improve, etc. | * Review previous action items * Kudos/Shoutouts * What things are working? * What could we improve for next time? * Any issues related to our team communication / transparency? * What is confusing? * Review new action items |✅ |✅ |✅ |✅ |✅ |✅ |✅ |} == Workstream-specific meetings == Below is the list of the '''Abstract Wikipedia workstream-specific''' '''meetings''' each week, what they should be about and who would be expected at each: {| class="wikitable" |+Abstract Wikipedia Team '''workstream-specific''' meetings plan, as of 2022-05-24 ! rowspan="3" |Meeting ! rowspan="3" |Timing ! rowspan="3" |Purpose ! rowspan="3" |Agenda ! colspan="7" |Attendance |- !Product !Design !Management ! colspan="2" |Engineering !Community !Program |- !L !L !EM !L !* !L !L |- !Experience: KIT |Weekly |Face to face time with the workstream members | * Discuss workstream blockers / risks * Emerging topics | |✅ | |〰️ |✅ | |✅ |- !Experience: Planning |Weekly |Align on weekly priorities | * Go around the room and review everyone's weekly priorities based on the tickets in Phab | |✅ | |〰️ |✅ | |✅ |- !Performance: KIT |Weekly |Face to face time with the workstream members | * Discuss workstream blockers / risks * Emerging topics |✅ | | |✅ |✅ | |✅ |- !Meta-data: KIT |Twice a week |Face to face time with the workstream members and co-working | * Discuss workstream blockers / risks * Emerging topics * Joint working on leads | | | |✅ |✅ | | |- !NLG: KIT |Weekly |Face to face time with the workstream members | * Discuss workstream blockers / risks * Emerging topics |〰️ | | |〰️ |✅ | |✅ |} Legend: *"✅" = attendance expected *"〰️" = attendance optional *"L" = Lead (mostly also only person in this sub-team) *"ED" = Engineering Director *"EM" = Engineering Manager *"*" = The whole sub-team, including ICs nahl3693usd66dz538n0m7wzuttua5g Template:InstallationNav/hi 10 1407333 5387199 5384786 2022-07-28T21:17:30Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=अनुकूलित करें}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] sdlmkn8dvx8znl79ftz9imzepw9lxw9 Growth/FAQ/en 0 1416324 5387832 5378635 2022-07-29T10:15:15Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''Welcome to the Growth team Frequently Asked Questions (FAQ).''' We hope you will find the information you need. However, if it is not the case, [[Talk:Growth|let us know]]. ''Note for translators: this page is updated regularly, which may impact your work. We are doing our best to avoid these disturbances.'' == General == {{Anchor|features}} === Which features are you working on? === * [[Special:MyLanguage/Growth/Feature summary#NH|'''Newcomer homepage''']]: a new special page, the best place for a newcomer to get started. It includes: ** [[Special:MyLanguage/Growth/Feature summary#NT|'''Newcomer tasks''']]: a feed of task suggestions that help newcomers learn to edit. Newcomers have been making [[NEWTEA|productive edits]] through this feed! [[Help:Growth/Tools/Suggested edits|Know more about this tool]]. ** '''Mentorship module''' [optional module]: each newcomers has a direct link to an experienced user. This way, they can ask questions about editing Wikipedia, less the need to find where to ask for assistance. ** '''Impact module''': the user sees how many pages views articles they edit received. * [[Special:MyLanguage/Growth/Feature summary#HP|'''Help panel''']]: a platform to provide resources to newcomers while they are editing. If they choose one of the suggested tasks on the newcomer homepage, they are guided step-by-step on the process of editing. * '''[[Growth/Understanding first day|Welcome Survey]]''': communities can know why newcomers create an account on Wikipedia. You can have a look at '''[[Special:MyLanguage/Growth/Feature summary|our features summary]]''' to know more about it. === On which wikis Growth features have been deployed? === You can find a list of wikis on our [[Special:MyLanguage/Growth/Deployment table|Deployment table]]. This page lists features activation per wiki as well. {{anchor|NEWTEA}} === Are Growth features effective? === [[NEWTEA|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in: * the probability that newcomers make their first article edit (+11.6%) * the probability that they are retained as editors * the number of edits they make during their first couple of weeks on the wiki (+22%) We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features. This deployment has been achieved in October 2021. {{anchor|translate}} === The interface is partially translated. How can I change this? === [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate Interface translations are hosted at translatewiki.net.] It takes up to one week to see new translations being deployed. Special pages names require a special process. For the following strings, [[Talk:Growth|please contact us]] directly with the translations: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. {{anchor|enable|test}} === Can I test the features? === [[Growth/Deployment table|On wikis where the Growth features are available]], and also on [https://test.wikipedia.org test.wikipedia.org], go to your [[Special:Preferences#mw-prefsection-personal|user preferences]] on one of these wikis and then: * enable the '''Help panel''' in the ''{{int|prefs-editing}}'' tab. * enable the '''Newcomer homepage''' in the ''{{int|prefs-personal}}'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''. Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work. {{anchor|get}} === How can my wiki get the features? === The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[#features|these features]], with the following conditions. As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: # Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us. # Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis. # All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis. === Do you plan to deploy the features outside of Wikipedia? === We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved. Please contact us [[Talk:Growth|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project. We are considering working with [[Growth/Communities/Wikisource|Wikisource communities]]. {{anchor|pilot|ambassador}} === Can you clarify what "Pilot wikis", "Control group wikis" and "Ambassadors" are? === '''Pilot wikis''' are wikis who have a close collaboration with the Growth team. They are involved in projects definitions and early review of the projects. They also test all prototypes first. The Growth team can contact some other wikis for some of these steps. As of {{ymd|2022|3|1}}, our pilot wikis are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. === Can I use the Growth features on mobile ? On the official apps (iOS, Android)? === Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). == Access to the features == {{anchor|ABtest}} === How can new accounts get the features? === On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where no [[A/B testing|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where an [[A/B testing|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences. Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. === How can existing accounts get the features? === On wikis [[Growth/Deployment table|where the Growth features have been deployed]], anyone can find the features [[#enable|in their Preferences]]. === I host a workshop. How can I control if my students get the features when they create an account? === It is possible to have a link parameter to control access to the features: * <code>Special:CreateAccount?geEnabled=1</code> will force Growth features at account creation * <code>Special:CreateAccount?geEnabled=0</code> will force the default experience at account creation Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[Talk:Growth|Please let us know]] if you plan to use these parameters. {{anchor|Homepage}} == Homepage == ''The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].'' === How to access the Homepage? === If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. === My email is requested, or my email is displayed at the top of the Homepage. Why? === We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[Special:MyLanguage/Help:Notifications|notifications]], like when they are mentioned by other users on wiki. The email address won't be visible by other users. Communication with other users all happen on the wiki. === The help links displayed on the homepage are not relevant. How to change them? === These links are [[#HP|the same as on the Help panel]]. An admin can change these links using <code>Special:EditGrowthConfig</code>. We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. == Suggested edits == === How does Suggested Edits work ? === ==== How topics and tasks are suggested? ==== We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. === SuggestedEdits' supervision and troubleshooting === ==== Can I monitor which articles have been edited as Suggested edits? ==== Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. ==== How to monitor which topics or which tasks need more articles? ==== Please use <code>Special:NewcomerTasksInfo</code>. ==== I don't have any task for a given combination. Is it normal? ==== Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. ==== A user uses the tools in an nonconstructive way. What can I do? ==== Overall, users make [[#NEWTEA|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: # try to understand what the use tries to do, # contact this user, explain the situation, ask them for details and guide them to a different path if it exists, # if the nonconstructive behavior persists, then block the user. If repetitive and similar nonconstructive edits are made at your wiki, [[Talk:Growth|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== Have you activated the Help panel in your preferences? If yes, [[Talk:Growth|please let us know about this issue]]. {{anchor|config}} === Suggested edits configuration === ==== How to provide more tasks for newcomers? ==== Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: {| class="wikitable" !'''Task''' !Level of difficulty !Goal of the task |- |Copyedit article |easy |fix spelling, grammar and tone |- |Add Links |easy |add links between articles |- |Update article |medium |bring existing articles up-to-date |- |Add References |medium |find sources for existing articles |- |Expand article |hard |expand stubs to become sourced articles |} Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: * Add other templates that match the definition of the task to <code>Special:EditGrowthConfig</code> on your wiki * Add maintenance templates to more articles on your wiki. Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== It is not possible at the moment. [[Talk:Growth|Please let us know]] about your potential project. === Structured tasks - Add a link === ''The following items are only valid for the wikis [[Special:MyLanguage/Growth/Deployment table|where ''Structured tasks - Add a link'' has been deployed]].'' ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== "Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates. Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too. As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article. Users have to decide if a link should be added or not added. These links are suggested by a machine. ==== Which wikis have Structured tasks - Add a link ? ==== You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. ==== What is the accuracy of Structured tasks - Add a link predictions? ==== The predictions are, on average, accurate at 70%. Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. ==== Is there a limitation to the number of articles one can edit per day? ==== We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits. As a consequence, we have setup some quality gates. As of January 2022, a user can edit up to 25 articles per day. ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. === Structured tasks - Add an image === ''This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].'' ==== What is the purpose of "Structured tasks - Add an image"? ==== Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. ==== Which rules define the work done by "Structured tasks - Add an image"? ==== We have several rules: * Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image. * Only articles where no image is displayed are taken into consideration for images addition. * Articles with an infobox but no image aren't taken into consideration for now. ==== Which types of users have been contacted to test this new concept ==== During the design process, several types users have been involved. * During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}). * To test early prototypes, we focused on the two types of editors our features target. ** people who aren't wiki editors (using UserTesting.com, in English and Spanish) ** experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia. {{anchor|HP}} == Help panel == === We want to change some links displayed on the Help panel. How to do it? === An admin can change these links using <code>Special:EditGrowthConfig</code>. We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. These links are [[#Homepage|also used on the Homepage]]. === Where does questions posted using the Help panel goes? === By default, these questions go the the local Help desk. If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: * new messages should go the newcomer's mentors, * new messages should be posted at the help desk. An admin can change this configuration using <code>Special:EditGrowthConfig</code>. === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New). As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page. {{anchor|mentoring}} == Configuration of the features == === We would like to change something on the configuration of the Growth features. How can we do it? === At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>). Of course, be sure that the change is based on a community consensus. [[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration. Sharing your feedback with us will help improve the Growth features. {{anchor|add-link-config}} === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue. Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. See [[Phab:T313642|T313642]] for plans to improve this situation. == Configuration and operation of the mentoring system == === My wiki doesn't have the Growth mentoring system. How can I set it up? === The next steps are a summary of the process. The full process is described on [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|this dedicated page]]. First, you need to check if the Growth tools are [[Growth/Deployment table|deployed at your wiki]]. If it is not yet the case, please see [[#get|how to get the features]]. Then, you have to find some other mentors to volunteer. All mentors have to sign-up on a specific page, using [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a specific syntax]]. If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. At your wiki, an admin has to add the mentor list to the configuration page (<code>Special:EditGrowthConfig</code>). === How many mentors does a wiki need? === Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. We recommend to have at least 3 mentors. === Who can be a mentor? === It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). === How mentors are assigned to newcomers? === Each new account receives a mentor randomly taken from a list of volunteers. === How many messages does a mentor receive per week? === It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. === Have you considered to assign a mentor only to people who already made some edits? === We don't know what each newcomer needs. [[Special:MyLanguage/New Editor Experiences|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. {{anchor|existing}} === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[d:Q3919128|listed on Wikidata]]. It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: '''Replace your mentoring system with the new one''' If your mentoring system hasn't much success, it could be replaced by the Growth team features. '''Have both systems working together''' You can imagine to have two roles: * Growth mentoring takes care of the newcomers basic questions, * The existing mentoring can take care of newcomers who are more involved. In this case, you might have to locally translate the interface for Growth features using your own terms. === Where can I signup as a mentor ? === If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. Your community may have defined some conditions to become a mentor. We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). {{anchor|mentorsyntax}} === How do I introduce myself as a mentor? === When you sign up to become a mentor, the following syntax must be used, with: <code>* <nowiki>[[</nowiki>User:Username<nowiki>]]</nowiki>|Description</code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|Read more about this]] {{anchor|reassign}} === Can we reassign a newcomer to a different mentor? === Yes, it is possible using <code>Special:ClaimMentee</code>. {{anchor|pause}} === As a mentor, I have to pause my mentorship activity. How can I do it? === You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. {{anchor|quit}} === As a mentor, I would like to quit mentorship. How can I do it? === You can go to <code>Special:QuitMentorship</code> and quit from there. This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. === A mentor just quit. Can we reassign all their newcomer to different mentors? === You can use <code>Special:ClaimMentee</code> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[Talk:Growth|please contact us]] directly. {{anchor|magicword}} === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === Type the magic word <code><nowiki>{{#mentor:Foo}}</nowiki></code> in a wikitext page, and preview. "Foo" has to be replaced by the username you target. This will display the name of Foo's mentor. This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. [[#reassign|If the mentor changes]], then the magic word picks the new mentor's name. You can "[[Special:MyLanguage/Help:Substitution|subst:]]" this message if needed: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Foo's mentor will then be saved as wikitext. === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === Have you updated <code>Special:EditGrowthConfig</code> with the new page name? == Interactions between mentors and newcomers == {{Anchor|questions}} === What kinds of questions do newcomers ask? === From the observations we have made, questions are mostly about basic editing. Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. Based on communities experiences, the Growth team worked [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|on a guide for mentors]] who have to reply to these questions. === Newcomers haven't replied to my messages. Why? === Two possible cases there: * Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages. * Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page. === Who can I ask if my mentor is not responding to me? === If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. === Can I ask to have a different mentor ? === You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[#reassign|make the change]]. === As a mentor, how can I monitor the newcomers assigned to me? === We are currently working on a [[Growth/Mentor dashboard|Mentor dashboard]]. It is available at all Wikipedias where [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|a list of mentors has been created and activated]]. === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === At wikis where the mentor dashboard is deployed, a new filter is available for mentors. They can monitor their mentees' activity in Watchlist and RecentChanges. For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|not listed as mentors]]. === A very experienced user is one of my mentees. Why? === For technical reasons, we assign a mentor to everyone, including experienced users. === Are all my mentees assigned to me being visible in my list of mentees? === Your list will only display users who have turned the Homepage on. b8vxvx9bcnew3ni82j26ys6swfaj82y Growth/FAQ/ja 0 1416359 5387836 5378640 2022-07-29T10:15:21Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''ようこそ、Growth チームのよくある質問 (FAQ) ページへ。''' お探しの情報が載っているでしょうか。もし、見つからないようなら、 [[Talk:Growth|ぜひこちらで質問してください]]。 ''翻訳者の皆さんへ:このページは定期的に更新していく予定で、皆さんの作業に影響すると見込まれます。なるべくご負担にならないよう配慮する所存です。'' == 全般 == {{Anchor|features}} === どの機能に取り組んでいますか? === * [[Special:MyLanguage/Growth/Feature summary#NH|'''新規参加者のホームページ''']]: 新しい特別ページとして、最初に準備を始めるのに適しています。以下の内容を含んでいます。 ** '''[[Special:MyLanguage/Growth/Feature summary#NT|編集初心者向けのタスク]]''':おすすめ編集を表示することで編集の方法を学んでもらいます。初心者の皆さんはこの表示を通じて、[[NEWTEA|意欲的に編集]]を続けました。[[Help:Growth/Tools/Suggested edits|詳細はこちらをご参照ください]]。 ** '''指導役モジュール''' [オプション設定]: 新規参加者は一人に一人ずつ経験者と直接、リンクが設定できます。この方法ならウィキペディアの編集について質問ができるので、補助をどこで受けたら良いか探さなかくてもすみます。 ** '''影響モジュール''': ページを編集した後、そのページの閲覧者数が表示されます。 * [[Special:MyLanguage/Growth/Feature summary#HP|'''ヘルプパネル''']]: 編集中の新規参加者に、便利なリソースを提示するプラットフォームです。新規参加者向けのホームページでおすすめ編集を選ぶと、編集のプロセスに沿ってステップごとにガイドが表示されます。 * '''[[Growth/Understanding first day|ようこそアンケート]]''': 新規参加者がウィキペディアにアカウント登録した動機をコミュニティに伝えます。 '''[[Special:MyLanguage/Growth/Feature summary|これら機能の概要]]'''ページを開いて、それぞれの紹介をご参照ください。 === この Growth 機能をどのウィキで実装したのですか? === [[Special:MyLanguage/Growth/Deployment table|実装予定表]]をご参照ください。展開予定の機能群も、リンクのページに週単位載せてあります。 {{anchor|NEWTEA}} === Growth 機能は使い物になりますか? === [[NEWTEA|Growth チームの分析では、これら機能の有効性が証明されています]]。手短に述べると、Growth 機能の「編集初学者向けのタスク」は次の各点で役に立ちます。 * 新規加入者が初めて記事を編集をしてみる可能性 (+11.6%) * そのまま編集者として続けていく可能性 * ウィキに登録後の半月ほどで、対象者が行った編集の回数 (+22%) また対象グループと比較したところ、編集の質にも有意な差が表れました。これに基づき、すべてのウィキペディアでGrowth 機能の採用が検討されるべきと考えます。 この展開は2021年10月にアーカイブ済みです。 {{anchor|translate}} === インターフェースはまだ翻訳が終わっていません。私にできることはありませんか? === [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] 新しく投稿した訳文の反映まで、通常は最大で1週間お待ちください。 特別ページの命名には、別途、専用の手順があります。 下記の文字列については右の宛先へ、訳文を直接、[[Talk:Growth|当チームにお知らせ願います]]: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>。 {{anchor|enable|test}} === 機能をお試ししたいんですが? === 試用するには[[Growth/Deployment table|Growth 機能を導入済みのウィキ]]に加えて[https://test.wikipedia.org test.wikipedia.org]を開き、[[Special:Preferences#mw-prefsection-personal|個人設定]]をクリックして次の設定をしてください。 * ''{{int|prefs-editing}}''タブをタップして'''ヘルプパネル'''を有効にします。(訳注=横の箱をタップして白以外の色に変え、保存ボタンをタップ。) * ''{{int|prefs-personal}}'' タブで'''新規参加者ホームページ'''を有効にします。これを有効にすると、'''新規参加者向けのタスク'''が表示されます。 ぜひ、これらのオプション機能を''両方とも'' 有効にしてください。おすすめ編集をご自分のホームページに表示するには、ヘルプパネル helpが必要だからです。 {{anchor|get}} === 私たちのウィキでも機能を使いたいんですが? === Growth 機能はウィキペディアの全言語版に導入済みです。しかしながら以下の条件にご同意の場合は、ウィキメディアがホストするその他のウィキから[[#features|これらの機能]]のリクエストを受け付けています。 詳細は[[Special:MyLanguage/Growth/Communities#Our%20focus|チームの目標]]にまとめたとおり、次の優先順位にしたがって指定のウィキと共同作業を進める予定です。 # ウィキペディアで'''[[#pilot|パイロット ウィキ]]''' (初期展開ウィキ) に設定したウィキ – 提供されたフィードバックはすべて公開します。 # ターゲット以外のウィキペディア – 機能を提供 しますが、改良点のご指摘を受け付けるかどうか未定です。 # その他のウィキメディアのプロジェクト群 – 機能を提供しても、それぞれの特性に沿った改良を優先事項に加える時間的な余力は当チームにはないと見込まれます。 === ウィキペディア以外に展開の予定は? === Growth 機能を導入したいとご希望なら、ウィキメディアのどのコミュニティも歓迎します。ただし、既製の機能を単にそのまま展開するのではなく、できるだけウィキ単位で機能をテーラーメイドしてお渡ししたいと考えています。 [[Talk:Growth|当チームのトークページに]]ご連絡をいただき、ツールをどのようにカスタム化して皆さんのウィキメディア・プロジェクトのお役に立つようにするか、ご相談させてください。 [[Growth/Communities/Wikisource|ウィキソースのコミュニティ群]]との協働を検討中です。 {{anchor|pilot|ambassador}} === 「早期導入のウィキ」と「対照グループのウィキ」「大使」とはどういう意味ですか? === '''早期導入のウィキ'''(パイロット・ウィキ)とは、これまで Growth チームと緊密に協働してきた実績のあるウィキのことです。プロジェクトの定義に始まり、プロジェクト初期のすり合わせ作業に参加してきました。さらに試作版をすべて他のウィキに先立ってテストしてあります。当チームとしてはその他のウィキにも、これらの段階へのご参加を呼びかける場合があります。 {{ymd|2022|3|1}} 時点の早期導入ウィキは以下の通りです: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}。 より多様で全体を代表するグループからデータを収集する目的で、複数のウィキをこのリストに載せています。これらを'''比較対象のウィキ群'''(コントロールグループのウィキ)としています。当該のグループは[[Special:MyLanguage/Growth/FAQ#ABtest|A/B 試験の過程]]に入っています。 {{ymd|2022|3|1}}時点で、コントロール・グループは上記の早期導入ウィキに加え、以下のウィキ群{{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}で構成しています。 <div lang="en" dir="ltr" class="mw-content-ltr"> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. </div> === モバイル機器なんですが、 I Growth 機能は使えますか? 公式のアプリでは? (iOS版、Android版) === Growth 機能は、ウィキペディアのモバイル版でもデスクトップ版でも使えるように設計してあります。ただし公式アプリには (iOS版もAndroid版も) 導入していません。 === 機能を使うには === {{anchor|ABtest}} === 新規登録したアカウントに機能はどう表示されますか? === [[Growth/Deployment table|Growth 機能を導入済み]]のウィキで[[A/B testing|A/B 試験]]を実行中ではない場合、新規登録アカウントの100%に表示します。ほぼ全ての言語版のウィキペディアでこの扱いをします。 [[Growth/Deployment table|Growth 機能を導入済み]]のウィキと、[[A/B testing|A/B 試験]]を実行中のウィキでは新規登録アカウントの80%に自動で表示します。 後者の残り20%は対照グループに加えます。そのグループは、Growth チームがそれぞれの体験を比較検討するために存在しています。 今回の A/B 試験の対象となるウィキは次のとおり。{{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}。 === 既存のアカウントにも機能は表示できますか? === [[Growth/Deployment table|Growth 機能を導入済み]]のウィキでは、[[#enable|個人設定]]に機能を載せてあります。 === ワークショップの主催者です。生徒たちが新規にアカウントを登録した場合に、これらの機能を表示させるかどうかコントロールできますか? === リンク パラメータを設定し、コントロールすることは可能です: * <code>Special:CreateAccount?geEnabled=1</code> はアカウント登録をすると必ず Growth 機能を表示 * <code>Special:CreateAccount?geEnabled=0</code> はアカウント登録をすると必ず既定の経験を表示 当然ながら、このパラメータの採用は極力、少なくする必要があります。アカウント登録と機能利用に関して Growth チームが収集するデータに影響するからです。これらのパラメータをご利用の計画は、[[Talk:Growth|当チームにご連絡ください]]。 {{anchor|Homepage}} == ホームページ == ''以下の項目は [[Growth/Deployment table|Growth 機能を導入済み]]のウィキ限定で有効です。'' === ホームページを利用するには === ウィキペディアのアカウント登録を最近したばかりなら、 ご自分の利用者名をクリックすると専用のホームページが開きます。利用者名のリンクは、ページ最上部の右の方に常に表示されています。 しばらく前からウィキペディアにアカウントがある利用者は、個人設定のページでホームページを有効にする手順に従ってください。設定を済ませてからご自分の利用者名をタップして表示させるか、またはご自分のトークページを開くと新しいタブが追加されていて、ホームページへリンクしているはずです。個人設定の項目には、ご自分の利用者名をタップするとホームページへ移動するオプションもあります。 === メールアドレスを登録しなさいと表示され、あるいは私のメールアドレスがホームページの上部に乗っています。理由は? === ほとんどの人はメールを使えると予測しています。その流れで利用者の皆さんにはメールを追加し、[[Special:MyLanguage/Help:Notifications|通知]]といって、ウィキのどこかで他に利用者から言及されたときに知らせを受け取る設定をするようお勧めしています。 またメールアドレスは登録したご本人以外には表示されません。利用者同士のやりとりはすべて、ウィキで行われます。 === ホームページにヘルプのリンクはあるけど、私向きではないんです。変更できませんか? === これらのリンクは[[#HP|新規参加者のホームページで採用しているものと同じです]]。 管理者なら <code>Special:EditGrowthConfig</code> を使ってリンクの変更ができます。 <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> == おすすめ編集 == === おすすめ編集の仕組みは ? === ==== おすすめのトピックやタスクは何を根拠にto選んでいますか? ==== <div lang="en" dir="ltr" class="mw-content-ltr"> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === SuggestedEdits' supervision and troubleshooting === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can I monitor which articles have been edited as Suggested edits? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to monitor which topics or which tasks need more articles? ==== </div> <code>Special:NewcomerTasksInfo</code> を使用してください。 <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I don't have any task for a given combination. Is it normal? ==== </div> 主題によっては記事の数がそれほど多くありません。その結果、管理用テンプレートが付いた記事数も少なく、選択肢が減る傾向があります。 ==== 特定の利用者がツールを悪用しているみたいです。何か対策した方が良いですか? ==== 全体的に見ると、利用者の皆さんは Growth 機能を(建設的な)[[#NEWTEA|ほかの人に役に立つ編集]]に使っているようです。それでもなお、ガイダンスを破る利用者を見かけるでしょうし、人によっては不適切なツールの使い方をする可能性もあります。 こういう場合は、建設的でない編集を見つけたときに適用する、通常の手順がもっとも適しているはずです。 # その利用がほんとうは何をしたいのか、想像力を駆使してみて、 # 相手にメッセージを送って客観的にどんな状況に見えるか説明することと、困っている点を返信で詳しく説明してもらい、もし別のやり方があるならガイドしてみましょう。 # それでも相手が不正なやり方を変えないのであれば、その利用者はブロックしてください。 皆さんがいつも活動するウィキで繰り返し同様の不正な編集が重なる場合は、[[Talk:Growth|私たちに連絡をお願いします]]。皆さんからのメッセージには不正な編集の具体例として、差分のリンクを加えてもらうと、Growth チームで状況を分析し解決策を 検討するのに役立ちます。 ==== 個人設定を編集して、私用のホームページを有効にしました。ホームページから記事を選んで改善しようと思ったのに、記事にちっともガイドが表示されません。 ==== 個人設定でヘルプパネルも有効にしてありますか? 有効なら[[Talk:Growth|問題の細かい点をついて教えてもらえませんか]]。 {{anchor|config}} === おすすめ編集の設定 === ==== 新規参加者にもっとタスクを提供する方法は? ==== 新規参加者には5段階の管理タスクをなってみるように呼びかけ、それぞれ難易度順に分かれています。 {| class="wikitable" !'''タスク名''' !難易度 !タスクの目的 |- |記事の文章を編集 |簡単 |綴り、用字や用語、「てにをは」や文法の修正 |- |リンクの追加 |簡単 |リンクを追加して記事と記事を結ぶ |- |記事を更新 |中難度 |既存の記事の情報を更新する |- |出典の追加 |中難度 |既存の記事に典拠を見つける |- |本文の加筆 |高難度 |スタブ記事を出典を追加して充実させる |} タスクの一覧は管理用テンプレートに基づいて作成されます。表示するタスクを増やすには、次の操作をしてください。 * タスクの定義にしたがい、皆さんのウィキの<code>Special:EditGrowthConfig</code>に他のテンプレートを追加します。 * 管理用テンプレートを皆さんのウィキのさまざまな記事ページに追加します。 ときには、経験者の編集者がまとめて作業しているために、簡単なタスクが残っていない場合があります。経験を積んだ編集者の皆さんには、難易度が上のタスクへと移行するようにお勧めし、ぜひ簡単なタスクは新規参加者が初めて取り組めるようにしていただけないでしょうか。 ==== 今までにないタスクを推薦したり、現状のタスクをもっと難しくしたり、提案は聞いてもらえますか? ==== 残念ながら現在はまだ実現は無理です。みなさんがどんなプロジェクトの構想を持っているのか、[[Talk:Growth|話を聞かせてください]]。 === 構造化タスク:リンクの追加 === ''以下の項目は [[Special:MyLanguage/Growth/Deployment table|''構造化タスク - リンクを追加'' を導入済み]]のウィキ限定で有効です。'' ==== ふつうの「リンクを追加」と、「構造化タスク- リンクを追加」に違いはありますか? ==== <span lang="en" dir="ltr" class="mw-content-ltr">"Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users have to decide if a link should be added or not added. These links are suggested by a machine.</span> ==== 構造化タスク - リンクの追加 が利用できるウィキとは? ==== <div lang="en" dir="ltr" class="mw-content-ltr"> You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. </div> ==== 構造化タスク - リンク追加の予測精度は? ==== <div lang="en" dir="ltr" class="mw-content-ltr"> The predictions are, on average, accurate at 70%. </div> 予測の精度をもっと上げられないかと質問を受けています。可能ではあるのですが、そうするとタスクの面白さを損なってしまいます。新規参加者の皆さんに呼びかけたいのは、おすすめのリンクが閲覧者にとって興味を引かれるか(または引かれないか)その理由まで考慮してから、リンクを選択することです。もし、ぴったりのリンクばかり提示されたのでは、ただの単純作業になってしまい、面白さは減ってしまわないでしょうか。 <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> === 構造化タスク:画像を追加 === ''<span lang="en" dir="ltr" class="mw-content-ltr">This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].</span>'' ==== 作業の「構造化タスク - 画像の追加」にはどんな目的があるのですか? ==== <div lang="en" dir="ltr" class="mw-content-ltr"> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. </div> ==== 作業のうち「構造化タスク - 画像を追加」にはどのルールが適用されますか? ==== ルールは複数あります。 * <span lang="en" dir="ltr" class="mw-content-ltr">Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Only articles where no image is displayed are taken into consideration for images addition.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Articles with an infobox but no image aren't taken into consideration for now.</span> ==== この新しいコンセプト作りについて相談をした利用者のタイプとは ==== <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">people who aren't wiki editors (using UserTesting.com, in English and Spanish)</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia.</span> {{anchor|HP}} == ヘルプ パネル == === 私たちのコミュニティでは、ヘルプパネルにあるリンクを変更したいです。リクエストの方法は? === 管理者なら <code>Special:EditGrowthConfig</code> を使ってリンクの変更ができます。 この作業は当チームで補佐ができます。要望を[[Talk:Growth|当チームに知らせて]]ください。コミュニティで合意形成をしたページのリンクを書き込むようお願いします。 これらのリンクは[[#Homepage|新規参加者のホームページでも採用しています]]。 <div lang="en" dir="ltr" class="mw-content-ltr"> === Where does questions posted using the Help panel goes? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, these questions go the the local Help desk. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should go the newcomer's mentors,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should be posted at the help desk.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change this configuration using <code>Special:EditGrowthConfig</code>. </div> === 私たちのコミュニティでは、ヘルプパネルに投稿された質問はすべて、ヘルプデスクが担当することに決めてあります。ところがページによっては、この仕組みが働きません。なぜ? === これまでの経過観察によると、編集初学者は自分担当の指導役に連絡を取ろうとして、自分自身のトークページにメッセージを投稿する場合があります(つまり、利用者:初学者は利用者:経験者に連絡がしたいので利用者_トーク:初学者に投稿する状況。) そういう成り行きに対応するため、利用者が自分自身のトークページでヘルプパネルを使った場合、担当の指導役に連絡を代行する仕組みにしました。 {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> == 指導役システムの環境設定と操作 == === 私のウィキにはGrowth 指導役システムがまだありません。設定する方法は? === 以下は、その手順の説明をまとめてあります。詳しい手順は[[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|こちらの専用ページをご参照ください]]。 まず最初に、Growth ツール類が[[Growth/Deployment table|ご利用のウィキに導入されているかどうか]]確認します。もし未導入の場合は、[[#get|機能を利用可能にする方法]]をご参照ください。 その場合は、ご自分以外のボランティアで参加してくれる指導役を見つける必要が出てきます。 指導役は全員、特別ページで自薦する必要があり、[[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a 専用の構文]]が使われます。 皆さんのコミュニティで Growth 機能を利用し、すでに指導役プログラムを立て上げているなら、ウィキのページ名は[[D:Q14339834|この Wikidata 項目]]配下に登録されているはずです。 ご利用のウィキで管理者に依頼して、指導役名簿を環境設定ページ (<code>Special:EditGrowthConfig</code>) へ追加してもらってください。 === ウィキに必要な指導役は何人 ですか? === これまでの観察に基づき、皆さんのウィキで月間に増える新規参加者500人単位に対して指導役を1名置くように推奨されます。一例として、月間の新規アカウントの登録が2,500 件なら、5名以上の指導役が必要です。 最低でも3名を推奨しています。 <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> ===指導役にはどのように担当の新規参加者が決まりますか? === ボランティアの名簿から、新規参加者の担当指導役がアトランダムに選出されます。 === 週単位で指導役が受け取るメッセージはどれくらいですか? === その判断は簡単ではありません。新規参加者の意欲にもよりますし、ウィキごとの指導役の登録数にも左右されます。 経過観察によると、週に届くメッセージは平均0件から6件で、週によって増減が見られます。 === 指導役が担当する相手は、すでに編集をしたことがある人に絞り込むという案は検討しなかったのですか? === 新規参加者のそれぞれのニーズは私たちには予測できません。 [[Special:MyLanguage/New Editor Experiences|こちらの調査では]]、一定数の新規利用者は最初の編集をする前に、実行しても大丈夫という権利の確信がないと困ると示しています。その他の利用者は編集を始める前に、もっと方法や手順の情報を読みたいかもしれません。この流れから、新規アカウントごとに担当の指導役を1名ずつ配置することにしました。連絡するかどうかは、新規参加者の自由です。 {{anchor|existing}} === うちのウィキには既に指導役プロジェクトがあります。Growth の指導役システムへの移行が必要ですか? === 皆さんの指導役システムとは経験を積んだ利用者の一覧で、意欲があり特定の主題に関して特定の質問がしたい新規参加者なら、補佐しても良いと考える人たちではないかと思います。ほとんどの指導役名は[[d:Q3919128|Wikidataに登録されます]]。 Growth 指導役機能をどのように統合するか、最適な方法は皆さんのコミュニティで決定してください。選択肢によって下記が含まれます。 '''既存の指導役システムを新規システムと置換する''' 既存の指導役システムがあまり成功していない場合、Growth チーム機能に置換する選択肢があります。 '''両方のシステムをどちらも有効に設定''' 予測していただきたいのは次の2つの役割です。 * Growth 指導役システムは新規参加者の基本的な質問に対応でき、 * 既存の指導役システムは、新規参加者で意欲の高い人を補佐の対象にできます。 その場合、Growth 機能についてローカルのコミュニティの皆さん自身の言葉で、インターフェースを翻訳していただく必要があると見込まれます。 === 指導役に立候補するには ? === 皆さんのコミュニティでGrowth 機能を利用して指導役システムを立ち上げた場合には、皆さんのウィキのページは[[D:Q14339834|この Wikidata 項目]]配下に表示されるはずです。 皆さんのコミュニティで指導役になる条件をいくつか決めているかもしれません。 <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> ウィキの編集に慣れていることが求められます (500回超で登録後90日が経過)。 {{anchor|mentorsyntax}} === 指導役として自己紹介するには? === 指導役に自薦するときは、 下記の構文を使用する必要があり、具体的な項目は以下のとおりです。 <code>* <nowiki>[[</nowiki>User:利用者名<nowiki>]]</nowiki>|説明</code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|これについて詳しく読む]] {{anchor|reassign}} === 特定の新規参加者の指導役を変更できますか? === もちろん、<code>Special:ClaimMentee</code>を使うと可能です。 {{anchor|pause}} === 指導役を引き受けましたが、しばらくお休みする必要があります。手続きはどうしますか? === [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] を開き、お休みの申請をしてください。 {{anchor|quit}} === 指導役だったのですが、この立場を辞退したいです。どんな手順を取ればよいですか? === <code>Special:QuitMentorship</code> を開いて、辞退の手続きをお願いします。 このリンクは、お使いの[[Special:MyLanguage/Growth/Mentor dashboard|指導役ダッシュボード]]に置いてありますのでご利用ください。 === ある指導役がさっき、辞退してしまいました。その人が担当していた新規参加者を全員、他の指導役に割り振っても良いですか? === <code>Special:ClaimMentee</code> を使うと、活動中の指導相手を指名できますが、特定の担当指導役に割り当てた編集初学者全員の担当変更をする場合は、直接、[[Talk:Growth|当チームにご連絡をお願いします]]。 {{anchor|magicword}} === 特定の利用者の指導役の名前を表示するには? / ようこそページに指導役の名前を追加する方法は? === 特定のページをウィキテキスト表示にして、マジックワードの <code><nowiki>{{#mentor:Foo}}</nowiki></code> を記入し、プレビューします。「Foo」は対象の利用者の名前に書き換えます。するとFooさんの指導役の名前が表示されるはずです。 この[[:ja:マジックワード]]は次のテンプレートで使用できます。ようこそメッセージ、利用者のトークページへのメッセージ、利用者ボックスその他。 [[#reassign|指導役が交代すると]]、マジックワードが新しい指導役の名前を抽出します。 必要ならこのメッセージを「[[Special:MyLanguage/Help:Substitution|subst:]]」してください: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>。Fooさんの指導役の名前がウィキテキスト形式で保存されます。 === 指導役名簿の題名を変更 したところ、新規参加者から質問がぜんぜん来なくなりました。修正方法は? === もしかして <code>Special:EditGrowthConfig</code> に新しい名称を付けていませんか? == 指導役と新規参加者のやりとり == {{Anchor|questions}} === 新規参加者からは、どんな質問が来そうですか? === これまでの経過観察によると、質問はほぼ編集の基本に集中していました。 中には社交的な呼びかけもあり(「こんにちは」など)、その場合は本当に誰か応答するのか、試しにツールを使ってみた利用者の書き込みでした。そういうあいさつにもぜひ返信をお願いしたいのですが、そこから交流が始まるのではないかとよそくされるからです。 コミュニティの経験の蓄積に基づき、Growth チームはそれらの質問に回答するべき人を対象に、[[Special:MyLanguage/Growth/Communities/How to interact with newcomers|指導役用の指針]]を作りました。 === 新規参加者にメッセージを送ったのに、返事が来ません。どんな理由がありそう? === 可能性があるのは2種類のケースです。 * 返答のときに、利用者名に言及してありましたか? 新規参加者はまだウォッチリストその他、変更を監視するツールの使い方を覚えていません。ホームページには指導役のトークページを再訪する手順をは書いてあるのですが、相手に言及するのがいちばん効果的な方法です。新規参加者に自分宛の返信が届いたと知らせるには、言及(ping)なら通知を発信するので最適です。 * 新規参加者は毎日、ウィキをチェックしているわけではありません。返信まで数日かかる場合や、何週間もしてから返信する利用者もいることでしょう。指導役の皆さん、ご自分のトークページを過去ログ化するときは、この点にご留意ください。 === 担当の指導役がちっとも 返答してくれないときは、誰に相談すれば良いですか? === もし皆さんの担当指導役が返事をくれないなら、質問をローカルのヘルプデスクに投稿するか、または他の経験が長い利用者に質問してみてください。 === 指導役を交代してもらえますか? === ご自分で他の指導役に連絡を取り、担当になってもらえないかお願いしてください。もしお互いが納得するなら、指導役が[[#reassign|変更手続きをします]]。 === 指導役になったので、担当の新規参加者をどう補佐したら良いですか? === 現在、[[Growth/Mentor dashboard|指導役用ダッシュボード]]を開発中です。 [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|指導者一覧を作成して有効にした]]ウィキペディアではすべて、利用可能です。 === 指導相手の編集活動を見るのに、「最近の更新」または私専用の「ウォッチリスト」にフィルタをかけて抽出できませんか? === 指導者ダッシュボードを展開済みのウィキなら、指導役向けに新しいフィルタが導入されています。 <span lang="en" dir="ltr" class="mw-content-ltr">They can monitor their mentees' activity in Watchlist and RecentChanges.</span> 個人情報のため、このフィルタは担当の指導役以外には表示されません。すなわち、指導役ごとに担当する利用者のみ抽出するからです。また、[[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|指導役として登録していない]]人に対しても表示されない仕組みです。 === かなり経験が長い人まで指導相手に混じっていますが理由は? === 技術的な制約があり、たとえ経験者でも除外せずに指導役を割り当てています。 === 指導相手の皆さんは全員、私専用の一覧に載っていますか? === 個人用ホームページを有効にした人以外は含まれません。 dzdkxp7pvd685lx7uf600jthr75zvkq Growth/FAQ/tr 0 1416451 5387841 5378645 2022-07-29T10:15:30Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''<span lang="en" dir="ltr" class="mw-content-ltr">Welcome to the Growth team Frequently Asked Questions (FAQ).</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">We hope you will find the information you need. However, if it is not the case, [[Talk:Growth|let us know]].</span> ''<span lang="en" dir="ltr" class="mw-content-ltr">Note for translators: this page is updated regularly, which may impact your work. We are doing our best to avoid these disturbances.</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> == General == </div> {{Anchor|features}} === Hangi özellikler üzerinde çalışıyorsunuz? === * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NH|'''Newcomer homepage''']]: a new special page, the best place for a newcomer to get started. It includes:</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NT|'''Newcomer tasks''']]: a feed of task suggestions that help newcomers learn to edit. Newcomers have been making [[NEWTEA|productive edits]] through this feed! [[Help:Growth/Tools/Suggested edits|Know more about this tool]].</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Mentorship module''' [optional module]: each newcomers has a direct link to an experienced user. This way, they can ask questions about editing Wikipedia, less the need to find where to ask for assistance.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Impact module''': the user sees how many pages views articles they edit received.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#HP|'''Help panel''']]: a platform to provide resources to newcomers while they are editing. If they choose one of the suggested tasks on the newcomer homepage, they are guided step-by-step on the process of editing.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''[[Growth/Understanding first day|Welcome Survey]]''': communities can know why newcomers create an account on Wikipedia.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You can have a look at '''[[Special:MyLanguage/Growth/Feature summary|our features summary]]''' to know more about it. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === On which wikis Growth features have been deployed? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find a list of wikis on our [[Special:MyLanguage/Growth/Deployment table|Deployment table]]. This page lists features activation per wiki as well. </div> {{anchor|NEWTEA}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Are Growth features effective? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[NEWTEA|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that newcomers make their first article edit (+11.6%)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that they are retained as editors</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the number of edits they make during their first couple of weeks on the wiki (+22%)</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This deployment has been achieved in October 2021.</span> {{anchor|translate}} <div lang="en" dir="ltr" class="mw-content-ltr"> === The interface is partially translated. How can I change this? === </div> [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] <div lang="en" dir="ltr" class="mw-content-ltr"> It takes up to one week to see new translations being deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Special pages names require a special process. For the following strings, [[Talk:Growth|please contact us]] directly with the translations: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. </div> {{anchor|enable|test}} === Özellikleri test edebilir miyim? === <div lang="en" dir="ltr" class="mw-content-ltr"> [[Growth/Deployment table|On wikis where the Growth features are available]], and also on [https://test.wikipedia.org test.wikipedia.org], go to your [[Special:Preferences#mw-prefsection-personal|user preferences]] on one of these wikis and then: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Help panel''' in the ''{{int|prefs-editing}}'' tab.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Newcomer homepage''' in the ''{{int|prefs-personal}}'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work.</span> {{anchor|get}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can my wiki get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[#features|these features]], with the following conditions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Do you plan to deploy the features outside of Wikipedia? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Please contact us [[Talk:Growth|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> We are considering working with [[Growth/Communities/Wikisource|Wikisource communities]]. </div> {{anchor|pilot|ambassador}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can you clarify what "Pilot wikis", "Control group wikis" and "Ambassadors" are? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''Pilot wikis''' are wikis who have a close collaboration with the Growth team. They are involved in projects definitions and early review of the projects. They also test all prototypes first. The Growth team can contact some other wikis for some of these steps. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, our pilot wikis are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I use the Growth features on mobile ? On the official apps (iOS, Android)? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). </div> == Özelliklere erişim == {{anchor|ABtest}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can new accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where no [[A/B testing|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where an [[A/B testing|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How can existing accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], anyone can find the features [[#enable|in their Preferences]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === I host a workshop. How can I control if my students get the features when they create an account? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is possible to have a link parameter to control access to the features: </div> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=1</code> will force Growth features at account creation</span> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=0</code> will force the default experience at account creation</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[Talk:Growth|Please let us know]] if you plan to use these parameters. </div> {{anchor|Homepage}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Homepage == </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> === How to access the Homepage? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My email is requested, or my email is displayed at the top of the Homepage. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[Special:MyLanguage/Help:Notifications|notifications]], like when they are mentioned by other users on wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The email address won't be visible by other users. Communication with other users all happen on the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === The help links displayed on the homepage are not relevant. How to change them? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#HP|the same as on the Help panel]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Suggested edits == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How does Suggested Edits work ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How topics and tasks are suggested? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === SuggestedEdits' supervision and troubleshooting === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can I monitor which articles have been edited as Suggested edits? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to monitor which topics or which tasks need more articles? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please use <code>Special:NewcomerTasksInfo</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I don't have any task for a given combination. Is it normal? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== A user uses the tools in an nonconstructive way. What can I do? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Overall, users make [[#NEWTEA|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">try to understand what the use tries to do,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">contact this user, explain the situation, ask them for details and guide them to a different path if it exists,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">if the nonconstructive behavior persists, then block the user.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If repetitive and similar nonconstructive edits are made at your wiki, [[Talk:Growth|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you activated the Help panel in your preferences? If yes, [[Talk:Growth|please let us know about this issue]]. </div> {{anchor|config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Suggested edits configuration === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to provide more tasks for newcomers? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: </div> {| class="wikitable" !'''<span lang="en" dir="ltr" class="mw-content-ltr">Task</span>''' !<span lang="en" dir="ltr" class="mw-content-ltr">Level of difficulty</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Goal of the task</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Copyedit article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">fix spelling, grammar and tone</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add Links</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">add links between articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Update article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">bring existing articles up-to-date</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add References</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">find sources for existing articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Expand article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">hard</span> |<span lang="en" dir="ltr" class="mw-content-ltr">expand stubs to become sourced articles</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Add other templates that match the definition of the task to <code>Special:EditGrowthConfig</code> on your wiki</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add maintenance templates to more articles on your wiki.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is not possible at the moment. [[Talk:Growth|Please let us know]] about your potential project. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add a link === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Special:MyLanguage/Growth/Deployment table|where ''Structured tasks - Add a link'' has been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">"Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users have to decide if a link should be added or not added. These links are suggested by a machine.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which wikis have Structured tasks - Add a link ? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the accuracy of Structured tasks - Add a link predictions? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The predictions are, on average, accurate at 70%. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add an image === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the purpose of "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which rules define the work done by "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have several rules: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Only articles where no image is displayed are taken into consideration for images addition.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Articles with an infobox but no image aren't taken into consideration for now.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which types of users have been contacted to test this new concept ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">people who aren't wiki editors (using UserTesting.com, in English and Spanish)</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia.</span> {{anchor|HP}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Help panel == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We want to change some links displayed on the Help panel. How to do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#Homepage|also used on the Homepage]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where does questions posted using the Help panel goes? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, these questions go the the local Help desk. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should go the newcomer's mentors,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should be posted at the help desk.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change this configuration using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page.</span> {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration and operation of the mentoring system == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My wiki doesn't have the Growth mentoring system. How can I set it up? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The next steps are a summary of the process. The full process is described on [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|this dedicated page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, you need to check if the Growth tools are [[Growth/Deployment table|deployed at your wiki]]. If it is not yet the case, please see [[#get|how to get the features]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Then, you have to find some other mentors to volunteer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All mentors have to sign-up on a specific page, using [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a specific syntax]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> At your wiki, an admin has to add the mentor list to the configuration page (<code>Special:EditGrowthConfig</code>). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many mentors does a wiki need? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We recommend to have at least 3 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How mentors are assigned to newcomers? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Each new account receives a mentor randomly taken from a list of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many messages does a mentor receive per week? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Have you considered to assign a mentor only to people who already made some edits? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We don't know what each newcomer needs. [[Special:MyLanguage/New Editor Experiences|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. </div> {{anchor|existing}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[d:Q3919128|listed on Wikidata]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: </div> '''<span lang="en" dir="ltr" class="mw-content-ltr">Replace your mentoring system with the new one</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">If your mentoring system hasn't much success, it could be replaced by the Growth team features.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">Have both systems working together</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">You can imagine to have two roles:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Growth mentoring takes care of the newcomers basic questions,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The existing mentoring can take care of newcomers who are more involved.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> In this case, you might have to locally translate the interface for Growth features using your own terms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where can I signup as a mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Your community may have defined some conditions to become a mentor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How do I introduce myself as a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you sign up to become a mentor, the following syntax must be used, with: </div> <code>* <nowiki>[[</nowiki><span lang="en" dir="ltr" class="mw-content-ltr">User:Username</span><nowiki>]]</nowiki>|<span lang="en" dir="ltr" class="mw-content-ltr">Description</span></code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|<span lang="en" dir="ltr" class="mw-content-ltr">Read more about this</span>]] {{anchor|reassign}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can we reassign a newcomer to a different mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes, it is possible using <code>Special:ClaimMentee</code>. </div> {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === A mentor just quit. Can we reassign all their newcomer to different mentors? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can use <code>Special:ClaimMentee</code> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[Talk:Growth|please contact us]] directly. </div> {{anchor|magicword}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Type the magic word <code><nowiki>{{#mentor:Foo}}</nowiki></code> in a wikitext page, and preview. "Foo" has to be replaced by the username you target. This will display the name of Foo's mentor. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[#reassign|If the mentor changes]], then the magic word picks the new mentor's name. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can "[[Special:MyLanguage/Help:Substitution|subst:]]" this message if needed: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Foo's mentor will then be saved as wikitext. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you updated <code>Special:EditGrowthConfig</code> with the new page name? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Interactions between mentors and newcomers == </div> {{Anchor|questions}} <div lang="en" dir="ltr" class="mw-content-ltr"> === What kinds of questions do newcomers ask? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> From the observations we have made, questions are mostly about basic editing. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on communities experiences, the Growth team worked [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|on a guide for mentors]] who have to reply to these questions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Newcomers haven't replied to my messages. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Two possible cases there: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can I ask if my mentor is not responding to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I ask to have a different mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[#reassign|make the change]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, how can I monitor the newcomers assigned to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are currently working on a [[Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is available at all Wikipedias where [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|a list of mentors has been created and activated]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At wikis where the mentor dashboard is deployed, a new filter is available for mentors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They can monitor their mentees' activity in Watchlist and RecentChanges.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|not listed as mentors]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> 55ndqlsa6qaon1u4yy5jvzav87ut9a4 Growth/FAQ/pl 0 1417252 5387838 5378642 2022-07-29T10:15:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''Witamy na liście najczęstszych pytań dotyczących narzędzi Growth.''' Mamy nadzieję, że znajdziesz tu potrzebne informacje. Jeżeli tak nie będzie, [[Talk:Growth|napisz do nas]]. ''Uwaga dla tłumaczy: ta strona często się zmienia, co może wpłynąć na wasza pracę. Staramy się to robić tak, by było to jak najmniej uciążliwe.'' == Ogólne == {{Anchor|features}} === Nad jakimi funkcjami pracujecie? === * [[Special:MyLanguage/Growth/Feature summary#NH|'''Strona domowa nowicjusza''']]: nowa strona specjalna mająca być najlepszym miejscem startu nowicjusza. Zawiera ona: ** [[Special:MyLanguage/Growth/Feature summary#NT|'''Zadania dla nowicjuszy''']]: zbiór proponowanych zadań, które pomogą nowicjuszom w nauce edytowania. Dzięki temu nowicjusz wykonują [[NEWTEA|produktywne zmiany]]! [[Help:Growth/Tools/Suggested edits|Dowiedz się więcej o tym narzędziu]]. ** '''Moduł wikiprzewodników''' [moduł dodatkowy]: każdemu nowicjuszowi prezentowany jest link do profilu doświadczonego użytkownika. W ten sposób mogą zadawać pytania na temat edytowania Wikipedii, bez konieczności zastanawiania się, gdzie szukać wsparcia. ** '''Moduł pokazywania wpływu''': użytkownik może zobaczyć, jak często oglądano artykuły, które edytował. * [[Special:MyLanguage/Growth/Feature summary#HP|'''Panel pomocy''']]: platforma wskazująca nowicjuszom zasoby podczas edytowania. Jeżeli wybiorą jedno z sugerowanych zadań ze strony dla nowicjusza, są oni prowadzeni krok po kroku przez proces edytowania. * '''[[Growth/Understanding first day|Ankieta powitalna]]''': społeczność może dowiedzieć się, dlaczego nowy użytkownik utworzył konto na Wikipedii. Możesz spojrzeć na '''[[Special:MyLanguage/Growth/Feature summary|przegląd naszych narzędzi]]''' aby dowiedzieć się o nich więcej. === Na jakich wiki wdrożono narzędzia Growth? === Listę wiki znajdziesz w [[Special:MyLanguage/Growth/Deployment table|tej tabeli]]. Widoczne są tam też włączenia poszczególnych funkcji. {{anchor|NEWTEA}} === Czy narzędzia Growth są skuteczne? === [[NEWTEA|Zespół Growth dowiódł efektywności tych narzędzi]]. W skrócie; funkcja Growth "zadania dla nowicjuszy" prowadzi do wzrostu: * prawdopodobieństwa, że nowy użytkownik dokona swojej pierwszej edycji artykułu (+11.6%) * prawdopodobieństwa, że pozostanie dalej by edytować * liczby edycji, jaką wykonają przez pierwsze kilka tygodni na wiki (+22%) Wywnioskowaliśmy też, że jakość ich edycji jest porównywana do grupy kontrolnej. Na podstawie tych wyników uważamy, że każda wersja językowa Wikipedii powinna włączyć te funkcje. Zostało to więc zrobione w październiku 2021. {{anchor|translate}} === Interfejs przetłumaczony jest tylko częściowo. Jak mogę to zmienić? === [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] Nowe tłumaczenia zostaną wprowadzone w ciągu tygodnia. Wprowadzenie przetłumaczonych nazw stron specjalnych wymaga przejścia specjalnej procedury. Aby przetłumaczyć te ciągi, [[Talk:Growth|skontaktuj się z nami]] przesyłając tłumaczenia: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. {{anchor|enable|test}} === Czy mogę przetestować te funkcje? === [[Growth/Deployment table|Na wiki gdzie dostępne są narzędzia Growth]] oraz na [https://test.wikipedia.org test.wikipedia.org], przejdź do [[Special:Preferences#mw-prefsection-personal|preferencji]], a następnie: * włącz '''Panel pomocy''' w zakładce ''{{int|prefs-editing}}''. * włącz '''Stronę domowa dla nowicjuszy''' w zakładce ''{{int|prefs-personal}}''. Włączenie strony domowej dla nowicjuszy da także dostęp do '''Zadań dla nowicjuszy'''. Nie zapomnij aby były włączone ''obie'' funkcje: Sugerowane edycje dostępne na stronie domowej dla nowicjuszy wymagają do działania włączonego Panelu pomocy. {{anchor|get}} === Jak mogę wprowadzić te funkcje na moją wiki? === Narzędzia Growth dostępne są we wszystkich wersjach językowych Wikipedii. Jednak każda wiki utrzymywana przez Wikimedia może poprosić o włączenie [[#features|tych funkcji]] na poniższych zasadach. <div lang="en" dir="ltr" class="mw-content-ltr"> As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</span> === Czy planujecie wdrożyć te narzędzia na wiki innych niż Wikipedia? === <span lang="en" dir="ltr" class="mw-content-ltr">We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</span> [[Talk:Growth|Skontaktuj się z nami]] aby omówić jak zmodyfikować nasze narzędzia aby współgrały z innym projektem Wikimedia. Rozważamy współpracę z [[Growth/Communities/Wikisource|Wikiźródłami]]. {{anchor|pilot|ambassador}} === Co to są "Pilotażowe wiki", "Wiki z grupy kontrolnej" i "Ambasadorzy"? === '''Wiki pilotażowe''' to wiki blisko współpracujące z zespołem Growth. Są one zaangażowane w określaniu projektów i wczesnym przeglądzie. Są też pierwszymi testerami prototypów. Zespół Growth może kontaktować się też z innymi wiki celem przeprowadzenia niektórych kroków. Na dzień {{ymd|2022|3|1}}, wiki pilotażowe to: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> Aby komunikacja z wiki pilotażowymi była sprawna, zespół Growth zatrudnia '''ambasadorów'''. Ambasadorzy rekrutowani są ze społeczności. Ambasadorzy mogą też kontaktować się z wiki z grupy kontrolnej celem podobnej współpracy co z pilotażowymi wiki. Ambasadorzy ułatwiają komunikację między zespołem Growth a społecznością. Pomagają zespołowi Growth zrozumieć zróżnicowanie naszych wiki i pomagają społecznościom w korzystaniu z narzędzi Growth i witaniu nowicjuszy. === Czy mogę korzystać z narzędzi Growth na urządzeniach mobilnych? Na oficjalnych aplikacjach (iOS, Android)? === Narzędzia Growth zostały stworzone tak, aby działały zarówno w wersji Wikipedii na komputery stacjonarne jak i mobilnej. Nie są dostępne w oficjalnych aplikacjach (iOS, Android). == Dostęp do tych narzędzi == {{anchor|ABtest}} === Jak nowe konta otrzymują te narzędzia? === Na wiki [[Growth/Deployment table|gdzie wdrożono narzędzia Growth]] i gdzie wyłączono [[A/B testing|testowanie A/B]], 100% nowych kont otrzyma te narzędzia. To prawie wszystkie wersje językowe Wikipedii. Na wiki [[Growth/Deployment table|gdzie wdrożono narzędzia Growth]] i gdzie włączono [[A/B testing|testowanie A/B]], 80% nowych kont otrzyma te narzędzia automatycznie; pozostałe 20% będzie częścią grupy kontrolnej. Zespół Growth może porównać doświadczenia tych grup. <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> === Jak dotychczasowe konta otrzymują te narzędzia? === Na wiki [[Growth/Deployment table|gdzie wdrożono narzędzia Growth]] każdy może je znaleźć [[#enable|w swoich Preferencjach]]. === Przeprowadzam warsztat. Jak mogę ustawić, aby jego uczestnicy mieli włączone te funkcje po utworzeniu konta? === Dodaj parametr do linku: * <code>Special:CreateAccount?geEnabled=1</code> wymusi włączenie narzędzi Growth podczas tworzenia konta * <code>Special:CreateAccount?geEnabled=0</code> wymusi domyślny sposób przydzielania narzędzi Growth podczas tworzenia konta Najlepiej, jeżeli korzystanie z tego parametru będzie ograniczane. Wpływa na dane zbierane przez zespół Growth dotyczące tworzenia kont i użycia tych funkcji. [[Talk:Growth|Powiadom nas]] jeżeli planujesz korzystać z tych parametrów. {{anchor|Homepage}} == Strona główna dla nowicjuszy == ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].</span>'' === Jak wejść na stronę startową dla nowicjuszy? === Jeżeli twoje konto zostało utworzone ostatnio, strona domowa jest dostępna po kliknięciu na nazwę użytkownika. To link dostępny po prawej na górze każdej strony. Jeżeli już masz od dawna konto na Wikipedii, włącz stronę domową dla nowicjuszy w swoich preferencjach. Gdy to zrobisz, strona domowa jest dostępna po kliknięciu na nazwę użytkownika lub link do Twojej dyskusji, a następnie kliknięciu zakładki "strona domowa". Możesz tez włączyć opcję, aby kliknięcie na nazwę użytkownika od razu prowadziło do strony domowej. === Dlaczego jestem proszony o podanie mojego adresu e-mail i dlaczego jest on wyświetlany na górze strony domowej? === Zakładamy, że większość ludzi umie korzystać z e-mail. Zachęcamy więc, aby użytkownicy podali swój adres e-mail aby otrzymywali [[Special:MyLanguage/Help:Notifications|powiadomienia]], na przykład gdy zostaną wywołani przez innych użytkowników wiki. Adres e-mail nie będzie widoczny przez innych użytkowników. Cała komunikacja z innymi użytkownikami odbywa się an wiki. === Linki do stron pomocy wyświetlane na stronie domowej nie są trafne. Jak je zmienić? === Te linki to te same co [[#HP|w panelu pomocy]]. Administratorzy mogą zmieniać te linki poprzez stronę <code>Special:EditGrowthConfig</code>. Możemy pomóc podczas tej czynności. [[Talk:Growth|Skontaktuj się z nami]] opisując swoją potrzebę i dołącz link do dyskusji w społeczności, w której podjęto decyzję. == Sugerowane edycje == === Jak działają Sugerowane edycje? === ==== Jak dobierane są sugerowane tematy i zadania? ==== Proponowane są artykuły, które są na wybrane tematy i w których należy wykonać wybrane rodzaje zadań. Jeżeli wybierzesz tylko rodzaj zadania, wybór zostanie dokonany spośród wszystkich artykułów oznaczonych szablonem związanym z danym typem zadania. Na przykład, jeżeli nie wybierzesz tematów i wybierzesz zadanie Redakcja, zostanie wybranych 200 artykułów na dowolny temat, w których została zgłoszona potrzeba dopracowania redakcyjnego. Jeżeli wybierzesz "Europa" jako temat i "Redakcja" jako zadanie, otrzymasz 200 propozycji artykułów o Europie, które zostały oznaczone szablonem Dopracować z określeniem, że artykuł wymaga dopracowania redakcyjnego. Jeżeli oprócz wcześniej wspomnianego wyboru zaznaczysz "Rozwiń krótkie artykuły", dostaniesz artykuły o Europie i wymagające jednocześnie poprawy redakcyjnej i rozbudowy. Jeżeli oprócz wcześniej wspomnianego wyboru dodasz temat "Azja", dostaniesz artykuły o Europie ''lub'' Azji i wymagające jednocześnie poprawy redakcyjnej i rozbudowy. === Nadzór nad sugerowanymi edycjami i rozwiązywanie problemów === ==== Czy mogę śledzić, które artykuły zostały zmienione w ramach sugerowanych edycji? ==== Artykuły, które zostały zmienione w ramach sugerowanych edycji są odpowiednio oznaczane w Ostatnich zmianach i Obserwowanych. ==== Jak mogę monitorować które tematy i rodzaje zadań wymagają więcej artykułów? ==== Skorzystaj z <code>Special:NewcomerTasksInfo</code>. ==== Nie dostaję żadnych zadań dla podanej przeze mnie kombinacji. Czy to prawidłowe? ==== Na niektóre tematy nie ma dużo artykułów. W związku z tym też będzie mało artykułów oznaczonych szablonem Dopracować, co prowadzi do zmniejszonego wyboru. ==== Użytkownik korzysta z tego narzędzi w sposób niekonstruktywny. Co mogę zrobić? ==== Ogólnie użytkownicy dokonują [[#NEWTEA|bardziej konstruktywnych edycji]] przy użyciu narzędzi Growth. Ale czasami można zauważyć, że jakiś użytkownik nie przestrzega reguł i korzysta z tych narzędzi w niewłaściwy sposób. Najodpowiedniejszym sposobem reakcji będzie zastosowanie standardowej procedury postępowania w przypadku zachowania niekonstruktywnego: # spróbuj zrozumieć, co użytkownik próbuje zrobić, # skontaktuj się z użytkownikiem, wyjaśnij co się stało, zapytaj o szczegóły i poprowadź na inną ścieżkę działania, jeśli to możliwe, # jeżeli niekonstruktywne zachowanie nadal trwa, zablokuj użytkownika. Jeżeli wykonywane są podobne niekonstruktywne edycje, są one powtarzające się, w podobnym stylu, [[Talk:Growth|daj nam znać]]. Dołącz linki do porównania zmian jako przykłady błędnych edycji, które zespół Growth przeanalizuje aby opracować rozwiązanie. ==== Włączyłem stronę domową w preferencjach. Gdy wybiorę na stronie domowej artykuł do poprawy, nie otrzymuję żadnych wskazówek podczas wyświetlania artykułu. ==== Czy włączyłeś w preferencjach panel pomocy? Jeżeli tak, [[Talk:Growth|powiadom nas o tym problemie]]. {{anchor|config}} === Konfigurowanie sugerowanych edycji === ==== Jak dać nowicjuszom więcej zadań? ==== Nowicjuszom poleca się pracę nad pięcioma rodzajami zadań redakcyjnych, podzielonych według stopnia trudności: {| class="wikitable" !'''Zadanie''' !Poziom trudności !Cel zadania |- |Poprawki redakcyjne |łatwy |poprawianie pisowni, gramatyki i stylu |- |Dodawanie linków |łatwy |wiązanie artykułów linkami |- |Aktualizacja treści |średni |aktualizowanie informacji w artykułach |- |Dodawanie przypisów |średni |wyszukiwanie przypisów dla już istniejących artykułów |- |Rozbuduj artykuł |trudny |rozwijanie treści krótkich artykułów, wraz z dodawaniem przypisów |} Zadania są dobierane na podstawie szablonów do oznaczania problemów (np. Dopracować). Aby zwiększyć listę prac do wykonania, możesz: * Wskazać inne szablony oznaczające dany problem w konfiguracji na stronie <code>Special:EditGrowthConfig</code> na twojej wiki * Dodaj szablony oznaczające problemy (np. Dopracować) w kolejnych artykułach na wiki. Czasami nie ma nic do zrobienia na poziomie łatwym, gdyż takie zadania są podejmowane również przez doświadczonych użytkowników. Zalecamy doświadczonym użytkownikom, aby pracowali nad trudniejszymi zadaniami aby dać szansę nowicjuszom na dokonanie swoich pierwszych edycji. ==== Czy możemy zaproponować nowy rodzaj zadania lub przypisać inne określenie poziomu trudności do już istniejącego zadania? ==== Na razie to nie jest możliwe. [[Talk:Growth|Daj nam znać]] o swoim pomyśle. === Zadania strukturyzowane: dodaj link === ''Poniższe pytania dotyczą tylko tych wiki, [[Special:MyLanguage/Growth/Deployment table|na których włączono ''Zadanie strukturyzowane - dodaj link'']].'' ==== Jaka jest różnica między "dodaj link" a "Zadanie strukturyzowane - dodaj link"? ==== "Dodaj link" pokaże użytkownikom artykuły, gdzie potrzebne jest więcej linków wewnętrznych. "Dodaj link" jest zadaniem, gdzie artykuły są wybieranie na podstawie szablonów Dopracować. Nowicjusze muszą rozumieć co zrobić, co może być dla nich skomplikowane: jaki link to dobry link, gdzie linkować...? Nawet ze wskazówkami wyświetlanymi w panelu pomocy, nie zawsze dodawane linki są dokładne, a czasami nawet sa dodawane linki zewnętrzne. W związku z tym zespół Growth pracuje nad ulepszeniem tego procesu, zmniejszając ilość trudności, jakich doświadczają edytujący. Dodajemy lepszy mechanizm oprowadzania i sugerujemy zestaw linków, które potencjalnie mogą zostać dodane. Te linki są pokazywane na określonych wyrazach w artykule. Użytkownicy mogą zdecydować, czy link powinien być dodany czy nie. Te linki są sugerowane maszynowo. ==== Które wiki mają Zadanie strukturyzowane - dodaj link? ==== Listę znajdziesz w [[Special:MyLanguage/Growth/Deployment table|tabeli]]. ==== Jaka jest dokładność przewidywania w "Zadanie strukturyzowane - dodaj link"? ==== Średnio, przewidywania te są trafne w 70%. <div lang="en" dir="ltr" class="mw-content-ltr"> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> === Zadania strukturyzowane: dodaj ilustrację === ''Ten projekt jest w trakcie tworzenia. Więcej przeczytasz na [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|stronie o nim]].'' ==== Jakie jest przeznaczenie Zadania strukturyzowanego - dodaj ilustrację? ==== Na tych samych zasadach co "Zadanie strukturyzowane - dodaj link" ten projekt skupia się na usunięciu przeszkód związanych ze wstawianiem ilustracji. ==== Jakie zasady określają pracę do wykonania przez "Zadanie strukturyzowane - dodaj ilustrację?"? ==== <div lang="en" dir="ltr" class="mw-content-ltr"> We have several rules: </div> * Ilustracje są wybierane, jeżeli są wykorzystywane w innych wersjach językowych Wikipedii. Jeżeli kilka artykułów z różnych wersji językowych, powiązanych w tym samym elemencie Wikidanych wykorzystuje tę samą ilustracje, to sugerujemy właśnie ją. * Tylko artykuły bez żadnej ilustracji są brane pod uwagę. * Na razie nie są uwzględniane artykuły z infoboksami, które nie mają zdjęcia. ==== Z jakimi typami użytkowników skontaktowano się, aby to przetestować ==== <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** ludzie, którzy nie są edytującymi wiki (poprzez UserTesting.com, w języku angielskim i hiszpańskim) ** doświadczeni użytkownicy wspierający nowicjuszy w pierwszych krokach, z [[#pilot|wiki pilotażowych]]. {{anchor|HP}} == Panel pomocy == === Chcemy zmienić niektóre linki w panelu pomocy. Jak to zrobić? === Administratorzy mogą zmieniać te linki poprzez stronę <code>Special:EditGrowthConfig</code>. Możemy pomóc podczas tej czynności. [[Talk:Growth|Skontaktuj się z nami]] opisując swoją potrzebę i dołącz link do dyskusji w społeczności, w której podjęto decyzję. Te linki są też wyświetlane [[#Homepage|na stronie startowej dla nowicjuszy]]. === Gdzie są umieszczane pytania zadane przez panel pomocy? === Domyślnie, takie pytania są umieszczane na lokalnej stronie z pytaniami nowicjuszy. Jeżeli na wiki jest włączony zarówno panel pomocy jak i skonfigurowana lista wikiprzewodników, to społeczność może zdecydowac czy: * nowe wiadomości mają być wysyłane na stronę dyskusji przypisanego nowicjuszowi przewodnika, * nowe wiadomości mają być wysyłane na stronę z pytaniami nowicjuszy. Administratorzy mogą zmieniać te ustawienia poprzez stronę <code>Special:EditGrowthConfig</code>. === Nasza społeczność zdecydowała, że wszystkie wiadomości wysłane przez panel pomocy będą lądowały w Pytaniach nowicjuszy. Nie zawsze się tak jednak dzieje. Dlaczego? === Zaobserwowaliśmy, że nowicjusze czasami próbują skontaktować się ze swoimi przewodnikami poprzez pozostawienie wiadomości na ich własnych stronach dyskusji (użytkownik "nowy" kontaktuje się z użytkownikiem "doświadczony" poprzez umieszczenie wiadomości na stronie "Dyskusja_użytkownika:Nowy"). W związku z tym oferujemy możliwość kontaktu z wikiprzewodnikiem gdy nowicjusz skorzysta z panelu pomocy będac na swojej stronie dyskusji. {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> == Konfigurowanie i obsługa systemu wikiprzewodników == === Na mojej wiki nie ma systemu wikiprzewodników stworzonego przez Growth. Jak mogę go uruchomić? === Niżej wymienione kroki skrótowo opisują ten proces. Pełna procedura opisana jest na [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|oddzielnej stronie]]. Upewnij się najpierw, że narzędzia Growth [[Growth/Deployment table|są zainstalowane na twojej wiki]]. Jeżeli tak nie jest, zobacz [[#get|jak otrzymać te narzędzia]]. Następnie, musisz poszukać kilku chętnych wikiprzewodników. Wszyscy wikiprzewodnicy muszą zapisać się na określonej stronie poprzez [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|specjalny sposób zapisu]]. Jeżeli na twojej wiki już uruchomiono system wikiprzewodników w ramach narzędzi Growth, taka strona odpowiadająca twojej wiki będzie wymieniona w [[D:Q14339834|tym elemencie Wikidanych]]. Na Twojej wiki administrator musi dodać listę wikiprzewodników do konfiguracji (<code>Special:EditGrowthConfig</code>). === Ilu wikiprzewodników potrzeba na wiki? === Na podstawie naszych obserwacji, zalecamy jednego przewodnika na każde 500 nowych użytkowników na miesiąc. Na przykład, jeżeli na twojej wiki rejestruje się co miesiąc 2500 nowych kont, powinieneś mieć przynajmniej 5 przewodników. Zalecamy mieć przynajmniej 3 przewodników. <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> === Jak przewodnicy są przydzielani nowicjuszom? === Każde nowe konto ma przydzielanego losowo przewodnika z listy chętnych. === Ile wiadomości na miesiąc będzie otrzymywał wikiprzewodnik? === Trudno powiedzieć. Zależy od stopnia motywacji nowicjuszy i od liczby wikiprzewodników. Z naszych obserwacji będzie to średnio 0 do 6 wiadomości w tygodniu, z wahaniami. === Czy rozważaliście, aby przypisywać przewodnika tylko tym, którzy już wykonali pierwsze edycje? === Nie znamy każdej potrzeby nowicjuszy. [[Special:MyLanguage/New Editor Experiences|Na podstawie tego badania]], niektórzy nowi użytkownicy potrzebują potwierdzić, że mają prawo edytować zanim dokonają swojej pierwszej edycji. Niektórzy chcą dowiedzieć się więcej o edytowaniu zanim sami zaczną edytować. W związku z tym przydzielamy przewodnika każdemu nowo zarejestrowanemu. Wtedy już od niego będzie zależało, czy i kiedy będzie chciał się skontaktować ze swoim przewodnikiem. {{anchor|existing}} === Nasza wiki już ma projekt dotyczący wikiprzewodników. Czy system od Growth zastąpi go? === Domyślamy się, że taki system wikiprzewodników polega wyłącznie na posiadaniu listy doświadczonych użytkowników, którzy chcą pomagać nowym użytkownikom, którzy mogą zwracać się do nich w sprawach różnych zagadnień. Większość takich stron możesz znaleźć poprzez [[d:Q3919128|Wikidane]]. Społeczność może sama zdecydować jak zintegrować to z systemem wikiprzewodników od Growth. Może to być: '''Zastąpienie dotychczasowego systemu mentoringu nowym''' Jeżeli dotychczasowy system wikiprzewodników nie był pomyślny, można go zastąpić narzędziami Growth. '''Posiadanie obydwu systemów działających równolegle''' Wyobraźmy sobie dwie role: * <span lang="en" dir="ltr" class="mw-content-ltr">Growth mentoring takes care of the newcomers basic questions,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The existing mentoring can take care of newcomers who are more involved.</span> Być może w tym przypadku będzie trzeba lokalnie dostosować tekst interfejsu Growth aby wykorzystywał lokalna terminologię. === Gdzie mogę zapisać się jako wikiprzewodnik? === Jeżeli na twojej wiki już uruchomiono system wikiprzewodników w ramach narzędzi Growth, taka strona odpowiadająca twojej wiki będzie wymieniona w [[D:Q14339834|tym elemencie Wikidanych]]. <span class="mw-translate-fuzzy">Społeczność może określić wymagania jakie trzeba spełnić, aby zostać wikiprzewodnikiem, Zazwyczaj jest to dobre doświadczenie w edytowaniu wiki (500 edycji, 90 dni od założenia konta).</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} === Jak przedstawić się jako przewodnik? === Gdy zapisujesz się jako wikiprzewodnik, należy użyć tej składni: <code>* <nowiki>[[</nowiki>Wikipedysta:Nazwa użytkownika<nowiki>]]</nowiki>|Opis</code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|Dowiedz się więcej]] {{anchor|reassign}} === Czy możemy przypisać nowicjusza innemu wikiprzewodnikowi? === Tak, można to zrobić poprzez <code>Special:ClaimMentee</code>. {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> === Przewodnik jest nieobecny. Czy możemy przypisać wszystkich jego nowicjuszy nowym przewodnikom? === <div class="mw-translate-fuzzy"> Możesz użyć <code>Special:ClaimMentee</code> do zmiany, ale jeżeli chcesz to zrobić dla wszystkich nowicjuszy, [[Talk:Growth|skontaktuj się z nami]]. </div> {{anchor|magicword}} === Jak mogę wyświetlić przewodnika przypisanego danemu użytkownikowi? / Jak wyświetlić nazwę wikiprzewodnika do naszej wiadomości powitalnej? === Wpisz magiczne słowo <code><nowiki>{{#mentor:Foo}}</nowiki></code> w wikikodzie. "Foo" należy zamienić na nazwę użytkownika (nowicjusza). Wyświetli to przewodnika użytkownika Foo. Tego magicznego słowa można użyć także w szablonie: wiadomość powitalna, wiadomości wstawiane na stronę dyskusji użytkownika, userboksy itp. [[#reassign|Jeżeli zmieni się przewodnik]], wyświetlona zostanie nazwa nowego mentora. Możesz też użyć "[[Special:MyLanguage/Help:Substitution|subst:]]" czyli: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Wtedy nazwa przewodnika użytkownika Foo zostanie automatycznie zapisana w wikikodzie. === Zmieniliśmy nazwę strony z listą wikiprzewodników i nie otrzymujemy już pytań od nowicjuszy. Jak to naprawić? === Czy zaktualizowaliście w <code>Special:EditGrowthConfig</code> wprowadzając nową nazwę strony? == Porozumiewanie się przewodników z nowicjuszami == {{Anchor|questions}} === Jakie pytania zadają nowicjusze? === Z naszych obserwacji wynika, że pytania najczęściej dotyczą podstaw edytowania. Niektóre pytania to próby kontaktu społecznego ("cześć") od użytkowników próbujących sprawdzić, czy ktoś odpowie. Zachęcamy do odpowiadania na takie wiadomości, ponieważ mogą być początkiem konwersacji. Korzystając z doświadczeń społeczności zespół Growth opracował [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|przewodnik dla wikiprzewodników]] odpowiadających na pytania od nowicjuszy. === Nowicjusze nie odpowiadają na moje wiadomości. Dlaczego? === Oto dwa możliwe powody: * Czy wywołałeś użytkownika w swojej odpowiedzi? Nowicjusze nie wiedzą jak korzystać z listy obserwowanych lub innych narzędzi do obserwacji zmian. Strona domowa pokazuje drogę na stronę dyskusji przewodnika ale wzmiankowanie nowicjusza jest skuteczniejsze. Ping wygeneruje powiadomienie, które jest najlepszym sposobem, aby oznajmić, że dostali odpowiedź na swoją wiadomość. * Nowicjusze nie wchodzą codziennie na wiki. Niektórzy z nich odpowiedzą po kilku dniach, a niektórzy po kilku tygodniach. Wikiprzewodnicy powinni mieć to na uwadze podczas archiwizacji stron dyskusji. === Kogo mogę zapytać, jeżeli mój przewodnik mi nie odpisuje? === Jeżeli twój przewodnik nie jest dostępny, możesz zadać pytanie na stronie z pytaniami nowicjuszy lub innemu doświadczonemu użytkownikowi. === Czy mogę poprosić o innego przewodnika? === Możesz skontaktować się z innym przewodnikiem i poprosić o zostanie Twoim mentorem. Jeżeli się zgodzi, [[#reassign|dokona zmiany]]. === Będąc wikiprzewodnikiem jak mogę zobaczyć listę nowicjuszy przypisanych do mnie? === Obecnie pracujemy nad [[Growth/Mentor dashboard|panelem przewodnika]]. Ta funkcja jest dostępna na wszystkich wersjach językowych Wikipedii, gdzie [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|lista wikiprzewodników została utworzona i aktywowana]]. === Czy mogę ograniczyć wyniki na ostatnich zmianach i obserwowanych do tych, które dotyczą moich podpoiecznych? === Na wiki, gdzie włączono panel przewodnika, przewodnicy mają do dyspozycji dodatkowy filtr. Mogą oni obserwować aktywność swoich podopiecznych w Obserwowanych i Ostatnich zmianach. Ze względu na ochronę prywatności, dostępu do wyników tego filtru nie mają inni niż dany przewodnik. Ten filtr pokaże tylko edycje wykonane przez nowicjuszy przypisanych do bieżącego konta wikiprzewodnika. Ten filtr nie jest dostępny dla tych, co nie [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|dopisali się jako przewodnicy]]. <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> l4948xw3v6rvmr76nrhewb88tav450h Growth/FAQ/pt-br 0 1419940 5387839 5378644 2022-07-29T10:15:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''Bem-vindo às Perguntas frequentes (FAQ) da equipe de crescimento.''' Esperamos que você encontre as informações que precisa. No entanto, se não for o caso [[Talk:Growth|informe-nos]] ''Nota para tradutores: esta página é atualizada regularmente, o que pode impactar seu trabalho. Estamos fazendo o nosso melhor para evitar esses distúrbios.'' == Geral == {{Anchor|features}} ===Em quais recursos você está trabalhando?=== * [[Special:MyLanguage/Growth/Feature summary#NH|'''Página do novato''']]: uma nova página especial, o melhor lugar para um novato começar. Inclui: ** [[Special:MyLanguage/Growth/Feature summary#NT|'''Tarefas para os novatos''']]: um feed de sugestões de tarefas que ajudam os novatos a aprender a editar. Os recém-chegados têm feito [[NEWTEA|edições produtivas]] através deste feed! [[Help:Growth/Tools/Suggested edits|Saiba mais sobre esta ferramenta]]. ** '''Módulo de tutoria''' [módulo opcional]: cada novato tem um link direto para um usuário experiente. Dessa forma, eles podem fazer perguntas sobre a edição da Wikipedia, sem a necessidade de encontrar onde pedir ajuda. ** '''Módulo de impacto''': o usuário vê quantas páginas visualiza os artigos que ele edita recebeu. * [[Special:MyLanguage/Growth/Feature summary#HP|''Painel de ajuda''']]: uma plataforma para fornecer recursos aos recém-chegados enquanto eles estão editando. Se eles escolherem uma das tarefas sugeridas na página inicial do recém-chegado, eles serão guiados passo a passo no processo de edição. * '''[[Growth/Understanding first day|Pesquisa de boas-vindas]]''': as comunidades podem saber por que os novatos criam uma conta na Wikipedia. Você pode dar uma olhada em nosso '''[[Special:MyLanguage/Growth/Feature summary|resumo de recursos]]''' para saber mais sobre isso. <div lang="en" dir="ltr" class="mw-content-ltr"> === On which wikis Growth features have been deployed? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find a list of wikis on our [[Special:MyLanguage/Growth/Deployment table|Deployment table]]. This page lists features activation per wiki as well. </div> {{anchor|NEWTEA}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Are Growth features effective? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[NEWTEA|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that newcomers make their first article edit (+11.6%)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that they are retained as editors</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the number of edits they make during their first couple of weeks on the wiki (+22%)</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This deployment has been achieved in October 2021.</span> {{anchor|translate}} <div lang="en" dir="ltr" class="mw-content-ltr"> === The interface is partially translated. How can I change this? === </div> [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] <div lang="en" dir="ltr" class="mw-content-ltr"> It takes up to one week to see new translations being deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Special pages names require a special process. For the following strings, [[Talk:Growth|please contact us]] directly with the translations: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. </div> {{anchor|enable|test}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I test the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[Growth/Deployment table|On wikis where the Growth features are available]], and also on [https://test.wikipedia.org test.wikipedia.org], go to your [[Special:Preferences#mw-prefsection-personal|user preferences]] on one of these wikis and then: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Help panel''' in the ''{{int|prefs-editing}}'' tab.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Newcomer homepage''' in the ''{{int|prefs-personal}}'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work.</span> {{anchor|get}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can my wiki get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[#features|these features]], with the following conditions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Do you plan to deploy the features outside of Wikipedia? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Please contact us [[Talk:Growth|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> We are considering working with [[Growth/Communities/Wikisource|Wikisource communities]]. </div> {{anchor|pilot|ambassador}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can you clarify what "Pilot wikis", "Control group wikis" and "Ambassadors" are? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''Pilot wikis''' are wikis who have a close collaboration with the Growth team. They are involved in projects definitions and early review of the projects. They also test all prototypes first. The Growth team can contact some other wikis for some of these steps. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, our pilot wikis are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I use the Growth features on mobile ? On the official apps (iOS, Android)? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Access to the features == </div> {{anchor|ABtest}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can new accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where no [[A/B testing|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where an [[A/B testing|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How can existing accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], anyone can find the features [[#enable|in their Preferences]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === I host a workshop. How can I control if my students get the features when they create an account? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is possible to have a link parameter to control access to the features: </div> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=1</code> will force Growth features at account creation</span> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=0</code> will force the default experience at account creation</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[Talk:Growth|Please let us know]] if you plan to use these parameters. </div> {{anchor|Homepage}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Homepage == </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> === How to access the Homepage? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My email is requested, or my email is displayed at the top of the Homepage. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[Special:MyLanguage/Help:Notifications|notifications]], like when they are mentioned by other users on wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The email address won't be visible by other users. Communication with other users all happen on the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === The help links displayed on the homepage are not relevant. How to change them? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#HP|the same as on the Help panel]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Suggested edits == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How does Suggested Edits work ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How topics and tasks are suggested? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === SuggestedEdits' supervision and troubleshooting === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can I monitor which articles have been edited as Suggested edits? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to monitor which topics or which tasks need more articles? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please use <code>Special:NewcomerTasksInfo</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I don't have any task for a given combination. Is it normal? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== A user uses the tools in an nonconstructive way. What can I do? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Overall, users make [[#NEWTEA|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">try to understand what the use tries to do,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">contact this user, explain the situation, ask them for details and guide them to a different path if it exists,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">if the nonconstructive behavior persists, then block the user.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If repetitive and similar nonconstructive edits are made at your wiki, [[Talk:Growth|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you activated the Help panel in your preferences? If yes, [[Talk:Growth|please let us know about this issue]]. </div> {{anchor|config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Suggested edits configuration === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to provide more tasks for newcomers? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: </div> {| class="wikitable" !'''<span lang="en" dir="ltr" class="mw-content-ltr">Task</span>''' !<span lang="en" dir="ltr" class="mw-content-ltr">Level of difficulty</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Goal of the task</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Copyedit article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">fix spelling, grammar and tone</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add Links</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">add links between articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Update article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">bring existing articles up-to-date</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add References</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">find sources for existing articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Expand article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">hard</span> |<span lang="en" dir="ltr" class="mw-content-ltr">expand stubs to become sourced articles</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Add other templates that match the definition of the task to <code>Special:EditGrowthConfig</code> on your wiki</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add maintenance templates to more articles on your wiki.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is not possible at the moment. [[Talk:Growth|Please let us know]] about your potential project. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add a link === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Special:MyLanguage/Growth/Deployment table|where ''Structured tasks - Add a link'' has been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">"Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users have to decide if a link should be added or not added. These links are suggested by a machine.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which wikis have Structured tasks - Add a link ? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the accuracy of Structured tasks - Add a link predictions? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The predictions are, on average, accurate at 70%. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add an image === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the purpose of "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which rules define the work done by "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have several rules: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Only articles where no image is displayed are taken into consideration for images addition.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Articles with an infobox but no image aren't taken into consideration for now.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which types of users have been contacted to test this new concept ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">people who aren't wiki editors (using UserTesting.com, in English and Spanish)</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia.</span> {{anchor|HP}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Help panel == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We want to change some links displayed on the Help panel. How to do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#Homepage|also used on the Homepage]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where does questions posted using the Help panel goes? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, these questions go the the local Help desk. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should go the newcomer's mentors,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should be posted at the help desk.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change this configuration using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page.</span> {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration and operation of the mentoring system == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My wiki doesn't have the Growth mentoring system. How can I set it up? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The next steps are a summary of the process. The full process is described on [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|this dedicated page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, you need to check if the Growth tools are [[Growth/Deployment table|deployed at your wiki]]. If it is not yet the case, please see [[#get|how to get the features]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Then, you have to find some other mentors to volunteer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All mentors have to sign-up on a specific page, using [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a specific syntax]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> At your wiki, an admin has to add the mentor list to the configuration page (<code>Special:EditGrowthConfig</code>). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many mentors does a wiki need? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We recommend to have at least 3 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How mentors are assigned to newcomers? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Each new account receives a mentor randomly taken from a list of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many messages does a mentor receive per week? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Have you considered to assign a mentor only to people who already made some edits? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We don't know what each newcomer needs. [[Special:MyLanguage/New Editor Experiences|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. </div> {{anchor|existing}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[d:Q3919128|listed on Wikidata]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: </div> '''<span lang="en" dir="ltr" class="mw-content-ltr">Replace your mentoring system with the new one</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">If your mentoring system hasn't much success, it could be replaced by the Growth team features.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">Have both systems working together</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">You can imagine to have two roles:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Growth mentoring takes care of the newcomers basic questions,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The existing mentoring can take care of newcomers who are more involved.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> In this case, you might have to locally translate the interface for Growth features using your own terms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where can I signup as a mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Your community may have defined some conditions to become a mentor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How do I introduce myself as a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you sign up to become a mentor, the following syntax must be used, with: </div> <code>* <nowiki>[[</nowiki><span lang="en" dir="ltr" class="mw-content-ltr">User:Username</span><nowiki>]]</nowiki>|<span lang="en" dir="ltr" class="mw-content-ltr">Description</span></code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|<span lang="en" dir="ltr" class="mw-content-ltr">Read more about this</span>]] {{anchor|reassign}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can we reassign a newcomer to a different mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes, it is possible using <code>Special:ClaimMentee</code>. </div> {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === A mentor just quit. Can we reassign all their newcomer to different mentors? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can use <code>Special:ClaimMentee</code> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[Talk:Growth|please contact us]] directly. </div> {{anchor|magicword}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Type the magic word <code><nowiki>{{#mentor:Foo}}</nowiki></code> in a wikitext page, and preview. "Foo" has to be replaced by the username you target. This will display the name of Foo's mentor. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[#reassign|If the mentor changes]], then the magic word picks the new mentor's name. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can "[[Special:MyLanguage/Help:Substitution|subst:]]" this message if needed: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Foo's mentor will then be saved as wikitext. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you updated <code>Special:EditGrowthConfig</code> with the new page name? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Interactions between mentors and newcomers == </div> {{Anchor|questions}} <div lang="en" dir="ltr" class="mw-content-ltr"> === What kinds of questions do newcomers ask? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> From the observations we have made, questions are mostly about basic editing. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on communities experiences, the Growth team worked [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|on a guide for mentors]] who have to reply to these questions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Newcomers haven't replied to my messages. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Two possible cases there: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can I ask if my mentor is not responding to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I ask to have a different mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[#reassign|make the change]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, how can I monitor the newcomers assigned to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are currently working on a [[Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is available at all Wikipedias where [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|a list of mentors has been created and activated]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At wikis where the mentor dashboard is deployed, a new filter is available for mentors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They can monitor their mentees' activity in Watchlist and RecentChanges.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|not listed as mentors]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> tc0uta7s69hnzugwixe9tj3adz2y900 Manual:Pywikibot/category redirect.py/ja 100 1425312 5387861 4824962 2022-07-29T10:22:53Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> '''category_redirect.py''' is a {{ll|Manual:Pywikibot|Pywikibot}} script used to move pages out of redirected categories. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The bot will look for categories that are marked with a category redirect template, take the first parameter of the template as the target of the redirect, and move all pages and subcategories of the category there. It also changes hard redirects into soft redirects, and fixes double redirects. A log is written under &lt;userpage>/category_redirect_log. Only category pages that haven't been edited for a certain cooldown period (7 days by default) are taken into account. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following parameters are supported: </div> {{Pywikibot command table beginning}} {{option|delay:#|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set an amount of days. If the category is edited more recenty than given days, ignore it. Default is 7</span>}} {{option|tiny|2=<span lang="en" dir="ltr" class="mw-content-ltr">Only loops over [[:d:Q8099903|Category:Wikipedia non-empty soft redirected categories]] and moves all images, pages and categories in redirect categories to the target category</span>}} {{Pywikibot command table end}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Usage == </div> <syntaxhighlight lang=shell-session> $ python pwb.py category_redirect [options] </syntaxhighlight> {{Manual:Pywikibot/Global Options}} [[Category:Pywikibot scripts{{#translation:}}|category_redirect]] s3fji6v8qik51a7gasjz96go0xixuht Extension:Highlight Links in Category/ru 102 1425896 5387154 5345731 2022-07-28T21:07:59Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''Highlight Links in Category''' is an extension that adds a CSS class to links pointing to members of a category. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Installation== </div> {{ExtensionInstall|HighlightLinksInCategory|registration=required}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Configuration parameters== </div> ; $wgHighlightLinksInCategory : <span lang="en" dir="ltr" class="mw-content-ltr">This global is an array that configures which categories get an added CSS class. The keys are the Category names, which must include underscores instead of spaces. Do not include the Category: namespace. The value for each key is the CSS class you would like to add to that category. For example:</span> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want add more than one class, separate the class names with spaces, like </div> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can add as many of these as you want, but from a UX perspective it's probably not awesome to add 500 different style links. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If $wgHighlightLinksInCategory is not set or empty, this extension will do nothing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're running a wiki farm and need to turn it off on some wikis, set <syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight>; using {{phpi|false}} could lead to incorrect behavior.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Styling== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Simply add the styles you need for these links to MediaWiki:Common.css on your wiki. For example: </div> {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want one category to override another, you'll have to specify it with CSS. </div> {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> Or alternatively, you could have defined the original <code>a.templates</code> rule as <code>a.templates:not(.disambig)</code> instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There's also the link icon approach: </div> {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==User Toggles== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An easy way to set up toggling this highlighting on or off is to make a [[Extension:Gadgets|Gadget]] with CSS in it. Yes, this is a personalization extension that outsources the personalization part to other extensions; I can still sleep at night. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==How this works== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Right after MediaWiki determines which linked pages exist (to make redlinks), it runs the <code>GetLinkColours</code> hook (see LinkHolderArray.php).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As we have a list of all of the page ids which are linked on that page, we can run one database query to see which of these links are in the set of categories we want to highlight.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Because the query only happens on an index of the <code>categorylinks</code> table, it's reasonably fast.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then CSS classes are assigned based on the result, using the configuration values the user sets in <code>$wgHighlightLinksInCategory</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Explaining how CSS works is outside the scope of this document. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Known issues== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * CSS styles are not added in Flow, because it doesn't appear to call the GetLinkColors hook there. </div> == См. также == <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:Category:LinkEnd extensions]] - which customize links in other ways </div> {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] 792qwktm71nfccch2kmr1ksd0bh82o0 HHVM/ru 0 1426121 5387455 5240449 2022-07-28T22:32:10Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Historical|1=HHVM has been removed from Wikimedia and no longer supported since MediaWiki 1.34.}} <onlyinclude>{{Wikimedia engineering project information | name = HHVM | description = <span lang="en" dir="ltr" class="mw-content-ltr">Support in MediaWiki for HHVM (HipHop Virtual Machine) and deployment to the Wikimedia cluster</span> | start = March 2014 | end = December 2014 | group = [[Special:MyLanguage/Wikimedia Platform Engineering|Platform]] | lead = [[Special:MyLanguage/User:Ori.livneh|Ori Livneh]] | team = [[Special:MyLanguage/user:Tim Starling|Tim Starling]], [[Special:MyLanguage/User:Aaron Schulz|Aaron Schulz]], [[Special:MyLanguage/User:😂|Chad Horohoe]], [[Special:MyLanguage/User:Hashar|Antoine Musso]], [[Special:MyLanguage/User:DGarry (WMF)|Dan Garry]], [[Special:MyLanguage/User:MaxSem|Max Semenik]] | previous = | next = | projectpage = HHVM | display = {{{display}}} }}</onlyinclude> :<span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/HHVM/About|HHVM/About]] for a shorter description, and the December 2014 blog post '''"[https://techblog.wikimedia.org/2014/12/29/how-we-made-editing-wikipedia-twice-as-fast/ How we made editing Wikipedia twice as fast]"''' for more background on HHVM, its benefits, and a look back on the deployment work.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">In September 2017, Facebook announced that HHVM would not aim for PHP compatibility in the future.<ref>Max Wang, [https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "The future of HHVM"]</ref> After discussion<ref>[https://lists.wikimedia.org/pipermail/wikitech-l/2017-September/088784.html "HHVM vs. Zend divergence"] on ''wikitech-l''</ref> WMF adopted a plan to migrate the WMF production cluster to PHP 7. HHVM support has been dropped from MediaWiki. See {{phabricator|T176209}} and {{phabricator|T192166}}.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">'''[[w:HHVM|HHVM]]''' is a PHP interpreter tool (concretely a virtual machine that compiles PHP bytecode to native instructions at runtime) that was deployed on Wikimedia servers in 2014, decreasing the loading time for: any page you view while logged in, and for saving pages that you've edited whether you are logged in or not.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Roadmap == </div> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM is a new way for websites to run [[Special:MyLanguage/Manual:What is MediaWiki?|MediaWiki]] (written in [[w:PHP|PHP]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is sometimes known by its full name HipHop Virtual Machine and has a just-in-time compiler (JIT).</span> <span lang="en" dir="ltr" class="mw-content-ltr">HHVM should speed up page viewing for logged-in users and also speed up the saving of edited pages for all users.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This page is about Wikimedia-sponsored work on HipHop support in MediaWiki, and its deployment to Wikimedia production wikis. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Historically, the HipHop compiler was a project by Facebook which involved compiling PHP code into C++ for purposes of speeding up the language. Facebook has since abandoned this project, and now their development efforts are focused on HHVM itself instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is the general plan for deploying HHVM to the production cluster in 2014: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Deployment to Beta Cluster (currently ongoing work, in parallel with other work) {{done}} * Week of July 21: deployment to a few job runners in production {{done}} * Deploy to test.wikipedia.org application server {{done}} * Deploy Varnish module allowing partial deployment to a fraction of application servers{{Done}} * Limited deployment to small number of application servers {{Done}} * Ramp up deployment to more application servers until most servers use HHVM{{done}} * Deploy to remainder of services{{done}} </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === HHVM work === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Phabricator: [[phabricator:project/board/79/|Open tasks]], [[phabricator:project/board/79/query/all/|All tasks]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Rationale == </div> <span lang="en" dir="ltr" class="mw-content-ltr">It is a well-studied phenomenon that even small delays in response time (e.g. half of a second) can result in sharp declines in web user retention.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://radar.oreilly.com/2009/06/bing-and-google-agree-slow-pag.html "Bing and Google Agree: Slow Pages Lose Users"] - Brady Forrest - ''O'Reilly Radar''</span> </ref><ref> <span lang="en" dir="ltr" class="mw-content-ltr">[http://glinden.blogspot.com/2006/11/marissa-mayer-at-web-20.html Greg Linden's blog: "Marissa Mayer at Web 2.0"] - Marissa Mayer pointed out that a change from 0.4 seconds to 0.9 seconds in response time from Google caused a 20% drop in revenue and traffic.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">As a result, popular websites such as Google and Facebook invest heavily in site performance initiatives, and partially as a result, remain popular.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Formerly popular sites (such as Friendster) suffered due to lack of attention to these issues.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">"[http://www.nytimes.com/2006/10/15/business/yourmoney/15friend.html Wallflower at the Web Party]", New York Times, October 15, 2006. Quote: "Kent Lindstrom, now president of Friendster, said the board failed to address technical issues that caused the company’s overwhelmed Web site to become slower."</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedia and its sister projects must remain usable and responsive in order for the movement to sustain its mission.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Facebook, as a big user of PHP, has recognized this problem, and invested heavily<ref>http://www.wired.com/wiredenterprise/2013/06/facebook-hhvm-saga/</ref> in a solution: [http://hhvm.com HHVM], a virtual machine that compiles PHP bytecode to native instructions at runtime, the same strategy used by Java and C# to achieve their speed advantages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We're quite confident that this will result in big performance improvements on our sites as well.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == What does HipHop do for our end users? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is written in PHP, a language that is [[w:Interpreter (computing)|interpreted]] at run-time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The overhead of running this PHP code every time someone views a page necessitates the usage of caching servers, running software such as [[w:Varnish (software)|Varnish]], which cache the HTML generated by running this PHP, so that the PHP does not have to run every time a page is viewed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These caches only serve users that are not logged in.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">By definition, users that are logged in cannot be served pages from a static cache, as the page served to them must include user-specific HTML such as their username at the top right of the page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, unfortunately, creates a situation where simply logging in causes a tangible decrease in how well our sites perform for you.</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Actions which are not affected by the cache, and therefore ''are'' affected by the run time of PHP code, include:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> *Any page you view while logged in. *Saving pages that you've edited, whether you are logged in or not. Therefore, any action we can take to reduce the time it takes for MediaWiki's PHP code will therefore also decrease the loading times of our site for all of our logged in users and anyone who edits anonymously. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> HipHop was written to be a faster, more efficient PHP interpreter than our current interpreter ([[:en:Zend Engine|Zend]]). It is our hope that by implementing HipHop as a replacement for Zend, our users will notice a tangible increase in the performance of our sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == How does our development work on HipHop affect MediaWiki developers? == </div> <span lang="en" dir="ltr" class="mw-content-ltr">In our initial sprint of work, due to be finished at the end of March 2014, we hope to make it so that anyone can elect to use HipHop on Beta Cluster instead of Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will be on a totally opt-in basis which can be disabled at any time.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will allow the MediaWiki Core team to gauge the performance of HipHop against that of Zend directly using our current test infrastructure, instead of just estimating theoretical performance increases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also create a development environment that will help us see how much work is needed to make HipHop compatible with MediaWiki, and as such let us create an estimate for how long it will take us to get HipHop live on production as a full replacement for Zend.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For other MediaWiki developers, the consequence of HipHop being deployed in this manner is that if they are using the Beta Cluster as a test environment, they will find it trivial to test how their patches perform using HipHop instead of Zend if they wish to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However, to minimise the disruption of our work, the opt-in nature of the infrastructure will allow developers will be able to continue to develop totally agnostic of the future HipHop migration if they wish to do so.</span> == См. также == <div lang="en" dir="ltr" class="mw-content-ltr"> * {{ll|HHVM/About|HHVM/About}} * [[Special:MyLanguage/HHVM/Vagrant|HHVM/Vagrant]]: Setting up HHVM in {{ll|MediaWiki-Vagrant|MediaWiki-Vagrant}} * [https://www.youtube.com/watch?v=vgXgDVrb-BU Ori presenting at @Scale about migrating to HHVM] * [https://www.youtube.com/watch?v=IKvILMSNNpk HHVM in production: what that means for Wikimedia developers] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == References and footnotes == </div> <references /> [[Category:Performance development{{#translation:}}]] [[Category:Programming language implementation{{#translation:}}]] cxuhfea25s0tslnb5fegt08ccwqw1ja Manual:Mwdocgen.php/ru 100 1427058 5386711 4827935 2022-07-28T17:47:56Z Артём 13327 17625157 Created page with "Описание" wikitext text/x-wiki <languages/> {{MW file|mwdocgen.php|maintenance/|class1=MWDocGen}} '''mwdocgen.php''' is a [[Special:MyLanguage/Manual:Maintenance scripts|MediaWiki maintenance script]] that generates class and file reference documentation for MediaWiki using [[Special:MyLanguage/Manual:Coding conventions#Comments and documentation|doxygen]]. If the dot DOT language processor is available, attempt call graph generation. ==Usage== php mwdocgen.php [&lt;command>] [&lt;options>] {| style="width: 75%; border:1px solid #338800; background-color:#FEFEFE;" |- ! width="33%" | Option/Parameter || Описание |- | --all || Process entire codebase. |- | --includes ||Process only files in includes/ directory. |- | --languages || Process only files in languages/ directory. |- | --maintenance || Process only files in maintenance/ directory. |- | --skins || Process only files in skins/ directory. |- | --files &lt;file> || Process only the given file. |- | --no-extensions || Process everything but extensions directories. |- | --output &lt;dir> || Set output directory (default <code>$doxyOutput</code>). |- | --generate-man || Generates manual page documentation. |- | --help || Shows the help and exit. |- |} ===Known bugs=== * <code>pass_thru</code> seems to always use buffering (even with <code>ob_implicit_flush()</code>), that make output slow when doxygen parses language files. * the menu doesn't work; it got disabled at revision 13740. We need to code it. == См. также == * [[Special:MyLanguage/Manual:Coding conventions/PHP#Comments and Documentation|Coding conventions/PHP#Comments and Documentation]] [[Category:Maintenance scripts{{#translation:}}|mwdocgen.php]] n5er003k145p7dum6lbo0clmojrq99s Documentation/Style guide/de 0 1427438 5387082 5384127 2022-07-28T20:21:20Z ThisCarthing 17456337 Created page with "Freundlich" wikitext text/x-wiki <languages/> == Überblick == <span lang="en" dir="ltr" class="mw-content-ltr">This style guide provides guidance for writing and editing technical documentation in MediaWiki and other technical spaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It provides tips to help you write clear, concise technical documentation in plain language. It also links to additional resources about technical writing and editing in general.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Good technical documentation makes it easier for people to contribute to Wikimedia projects.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to follow clear standards and style guidelines for writing and editing documentation, especially when the contributors and readers have varying levels of skills and experience.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not you consider yourself a writer, your contributions are needed and appreciated!</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===English Wikipedia Manual of Style=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[w:WP:MOS|English Wikipedia's Manual of style]] covers general writing topics (like punctuation) in detail, and summarizes the key points of other style guides.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It can be a useful reference for anyone writing or editing technical documentation in English across Wikimedia projects, especially if the local wiki doesn't have more specific guidelines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This page provides basic guidelines and tips to help get you started with technical documentation. It includes some information specific to technical documentation that is not covered in the Wikipedia Manual of Style.</span> {{TOC|align=right}} == Leserschaft und Inhalt == === Für technische Leserschaften schreiben === <div lang="en" dir="ltr" class="mw-content-ltr"> Before you begin writing, consider the audience for your work: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Who will read this technical documentation? </div> * Wo kommen sie her? <div lang="en" dir="ltr" class="mw-content-ltr"> * How familiar are they with the concepts you are presenting? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * What might they need to know in order to understand? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once you have an understanding of your audience, you will have a better sense of what you need to communicate. </div> {{tip|1=<nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * If you know your audience is ''highly technical and familiar'' with the processes you are describing, then you ''do not need to explain'' basic concepts. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * If you know your audience is ''learning or unfamiliar'' with the processes you are describing, then ''include explanations'' of basic concepts ''and links'' to additional information. </div> }} <div lang="en" dir="ltr" class="mw-content-ltr"> === Writing with a purpose === </div> <span lang="en" dir="ltr" class="mw-content-ltr">What purpose will your technical documentation serve? There are many reasons to write documentation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is helpful to know ''why'' you are writing and what your goal is before you begin.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Is it to teach someone, like a newcomer, about a process or concept? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Is it to show someone how to follow a process? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Is it meant to provide background and context for a concept or process? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Is it a reference intended to provide information? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Writing within a context === </div> <span lang="en" dir="ltr" class="mw-content-ltr">When deciding what to write and how to frame it for your reader, it can help to define a context or occasion for your writing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Your communication takes place in the context of a bigger situation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The context may be bounded by the era you are writing in, the type of technology available, your geographical location and culture, or the current culture and communication styles of your readers.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The occasion may be personal and arise from the situation that motivated you to create or improve a piece of documentation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you are writing technical documentation for Wikimedia projects, consider the culture created by the individuals who participate in those projects.</span> <span lang="en" dir="ltr" class="mw-content-ltr">How could you best position your writing within the context of this community and its culture to create the most meaningful and useful technical documentation?</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === User testing and feedback === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Create technical documentation to communicate ideas and concepts to a real audience of users.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Naturally, this audience should play a critical role in how the documentation is shaped and reshaped.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Think about ways you can gather information about your users' experiences.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Take some time to answer the following questions:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Does your documentation include a mechanism for feedback? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Can you engage in timely conversations with the audience to make improvements? </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Can you use forums like Stack Overflow or mailing lists to check if your document answers the most common questions people have about your specific topic?</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Clarity and consistency === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Clarity and consistency makes it easier to access, read, and create technical documentation across MediaWiki/Wikimedia projects.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Technical documentation is written for a wide audience and edited by a variety of contributors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Voice, tone, grammar usage, style, and format should be consistent across technical documentation and similar content collections.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This helps readers learn how to navigate information and makes it easier for contributors to understand how to edit and add new information.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Deciding on a document type === </div> {{see also|Documentation/Technical documentation templates and suggestions|ll=1}} <div lang="en" dir="ltr" class="mw-content-ltr"> Identify your main audience, purpose, and context first to decide on the type of document you will create. </div> {| class="wikitable" |+ !Beispielleserschaft !Zweck<ref>https://www.divio.com/en/blog/documentation/</ref> !<span lang="en" dir="ltr" class="mw-content-ltr">Potential Document Types</span> !Beispiel |- |<span lang="en" dir="ltr" class="mw-content-ltr">Newcomer interested in learning how to become a Toolforge user</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To learn</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Tutorial, FAQ, Getting Started guide</span> |[[wikitech:Help:FAQ#Cloud_VPS|<span lang="en" dir="ltr" class="mw-content-ltr">Cloud VPS and Toolforge FAQ</span>]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">Experienced technical contributor trying to work through a known problem</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To achieve a goal</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Walk-through, How-To guide</span> |[[wikitech:Help:Toolforge/My_first_Flask_OAuth_tool|<span lang="en" dir="ltr" class="mw-content-ltr">My First Flask OAuth Tool</span>]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">Individual trying to understand the history of ORES and how it evolved</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To understand</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Explanatory article, blog post, "overview"</span> |[[wmfblog:2015/11/30/artificial-intelligence-x-ray-specs/|<span lang="en" dir="ltr" class="mw-content-ltr">Artificial intelligence service “ORES” gives Wikipedians X-ray specs to see through bad edits</span>]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">A person looking for a definition of SSH keys</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To inform</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Reference guide, glossary</span> |[[wikitech:Help:Glossary|Glossar]] |} == Sprache == {{see also|wikiversity:Technical_writing_style|label 1=<span lang="en" dir="ltr" class="mw-content-ltr">The "Writing clearly" article on Wikiversity</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">This section briefly mentions some topics worth exploring elsewhere in more detail.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Always check your words and expressions against these criteria on [[wikt:|Wiktionary]]:</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiktionary entries cover hundreds of languages, explicitly state the grammatical and lexical features of words and their declensions, provide detailed context labels (including about jargon, UK vs. USA English) and expose how translatable terms are in hundreds of other languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Plain English === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please remember: many visitors to these pages are not native English speakers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For documentation written in English, [[w:Plain English|Plain English]] (also called [[w:plain language|plain language]]) works best.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Clear writing is the most understandable by diverse audiences, and is also easiest to translate.</span> <span lang="en" dir="ltr" class="mw-content-ltr">There are a number of good tools for checking your writing, at [[m:Special:MyLanguage/Tech/News/Manual#Guidelines|Tech News' Writing Guidelines on Meta-Wiki.]]</span> {{tip|1=<nowiki/> * <span lang="en" dir="ltr" class="mw-content-ltr">Avoid ambiguity, jargon, and vague or complex wording.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Use words your audience will understand, and enough words to convey your message.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Define terms that may not be obvious to individuals who are new to the subject matter you are writing about.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Keep paragraphs and sentences short and concise.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Use contractions or don't. Be consistent.</span> }} <div lang="en" dir="ltr" class="mw-content-ltr"> === Voice and tone === </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is a place where anyone can edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, it can be difficult to maintain a consistent voice and tone in the documentation.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Consider using these elements in your writing: </div> {| class="wikitable" !<span lang="en" dir="ltr" class="mw-content-ltr">Voice and tone</span> !<span lang="en" dir="ltr" class="mw-content-ltr">What this means</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Instead of this</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Try This</span> |- |Freundlich |<span lang="en" dir="ltr" class="mw-content-ltr">Technical documentation does not need to sound academic or dry.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Write to your audience as if they are there in person.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Before beginning, the user must create an account.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Start by creating an account.</span> |- |Professionell |Technische Dokumentation kann freundlich sein, sollte jedoch professionell bleiben. Verwende {{ll|Inclusive language}}. |<span lang="en" dir="ltr" class="mw-content-ltr">Don't make a bazillion changes.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Try to make minimum changes.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Positive</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Avoid using negative sentence constructions. Explain things in terms of what to do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is harder to mentally parse a complex negative sentence!</span> |<span lang="en" dir="ltr" class="mw-content-ltr">''N'' won't happen, if you don't ''XYZ''.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To make ''N'' happen, do ''XYZ''.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Active</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Try to use [[w:Active voice|active voice]], except when diplomacy calls for [[w:Passive voice|passive voice]].</span> |<span lang="en" dir="ltr" class="mw-content-ltr">The extension must be registered.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">You must register the extension.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Non-gendered</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Adopt [[w:Gender-neutral language|gender-inclusive language]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Assume your audience comprises all gender identities.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">When he clicks Save</span> |<span lang="en" dir="ltr" class="mw-content-ltr">When the user clicks Save</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Inclusive</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Use alternatives to common words or phrases that may unintentionally reinforce inappropriate stereotypes.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">This UI is crazy.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">This UI could be improved.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Free of frustration</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Avoid terms like "easy" and "simple" which can be frustrating for less tech-savvy users.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Simply create a user account.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Create a user account.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Free of colloquialisms</span> |<span lang="en" dir="ltr" class="mw-content-ltr">It can be confusing to use [[w:Colloquialism|colloquialisms]], jokes, puns, or ''turns of phrase'' that non-native English speakers or individuals from other regions might not easily understand.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Creating a user account is a piece of cake.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Creating a user account requires two steps.</span> |} {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is not meant to be an exhaustive list or a strict set of rules.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Point of view=== </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The following guidance overrides the general Wikipedia style guidelines for [[w:Wikipedia:Manual_of_Style#First-person_pronouns|pronouns]], but only for technical documentation.</span>}} * <span lang="en" dir="ltr" class="mw-content-ltr">Use [[w:Grammatical_person|second person]] ("You" or assumed "You") when addressing your audience.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Avoid [[w:Grammatical_person|first person]] ("I" or "we"), unless you are writing a FAQ with questions asked from the first person perspective.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Use an [[w:Imperative_mood|imperative mood]] for most documentation focused on goals or process.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Dates=== </div> * Verwende immer das vollständige, vierstellige Jahr. * <span lang="en" dir="ltr" class="mw-content-ltr">Use absolute dates ("in May 2037") instead of relative dates ("next year in May").</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Avoid adding dates that will require regular manual updates. Example: Write <code><nowiki>{{#time: Y }}</nowiki></code> instead of {{#time: Y }} when referring to the current year, no matter what year it is currently.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Structuring pages == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Overview === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages should include an overview section (also called the [[w:Wikipedia:Manual_of_Style/Lead_section|Lead section]]) that explains: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Purpose of the page</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Audience of the page</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Prerequisites the reader will need to know before proceeding (Ex. a working knowledge of Python)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Software or tools the reader will need to complete the processes or tasks outlined on the page (Ex. Java installed)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Use case, case study, a practical understanding of the product, service or tool in action. (optional)</span> === Inhaltsverzeichnis === * <span lang="en" dir="ltr" class="mw-content-ltr">Each page should include a table of contents, so information can be accessed easily.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Titles and headers === </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Use [[w:Letter_case#Sentence_case | sentence case]] for headers.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Keep header fonts consistent throughout documentation.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Optional use of [[w:Help:Link#Section_linking_(anchors)|anchors]] to link sections or subsections in the same page.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add a blank line after section headers. This impacts [[Special:MyLanguage/Help:Extension:Translate/Page_translation_example#About_titles|how the content is packaged for translation]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Do not put a header before your overview or lead section.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Information flow === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Technical documentation pages should follow a consistent pattern across content collections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''An ideal pattern''' for each page might be: </div> * Seitentitel * Einführung/Übersicht * <span lang="en" dir="ltr" class="mw-content-ltr">Header</span> ** Inhalt *** <span lang="en" dir="ltr" class="mw-content-ltr">Subhead if needed</span> **** Inhalt <div lang="en" dir="ltr" class="mw-content-ltr"> ==Formatting text== </div> {{main|Help:Formatting}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Formatting code examples and other technical elements=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Formatting distinguishes code and other technical elements from regular text. </div> {| class="wikitable" |+ !Purpose !Wiki-Markup !Result !Situation |- |Code |{{tag|code|content=code}} |<code>code</code> |Use for short strings of code, including wikitext markup. Within {{Tag|code}}, use <code><nowiki>''</nowiki></code>italics<code><nowiki>''</nowiki></code> to indicate variables and sample names so users know what to replace. |- |Syntax highlight | <syntaxhighlight lang="html"> <syntaxhighlight lang="css"> .citation { margin: 0; } </syntaxhighlight> </syntaxhighlight> Text before <syntaxhighlight lang=html inline><syntaxhighlight lang="css" inline>.foo {margin: 0;}</syntaxhighlight></syntaxhighlight> text after. |<syntaxhighlight lang="css"> .citation { margin: 0; } </syntaxhighlight> Text before <syntaxhighlight lang="css" inline="">.foo {margin: 0;}</syntaxhighlight> text after. |Use the {{tag|source|params={{attr|lang|"''...''"}} }} tag to document a few lines of code, and preserve whitespace and linebreaks. The <code>inline</code> attribute allows using it within an existing paragraph. Note you cannot use italic in the middle of a <syntaxhighlight lang="html inline><syntaxhighlight lang="foo">...</syntaxhighlight></syntaxhighlight> block, so you have to fall back to YOURPASSWORD or The_page_title to indicate variables. See [[Extension:SyntaxHighlight]] for more details. |- |Preformatted |{{tag|pre|content=preformatted text<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with indent}} |<pre>preformatted text with indent</pre> |Same as above (preserve whitespace and linebreaks), but without coloring. |- |Keyboard input |{{tag|kbd|content=keyboard 123}} (vs keyboard 123) |<kbd>keyboard 123</kbd> (vs keyboard 123) |Use {{tag|kbd}} for actual keyboard input - the text a user types into an input field or at a terminal command line. It displays in plain monospace. |- |Variables |{{tag|var|content=variable}} <code><nowiki>''</nowiki></code>italics<code><nowiki>''</nowiki></code> |<var>variable</var> ''italics'' |Use italics for variables like ''message-key-name'' and sample names like ''My page title''. Do not use punctuation such as &lt;YOURPASSWORD>, because readers don't know the angle brackets are noise and will type them. |- |Bold |<code><nowiki>'''</nowiki></code>bold<code><nowiki>'''</nowiki></code> |'''bold''' |Generally only used for the first instance of the page-title, and for rare emphasis of keywords to enable easier skimming of lists or paragraphs. Note: Sometimes '''bold''' is '''overused''' for emphasis. You may consider using a template instead, e.g. {{tl|Caution}}, {{tl|Note}}, or {{tl|Warning}}. |- |Quotations |<code>"</code>quotation marks<code>"</code> Text before {{tag|blockquote|content=blockquote}} Text after |"quotation marks" Text before<blockquote>blockquote</blockquote>Text after |Use quotation marks for brief pieces of content quoted from other sources. Use blockquote for longer pieces of content. |- |Abbreviations |JavaScript (JS) <syntaxhighlight lang=html inline><abbr title="JavaScript">JS</abbr></syntaxhighlight> |JavaScript (JS) <abbr title="JavaScript">JS</abbr> |You should define abbreviations the first time they are used. Use either plain text and parentheses, or the HTML abbr tag. |- |Keypress |<code>{{tl|key press|Ctrl|Shift|I}}</code> |{{key press|Ctrl|Shift|I}} |Showing specific keyboard presses or combinations. Extensive examples in [[Special:MyLanguage/VisualEditor/Portal/Keyboard shortcuts|VisualEditor/Portal/Keyboard shortcuts]]. Note: This template might not exist on other wikis. |- |Button |<code>{{tl|Button|<nowiki>{{int|showpreview}}</nowiki>}}</code> |{{button|{{int|showpreview}}}} |Showing UI buttons that need to be clicked on. Note: This template might not exist on other wikis. |} === Links === {{main|Help:Links}} {| class="wikitable" |+ !<span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Purpose</span> !<span lang="en" dir="ltr" class="mw-content-ltr">How to implement</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Example</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Local</span> |Link zu anderen MediaWiki-Seiten | * <code><nowiki>[[Foo]]</nowiki></code> * <code><nowiki>[[Foo|Bar]]</nowiki></code> |[[MediaWiki]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">Translated Target</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Link to other ''translated'' MediaWiki pages</span> |<code><nowiki>[[Special:MyLanguage/Foo|Foo]]</nowiki></code> |[[Special:MyLanguage/How to contribute|<span lang="en" dir="ltr" class="mw-content-ltr">How to contribute</span>]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">Interwiki</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Link to page belonging to a different Wikimedia project</span> | * <code><nowiki>[[</nowiki>phab:''T2001''<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">for tasks and project tags</span> * <code><nowiki>[[</nowiki>mail:''wikitech-l''<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">for mailing lists</span> * <code><nowiki>[[</nowiki>w:en:''foobar''<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">to English Wikipedia articles</span> * <code><nowiki>[[</nowiki>wikitech:''foobar''<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">for details about the WMF cluster</span> * <code><nowiki>[[</nowiki>gerrit:604435<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">for change requests in {{ll|Gerrit}}</span> |<span lang="en" dir="ltr" class="mw-content-ltr">[[w:en:Documentation|Documentation page on Wikipedia]]</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">External</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Link to external pages</span> |<code><nowiki>[https://www.example.org Example.org]</nowiki></code> |[https://dictionary.cambridge.org/dictionary/english/example Example] |} === Vorlagen === {{See also|Documentation/Style guide/templates|ll=1}} Vorlagen werden häufig auf MediaWiki.org-Seiten verwendet. <span lang="en" dir="ltr" class="mw-content-ltr">Templates can help to maintain consistency and can make it easier to translate information.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Below are some common templates. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Templates for page formatting==== </div> * {{tl|caution}}, {{tl|fixtext}}, {{tl|note}}, {{tl|tip}}, {{tl|todo}}, {{tl|warning}} - <span lang="en" dir="ltr" class="mw-content-ltr">for styles of inline highlight boxes</span> * {{tl|fixme}}, {{tl|historical}}, {{tl|notice}}, {{tl|outdated}}, {{tl|update}} - <span lang="en" dir="ltr" class="mw-content-ltr">for page/section message boxes</span> * {{tl|main}}, {{tl|see also}} - <span lang="en" dir="ltr" class="mw-content-ltr">for page/section hatnotes (a short note placed at the top of an article)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Templates for MediaWiki core and Git source==== </div> * {{tl|class doclink}}, {{tl|file doclink}}, {{tl|js doclink}} - <span lang="en" dir="ltr" class="mw-content-ltr">to link to MediaWiki core's [https://doc.wikimedia.org/mediawiki-core/master/php/ generated documentation]</span> * {{tl|MW file}} - <span lang="en" dir="ltr" class="mw-content-ltr">for a box with info and links for a file in MediaWiki core</span> * {{tl|git file}} - <span lang="en" dir="ltr" class="mw-content-ltr">to link to source code</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Templates for Phabricator==== </div> * {{tl|ptag}} - <span lang="en" dir="ltr" class="mw-content-ltr">for the top-right-of-page Phabricator project tag</span> * {{tl|tracked}} - <span lang="en" dir="ltr" class="mw-content-ltr">for the related Phabricator task</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Other useful templates==== </div> * {{tlx|irc|wikimedia-tech}} - <span lang="en" dir="ltr" class="mw-content-ltr">for IRC link</span> * {{tl|Key press}} - <span lang="en" dir="ltr" class="mw-content-ltr">for, e.g. {{Key press|Ctrl|Shift|I}}, and {{tl|button}} for, e.g. {{button|{{int|showpreview}}}}</span> * {{tl|ApiEx}} - <span lang="en" dir="ltr" class="mw-content-ltr">for api.php request URLs</span> * {{tl|Api help}} - <span lang="en" dir="ltr" class="mw-content-ltr">to transclude generated API documentation</span> * {{tl|wg|RestOfVariableName}} - für globale Variablen * {{tl|tag}} - <span lang="en" dir="ltr" class="mw-content-ltr">for a quick way to mention an XML-style tag in a preformatted way</span> == Übersetzungen == <span lang="en" dir="ltr" class="mw-content-ltr">All pages on mediawiki.org are candidates for translation into multiple languages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki.org is a multilingual wiki, it uses the [[Special:MyLanguage/Extension:Translate|Translate extension]] to present alternative translations and [[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration|manage the translation of pages]].</span> {{tip|1=<nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * If a page has been translated, then click 'Edit source' to edit the entire page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration#Markup_examples|Wrongly placed]] translation tag markers around section headings can confuse section editing, and as of July 2015 VisualEditor does not understand the following tags:</span> {{tag|languages|open}}, {{tag|translate|open}}, {{tag|tvar|open}} <div lang="en" dir="ltr" class="mw-content-ltr"> * Do not copy and paste existing markup. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If in doubt, focus on writing a good text and let someone else handle the Translate markup.</span> }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Further information == </div> *[[Documentation/Technical writer guide]] *[[Documentation/Technical documentation prioritization]] == Siehe auch == * <span lang="en" dir="ltr" class="mw-content-ltr">Some other technical documentation style guides:</span> ** [https://developers.google.com/style/ <span lang="en" dir="ltr" class="mw-content-ltr">Google Developer Documentation Style Guide</span>] ** [https://developer.mozilla.org/docs/MDN/Guidelines/Writing_style_guide <span lang="en" dir="ltr" class="mw-content-ltr">MDN Web Docs Writing Style Guide</span>] * [[Wikiversity:Technical writing]] * <span lang="en" dir="ltr" class="mw-content-ltr">Other language related resources:</span> ** {{ll|Inclusive language}} ** [https://developers.google.com/style/word-list <span lang="en" dir="ltr" class="mw-content-ltr">word-list</span>] ** [[Naming things]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Footnotes == </div> <references /> {{Conventions navigation}} [[Category:Documentation{{#translation:}}]] 0ownpfwcm83o2dpp82y1rk4chjslik1 5387084 5387082 2022-07-28T20:21:28Z ThisCarthing 17456337 Created page with "Positiv" wikitext text/x-wiki <languages/> == Überblick == <span lang="en" dir="ltr" class="mw-content-ltr">This style guide provides guidance for writing and editing technical documentation in MediaWiki and other technical spaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It provides tips to help you write clear, concise technical documentation in plain language. It also links to additional resources about technical writing and editing in general.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Good technical documentation makes it easier for people to contribute to Wikimedia projects.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to follow clear standards and style guidelines for writing and editing documentation, especially when the contributors and readers have varying levels of skills and experience.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not you consider yourself a writer, your contributions are needed and appreciated!</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===English Wikipedia Manual of Style=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[w:WP:MOS|English Wikipedia's Manual of style]] covers general writing topics (like punctuation) in detail, and summarizes the key points of other style guides.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It can be a useful reference for anyone writing or editing technical documentation in English across Wikimedia projects, especially if the local wiki doesn't have more specific guidelines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This page provides basic guidelines and tips to help get you started with technical documentation. It includes some information specific to technical documentation that is not covered in the Wikipedia Manual of Style.</span> {{TOC|align=right}} == Leserschaft und Inhalt == === Für technische Leserschaften schreiben === <div lang="en" dir="ltr" class="mw-content-ltr"> Before you begin writing, consider the audience for your work: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Who will read this technical documentation? </div> * Wo kommen sie her? <div lang="en" dir="ltr" class="mw-content-ltr"> * How familiar are they with the concepts you are presenting? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * What might they need to know in order to understand? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once you have an understanding of your audience, you will have a better sense of what you need to communicate. </div> {{tip|1=<nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * If you know your audience is ''highly technical and familiar'' with the processes you are describing, then you ''do not need to explain'' basic concepts. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * If you know your audience is ''learning or unfamiliar'' with the processes you are describing, then ''include explanations'' of basic concepts ''and links'' to additional information. </div> }} <div lang="en" dir="ltr" class="mw-content-ltr"> === Writing with a purpose === </div> <span lang="en" dir="ltr" class="mw-content-ltr">What purpose will your technical documentation serve? There are many reasons to write documentation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is helpful to know ''why'' you are writing and what your goal is before you begin.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Is it to teach someone, like a newcomer, about a process or concept? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Is it to show someone how to follow a process? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Is it meant to provide background and context for a concept or process? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Is it a reference intended to provide information? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Writing within a context === </div> <span lang="en" dir="ltr" class="mw-content-ltr">When deciding what to write and how to frame it for your reader, it can help to define a context or occasion for your writing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Your communication takes place in the context of a bigger situation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The context may be bounded by the era you are writing in, the type of technology available, your geographical location and culture, or the current culture and communication styles of your readers.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The occasion may be personal and arise from the situation that motivated you to create or improve a piece of documentation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you are writing technical documentation for Wikimedia projects, consider the culture created by the individuals who participate in those projects.</span> <span lang="en" dir="ltr" class="mw-content-ltr">How could you best position your writing within the context of this community and its culture to create the most meaningful and useful technical documentation?</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === User testing and feedback === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Create technical documentation to communicate ideas and concepts to a real audience of users.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Naturally, this audience should play a critical role in how the documentation is shaped and reshaped.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Think about ways you can gather information about your users' experiences.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Take some time to answer the following questions:</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Does your documentation include a mechanism for feedback? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Can you engage in timely conversations with the audience to make improvements? </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Can you use forums like Stack Overflow or mailing lists to check if your document answers the most common questions people have about your specific topic?</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Clarity and consistency === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Clarity and consistency makes it easier to access, read, and create technical documentation across MediaWiki/Wikimedia projects.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Technical documentation is written for a wide audience and edited by a variety of contributors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Voice, tone, grammar usage, style, and format should be consistent across technical documentation and similar content collections.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This helps readers learn how to navigate information and makes it easier for contributors to understand how to edit and add new information.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Deciding on a document type === </div> {{see also|Documentation/Technical documentation templates and suggestions|ll=1}} <div lang="en" dir="ltr" class="mw-content-ltr"> Identify your main audience, purpose, and context first to decide on the type of document you will create. </div> {| class="wikitable" |+ !Beispielleserschaft !Zweck<ref>https://www.divio.com/en/blog/documentation/</ref> !<span lang="en" dir="ltr" class="mw-content-ltr">Potential Document Types</span> !Beispiel |- |<span lang="en" dir="ltr" class="mw-content-ltr">Newcomer interested in learning how to become a Toolforge user</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To learn</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Tutorial, FAQ, Getting Started guide</span> |[[wikitech:Help:FAQ#Cloud_VPS|<span lang="en" dir="ltr" class="mw-content-ltr">Cloud VPS and Toolforge FAQ</span>]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">Experienced technical contributor trying to work through a known problem</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To achieve a goal</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Walk-through, How-To guide</span> |[[wikitech:Help:Toolforge/My_first_Flask_OAuth_tool|<span lang="en" dir="ltr" class="mw-content-ltr">My First Flask OAuth Tool</span>]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">Individual trying to understand the history of ORES and how it evolved</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To understand</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Explanatory article, blog post, "overview"</span> |[[wmfblog:2015/11/30/artificial-intelligence-x-ray-specs/|<span lang="en" dir="ltr" class="mw-content-ltr">Artificial intelligence service “ORES” gives Wikipedians X-ray specs to see through bad edits</span>]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">A person looking for a definition of SSH keys</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To inform</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Reference guide, glossary</span> |[[wikitech:Help:Glossary|Glossar]] |} == Sprache == {{see also|wikiversity:Technical_writing_style|label 1=<span lang="en" dir="ltr" class="mw-content-ltr">The "Writing clearly" article on Wikiversity</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">This section briefly mentions some topics worth exploring elsewhere in more detail.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Always check your words and expressions against these criteria on [[wikt:|Wiktionary]]:</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiktionary entries cover hundreds of languages, explicitly state the grammatical and lexical features of words and their declensions, provide detailed context labels (including about jargon, UK vs. USA English) and expose how translatable terms are in hundreds of other languages.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Plain English === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please remember: many visitors to these pages are not native English speakers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For documentation written in English, [[w:Plain English|Plain English]] (also called [[w:plain language|plain language]]) works best.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Clear writing is the most understandable by diverse audiences, and is also easiest to translate.</span> <span lang="en" dir="ltr" class="mw-content-ltr">There are a number of good tools for checking your writing, at [[m:Special:MyLanguage/Tech/News/Manual#Guidelines|Tech News' Writing Guidelines on Meta-Wiki.]]</span> {{tip|1=<nowiki/> * <span lang="en" dir="ltr" class="mw-content-ltr">Avoid ambiguity, jargon, and vague or complex wording.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Use words your audience will understand, and enough words to convey your message.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Define terms that may not be obvious to individuals who are new to the subject matter you are writing about.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Keep paragraphs and sentences short and concise.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Use contractions or don't. Be consistent.</span> }} <div lang="en" dir="ltr" class="mw-content-ltr"> === Voice and tone === </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki is a place where anyone can edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Thus, it can be difficult to maintain a consistent voice and tone in the documentation.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Consider using these elements in your writing: </div> {| class="wikitable" !<span lang="en" dir="ltr" class="mw-content-ltr">Voice and tone</span> !<span lang="en" dir="ltr" class="mw-content-ltr">What this means</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Instead of this</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Try This</span> |- |Freundlich |<span lang="en" dir="ltr" class="mw-content-ltr">Technical documentation does not need to sound academic or dry.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Write to your audience as if they are there in person.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Before beginning, the user must create an account.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Start by creating an account.</span> |- |Professionell |Technische Dokumentation kann freundlich sein, sollte jedoch professionell bleiben. Verwende {{ll|Inclusive language}}. |<span lang="en" dir="ltr" class="mw-content-ltr">Don't make a bazillion changes.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Try to make minimum changes.</span> |- |Positiv |<span lang="en" dir="ltr" class="mw-content-ltr">Avoid using negative sentence constructions. Explain things in terms of what to do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is harder to mentally parse a complex negative sentence!</span> |<span lang="en" dir="ltr" class="mw-content-ltr">''N'' won't happen, if you don't ''XYZ''.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">To make ''N'' happen, do ''XYZ''.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Active</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Try to use [[w:Active voice|active voice]], except when diplomacy calls for [[w:Passive voice|passive voice]].</span> |<span lang="en" dir="ltr" class="mw-content-ltr">The extension must be registered.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">You must register the extension.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Non-gendered</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Adopt [[w:Gender-neutral language|gender-inclusive language]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Assume your audience comprises all gender identities.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">When he clicks Save</span> |<span lang="en" dir="ltr" class="mw-content-ltr">When the user clicks Save</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Inclusive</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Use alternatives to common words or phrases that may unintentionally reinforce inappropriate stereotypes.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">This UI is crazy.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">This UI could be improved.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Free of frustration</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Avoid terms like "easy" and "simple" which can be frustrating for less tech-savvy users.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Simply create a user account.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Create a user account.</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Free of colloquialisms</span> |<span lang="en" dir="ltr" class="mw-content-ltr">It can be confusing to use [[w:Colloquialism|colloquialisms]], jokes, puns, or ''turns of phrase'' that non-native English speakers or individuals from other regions might not easily understand.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Creating a user account is a piece of cake.</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Creating a user account requires two steps.</span> |} {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This is not meant to be an exhaustive list or a strict set of rules.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Point of view=== </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The following guidance overrides the general Wikipedia style guidelines for [[w:Wikipedia:Manual_of_Style#First-person_pronouns|pronouns]], but only for technical documentation.</span>}} * <span lang="en" dir="ltr" class="mw-content-ltr">Use [[w:Grammatical_person|second person]] ("You" or assumed "You") when addressing your audience.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Avoid [[w:Grammatical_person|first person]] ("I" or "we"), unless you are writing a FAQ with questions asked from the first person perspective.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Use an [[w:Imperative_mood|imperative mood]] for most documentation focused on goals or process.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Dates=== </div> * Verwende immer das vollständige, vierstellige Jahr. * <span lang="en" dir="ltr" class="mw-content-ltr">Use absolute dates ("in May 2037") instead of relative dates ("next year in May").</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Avoid adding dates that will require regular manual updates. Example: Write <code><nowiki>{{#time: Y }}</nowiki></code> instead of {{#time: Y }} when referring to the current year, no matter what year it is currently.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Structuring pages == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Overview === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All pages should include an overview section (also called the [[w:Wikipedia:Manual_of_Style/Lead_section|Lead section]]) that explains: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Purpose of the page</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Audience of the page</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Prerequisites the reader will need to know before proceeding (Ex. a working knowledge of Python)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Software or tools the reader will need to complete the processes or tasks outlined on the page (Ex. Java installed)</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Use case, case study, a practical understanding of the product, service or tool in action. (optional)</span> === Inhaltsverzeichnis === * <span lang="en" dir="ltr" class="mw-content-ltr">Each page should include a table of contents, so information can be accessed easily.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Titles and headers === </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Use [[w:Letter_case#Sentence_case | sentence case]] for headers.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Keep header fonts consistent throughout documentation.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Optional use of [[w:Help:Link#Section_linking_(anchors)|anchors]] to link sections or subsections in the same page.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add a blank line after section headers. This impacts [[Special:MyLanguage/Help:Extension:Translate/Page_translation_example#About_titles|how the content is packaged for translation]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Do not put a header before your overview or lead section.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Information flow === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Technical documentation pages should follow a consistent pattern across content collections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''An ideal pattern''' for each page might be: </div> * Seitentitel * Einführung/Übersicht * <span lang="en" dir="ltr" class="mw-content-ltr">Header</span> ** Inhalt *** <span lang="en" dir="ltr" class="mw-content-ltr">Subhead if needed</span> **** Inhalt <div lang="en" dir="ltr" class="mw-content-ltr"> ==Formatting text== </div> {{main|Help:Formatting}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Formatting code examples and other technical elements=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Formatting distinguishes code and other technical elements from regular text. </div> {| class="wikitable" |+ !Purpose !Wiki-Markup !Result !Situation |- |Code |{{tag|code|content=code}} |<code>code</code> |Use for short strings of code, including wikitext markup. Within {{Tag|code}}, use <code><nowiki>''</nowiki></code>italics<code><nowiki>''</nowiki></code> to indicate variables and sample names so users know what to replace. |- |Syntax highlight | <syntaxhighlight lang="html"> <syntaxhighlight lang="css"> .citation { margin: 0; } </syntaxhighlight> </syntaxhighlight> Text before <syntaxhighlight lang=html inline><syntaxhighlight lang="css" inline>.foo {margin: 0;}</syntaxhighlight></syntaxhighlight> text after. |<syntaxhighlight lang="css"> .citation { margin: 0; } </syntaxhighlight> Text before <syntaxhighlight lang="css" inline="">.foo {margin: 0;}</syntaxhighlight> text after. |Use the {{tag|source|params={{attr|lang|"''...''"}} }} tag to document a few lines of code, and preserve whitespace and linebreaks. The <code>inline</code> attribute allows using it within an existing paragraph. Note you cannot use italic in the middle of a <syntaxhighlight lang="html inline><syntaxhighlight lang="foo">...</syntaxhighlight></syntaxhighlight> block, so you have to fall back to YOURPASSWORD or The_page_title to indicate variables. See [[Extension:SyntaxHighlight]] for more details. |- |Preformatted |{{tag|pre|content=preformatted text<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with indent}} |<pre>preformatted text with indent</pre> |Same as above (preserve whitespace and linebreaks), but without coloring. |- |Keyboard input |{{tag|kbd|content=keyboard 123}} (vs keyboard 123) |<kbd>keyboard 123</kbd> (vs keyboard 123) |Use {{tag|kbd}} for actual keyboard input - the text a user types into an input field or at a terminal command line. It displays in plain monospace. |- |Variables |{{tag|var|content=variable}} <code><nowiki>''</nowiki></code>italics<code><nowiki>''</nowiki></code> |<var>variable</var> ''italics'' |Use italics for variables like ''message-key-name'' and sample names like ''My page title''. Do not use punctuation such as &lt;YOURPASSWORD>, because readers don't know the angle brackets are noise and will type them. |- |Bold |<code><nowiki>'''</nowiki></code>bold<code><nowiki>'''</nowiki></code> |'''bold''' |Generally only used for the first instance of the page-title, and for rare emphasis of keywords to enable easier skimming of lists or paragraphs. Note: Sometimes '''bold''' is '''overused''' for emphasis. You may consider using a template instead, e.g. {{tl|Caution}}, {{tl|Note}}, or {{tl|Warning}}. |- |Quotations |<code>"</code>quotation marks<code>"</code> Text before {{tag|blockquote|content=blockquote}} Text after |"quotation marks" Text before<blockquote>blockquote</blockquote>Text after |Use quotation marks for brief pieces of content quoted from other sources. Use blockquote for longer pieces of content. |- |Abbreviations |JavaScript (JS) <syntaxhighlight lang=html inline><abbr title="JavaScript">JS</abbr></syntaxhighlight> |JavaScript (JS) <abbr title="JavaScript">JS</abbr> |You should define abbreviations the first time they are used. Use either plain text and parentheses, or the HTML abbr tag. |- |Keypress |<code>{{tl|key press|Ctrl|Shift|I}}</code> |{{key press|Ctrl|Shift|I}} |Showing specific keyboard presses or combinations. Extensive examples in [[Special:MyLanguage/VisualEditor/Portal/Keyboard shortcuts|VisualEditor/Portal/Keyboard shortcuts]]. Note: This template might not exist on other wikis. |- |Button |<code>{{tl|Button|<nowiki>{{int|showpreview}}</nowiki>}}</code> |{{button|{{int|showpreview}}}} |Showing UI buttons that need to be clicked on. Note: This template might not exist on other wikis. |} === Links === {{main|Help:Links}} {| class="wikitable" |+ !<span lang="en" dir="ltr" class="mw-content-ltr">Type</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Purpose</span> !<span lang="en" dir="ltr" class="mw-content-ltr">How to implement</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Example</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Local</span> |Link zu anderen MediaWiki-Seiten | * <code><nowiki>[[Foo]]</nowiki></code> * <code><nowiki>[[Foo|Bar]]</nowiki></code> |[[MediaWiki]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">Translated Target</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Link to other ''translated'' MediaWiki pages</span> |<code><nowiki>[[Special:MyLanguage/Foo|Foo]]</nowiki></code> |[[Special:MyLanguage/How to contribute|<span lang="en" dir="ltr" class="mw-content-ltr">How to contribute</span>]] |- |<span lang="en" dir="ltr" class="mw-content-ltr">Interwiki</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Link to page belonging to a different Wikimedia project</span> | * <code><nowiki>[[</nowiki>phab:''T2001''<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">for tasks and project tags</span> * <code><nowiki>[[</nowiki>mail:''wikitech-l''<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">for mailing lists</span> * <code><nowiki>[[</nowiki>w:en:''foobar''<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">to English Wikipedia articles</span> * <code><nowiki>[[</nowiki>wikitech:''foobar''<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">for details about the WMF cluster</span> * <code><nowiki>[[</nowiki>gerrit:604435<nowiki>]]</nowiki></code> <span lang="en" dir="ltr" class="mw-content-ltr">for change requests in {{ll|Gerrit}}</span> |<span lang="en" dir="ltr" class="mw-content-ltr">[[w:en:Documentation|Documentation page on Wikipedia]]</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">External</span> |<span lang="en" dir="ltr" class="mw-content-ltr">Link to external pages</span> |<code><nowiki>[https://www.example.org Example.org]</nowiki></code> |[https://dictionary.cambridge.org/dictionary/english/example Example] |} === Vorlagen === {{See also|Documentation/Style guide/templates|ll=1}} Vorlagen werden häufig auf MediaWiki.org-Seiten verwendet. <span lang="en" dir="ltr" class="mw-content-ltr">Templates can help to maintain consistency and can make it easier to translate information.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Below are some common templates. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Templates for page formatting==== </div> * {{tl|caution}}, {{tl|fixtext}}, {{tl|note}}, {{tl|tip}}, {{tl|todo}}, {{tl|warning}} - <span lang="en" dir="ltr" class="mw-content-ltr">for styles of inline highlight boxes</span> * {{tl|fixme}}, {{tl|historical}}, {{tl|notice}}, {{tl|outdated}}, {{tl|update}} - <span lang="en" dir="ltr" class="mw-content-ltr">for page/section message boxes</span> * {{tl|main}}, {{tl|see also}} - <span lang="en" dir="ltr" class="mw-content-ltr">for page/section hatnotes (a short note placed at the top of an article)</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Templates for MediaWiki core and Git source==== </div> * {{tl|class doclink}}, {{tl|file doclink}}, {{tl|js doclink}} - <span lang="en" dir="ltr" class="mw-content-ltr">to link to MediaWiki core's [https://doc.wikimedia.org/mediawiki-core/master/php/ generated documentation]</span> * {{tl|MW file}} - <span lang="en" dir="ltr" class="mw-content-ltr">for a box with info and links for a file in MediaWiki core</span> * {{tl|git file}} - <span lang="en" dir="ltr" class="mw-content-ltr">to link to source code</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Templates for Phabricator==== </div> * {{tl|ptag}} - <span lang="en" dir="ltr" class="mw-content-ltr">for the top-right-of-page Phabricator project tag</span> * {{tl|tracked}} - <span lang="en" dir="ltr" class="mw-content-ltr">for the related Phabricator task</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Other useful templates==== </div> * {{tlx|irc|wikimedia-tech}} - <span lang="en" dir="ltr" class="mw-content-ltr">for IRC link</span> * {{tl|Key press}} - <span lang="en" dir="ltr" class="mw-content-ltr">for, e.g. {{Key press|Ctrl|Shift|I}}, and {{tl|button}} for, e.g. {{button|{{int|showpreview}}}}</span> * {{tl|ApiEx}} - <span lang="en" dir="ltr" class="mw-content-ltr">for api.php request URLs</span> * {{tl|Api help}} - <span lang="en" dir="ltr" class="mw-content-ltr">to transclude generated API documentation</span> * {{tl|wg|RestOfVariableName}} - für globale Variablen * {{tl|tag}} - <span lang="en" dir="ltr" class="mw-content-ltr">for a quick way to mention an XML-style tag in a preformatted way</span> == Übersetzungen == <span lang="en" dir="ltr" class="mw-content-ltr">All pages on mediawiki.org are candidates for translation into multiple languages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki.org is a multilingual wiki, it uses the [[Special:MyLanguage/Extension:Translate|Translate extension]] to present alternative translations and [[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration|manage the translation of pages]].</span> {{tip|1=<nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * If a page has been translated, then click 'Edit source' to edit the entire page. </div> <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Help:Extension:Translate/Page_translation_administration#Markup_examples|Wrongly placed]] translation tag markers around section headings can confuse section editing, and as of July 2015 VisualEditor does not understand the following tags:</span> {{tag|languages|open}}, {{tag|translate|open}}, {{tag|tvar|open}} <div lang="en" dir="ltr" class="mw-content-ltr"> * Do not copy and paste existing markup. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If in doubt, focus on writing a good text and let someone else handle the Translate markup.</span> }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Further information == </div> *[[Documentation/Technical writer guide]] *[[Documentation/Technical documentation prioritization]] == Siehe auch == * <span lang="en" dir="ltr" class="mw-content-ltr">Some other technical documentation style guides:</span> ** [https://developers.google.com/style/ <span lang="en" dir="ltr" class="mw-content-ltr">Google Developer Documentation Style Guide</span>] ** [https://developer.mozilla.org/docs/MDN/Guidelines/Writing_style_guide <span lang="en" dir="ltr" class="mw-content-ltr">MDN Web Docs Writing Style Guide</span>] * [[Wikiversity:Technical writing]] * <span lang="en" dir="ltr" class="mw-content-ltr">Other language related resources:</span> ** {{ll|Inclusive language}} ** [https://developers.google.com/style/word-list <span lang="en" dir="ltr" class="mw-content-ltr">word-list</span>] ** [[Naming things]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Footnotes == </div> <references /> {{Conventions navigation}} [[Category:Documentation{{#translation:}}]] 465q9f7r7ltci9f5rmxhemkc7m0fpen Extension:CLDR/de 102 1427490 5386956 5330268 2022-07-28T19:47:16Z ThisCarthing 17456337 Created page with "=== Landesnamen ===" wikitext text/x-wiki <languages/> {{Extension |status = stable |author = * [[User:Nikerabbit|Niklas Laxström]] * Siebrand Mazeland * [[User:Kaldari|Ryan Kaldari]] * Sam Reed |license = GPL-2.0-or-later, data [http://unicode.org/copyright.html#Exhibit1 variant of BSD 3-clauses] |type = parser function |image = ExampleOfCLDRExtension.png |version = |update = Laufende Aktualisierungen |compatibility = master |mediawiki = 1.30+ |download = {{ll|MediaWiki Language Extension Bundle|Enthalten im Spracherweiterungspaket}} oder {{WikimediaDownload|cldr}} |needs-updatephp = No |readme = {{git file|action=raw|project=mediawiki/extensions/cldr|file=README|text=README}} |changelog = |description = Bietet Funktionen zur Lokalisierung der Namen von Sprachen, Ländern, Währungen und Zeiteinheiten auf der Grundlage ihres Sprachcodes. |parameters = |tags = |rights = |example = [[betawiki:|Translatewiki.net]] |pagedrive1 = true |composer = mediawiki/cldr }} Die Erweiterung '''CLDR''' enthält lokale Sprachnamen für verschiedene Sprachen, Länder, Währungen und Zeiteinheiten, die aus [[w:Common Locale Data Repository|CLDR]]-Daten extrahiert wurden. Siehe [[translatewiki:CLDR]] für Informationen. == Installation == {{ExtensionInstall |cldr |repo-name=cldr |registration=required }} Wenn Sie von git herunterladen, ändern Sie die Datei von CLDR in cldr. == Aktualisierung der Daten == Die CLDR-Erweiterung enthält bereits Daten in den Sprachdateien, aber wenn Sie die neuesten Daten vom Unicode-Konsortium erhalten möchten, müssen Sie sie von der CLDR-Website herunterladen und dann ein Rebuild-Skript ausführen. Laden Sie die neuesten Daten von der CLDR-Website herunter: http://www.unicode.org/cldr/repository_access.html Beispiel (aus dem cldr-Verzeichnis): <syntaxhighlight lang="bash"> wget http://www.unicode.org/Public/cldr/latest/core.zip unzip core.zip -d core php rebuild.php </syntaxhighlight> == Verwendung und Parameter == === Sprachnamen === <span lang="en" dir="ltr" class="mw-content-ltr">CLDR defines the class LanguageNames which has a static method, <code>getNames()</code>.</span> {{phpi|LanguageNames::getNames}} nimmt drei Parameter entgegen: # code - <span lang="en" dir="ltr" class="mw-content-ltr">the [[w:ISO 639|ISO 639]] (see [[Special:MyLanguage/Manual:Language#Language code|Manual:Language#Language code]] for details) code of the preferred language to return the list in</span> # fbMethod - <span lang="en" dir="ltr" class="mw-content-ltr">fallback method, it should be set to one of the following:</span> #* '''LanguageNames::FALLBACK_NATIVE''' - <span lang="en" dir="ltr" class="mw-content-ltr">Missing entries fallback to the native name (default)</span> #* '''LanguageNames::FALLBACK_NORMAL''' - <span lang="en" dir="ltr" class="mw-content-ltr">Missing entries fallback through the fallback chain</span> # list - <span lang="en" dir="ltr" class="mw-content-ltr">which languages to return.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Should be set to one of the following:</span> #* '''LanguageNames::LIST_MW_SUPPORTED''' - <span lang="en" dir="ltr" class="mw-content-ltr">Only languages that have localization in MediaWiki</span> #* '''LanguageNames::LIST_MW''' - <span lang="en" dir="ltr" class="mw-content-ltr">All languages that are in <code>Names.php</code> (default)</span> #* '''LanguageNames::LIST_MW_AND_CLDR''' - <span lang="en" dir="ltr" class="mw-content-ltr">All languages that are either in MediaWiki or in CLDR</span> ==== Beispiel ==== <div lang="en" dir="ltr" class="mw-content-ltr"> The language names are best access with MediaWiki core functions: </div> <syntaxhighlight lang="php"> // Japanisch $name = Language::fetchLanguageName( 'ja', 'de', 'all' ); </syntaxhighlight> === Landesnamen === <span lang="en" dir="ltr" class="mw-content-ltr">CLDR defines the class <code>CountryNames</code> which has a static method, <code>getNames()</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{phpi|CountryNames::getNames}} accepts one parameter:</span> # code - <span lang="en" dir="ltr" class="mw-content-ltr">the [[w:ISO 639|ISO 639]] code of the preferred language to return the list in</span> ==== Beispiel ==== <div lang="en" dir="ltr" class="mw-content-ltr"> The following example sets a variable to the list of all countries in CLDR in French. </div> <syntaxhighlight lang="php"> if ( is_callable( array( 'CountryNames', 'getNames' ) ) ) { $countries = CountryNames::getNames( 'fr' ); } </syntaxhighlight> <!-- === Time units === ==== Example ==== The following example sets a variable to the list of all time units in CLDR in Spanish. <syntaxhighlight lang=php> if ( is_callable( array( 'TimeUnits', 'getUnits' ) ) ) { $timeUnits = TimeUnits::getUnits( 'es' ); } </syntaxhighlight> --> == Siehe auch == * {{ll|Extension:I18nTags|Extension:I18nTags}} * {{ll|Extension:Babel|Extension:Babel}} {{OnWikimedia}} {{Used by|fandom=1|miraheze=1|mleb=1|prowiki=1}} [[Category:Localisation extensions{{#translation:}}]] 2bxxa3ihw2wxjfrrzzw6layhialcoa7 Extension:DebugMode/de 102 1427517 5386879 4859852 2022-07-28T19:34:18Z ThisCarthing 17456337 Created page with "Setzt das Wiki im Debugmodus" wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = unmaintained |type1 = interface |type2 = |hook1 = <!-- default / custom hooks used, see [[Template:Extension]] for details --> |hook2 = |username = Tosfos |author = Ike Hecht |description = Setzt das Wiki im Debugmodus |image = |imagesize = |version = 0.1.0 |update = 2014-10-28 |version preview = |update preview = |mediawiki = 1.23 |php = 5.3 |needs-updatephp = No |composer = |table1 = |table2 = |license = GPL-2.0+ |download = {{WikimediaDownload}} |readme = |changelog = |example = |namespace = |parameters = * <syntaxhighlight lang="php" inline="">$wgDebugMode</syntaxhighlight> * <syntaxhighlight lang="php" inline="">$wgDebugModeIgnoreVars</syntaxhighlight> |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |bugzilla = }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''DebugMode''' extension puts the wiki into debug mode, which means all MediaWiki debugging parameters are switched on. </div> == Installation == {{ExtensionInstall|DebugMode}} == Konfigurationsparameter == ; <syntaxhighlight lang="php" inline="">$wgDebugMode</syntaxhighlight> : <span lang="en" dir="ltr" class="mw-content-ltr">Level of debugging.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Can be set to <syntaxhighlight lang="php" inline="">true</syntaxhighlight> to enable all debugging or <syntaxhighlight lang="php" inline="">false</syntaxhighlight> to do nothing.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Setting to <syntaxhighlight lang="php" inline="">false</syntaxhighlight> does not turn debugging off!</span> <span lang="en" dir="ltr" class="mw-content-ltr">It just leaves the existing settings alone.</span>}} : <span lang="en" dir="ltr" class="mw-content-ltr">Can be set using named constants in the DebugMode class, using bitwise operators:</span> :* <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_NONE</syntaxhighlight>: <span lang="en" dir="ltr" class="mw-content-ltr">the extension does nothing, equivalent to <syntaxhighlight lang="php" inline="">false</syntaxhighlight>;</span><br /><span lang="en" dir="ltr" class="mw-content-ltr">Except in this mode, the following MediaWiki’s parameters are activated:</span> :** <code>{{ll|Manual:$wgColorErrors|$wgColorErrors}}</code> :** <code>{{ll|Manual:$wgDebugAPI|$wgDebugAPI}}</code> :** <code>{{ll|Manual:$wgDebugComments|$wgDebugComments}}</code> :** <code>{{ll|Manual:$wgDebugDBTransactions|$wgDebugDBTransactions}}</code> :** <code>{{ll|Manual:$wgDebugDumpSql|$wgDebugDumpSql}}</code> :** <code>{{ll|Manual:$wgDebugFunctionEntry|$wgDebugFunctionEntry}}</code> :** <code>{{ll|Manual:$wgDebugPrintHttpHeaders|$wgDebugPrintHttpHeaders}}</code> :** <code>{{ll|Manual:$wgDebugTimestamps|$wgDebugTimestamps}}</code> :** <code>{{ll|Manual:$wgDebugToolbar|$wgDebugToolbar}}</code> :** <code>{{ll|Manual:$wgDevelopmentWarnings|$wgDevelopmentWarnings}}</code> :** <code>{{ll|Manual:$wgLogExceptionBacktrace|$wgLogExceptionBacktrace}}</code> :** <code>{{ll|Manual:$wgShowDBErrorBacktrace|$wgShowDBErrorBacktrace}}</code> :** <code>{{ll|Manual:$wgShowExceptionDetails|$wgShowExceptionDetails}}</code> :** <code>{{ll|Manual:$wgShowSQLErrors|$wgShowSQLErrors}}</code> :** <span lang="en" dir="ltr" class="mw-content-ltr"><code>{{ll|Manual:$wgProfileLimit|$wgProfileLimit}}</code> is set to <syntaxhighlight lang="php" inline="">0.0</syntaxhighlight>,</span> :* <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_INI</syntaxhighlight>: <span lang="en" dir="ltr" class="mw-content-ltr">set PHP’s <code>[https://php.net/errorfunc.configuration#ini.display-errors display_errors]</code> to <syntaxhighlight lang="php" inline="">true</syntaxhighlight>;</span> :* <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_PHP</syntaxhighlight>: <span lang="en" dir="ltr" class="mw-content-ltr">set PHP’s <code>[https://php.net/errorfunc.configuration#ini.error-reporting error_reporting]</code> to <syntaxhighlight lang="php" inline="">-1</syntaxhighlight> (all debugging messages);</span> :* <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_VERBOSE</syntaxhighlight>: <span lang="en" dir="ltr" class="mw-content-ltr">activate MediaWiki’s <code>{{ll|Manual:$wgShowDebug|$wgShowDebug}}</code>;</span> :* <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_CACHE</syntaxhighlight>: <span lang="en" dir="ltr" class="mw-content-ltr">deactivate MediaWiki’s <code>{{ll|Manual:$wgCachePages|$wgCachePages}}</code>, <code>{{ll|Manual:$wgDeprecationReleaseLimit|$wgDeprecationReleaseLimit}}</code>, and <code>{{ll|Manual:$wgEnableParserCache|$wgEnableParserCache}}</code>;</span> :* <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_RESOURCE_LOADER</syntaxhighlight>: <span lang="en" dir="ltr" class="mw-content-ltr">activate MediaWiki’s <code>{{ll|Manual:$wgResourceLoaderDebug|$wgResourceLoaderDebug}}</code> and set MediaWiki’s <code>{{ll|Manual:$wgResourceLoaderMaxage|$wgResourceLoaderMaxage}}</code> to <syntaxhighlight lang="php" inline="">1</syntaxhighlight>;</span> :* <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_INSECURE</syntaxhighlight>: <span lang="en" dir="ltr" class="mw-content-ltr">(unused);</span> :* <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_ALL</syntaxhighlight>: <span lang="en" dir="ltr" class="mw-content-ltr">all debugging modes are activated, equivalent to <syntaxhighlight lang="php" inline="">true</syntaxhighlight>.</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Default value is a reasonable level of debugging, which is <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_ALL</syntaxhighlight> minus <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_VERBOSE</syntaxhighlight>.</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example: <syntaxhighlight lang="php" inline="">DebugMode::DEBUG_MODE_ALL ^ DebugMode::DEBUG_MODE_INI ^ DebugMode::DEBUG_MODE_PHP</syntaxhighlight> for “all but no PHP settings”.</span> ; <syntaxhighlight lang="php" inline="">$wgDebugModeIgnoreVars</syntaxhighlight> : <span lang="en" dir="ltr" class="mw-content-ltr">An array of variables that should be ignored by the extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Can be used for more fine-tuning of variables than allowed by <syntaxhighlight lang="php" inline="">$wgDebugMode</syntaxhighlight>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These vars can be any named variables known to the extension, including MediaWiki globals and PHP settings.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Default is an empty array, nothing is ignored.</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example: <syntaxhighlight lang="php" inline="">array( 'wgDebugAPI' )</syntaxhighlight> to ignore setting of <code>{{ll|Manual:$wgDebugAPI|$wgDebugAPI}}</code>.</span> == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> * The file [https://phabricator.wikimedia.org/source/mediawiki/browse/master/includes/DevelopmentSettings.php DevelopmentSettings.php]. </div> 1ju9ybrjobjx68ess84kistrwsb4fcr Extension:Echo/de 102 1427534 5386962 5370957 2022-07-28T19:48:39Z ThisCarthing 17456337 Created page with "koniguriere $1" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = notify |image = Screenshot_of_Echo_notification_extension.png |imagesize = 375 |author = <nowiki/> * [[User:Werdna|Andrew Garrett]] * [[User:Kaldari|Ryan Kaldari]] * [[User:Bsitu|Benny Situ]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides an in-wiki notification system that can be used by other extensions.</span> |version = Laufende Aktualisierungen |update = |download = {{WikimediaDownload}} |compatibility policy = rel |mediawiki = |license = |newhook1 = EchoGetEventsForRevision |newhook2 = BeforeCreateEchoEvent |newhook3 = BeforeDisplayOrangeAlert |newhook4 = EchoCanAbortNewMessagesAlert |newhook5 = EchoAbortEmailNotification |newhook6 = EchoGetBundleRules |newhook7 = EchoGetNotificationTypes |newhook8 = EchoGetDefaultNotifiedUsers |newhook9 = BeforeEchoEventInsert |newhook10 = EchoEventInsertComplete |newhook11 = EchoCreateNotificationComplete |phabricator = Notifications |table1 = echo_email_batch |table2 = echo_event |table3 = echo_notification |table4 = echo_subscription |table5 = echo_target_page |table6 = echo_push_provider |table7 = echo_push_subscription |table8 = echo_push_topic }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''Echo''' extension provides an in-wiki notification system that can be used by other extensions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:Thanks|nsp=0}} and {{ll|Extension:StructuredDiscussions|nsp=0}} are two MediaWiki extensions that make use of Echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Notifications}} for a full description of what this extension does.</span> == Herunterladen == {{WikimediaGitCheckout}} {{Note |1=<span lang="en" dir="ltr" class="mw-content-ltr">The master branch of this extension only supports the master branch of MediaWiki's core (currently {{MW stable branch number}}+).</span> <span lang="en" dir="ltr" class="mw-content-ltr">To use with 1.32–{{MW legacy branch number}}, you must switch to a matching branch (for example Echo {{MW legacy release git}} with core {{MW legacy release git}}).</span> }} == Installation == {{ExtensionInstall |repo-name=Echo |db-update=Yes |custom-steps0= * <span lang="en" dir="ltr" class="mw-content-ltr">The database user must have been granted the "REFERENCES" right for the database.</span> |custom-steps= * [[#Configuration|<span lang="en" dir="ltr" class="mw-content-ltr">If necessary configure at your convenience</span>]] |registration=required |no-registration-version=1.28 }} {{clear}} {{anchor|Configuration}} == Konfiguration == <span lang="en" dir="ltr" class="mw-content-ltr">In addition to setting default user preferences, you can also use the {{ll|Manual:Hooks/AddNewAccount|AddNewAccount}} hook to change user preferences on signup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">That allows setting different user preferences going forward without affecting existing users.</span> Siehe [[Special:DisplayNotificationsConfiguration]] für lokale Details. === Parameter === {| class="wikitable" |+ Konfigurationseinstellungen (Voreinstellungen in {{git file|project=mediawiki/extensions/Echo|file=extension.json}} festgelegt) |-- ! Parameter ! Standard ! Anmerkung |--- | <code>$wgEchoEnableEmailBatch</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to turn on email batch function</span> |--- | <code>$wgEchoUseJobQueue</code> | {{phpi|false}} | * <code>true</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defer web and email notification delivery via job queue.</span> * <code>false</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Deliver notifications immediately</span> |--- | <code>$wgEchoEmailFooterAddress</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">The organization address (or whatever text you want to appear in the footer of the email notifications).</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSender</code> | <code>$wgPasswordSender</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The email address for both "from" and "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSenderName</code> | [[MediaWiki:emailsender|<span lang="en" dir="ltr" class="mw-content-ltr">"emailsender" message</span>]] ({{int|emailsender}}) | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "from" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationReplyName</code> | No Reply | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgEchoCluster</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Use the main db if this is set to false, to use a specific external db, just use any key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |- | <code>$wgEchoSharedTrackingDB</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Shared database to use for keeping track of cross-wiki unread notifications; false to not keep track of it at all</span> |- | <code>$wgEchoSharedTrackingCluster</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Cluster the shared tracking database is located on; false if it is on the main one.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Must be a key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |--- | <code>$wgEchoMaxUpdateCount</code> | 2000 | <span lang="en" dir="ltr" class="mw-content-ltr">The max number of notifications allowed for a user to do a live update, this is also the number of max notifications allowed for a user to have.</span> |- | <code>$wgEchoMaxMentionsCount</code> | 50 |<span lang="en" dir="ltr" class="mw-content-ltr">The max number of mention notifications allowed for a user to send at once</span> |- | <code>$wgEchoMentionStatusNotifications</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Enable mention success/failure notifications</span> |- | <code>$wgEchoMentionsOnMultipleSectionEdits</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for multiple-section edits</span> |- | <code>$wgEchoMentionOnChanges</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for edits to existing comments, as long as a signature is added in the same section</span> |--- | <code>$wgEchoMaxMentionsInEditSummary</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Maximum number of users that will be notified that they were linked from an edit summary or 0 for no notifications</span> |--- | <code>$wgEchoBundleEmailInterval</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">The time interval between each bundle email in seconds; set a small number for test wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This should be set to 0 to disable email bundling if there is no delay queue support</span> |--- | <code>$wgEchoNewMsgAlert</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to enable a new talk page message alert for logged in users.</span> |- | <code>$wgEchoShowFooterNotice</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to show the footer feedback notice in the notifications popup</span> |- | <code>$wgEchoFooterNoticeURL</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">A URL for the survey that appears in the footer feedback notice in the notification popup</span> |- | <code>$wgNotifyTypeAvailabilityByCategory</code> | <syntaxhighlight lang=php>[ // Otherwise, a user->user email could trigger an additional redundant notification email. 'emailuser' => [ 'web' => true, 'email' => false, ], 'mention-failure' => [ 'web' => true, 'email' => false, ], 'mention-success' => [ 'web' => true, 'email' => false, ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Define which notify types are available for each notification category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If any notify types are omitted, it defaults to $wgDefaultNotifyTypeAvailability.</span> |--- | <code>$wgEchoNotifiers</code> | <syntaxhighlight lang=php>[ 'web' => [ 'EchoNotifier', 'notifyWithNotification' ], 'email' => [ 'EchoNotifier', 'notifyWithEmail' ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Definitions of the different types of notification delivery that are possible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each definition consists of a class name and a function name.</span> Siehe auch die Klasse EchoNotificationController. |--- | <code>$wgEchoAgentBlacklist</code> | [] | <span lang="en" dir="ltr" class="mw-content-ltr">List of usernames which will not trigger notifications</span> |--- | <code>$wgEchoOnWikiBlacklist</code> | Echo-blacklist | <span lang="en" dir="ltr" class="mw-content-ltr">Page location of community maintained blacklist within NS_MEDIAWIKI containing one username per line which will not trigger notifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set to null to disable.</span> |--- | <code>$wgEchoPerUserWhitelistFormat</code> | %s/Echo-whitelist | <span lang="en" dir="ltr" class="mw-content-ltr">An sprintf format of the location of the per-user notification agent whitelist within the NS_USER namespace.</span> <span lang="en" dir="ltr" class="mw-content-ltr">%s will be replaced with the users name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelists must contain one username per line which will always trigger notifications regardless of their existence in the blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set to {{phpi|null}} to disable.</span> |- | <code>$wgEchoCrossWikiNotifications</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to enable the cross-wiki notifications feature.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable this feature you need to:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have a global user system (e.g. CentralAuth or a shared user table)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have $wgMainStash and $wgMainWANCache shared between wikis</span> * koniguriere $wgEchoSharedTrackingDB |- | <code>$wgEchoUseCrossWikiBetaFeature</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Feature flag for the cross-wiki notifications beta feature</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|true}}, the cross-wiki notifications preference will appear in the BetaFeatures section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|false}}, it'll appear in the Notifications section instead.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This does not control whether cross-wiki notifications are enabled by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For that, use {{phpi|$wgDefaultUserOptions['echo-cross-wiki-notifications'] {{=}} true;}}</span> |--- | <code>$wgEchoNotificationCategories</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Define the categories that notifications can belong to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Categories can be assigned the following parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All parameters are optional:</span> * <code>priority</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Controls the order in which notifications are displayed in preferences and batch emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Priority ranges from 1 to 10.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the priority is not specified, it defaults to 10, which is the lowest.</span> * <code>no-dismiss</code> - <span lang="en" dir="ltr" class="mw-content-ltr">disables the dismissability of notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It can either be set to an array of output formats (see <code>$wgEchoNotifiers</code>) or an array containing 'all'.</span> * <code>usergroups</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Specifies an array of usergroups eligible to receive the notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If no usergroups parameter is specified, all groups are eligible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If a notifications type doesn't have a category parameter, it is automatically assigned to the <code>other</code> category which is lowest priority and has no preferences or dismissibility.</span> |--- | <code>$wgEchoNotificationIcons</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Defines icons, which are 30x30 images.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is passed to BeforeCreateEchoEvent so extensions can define their own icons with the same structure.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is recommended that extensions prefix their icon key.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An example is myextension-name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will help avoid namespace conflicts.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use either a path or a url, but not both.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'path' is relative to <code>$wgExtensionAssetsPath</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'url' should be a URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should customize the site icon URL, which is:</span> <code>$wgEchoNotificationIcons['site']['url']</code> |--- | <code>$wgEchoNotifications</code> | Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Define the event types for echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Event definitions are in the form of 'event-name' => [ ... ].</span> * <code>category</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defines the category the event belongs to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'other'.</span> * <code>group</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'neutral'.</span> * <code>bundle</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which output formats are available for bundling.</span> * <code>presentation-model</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which class is used to render notification messages and links for notification panels, special page and emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It must extend <code>EchoEventPresentationModel</code>.</span> |- | <code>$wgEchoConfig</code> |Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Configuration for EventLogging.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual schemas can be disabled.</span> |- | <code>$wgEchoPerUserBlacklist</code> | {{phpi|null}} | <span lang="en" dir="ltr" class="mw-content-ltr">Boolean that enabled Per User Blacklist.</span> |} === Benutzereinstellungen ==== {| class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Preference settings (defaults defined in {{git file|project=mediawiki/extensions/Echo|file=extension.json}})</span> |-- ! Einstellungen ! Standard ! Anmerkung |--- |- | <code>$wgDefaultUserOptions['echo-show-alert']</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for showing the special talk page alert bar</span> |- | <code>$wgDefaultUserOptions['echo-email-frequency']</code> | 0 | Wie oft E-Mails standardmäßig gesendet werden sollen: * 0 - <span lang="en" dir="ltr" class="mw-content-ltr">send emails for each notification as they come in (default)</span> * -1 - Sende keine E-Mails * 1 - Jeden Tag * 7 - Alle 7 Tage * ... |- | <code>$wgDefaultUserOptions['echo-dismiss-feedback-alert']</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Ensures the feedback alert is visible by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do not change; to disable, use <code>$wgEchoShowFooterNotice</code>.</span> |- | <code>$wgDefaultUserOptions['echo-email-format']</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Depends on <code>$wgAllowHTMLEmail</code></span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to use HTML or text email</span>. Either <code>html</code> or <code>plain-text</code>. |- | <code>$wgDefaultUserOptions["echo-subscriptions-email-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>false</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via email for a particular category</span> |- | <code>$wgDefaultUserOptions["echo-subscriptions-web-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>true</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via web for a particular category</span> |} == Architektur == <div lang="en" dir="ltr" class="mw-content-ltr"> See {{ll|Echo (Notifications)/Technical Architecture|the architecture section of the feature page}}. </div> == Verwendung == ; <span lang="en" dir="ltr" class="mw-content-ltr">Notification negative list / positive list</span> <span lang="en" dir="ltr" class="mw-content-ltr">There are occasionally specific users, typically bots, which perform maintenance tasks that should not generate notifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To handle these cases, users can be globally blacklisted from the LocalSettings.php file (or InitialiseSettings.php in the case of WMF wikis):</span> <syntaxhighlight lang="php"> $wgEchoAgentBlacklist = [ 'SampleBot', 'SampleUser' ]; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">There is also an on-wiki blacklist that can be maintained by the wiki's community.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The location of the global on-wiki blacklist defaults to [[MediaWiki:Echo-blacklist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual users can override the blacklist by creating a whitelist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelist location defaults to [[Special:MyPage/Echo-whitelist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All on-wiki lists expect to receive one case-specific username per line with no special markup or prefixes.</span> Zum Beispiel: SampleBot SampleUser ; <span lang="en" dir="ltr" class="mw-content-ltr">"Mention" option</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the notification types that this extension allows is: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">It might not be obvious to some users, but this particular notification only works when the person linking to another user's page also signs (<nowiki>~~~~</nowiki>) the post.</span><br /> <span lang="en" dir="ltr" class="mw-content-ltr">After installation of the extension, a new tab "Notifications" is created in a user's [[Special:Preferences]] page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Under the section "Notify me about these events", in front of the "Mention" option, the hoverbox states: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">If an administrator feels, that the requirement for signing the post isn't obvious in this help text, it can be modified by changing the text in the Wiki's [[MediaWiki:Echo-pref-tooltip-mention]] page.</span> == Begriffe == <div lang="en" dir="ltr" class="mw-content-ltr"> * notification - Any individual notice that is delivered by Echo </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * message - A notification about activity in a Flow discussion </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * alert - Any notification other than a message </div> == Siehe auch == * {{ll|Notifications/API}} * {{ll|Manual:Echo}} - Für Details über die Mention-Anforderungen * {{ll|Extension:Echo/Creating a new notification type}} (aktuell) * {{ll|Notifications/Developer_guide}} (veraltet) {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|miraheze=1|mywikis=1|prowiki=1|semantic core=1}} [[Category:Echo{{#translation:}}]] itc9lqf30s5o17s1i350kxo4zw844o8 5386964 5386962 2022-07-28T19:48:59Z ThisCarthing 17456337 Created page with "Setze auf $1, um zu deaktivieren." wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = notify |image = Screenshot_of_Echo_notification_extension.png |imagesize = 375 |author = <nowiki/> * [[User:Werdna|Andrew Garrett]] * [[User:Kaldari|Ryan Kaldari]] * [[User:Bsitu|Benny Situ]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides an in-wiki notification system that can be used by other extensions.</span> |version = Laufende Aktualisierungen |update = |download = {{WikimediaDownload}} |compatibility policy = rel |mediawiki = |license = |newhook1 = EchoGetEventsForRevision |newhook2 = BeforeCreateEchoEvent |newhook3 = BeforeDisplayOrangeAlert |newhook4 = EchoCanAbortNewMessagesAlert |newhook5 = EchoAbortEmailNotification |newhook6 = EchoGetBundleRules |newhook7 = EchoGetNotificationTypes |newhook8 = EchoGetDefaultNotifiedUsers |newhook9 = BeforeEchoEventInsert |newhook10 = EchoEventInsertComplete |newhook11 = EchoCreateNotificationComplete |phabricator = Notifications |table1 = echo_email_batch |table2 = echo_event |table3 = echo_notification |table4 = echo_subscription |table5 = echo_target_page |table6 = echo_push_provider |table7 = echo_push_subscription |table8 = echo_push_topic }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''Echo''' extension provides an in-wiki notification system that can be used by other extensions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:Thanks|nsp=0}} and {{ll|Extension:StructuredDiscussions|nsp=0}} are two MediaWiki extensions that make use of Echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Notifications}} for a full description of what this extension does.</span> == Herunterladen == {{WikimediaGitCheckout}} {{Note |1=<span lang="en" dir="ltr" class="mw-content-ltr">The master branch of this extension only supports the master branch of MediaWiki's core (currently {{MW stable branch number}}+).</span> <span lang="en" dir="ltr" class="mw-content-ltr">To use with 1.32–{{MW legacy branch number}}, you must switch to a matching branch (for example Echo {{MW legacy release git}} with core {{MW legacy release git}}).</span> }} == Installation == {{ExtensionInstall |repo-name=Echo |db-update=Yes |custom-steps0= * <span lang="en" dir="ltr" class="mw-content-ltr">The database user must have been granted the "REFERENCES" right for the database.</span> |custom-steps= * [[#Configuration|<span lang="en" dir="ltr" class="mw-content-ltr">If necessary configure at your convenience</span>]] |registration=required |no-registration-version=1.28 }} {{clear}} {{anchor|Configuration}} == Konfiguration == <span lang="en" dir="ltr" class="mw-content-ltr">In addition to setting default user preferences, you can also use the {{ll|Manual:Hooks/AddNewAccount|AddNewAccount}} hook to change user preferences on signup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">That allows setting different user preferences going forward without affecting existing users.</span> Siehe [[Special:DisplayNotificationsConfiguration]] für lokale Details. === Parameter === {| class="wikitable" |+ Konfigurationseinstellungen (Voreinstellungen in {{git file|project=mediawiki/extensions/Echo|file=extension.json}} festgelegt) |-- ! Parameter ! Standard ! Anmerkung |--- | <code>$wgEchoEnableEmailBatch</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to turn on email batch function</span> |--- | <code>$wgEchoUseJobQueue</code> | {{phpi|false}} | * <code>true</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defer web and email notification delivery via job queue.</span> * <code>false</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Deliver notifications immediately</span> |--- | <code>$wgEchoEmailFooterAddress</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">The organization address (or whatever text you want to appear in the footer of the email notifications).</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSender</code> | <code>$wgPasswordSender</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The email address for both "from" and "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSenderName</code> | [[MediaWiki:emailsender|<span lang="en" dir="ltr" class="mw-content-ltr">"emailsender" message</span>]] ({{int|emailsender}}) | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "from" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationReplyName</code> | No Reply | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgEchoCluster</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Use the main db if this is set to false, to use a specific external db, just use any key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |- | <code>$wgEchoSharedTrackingDB</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Shared database to use for keeping track of cross-wiki unread notifications; false to not keep track of it at all</span> |- | <code>$wgEchoSharedTrackingCluster</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Cluster the shared tracking database is located on; false if it is on the main one.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Must be a key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |--- | <code>$wgEchoMaxUpdateCount</code> | 2000 | <span lang="en" dir="ltr" class="mw-content-ltr">The max number of notifications allowed for a user to do a live update, this is also the number of max notifications allowed for a user to have.</span> |- | <code>$wgEchoMaxMentionsCount</code> | 50 |<span lang="en" dir="ltr" class="mw-content-ltr">The max number of mention notifications allowed for a user to send at once</span> |- | <code>$wgEchoMentionStatusNotifications</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Enable mention success/failure notifications</span> |- | <code>$wgEchoMentionsOnMultipleSectionEdits</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for multiple-section edits</span> |- | <code>$wgEchoMentionOnChanges</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for edits to existing comments, as long as a signature is added in the same section</span> |--- | <code>$wgEchoMaxMentionsInEditSummary</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Maximum number of users that will be notified that they were linked from an edit summary or 0 for no notifications</span> |--- | <code>$wgEchoBundleEmailInterval</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">The time interval between each bundle email in seconds; set a small number for test wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This should be set to 0 to disable email bundling if there is no delay queue support</span> |--- | <code>$wgEchoNewMsgAlert</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to enable a new talk page message alert for logged in users.</span> |- | <code>$wgEchoShowFooterNotice</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to show the footer feedback notice in the notifications popup</span> |- | <code>$wgEchoFooterNoticeURL</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">A URL for the survey that appears in the footer feedback notice in the notification popup</span> |- | <code>$wgNotifyTypeAvailabilityByCategory</code> | <syntaxhighlight lang=php>[ // Otherwise, a user->user email could trigger an additional redundant notification email. 'emailuser' => [ 'web' => true, 'email' => false, ], 'mention-failure' => [ 'web' => true, 'email' => false, ], 'mention-success' => [ 'web' => true, 'email' => false, ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Define which notify types are available for each notification category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If any notify types are omitted, it defaults to $wgDefaultNotifyTypeAvailability.</span> |--- | <code>$wgEchoNotifiers</code> | <syntaxhighlight lang=php>[ 'web' => [ 'EchoNotifier', 'notifyWithNotification' ], 'email' => [ 'EchoNotifier', 'notifyWithEmail' ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Definitions of the different types of notification delivery that are possible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each definition consists of a class name and a function name.</span> Siehe auch die Klasse EchoNotificationController. |--- | <code>$wgEchoAgentBlacklist</code> | [] | <span lang="en" dir="ltr" class="mw-content-ltr">List of usernames which will not trigger notifications</span> |--- | <code>$wgEchoOnWikiBlacklist</code> | Echo-blacklist | <span lang="en" dir="ltr" class="mw-content-ltr">Page location of community maintained blacklist within NS_MEDIAWIKI containing one username per line which will not trigger notifications.</span> Setze auf null, um zu deaktivieren. |--- | <code>$wgEchoPerUserWhitelistFormat</code> | %s/Echo-whitelist | <span lang="en" dir="ltr" class="mw-content-ltr">An sprintf format of the location of the per-user notification agent whitelist within the NS_USER namespace.</span> <span lang="en" dir="ltr" class="mw-content-ltr">%s will be replaced with the users name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelists must contain one username per line which will always trigger notifications regardless of their existence in the blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set to {{phpi|null}} to disable.</span> |- | <code>$wgEchoCrossWikiNotifications</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to enable the cross-wiki notifications feature.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable this feature you need to:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have a global user system (e.g. CentralAuth or a shared user table)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have $wgMainStash and $wgMainWANCache shared between wikis</span> * koniguriere $wgEchoSharedTrackingDB |- | <code>$wgEchoUseCrossWikiBetaFeature</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Feature flag for the cross-wiki notifications beta feature</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|true}}, the cross-wiki notifications preference will appear in the BetaFeatures section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|false}}, it'll appear in the Notifications section instead.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This does not control whether cross-wiki notifications are enabled by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For that, use {{phpi|$wgDefaultUserOptions['echo-cross-wiki-notifications'] {{=}} true;}}</span> |--- | <code>$wgEchoNotificationCategories</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Define the categories that notifications can belong to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Categories can be assigned the following parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All parameters are optional:</span> * <code>priority</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Controls the order in which notifications are displayed in preferences and batch emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Priority ranges from 1 to 10.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the priority is not specified, it defaults to 10, which is the lowest.</span> * <code>no-dismiss</code> - <span lang="en" dir="ltr" class="mw-content-ltr">disables the dismissability of notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It can either be set to an array of output formats (see <code>$wgEchoNotifiers</code>) or an array containing 'all'.</span> * <code>usergroups</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Specifies an array of usergroups eligible to receive the notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If no usergroups parameter is specified, all groups are eligible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If a notifications type doesn't have a category parameter, it is automatically assigned to the <code>other</code> category which is lowest priority and has no preferences or dismissibility.</span> |--- | <code>$wgEchoNotificationIcons</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Defines icons, which are 30x30 images.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is passed to BeforeCreateEchoEvent so extensions can define their own icons with the same structure.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is recommended that extensions prefix their icon key.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An example is myextension-name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will help avoid namespace conflicts.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use either a path or a url, but not both.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'path' is relative to <code>$wgExtensionAssetsPath</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'url' should be a URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should customize the site icon URL, which is:</span> <code>$wgEchoNotificationIcons['site']['url']</code> |--- | <code>$wgEchoNotifications</code> | Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Define the event types for echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Event definitions are in the form of 'event-name' => [ ... ].</span> * <code>category</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defines the category the event belongs to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'other'.</span> * <code>group</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'neutral'.</span> * <code>bundle</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which output formats are available for bundling.</span> * <code>presentation-model</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which class is used to render notification messages and links for notification panels, special page and emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It must extend <code>EchoEventPresentationModel</code>.</span> |- | <code>$wgEchoConfig</code> |Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Configuration for EventLogging.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual schemas can be disabled.</span> |- | <code>$wgEchoPerUserBlacklist</code> | {{phpi|null}} | <span lang="en" dir="ltr" class="mw-content-ltr">Boolean that enabled Per User Blacklist.</span> |} === Benutzereinstellungen ==== {| class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Preference settings (defaults defined in {{git file|project=mediawiki/extensions/Echo|file=extension.json}})</span> |-- ! Einstellungen ! Standard ! Anmerkung |--- |- | <code>$wgDefaultUserOptions['echo-show-alert']</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for showing the special talk page alert bar</span> |- | <code>$wgDefaultUserOptions['echo-email-frequency']</code> | 0 | Wie oft E-Mails standardmäßig gesendet werden sollen: * 0 - <span lang="en" dir="ltr" class="mw-content-ltr">send emails for each notification as they come in (default)</span> * -1 - Sende keine E-Mails * 1 - Jeden Tag * 7 - Alle 7 Tage * ... |- | <code>$wgDefaultUserOptions['echo-dismiss-feedback-alert']</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Ensures the feedback alert is visible by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do not change; to disable, use <code>$wgEchoShowFooterNotice</code>.</span> |- | <code>$wgDefaultUserOptions['echo-email-format']</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Depends on <code>$wgAllowHTMLEmail</code></span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to use HTML or text email</span>. Either <code>html</code> or <code>plain-text</code>. |- | <code>$wgDefaultUserOptions["echo-subscriptions-email-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>false</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via email for a particular category</span> |- | <code>$wgDefaultUserOptions["echo-subscriptions-web-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>true</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via web for a particular category</span> |} == Architektur == <div lang="en" dir="ltr" class="mw-content-ltr"> See {{ll|Echo (Notifications)/Technical Architecture|the architecture section of the feature page}}. </div> == Verwendung == ; <span lang="en" dir="ltr" class="mw-content-ltr">Notification negative list / positive list</span> <span lang="en" dir="ltr" class="mw-content-ltr">There are occasionally specific users, typically bots, which perform maintenance tasks that should not generate notifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To handle these cases, users can be globally blacklisted from the LocalSettings.php file (or InitialiseSettings.php in the case of WMF wikis):</span> <syntaxhighlight lang="php"> $wgEchoAgentBlacklist = [ 'SampleBot', 'SampleUser' ]; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">There is also an on-wiki blacklist that can be maintained by the wiki's community.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The location of the global on-wiki blacklist defaults to [[MediaWiki:Echo-blacklist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual users can override the blacklist by creating a whitelist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelist location defaults to [[Special:MyPage/Echo-whitelist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All on-wiki lists expect to receive one case-specific username per line with no special markup or prefixes.</span> Zum Beispiel: SampleBot SampleUser ; <span lang="en" dir="ltr" class="mw-content-ltr">"Mention" option</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the notification types that this extension allows is: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">It might not be obvious to some users, but this particular notification only works when the person linking to another user's page also signs (<nowiki>~~~~</nowiki>) the post.</span><br /> <span lang="en" dir="ltr" class="mw-content-ltr">After installation of the extension, a new tab "Notifications" is created in a user's [[Special:Preferences]] page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Under the section "Notify me about these events", in front of the "Mention" option, the hoverbox states: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">If an administrator feels, that the requirement for signing the post isn't obvious in this help text, it can be modified by changing the text in the Wiki's [[MediaWiki:Echo-pref-tooltip-mention]] page.</span> == Begriffe == <div lang="en" dir="ltr" class="mw-content-ltr"> * notification - Any individual notice that is delivered by Echo </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * message - A notification about activity in a Flow discussion </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * alert - Any notification other than a message </div> == Siehe auch == * {{ll|Notifications/API}} * {{ll|Manual:Echo}} - Für Details über die Mention-Anforderungen * {{ll|Extension:Echo/Creating a new notification type}} (aktuell) * {{ll|Notifications/Developer_guide}} (veraltet) {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|miraheze=1|mywikis=1|prowiki=1|semantic core=1}} [[Category:Echo{{#translation:}}]] t1dio64mp68j6pioikvw7qpxmt2sj13 5386966 5386964 2022-07-28T19:49:04Z ThisCarthing 17456337 Created page with "Setze auf $1, um zu deaktivieren." wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = notify |image = Screenshot_of_Echo_notification_extension.png |imagesize = 375 |author = <nowiki/> * [[User:Werdna|Andrew Garrett]] * [[User:Kaldari|Ryan Kaldari]] * [[User:Bsitu|Benny Situ]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides an in-wiki notification system that can be used by other extensions.</span> |version = Laufende Aktualisierungen |update = |download = {{WikimediaDownload}} |compatibility policy = rel |mediawiki = |license = |newhook1 = EchoGetEventsForRevision |newhook2 = BeforeCreateEchoEvent |newhook3 = BeforeDisplayOrangeAlert |newhook4 = EchoCanAbortNewMessagesAlert |newhook5 = EchoAbortEmailNotification |newhook6 = EchoGetBundleRules |newhook7 = EchoGetNotificationTypes |newhook8 = EchoGetDefaultNotifiedUsers |newhook9 = BeforeEchoEventInsert |newhook10 = EchoEventInsertComplete |newhook11 = EchoCreateNotificationComplete |phabricator = Notifications |table1 = echo_email_batch |table2 = echo_event |table3 = echo_notification |table4 = echo_subscription |table5 = echo_target_page |table6 = echo_push_provider |table7 = echo_push_subscription |table8 = echo_push_topic }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''Echo''' extension provides an in-wiki notification system that can be used by other extensions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:Thanks|nsp=0}} and {{ll|Extension:StructuredDiscussions|nsp=0}} are two MediaWiki extensions that make use of Echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Notifications}} for a full description of what this extension does.</span> == Herunterladen == {{WikimediaGitCheckout}} {{Note |1=<span lang="en" dir="ltr" class="mw-content-ltr">The master branch of this extension only supports the master branch of MediaWiki's core (currently {{MW stable branch number}}+).</span> <span lang="en" dir="ltr" class="mw-content-ltr">To use with 1.32–{{MW legacy branch number}}, you must switch to a matching branch (for example Echo {{MW legacy release git}} with core {{MW legacy release git}}).</span> }} == Installation == {{ExtensionInstall |repo-name=Echo |db-update=Yes |custom-steps0= * <span lang="en" dir="ltr" class="mw-content-ltr">The database user must have been granted the "REFERENCES" right for the database.</span> |custom-steps= * [[#Configuration|<span lang="en" dir="ltr" class="mw-content-ltr">If necessary configure at your convenience</span>]] |registration=required |no-registration-version=1.28 }} {{clear}} {{anchor|Configuration}} == Konfiguration == <span lang="en" dir="ltr" class="mw-content-ltr">In addition to setting default user preferences, you can also use the {{ll|Manual:Hooks/AddNewAccount|AddNewAccount}} hook to change user preferences on signup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">That allows setting different user preferences going forward without affecting existing users.</span> Siehe [[Special:DisplayNotificationsConfiguration]] für lokale Details. === Parameter === {| class="wikitable" |+ Konfigurationseinstellungen (Voreinstellungen in {{git file|project=mediawiki/extensions/Echo|file=extension.json}} festgelegt) |-- ! Parameter ! Standard ! Anmerkung |--- | <code>$wgEchoEnableEmailBatch</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to turn on email batch function</span> |--- | <code>$wgEchoUseJobQueue</code> | {{phpi|false}} | * <code>true</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defer web and email notification delivery via job queue.</span> * <code>false</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Deliver notifications immediately</span> |--- | <code>$wgEchoEmailFooterAddress</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">The organization address (or whatever text you want to appear in the footer of the email notifications).</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSender</code> | <code>$wgPasswordSender</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The email address for both "from" and "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSenderName</code> | [[MediaWiki:emailsender|<span lang="en" dir="ltr" class="mw-content-ltr">"emailsender" message</span>]] ({{int|emailsender}}) | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "from" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationReplyName</code> | No Reply | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgEchoCluster</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Use the main db if this is set to false, to use a specific external db, just use any key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |- | <code>$wgEchoSharedTrackingDB</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Shared database to use for keeping track of cross-wiki unread notifications; false to not keep track of it at all</span> |- | <code>$wgEchoSharedTrackingCluster</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Cluster the shared tracking database is located on; false if it is on the main one.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Must be a key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |--- | <code>$wgEchoMaxUpdateCount</code> | 2000 | <span lang="en" dir="ltr" class="mw-content-ltr">The max number of notifications allowed for a user to do a live update, this is also the number of max notifications allowed for a user to have.</span> |- | <code>$wgEchoMaxMentionsCount</code> | 50 |<span lang="en" dir="ltr" class="mw-content-ltr">The max number of mention notifications allowed for a user to send at once</span> |- | <code>$wgEchoMentionStatusNotifications</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Enable mention success/failure notifications</span> |- | <code>$wgEchoMentionsOnMultipleSectionEdits</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for multiple-section edits</span> |- | <code>$wgEchoMentionOnChanges</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for edits to existing comments, as long as a signature is added in the same section</span> |--- | <code>$wgEchoMaxMentionsInEditSummary</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Maximum number of users that will be notified that they were linked from an edit summary or 0 for no notifications</span> |--- | <code>$wgEchoBundleEmailInterval</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">The time interval between each bundle email in seconds; set a small number for test wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This should be set to 0 to disable email bundling if there is no delay queue support</span> |--- | <code>$wgEchoNewMsgAlert</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to enable a new talk page message alert for logged in users.</span> |- | <code>$wgEchoShowFooterNotice</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to show the footer feedback notice in the notifications popup</span> |- | <code>$wgEchoFooterNoticeURL</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">A URL for the survey that appears in the footer feedback notice in the notification popup</span> |- | <code>$wgNotifyTypeAvailabilityByCategory</code> | <syntaxhighlight lang=php>[ // Otherwise, a user->user email could trigger an additional redundant notification email. 'emailuser' => [ 'web' => true, 'email' => false, ], 'mention-failure' => [ 'web' => true, 'email' => false, ], 'mention-success' => [ 'web' => true, 'email' => false, ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Define which notify types are available for each notification category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If any notify types are omitted, it defaults to $wgDefaultNotifyTypeAvailability.</span> |--- | <code>$wgEchoNotifiers</code> | <syntaxhighlight lang=php>[ 'web' => [ 'EchoNotifier', 'notifyWithNotification' ], 'email' => [ 'EchoNotifier', 'notifyWithEmail' ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Definitions of the different types of notification delivery that are possible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each definition consists of a class name and a function name.</span> Siehe auch die Klasse EchoNotificationController. |--- | <code>$wgEchoAgentBlacklist</code> | [] | <span lang="en" dir="ltr" class="mw-content-ltr">List of usernames which will not trigger notifications</span> |--- | <code>$wgEchoOnWikiBlacklist</code> | Echo-blacklist | <span lang="en" dir="ltr" class="mw-content-ltr">Page location of community maintained blacklist within NS_MEDIAWIKI containing one username per line which will not trigger notifications.</span> Setze auf null, um zu deaktivieren. |--- | <code>$wgEchoPerUserWhitelistFormat</code> | %s/Echo-whitelist | <span lang="en" dir="ltr" class="mw-content-ltr">An sprintf format of the location of the per-user notification agent whitelist within the NS_USER namespace.</span> <span lang="en" dir="ltr" class="mw-content-ltr">%s will be replaced with the users name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelists must contain one username per line which will always trigger notifications regardless of their existence in the blacklists.</span> Setze auf {{phpi|null}}, um zu deaktivieren. |- | <code>$wgEchoCrossWikiNotifications</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to enable the cross-wiki notifications feature.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable this feature you need to:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have a global user system (e.g. CentralAuth or a shared user table)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have $wgMainStash and $wgMainWANCache shared between wikis</span> * koniguriere $wgEchoSharedTrackingDB |- | <code>$wgEchoUseCrossWikiBetaFeature</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Feature flag for the cross-wiki notifications beta feature</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|true}}, the cross-wiki notifications preference will appear in the BetaFeatures section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|false}}, it'll appear in the Notifications section instead.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This does not control whether cross-wiki notifications are enabled by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For that, use {{phpi|$wgDefaultUserOptions['echo-cross-wiki-notifications'] {{=}} true;}}</span> |--- | <code>$wgEchoNotificationCategories</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Define the categories that notifications can belong to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Categories can be assigned the following parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All parameters are optional:</span> * <code>priority</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Controls the order in which notifications are displayed in preferences and batch emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Priority ranges from 1 to 10.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the priority is not specified, it defaults to 10, which is the lowest.</span> * <code>no-dismiss</code> - <span lang="en" dir="ltr" class="mw-content-ltr">disables the dismissability of notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It can either be set to an array of output formats (see <code>$wgEchoNotifiers</code>) or an array containing 'all'.</span> * <code>usergroups</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Specifies an array of usergroups eligible to receive the notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If no usergroups parameter is specified, all groups are eligible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If a notifications type doesn't have a category parameter, it is automatically assigned to the <code>other</code> category which is lowest priority and has no preferences or dismissibility.</span> |--- | <code>$wgEchoNotificationIcons</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Defines icons, which are 30x30 images.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is passed to BeforeCreateEchoEvent so extensions can define their own icons with the same structure.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is recommended that extensions prefix their icon key.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An example is myextension-name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will help avoid namespace conflicts.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use either a path or a url, but not both.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'path' is relative to <code>$wgExtensionAssetsPath</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'url' should be a URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should customize the site icon URL, which is:</span> <code>$wgEchoNotificationIcons['site']['url']</code> |--- | <code>$wgEchoNotifications</code> | Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Define the event types for echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Event definitions are in the form of 'event-name' => [ ... ].</span> * <code>category</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defines the category the event belongs to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'other'.</span> * <code>group</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'neutral'.</span> * <code>bundle</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which output formats are available for bundling.</span> * <code>presentation-model</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which class is used to render notification messages and links for notification panels, special page and emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It must extend <code>EchoEventPresentationModel</code>.</span> |- | <code>$wgEchoConfig</code> |Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Configuration for EventLogging.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual schemas can be disabled.</span> |- | <code>$wgEchoPerUserBlacklist</code> | {{phpi|null}} | <span lang="en" dir="ltr" class="mw-content-ltr">Boolean that enabled Per User Blacklist.</span> |} === Benutzereinstellungen ==== {| class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Preference settings (defaults defined in {{git file|project=mediawiki/extensions/Echo|file=extension.json}})</span> |-- ! Einstellungen ! Standard ! Anmerkung |--- |- | <code>$wgDefaultUserOptions['echo-show-alert']</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for showing the special talk page alert bar</span> |- | <code>$wgDefaultUserOptions['echo-email-frequency']</code> | 0 | Wie oft E-Mails standardmäßig gesendet werden sollen: * 0 - <span lang="en" dir="ltr" class="mw-content-ltr">send emails for each notification as they come in (default)</span> * -1 - Sende keine E-Mails * 1 - Jeden Tag * 7 - Alle 7 Tage * ... |- | <code>$wgDefaultUserOptions['echo-dismiss-feedback-alert']</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Ensures the feedback alert is visible by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do not change; to disable, use <code>$wgEchoShowFooterNotice</code>.</span> |- | <code>$wgDefaultUserOptions['echo-email-format']</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Depends on <code>$wgAllowHTMLEmail</code></span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to use HTML or text email</span>. Either <code>html</code> or <code>plain-text</code>. |- | <code>$wgDefaultUserOptions["echo-subscriptions-email-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>false</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via email for a particular category</span> |- | <code>$wgDefaultUserOptions["echo-subscriptions-web-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>true</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via web for a particular category</span> |} == Architektur == <div lang="en" dir="ltr" class="mw-content-ltr"> See {{ll|Echo (Notifications)/Technical Architecture|the architecture section of the feature page}}. </div> == Verwendung == ; <span lang="en" dir="ltr" class="mw-content-ltr">Notification negative list / positive list</span> <span lang="en" dir="ltr" class="mw-content-ltr">There are occasionally specific users, typically bots, which perform maintenance tasks that should not generate notifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To handle these cases, users can be globally blacklisted from the LocalSettings.php file (or InitialiseSettings.php in the case of WMF wikis):</span> <syntaxhighlight lang="php"> $wgEchoAgentBlacklist = [ 'SampleBot', 'SampleUser' ]; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">There is also an on-wiki blacklist that can be maintained by the wiki's community.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The location of the global on-wiki blacklist defaults to [[MediaWiki:Echo-blacklist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual users can override the blacklist by creating a whitelist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelist location defaults to [[Special:MyPage/Echo-whitelist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All on-wiki lists expect to receive one case-specific username per line with no special markup or prefixes.</span> Zum Beispiel: SampleBot SampleUser ; <span lang="en" dir="ltr" class="mw-content-ltr">"Mention" option</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the notification types that this extension allows is: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">It might not be obvious to some users, but this particular notification only works when the person linking to another user's page also signs (<nowiki>~~~~</nowiki>) the post.</span><br /> <span lang="en" dir="ltr" class="mw-content-ltr">After installation of the extension, a new tab "Notifications" is created in a user's [[Special:Preferences]] page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Under the section "Notify me about these events", in front of the "Mention" option, the hoverbox states: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">If an administrator feels, that the requirement for signing the post isn't obvious in this help text, it can be modified by changing the text in the Wiki's [[MediaWiki:Echo-pref-tooltip-mention]] page.</span> == Begriffe == <div lang="en" dir="ltr" class="mw-content-ltr"> * notification - Any individual notice that is delivered by Echo </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * message - A notification about activity in a Flow discussion </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * alert - Any notification other than a message </div> == Siehe auch == * {{ll|Notifications/API}} * {{ll|Manual:Echo}} - Für Details über die Mention-Anforderungen * {{ll|Extension:Echo/Creating a new notification type}} (aktuell) * {{ll|Notifications/Developer_guide}} (veraltet) {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|miraheze=1|mywikis=1|prowiki=1|semantic core=1}} [[Category:Echo{{#translation:}}]] 04i7o0y46vfc91j9fuech9j3q4vauiz 5386968 5386966 2022-07-28T19:49:16Z ThisCarthing 17456337 Created page with "Für dies, verwende $1" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = notify |image = Screenshot_of_Echo_notification_extension.png |imagesize = 375 |author = <nowiki/> * [[User:Werdna|Andrew Garrett]] * [[User:Kaldari|Ryan Kaldari]] * [[User:Bsitu|Benny Situ]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides an in-wiki notification system that can be used by other extensions.</span> |version = Laufende Aktualisierungen |update = |download = {{WikimediaDownload}} |compatibility policy = rel |mediawiki = |license = |newhook1 = EchoGetEventsForRevision |newhook2 = BeforeCreateEchoEvent |newhook3 = BeforeDisplayOrangeAlert |newhook4 = EchoCanAbortNewMessagesAlert |newhook5 = EchoAbortEmailNotification |newhook6 = EchoGetBundleRules |newhook7 = EchoGetNotificationTypes |newhook8 = EchoGetDefaultNotifiedUsers |newhook9 = BeforeEchoEventInsert |newhook10 = EchoEventInsertComplete |newhook11 = EchoCreateNotificationComplete |phabricator = Notifications |table1 = echo_email_batch |table2 = echo_event |table3 = echo_notification |table4 = echo_subscription |table5 = echo_target_page |table6 = echo_push_provider |table7 = echo_push_subscription |table8 = echo_push_topic }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''Echo''' extension provides an in-wiki notification system that can be used by other extensions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:Thanks|nsp=0}} and {{ll|Extension:StructuredDiscussions|nsp=0}} are two MediaWiki extensions that make use of Echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Notifications}} for a full description of what this extension does.</span> == Herunterladen == {{WikimediaGitCheckout}} {{Note |1=<span lang="en" dir="ltr" class="mw-content-ltr">The master branch of this extension only supports the master branch of MediaWiki's core (currently {{MW stable branch number}}+).</span> <span lang="en" dir="ltr" class="mw-content-ltr">To use with 1.32–{{MW legacy branch number}}, you must switch to a matching branch (for example Echo {{MW legacy release git}} with core {{MW legacy release git}}).</span> }} == Installation == {{ExtensionInstall |repo-name=Echo |db-update=Yes |custom-steps0= * <span lang="en" dir="ltr" class="mw-content-ltr">The database user must have been granted the "REFERENCES" right for the database.</span> |custom-steps= * [[#Configuration|<span lang="en" dir="ltr" class="mw-content-ltr">If necessary configure at your convenience</span>]] |registration=required |no-registration-version=1.28 }} {{clear}} {{anchor|Configuration}} == Konfiguration == <span lang="en" dir="ltr" class="mw-content-ltr">In addition to setting default user preferences, you can also use the {{ll|Manual:Hooks/AddNewAccount|AddNewAccount}} hook to change user preferences on signup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">That allows setting different user preferences going forward without affecting existing users.</span> Siehe [[Special:DisplayNotificationsConfiguration]] für lokale Details. === Parameter === {| class="wikitable" |+ Konfigurationseinstellungen (Voreinstellungen in {{git file|project=mediawiki/extensions/Echo|file=extension.json}} festgelegt) |-- ! Parameter ! Standard ! Anmerkung |--- | <code>$wgEchoEnableEmailBatch</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to turn on email batch function</span> |--- | <code>$wgEchoUseJobQueue</code> | {{phpi|false}} | * <code>true</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defer web and email notification delivery via job queue.</span> * <code>false</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Deliver notifications immediately</span> |--- | <code>$wgEchoEmailFooterAddress</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">The organization address (or whatever text you want to appear in the footer of the email notifications).</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSender</code> | <code>$wgPasswordSender</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The email address for both "from" and "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSenderName</code> | [[MediaWiki:emailsender|<span lang="en" dir="ltr" class="mw-content-ltr">"emailsender" message</span>]] ({{int|emailsender}}) | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "from" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationReplyName</code> | No Reply | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgEchoCluster</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Use the main db if this is set to false, to use a specific external db, just use any key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |- | <code>$wgEchoSharedTrackingDB</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Shared database to use for keeping track of cross-wiki unread notifications; false to not keep track of it at all</span> |- | <code>$wgEchoSharedTrackingCluster</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Cluster the shared tracking database is located on; false if it is on the main one.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Must be a key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |--- | <code>$wgEchoMaxUpdateCount</code> | 2000 | <span lang="en" dir="ltr" class="mw-content-ltr">The max number of notifications allowed for a user to do a live update, this is also the number of max notifications allowed for a user to have.</span> |- | <code>$wgEchoMaxMentionsCount</code> | 50 |<span lang="en" dir="ltr" class="mw-content-ltr">The max number of mention notifications allowed for a user to send at once</span> |- | <code>$wgEchoMentionStatusNotifications</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Enable mention success/failure notifications</span> |- | <code>$wgEchoMentionsOnMultipleSectionEdits</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for multiple-section edits</span> |- | <code>$wgEchoMentionOnChanges</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for edits to existing comments, as long as a signature is added in the same section</span> |--- | <code>$wgEchoMaxMentionsInEditSummary</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Maximum number of users that will be notified that they were linked from an edit summary or 0 for no notifications</span> |--- | <code>$wgEchoBundleEmailInterval</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">The time interval between each bundle email in seconds; set a small number for test wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This should be set to 0 to disable email bundling if there is no delay queue support</span> |--- | <code>$wgEchoNewMsgAlert</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to enable a new talk page message alert for logged in users.</span> |- | <code>$wgEchoShowFooterNotice</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to show the footer feedback notice in the notifications popup</span> |- | <code>$wgEchoFooterNoticeURL</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">A URL for the survey that appears in the footer feedback notice in the notification popup</span> |- | <code>$wgNotifyTypeAvailabilityByCategory</code> | <syntaxhighlight lang=php>[ // Otherwise, a user->user email could trigger an additional redundant notification email. 'emailuser' => [ 'web' => true, 'email' => false, ], 'mention-failure' => [ 'web' => true, 'email' => false, ], 'mention-success' => [ 'web' => true, 'email' => false, ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Define which notify types are available for each notification category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If any notify types are omitted, it defaults to $wgDefaultNotifyTypeAvailability.</span> |--- | <code>$wgEchoNotifiers</code> | <syntaxhighlight lang=php>[ 'web' => [ 'EchoNotifier', 'notifyWithNotification' ], 'email' => [ 'EchoNotifier', 'notifyWithEmail' ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Definitions of the different types of notification delivery that are possible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each definition consists of a class name and a function name.</span> Siehe auch die Klasse EchoNotificationController. |--- | <code>$wgEchoAgentBlacklist</code> | [] | <span lang="en" dir="ltr" class="mw-content-ltr">List of usernames which will not trigger notifications</span> |--- | <code>$wgEchoOnWikiBlacklist</code> | Echo-blacklist | <span lang="en" dir="ltr" class="mw-content-ltr">Page location of community maintained blacklist within NS_MEDIAWIKI containing one username per line which will not trigger notifications.</span> Setze auf null, um zu deaktivieren. |--- | <code>$wgEchoPerUserWhitelistFormat</code> | %s/Echo-whitelist | <span lang="en" dir="ltr" class="mw-content-ltr">An sprintf format of the location of the per-user notification agent whitelist within the NS_USER namespace.</span> <span lang="en" dir="ltr" class="mw-content-ltr">%s will be replaced with the users name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelists must contain one username per line which will always trigger notifications regardless of their existence in the blacklists.</span> Setze auf {{phpi|null}}, um zu deaktivieren. |- | <code>$wgEchoCrossWikiNotifications</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to enable the cross-wiki notifications feature.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable this feature you need to:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have a global user system (e.g. CentralAuth or a shared user table)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have $wgMainStash and $wgMainWANCache shared between wikis</span> * koniguriere $wgEchoSharedTrackingDB |- | <code>$wgEchoUseCrossWikiBetaFeature</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Feature flag for the cross-wiki notifications beta feature</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|true}}, the cross-wiki notifications preference will appear in the BetaFeatures section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|false}}, it'll appear in the Notifications section instead.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This does not control whether cross-wiki notifications are enabled by default.</span> Für dies, verwende {{phpi|$wgDefaultUserOptions['echo-cross-wiki-notifications'] {{=}} true;}} |--- | <code>$wgEchoNotificationCategories</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Define the categories that notifications can belong to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Categories can be assigned the following parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">All parameters are optional:</span> * <code>priority</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Controls the order in which notifications are displayed in preferences and batch emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Priority ranges from 1 to 10.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the priority is not specified, it defaults to 10, which is the lowest.</span> * <code>no-dismiss</code> - <span lang="en" dir="ltr" class="mw-content-ltr">disables the dismissability of notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It can either be set to an array of output formats (see <code>$wgEchoNotifiers</code>) or an array containing 'all'.</span> * <code>usergroups</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Specifies an array of usergroups eligible to receive the notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If no usergroups parameter is specified, all groups are eligible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If a notifications type doesn't have a category parameter, it is automatically assigned to the <code>other</code> category which is lowest priority and has no preferences or dismissibility.</span> |--- | <code>$wgEchoNotificationIcons</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Defines icons, which are 30x30 images.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is passed to BeforeCreateEchoEvent so extensions can define their own icons with the same structure.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is recommended that extensions prefix their icon key.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An example is myextension-name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will help avoid namespace conflicts.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use either a path or a url, but not both.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'path' is relative to <code>$wgExtensionAssetsPath</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'url' should be a URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should customize the site icon URL, which is:</span> <code>$wgEchoNotificationIcons['site']['url']</code> |--- | <code>$wgEchoNotifications</code> | Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Define the event types for echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Event definitions are in the form of 'event-name' => [ ... ].</span> * <code>category</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defines the category the event belongs to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'other'.</span> * <code>group</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'neutral'.</span> * <code>bundle</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which output formats are available for bundling.</span> * <code>presentation-model</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which class is used to render notification messages and links for notification panels, special page and emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It must extend <code>EchoEventPresentationModel</code>.</span> |- | <code>$wgEchoConfig</code> |Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Configuration for EventLogging.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual schemas can be disabled.</span> |- | <code>$wgEchoPerUserBlacklist</code> | {{phpi|null}} | <span lang="en" dir="ltr" class="mw-content-ltr">Boolean that enabled Per User Blacklist.</span> |} === Benutzereinstellungen ==== {| class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Preference settings (defaults defined in {{git file|project=mediawiki/extensions/Echo|file=extension.json}})</span> |-- ! Einstellungen ! Standard ! Anmerkung |--- |- | <code>$wgDefaultUserOptions['echo-show-alert']</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for showing the special talk page alert bar</span> |- | <code>$wgDefaultUserOptions['echo-email-frequency']</code> | 0 | Wie oft E-Mails standardmäßig gesendet werden sollen: * 0 - <span lang="en" dir="ltr" class="mw-content-ltr">send emails for each notification as they come in (default)</span> * -1 - Sende keine E-Mails * 1 - Jeden Tag * 7 - Alle 7 Tage * ... |- | <code>$wgDefaultUserOptions['echo-dismiss-feedback-alert']</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Ensures the feedback alert is visible by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do not change; to disable, use <code>$wgEchoShowFooterNotice</code>.</span> |- | <code>$wgDefaultUserOptions['echo-email-format']</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Depends on <code>$wgAllowHTMLEmail</code></span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to use HTML or text email</span>. Either <code>html</code> or <code>plain-text</code>. |- | <code>$wgDefaultUserOptions["echo-subscriptions-email-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>false</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via email for a particular category</span> |- | <code>$wgDefaultUserOptions["echo-subscriptions-web-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>true</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via web for a particular category</span> |} == Architektur == <div lang="en" dir="ltr" class="mw-content-ltr"> See {{ll|Echo (Notifications)/Technical Architecture|the architecture section of the feature page}}. </div> == Verwendung == ; <span lang="en" dir="ltr" class="mw-content-ltr">Notification negative list / positive list</span> <span lang="en" dir="ltr" class="mw-content-ltr">There are occasionally specific users, typically bots, which perform maintenance tasks that should not generate notifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To handle these cases, users can be globally blacklisted from the LocalSettings.php file (or InitialiseSettings.php in the case of WMF wikis):</span> <syntaxhighlight lang="php"> $wgEchoAgentBlacklist = [ 'SampleBot', 'SampleUser' ]; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">There is also an on-wiki blacklist that can be maintained by the wiki's community.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The location of the global on-wiki blacklist defaults to [[MediaWiki:Echo-blacklist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual users can override the blacklist by creating a whitelist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelist location defaults to [[Special:MyPage/Echo-whitelist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All on-wiki lists expect to receive one case-specific username per line with no special markup or prefixes.</span> Zum Beispiel: SampleBot SampleUser ; <span lang="en" dir="ltr" class="mw-content-ltr">"Mention" option</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the notification types that this extension allows is: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">It might not be obvious to some users, but this particular notification only works when the person linking to another user's page also signs (<nowiki>~~~~</nowiki>) the post.</span><br /> <span lang="en" dir="ltr" class="mw-content-ltr">After installation of the extension, a new tab "Notifications" is created in a user's [[Special:Preferences]] page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Under the section "Notify me about these events", in front of the "Mention" option, the hoverbox states: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">If an administrator feels, that the requirement for signing the post isn't obvious in this help text, it can be modified by changing the text in the Wiki's [[MediaWiki:Echo-pref-tooltip-mention]] page.</span> == Begriffe == <div lang="en" dir="ltr" class="mw-content-ltr"> * notification - Any individual notice that is delivered by Echo </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * message - A notification about activity in a Flow discussion </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * alert - Any notification other than a message </div> == Siehe auch == * {{ll|Notifications/API}} * {{ll|Manual:Echo}} - Für Details über die Mention-Anforderungen * {{ll|Extension:Echo/Creating a new notification type}} (aktuell) * {{ll|Notifications/Developer_guide}} (veraltet) {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|miraheze=1|mywikis=1|prowiki=1|semantic core=1}} [[Category:Echo{{#translation:}}]] 2ox5v5j5nbs2b74v2wwn3jo6fmqfyva 5386970 5386968 2022-07-28T19:49:31Z ThisCarthing 17456337 Created page with "Alle Parameter sind optional:" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = notify |image = Screenshot_of_Echo_notification_extension.png |imagesize = 375 |author = <nowiki/> * [[User:Werdna|Andrew Garrett]] * [[User:Kaldari|Ryan Kaldari]] * [[User:Bsitu|Benny Situ]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides an in-wiki notification system that can be used by other extensions.</span> |version = Laufende Aktualisierungen |update = |download = {{WikimediaDownload}} |compatibility policy = rel |mediawiki = |license = |newhook1 = EchoGetEventsForRevision |newhook2 = BeforeCreateEchoEvent |newhook3 = BeforeDisplayOrangeAlert |newhook4 = EchoCanAbortNewMessagesAlert |newhook5 = EchoAbortEmailNotification |newhook6 = EchoGetBundleRules |newhook7 = EchoGetNotificationTypes |newhook8 = EchoGetDefaultNotifiedUsers |newhook9 = BeforeEchoEventInsert |newhook10 = EchoEventInsertComplete |newhook11 = EchoCreateNotificationComplete |phabricator = Notifications |table1 = echo_email_batch |table2 = echo_event |table3 = echo_notification |table4 = echo_subscription |table5 = echo_target_page |table6 = echo_push_provider |table7 = echo_push_subscription |table8 = echo_push_topic }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''Echo''' extension provides an in-wiki notification system that can be used by other extensions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:Thanks|nsp=0}} and {{ll|Extension:StructuredDiscussions|nsp=0}} are two MediaWiki extensions that make use of Echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Notifications}} for a full description of what this extension does.</span> == Herunterladen == {{WikimediaGitCheckout}} {{Note |1=<span lang="en" dir="ltr" class="mw-content-ltr">The master branch of this extension only supports the master branch of MediaWiki's core (currently {{MW stable branch number}}+).</span> <span lang="en" dir="ltr" class="mw-content-ltr">To use with 1.32–{{MW legacy branch number}}, you must switch to a matching branch (for example Echo {{MW legacy release git}} with core {{MW legacy release git}}).</span> }} == Installation == {{ExtensionInstall |repo-name=Echo |db-update=Yes |custom-steps0= * <span lang="en" dir="ltr" class="mw-content-ltr">The database user must have been granted the "REFERENCES" right for the database.</span> |custom-steps= * [[#Configuration|<span lang="en" dir="ltr" class="mw-content-ltr">If necessary configure at your convenience</span>]] |registration=required |no-registration-version=1.28 }} {{clear}} {{anchor|Configuration}} == Konfiguration == <span lang="en" dir="ltr" class="mw-content-ltr">In addition to setting default user preferences, you can also use the {{ll|Manual:Hooks/AddNewAccount|AddNewAccount}} hook to change user preferences on signup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">That allows setting different user preferences going forward without affecting existing users.</span> Siehe [[Special:DisplayNotificationsConfiguration]] für lokale Details. === Parameter === {| class="wikitable" |+ Konfigurationseinstellungen (Voreinstellungen in {{git file|project=mediawiki/extensions/Echo|file=extension.json}} festgelegt) |-- ! Parameter ! Standard ! Anmerkung |--- | <code>$wgEchoEnableEmailBatch</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to turn on email batch function</span> |--- | <code>$wgEchoUseJobQueue</code> | {{phpi|false}} | * <code>true</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defer web and email notification delivery via job queue.</span> * <code>false</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Deliver notifications immediately</span> |--- | <code>$wgEchoEmailFooterAddress</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">The organization address (or whatever text you want to appear in the footer of the email notifications).</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSender</code> | <code>$wgPasswordSender</code> | <span lang="en" dir="ltr" class="mw-content-ltr">The email address for both "from" and "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationSenderName</code> | [[MediaWiki:emailsender|<span lang="en" dir="ltr" class="mw-content-ltr">"emailsender" message</span>]] ({{int|emailsender}}) | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "from" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgNotificationReplyName</code> | No Reply | <span lang="en" dir="ltr" class="mw-content-ltr">Name for "reply to" on email notifications.</span> Sollte in LocalSettings.php definiert sein |--- | <code>$wgEchoCluster</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Use the main db if this is set to false, to use a specific external db, just use any key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |- | <code>$wgEchoSharedTrackingDB</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Shared database to use for keeping track of cross-wiki unread notifications; false to not keep track of it at all</span> |- | <code>$wgEchoSharedTrackingCluster</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Cluster the shared tracking database is located on; false if it is on the main one.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Must be a key defined in {{ll|Manual:$wgExternalServers|$wgExternalServers}}</span> |--- | <code>$wgEchoMaxUpdateCount</code> | 2000 | <span lang="en" dir="ltr" class="mw-content-ltr">The max number of notifications allowed for a user to do a live update, this is also the number of max notifications allowed for a user to have.</span> |- | <code>$wgEchoMaxMentionsCount</code> | 50 |<span lang="en" dir="ltr" class="mw-content-ltr">The max number of mention notifications allowed for a user to send at once</span> |- | <code>$wgEchoMentionStatusNotifications</code> | {{phpi|false}} |<span lang="en" dir="ltr" class="mw-content-ltr">Enable mention success/failure notifications</span> |- | <code>$wgEchoMentionsOnMultipleSectionEdits</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for multiple-section edits</span> |- | <code>$wgEchoMentionOnChanges</code> | {{phpi|true}} |<span lang="en" dir="ltr" class="mw-content-ltr">Trigger mentions for edits to existing comments, as long as a signature is added in the same section</span> |--- | <code>$wgEchoMaxMentionsInEditSummary</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Maximum number of users that will be notified that they were linked from an edit summary or 0 for no notifications</span> |--- | <code>$wgEchoBundleEmailInterval</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">The time interval between each bundle email in seconds; set a small number for test wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This should be set to 0 to disable email bundling if there is no delay queue support</span> |--- | <code>$wgEchoNewMsgAlert</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to enable a new talk page message alert for logged in users.</span> |- | <code>$wgEchoShowFooterNotice</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether or not to show the footer feedback notice in the notifications popup</span> |- | <code>$wgEchoFooterNoticeURL</code> | <nowiki>''</nowiki> | <span lang="en" dir="ltr" class="mw-content-ltr">A URL for the survey that appears in the footer feedback notice in the notification popup</span> |- | <code>$wgNotifyTypeAvailabilityByCategory</code> | <syntaxhighlight lang=php>[ // Otherwise, a user->user email could trigger an additional redundant notification email. 'emailuser' => [ 'web' => true, 'email' => false, ], 'mention-failure' => [ 'web' => true, 'email' => false, ], 'mention-success' => [ 'web' => true, 'email' => false, ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Define which notify types are available for each notification category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If any notify types are omitted, it defaults to $wgDefaultNotifyTypeAvailability.</span> |--- | <code>$wgEchoNotifiers</code> | <syntaxhighlight lang=php>[ 'web' => [ 'EchoNotifier', 'notifyWithNotification' ], 'email' => [ 'EchoNotifier', 'notifyWithEmail' ], ] </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Definitions of the different types of notification delivery that are possible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each definition consists of a class name and a function name.</span> Siehe auch die Klasse EchoNotificationController. |--- | <code>$wgEchoAgentBlacklist</code> | [] | <span lang="en" dir="ltr" class="mw-content-ltr">List of usernames which will not trigger notifications</span> |--- | <code>$wgEchoOnWikiBlacklist</code> | Echo-blacklist | <span lang="en" dir="ltr" class="mw-content-ltr">Page location of community maintained blacklist within NS_MEDIAWIKI containing one username per line which will not trigger notifications.</span> Setze auf null, um zu deaktivieren. |--- | <code>$wgEchoPerUserWhitelistFormat</code> | %s/Echo-whitelist | <span lang="en" dir="ltr" class="mw-content-ltr">An sprintf format of the location of the per-user notification agent whitelist within the NS_USER namespace.</span> <span lang="en" dir="ltr" class="mw-content-ltr">%s will be replaced with the users name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelists must contain one username per line which will always trigger notifications regardless of their existence in the blacklists.</span> Setze auf {{phpi|null}}, um zu deaktivieren. |- | <code>$wgEchoCrossWikiNotifications</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to enable the cross-wiki notifications feature.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable this feature you need to:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have a global user system (e.g. CentralAuth or a shared user table)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">have $wgMainStash and $wgMainWANCache shared between wikis</span> * koniguriere $wgEchoSharedTrackingDB |- | <code>$wgEchoUseCrossWikiBetaFeature</code> | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Feature flag for the cross-wiki notifications beta feature</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|true}}, the cross-wiki notifications preference will appear in the BetaFeatures section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this is {{phpi|false}}, it'll appear in the Notifications section instead.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This does not control whether cross-wiki notifications are enabled by default.</span> Für dies, verwende {{phpi|$wgDefaultUserOptions['echo-cross-wiki-notifications'] {{=}} true;}} |--- | <code>$wgEchoNotificationCategories</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Define the categories that notifications can belong to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Categories can be assigned the following parameters.</span> Alle Parameter sind optional: * <code>priority</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Controls the order in which notifications are displayed in preferences and batch emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Priority ranges from 1 to 10.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the priority is not specified, it defaults to 10, which is the lowest.</span> * <code>no-dismiss</code> - <span lang="en" dir="ltr" class="mw-content-ltr">disables the dismissability of notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It can either be set to an array of output formats (see <code>$wgEchoNotifiers</code>) or an array containing 'all'.</span> * <code>usergroups</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Specifies an array of usergroups eligible to receive the notifications in the category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If no usergroups parameter is specified, all groups are eligible.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If a notifications type doesn't have a category parameter, it is automatically assigned to the <code>other</code> category which is lowest priority and has no preferences or dismissibility.</span> |--- | <code>$wgEchoNotificationIcons</code> | ''Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">Defines icons, which are 30x30 images.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is passed to BeforeCreateEchoEvent so extensions can define their own icons with the same structure.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is recommended that extensions prefix their icon key.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An example is myextension-name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will help avoid namespace conflicts.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use either a path or a url, but not both.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'path' is relative to <code>$wgExtensionAssetsPath</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The value of 'url' should be a URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should customize the site icon URL, which is:</span> <code>$wgEchoNotificationIcons['site']['url']</code> |--- | <code>$wgEchoNotifications</code> | Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Define the event types for echo.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Event definitions are in the form of 'event-name' => [ ... ].</span> * <code>category</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defines the category the event belongs to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'other'.</span> * <code>group</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to 'neutral'.</span> * <code>bundle</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which output formats are available for bundling.</span> * <code>presentation-model</code> - <span lang="en" dir="ltr" class="mw-content-ltr">Define which class is used to render notification messages and links for notification panels, special page and emails.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It must extend <code>EchoEventPresentationModel</code>.</span> |- | <code>$wgEchoConfig</code> |Siehe {{git file|project=mediawiki/extensions/Echo|file=extension.json}} | <span lang="en" dir="ltr" class="mw-content-ltr">Configuration for EventLogging.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual schemas can be disabled.</span> |- | <code>$wgEchoPerUserBlacklist</code> | {{phpi|null}} | <span lang="en" dir="ltr" class="mw-content-ltr">Boolean that enabled Per User Blacklist.</span> |} === Benutzereinstellungen ==== {| class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Preference settings (defaults defined in {{git file|project=mediawiki/extensions/Echo|file=extension.json}})</span> |-- ! Einstellungen ! Standard ! Anmerkung |--- |- | <code>$wgDefaultUserOptions['echo-show-alert']</code> | {{phpi|true}} | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for showing the special talk page alert bar</span> |- | <code>$wgDefaultUserOptions['echo-email-frequency']</code> | 0 | Wie oft E-Mails standardmäßig gesendet werden sollen: * 0 - <span lang="en" dir="ltr" class="mw-content-ltr">send emails for each notification as they come in (default)</span> * -1 - Sende keine E-Mails * 1 - Jeden Tag * 7 - Alle 7 Tage * ... |- | <code>$wgDefaultUserOptions['echo-dismiss-feedback-alert']</code> | 0 | <span lang="en" dir="ltr" class="mw-content-ltr">Ensures the feedback alert is visible by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do not change; to disable, use <code>$wgEchoShowFooterNotice</code>.</span> |- | <code>$wgDefaultUserOptions['echo-email-format']</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Depends on <code>$wgAllowHTMLEmail</code></span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to use HTML or text email</span>. Either <code>html</code> or <code>plain-text</code>. |- | <code>$wgDefaultUserOptions["echo-subscriptions-email-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>false</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via email for a particular category</span> |- | <code>$wgDefaultUserOptions["echo-subscriptions-web-<nowiki/>{$category}"]</code> | <span lang="en" dir="ltr" class="mw-content-ltr"><code>true</code> for most categories; depends</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Default user preference for whether to notify via web for a particular category</span> |} == Architektur == <div lang="en" dir="ltr" class="mw-content-ltr"> See {{ll|Echo (Notifications)/Technical Architecture|the architecture section of the feature page}}. </div> == Verwendung == ; <span lang="en" dir="ltr" class="mw-content-ltr">Notification negative list / positive list</span> <span lang="en" dir="ltr" class="mw-content-ltr">There are occasionally specific users, typically bots, which perform maintenance tasks that should not generate notifications.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To handle these cases, users can be globally blacklisted from the LocalSettings.php file (or InitialiseSettings.php in the case of WMF wikis):</span> <syntaxhighlight lang="php"> $wgEchoAgentBlacklist = [ 'SampleBot', 'SampleUser' ]; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">There is also an on-wiki blacklist that can be maintained by the wiki's community.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The location of the global on-wiki blacklist defaults to [[MediaWiki:Echo-blacklist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Individual users can override the blacklist by creating a whitelist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The whitelist location defaults to [[Special:MyPage/Echo-whitelist]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All on-wiki lists expect to receive one case-specific username per line with no special markup or prefixes.</span> Zum Beispiel: SampleBot SampleUser ; <span lang="en" dir="ltr" class="mw-content-ltr">"Mention" option</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the notification types that this extension allows is: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">It might not be obvious to some users, but this particular notification only works when the person linking to another user's page also signs (<nowiki>~~~~</nowiki>) the post.</span><br /> <span lang="en" dir="ltr" class="mw-content-ltr">After installation of the extension, a new tab "Notifications" is created in a user's [[Special:Preferences]] page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Under the section "Notify me about these events", in front of the "Mention" option, the hoverbox states: "Notify me when someone links to my user page."</span> <span lang="en" dir="ltr" class="mw-content-ltr">If an administrator feels, that the requirement for signing the post isn't obvious in this help text, it can be modified by changing the text in the Wiki's [[MediaWiki:Echo-pref-tooltip-mention]] page.</span> == Begriffe == <div lang="en" dir="ltr" class="mw-content-ltr"> * notification - Any individual notice that is delivered by Echo </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * message - A notification about activity in a Flow discussion </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * alert - Any notification other than a message </div> == Siehe auch == * {{ll|Notifications/API}} * {{ll|Manual:Echo}} - Für Details über die Mention-Anforderungen * {{ll|Extension:Echo/Creating a new notification type}} (aktuell) * {{ll|Notifications/Developer_guide}} (veraltet) {{OnWikimedia}} {{Used by|bluespice=1|canasta=1|miraheze=1|mywikis=1|prowiki=1|semantic core=1}} [[Category:Echo{{#translation:}}]] kmwr152z3tuxvzr25zvh2g2wpzk5rme Extension:GWToolset/de 102 1427563 5386847 5372516 2022-07-28T19:22:11Z ThisCarthing 17456337 Created page with "Funktionsanfragen" wikitext text/x-wiki <languages /> {{Extension|templatemode = |status = beta |type1 = media |type2 = special |author = Dan Entous |username = dan-nl |description = <span lang="en" dir="ltr" class="mw-content-ltr">Mass upload of content based on provided metadata</span> |image = GWT-metadata-mapping.png |imagesize = 300px |version = 0.3.8 |update = 2014-09-16 |mediawiki = 1.22+ |php = 5.4+ |compatibility policy = rel |download = {{WikimediaDownload|GWToolset}} |needs-updatephp = No |readme = |changelog = |tags = |example = |compatibility = |bugzilla = GWToolset }} {{GWToolset_abstract}} == Installation == {{ExtensionInstall | GWToolset | custom-steps = <nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * '''[[phab:diffusion/EGWT/browse/master/INSTALL|Read the <code>INSTALL</code> file]]''' and make sure your wiki configuration satisfies all those dependences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Assign users to the '''gwtoolset''' group as appropriate with the [[Special:UserRights]] page. </div> }} == Verwendung == * {{ll|Help:Extension:GWToolset|2=<span lang="en" dir="ltr" class="mw-content-ltr">End User Documentation</span>}} * {{ll|Extension:GWToolset/Technical Architecture|2=Technische Architektur}} * {{ll|Extension:GWToolset/Technical Design|2=Technisches Design}} * {{ll|Extension:GWToolset/Technical Implementation|2=<span lang="en" dir="ltr" class="mw-content-ltr">Technical Implementation</span>}} == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> * [[commons:Special:MyLanguage/Commons:GLAMwiki Toolset Project|GWToolset project]] </div> * [https://bugzilla.wikimedia.org/buglist.cgi?bug_severity=enhancement&component=GWToolset&f1=resolution&list_id=350126&o1=notequals&v1=fixed Funktionsanfragen] <div lang="en" dir="ltr" class="mw-content-ltr"> == Notes and references == </div> <references/> {{OnWikimedia}} 0gxfa7suijvava1nk8pk64wzn7l40md Extension:Highlight Links in Category/de 102 1427572 5387152 5350426 2022-07-28T21:07:57Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''Highlight Links in Category''' is an extension that adds a CSS class to links pointing to members of a category. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator]. </div> == Installation == {{ExtensionInstall|HighlightLinksInCategory|registration=required}} == Konfigurationsparameter == ; $wgHighlightLinksInCategory : <span lang="en" dir="ltr" class="mw-content-ltr">This global is an array that configures which categories get an added CSS class. The keys are the Category names, which must include underscores instead of spaces. Do not include the Category: namespace. The value for each key is the CSS class you would like to add to that category. For example:</span> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want add more than one class, separate the class names with spaces, like </div> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can add as many of these as you want, but from a UX perspective it's probably not awesome to add 500 different style links. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If $wgHighlightLinksInCategory is not set or empty, this extension will do nothing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're running a wiki farm and need to turn it off on some wikis, set <syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight>; using {{phpi|false}} could lead to incorrect behavior.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Styling== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Simply add the styles you need for these links to MediaWiki:Common.css on your wiki. For example: </div> {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want one category to override another, you'll have to specify it with CSS. </div> {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> Or alternatively, you could have defined the original <code>a.templates</code> rule as <code>a.templates:not(.disambig)</code> instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There's also the link icon approach: </div> {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==User Toggles== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An easy way to set up toggling this highlighting on or off is to make a [[Extension:Gadgets|Gadget]] with CSS in it. Yes, this is a personalization extension that outsources the personalization part to other extensions; I can still sleep at night. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==How this works== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Right after MediaWiki determines which linked pages exist (to make redlinks), it runs the <code>GetLinkColours</code> hook (see LinkHolderArray.php).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As we have a list of all of the page ids which are linked on that page, we can run one database query to see which of these links are in the set of categories we want to highlight.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Because the query only happens on an index of the <code>categorylinks</code> table, it's reasonably fast.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then CSS classes are assigned based on the result, using the configuration values the user sets in <code>$wgHighlightLinksInCategory</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Explaining how CSS works is outside the scope of this document. </div> == Bekannte Probleme == <div lang="en" dir="ltr" class="mw-content-ltr"> * CSS styles are not added in Flow, because it doesn't appear to call the GetLinkColors hook there. </div> == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:Category:LinkEnd extensions]] - which customize links in other ways </div> {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] d5vu6y5w4i2lyhwcgqdued6hc16tkt1 Extension:HtmlFromFile/de 102 1427580 5386881 4859841 2022-07-28T19:34:25Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki <languages/> {{unmaintained extension |alternative=[[Extension:HTMLets]] * [[Extension:Widgets]] }} {{Extension|templatemode = |status = unmaintained |type1 = tag |type2 = |hook1 = ParserFirstCallInit |hook2 = |username = ConnyOnnyOnny |author = Constantin Berhard |description = <span lang="en" dir="ltr" class="mw-content-ltr">Includes HTML snippets from files into wiki pages</span> |image = |imagesize = |version = |update = |version preview = |update preview = |mediawiki = |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = CC0-1.0 |download = {{GitlabDownload|Thunis|HtmlFromFile}} |readme = |changelog = |example = |namespace = |parameters = $wgHtmlFromFileMappings |tags = |rights = |compatibility = |bugzilla = }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''HtmlFromFile''' extension includes some HTML snippet in the rendering of a wiki page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In the wiki markup you add <htmlfromfile>someName</htmlfromfile>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The extension does a lookup for "someName" in the configured mapping array (see below) to get a complete file name and then directly forwards the contents of that file to the viewer's browser.</span> == Installation == {{ExtensionInstall |download-link=[https://gitlab.com/Thunis/HtmlFromFile/-/archive/master/HtmlFromFile-master.zip Erweiterung herunterladen] }} == Konfigurationsparameter == ; $wgHtmlFromFileMappings : <span lang="en" dir="ltr" class="mw-content-ltr">Array which maps short names for in-wiki usage to actual file names where the content is</span> == Siehe auch == * {{ll|Extension:IframePage}} * {{ll|Extension:Widgets}} * {{ll|Extension:SecureInclude}} * {{ll|Extension:Secure HTML}} djgletjyx9oezgzf9zl2av0mfyn09hp Extension:ManageWiki/de 102 1427601 5386895 5345735 2022-07-28T19:40:16Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki <languages /> {{Extension |image = ManageWiki screenshot 2022.png |alt = test |status = stable |hook1 = CreateWikiCreation |hook2 = CreateWikiDeletion |hook3 = CreateWikiRename |hook4 = CreateWikiStatePrivate |hook5 = CreateWikiStatePublic |hook6 = CreateWikiTables |hook7 = GetPreferences |hook8 = LoadExtensionSchemaUpdates |hook9 = SetupAfterCache |hook10 = SkinBuildSidebar |newhook1 = CreateWikiStateClosed |newhook2 = CreateWikiStateOpen |newhook3 = CreateWikiStatePrivate |newhook4 = CreateWikiStatePublic |newhook5 = ManageWikiModifiedSettings |mediawiki = 1.36.0+ |php=7.2+ |needs-updatephp = Yes |version = continuous updates |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows wiki administrators to change many aspects of their configuration.</span> |maintainer = [https://meta.miraheze.org/wiki/Special:MyLanguage/Tech:SRE_Volunteers Miraheze system administrators] |download = {{GithubDownload|Miraheze|ManageWiki|translatewiki=1}} |readme = |translate = mwgithub-managewiki |rights = managewiki, managewiki-editdefault, managewiki-restricted |license = GPL-3.0 |phabricator = |pagedrive1 = }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''ManageWiki''' extension provides several special pages for wiki management: Special:ManageWiki, Special:ManageWiki/extensions, Special:ManageWiki/settings, Special:ManageWiki/namespaces and Special:ManageWiki/permissions. The names are self explanatory. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For detailed information please see [https://meta.miraheze.org/wiki/ManageWiki this detailed page]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator].</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [https://phabricator.miraheze.org/tag/managewiki/ here for the workboard].</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/miraheze/ManageWiki Erweiterung herunterladen] |registration=required |db-update=true |custom-steps0=* <span lang="en" dir="ltr" class="mw-content-ltr">First, download and install the separate extension {{ll|Extension:CreateWiki|CreateWiki}}.</span> }} == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> The ManageWiki page is used to manage several aspects of a wiki's settings. As mentioned above, users with the appropriate permissions can manage settings on their wiki, enable/disable extensions and also change permissions (wgGroupPermissions) directly from their wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All settings changes are listed at Special:Log/managewiki. Anyone who has the <code>managewiki</code> right can change wiki settings and use Special:ManageWiki but you only need the "read" right to view configuration. </div> == Konfiguration == {| class="wikitable" |-- ! Parameter ! Voreinstellung ! Anmerkung |--- | {{phpi|$wgManageWiki}} | <syntaxhighlight lang="php" inline>[ 'cdb' => false, 'core' => false, 'extensions' => false, 'namespaces' => false, 'permissions' => false, 'settings' => false, ];</syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Which modules of ManageWiki should be enabled on the wiki.</span> |--- | {{phpi|$wgManageWikiCDBDirectory}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">This will enable CDB capabilities in ManageWiki.</span> |--- | {{phpi|$wgManageWikiExtensions}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of extensions enabled within the wiki farm.</span> |--- | {{phpi|$wgManageWikiExtensionsDefault}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of default extensions.</span> |--- | {{phpi|$wgManageWikiSettings}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of settings that can be managed through Special:ManageWiki</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalAddGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgAddGroups.</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalRemoveGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgRemoveGroups.</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalRights}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgGroupPermissions.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of usergroups which ManageWiki can't manage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Will prevent users creating same named groups as well.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedRights}} | <syntaxhighlight lang="php" inline> [ 'managewiki-restricted', ]; </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">An array of user rights that ManageWiki can not manage and assign on wiki.</span> |--- | {{phpi|$wgManageWikiPermissionsDefaultPrivateGroup}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Name of a group to add to private wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">False disables this function.</span> |--- | {{phpi|$wgManageWikiHelpUrl}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">URL of a help page for ManageWiki on the local wiki farm.</span> |--- | {{phpi|$wgManageWikiSidebarLinks}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to show quick links to ManageWiki pages in the side bar.</span> |} == Siehe auch == * {{ll|Extension:CreateWiki}} * {{ll|Extension:PermissionManager}} {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Wiki farm extensions]] [[Category:Site management extensions{{#translation:}}]] m2yub9bug2a6rj5f0j9oa2iugfx78bd 5386897 5386895 2022-07-28T19:40:40Z ThisCarthing 17456337 Created page with "Lade zuerst die separate $1-Erweiterung herunter und installiere sie." wikitext text/x-wiki <languages /> {{Extension |image = ManageWiki screenshot 2022.png |alt = test |status = stable |hook1 = CreateWikiCreation |hook2 = CreateWikiDeletion |hook3 = CreateWikiRename |hook4 = CreateWikiStatePrivate |hook5 = CreateWikiStatePublic |hook6 = CreateWikiTables |hook7 = GetPreferences |hook8 = LoadExtensionSchemaUpdates |hook9 = SetupAfterCache |hook10 = SkinBuildSidebar |newhook1 = CreateWikiStateClosed |newhook2 = CreateWikiStateOpen |newhook3 = CreateWikiStatePrivate |newhook4 = CreateWikiStatePublic |newhook5 = ManageWikiModifiedSettings |mediawiki = 1.36.0+ |php=7.2+ |needs-updatephp = Yes |version = continuous updates |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows wiki administrators to change many aspects of their configuration.</span> |maintainer = [https://meta.miraheze.org/wiki/Special:MyLanguage/Tech:SRE_Volunteers Miraheze system administrators] |download = {{GithubDownload|Miraheze|ManageWiki|translatewiki=1}} |readme = |translate = mwgithub-managewiki |rights = managewiki, managewiki-editdefault, managewiki-restricted |license = GPL-3.0 |phabricator = |pagedrive1 = }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''ManageWiki''' extension provides several special pages for wiki management: Special:ManageWiki, Special:ManageWiki/extensions, Special:ManageWiki/settings, Special:ManageWiki/namespaces and Special:ManageWiki/permissions. The names are self explanatory. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For detailed information please see [https://meta.miraheze.org/wiki/ManageWiki this detailed page]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator].</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [https://phabricator.miraheze.org/tag/managewiki/ here for the workboard].</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/miraheze/ManageWiki Erweiterung herunterladen] |registration=required |db-update=true |custom-steps0=* Lade zuerst die separate {{ll|Extension:CreateWiki|CreateWiki}}-Erweiterung herunter und installiere sie. }} == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> The ManageWiki page is used to manage several aspects of a wiki's settings. As mentioned above, users with the appropriate permissions can manage settings on their wiki, enable/disable extensions and also change permissions (wgGroupPermissions) directly from their wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All settings changes are listed at Special:Log/managewiki. Anyone who has the <code>managewiki</code> right can change wiki settings and use Special:ManageWiki but you only need the "read" right to view configuration. </div> == Konfiguration == {| class="wikitable" |-- ! Parameter ! Voreinstellung ! Anmerkung |--- | {{phpi|$wgManageWiki}} | <syntaxhighlight lang="php" inline>[ 'cdb' => false, 'core' => false, 'extensions' => false, 'namespaces' => false, 'permissions' => false, 'settings' => false, ];</syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Which modules of ManageWiki should be enabled on the wiki.</span> |--- | {{phpi|$wgManageWikiCDBDirectory}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">This will enable CDB capabilities in ManageWiki.</span> |--- | {{phpi|$wgManageWikiExtensions}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of extensions enabled within the wiki farm.</span> |--- | {{phpi|$wgManageWikiExtensionsDefault}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of default extensions.</span> |--- | {{phpi|$wgManageWikiSettings}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of settings that can be managed through Special:ManageWiki</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalAddGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgAddGroups.</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalRemoveGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgRemoveGroups.</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalRights}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgGroupPermissions.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of usergroups which ManageWiki can't manage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Will prevent users creating same named groups as well.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedRights}} | <syntaxhighlight lang="php" inline> [ 'managewiki-restricted', ]; </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">An array of user rights that ManageWiki can not manage and assign on wiki.</span> |--- | {{phpi|$wgManageWikiPermissionsDefaultPrivateGroup}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Name of a group to add to private wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">False disables this function.</span> |--- | {{phpi|$wgManageWikiHelpUrl}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">URL of a help page for ManageWiki on the local wiki farm.</span> |--- | {{phpi|$wgManageWikiSidebarLinks}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to show quick links to ManageWiki pages in the side bar.</span> |} == Siehe auch == * {{ll|Extension:CreateWiki}} * {{ll|Extension:PermissionManager}} {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Wiki farm extensions]] [[Category:Site management extensions{{#translation:}}]] 89n8gfix1fgydrzapnbaadtgpv6t6p1 5386899 5386897 2022-07-28T19:41:31Z ThisCarthing 17456337 Created page with "ManageWikis Version von $wgAddGroups." wikitext text/x-wiki <languages /> {{Extension |image = ManageWiki screenshot 2022.png |alt = test |status = stable |hook1 = CreateWikiCreation |hook2 = CreateWikiDeletion |hook3 = CreateWikiRename |hook4 = CreateWikiStatePrivate |hook5 = CreateWikiStatePublic |hook6 = CreateWikiTables |hook7 = GetPreferences |hook8 = LoadExtensionSchemaUpdates |hook9 = SetupAfterCache |hook10 = SkinBuildSidebar |newhook1 = CreateWikiStateClosed |newhook2 = CreateWikiStateOpen |newhook3 = CreateWikiStatePrivate |newhook4 = CreateWikiStatePublic |newhook5 = ManageWikiModifiedSettings |mediawiki = 1.36.0+ |php=7.2+ |needs-updatephp = Yes |version = continuous updates |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows wiki administrators to change many aspects of their configuration.</span> |maintainer = [https://meta.miraheze.org/wiki/Special:MyLanguage/Tech:SRE_Volunteers Miraheze system administrators] |download = {{GithubDownload|Miraheze|ManageWiki|translatewiki=1}} |readme = |translate = mwgithub-managewiki |rights = managewiki, managewiki-editdefault, managewiki-restricted |license = GPL-3.0 |phabricator = |pagedrive1 = }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''ManageWiki''' extension provides several special pages for wiki management: Special:ManageWiki, Special:ManageWiki/extensions, Special:ManageWiki/settings, Special:ManageWiki/namespaces and Special:ManageWiki/permissions. The names are self explanatory. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For detailed information please see [https://meta.miraheze.org/wiki/ManageWiki this detailed page]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator].</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [https://phabricator.miraheze.org/tag/managewiki/ here for the workboard].</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/miraheze/ManageWiki Erweiterung herunterladen] |registration=required |db-update=true |custom-steps0=* Lade zuerst die separate {{ll|Extension:CreateWiki|CreateWiki}}-Erweiterung herunter und installiere sie. }} == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> The ManageWiki page is used to manage several aspects of a wiki's settings. As mentioned above, users with the appropriate permissions can manage settings on their wiki, enable/disable extensions and also change permissions (wgGroupPermissions) directly from their wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All settings changes are listed at Special:Log/managewiki. Anyone who has the <code>managewiki</code> right can change wiki settings and use Special:ManageWiki but you only need the "read" right to view configuration. </div> == Konfiguration == {| class="wikitable" |-- ! Parameter ! Voreinstellung ! Anmerkung |--- | {{phpi|$wgManageWiki}} | <syntaxhighlight lang="php" inline>[ 'cdb' => false, 'core' => false, 'extensions' => false, 'namespaces' => false, 'permissions' => false, 'settings' => false, ];</syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Which modules of ManageWiki should be enabled on the wiki.</span> |--- | {{phpi|$wgManageWikiCDBDirectory}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">This will enable CDB capabilities in ManageWiki.</span> |--- | {{phpi|$wgManageWikiExtensions}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of extensions enabled within the wiki farm.</span> |--- | {{phpi|$wgManageWikiExtensionsDefault}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of default extensions.</span> |--- | {{phpi|$wgManageWikiSettings}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of settings that can be managed through Special:ManageWiki</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalAddGroups}} | {{phpi|false}} | ManageWikis Version von $wgAddGroups. |--- | {{phpi|$wgManageWikiPermissionsAdditionalRemoveGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgRemoveGroups.</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalRights}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgGroupPermissions.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of usergroups which ManageWiki can't manage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Will prevent users creating same named groups as well.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedRights}} | <syntaxhighlight lang="php" inline> [ 'managewiki-restricted', ]; </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">An array of user rights that ManageWiki can not manage and assign on wiki.</span> |--- | {{phpi|$wgManageWikiPermissionsDefaultPrivateGroup}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Name of a group to add to private wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">False disables this function.</span> |--- | {{phpi|$wgManageWikiHelpUrl}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">URL of a help page for ManageWiki on the local wiki farm.</span> |--- | {{phpi|$wgManageWikiSidebarLinks}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to show quick links to ManageWiki pages in the side bar.</span> |} == Siehe auch == * {{ll|Extension:CreateWiki}} * {{ll|Extension:PermissionManager}} {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Wiki farm extensions]] [[Category:Site management extensions{{#translation:}}]] loexsz2pwctsbmj4slp405zhwiexbsv 5386901 5386899 2022-07-28T19:41:52Z ThisCarthing 17456337 Created page with "ManageWikis Version von $wgGroupPermissions." wikitext text/x-wiki <languages /> {{Extension |image = ManageWiki screenshot 2022.png |alt = test |status = stable |hook1 = CreateWikiCreation |hook2 = CreateWikiDeletion |hook3 = CreateWikiRename |hook4 = CreateWikiStatePrivate |hook5 = CreateWikiStatePublic |hook6 = CreateWikiTables |hook7 = GetPreferences |hook8 = LoadExtensionSchemaUpdates |hook9 = SetupAfterCache |hook10 = SkinBuildSidebar |newhook1 = CreateWikiStateClosed |newhook2 = CreateWikiStateOpen |newhook3 = CreateWikiStatePrivate |newhook4 = CreateWikiStatePublic |newhook5 = ManageWikiModifiedSettings |mediawiki = 1.36.0+ |php=7.2+ |needs-updatephp = Yes |version = continuous updates |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows wiki administrators to change many aspects of their configuration.</span> |maintainer = [https://meta.miraheze.org/wiki/Special:MyLanguage/Tech:SRE_Volunteers Miraheze system administrators] |download = {{GithubDownload|Miraheze|ManageWiki|translatewiki=1}} |readme = |translate = mwgithub-managewiki |rights = managewiki, managewiki-editdefault, managewiki-restricted |license = GPL-3.0 |phabricator = |pagedrive1 = }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''ManageWiki''' extension provides several special pages for wiki management: Special:ManageWiki, Special:ManageWiki/extensions, Special:ManageWiki/settings, Special:ManageWiki/namespaces and Special:ManageWiki/permissions. The names are self explanatory. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For detailed information please see [https://meta.miraheze.org/wiki/ManageWiki this detailed page]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator].</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [https://phabricator.miraheze.org/tag/managewiki/ here for the workboard].</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/miraheze/ManageWiki Erweiterung herunterladen] |registration=required |db-update=true |custom-steps0=* Lade zuerst die separate {{ll|Extension:CreateWiki|CreateWiki}}-Erweiterung herunter und installiere sie. }} == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> The ManageWiki page is used to manage several aspects of a wiki's settings. As mentioned above, users with the appropriate permissions can manage settings on their wiki, enable/disable extensions and also change permissions (wgGroupPermissions) directly from their wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All settings changes are listed at Special:Log/managewiki. Anyone who has the <code>managewiki</code> right can change wiki settings and use Special:ManageWiki but you only need the "read" right to view configuration. </div> == Konfiguration == {| class="wikitable" |-- ! Parameter ! Voreinstellung ! Anmerkung |--- | {{phpi|$wgManageWiki}} | <syntaxhighlight lang="php" inline>[ 'cdb' => false, 'core' => false, 'extensions' => false, 'namespaces' => false, 'permissions' => false, 'settings' => false, ];</syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Which modules of ManageWiki should be enabled on the wiki.</span> |--- | {{phpi|$wgManageWikiCDBDirectory}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">This will enable CDB capabilities in ManageWiki.</span> |--- | {{phpi|$wgManageWikiExtensions}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of extensions enabled within the wiki farm.</span> |--- | {{phpi|$wgManageWikiExtensionsDefault}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of default extensions.</span> |--- | {{phpi|$wgManageWikiSettings}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of settings that can be managed through Special:ManageWiki</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalAddGroups}} | {{phpi|false}} | ManageWikis Version von $wgAddGroups. |--- | {{phpi|$wgManageWikiPermissionsAdditionalRemoveGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgRemoveGroups.</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalRights}} | {{phpi|false}} | ManageWikis Version von $wgGroupPermissions. |--- | {{phpi|$wgManageWikiPermissionsDisallowedGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of usergroups which ManageWiki can't manage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Will prevent users creating same named groups as well.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedRights}} | <syntaxhighlight lang="php" inline> [ 'managewiki-restricted', ]; </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">An array of user rights that ManageWiki can not manage and assign on wiki.</span> |--- | {{phpi|$wgManageWikiPermissionsDefaultPrivateGroup}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Name of a group to add to private wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">False disables this function.</span> |--- | {{phpi|$wgManageWikiHelpUrl}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">URL of a help page for ManageWiki on the local wiki farm.</span> |--- | {{phpi|$wgManageWikiSidebarLinks}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to show quick links to ManageWiki pages in the side bar.</span> |} == Siehe auch == * {{ll|Extension:CreateWiki}} * {{ll|Extension:PermissionManager}} {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Wiki farm extensions]] [[Category:Site management extensions{{#translation:}}]] o0lx0klynsdifiyyvpjniip01p3smsw 5386903 5386901 2022-07-28T19:42:09Z ThisCarthing 17456337 Created page with "False deaktiviert diese Funktion." wikitext text/x-wiki <languages /> {{Extension |image = ManageWiki screenshot 2022.png |alt = test |status = stable |hook1 = CreateWikiCreation |hook2 = CreateWikiDeletion |hook3 = CreateWikiRename |hook4 = CreateWikiStatePrivate |hook5 = CreateWikiStatePublic |hook6 = CreateWikiTables |hook7 = GetPreferences |hook8 = LoadExtensionSchemaUpdates |hook9 = SetupAfterCache |hook10 = SkinBuildSidebar |newhook1 = CreateWikiStateClosed |newhook2 = CreateWikiStateOpen |newhook3 = CreateWikiStatePrivate |newhook4 = CreateWikiStatePublic |newhook5 = ManageWikiModifiedSettings |mediawiki = 1.36.0+ |php=7.2+ |needs-updatephp = Yes |version = continuous updates |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows wiki administrators to change many aspects of their configuration.</span> |maintainer = [https://meta.miraheze.org/wiki/Special:MyLanguage/Tech:SRE_Volunteers Miraheze system administrators] |download = {{GithubDownload|Miraheze|ManageWiki|translatewiki=1}} |readme = |translate = mwgithub-managewiki |rights = managewiki, managewiki-editdefault, managewiki-restricted |license = GPL-3.0 |phabricator = |pagedrive1 = }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''ManageWiki''' extension provides several special pages for wiki management: Special:ManageWiki, Special:ManageWiki/extensions, Special:ManageWiki/settings, Special:ManageWiki/namespaces and Special:ManageWiki/permissions. The names are self explanatory. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For detailed information please see [https://meta.miraheze.org/wiki/ManageWiki this detailed page]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator].</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [https://phabricator.miraheze.org/tag/managewiki/ here for the workboard].</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/miraheze/ManageWiki Erweiterung herunterladen] |registration=required |db-update=true |custom-steps0=* Lade zuerst die separate {{ll|Extension:CreateWiki|CreateWiki}}-Erweiterung herunter und installiere sie. }} == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> The ManageWiki page is used to manage several aspects of a wiki's settings. As mentioned above, users with the appropriate permissions can manage settings on their wiki, enable/disable extensions and also change permissions (wgGroupPermissions) directly from their wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All settings changes are listed at Special:Log/managewiki. Anyone who has the <code>managewiki</code> right can change wiki settings and use Special:ManageWiki but you only need the "read" right to view configuration. </div> == Konfiguration == {| class="wikitable" |-- ! Parameter ! Voreinstellung ! Anmerkung |--- | {{phpi|$wgManageWiki}} | <syntaxhighlight lang="php" inline>[ 'cdb' => false, 'core' => false, 'extensions' => false, 'namespaces' => false, 'permissions' => false, 'settings' => false, ];</syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Which modules of ManageWiki should be enabled on the wiki.</span> |--- | {{phpi|$wgManageWikiCDBDirectory}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">This will enable CDB capabilities in ManageWiki.</span> |--- | {{phpi|$wgManageWikiExtensions}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of extensions enabled within the wiki farm.</span> |--- | {{phpi|$wgManageWikiExtensionsDefault}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of default extensions.</span> |--- | {{phpi|$wgManageWikiSettings}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of settings that can be managed through Special:ManageWiki</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalAddGroups}} | {{phpi|false}} | ManageWikis Version von $wgAddGroups. |--- | {{phpi|$wgManageWikiPermissionsAdditionalRemoveGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">ManageWiki's version of $wgRemoveGroups.</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalRights}} | {{phpi|false}} | ManageWikis Version von $wgGroupPermissions. |--- | {{phpi|$wgManageWikiPermissionsDisallowedGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of usergroups which ManageWiki can't manage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Will prevent users creating same named groups as well.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedRights}} | <syntaxhighlight lang="php" inline> [ 'managewiki-restricted', ]; </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">An array of user rights that ManageWiki can not manage and assign on wiki.</span> |--- | {{phpi|$wgManageWikiPermissionsDefaultPrivateGroup}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Name of a group to add to private wikis.</span> False deaktiviert diese Funktion. |--- | {{phpi|$wgManageWikiHelpUrl}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">URL of a help page for ManageWiki on the local wiki farm.</span> |--- | {{phpi|$wgManageWikiSidebarLinks}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to show quick links to ManageWiki pages in the side bar.</span> |} == Siehe auch == * {{ll|Extension:CreateWiki}} * {{ll|Extension:PermissionManager}} {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Wiki farm extensions]] [[Category:Site management extensions{{#translation:}}]] nuxdhezqawlfktqvxoabqj9me1zi9j5 5386905 5386903 2022-07-28T19:42:17Z ThisCarthing 17456337 Created page with "ManageWikis Version von $wgRemoveGroups." wikitext text/x-wiki <languages /> {{Extension |image = ManageWiki screenshot 2022.png |alt = test |status = stable |hook1 = CreateWikiCreation |hook2 = CreateWikiDeletion |hook3 = CreateWikiRename |hook4 = CreateWikiStatePrivate |hook5 = CreateWikiStatePublic |hook6 = CreateWikiTables |hook7 = GetPreferences |hook8 = LoadExtensionSchemaUpdates |hook9 = SetupAfterCache |hook10 = SkinBuildSidebar |newhook1 = CreateWikiStateClosed |newhook2 = CreateWikiStateOpen |newhook3 = CreateWikiStatePrivate |newhook4 = CreateWikiStatePublic |newhook5 = ManageWikiModifiedSettings |mediawiki = 1.36.0+ |php=7.2+ |needs-updatephp = Yes |version = continuous updates |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows wiki administrators to change many aspects of their configuration.</span> |maintainer = [https://meta.miraheze.org/wiki/Special:MyLanguage/Tech:SRE_Volunteers Miraheze system administrators] |download = {{GithubDownload|Miraheze|ManageWiki|translatewiki=1}} |readme = |translate = mwgithub-managewiki |rights = managewiki, managewiki-editdefault, managewiki-restricted |license = GPL-3.0 |phabricator = |pagedrive1 = }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''ManageWiki''' extension provides several special pages for wiki management: Special:ManageWiki, Special:ManageWiki/extensions, Special:ManageWiki/settings, Special:ManageWiki/namespaces and Special:ManageWiki/permissions. The names are self explanatory. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For detailed information please see [https://meta.miraheze.org/wiki/ManageWiki this detailed page]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator].</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [https://phabricator.miraheze.org/tag/managewiki/ here for the workboard].</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/miraheze/ManageWiki Erweiterung herunterladen] |registration=required |db-update=true |custom-steps0=* Lade zuerst die separate {{ll|Extension:CreateWiki|CreateWiki}}-Erweiterung herunter und installiere sie. }} == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> The ManageWiki page is used to manage several aspects of a wiki's settings. As mentioned above, users with the appropriate permissions can manage settings on their wiki, enable/disable extensions and also change permissions (wgGroupPermissions) directly from their wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All settings changes are listed at Special:Log/managewiki. Anyone who has the <code>managewiki</code> right can change wiki settings and use Special:ManageWiki but you only need the "read" right to view configuration. </div> == Konfiguration == {| class="wikitable" |-- ! Parameter ! Voreinstellung ! Anmerkung |--- | {{phpi|$wgManageWiki}} | <syntaxhighlight lang="php" inline>[ 'cdb' => false, 'core' => false, 'extensions' => false, 'namespaces' => false, 'permissions' => false, 'settings' => false, ];</syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">Which modules of ManageWiki should be enabled on the wiki.</span> |--- | {{phpi|$wgManageWikiCDBDirectory}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">This will enable CDB capabilities in ManageWiki.</span> |--- | {{phpi|$wgManageWikiExtensions}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of extensions enabled within the wiki farm.</span> |--- | {{phpi|$wgManageWikiExtensionsDefault}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of default extensions.</span> |--- | {{phpi|$wgManageWikiSettings}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of settings that can be managed through Special:ManageWiki</span> |--- | {{phpi|$wgManageWikiPermissionsAdditionalAddGroups}} | {{phpi|false}} | ManageWikis Version von $wgAddGroups. |--- | {{phpi|$wgManageWikiPermissionsAdditionalRemoveGroups}} | {{phpi|false}} | ManageWikis Version von $wgRemoveGroups. |--- | {{phpi|$wgManageWikiPermissionsAdditionalRights}} | {{phpi|false}} | ManageWikis Version von $wgGroupPermissions. |--- | {{phpi|$wgManageWikiPermissionsDisallowedGroups}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">An array of usergroups which ManageWiki can't manage.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Will prevent users creating same named groups as well.</span> |--- | {{phpi|$wgManageWikiPermissionsDisallowedRights}} | <syntaxhighlight lang="php" inline> [ 'managewiki-restricted', ]; </syntaxhighlight> | <span lang="en" dir="ltr" class="mw-content-ltr">An array of user rights that ManageWiki can not manage and assign on wiki.</span> |--- | {{phpi|$wgManageWikiPermissionsDefaultPrivateGroup}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Name of a group to add to private wikis.</span> False deaktiviert diese Funktion. |--- | {{phpi|$wgManageWikiHelpUrl}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">URL of a help page for ManageWiki on the local wiki farm.</span> |--- | {{phpi|$wgManageWikiSidebarLinks}} | {{phpi|false}} | <span lang="en" dir="ltr" class="mw-content-ltr">Whether to show quick links to ManageWiki pages in the side bar.</span> |} == Siehe auch == * {{ll|Extension:CreateWiki}} * {{ll|Extension:PermissionManager}} {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Wiki farm extensions]] [[Category:Site management extensions{{#translation:}}]] tnusosn8t1sbfvzaz7gpbayaafc1noy Extension:NoTitle/de 102 1427630 5386849 4856568 2022-07-28T19:22:38Z ThisCarthing 17456337 Created page with "$1 funktioniert für jede Seite." wikitext text/x-wiki <languages /> {{Extension |status = stable |type = extended syntax |author = * [[User:Clofresh|Carlo Cabanilla]], * [[User:AABoyles|Tony Boyles]], * [[User:Legoktm|Kunal Mehta]] |image = |version = 0.4.0 |update = 2018-07-16 |mediawiki = 1.29+ |php = 5.5+ |download = {{WikimediaDownload}} |needs-updatephp = No |readme = |changelog = |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds a magic word that lets you hide the main title heading</span> |parameters = |rights = |example = [https://sandbox.semantic-mediawiki.org/wiki/NoTitle sandbox.semantic-mediawiki.org] |pagedrive1 = true }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''NoTitle''' extension adds a magic word, <code>__NOTITLE__</code>, that lets you hide the main title heading on any page. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> Add <code>__NOTITLE__</code> behaviour switch on any pages where you want to hide the title. </div> <ref><span lang="en" dir="ltr" class="mw-content-ltr">This extension will work for any skin that puts the title heading in an {{tag|h1|open}} with <code>class="firstHeading"</code>, including the default [[Special:MyLanguage/Skin:Vector|Vector skin]].</span></ref> {{Note|1=<code><nowiki>{{DISPLAYTITLE:newtitle}}</nowiki></code> funktioniert für jede Seite.}} == Installation == {{ExtensionInstall |repo-name=NoTitle |localsettings=$wgRestrictDisplayTitle = false; |registration=only |no-registration-version=1.30 }} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Notes== </div> <references/> == Siehe auch == <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Manual:FAQ#How do I hide the main page title?|How to hide the Main Page title]] - Manual for hiding only the Main Page title. </div> [[Category:HTML head extensions{{#translation:}}]] mfv2s1nhoss45more62r0envdj74xfw Extension:Parser function extensions/de 102 1427648 5386907 4901223 2022-07-28T19:42:26Z ThisCarthing 17456337 Created page with "Erweiterung" wikitext text/x-wiki <languages /> {{outdated}} <div lang="en" dir="ltr" class="mw-content-ltr"> A "'''[[Special:MyLanguage/Help:Extension:ParserFunctions|parser function]]'''" is a [[Special:MyLanguage/Help:Templates|template]]-like construct that returns a value based on at least one unnamed parameter, separated from the function name by a colon [''':''']. There may be more parameters, as well; like those of ordinary templates, these additional parameters are each preceded by a "pipe" ['''|''']. In the case of a [[w:Number sign|hash character]] [#] at the start of the function name (which prevents collision with namespaces and interwiki prefixes), this may or may not be considered part of the name. If it is considered part of the name, the syntax is of the form </div> :<nowiki>{{</nowiki>''functionname'': ''argument 1'' | ''argument 2'' | ''argument 3''...}} {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If the caller has '''no arguments''' to provide the parser function, then the form is simply <nowiki>{{</nowiki>''functionname'':<nowiki>}}</nowiki> or, when a hash character applies (as is normally the case) then the form is <nowiki>{{</nowiki>''#functionname'':<nowiki>}}</nowiki>. If the trailing colon is not supplied, then ''functionname'' is not recognized by the parser.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> Arguments cannot directly contain "|" or "}}" except as part of the code of a template call, parser function call, variable, link or image, but they can contain them arbitrarily using a template, e.g., {{tim|!}}, or a parser function. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The code can specify whether the function name is case-sensitive. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The separation of the arguments from each other is with "|", and from the function name is with the first ":" The expansion of each of these pieces is standard, as in [[Special:ExpandTemplates]] (which is a good place to experiment, by the way, if you are learning this stuff) and is beyond the control of the parser function itself. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> However, everything else can be different for each parser function, including: *whether an argument is just a value, or of the form ''parname'' = ''parvalue'', or whatever *if applicable, whether parameter names are case-sensitive </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Syntax prescribed by a parser function extension== </div> <span lang="en" dir="ltr" class="mw-content-ltr">In view of the above, it is advantageous to make an extension such that the syntax to be used in an argument does ''not'' contain the [[w:Vertical_bar|pipe character]] "|" or double braces (more specifically, double closing braces "}}" ).</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, in spite of the fact that a pipe character would otherwise seem a suitable symbol for, e.g., a choice or union (see, e.g., [http://semeb.com/dpldemo/index.php/Manual#category]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Allowing such codes is harmless if an alternative code is also allowed, e.g. "\" for "|".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Table of functions== </div> {|class="sortable wikitable" !Erweiterung!!<span lang="en" dir="ltr" class="mw-content-ltr">function</span>!!<span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki version</span> |- |[[m:Special:MyLanguage/Help:Parser function#LC|built-in]]||lc||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#UC|built-in]]||uc||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#LCFIRST|built-in]]||lcfirst||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#UCFIRST|built-in]]||ucfirst||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#URLENCODE|built-in]]||urlencode||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#ANCHORENCODE|built-in]]||anchorencode||1.8+ |- |[[m:Special:MyLanguage/Help:Parser function#URLs etc.|built-in]]||localurl||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#URLs etc.|built-in]]||fullurl||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function##language:|built-in]]||#language||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#|built-in]]||#special||1.9+ |- |[[m:Special:MyLanguage/Help:Parser function#|built-in]]||#tag||1.12+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##expr|usage}})||#expr||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifexpr|usage}})||#ifexpr||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##if|usage}})||#if||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifeq|usage}})||#ifeq||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifexist|usage}})||#ifexist||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##rel2abs|usage}})||#rel2abs||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##titleparts|usage}})||#titleparts||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##switch|usage}})||#switch||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##time|usage}})||#time||1.19+ |- |{{ll|Extension:AddScriptCss|nsp=0}}||#addscript||Archived |- |{{ll|Extension:Arrays|nsp=0}}||#arraydefine||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraydiff||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayindex||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayintersect||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraymerge||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayprint||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayreset||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysearch||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysearcharray||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysize||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayslice||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysort||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraytohash||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayunion||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayunique||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#hashtoarray||1.23+ |- |{{ll|Extension:Attachments|nsp=0}}||#attach||1.31+ |- |{{ll|Extension:Attachments|nsp=0}}||#exturl||1.31+ |- |{{ll|Extension:Babel|nsp=0}}||#babel||1.30+ |- |{{ll|Extension:CSS|nsp=0}}||#css||1.25+ |- |{{ll|Extension:Coordinate|nsp=0}}||#coordinate||1.10+ |- |{{ll|Extension:Counter|nsp=0}}||#+||1.15+ |- |{{ll|Extension:Data|nsp=0}}|||#data||Archived |- |{{ll|Extension:Data|nsp=0}}|||#sort||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#arg||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#ip||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#rand||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#skin||Archived |- |{{ll|Extension:DynamicPageList (third-party)|nsp=0}}|||#dpl |- |{{ll|Extension:ExpandAfter|nsp=0}}||#expandafter ({{ll|Extension:ExpandAfter#Usage Note|deprecated}}, see: #tag)||Archived |- |{{ll|Extension:ForeachFunction|nsp=0}}||#foreachx||Archived |- |{{ll|Extension:ForeachFunction|nsp=0}}||#foreachy||Archived |- |{{ll|Extension:HasCategory|nsp=0}}||#ifhascat||Archived |- |{{ll|Extension:HideNamespace|nsp=0}}||#hidens||1.15+ |- |{{ll|Extension:HideNamespace|nsp=0}}||#unhidens||1.15+ |- |{{ll|Extension:ImageLink|nsp=0}}||#img (old: #imagelink, {{ll|Extension:ImageLink#Usage Note|deprecated}})||Archived |- |{{ll|Extension:Infobox Data Capture|nsp=0}}||#dataentry||Archived |- |{{ll|Extension:Infobox Data Capture|nsp=0}}||#listsplit||Archived |- |{{ll|Extension:InterWikiLinkManager|nsp=0}}||#iwl||Archived |- |{{ll|Extension:KeyValue|nsp=0}}||#keyvalue||1.16+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lst||1.25+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lstx||1.25+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lsth||1.25+ |- |{{ll|Extension:LoopFunctions|nsp=0}}||#for||1.23+ |- |{{ll|Extension:LoopFunctions|nsp=0}}||#foreach||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#while||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#dowhile||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#forargs||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#fornumargs||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#loop||1.25+ |- |{{ll|Extension:Maps|nsp=0}}||#geocode||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#display_map||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#display_point||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#coordinates||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#distance||1.27+ |- |{{ll|Extension:MediaFunctions|nsp=0}}||#media..||1.23+ |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#pagebefore||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#pageafter||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#firstpage||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#lastpage||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pagetitle||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pagesubtitle||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pageexists||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varget||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varcapset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#cshow||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varaset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varaget||Archived |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#expr (extended)||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifexpr (extended)||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#min||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#max||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#if||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifeq||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifexist||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#rel2abs||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#switch||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#time||1.19+ |- |{{ll|Extension:Pipe Escape|nsp=0}}||#!||1.23+ |- |{{ll|Extension:QPoll|nsp=0}}||#qpuserchoice||1.23+ |- |{{ll|Extension:RegexTools|nsp=0}}||#regex||Archived |- |{{ll|Extension:RegexTools|nsp=0}}||#regex_vars||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#pg||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#ps||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#pf||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#gg||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#gs||Archived |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#ask||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#concept||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#info||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#show||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#set||1.27+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#len||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#pos||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#rpos||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#sub||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#pad||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#replace||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#explode||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#urlencode||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#urldecode||1.7+ |- |{{ll|Extension:TreeAndMenu|nsp=0}}|||#tree||1.23+ |- |{{ll|Extension:TreeAndMenu|nsp=0}}|||#menu||1.23+ |- |{{ll|Extension:Variables|nsp=0}}||#vardefine||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#vardefineecho||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#var||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#varexists||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#var_final||1.29+ |- |{{ll|Extension:Wikibase Client|nsp=0}}||#property|| |- |{{ll|Extension:Wikibase Client|nsp=0}}||#statements|| |- |} == Siehe auch == *{{ll|Help:Magic words}} *{{ll|Category:Parser function extensions}} *{{ll|Manual:Parser functions|Writing parser functions}} (software development) *{{ll|Extending wiki markup#Parser_functions}} *[http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/examples/Parser_function.php Sample parser function], from {{ll|Subversion|SVN}} *Parser function extensions with documentation on Meta: **{{ll|Extension:Data}} - requires extra table data_extension in database **{{ll|Extension:DynamicFunctions}} **{{ll|Help:Extension:ParserFunctions}} **{{ll|Extension:StringFunctions}} **{{ll|Extension:VariablesExtension}} *{{ll|Extension:Winter}} - "Wiki Interpreter" - Complete programming language which is very similar to native parser functions. * Parser functions for Wikibase (the extensions that enables Wikidata): [[:d:Wikidata:How to use data on Wikimedia projects]] [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:Parser function extensions{{#translation:}}| ]] [[Category:Extension examples{{#translation:}}| ]] 6no13paka5ypktx3mmg3r24tr1dnjx8 5386910 5386907 2022-07-28T19:42:29Z ThisCarthing 17456337 Created page with "Funktion" wikitext text/x-wiki <languages /> {{outdated}} <div lang="en" dir="ltr" class="mw-content-ltr"> A "'''[[Special:MyLanguage/Help:Extension:ParserFunctions|parser function]]'''" is a [[Special:MyLanguage/Help:Templates|template]]-like construct that returns a value based on at least one unnamed parameter, separated from the function name by a colon [''':''']. There may be more parameters, as well; like those of ordinary templates, these additional parameters are each preceded by a "pipe" ['''|''']. In the case of a [[w:Number sign|hash character]] [#] at the start of the function name (which prevents collision with namespaces and interwiki prefixes), this may or may not be considered part of the name. If it is considered part of the name, the syntax is of the form </div> :<nowiki>{{</nowiki>''functionname'': ''argument 1'' | ''argument 2'' | ''argument 3''...}} {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If the caller has '''no arguments''' to provide the parser function, then the form is simply <nowiki>{{</nowiki>''functionname'':<nowiki>}}</nowiki> or, when a hash character applies (as is normally the case) then the form is <nowiki>{{</nowiki>''#functionname'':<nowiki>}}</nowiki>. If the trailing colon is not supplied, then ''functionname'' is not recognized by the parser.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> Arguments cannot directly contain "|" or "}}" except as part of the code of a template call, parser function call, variable, link or image, but they can contain them arbitrarily using a template, e.g., {{tim|!}}, or a parser function. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The code can specify whether the function name is case-sensitive. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The separation of the arguments from each other is with "|", and from the function name is with the first ":" The expansion of each of these pieces is standard, as in [[Special:ExpandTemplates]] (which is a good place to experiment, by the way, if you are learning this stuff) and is beyond the control of the parser function itself. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> However, everything else can be different for each parser function, including: *whether an argument is just a value, or of the form ''parname'' = ''parvalue'', or whatever *if applicable, whether parameter names are case-sensitive </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Syntax prescribed by a parser function extension== </div> <span lang="en" dir="ltr" class="mw-content-ltr">In view of the above, it is advantageous to make an extension such that the syntax to be used in an argument does ''not'' contain the [[w:Vertical_bar|pipe character]] "|" or double braces (more specifically, double closing braces "}}" ).</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, in spite of the fact that a pipe character would otherwise seem a suitable symbol for, e.g., a choice or union (see, e.g., [http://semeb.com/dpldemo/index.php/Manual#category]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Allowing such codes is harmless if an alternative code is also allowed, e.g. "\" for "|".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Table of functions== </div> {|class="sortable wikitable" !Erweiterung!!Funktion!!<span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki version</span> |- |[[m:Special:MyLanguage/Help:Parser function#LC|built-in]]||lc||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#UC|built-in]]||uc||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#LCFIRST|built-in]]||lcfirst||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#UCFIRST|built-in]]||ucfirst||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#URLENCODE|built-in]]||urlencode||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#ANCHORENCODE|built-in]]||anchorencode||1.8+ |- |[[m:Special:MyLanguage/Help:Parser function#URLs etc.|built-in]]||localurl||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#URLs etc.|built-in]]||fullurl||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function##language:|built-in]]||#language||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#|built-in]]||#special||1.9+ |- |[[m:Special:MyLanguage/Help:Parser function#|built-in]]||#tag||1.12+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##expr|usage}})||#expr||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifexpr|usage}})||#ifexpr||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##if|usage}})||#if||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifeq|usage}})||#ifeq||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifexist|usage}})||#ifexist||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##rel2abs|usage}})||#rel2abs||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##titleparts|usage}})||#titleparts||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##switch|usage}})||#switch||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##time|usage}})||#time||1.19+ |- |{{ll|Extension:AddScriptCss|nsp=0}}||#addscript||Archived |- |{{ll|Extension:Arrays|nsp=0}}||#arraydefine||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraydiff||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayindex||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayintersect||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraymerge||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayprint||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayreset||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysearch||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysearcharray||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysize||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayslice||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysort||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraytohash||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayunion||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayunique||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#hashtoarray||1.23+ |- |{{ll|Extension:Attachments|nsp=0}}||#attach||1.31+ |- |{{ll|Extension:Attachments|nsp=0}}||#exturl||1.31+ |- |{{ll|Extension:Babel|nsp=0}}||#babel||1.30+ |- |{{ll|Extension:CSS|nsp=0}}||#css||1.25+ |- |{{ll|Extension:Coordinate|nsp=0}}||#coordinate||1.10+ |- |{{ll|Extension:Counter|nsp=0}}||#+||1.15+ |- |{{ll|Extension:Data|nsp=0}}|||#data||Archived |- |{{ll|Extension:Data|nsp=0}}|||#sort||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#arg||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#ip||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#rand||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#skin||Archived |- |{{ll|Extension:DynamicPageList (third-party)|nsp=0}}|||#dpl |- |{{ll|Extension:ExpandAfter|nsp=0}}||#expandafter ({{ll|Extension:ExpandAfter#Usage Note|deprecated}}, see: #tag)||Archived |- |{{ll|Extension:ForeachFunction|nsp=0}}||#foreachx||Archived |- |{{ll|Extension:ForeachFunction|nsp=0}}||#foreachy||Archived |- |{{ll|Extension:HasCategory|nsp=0}}||#ifhascat||Archived |- |{{ll|Extension:HideNamespace|nsp=0}}||#hidens||1.15+ |- |{{ll|Extension:HideNamespace|nsp=0}}||#unhidens||1.15+ |- |{{ll|Extension:ImageLink|nsp=0}}||#img (old: #imagelink, {{ll|Extension:ImageLink#Usage Note|deprecated}})||Archived |- |{{ll|Extension:Infobox Data Capture|nsp=0}}||#dataentry||Archived |- |{{ll|Extension:Infobox Data Capture|nsp=0}}||#listsplit||Archived |- |{{ll|Extension:InterWikiLinkManager|nsp=0}}||#iwl||Archived |- |{{ll|Extension:KeyValue|nsp=0}}||#keyvalue||1.16+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lst||1.25+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lstx||1.25+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lsth||1.25+ |- |{{ll|Extension:LoopFunctions|nsp=0}}||#for||1.23+ |- |{{ll|Extension:LoopFunctions|nsp=0}}||#foreach||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#while||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#dowhile||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#forargs||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#fornumargs||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#loop||1.25+ |- |{{ll|Extension:Maps|nsp=0}}||#geocode||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#display_map||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#display_point||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#coordinates||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#distance||1.27+ |- |{{ll|Extension:MediaFunctions|nsp=0}}||#media..||1.23+ |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#pagebefore||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#pageafter||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#firstpage||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#lastpage||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pagetitle||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pagesubtitle||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pageexists||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varget||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varcapset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#cshow||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varaset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varaget||Archived |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#expr (extended)||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifexpr (extended)||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#min||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#max||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#if||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifeq||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifexist||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#rel2abs||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#switch||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#time||1.19+ |- |{{ll|Extension:Pipe Escape|nsp=0}}||#!||1.23+ |- |{{ll|Extension:QPoll|nsp=0}}||#qpuserchoice||1.23+ |- |{{ll|Extension:RegexTools|nsp=0}}||#regex||Archived |- |{{ll|Extension:RegexTools|nsp=0}}||#regex_vars||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#pg||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#ps||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#pf||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#gg||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#gs||Archived |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#ask||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#concept||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#info||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#show||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#set||1.27+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#len||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#pos||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#rpos||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#sub||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#pad||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#replace||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#explode||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#urlencode||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#urldecode||1.7+ |- |{{ll|Extension:TreeAndMenu|nsp=0}}|||#tree||1.23+ |- |{{ll|Extension:TreeAndMenu|nsp=0}}|||#menu||1.23+ |- |{{ll|Extension:Variables|nsp=0}}||#vardefine||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#vardefineecho||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#var||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#varexists||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#var_final||1.29+ |- |{{ll|Extension:Wikibase Client|nsp=0}}||#property|| |- |{{ll|Extension:Wikibase Client|nsp=0}}||#statements|| |- |} == Siehe auch == *{{ll|Help:Magic words}} *{{ll|Category:Parser function extensions}} *{{ll|Manual:Parser functions|Writing parser functions}} (software development) *{{ll|Extending wiki markup#Parser_functions}} *[http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/examples/Parser_function.php Sample parser function], from {{ll|Subversion|SVN}} *Parser function extensions with documentation on Meta: **{{ll|Extension:Data}} - requires extra table data_extension in database **{{ll|Extension:DynamicFunctions}} **{{ll|Help:Extension:ParserFunctions}} **{{ll|Extension:StringFunctions}} **{{ll|Extension:VariablesExtension}} *{{ll|Extension:Winter}} - "Wiki Interpreter" - Complete programming language which is very similar to native parser functions. * Parser functions for Wikibase (the extensions that enables Wikidata): [[:d:Wikidata:How to use data on Wikimedia projects]] [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:Parser function extensions{{#translation:}}| ]] [[Category:Extension examples{{#translation:}}| ]] 7n5t4zvcn8g9nwrvsvv4z9a8br5k6jx 5386911 5386910 2022-07-28T19:42:31Z ThisCarthing 17456337 Created page with "MediaWiki-Version" wikitext text/x-wiki <languages /> {{outdated}} <div lang="en" dir="ltr" class="mw-content-ltr"> A "'''[[Special:MyLanguage/Help:Extension:ParserFunctions|parser function]]'''" is a [[Special:MyLanguage/Help:Templates|template]]-like construct that returns a value based on at least one unnamed parameter, separated from the function name by a colon [''':''']. There may be more parameters, as well; like those of ordinary templates, these additional parameters are each preceded by a "pipe" ['''|''']. In the case of a [[w:Number sign|hash character]] [#] at the start of the function name (which prevents collision with namespaces and interwiki prefixes), this may or may not be considered part of the name. If it is considered part of the name, the syntax is of the form </div> :<nowiki>{{</nowiki>''functionname'': ''argument 1'' | ''argument 2'' | ''argument 3''...}} {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If the caller has '''no arguments''' to provide the parser function, then the form is simply <nowiki>{{</nowiki>''functionname'':<nowiki>}}</nowiki> or, when a hash character applies (as is normally the case) then the form is <nowiki>{{</nowiki>''#functionname'':<nowiki>}}</nowiki>. If the trailing colon is not supplied, then ''functionname'' is not recognized by the parser.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> Arguments cannot directly contain "|" or "}}" except as part of the code of a template call, parser function call, variable, link or image, but they can contain them arbitrarily using a template, e.g., {{tim|!}}, or a parser function. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The code can specify whether the function name is case-sensitive. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The separation of the arguments from each other is with "|", and from the function name is with the first ":" The expansion of each of these pieces is standard, as in [[Special:ExpandTemplates]] (which is a good place to experiment, by the way, if you are learning this stuff) and is beyond the control of the parser function itself. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> However, everything else can be different for each parser function, including: *whether an argument is just a value, or of the form ''parname'' = ''parvalue'', or whatever *if applicable, whether parameter names are case-sensitive </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Syntax prescribed by a parser function extension== </div> <span lang="en" dir="ltr" class="mw-content-ltr">In view of the above, it is advantageous to make an extension such that the syntax to be used in an argument does ''not'' contain the [[w:Vertical_bar|pipe character]] "|" or double braces (more specifically, double closing braces "}}" ).</span> <span lang="en" dir="ltr" class="mw-content-ltr">This, in spite of the fact that a pipe character would otherwise seem a suitable symbol for, e.g., a choice or union (see, e.g., [http://semeb.com/dpldemo/index.php/Manual#category]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Allowing such codes is harmless if an alternative code is also allowed, e.g. "\" for "|".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Table of functions== </div> {|class="sortable wikitable" !Erweiterung!!Funktion!!MediaWiki-Version |- |[[m:Special:MyLanguage/Help:Parser function#LC|built-in]]||lc||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#UC|built-in]]||uc||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#LCFIRST|built-in]]||lcfirst||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#UCFIRST|built-in]]||ucfirst||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#URLENCODE|built-in]]||urlencode||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#ANCHORENCODE|built-in]]||anchorencode||1.8+ |- |[[m:Special:MyLanguage/Help:Parser function#URLs etc.|built-in]]||localurl||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#URLs etc.|built-in]]||fullurl||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function##language:|built-in]]||#language||1.7+ |- |[[m:Special:MyLanguage/Help:Parser function#|built-in]]||#special||1.9+ |- |[[m:Special:MyLanguage/Help:Parser function#|built-in]]||#tag||1.12+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##expr|usage}})||#expr||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifexpr|usage}})||#ifexpr||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##if|usage}})||#if||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifeq|usage}})||#ifeq||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##ifexist|usage}})||#ifexist||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##rel2abs|usage}})||#rel2abs||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##titleparts|usage}})||#titleparts||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##switch|usage}})||#switch||1.19+ |- |{{ll|Extension:ParserFunctions|nsp=0}} ({{ll|Help:Extension:ParserFunctions##time|usage}})||#time||1.19+ |- |{{ll|Extension:AddScriptCss|nsp=0}}||#addscript||Archived |- |{{ll|Extension:Arrays|nsp=0}}||#arraydefine||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraydiff||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayindex||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayintersect||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraymerge||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayprint||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayreset||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysearch||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysearcharray||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysize||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayslice||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraysort||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arraytohash||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayunion||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#arrayunique||1.23+ |- |{{ll|Extension:Arrays|nsp=0}}||#hashtoarray||1.23+ |- |{{ll|Extension:Attachments|nsp=0}}||#attach||1.31+ |- |{{ll|Extension:Attachments|nsp=0}}||#exturl||1.31+ |- |{{ll|Extension:Babel|nsp=0}}||#babel||1.30+ |- |{{ll|Extension:CSS|nsp=0}}||#css||1.25+ |- |{{ll|Extension:Coordinate|nsp=0}}||#coordinate||1.10+ |- |{{ll|Extension:Counter|nsp=0}}||#+||1.15+ |- |{{ll|Extension:Data|nsp=0}}|||#data||Archived |- |{{ll|Extension:Data|nsp=0}}|||#sort||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#arg||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#ip||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#rand||Archived |- |{{ll|Extension:DynamicFunctions|nsp=0}}|||#skin||Archived |- |{{ll|Extension:DynamicPageList (third-party)|nsp=0}}|||#dpl |- |{{ll|Extension:ExpandAfter|nsp=0}}||#expandafter ({{ll|Extension:ExpandAfter#Usage Note|deprecated}}, see: #tag)||Archived |- |{{ll|Extension:ForeachFunction|nsp=0}}||#foreachx||Archived |- |{{ll|Extension:ForeachFunction|nsp=0}}||#foreachy||Archived |- |{{ll|Extension:HasCategory|nsp=0}}||#ifhascat||Archived |- |{{ll|Extension:HideNamespace|nsp=0}}||#hidens||1.15+ |- |{{ll|Extension:HideNamespace|nsp=0}}||#unhidens||1.15+ |- |{{ll|Extension:ImageLink|nsp=0}}||#img (old: #imagelink, {{ll|Extension:ImageLink#Usage Note|deprecated}})||Archived |- |{{ll|Extension:Infobox Data Capture|nsp=0}}||#dataentry||Archived |- |{{ll|Extension:Infobox Data Capture|nsp=0}}||#listsplit||Archived |- |{{ll|Extension:InterWikiLinkManager|nsp=0}}||#iwl||Archived |- |{{ll|Extension:KeyValue|nsp=0}}||#keyvalue||1.16+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lst||1.25+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lstx||1.25+ |- |{{ll|Extension:Labeled Section Transclusion|nsp=0}}||#lsth||1.25+ |- |{{ll|Extension:LoopFunctions|nsp=0}}||#for||1.23+ |- |{{ll|Extension:LoopFunctions|nsp=0}}||#foreach||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#while||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#dowhile||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#forargs||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#fornumargs||1.25+ |- |{{ll|Extension:Loops|nsp=0}}||#loop||1.25+ |- |{{ll|Extension:Maps|nsp=0}}||#geocode||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#display_map||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#display_point||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#coordinates||1.27+ |- |{{ll|Extension:Maps|nsp=0}}||#distance||1.27+ |- |{{ll|Extension:MediaFunctions|nsp=0}}||#media..||1.23+ |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#pagebefore||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#pageafter||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#firstpage||Archived |- |{{ll|Extension:PageAfterAndBefore|nsp=0}}||#lastpage||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pagetitle||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pagesubtitle||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#pageexists||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varget||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varcapset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#cshow||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varaset||Archived |- |{{ll|Extension:PageFunctions|nsp=0}}||#varaget||Archived |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#expr (extended)||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifexpr (extended)||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#min||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#max||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#if||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifeq||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#ifexist||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#rel2abs||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#switch||1.19+ |- |{{ll|Extension:ParserFunctions (extended)|nsp=0}}||#time||1.19+ |- |{{ll|Extension:Pipe Escape|nsp=0}}||#!||1.23+ |- |{{ll|Extension:QPoll|nsp=0}}||#qpuserchoice||1.23+ |- |{{ll|Extension:RegexTools|nsp=0}}||#regex||Archived |- |{{ll|Extension:RegexTools|nsp=0}}||#regex_vars||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#pg||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#ps||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#pf||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#gg||Archived |- |{{ll|Extension:SecureProperties|nsp=0}}|||#gs||Archived |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#ask||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#concept||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#info||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#show||1.27+ |- |{{ll|Extension:Semantic MediaWiki|nsp=0}}||#set||1.27+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#len||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#pos||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#rpos||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#sub||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#pad||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#replace||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#explode||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#urlencode||1.7+ |- |{{ll|Extension:StringFunctions|nsp=0}}||#urldecode||1.7+ |- |{{ll|Extension:TreeAndMenu|nsp=0}}|||#tree||1.23+ |- |{{ll|Extension:TreeAndMenu|nsp=0}}|||#menu||1.23+ |- |{{ll|Extension:Variables|nsp=0}}||#vardefine||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#vardefineecho||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#var||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#varexists||1.29+ |- |{{ll|Extension:Variables|nsp=0}}||#var_final||1.29+ |- |{{ll|Extension:Wikibase Client|nsp=0}}||#property|| |- |{{ll|Extension:Wikibase Client|nsp=0}}||#statements|| |- |} == Siehe auch == *{{ll|Help:Magic words}} *{{ll|Category:Parser function extensions}} *{{ll|Manual:Parser functions|Writing parser functions}} (software development) *{{ll|Extending wiki markup#Parser_functions}} *[http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/examples/Parser_function.php Sample parser function], from {{ll|Subversion|SVN}} *Parser function extensions with documentation on Meta: **{{ll|Extension:Data}} - requires extra table data_extension in database **{{ll|Extension:DynamicFunctions}} **{{ll|Help:Extension:ParserFunctions}} **{{ll|Extension:StringFunctions}} **{{ll|Extension:VariablesExtension}} *{{ll|Extension:Winter}} - "Wiki Interpreter" - Complete programming language which is very similar to native parser functions. * Parser functions for Wikibase (the extensions that enables Wikidata): [[:d:Wikidata:How to use data on Wikimedia projects]] [[Category:Customization techniques{{#translation:}}|{{PAGENAME}}]] [[Category:Parser function extensions{{#translation:}}| ]] [[Category:Extension examples{{#translation:}}| ]] st8r7mi7ex6rvj2jg785hw6ggji0l17 Extension:PoolCounter/de 102 1427663 5386891 5305863 2022-07-28T19:37:53Z ThisCarthing 17456337 Created page with "Ein Array von Server-IP-Adressen." wikitext text/x-wiki <languages/> {{Extension |status = beta |type1 = |type2 = |hook1 = |hook2 = |username = |author = Tim Starling, Platonides |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides a MediaWiki client for the [[PoolCounter|pool counter]] daemon</span> |image = |imagesize = |version = |update = |mediawiki = |php = |license = GPL-2.0+ |download = {{WikimediaDownload|PoolCounter}} |needs-updatephp = No |readme = |changelog = |parameters = |tags = |rights = |example = |compatibility = |bugzilla = PoolCounter }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''PoolCounter''' extension provides a MediaWiki client for the [[PoolCounter|pool counter]] daemon. </div> == Installation == {{ExtensionInstall |repo-name=PoolCounter |registration=yes }} == Konfiguration == <div lang="en" dir="ltr" class="mw-content-ltr"> The extension can be configured with the global <code>$wgPoolCountClientConf</code>, which is an associative array with the following keys: </div> ; servers : Ein Array von Server-IP-Adressen. <span lang="en" dir="ltr" class="mw-content-ltr">Adding multiple servers causes locks to be distributed on the client side using a consistent hashing algorithm.</span> ; timeout : <span lang="en" dir="ltr" class="mw-content-ltr">The connect timeout in seconds.</span> == Siehe auch == * [[PoolCounter]] * {{ll|Manual:$wgPoolCounterConf|$wgPoolCounterConf}} {{OnWikimedia}} {{Used by|fandom=1}} 8ukswtww2x3wn3lsnq4bkgkmsx0vbh1 Extension:RegexFunctions/de 102 1427685 5386932 5366310 2022-07-28T19:45:48Z ThisCarthing 17456337 Created page with "Verwendung" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} 62u71izgsqg01evakjds6t6b60aqoyx 5386934 5386932 2022-07-28T19:45:54Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} pfwurmnjz0ka7zqlqf04u5fyzbzihdz 5386936 5386934 2022-07-28T19:45:58Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} dm4l8i3fsyeumf2l3i34vwumu2k49hm 5386938 5386936 2022-07-28T19:46:03Z ThisCarthing 17456337 Created page with "optional" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} 2fa12ieirkmq2bu0a7akp5wtu57bgd6 5386940 5386938 2022-07-28T19:46:08Z ThisCarthing 17456337 Created page with "optional" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} g5ktq3tt2y66uux4xhf12a0u9qm4rid 5386942 5386940 2022-07-28T19:46:13Z ThisCarthing 17456337 Created page with "notwendig" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} eloh2yvvd1r9vl2izx51jov6errm4g3 5386944 5386942 2022-07-28T19:46:19Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (<span lang="en" dir="ltr" class="mw-content-ltr">optional</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} 3b2ceekhlc8khl1f4wy8ffivha39qw7 5386946 5386944 2022-07-28T19:46:23Z ThisCarthing 17456337 Created page with "optional" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} rj1f21b7wajwh5ionfb4robb2jb5jul 5386948 5386946 2022-07-28T19:46:31Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} 9v2xilwz97n3t5p5oajjlmhqsi2v2i9 5386950 5386948 2022-07-28T19:46:35Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (<span lang="en" dir="ltr" class="mw-content-ltr">required</span>) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} qhe0qrfaebzlqpb4mrth7fo1nkk3xzo 5386952 5386950 2022-07-28T19:46:38Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = parser function |username = Skizzerz |author = Ryan Schmidt |description = <span lang="en" dir="ltr" class="mw-content-ltr">Regular expression based parser functions</span> |version = 2.0.0 |update = 2020-03-18 |mediawiki = 1.31+ |license = PD |download = {{WikimediaDownload|RegexFunctions}} |readme = [[#Usage|Verwendung]] }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RegexFunctions''' extension provides regular expression based parser functions. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> As of now, this extension defines three parser functions: <code>rmatch</code>, <code>rsplit</code>, and <code>rreplace</code> : </div> ; <code><nowiki>#rmatch:</nowiki></code> : <code><nowiki>{{#rmatch:string|pattern|then|else}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function uses for the matching.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''then''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> : '''else''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">What to return if the match was not successful.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty string.</span> ; <code><nowiki>#rsplit:</nowiki></code> : <code><nowiki>{{#rsplit:string|pattern|piece}}</nowiki></code> : '''string''' (notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will split.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text. No text is captured.</span> : '''piece''' (optional) - <span lang="en" dir="ltr" class="mw-content-ltr">The piece to return. Defaults to 0 (the first piece).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Negative numbers return pieces starting from the end.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, -1 is the last piece.</span> ; <code><nowiki>#rreplace:</nowiki></code> : <code><nowiki>{{#rreplace:string|pattern|replacement}}</nowiki></code> : '''string''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text the function will replace.</span> : '''pattern''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The regular expression to use on the text.</span> : '''replacement''' (Notwendig) - <span lang="en" dir="ltr" class="mw-content-ltr">The text to replace the matched text with.</span> <span lang="en" dir="ltr" class="mw-content-ltr">$# and \# contain the captured text.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Use ${#}# if you want a group followed by another number.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Except for the ''string'' parameter, every parameter can be specified either by name or position.</span> Zum Beispiel, <code><nowiki>{{#rmatch:some string|pattern=^.+$|then=success|else=failure}}</nowiki></code>. <span lang="en" dir="ltr" class="mw-content-ltr">If your wiki's content language is not English, both the English names as well as a translated name may be usable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In addition, every function supports the following named parameters which allow you to modify the behavior of the regex:</span> * '''multiline''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>^</code> and <code>$</code> match the start and end of each line, rather than the start and end of the entire string.</span> * '''caseless''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the pattern is case-insensitive.</span> * '''ungreedy''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>*</code> and <code>+</code> do not match greedily whereas <code>*?</code> and <code>+?</code> match greedily.</span> * '''extended''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, the regex can contain spaces and inline comments.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See the PHP documentation in the pattern help section for more information.</span> * ''' dotall''' - <span lang="en" dir="ltr" class="mw-content-ltr">If non-empty, <code>.</code> matches all characters, including newlines. Normally it does not match newlines.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, <code><nowiki>{{#rmatch:XxXxX|x+|$0|caseless=1}}</nowiki></code> would result in the output <code>XxXxX</code> because <code>x+</code> matches both uppercase and lowercase X's when the caseless modifier is set. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Pattern help === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For help on constructing the syntax, please read [https://php.net/regexp.reference] for general help and [https://php.net/reference.pcre.pattern.modifiers] for an overview of the modifiers. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Delimiters are not required on the pattern in general and should be omitted for readability where possible, but are required if you would like to specify the single-letter modifiers after the pattern.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In this event, the delimiters '''must''' be forward slashes (no other delimiter type is supported).</span> == Installation == {{ExtensionInstall |registration=required }} == Siehe auch == * {{ll|Extension:ReplaceSet|ReplaceSet}} - <span lang="en" dir="ltr" class="mw-content-ltr">an excellent substitute for using nested #replace commands when you need to perform a sequence of replaces on a single text string.</span> * {{ll|Extension:Regex Fun|Regex Fun}} - <span lang="en" dir="ltr" class="mw-content-ltr">just another regex extension with more functionality but without any customization variables for limitations.</span> * {{ll|Extension:RegexParserFunctions}} md84xgarg4xun21djjsdwe0dt38ar4a Extension:UserExport/de 102 1427746 5387059 5127659 2022-07-28T20:07:32Z ThisCarthing 17456337 Created page with "Benutzerrecht" wikitext text/x-wiki <languages/> {{Extension |name = UserExport |status = stable |type1 = special |type2 = data extraction |author = Rodrigo Sampaio Primo |username = RodrigoSampaioPrimo |maintainer = [[User:MarkAHershberger|Mark A. Hershberger]] |description = Allows to export user name and email to a CSV file |version = 2.1.1 |update = 2020-04-15 |mediawiki = 1.34+ |php = 7.2+ |composer = mediawiki/user-export |license = GPL-2.0-or-later |download = {{WikimediaDownload|UserExport}} |needs-updatephp = No |readme = [https://phabricator.wikimedia.org/diffusion/EUSE/repository/master/ README] |changelog = [https://phabricator.wikimedia.org/diffusion/EUSE/browse/master/CHANGELOG.md CHANGELOG] |example = |rights = userexport |parameters = |CheckUsageNameOverride=User Export }} The '''UserExport''' extension allows to export the user name and email of all MediaWiki users to a CSV-file via a new special page called "Special:UserExport". == Verwendung == This extension creates a new restricted special page called "Special:UserExport" with the title '''User Export''' which has only a button to trigger the generation of the CSV file. Click on this button and download the file. The data gets exported in "UTF-8". == Installation == {{ExtensionInstall |download-link=[[Special:ExtensionDistributor/UserExport|Download]] |custom-steps=* [[#Configuration|Configure as required.]] |registration=required |no-registration-version=1.31 }} {{anchor|Configuration}} == Konfiguration == ; Benutzerrecht <span lang="en" dir="ltr" class="mw-content-ltr">By default the "userexport" permission provided by this extension is assigned to the "bureaucrat" user group.</span> In case you would like to change this add the following lines to your "LocalSettings.php" file after the inclusion of the extension as described in the "Installation" section above: <syntaxhighlight lang=php> $wgGroupPermissions['bureaucrat']['userexport'] = false; // remove from "bureaucrat" group $wgGroupPermissions['userexport']['userexport'] = true; // add to dedicated "userexport" group </syntaxhighlight> == Siehe auch == * {{ll|Extension:ImportUsers}} – <span lang="en" dir="ltr" class="mw-content-ltr">Extension that allows to import users in bulk from a CSV file</span> ltx5zvuio57e7zswsa7j9g5vdfk0kud Extension:UserFunctions/de 102 1427748 5387057 5371002 2022-07-28T20:07:17Z ThisCarthing 17456337 Created page with "Algorithmus" wikitext text/x-wiki <languages /> {{Extension |status = stable |type = parser function |author = <nowiki/> * [[User:Algorithm|Algorithm]], * [[User:Toniher|Toniher]], * [[User:Universal Omega|Universal Omega]], * and others |username = |image = |version = 2.8.1 |update = 2022-07-20 |mediawiki = 1.35+ |download = {{WikimediaDownload}} |needs-updatephp = No |composer = mediawiki/user-functions |readme = |changelog = |license = GPL-2.0-or-later |php = 7.2+ |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides a set of parser functions that trigger on the current user</span> |parameters = <nowiki/> * $wgUFEnabledPersonalDataFunctions * $wgUFAllowedNamespaces * $wgUFEnableSpecialContexts |rights = |example = [https://sandbox.semantic-mediawiki.org/wiki/UserFunctions sandbox.semantic-mediawiki.org] |hook1 = ParserFirstCallInit |hook2 = ParserClearState }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''UserFunctions''' extension provides a set of dynamic parser functions that trigger on the current user. </div> == Verwendung == {{Note |1=<span lang="en" dir="ltr" class="mw-content-ltr">By default functions are only enabled in <code>NS_MEDIAWIKI</code> namespace, for enabling them in other namespaces, see the [[#Allowing namespaces|examples below]].</span> |2=reminder }} {{Note |1=<span lang="en" dir="ltr" class="mw-content-ltr">If you are using these functions within you wiki's sidebar, you cannot set <code class="mw-highlight">{{ll|Manual:$wgEnableSidebarCache|$wgEnableSidebarCache}} = {{#tag:span|true|class=k}};</code>.</span> }} <span lang="en" dir="ltr" class="mw-content-ltr">The following four functions are always available for use:</span> * <code>{{#ifanon:then|else}}</code> : Testet, ob der aktuelle Benutzer anonym ist. * <code>{{#ifblocked:then|else}}</code> : Testet, ob der aktuelle Benutzer gesperrt ist. * <code>{{#ifsysop:then|else}}</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Tests whether the current user is a sysop.</span> * <code>{{#ifingroup:group|then|else}}</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Tests whether the current user is a member of the group "group".</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can check for multiple groups as well:</span> : <code>{{#ifingroup:group1, group2, group3|then|else}}</code> <div lang="en" dir="ltr" class="mw-content-ltr"> The following five personal data functions are disabled by default (see [[#Installation|#Installation]] for how to enable them): </div> {{Note |1=<span lang="en" dir="ltr" class="mw-content-ltr">The functions described below are called personal data functions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They can be used to leak some of your user's personal data like their email address and real name.</span> <br/> <span lang="en" dir="ltr" class="mw-content-ltr">'''If unsure, do not activate personal data functions.'''</span> |2=gotcha }} * <code>{{#realname:alt}}</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Returns the current user's real name.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the user is not logged in, this function returns the given alternate text, or the user IP if no alternate is provided.</span> * <code>{{#username:alt}}</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Returns the current username.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the user is not logged in, this function returns the given alternate text, or the user IP if no alternate is provided.</span> * <code>{{#useremail:alt}}</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Returns the current user's email address.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the user is not logged in, this function returns the given alternate text, or the user IP if no alternate is provided.</span> * <code>{{#nickname:alt}}</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Returns the current user's nickname.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the user has no nickname, returns the username.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the user is not logged in, this function returns the given alternate text, or the user IP if no alternate is provided.</span> * <code>{{#ip:}}</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Returns the current user's IP address.</span> {{anchor|Installation}} == Installation == {{ExtensionInstall |repo-name=UserFunctions |registration=yes |custom-steps= * <span lang="en" dir="ltr" class="mw-content-ltr">If you want to use any of the following functions: <code>#realname</code>, <code>#username</code>, <code>#useremail</code>, <code>#nickname</code> or <code>#ip</code>, add the following just ''after'' that line:</span> <syntaxhighlight lang="php">$wgUFEnabledPersonalDataFunctions = [ 'ip', 'nickname', 'realname', 'useremail', 'username', ];</syntaxhighlight> * <span lang="en" dir="ltr" class="mw-content-ltr">If you want to enable functions in other namespaces apart from <code>NS_MEDIAWIKI</code> (default), follow the model of some of the [[#Allowing namespaces|examples below]].</span> |no-registration-version=1.35 }} {{anchor|Allowing namespaces}} == Namensräume erlauben == <span lang="en" dir="ltr" class="mw-content-ltr">By default, user functions only work in <code>NS_MEDIAWIKI</code> namespace.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Below there are some examples of allowing or disallowing the functions to work in other namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The syntax is based on the one [[Special:MyLanguage/Manual:$wgNamespacesWithSubpages|used with subpages]].</span> <syntaxhighlight lang="php"> // Enable user functions additionally in namespace "Main" // Adds values to the existing array $wgUFAllowedNamespaces[NS_MAIN] = true; </syntaxhighlight> <syntaxhighlight lang="php"> // Enable user functions in namespaces "Main" and "User", but not in namespace "MediaWiki" // Replaces values in the existing array $wgUFAllowedNamespaces = [ NS_MAIN => true, NS_USER => true ]; </syntaxhighlight> <syntaxhighlight lang="php"> // Enable user functions in namespaces with the indexes from 0 to 200 // Replaces values in the existing array $wgUFAllowedNamespaces = array_fill( 0, 200, true ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> More info on [[Special:MyLanguage/Manual:Namespace|namespace numbering]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In other contexts (recognized as NS -1, but not always a [[Special:MyLanguage/Manual:Special_pages|Special Page]]), such as in [[Special:MyLanguage/Extension:Page Forms|Page Forms]] pages, check you have the following parameter enabled: </div> <syntaxhighlight lang="php"> $wgUFEnableSpecialContexts = true; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The parameter above is enabled by default. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you experience any problem with bots or maintenance scripts, turn it to false and report it to this [[Extension_talk:{{PAGENAME}}|talk page]]. </div> == Versionsgeschichte == <div lang="en" dir="ltr" class="mw-content-ltr"> Authors: Algorithm and others </div> * Version 2.8.1 (2022-07-20) Allow disabling/enabling specific personal data functions - Universal Omega ** '''Note:''' Prior to this, the <syntaxhighlight lang="php" inline>$wgUFEnabledPersonalDataFunctions</syntaxhighlight> configuration variable was named <syntaxhighlight lang="php" inline>$wgUFEnablePersonalDataFunctions</syntaxhighlight>, and setting it to true would enable all personal data functions, and was only able to enable/disable all of them or none of them. * Version 2.8.0 (2021-04-18) <span lang="en" dir="ltr" class="mw-content-ltr">Convert to ExtensionRegistry and other code cleanups - Universal Omega</span> * Version 2.7.0 (2017-07-26) <span lang="en" dir="ltr" class="mw-content-ltr">Removed PHP i18n shim</span> - [[user:Kghbln|Kghbln]] * Version 2.6.1 (2014-11-15) <span lang="en" dir="ltr" class="mw-content-ltr">Provided syntax changes</span> - [[user:Kghbln|Kghbln]], [[user:Umherirrender|Umherirrender]] * Version 2.6.0 (2014-09-18) Composer-kompatible Erweiterung - [[user:Toniher|Toniher]] * Version 2.5.0 (2014-04-01) <span lang="en" dir="ltr" class="mw-content-ltr">Migrated to JSON i18n</span> - [[user:Siebrand|Siebrand]] * Version 2.4.3 (2014-03-16) <span lang="en" dir="ltr" class="mw-content-ltr">Accumulated fixes and code cleaning</span> - [[user:Chad|Chad]] [[user:Uckelman|Uckelman]] * Version 2.4.2 (2013-04-08) <span lang="en" dir="ltr" class="mw-content-ltr">Some code cleaning</span> - [[user:Reedy|Reedy]] * Version 2.4.1 (2012-07-17) <span lang="en" dir="ltr" class="mw-content-ltr">Fixed problems with Sidebar (report [[user:Kghbln|Kghbln]]). Cleared PHP warnings in functions</span> - [[user:Toniher|Toniher]] * Version 2.4 (2012-06-02) <span lang="en" dir="ltr" class="mw-content-ltr">Cleaned using current ParserFunctions models. Fix when editing Semantic Forms</span> - [[user:Toniher|Toniher]] * Version 2.3 (2012-05-27) <span lang="en" dir="ltr" class="mw-content-ltr">fixed problems when using scripts and allowed multiple groups to be checked against in ifingroup.</span> - [[user:Toniher|Toniher]] * Version 2.2 (2012-01-03) <span lang="en" dir="ltr" class="mw-content-ltr">added $wgUFAllowedNamespaces parameter. Users need to define in which allowed NS functions will work.</span> - [[user:Toniher|Toniher]] * Version 2.1 (2011-12-21) <span lang="en" dir="ltr" class="mw-content-ltr">added $wgUFEnablePersonalDataFunctions parameter. Migrated $wgUser to ParserOptions equivalent</span> - [[user:Toniher|Toniher]] * Version 2.0 (2011-12-13) <span lang="en" dir="ltr" class="mw-content-ltr">added i18n and compatibility with other parser function extensions</span> - [[user:Toniher|Toniher]] * Version 1.5 (2011-10-30) <span lang="en" dir="ltr" class="mw-content-ltr">added ip</span> - [[user:Kghbln|Kghbln]] * Version 1.4 (2011-09-27) <span lang="en" dir="ltr" class="mw-content-ltr">added realname</span> - [[user:Kghbln|Kghbln]] * Version 1.3 (2010-02-13) <span lang="en" dir="ltr" class="mw-content-ltr">added useremail</span> - [[user:Wikinaut|Wikinaut]] * Version 1.2 (2008-07-25) <span lang="en" dir="ltr" class="mw-content-ltr">added ifingroup</span> - [[user:Louperivois|Louperivois]] * Version 1.1 (2008-06-27) <span lang="en" dir="ltr" class="mw-content-ltr">added nickname</span> - [[user:Lexw|Lexw]] * Version 1.0 (2006-05-21) Algorithmus == Siehe auch == * {{ll|Extension:UserMagic}} * {{ll|Extension:MyVariables}} {{Used by|bluespice=1|miraheze=1|prowiki=1|semantic core=1}} [[Category:Menu extensions{{#translation:}}]] [[Category:Real name display extensions{{#translation:}}]] 4fu7hhto6nv1su3cu1hsgh5j56q59y2 Extension:UserManager/de 102 1427752 5387061 5364082 2022-07-28T20:08:25Z ThisCarthing 17456337 Created page with "== Verwendung / Funktionen ==" wikitext text/x-wiki <languages/> {{BlueSpiceExtensionInfobox |compatibility = |download = |phabricator = |name = UserManager |author = |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides a visual interface to administrate users</span> |image = BlueSpice Mediawiki Extension BlueSpiceUserManager.png |imagesize = 300 |example = |repo = BlueSpiceUserManager |newhook1 = BSUserManagerAfterAddUser |newhook2 = BSUserManagerAfterEditUser |newhook3 = BSUserManagerAfterDeleteUser |newhook4 = BSUserManagerAfterSetGroups }} '''UserManager''' provides a visual interface for user administration. It allows to create and edit user accounts and to assign users to groups. == Verwendung / Funktionen == <div lang="en" dir="ltr" class="mw-content-ltr"> The extension enables the following actions: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">create a new user</span> * <span lang="en" dir="ltr" class="mw-content-ltr">assign a user to a group</span> * <span lang="en" dir="ltr" class="mw-content-ltr">change user data</span> * <span lang="en" dir="ltr" class="mw-content-ltr">change the password</span> * <span lang="en" dir="ltr" class="mw-content-ltr">delete users (multiple selections possible)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">sort, filter, and export the user list</span> == Externe Links == * Read more about the usage of UserManager in the [https://en.wiki.bluespice.com/wiki/Reference:BlueSpiceUserManager helpdesk]. == Siehe auch == * {{ll|Extension:GroupManager}} {{Template:BlueSpiceExtensionFooter|UserManager |download-with = BlueSpice free |support-links = [http://hallowelt.com Hallo Welt! GmbH] }} mel1u2bw09mju51mrwzyw0twwc1cs3f Extension:VoteNY/de 102 1427764 5386960 5370465 2022-07-28T19:48:08Z ThisCarthing 17456337 Created page with "=== Spezialseite ===" wikitext text/x-wiki <languages /> {{Extension |status = stable |image = VoteNY.png |type1 = parser |type2 = hook |type3 = tag |description = <span lang="en" dir="ltr" class="mw-content-ltr">JavaScript-based voting with the {{tag|vote|open}} tag</span> |author = * Aaron Wright * David Pean * {{u|Jack Phoenix}} |compatibility policy = master |version = 3.2 |update = 2021-11-24 |mediawiki = {{MW lts branch number}}+ |table1 = Vote |download = {{WikimediaDownload}} |readme = |changelog = |example = |bugzilla = VoteNY |phabricator = VoteNY |CheckUsageNameOverride = Vote }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''VoteNY''' a.k.a '''Vote''' extension adds the {{tag|vote|open}} parser hook tag to allow voting on articles where the tag is present.</span> == Installation == {{ExtensionInstall |repo-name=VoteNY |db-update=Yes |registration=required }} == Konfiguration == <span lang="en" dir="ltr" class="mw-content-ltr">This extension adds one new user right, <code>voteny</code>, which is required in order to vote.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, anonymous users do not have this right and thus they cannot vote but registered users can.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To allow anonymous users to vote, add the following to your LocalSettings.php:</span> <syntaxhighlight lang=php> $wgGroupPermissions['*']['voteny'] = true; </syntaxhighlight> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Tags=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> {{tag|vote|single}} outputs a green square voting box. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> <syntaxhighlight lang=html inline><vote type=1 /></syntaxhighlight> outputs five voting stars. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Magic words=== </div> * <code><nowiki>{{NUMBEROFVOTES}}</nowiki></code>: <span lang="en" dir="ltr" class="mw-content-ltr">Returns the entire number of votes on the wiki.</span> * <code><nowiki>{{NUMBEROFVOTESPAGE}}</nowiki></code>: <span lang="en" dir="ltr" class="mw-content-ltr">Returns the number of votes on the current page.</span> * <code><nowiki>{{NUMBEROFVOTESPAGE:<page>}}</nowiki></code>: <span lang="en" dir="ltr" class="mw-content-ltr">Returns the number of votes on the given page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The magic word <code><nowiki>{{NUMBEROFVOTES}}</nowiki></code> can be used to display the number of votes in the database; this number is cached (in {{ll|Memcached|memcached}}) for 24 hours, so it's not totally up-to-date. </div> === Spezialseite === <span lang="en" dir="ltr" class="mw-content-ltr">The special page ''Special:TopRatings'' displays the highest rated pages on the wiki.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It supports filtering by category and namespace and its output can be embedded on wiki pages, so <code><nowiki>{{Special:TopRatings/Adventure Games/0/10}}</nowiki></code> will show 10 ratings where the pages are in the "Adventure Games" category and the pages are in the main (0) namespace.</span> == Internationalisierung == {| class="wikitable" ! Nachricht !! {{#language:en|{{PAGELANGUAGE}}}} !! Beschreibung |- | voteny-link || Vote || |- | voteny-unvote-link || unvote || Displayed to the user after their vote has been successfully added. |- | voteny-community-score || community score: $1 || "community score" is the average score of the page in question |- | voteny-ratings || <nowiki>{{PLURAL:$1|one rating|$1 ratings}}</nowiki> || $1 is the number of ratings, if said number is greater than 1. |- | voteny-remove || remove || |- | voteny-gave-this || you gave this a $1 || $1 is the score you gave to the page, for example 5 or 3.50. |- | voteny-votes || <nowiki>{{PLURAL:$1|one vote|$1 votes}}</nowiki> || $1 is the number of votes. |- | topratings || Top Ratings || Title of ''Special:TopRatings'', will be shown on the listing of special pages at [[Special:SpecialPages]] and on ''Special:TopRating'' itself. |- | topratings-no-pages || No top rated pages. || Shown on Special:TopRatings if there are absolutely no pages that have been rated yet (as is the case usually right after installing the extension). |- | right-voteny || Vote pages || Displayed on [[Special:ListGroupRights]]. |} == Siehe auch == * {{Ll|Extension:RatePage|RatePage}} - <span lang="en" dir="ltr" class="mw-content-ltr">Allows for voting and voting contests</span> {{Social tools}} {{Used by|canasta=1}} [[Category:Poll extensions{{#translation:}}]] [[Category:Rating extensions{{#translation:}}]] j5bqgr1ti3476cnrnq12vfp2iyzzr5j Extension:WikiHiero/de 102 1427784 5387076 4939189 2022-07-28T20:13:56Z ThisCarthing 17456337 Created page with "WikiHieros Syntax" wikitext text/x-wiki <languages/> {{Extension |status = stable |type = tag |author = [[:fr:Utilisateur:Aoineko|Guillaume Blanchard]], [[User:MaxSem|Max Semenik]] and others |image = Wikihiero.png |imagesize = 350px |update = |version = <span lang="en" dir="ltr" class="mw-content-ltr">continuous updates</span> |mediawiki = |license = GPL-2.0-or-later |download = {{WikimediaDownload|wikihiero}} |needs-updatephp = No |readme = [https://phabricator.wikimedia.org/diffusion/EHIE/browse/master/README README] |changelog = |compatibility policy = rel |description = <span lang="en" dir="ltr" class="mw-content-ltr">Enables the use of hieroglyphs with additional syntaxes</span> |parameters = |rights = |example = <hiero>A2 B4 C6 D8</hiero> |hook1 = ParserFirstCallInit |tags = {{tag|hiero|open}} |phabricator = WikiHiero |pagedrive1 = true }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''WikiHiero''' extension allows the addition of Ancient Egyptian [[w:hieroglyph|hieroglyph]]s from text written in accordance with the ''Hieroglyph coding manual'' syntax. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> See the ''Hieroglyph coding manual'' for details. </div> In Kürze: :<code>-</code> <span lang="en" dir="ltr" class="mw-content-ltr">separator</span> :<code>:</code> <span lang="en" dir="ltr" class="mw-content-ltr">subdivision</span> :<code>*</code> <span lang="en" dir="ltr" class="mw-content-ltr">juxtaposition</span> :<code>!</code> Zeilenende <div lang="en" dir="ltr" class="mw-content-ltr"> Each hieroglyph is given a unique code: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *A letter [A-Z + Aa] that represents the hieroglyph category (human, god, bird, etc.) </div> <div lang="en" dir="ltr" class="mw-content-ltr"> *A number that represents the rank in this category [1-...] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This unique code is an extension of Gardiner's list of hieroglyphs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The ''Hieroglyph coding manual'' allows the use of the more common phonemes as well as unique code. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For details, see {{ll|Extension:WikiHiero/Syntax|WikiHiero's syntax}}. </div> == Installation == {{ExtensionInstall |wikihiero |registration=1 |no-registration-version=1.26 }} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Testing== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Test with some example wiki text. </div> Der folgende Code: <code><nowiki><hiero>A1</hiero></nowiki></code> <div lang="en" dir="ltr" class="mw-content-ltr"> should produce the following output: </div> <hiero>A1</hiero> ==Lizenz== <div lang="en" dir="ltr" class="mw-content-ltr"> * Sources are copyrighted [[:fr:Utilisateur:Aoineko|G. Blanchard]] and released under [[w:GPL|GNU Public License]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Hieroglyph pictures are copyrighted S. Rosmorduc, G. Watson and J. Hirst and released under [[w:GFDL|GNU Free Documentation License]]. </div> == Siehe auch == *[https://www.catchpenny.org/codage/ <span lang="en" dir="ltr" class="mw-content-ltr">Manuel de Codage</span>] *[[m:Egyptopedia|Egyptopedia]] - <span lang="en" dir="ltr" class="mw-content-ltr">the international Egyptology project</span> *{{ll|Extension:WikiHiero/Syntax|2=WikiHieros Syntax}} *{{ll|Extension:WikiHiero/Test text|2=<span lang="en" dir="ltr" class="mw-content-ltr">WikiHiero test text</span>}} {{OnWikimedia}} [[Category:Extensions with VisualEditor support{{#translation:}}]] 25yyvg7kh8eft44wgadl7zvfl8s3ffi Manual:$wgUpdateRowsPerJob/de 100 1429046 5387266 5374373 2022-07-28T21:51:27Z Piet2609 17478837 Created page with "Zu aktualisierende Reihenanzahl pro Job" wikitext text/x-wiki <languages /> {{SettingSummary |name=UpdateRowsPerJob |version_min=1.7.0 |rev_introduced=14809 |section=Jobs |range=(Ganzzahl) |default=300 |summary=Zu aktualisierende Reihenanzahl pro Job }} == Details == <div lang="en" dir="ltr" class="mw-content-ltr"> Number of rows to update per job. </div> == Siehe auch == * {{ll|Manual:Job queue}} * {{ll|Manual:$wgJobRunRate}} fycb82k72tbh2b1khc3ihrjijj9xbnu 5387268 5387266 2022-07-28T21:51:41Z Piet2609 17478837 Created page with "Zu aktualisierende Reihenanzahl pro Job." wikitext text/x-wiki <languages /> {{SettingSummary |name=UpdateRowsPerJob |version_min=1.7.0 |rev_introduced=14809 |section=Jobs |range=(Ganzzahl) |default=300 |summary=Zu aktualisierende Reihenanzahl pro Job }} == Details == Zu aktualisierende Reihenanzahl pro Job. == Siehe auch == * {{ll|Manual:Job queue}} * {{ll|Manual:$wgJobRunRate}} d9g7q84ihdy41hhvm5x4xeqcctwwvf2 Manual:Pywikibot/category.py/de 100 1429477 5387843 5299625 2022-07-29T10:19:54Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Ptag|Pywikibot-category.py}} {{Git/pywikibot}} {{Pywikibot|scripts}} == Syntax == Die Syntax ist: python pwb.py category action [-option] wobei action eine der folgenden sein kann. {| class="wikitable |- | <code>add</code> || <span lang="en" dir="ltr" class="mw-content-ltr">mass-add a category to a list of pages</span> |- | <code>remove</code> || <span lang="en" dir="ltr" class="mw-content-ltr">remove category tag from all pages in a category</span> |- | <code>move</code> || <span lang="en" dir="ltr" class="mw-content-ltr">move all pages in a category to another category</span> |- | <code>tidy</code> || <span lang="en" dir="ltr" class="mw-content-ltr">tidy up a category by moving its articles into subcategories</span> |- | <code>clean</code> || assisted [https://en.wikipedia.org/wiki/Wikipedia:Categorization#Diffusing_large_categories diffusing of large categories] |- | <code>tree</code> || <span lang="en" dir="ltr" class="mw-content-ltr">show a tree of subcategories of a given category</span> |- | <code>listify</code> || <span lang="en" dir="ltr" class="mw-content-ltr">make a list of all of the articles that are in a category</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> and option can be one of the following. </div> === Optionen für die <code>add</code>-Aktion === {| class="wikitable" |- | <code>-person</code> || <span lang="en" dir="ltr" class="mw-content-ltr">sort persons by their last name</span> |- | <code>-create</code> || <span lang="en" dir="ltr" class="mw-content-ltr">If a page doesn't exist, do not skip it, create it instead</span> |- | <code>-redirect</code> || <span lang="en" dir="ltr" class="mw-content-ltr">Follow redirects</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> For this action, [[#page_generators|page generator options]] are supported. </div> === Optionen für die <code>listify</code>-Aktion === * -overwrite - <span lang="en" dir="ltr" class="mw-content-ltr">This overwrites the current page with the list even if something is already there.</span> * -showimages - <span lang="en" dir="ltr" class="mw-content-ltr">This displays images rather than linking them in the list.</span> * -talkpages - <span lang="en" dir="ltr" class="mw-content-ltr">This outputs the links to talk pages of the pages to be listified in addition to the pages themselves.</span> === Optionen für die <code>remove</code>-Aktion === * -nodelsum - <span lang="en" dir="ltr" class="mw-content-ltr">This specifies not to use the custom edit summary as the deletion reason.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instead, it uses the default deletion reason for the language, which is "Category was disbanded" in English.</span> === Optionen für die <code>move</code>-Aktion === {| class="wikitable" | -hist || <span lang="en" dir="ltr" class="mw-content-ltr">Creates a nice wikitable on the talk page of target category that contains detailed page history of the source category.</span> |- | -nodelete || <span lang="en" dir="ltr" class="mw-content-ltr">Don't delete the old category after move</span> |- | -nowb || <span lang="en" dir="ltr" class="mw-content-ltr">Don't update the wikibase repository</span> |- | -allowsplit || <span lang="en" dir="ltr" class="mw-content-ltr">If that option is not set, it only moves the talk and main page together.</span> |- | -mvtogether || <span lang="en" dir="ltr" class="mw-content-ltr">Only move the pages/subcategories of a category, if the target page (and talk page, if -allowsplit is not set) doesn't exist.</span> |- | -keepsortkey | <span lang="en" dir="ltr" class="mw-content-ltr">Use sortKey of the old category also for the new category.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If not specified, sortKey is removed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">An alternative method to keep sortKey is to use -inplace option.</span> |} === Optionen für die <code>tidy</code>-Aktion === {| class="wikitable" |- | <code>-namespaces</code><br/><code>-namespace</code><br/><code>-ns</code> | <span lang="en" dir="ltr" class="mw-content-ltr">Filter the articles in the specified namespaces.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Separate multiple namespace numbers or names with commas.</span> Beispiele: -ns:0,2,4 -ns:Help,MediaWiki |} === <span lang="en" dir="ltr" class="mw-content-ltr">Options for several actions</span> === {| class="wikitable" | -rebuild || <span lang="en" dir="ltr" class="mw-content-ltr">reset the database</span> |- | -from: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move from (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to remove from in the remove option</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the category to make a list of in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -to: | <span lang="en" dir="ltr" class="mw-content-ltr">The category to move to (for the move option)</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, the name of the list to make in the listify option</span> <span lang="en" dir="ltr" class="mw-content-ltr">See note below table.</span> |- | -batch || <span lang="en" dir="ltr" class="mw-content-ltr">Don't prompt to delete emptied categories (do it automatically).</span> |- | -summary: || <span lang="en" dir="ltr" class="mw-content-ltr">Pick a custom edit summary for the bot.</span> |- | -inplace || <span lang="en" dir="ltr" class="mw-content-ltr">Use this flag to change categories in place rather than rearranging them.</span> |- | -recurse || <span lang="en" dir="ltr" class="mw-content-ltr">Recurse through all subcategories of categories.</span> |- | -pagesonly || <span lang="en" dir="ltr" class="mw-content-ltr">While removing pages from a category, keep the subpage links and do not remove them</span> |- | -match || <span lang="en" dir="ltr" class="mw-content-ltr">Only work on pages whose titles match the given regex (for move and remove actions).</span> |- | -depth: || <span lang="en" dir="ltr" class="mw-content-ltr">The max depth limit beyond which no subcategories will be listed.</span> |} {{note|1= Für die Optionen ''-from'' und ''-to'': <span lang="en" dir="ltr" class="mw-content-ltr">If the category names have spaces in them you may need to use a special syntax in your shell so that the names aren't treated as separate parameters.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For instance, in BASH, use single quotes, e.g. <code>-from:'Polar bears'</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For categories containing a colon you must explicitly prepend the namespace prefix <code>category:</code> or its localized equivalent.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For actions ''tidy'' and ''tree'', the bot will store the category structure locally in <code>category.dump</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This saves time and server load, but if it uses these data later, they may be outdated; use the <code>-rebuild</code> parameter in this case.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, to create a new category from a list of persons, type:</span> python pwb.py category add -person <div lang="en" dir="ltr" class="mw-content-ltr"> and follow the on-screen instructions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or to do it all from the command-line, use the following syntax: </div> python pwb.py category move -from:US -to:"United States" <div lang="en" dir="ltr" class="mw-content-ltr"> This will move all pages in the category US to the category United States. </div> }} {{anchor|page_generators}} {{Manual:Pywikibot/Page Generators}} {{Manual:Pywikibot/Global Options}} == Siehe auch == * [[:fr:Aide:Pywikipedia/category.py]] * [https://github.com/makelinux/wikigraphviz wikigraphviz] - visualizes category tree with https://graphviz.org/ * [https://gerrit.wikimedia.org/r/plugins/gitiles/pywikibot/core/+/refs/heads/stable/scripts/category.py stable source of category.py] [[Category:Pywikibot scripts{{#translation:}}|category]] fvq4dt73fel72dambv4lvrkxfcfksv5 Growth/FAQ/nan 0 1433273 5387837 5378641 2022-07-29T10:15:24Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''<span lang="en" dir="ltr" class="mw-content-ltr">Welcome to the Growth team Frequently Asked Questions (FAQ).</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">We hope you will find the information you need. However, if it is not the case, [[Talk:Growth|let us know]].</span> ''<span lang="en" dir="ltr" class="mw-content-ltr">Note for translators: this page is updated regularly, which may impact your work. We are doing our best to avoid these disturbances.</span>'' == It-puann == {{Anchor|features}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Which features are you working on? === </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NH|'''Newcomer homepage''']]: a new special page, the best place for a newcomer to get started. It includes:</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NT|'''Newcomer tasks''']]: a feed of task suggestions that help newcomers learn to edit. Newcomers have been making [[NEWTEA|productive edits]] through this feed! [[Help:Growth/Tools/Suggested edits|Know more about this tool]].</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Mentorship module''' [optional module]: each newcomers has a direct link to an experienced user. This way, they can ask questions about editing Wikipedia, less the need to find where to ask for assistance.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Impact module''': the user sees how many pages views articles they edit received.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#HP|'''Help panel''']]: a platform to provide resources to newcomers while they are editing. If they choose one of the suggested tasks on the newcomer homepage, they are guided step-by-step on the process of editing.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''[[Growth/Understanding first day|Welcome Survey]]''': communities can know why newcomers create an account on Wikipedia.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You can have a look at '''[[Special:MyLanguage/Growth/Feature summary|our features summary]]''' to know more about it. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === On which wikis Growth features have been deployed? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find a list of wikis on our [[Special:MyLanguage/Growth/Deployment table|Deployment table]]. This page lists features activation per wiki as well. </div> {{anchor|NEWTEA}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Are Growth features effective? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[NEWTEA|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that newcomers make their first article edit (+11.6%)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that they are retained as editors</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the number of edits they make during their first couple of weeks on the wiki (+22%)</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This deployment has been achieved in October 2021.</span> {{anchor|translate}} <div lang="en" dir="ltr" class="mw-content-ltr"> === The interface is partially translated. How can I change this? === </div> [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] <div lang="en" dir="ltr" class="mw-content-ltr"> It takes up to one week to see new translations being deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Special pages names require a special process. For the following strings, [[Talk:Growth|please contact us]] directly with the translations: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. </div> {{anchor|enable|test}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I test the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[Growth/Deployment table|On wikis where the Growth features are available]], and also on [https://test.wikipedia.org test.wikipedia.org], go to your [[Special:Preferences#mw-prefsection-personal|user preferences]] on one of these wikis and then: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Help panel''' in the ''{{int|prefs-editing}}'' tab.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Newcomer homepage''' in the ''{{int|prefs-personal}}'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work.</span> {{anchor|get}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can my wiki get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[#features|these features]], with the following conditions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Do you plan to deploy the features outside of Wikipedia? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Please contact us [[Talk:Growth|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> We are considering working with [[Growth/Communities/Wikisource|Wikisource communities]]. </div> {{anchor|pilot|ambassador}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can you clarify what "Pilot wikis", "Control group wikis" and "Ambassadors" are? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''Pilot wikis''' are wikis who have a close collaboration with the Growth team. They are involved in projects definitions and early review of the projects. They also test all prototypes first. The Growth team can contact some other wikis for some of these steps. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, our pilot wikis are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I use the Growth features on mobile ? On the official apps (iOS, Android)? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Access to the features == </div> {{anchor|ABtest}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can new accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where no [[A/B testing|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where an [[A/B testing|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How can existing accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], anyone can find the features [[#enable|in their Preferences]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === I host a workshop. How can I control if my students get the features when they create an account? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is possible to have a link parameter to control access to the features: </div> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=1</code> will force Growth features at account creation</span> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=0</code> will force the default experience at account creation</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[Talk:Growth|Please let us know]] if you plan to use these parameters. </div> {{anchor|Homepage}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Homepage == </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> === How to access the Homepage? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My email is requested, or my email is displayed at the top of the Homepage. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[Special:MyLanguage/Help:Notifications|notifications]], like when they are mentioned by other users on wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The email address won't be visible by other users. Communication with other users all happen on the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === The help links displayed on the homepage are not relevant. How to change them? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#HP|the same as on the Help panel]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Suggested edits == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How does Suggested Edits work ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How topics and tasks are suggested? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === SuggestedEdits' supervision and troubleshooting === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can I monitor which articles have been edited as Suggested edits? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to monitor which topics or which tasks need more articles? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please use <code>Special:NewcomerTasksInfo</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I don't have any task for a given combination. Is it normal? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== A user uses the tools in an nonconstructive way. What can I do? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Overall, users make [[#NEWTEA|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">try to understand what the use tries to do,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">contact this user, explain the situation, ask them for details and guide them to a different path if it exists,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">if the nonconstructive behavior persists, then block the user.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If repetitive and similar nonconstructive edits are made at your wiki, [[Talk:Growth|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you activated the Help panel in your preferences? If yes, [[Talk:Growth|please let us know about this issue]]. </div> {{anchor|config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Suggested edits configuration === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to provide more tasks for newcomers? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: </div> {| class="wikitable" !'''Jīm-bū''' !<span lang="en" dir="ltr" class="mw-content-ltr">Level of difficulty</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Goal of the task</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Copyedit article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">fix spelling, grammar and tone</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add Links</span> |kan-tan |<span lang="en" dir="ltr" class="mw-content-ltr">add links between articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Update article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">bring existing articles up-to-date</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add References</span> |Tiong lân-tōo |<span lang="en" dir="ltr" class="mw-content-ltr">find sources for existing articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Expand article</span> |Ko lân-tōo |<span lang="en" dir="ltr" class="mw-content-ltr">expand stubs to become sourced articles</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Add other templates that match the definition of the task to <code>Special:EditGrowthConfig</code> on your wiki</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add maintenance templates to more articles on your wiki.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is not possible at the moment. [[Talk:Growth|Please let us know]] about your potential project. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add a link === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Special:MyLanguage/Growth/Deployment table|where ''Structured tasks - Add a link'' has been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">"Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users have to decide if a link should be added or not added. These links are suggested by a machine.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which wikis have Structured tasks - Add a link ? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the accuracy of Structured tasks - Add a link predictions? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The predictions are, on average, accurate at 70%. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add an image === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the purpose of "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which rules define the work done by "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have several rules: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Only articles where no image is displayed are taken into consideration for images addition.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Articles with an infobox but no image aren't taken into consideration for now.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which types of users have been contacted to test this new concept ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">people who aren't wiki editors (using UserTesting.com, in English and Spanish)</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia.</span> {{anchor|HP}} == Pang-tsoo puânn-bīn == <div lang="en" dir="ltr" class="mw-content-ltr"> === We want to change some links displayed on the Help panel. How to do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#Homepage|also used on the Homepage]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where does questions posted using the Help panel goes? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, these questions go the the local Help desk. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should go the newcomer's mentors,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should be posted at the help desk.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change this configuration using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page.</span> {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration and operation of the mentoring system == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My wiki doesn't have the Growth mentoring system. How can I set it up? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The next steps are a summary of the process. The full process is described on [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|this dedicated page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, you need to check if the Growth tools are [[Growth/Deployment table|deployed at your wiki]]. If it is not yet the case, please see [[#get|how to get the features]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Then, you have to find some other mentors to volunteer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All mentors have to sign-up on a specific page, using [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a specific syntax]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> At your wiki, an admin has to add the mentor list to the configuration page (<code>Special:EditGrowthConfig</code>). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many mentors does a wiki need? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We recommend to have at least 3 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How mentors are assigned to newcomers? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Each new account receives a mentor randomly taken from a list of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many messages does a mentor receive per week? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Have you considered to assign a mentor only to people who already made some edits? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We don't know what each newcomer needs. [[Special:MyLanguage/New Editor Experiences|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. </div> {{anchor|existing}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[d:Q3919128|listed on Wikidata]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: </div> '''<span lang="en" dir="ltr" class="mw-content-ltr">Replace your mentoring system with the new one</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">If your mentoring system hasn't much success, it could be replaced by the Growth team features.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">Have both systems working together</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">You can imagine to have two roles:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Growth mentoring takes care of the newcomers basic questions,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The existing mentoring can take care of newcomers who are more involved.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> In this case, you might have to locally translate the interface for Growth features using your own terms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where can I signup as a mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Your community may have defined some conditions to become a mentor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How do I introduce myself as a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you sign up to become a mentor, the following syntax must be used, with: </div> <code>* <nowiki>[[</nowiki><span lang="en" dir="ltr" class="mw-content-ltr">User:Username</span><nowiki>]]</nowiki>|<span lang="en" dir="ltr" class="mw-content-ltr">Description</span></code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|<span lang="en" dir="ltr" class="mw-content-ltr">Read more about this</span>]] {{anchor|reassign}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can we reassign a newcomer to a different mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes, it is possible using <code>Special:ClaimMentee</code>. </div> {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === A mentor just quit. Can we reassign all their newcomer to different mentors? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can use <code>Special:ClaimMentee</code> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[Talk:Growth|please contact us]] directly. </div> {{anchor|magicword}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Type the magic word <code><nowiki>{{#mentor:Foo}}</nowiki></code> in a wikitext page, and preview. "Foo" has to be replaced by the username you target. This will display the name of Foo's mentor. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[#reassign|If the mentor changes]], then the magic word picks the new mentor's name. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can "[[Special:MyLanguage/Help:Substitution|subst:]]" this message if needed: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Foo's mentor will then be saved as wikitext. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you updated <code>Special:EditGrowthConfig</code> with the new page name? </div> == Tó-su hām sin-lâng ê hōo-tōng == {{Anchor|questions}} <div lang="en" dir="ltr" class="mw-content-ltr"> === What kinds of questions do newcomers ask? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> From the observations we have made, questions are mostly about basic editing. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on communities experiences, the Growth team worked [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|on a guide for mentors]] who have to reply to these questions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Newcomers haven't replied to my messages. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Two possible cases there: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can I ask if my mentor is not responding to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I ask to have a different mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[#reassign|make the change]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, how can I monitor the newcomers assigned to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are currently working on a [[Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is available at all Wikipedias where [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|a list of mentors has been created and activated]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At wikis where the mentor dashboard is deployed, a new filter is available for mentors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They can monitor their mentees' activity in Watchlist and RecentChanges.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|not listed as mentors]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> b722pirizteqss27l34xhd1pdtygepi Reading/Web/Desktop Improvements/Updates/Talk to Web/uk 0 1436719 5387123 5383464 2022-07-28T20:35:32Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Архіви |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 56ckhfzvdqzzxr4flrm88xjdz899vde Reading/Web/Desktop Improvements/Updates/Talk to Web/sv 0 1437255 5387121 5383463 2022-07-28T20:35:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Arkiv |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} s8bsx86n7ng6cpo2mdm9m6w2xh13zmh Extension:ViewTable/de 102 1438021 5386877 4855840 2022-07-28T19:33:49Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = unmaintained |type1 = |type2 = |hook1 = |hook2 = |username = Leucosticte |author = Leucosticte |description = <span lang="en" dir="ltr" class="mw-content-ltr">View database tables</span> |image = ViewTable.png |imagesize = 300px |version = |update = 2014-09-30 |version preview = |update preview = |mediawiki = 1.24+ |php = |needs-updatephp = |composer = |table1 = |table2 = |license = GPL-3.0-or-later |download = {{GithubDownload|Inclumedia|ViewTable}} |readme = |changelog = |example = |namespace = |parameters = |tags = |rights = |compatibility = |bugzilla = |vagrant-role = }} <span lang="en" dir="ltr" class="mw-content-ltr">This creates a special page, Special:ViewTable, that allows bureaucrats to view database tables.</span> <span lang="en" dir="ltr" class="mw-content-ltr">User Special:ViewTable/all to view all tables (will probably take awhile because of the {{db table|objectcache}}.</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/Inclumedia/ViewTable/archive/master.zip Erweiterung herunterladen] }} o0xq9rzjtwfwdjhzm231fhljjlbylci Extension:VectorUp/de 102 1438023 5386887 5107224 2022-07-28T19:35:22Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki <languages/> {{Extension | status = beta | type1 = skin | hook1 = BeforePageDisplay | author = Simon Heimler | username = Fannon | version = 1.2.0 | update = 2016-02-02 | mediawiki = 1.20+ | license = MIT | download = {{GithubDownload|Fannon|VectorUp}} | readme = [https://github.com/Fannon/VectorUp/blob/master/README.md README] | php = 5.2+ | needs-updatephp = No }} == Beschreibung == <span lang="en" dir="ltr" class="mw-content-ltr">This is a personal collection of CSS Style changes and JavaScript Snippets / Fixes.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The goal is to provide a more modern and consistent MediaWiki / SMW appearance.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course this is totally subjective. Feel free to use, like or dislike it :)</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/Fannon/VectorUp/archive/master.zip Erweiterung herunterladen] }} <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of downloading the zip archive you may also check this extension out via Git: </div> <syntaxhighlight lang="bash"> git clone https://github.com/Fannon/VectorUp.git </syntaxhighlight> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> You're already done. Enjoy the skin! </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Notable Features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Changed Typography </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The TOC is floating on the right side </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Semantic Forms have a more consistent layout, forced by fixed width fields </div> 8apv8h9onej1duee9fv2aphz8rvh6ih 5386889 5386887 2022-07-28T19:37:28Z ThisCarthing 17456337 Created page with "Du bist bereits fertig! Genieße den Skin!" wikitext text/x-wiki <languages/> {{Extension | status = beta | type1 = skin | hook1 = BeforePageDisplay | author = Simon Heimler | username = Fannon | version = 1.2.0 | update = 2016-02-02 | mediawiki = 1.20+ | license = MIT | download = {{GithubDownload|Fannon|VectorUp}} | readme = [https://github.com/Fannon/VectorUp/blob/master/README.md README] | php = 5.2+ | needs-updatephp = No }} == Beschreibung == <span lang="en" dir="ltr" class="mw-content-ltr">This is a personal collection of CSS Style changes and JavaScript Snippets / Fixes.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The goal is to provide a more modern and consistent MediaWiki / SMW appearance.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course this is totally subjective. Feel free to use, like or dislike it :)</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/Fannon/VectorUp/archive/master.zip Erweiterung herunterladen] }} <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of downloading the zip archive you may also check this extension out via Git: </div> <syntaxhighlight lang="bash"> git clone https://github.com/Fannon/VectorUp.git </syntaxhighlight> == Verwendung == Du bist bereits fertig! Genieße den Skin! <div lang="en" dir="ltr" class="mw-content-ltr"> == Notable Features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Changed Typography </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The TOC is floating on the right side </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Semantic Forms have a more consistent layout, forced by fixed width fields </div> qdxu5mrgx3rctt73rupgwjql9r4wg7o Extension:UserWelcome/de 102 1438025 5387069 4961698 2022-07-28T20:10:19Z ThisCarthing 17456337 Created page with "Was auch immer SocialProfile benötigt" wikitext text/x-wiki <languages /> {{Extension |status = stable |type = tag |author = David Pean<br />[[User:Jack Phoenix|Jack Phoenix]] |image = |version = 1.4.1 |update = |mediawiki = Was auch immer SocialProfile benötigt |download = <span lang="en" dir="ltr" class="mw-content-ltr">Available as a part of {{ll|Extension:SocialProfile}}</span> |readme = |changelog = |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds {{ll|Extension:SocialProfile|nsp=0}} tag to display user-specific social info to logged-in users when {{ll|Extension:SocialProfile|nsp=0}} extension is installed on the wiki.</span> |parameters = |license = GPL-2.0-or-later |bugzilla = Social-Tools |example = [http://fishhooks.shoutwiki.com/ Fish Hooks Wiki] (<span lang="en" dir="ltr" class="mw-content-ltr">while logged in</span>) |translate = ext-UserWelcome }} <span lang="en" dir="ltr" class="mw-content-ltr">'''UserWelcome''' extension adds {{tag|welcomeUser|single}} parser hook that displays user-specific social info to the user on the page where a {{tag|welcomeUser|single}} tag is present.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The extension will display the number of new user board messages, gifts, awards, friend and foe requests and the amount of points required to advance into the next level.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">You '''need''' to have {{ll|Extension:SocialProfile|nsp=0}} installed and configured properly before installing this extension, since this requires parts of SocialProfile extension and is not meant to be used standalone.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">UserWelcome extension works well with {{ll|Extension:WikiTextLoggedInOut|nsp=0}} extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have these extensions installed alongside SocialProfile, you could add the following code to your wiki's main page to show random avatars to anonymous users and user-specific social info to logged-in users:</span> <syntaxhighlight lang=html> <loggedout><randomuserswithavatars count=15 row=5/></loggedout> <loggedin><welcomeUser/></loggedin> </syntaxhighlight> == Installation == {{ExtensionInstall |SocialProfile/UserWelcome |registration=1 |no-registration-version=1.28 }} {{Social tools}} [[Category:Extensions by Fandom{{#translation:}}]] rjm7yhy14ua8gdo5keg8tmpus4mdu7h 5387071 5387069 2022-07-28T20:10:26Z ThisCarthing 17456337 Created page with "Verfügbar als Teil von $1" wikitext text/x-wiki <languages /> {{Extension |status = stable |type = tag |author = David Pean<br />[[User:Jack Phoenix|Jack Phoenix]] |image = |version = 1.4.1 |update = |mediawiki = Was auch immer SocialProfile benötigt |download = Verfügbar als Teil von {{ll|Extension:SocialProfile}} |readme = |changelog = |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds {{ll|Extension:SocialProfile|nsp=0}} tag to display user-specific social info to logged-in users when {{ll|Extension:SocialProfile|nsp=0}} extension is installed on the wiki.</span> |parameters = |license = GPL-2.0-or-later |bugzilla = Social-Tools |example = [http://fishhooks.shoutwiki.com/ Fish Hooks Wiki] (<span lang="en" dir="ltr" class="mw-content-ltr">while logged in</span>) |translate = ext-UserWelcome }} <span lang="en" dir="ltr" class="mw-content-ltr">'''UserWelcome''' extension adds {{tag|welcomeUser|single}} parser hook that displays user-specific social info to the user on the page where a {{tag|welcomeUser|single}} tag is present.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The extension will display the number of new user board messages, gifts, awards, friend and foe requests and the amount of points required to advance into the next level.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">You '''need''' to have {{ll|Extension:SocialProfile|nsp=0}} installed and configured properly before installing this extension, since this requires parts of SocialProfile extension and is not meant to be used standalone.</span>}} <span lang="en" dir="ltr" class="mw-content-ltr">UserWelcome extension works well with {{ll|Extension:WikiTextLoggedInOut|nsp=0}} extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if you have these extensions installed alongside SocialProfile, you could add the following code to your wiki's main page to show random avatars to anonymous users and user-specific social info to logged-in users:</span> <syntaxhighlight lang=html> <loggedout><randomuserswithavatars count=15 row=5/></loggedout> <loggedin><welcomeUser/></loggedin> </syntaxhighlight> == Installation == {{ExtensionInstall |SocialProfile/UserWelcome |registration=1 |no-registration-version=1.28 }} {{Social tools}} [[Category:Extensions by Fandom{{#translation:}}]] trvczlmhg4trqc6xnrlm473kw68k4w9 Extension:UserThrottle/de 102 1438027 5387063 4858530 2022-07-28T20:09:17Z ThisCarthing 17456337 Created page with "== Was diese Erweiterung macht ==" wikitext text/x-wiki <languages/> {{unmaintained extension}} {{Extension|templatemode = |status = unmaintained |type1 = access |type2 = |hook1 = AbortNewAccount |hook2 = |username = Brion VIBBER |author = Brion Vibber |description = <span lang="en" dir="ltr" class="mw-content-ltr">Throttle on user account registrations</span> |image = |imagesize = |version = |update = |mediawiki = |php = |license = GPL-2.0-or-later |download = {{WikimediaDownload}} |readme = |changelog = |parameters = |tags = |rights = |example = |compatibility = }} == Was diese Erweiterung macht == <span lang="en" dir="ltr" class="mw-content-ltr">Monitors global frequency of user account registrations and throttles apparent flood attacks, regardless of origin.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not always suitable for use on large public sites, but it's been used during occasional particular vandal attacks on Wikimedia in the past.</span> == Installation == <div lang="en" dir="ltr" class="mw-content-ltr"> To install this extension, add the following to {{ll|Manual:LocalSettings.php|LocalSettings.php}}: </div> <syntaxhighlight lang="php"> require_once("$IP/extensions/UserThrottle/UserThrottle.php"); </syntaxhighlight> == Konfiguration == <div lang="en" dir="ltr" class="mw-content-ltr"> You can adjust the throttle settings in $wgGlobalAccountCreationThrottle: </div> <syntaxhighlight lang="php"> $wgGlobalAccountCreationThrottle = array( 'min_interval' => 5, // Hard minimum time between creations 'soft_time' => 300, // Timeout for rolling count 'soft_limit' => 10, // 10 registrations in five minutes ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> If you legitimately have signup floods, you may wish to adjust these. </div> eksoozy0mqw3vzsm5vbeas5wayfunvh 5387065 5387063 2022-07-28T20:09:43Z ThisCarthing 17456337 Created page with "10 Registrierungen in fünf Minuten" wikitext text/x-wiki <languages/> {{unmaintained extension}} {{Extension|templatemode = |status = unmaintained |type1 = access |type2 = |hook1 = AbortNewAccount |hook2 = |username = Brion VIBBER |author = Brion Vibber |description = <span lang="en" dir="ltr" class="mw-content-ltr">Throttle on user account registrations</span> |image = |imagesize = |version = |update = |mediawiki = |php = |license = GPL-2.0-or-later |download = {{WikimediaDownload}} |readme = |changelog = |parameters = |tags = |rights = |example = |compatibility = }} == Was diese Erweiterung macht == <span lang="en" dir="ltr" class="mw-content-ltr">Monitors global frequency of user account registrations and throttles apparent flood attacks, regardless of origin.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not always suitable for use on large public sites, but it's been used during occasional particular vandal attacks on Wikimedia in the past.</span> == Installation == <div lang="en" dir="ltr" class="mw-content-ltr"> To install this extension, add the following to {{ll|Manual:LocalSettings.php|LocalSettings.php}}: </div> <syntaxhighlight lang="php"> require_once("$IP/extensions/UserThrottle/UserThrottle.php"); </syntaxhighlight> == Konfiguration == <div lang="en" dir="ltr" class="mw-content-ltr"> You can adjust the throttle settings in $wgGlobalAccountCreationThrottle: </div> <syntaxhighlight lang="php"> $wgGlobalAccountCreationThrottle = array( 'min_interval' => 5, // Hard minimum time between creations 'soft_time' => 300, // Timeout for rolling count 'soft_limit' => 10, // 10 Registrierungen in fünf Minuten ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> If you legitimately have signup floods, you may wish to adjust these. </div> af8peia3xtolkkwygml8xjkpl2ka4k1 5387067 5387065 2022-07-28T20:09:57Z ThisCarthing 17456337 Created page with "Um diese Erweiterung zu installieren, füge folgendes zu $LocalSettings hinzu:" wikitext text/x-wiki <languages/> {{unmaintained extension}} {{Extension|templatemode = |status = unmaintained |type1 = access |type2 = |hook1 = AbortNewAccount |hook2 = |username = Brion VIBBER |author = Brion Vibber |description = <span lang="en" dir="ltr" class="mw-content-ltr">Throttle on user account registrations</span> |image = |imagesize = |version = |update = |mediawiki = |php = |license = GPL-2.0-or-later |download = {{WikimediaDownload}} |readme = |changelog = |parameters = |tags = |rights = |example = |compatibility = }} == Was diese Erweiterung macht == <span lang="en" dir="ltr" class="mw-content-ltr">Monitors global frequency of user account registrations and throttles apparent flood attacks, regardless of origin.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Not always suitable for use on large public sites, but it's been used during occasional particular vandal attacks on Wikimedia in the past.</span> == Installation == Um diese Erweiterung zu installieren, füge folgendes zu {{ll|Manual:LocalSettings.php|LocalSettings.php}} hinzu: <syntaxhighlight lang="php"> require_once("$IP/extensions/UserThrottle/UserThrottle.php"); </syntaxhighlight> == Konfiguration == <div lang="en" dir="ltr" class="mw-content-ltr"> You can adjust the throttle settings in $wgGlobalAccountCreationThrottle: </div> <syntaxhighlight lang="php"> $wgGlobalAccountCreationThrottle = array( 'min_interval' => 5, // Hard minimum time between creations 'soft_time' => 300, // Timeout for rolling count 'soft_limit' => 10, // 10 Registrierungen in fünf Minuten ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> If you legitimately have signup floods, you may wish to adjust these. </div> 53qf4ctfyvmczkruex044pfnakivwnr Extension:UnicodeConverter/de 102 1438044 5387043 4855871 2022-07-28T20:00:35Z ThisCarthing 17456337 Created page with "Beispielspezialseite" wikitext text/x-wiki <languages/> {{Extension |name = UnicodeConverter |status = stable |type1 = special |description = Beispielspezialseite |username = Tim Starling |license = GPL2 or {{Tim Starling license}} |download = {{WikimediaDownload|UnicodeConverter}} |phabricator = MediaWiki-extensions-UnicodeConverter }} <span lang="en" dir="ltr" class="mw-content-ltr">This was the first special page extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It was created as a demonstration showing how to create special page extensions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Its function is to take Unicode text pasted into an input box, and to show the text with any non-ASCII characters converted to HTML entities.</span> == Installation == {{ExtensionInstall |registration=yes }} c6mmiw4b69gx7f7yswtv6sux35wajfq 5387045 5387043 2022-07-28T20:00:56Z ThisCarthing 17456337 Created page with "Dies war die erste Spezialseitenerweiterung." wikitext text/x-wiki <languages/> {{Extension |name = UnicodeConverter |status = stable |type1 = special |description = Beispielspezialseite |username = Tim Starling |license = GPL2 or {{Tim Starling license}} |download = {{WikimediaDownload|UnicodeConverter}} |phabricator = MediaWiki-extensions-UnicodeConverter }} Dies war die erste Spezialseitenerweiterung. <span lang="en" dir="ltr" class="mw-content-ltr">It was created as a demonstration showing how to create special page extensions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Its function is to take Unicode text pasted into an input box, and to show the text with any non-ASCII characters converted to HTML entities.</span> == Installation == {{ExtensionInstall |registration=yes }} gid9zeh36y6lp6bkvpb2rm9tqt35ida Extension:TimedMediaHandler/de 102 1438059 5386851 5381532 2022-07-28T19:23:27Z ThisCarthing 17456337 Created page with "== Funktionsübersicht ==" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = media |type2 = api |author = Michael Dale, Jan Gerber, Tim Starling, James Heinrich, Brion Vibber, Derk-Jan Hartman |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides integrated support for server side transcoding, WebM, Ogg Theora, Vorbis, MP3, Speex and Timed Text</span> |image = Screenshot of TimedMediaHandler using VideoJS with Big Buck Bunny.png |imagesize = 300 |version = |update = |mediawiki = |php = |compatibility policy = rel |download = {{WikimediaDownload}} |phabricator = timedmediahandler |table1 = transcode }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''TimedMediaHandler''' extension allows you to display audio and video files in wiki pages, using the same syntax as for [[Special:MyLanguage/Help:Images|image]] files.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It includes the [[Special:MyLanguage/Extension:TimedMediaHandler/VideoJS Player|VideoJS Player]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">There is support for subtitles and captions (aka Timed Text) and real time stream switching between multiple WebM and other derivatives and many other features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">TMH server side support includes options for uploading HTML5 audio and video, multiple transcode profiles to deliver content, playback of MIDI files, metadata parsing for Ogg and WebM videos, and integration with MediaWiki's [[Special:MyLanguage/Manual:Job queue|job queue]] system for scheduling transcoding jobs.</span> '''''For new and upcoming developments in 2022, see [[Extension:TimedMediaHandler/2022 work]].''''' ''<span lang="en" dir="ltr" class="mw-content-ltr">Please note that TimedMediaHandler does not currently work with PostgreSQL.</span> Siehe {{Phab|T157424}}.'' == Funktionsübersicht == <div lang="en" dir="ltr" class="mw-content-ltr"> For the player see: [[Special:MyLanguage/Extension:TimedMediaHandler/VideoJS Player|VideoJS Player]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For features of the subtitling system, see [[commons:Special:MyLanguage/Commons:Timed Text|Commons:Timed Text]] page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Syntax synopsis== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In addition to the [[Special:MyLanguage/Help:Images#Syntax|image embed syntax]], Timed Media Handler supports: </div> ; <nowiki>[[File:Video.ogv|File:Video.ogv]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Display a video at its nominal size. Displays a still image from the midpoint with a play button to start an embedded player.</span> ; <nowiki>[[File:Audio.oga|File:Audio.oga]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a placeholder for a sound file, with a play button to start an embedded player.</span> ; <nowiki>[[File:Midi.mid]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Generate digital audio from the music instructions in the MIDI file, and show the embedded audio player to play this audio.</span> ; <nowiki>[[File:Video.ogv|thumb]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a video in a floating thumbnail box</span> ; <syntaxhighlight lang=html inline><gallery>File:Video.ogv</gallery></syntaxhighlight> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a video embedded in an image gallery (each clip will popup a dialog for the full player)</span> ; <nowiki>[[File:Video.ogg|thumbtime=1:25]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Use a frame from 1 minute 25 seconds into the video as the placeholder image. A single number is taken as an offset in seconds.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One can also use HH:MM:SS, e.g. 1:02:22 will be 1 hour, 2 minutes, and 22 seconds into the video.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Floating-point seconds are supported (but broken on Wikimedia wikis: [[phab:T228467]]).</span> ; <nowiki>[[File:Video.ogg|start=1:25]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">''Temporal media fragments'' displays a video clip starting at 1 minute 25 seconds into the video. A single number is taken as an offset in seconds. You can also include an end time of the form <code>end=1:30</code> Which would result in a clip of 5 seconds playing from 1:25 to 1:30. If thumbtime is not provided, the start time will be used for the displayed thumbnail.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One can also use HH:MM:SS, e.g. 1:02:22 will be 1 hour, 2 minutes, and 22 seconds into the video.</span> : <span lang="en" dir="ltr" class="mw-content-ltr"><code>start=</code> and <code>end=</code> can also be used as [[Special:MyLanguage/Manual:Parameters to index.php|query parameters]] in the URL for a video's file page.</span> ; <nowiki>[[File:Video.ogg|muted]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Start the media with muted audio.</span> {{introduced-inline|1.39}} ; <nowiki>[[File:Video.ogg|loop]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Loop the video continuously.</span> {{introduced-inline|1.39}} ; Veraltet : <span lang="en" dir="ltr" class="mw-content-ltr">The syntax words <kbd>noicon</kbd> and <kbd>noplayer</kbd> are deprecated and do not function.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The keyword disablecontrols will likely be deprecated.</span> (Siehe {{PhabT|T135537}}) <span lang="en" dir="ltr" class="mw-content-ltr">It takes a comma-separated list of any of the following values:</span> <kbd>options</kbd>, <kbd>timedText</kbd>, <kbd>fullscreen</kbd> <div lang="en" dir="ltr" class="mw-content-ltr"> == Client support == </div> [[File:Videoonwikipedia.ogv|300px|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Example video player</span>]] [[File:example.ogg|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Example audio player</span>]] [[File:example.ogg|300px|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Wider audio player, showing progress bar</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">The player works on most modern browsers (see [[Special:MyLanguage/Compatibility#Browser support matrix|MediaWiki's support matrix]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Mobile support is spotty, especially on iOS.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> TimedMediaHandler includes a [[Special:MyLanguage/Extension:TimedMediaHandler/ogv.js|JavaScript compatibility shim]] for Ogg audio/video that works in Safari, Internet Explorer 10/11, and Microsoft Edge browsers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party users of MediaWiki may also wish to manually enable MP4 H.264/AAC support for native video and audio playback in Safari/IE/Edge, but when using these formats you may need a patent license from MPEG-LA for internet broadcasting. </div> == Installation == <span lang="en" dir="ltr" class="mw-content-ltr">You will want a recent version of ''ffmpeg'' in order to support encoding to WebM (with the latest version of VP9).</span> {{ExtensionInstall |TimedMediaHandler |db-update=yes |composer=yes |oldreg= wfLoadExtension( 'TimedMediaHandler' ); $wgFFmpegLocation = '/usr/bin/ffmpeg'; // Häufigster ffmpeg-Pfad auf Linux |custom-steps= * [[#Configuration|Konfiguriere nach Bedarf.]] * <span lang="en" dir="ltr" class="mw-content-ltr">You may need to increase the allowed memory in {{ll|Manual:$wgMaxShellMemory|$wgMaxShellMemory}}.</span><!-- What is the recommended number?? --> }} <div lang="en" dir="ltr" class="mw-content-ltr"> The extension will automatically add supported file types (except for mp4) to {{ll|Manual:$wgFileExtensions|$wgFileExtensions}}, so you do not need to manually add video file types. </div> {{Note|1= <div lang="en" dir="ltr" class="mw-content-ltr"> After downloading this extension, please note that it requires {{ll|Composer}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> So, after installation change to the directory containing the extension e.g. "../extensions/TimedMediaHandler/" and run <code>composer install --no-dev</code>, or when updating: <code>composer update --no-dev</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Alternatively as well as preferably add the line <code>"extensions/TimedMediaHandler/composer.json"</code> to the "composer.local.json" file in the root directory of your wiki like e.g. </div> <syntaxhighlight lang="json"> { "extra": { "merge-plugin": { "include": [ "extensions/TimedMediaHandler/composer.json" ] } } } </syntaxhighlight> }} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Comparison of Wikipedia media encoding options=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of 2018, Wikimedia sites use VP9. </div> Sortiert nach Bandbreitenstufe: {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Bitrate</span> ! Mbit/s ! WebM VP8 ! WebM VP9 |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Super Low</span> | 0.08 | | 160p |- ! Sehr niedrig | 0.16 | 160p | 240p |- ! Niedrig | 0.25 | 240p | 360p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Moderate</span> | 0.5 | 360p | 480p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Medium</span> | 1.0 | 480p | 720p |- ! Hoch | 2.0 | 720p | 1080p |- ! Sehr hoch | 4.0 | 1080p | 1440p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Super high</span> | 8.0 | | 2160p |} Detaillierte Optionen: {| class="wikitable" |- style="text-align:center;" ! colspan="2" style="text-align:{{dir|{{pagelang}}|right|left}}"| Name !! 160P !240P!! 360P !! 480P !! 720P !! 1080P !160P !240P!! 360P !! 480P !! 720P !! 1080P !1440P!! 2160P |- style="text-align:center" | colspan="2" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Container''' || colspan="14" | WebM |- style="text-align:center" | rowspan="4" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Video''' || style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Codierung''' || colspan="6" | VP8 | colspan="8" |VP9 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Maximale Breite''' (Pixel) || 288 |426|| 640 || 854 || 1280 || 1920 |288 |426|| 640 || 854 || 1280 || 1920 |2560|| 4096 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Maximale Höhe''' (Pixel) || 160 |240|| 360 || 480 || 720 || 1080 |160 |240|| 360 || 480 || 720 || 1080 |1440|| 2160 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| <span lang="en" dir="ltr" class="mw-content-ltr">'''Bitrate'''</span> (Mbit/s) || 0.16 |0.25|| 0.5 || 1.0 || 2.0 || 4.0 |0.08 |0.16|| 0.25 || 0.5 || 1.0 || 2.0 |4.0|| 8.0 |- style="text-align:center" | rowspan="4" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Audio''' || style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Codierung''' | colspan="6" |Vorbis | colspan="8" |Opus |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Kanäle''' | colspan="6" |2&nbsp;(stereo) | colspan="8" |(pass-through) |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | <span lang="en" dir="ltr" class="mw-content-ltr">'''Sampling rate'''</span> (Hz) | colspan="6" |44100 | colspan="8" |48000 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Qualität''' || - ||| 1 || 2 || 3 || - | colspan="8" |(default) |} {{anchor|Configuration}} === Konfiguration === {{update}} {{Note|1='''<span lang="en" dir="ltr" class="mw-content-ltr">This section is out of date -- please update me</span>'''|2=reminder}} <div lang="en" dir="ltr" class="mw-content-ltr"> Here are some configuration variables which may be useful: </div> <syntaxhighlight lang="php"> // The minimum size for an embed video player (smaller than this size uses a pop-up player). $wgMinimumVideoPlayerSize = 200; // If transcoding is enabled for this wiki (if disabled, no transcode jobs are added and no transcode status is displayed). // Note if remote embedding an asset we will still check if the remote repo has transcoding enabled and associated flavors // for that media embed. $wgEnableTranscode = true; // The total amout of time a transcoding shell command can take: $wgTranscodeBackgroundTimeLimit = 3600 * 8; // Maximum amount of virtual memory available to transcoding processes in KB $wgTranscodeBackgroundMemoryLimit = 2 * 1024 * 1024; // 2GB avconv, ffmpeg2theora mmap resources so virtual memory needs to be high enough // Maximum file size transcoding processes can create, in KB $wgTranscodeBackgroundSizeLimit = 3 * 1024 * 1024; // 3GB // Number of threads to use in avconv for transcoding $wgFFmpegThreads = 1; // The NS for TimedText (registered on MediaWiki.org) // https://www.mediawiki.org/wiki/Extension_namespace_registration // Note commons pre-dates TimedMediaHandler and should set $wgTimedTextNS = 102 in LocalSettings.php $wgTimedTextNS = 710; // Set TimedText namespace for ForeignDBViaLBRepo on a per wikiID basis // $wgTimedTextForeignNamespaces = array( 'commonswiki' => 102 ); $wgTimedTextForeignNamespaces = array(); /** * Default enabled transcodes * * -If set to empty array, no derivatives will be created * -Derivative keys encode settings are defined in WebVideoTranscode.php * * -These transcodes are *in addition to* the source file. * -Only derivatives with smaller width than the source asset size will be created * -Regardless of source size at least one WebM and Ogg source will be created from the $wgEnabledTranscodeSet * -Derivative jobs are added to the MediaWiki JobQueue the first time the asset is uploaded * -Derivative should be listed min to max */ // Starting from 1.31 // All valid string values are listed in the extension's extension.json file $wgEnabledTranscodeSet = [ '160p.webm' => true, '240p.webm' => true, '360p.webm' => true, '480p.webm' => true, '720p.webm' => true, '1080p.webm' => true, ]; $wgEnabledAudioTranscodeSet = [ 'ogg' => true, // ogg+vorbis 'opus' => false, // ogg+opus 'mp3' => true, // raw mp3 'm4a' => false, // mp4+aac (mp4a.40.5) ]; // If mp3 source assets can be ingested: $wgTmhEnableMp3Uploads = true; // If mp4 source assets can be ingested: $wgTmhEnableMp4Uploads = false; // If you use ffmpeg 2 can be set it to true $wgUseFFmpeg2 = false; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> For transcoding, make sure you have {{phpi|$wgMaxShellMemory}}, {{phpi|$wgMaxShellTime}}, {{phpi|$wgMaxShellFileSize}} are large enough to allow encoding jobs to run and save output. Default values are most likely too low. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Running transcode jobs=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Because transcode jobs are resource intensive they will not run as part of normal job queue (see {{PhabT|T29336}}) Instead they must be requested by the <code>--type</code> argument: </div> <syntaxhighlight lang="php"> php maintenance/runJobs.php --type webVideoTranscode </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">If running this command causes it to hang forever, you may need to set {{phpi|$wgTranscodeBackgroundTimeLimit {{=}} 0;}} in LocalSettings.php.</span> Siehe {{phabricator|T206957}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ===Encoding nodes=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To be able to transcode many videos you might want to run multiple encoding nodes that connect to the master db and access your file store directly. You will need to install ffmpeg. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Minimal install under Debian and Ubuntu === </div> <syntaxhighlight lang="bash"> apt install ffmpeg </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Plus, add this to your {{ll|Manual:LocalSettings.php|LocalSettings.php}} (tested for [https://devuan.org/os/debian-fork/ascii-stable-announce-060818 Devuan ASCII] {{Webarchive|url=https://web.archive.org/web/20180923085518/https://devuan.org/os/debian-fork/ascii-stable-announce-060818 |date=2018-09-23 }} only):</span> <syntaxhighlight lang="php"> $wgFFmpegLocation = '/usr/bin/ffmpeg'; </syntaxhighlight> == Fehlerbehebung == {{Note|1='''Dieser Abschnitt muss erweitert werden'''|2=reminder}} ;{{anchor|wgMaxShellMemory}}"<code>ffmpeg</code> – <span lang="en" dir="ltr" class="mw-content-ltr">failed to map segment from shared object</span>" :<span lang="en" dir="ltr" class="mw-content-ltr">You need to increase the allowed memory in {{ll|Manual:$wgMaxShellMemory|$wgMaxShellMemory}}.</span><!-- What is the recommended number?? --> ;"Klasse 'getID3' nicht gefunden" :<span lang="en" dir="ltr" class="mw-content-ltr">You need to install the extension's PHP dependencies using Composer, see the Installation section above.</span> ;"<span lang="en" dir="ltr" class="mw-content-ltr">Unrecognized option 'max_muxing_queue_size'</span>" :<span lang="en" dir="ltr" class="mw-content-ltr">You may be using ffmpeg 2.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need add <source lang=php inline>$wgUseFFmpeg2 = true;</source> to your <code>LocalSettings.php</code>.</span> {{OnWikimedia}} {{Used by|canasta=1|fandom=1|miraheze=1}} [[Category:Media handling extensions{{#translation:}}]] [[Category:Video player extensions{{#translation:}}]] [[Category:Audio player extensions{{#translation:}}]] 5nzr90nwlnrkpvzc1pmziaxh88khb7x 5386853 5386851 2022-07-28T19:23:57Z ThisCarthing 17456337 Created page with "Bitrate" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = media |type2 = api |author = Michael Dale, Jan Gerber, Tim Starling, James Heinrich, Brion Vibber, Derk-Jan Hartman |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides integrated support for server side transcoding, WebM, Ogg Theora, Vorbis, MP3, Speex and Timed Text</span> |image = Screenshot of TimedMediaHandler using VideoJS with Big Buck Bunny.png |imagesize = 300 |version = |update = |mediawiki = |php = |compatibility policy = rel |download = {{WikimediaDownload}} |phabricator = timedmediahandler |table1 = transcode }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''TimedMediaHandler''' extension allows you to display audio and video files in wiki pages, using the same syntax as for [[Special:MyLanguage/Help:Images|image]] files.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It includes the [[Special:MyLanguage/Extension:TimedMediaHandler/VideoJS Player|VideoJS Player]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">There is support for subtitles and captions (aka Timed Text) and real time stream switching between multiple WebM and other derivatives and many other features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">TMH server side support includes options for uploading HTML5 audio and video, multiple transcode profiles to deliver content, playback of MIDI files, metadata parsing for Ogg and WebM videos, and integration with MediaWiki's [[Special:MyLanguage/Manual:Job queue|job queue]] system for scheduling transcoding jobs.</span> '''''For new and upcoming developments in 2022, see [[Extension:TimedMediaHandler/2022 work]].''''' ''<span lang="en" dir="ltr" class="mw-content-ltr">Please note that TimedMediaHandler does not currently work with PostgreSQL.</span> Siehe {{Phab|T157424}}.'' == Funktionsübersicht == <div lang="en" dir="ltr" class="mw-content-ltr"> For the player see: [[Special:MyLanguage/Extension:TimedMediaHandler/VideoJS Player|VideoJS Player]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For features of the subtitling system, see [[commons:Special:MyLanguage/Commons:Timed Text|Commons:Timed Text]] page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Syntax synopsis== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In addition to the [[Special:MyLanguage/Help:Images#Syntax|image embed syntax]], Timed Media Handler supports: </div> ; <nowiki>[[File:Video.ogv|File:Video.ogv]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Display a video at its nominal size. Displays a still image from the midpoint with a play button to start an embedded player.</span> ; <nowiki>[[File:Audio.oga|File:Audio.oga]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a placeholder for a sound file, with a play button to start an embedded player.</span> ; <nowiki>[[File:Midi.mid]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Generate digital audio from the music instructions in the MIDI file, and show the embedded audio player to play this audio.</span> ; <nowiki>[[File:Video.ogv|thumb]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a video in a floating thumbnail box</span> ; <syntaxhighlight lang=html inline><gallery>File:Video.ogv</gallery></syntaxhighlight> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a video embedded in an image gallery (each clip will popup a dialog for the full player)</span> ; <nowiki>[[File:Video.ogg|thumbtime=1:25]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Use a frame from 1 minute 25 seconds into the video as the placeholder image. A single number is taken as an offset in seconds.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One can also use HH:MM:SS, e.g. 1:02:22 will be 1 hour, 2 minutes, and 22 seconds into the video.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Floating-point seconds are supported (but broken on Wikimedia wikis: [[phab:T228467]]).</span> ; <nowiki>[[File:Video.ogg|start=1:25]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">''Temporal media fragments'' displays a video clip starting at 1 minute 25 seconds into the video. A single number is taken as an offset in seconds. You can also include an end time of the form <code>end=1:30</code> Which would result in a clip of 5 seconds playing from 1:25 to 1:30. If thumbtime is not provided, the start time will be used for the displayed thumbnail.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One can also use HH:MM:SS, e.g. 1:02:22 will be 1 hour, 2 minutes, and 22 seconds into the video.</span> : <span lang="en" dir="ltr" class="mw-content-ltr"><code>start=</code> and <code>end=</code> can also be used as [[Special:MyLanguage/Manual:Parameters to index.php|query parameters]] in the URL for a video's file page.</span> ; <nowiki>[[File:Video.ogg|muted]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Start the media with muted audio.</span> {{introduced-inline|1.39}} ; <nowiki>[[File:Video.ogg|loop]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Loop the video continuously.</span> {{introduced-inline|1.39}} ; Veraltet : <span lang="en" dir="ltr" class="mw-content-ltr">The syntax words <kbd>noicon</kbd> and <kbd>noplayer</kbd> are deprecated and do not function.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The keyword disablecontrols will likely be deprecated.</span> (Siehe {{PhabT|T135537}}) <span lang="en" dir="ltr" class="mw-content-ltr">It takes a comma-separated list of any of the following values:</span> <kbd>options</kbd>, <kbd>timedText</kbd>, <kbd>fullscreen</kbd> <div lang="en" dir="ltr" class="mw-content-ltr"> == Client support == </div> [[File:Videoonwikipedia.ogv|300px|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Example video player</span>]] [[File:example.ogg|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Example audio player</span>]] [[File:example.ogg|300px|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Wider audio player, showing progress bar</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">The player works on most modern browsers (see [[Special:MyLanguage/Compatibility#Browser support matrix|MediaWiki's support matrix]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Mobile support is spotty, especially on iOS.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> TimedMediaHandler includes a [[Special:MyLanguage/Extension:TimedMediaHandler/ogv.js|JavaScript compatibility shim]] for Ogg audio/video that works in Safari, Internet Explorer 10/11, and Microsoft Edge browsers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party users of MediaWiki may also wish to manually enable MP4 H.264/AAC support for native video and audio playback in Safari/IE/Edge, but when using these formats you may need a patent license from MPEG-LA for internet broadcasting. </div> == Installation == <span lang="en" dir="ltr" class="mw-content-ltr">You will want a recent version of ''ffmpeg'' in order to support encoding to WebM (with the latest version of VP9).</span> {{ExtensionInstall |TimedMediaHandler |db-update=yes |composer=yes |oldreg= wfLoadExtension( 'TimedMediaHandler' ); $wgFFmpegLocation = '/usr/bin/ffmpeg'; // Häufigster ffmpeg-Pfad auf Linux |custom-steps= * [[#Configuration|Konfiguriere nach Bedarf.]] * <span lang="en" dir="ltr" class="mw-content-ltr">You may need to increase the allowed memory in {{ll|Manual:$wgMaxShellMemory|$wgMaxShellMemory}}.</span><!-- What is the recommended number?? --> }} <div lang="en" dir="ltr" class="mw-content-ltr"> The extension will automatically add supported file types (except for mp4) to {{ll|Manual:$wgFileExtensions|$wgFileExtensions}}, so you do not need to manually add video file types. </div> {{Note|1= <div lang="en" dir="ltr" class="mw-content-ltr"> After downloading this extension, please note that it requires {{ll|Composer}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> So, after installation change to the directory containing the extension e.g. "../extensions/TimedMediaHandler/" and run <code>composer install --no-dev</code>, or when updating: <code>composer update --no-dev</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Alternatively as well as preferably add the line <code>"extensions/TimedMediaHandler/composer.json"</code> to the "composer.local.json" file in the root directory of your wiki like e.g. </div> <syntaxhighlight lang="json"> { "extra": { "merge-plugin": { "include": [ "extensions/TimedMediaHandler/composer.json" ] } } } </syntaxhighlight> }} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Comparison of Wikipedia media encoding options=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of 2018, Wikimedia sites use VP9. </div> Sortiert nach Bandbreitenstufe: {| class="wikitable" ! Bitrate ! Mbit/s ! WebM VP8 ! WebM VP9 |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Super Low</span> | 0.08 | | 160p |- ! Sehr niedrig | 0.16 | 160p | 240p |- ! Niedrig | 0.25 | 240p | 360p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Moderate</span> | 0.5 | 360p | 480p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Medium</span> | 1.0 | 480p | 720p |- ! Hoch | 2.0 | 720p | 1080p |- ! Sehr hoch | 4.0 | 1080p | 1440p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Super high</span> | 8.0 | | 2160p |} Detaillierte Optionen: {| class="wikitable" |- style="text-align:center;" ! colspan="2" style="text-align:{{dir|{{pagelang}}|right|left}}"| Name !! 160P !240P!! 360P !! 480P !! 720P !! 1080P !160P !240P!! 360P !! 480P !! 720P !! 1080P !1440P!! 2160P |- style="text-align:center" | colspan="2" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Container''' || colspan="14" | WebM |- style="text-align:center" | rowspan="4" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Video''' || style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Codierung''' || colspan="6" | VP8 | colspan="8" |VP9 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Maximale Breite''' (Pixel) || 288 |426|| 640 || 854 || 1280 || 1920 |288 |426|| 640 || 854 || 1280 || 1920 |2560|| 4096 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Maximale Höhe''' (Pixel) || 160 |240|| 360 || 480 || 720 || 1080 |160 |240|| 360 || 480 || 720 || 1080 |1440|| 2160 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| <span lang="en" dir="ltr" class="mw-content-ltr">'''Bitrate'''</span> (Mbit/s) || 0.16 |0.25|| 0.5 || 1.0 || 2.0 || 4.0 |0.08 |0.16|| 0.25 || 0.5 || 1.0 || 2.0 |4.0|| 8.0 |- style="text-align:center" | rowspan="4" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Audio''' || style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Codierung''' | colspan="6" |Vorbis | colspan="8" |Opus |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Kanäle''' | colspan="6" |2&nbsp;(stereo) | colspan="8" |(pass-through) |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | <span lang="en" dir="ltr" class="mw-content-ltr">'''Sampling rate'''</span> (Hz) | colspan="6" |44100 | colspan="8" |48000 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Qualität''' || - ||| 1 || 2 || 3 || - | colspan="8" |(default) |} {{anchor|Configuration}} === Konfiguration === {{update}} {{Note|1='''<span lang="en" dir="ltr" class="mw-content-ltr">This section is out of date -- please update me</span>'''|2=reminder}} <div lang="en" dir="ltr" class="mw-content-ltr"> Here are some configuration variables which may be useful: </div> <syntaxhighlight lang="php"> // The minimum size for an embed video player (smaller than this size uses a pop-up player). $wgMinimumVideoPlayerSize = 200; // If transcoding is enabled for this wiki (if disabled, no transcode jobs are added and no transcode status is displayed). // Note if remote embedding an asset we will still check if the remote repo has transcoding enabled and associated flavors // for that media embed. $wgEnableTranscode = true; // The total amout of time a transcoding shell command can take: $wgTranscodeBackgroundTimeLimit = 3600 * 8; // Maximum amount of virtual memory available to transcoding processes in KB $wgTranscodeBackgroundMemoryLimit = 2 * 1024 * 1024; // 2GB avconv, ffmpeg2theora mmap resources so virtual memory needs to be high enough // Maximum file size transcoding processes can create, in KB $wgTranscodeBackgroundSizeLimit = 3 * 1024 * 1024; // 3GB // Number of threads to use in avconv for transcoding $wgFFmpegThreads = 1; // The NS for TimedText (registered on MediaWiki.org) // https://www.mediawiki.org/wiki/Extension_namespace_registration // Note commons pre-dates TimedMediaHandler and should set $wgTimedTextNS = 102 in LocalSettings.php $wgTimedTextNS = 710; // Set TimedText namespace for ForeignDBViaLBRepo on a per wikiID basis // $wgTimedTextForeignNamespaces = array( 'commonswiki' => 102 ); $wgTimedTextForeignNamespaces = array(); /** * Default enabled transcodes * * -If set to empty array, no derivatives will be created * -Derivative keys encode settings are defined in WebVideoTranscode.php * * -These transcodes are *in addition to* the source file. * -Only derivatives with smaller width than the source asset size will be created * -Regardless of source size at least one WebM and Ogg source will be created from the $wgEnabledTranscodeSet * -Derivative jobs are added to the MediaWiki JobQueue the first time the asset is uploaded * -Derivative should be listed min to max */ // Starting from 1.31 // All valid string values are listed in the extension's extension.json file $wgEnabledTranscodeSet = [ '160p.webm' => true, '240p.webm' => true, '360p.webm' => true, '480p.webm' => true, '720p.webm' => true, '1080p.webm' => true, ]; $wgEnabledAudioTranscodeSet = [ 'ogg' => true, // ogg+vorbis 'opus' => false, // ogg+opus 'mp3' => true, // raw mp3 'm4a' => false, // mp4+aac (mp4a.40.5) ]; // If mp3 source assets can be ingested: $wgTmhEnableMp3Uploads = true; // If mp4 source assets can be ingested: $wgTmhEnableMp4Uploads = false; // If you use ffmpeg 2 can be set it to true $wgUseFFmpeg2 = false; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> For transcoding, make sure you have {{phpi|$wgMaxShellMemory}}, {{phpi|$wgMaxShellTime}}, {{phpi|$wgMaxShellFileSize}} are large enough to allow encoding jobs to run and save output. Default values are most likely too low. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Running transcode jobs=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Because transcode jobs are resource intensive they will not run as part of normal job queue (see {{PhabT|T29336}}) Instead they must be requested by the <code>--type</code> argument: </div> <syntaxhighlight lang="php"> php maintenance/runJobs.php --type webVideoTranscode </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">If running this command causes it to hang forever, you may need to set {{phpi|$wgTranscodeBackgroundTimeLimit {{=}} 0;}} in LocalSettings.php.</span> Siehe {{phabricator|T206957}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ===Encoding nodes=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To be able to transcode many videos you might want to run multiple encoding nodes that connect to the master db and access your file store directly. You will need to install ffmpeg. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Minimal install under Debian and Ubuntu === </div> <syntaxhighlight lang="bash"> apt install ffmpeg </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Plus, add this to your {{ll|Manual:LocalSettings.php|LocalSettings.php}} (tested for [https://devuan.org/os/debian-fork/ascii-stable-announce-060818 Devuan ASCII] {{Webarchive|url=https://web.archive.org/web/20180923085518/https://devuan.org/os/debian-fork/ascii-stable-announce-060818 |date=2018-09-23 }} only):</span> <syntaxhighlight lang="php"> $wgFFmpegLocation = '/usr/bin/ffmpeg'; </syntaxhighlight> == Fehlerbehebung == {{Note|1='''Dieser Abschnitt muss erweitert werden'''|2=reminder}} ;{{anchor|wgMaxShellMemory}}"<code>ffmpeg</code> – <span lang="en" dir="ltr" class="mw-content-ltr">failed to map segment from shared object</span>" :<span lang="en" dir="ltr" class="mw-content-ltr">You need to increase the allowed memory in {{ll|Manual:$wgMaxShellMemory|$wgMaxShellMemory}}.</span><!-- What is the recommended number?? --> ;"Klasse 'getID3' nicht gefunden" :<span lang="en" dir="ltr" class="mw-content-ltr">You need to install the extension's PHP dependencies using Composer, see the Installation section above.</span> ;"<span lang="en" dir="ltr" class="mw-content-ltr">Unrecognized option 'max_muxing_queue_size'</span>" :<span lang="en" dir="ltr" class="mw-content-ltr">You may be using ffmpeg 2.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need add <source lang=php inline>$wgUseFFmpeg2 = true;</source> to your <code>LocalSettings.php</code>.</span> {{OnWikimedia}} {{Used by|canasta=1|fandom=1|miraheze=1}} [[Category:Media handling extensions{{#translation:}}]] [[Category:Video player extensions{{#translation:}}]] [[Category:Audio player extensions{{#translation:}}]] 4d4nx4jfb5xe2j5e5zivea55j6emywc 5386855 5386853 2022-07-28T19:24:05Z ThisCarthing 17456337 Created page with "'''Bitrate'''" wikitext text/x-wiki <languages /> {{Extension |status = stable |type1 = media |type2 = api |author = Michael Dale, Jan Gerber, Tim Starling, James Heinrich, Brion Vibber, Derk-Jan Hartman |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides integrated support for server side transcoding, WebM, Ogg Theora, Vorbis, MP3, Speex and Timed Text</span> |image = Screenshot of TimedMediaHandler using VideoJS with Big Buck Bunny.png |imagesize = 300 |version = |update = |mediawiki = |php = |compatibility policy = rel |download = {{WikimediaDownload}} |phabricator = timedmediahandler |table1 = transcode }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''TimedMediaHandler''' extension allows you to display audio and video files in wiki pages, using the same syntax as for [[Special:MyLanguage/Help:Images|image]] files.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It includes the [[Special:MyLanguage/Extension:TimedMediaHandler/VideoJS Player|VideoJS Player]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">There is support for subtitles and captions (aka Timed Text) and real time stream switching between multiple WebM and other derivatives and many other features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">TMH server side support includes options for uploading HTML5 audio and video, multiple transcode profiles to deliver content, playback of MIDI files, metadata parsing for Ogg and WebM videos, and integration with MediaWiki's [[Special:MyLanguage/Manual:Job queue|job queue]] system for scheduling transcoding jobs.</span> '''''For new and upcoming developments in 2022, see [[Extension:TimedMediaHandler/2022 work]].''''' ''<span lang="en" dir="ltr" class="mw-content-ltr">Please note that TimedMediaHandler does not currently work with PostgreSQL.</span> Siehe {{Phab|T157424}}.'' == Funktionsübersicht == <div lang="en" dir="ltr" class="mw-content-ltr"> For the player see: [[Special:MyLanguage/Extension:TimedMediaHandler/VideoJS Player|VideoJS Player]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For features of the subtitling system, see [[commons:Special:MyLanguage/Commons:Timed Text|Commons:Timed Text]] page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Syntax synopsis== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In addition to the [[Special:MyLanguage/Help:Images#Syntax|image embed syntax]], Timed Media Handler supports: </div> ; <nowiki>[[File:Video.ogv|File:Video.ogv]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Display a video at its nominal size. Displays a still image from the midpoint with a play button to start an embedded player.</span> ; <nowiki>[[File:Audio.oga|File:Audio.oga]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a placeholder for a sound file, with a play button to start an embedded player.</span> ; <nowiki>[[File:Midi.mid]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Generate digital audio from the music instructions in the MIDI file, and show the embedded audio player to play this audio.</span> ; <nowiki>[[File:Video.ogv|thumb]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a video in a floating thumbnail box</span> ; <syntaxhighlight lang=html inline><gallery>File:Video.ogv</gallery></syntaxhighlight> : <span lang="en" dir="ltr" class="mw-content-ltr">Show a video embedded in an image gallery (each clip will popup a dialog for the full player)</span> ; <nowiki>[[File:Video.ogg|thumbtime=1:25]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Use a frame from 1 minute 25 seconds into the video as the placeholder image. A single number is taken as an offset in seconds.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One can also use HH:MM:SS, e.g. 1:02:22 will be 1 hour, 2 minutes, and 22 seconds into the video.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Floating-point seconds are supported (but broken on Wikimedia wikis: [[phab:T228467]]).</span> ; <nowiki>[[File:Video.ogg|start=1:25]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">''Temporal media fragments'' displays a video clip starting at 1 minute 25 seconds into the video. A single number is taken as an offset in seconds. You can also include an end time of the form <code>end=1:30</code> Which would result in a clip of 5 seconds playing from 1:25 to 1:30. If thumbtime is not provided, the start time will be used for the displayed thumbnail.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One can also use HH:MM:SS, e.g. 1:02:22 will be 1 hour, 2 minutes, and 22 seconds into the video.</span> : <span lang="en" dir="ltr" class="mw-content-ltr"><code>start=</code> and <code>end=</code> can also be used as [[Special:MyLanguage/Manual:Parameters to index.php|query parameters]] in the URL for a video's file page.</span> ; <nowiki>[[File:Video.ogg|muted]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Start the media with muted audio.</span> {{introduced-inline|1.39}} ; <nowiki>[[File:Video.ogg|loop]]</nowiki> : <span lang="en" dir="ltr" class="mw-content-ltr">Loop the video continuously.</span> {{introduced-inline|1.39}} ; Veraltet : <span lang="en" dir="ltr" class="mw-content-ltr">The syntax words <kbd>noicon</kbd> and <kbd>noplayer</kbd> are deprecated and do not function.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The keyword disablecontrols will likely be deprecated.</span> (Siehe {{PhabT|T135537}}) <span lang="en" dir="ltr" class="mw-content-ltr">It takes a comma-separated list of any of the following values:</span> <kbd>options</kbd>, <kbd>timedText</kbd>, <kbd>fullscreen</kbd> <div lang="en" dir="ltr" class="mw-content-ltr"> == Client support == </div> [[File:Videoonwikipedia.ogv|300px|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Example video player</span>]] [[File:example.ogg|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Example audio player</span>]] [[File:example.ogg|300px|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Wider audio player, showing progress bar</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">The player works on most modern browsers (see [[Special:MyLanguage/Compatibility#Browser support matrix|MediaWiki's support matrix]]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Mobile support is spotty, especially on iOS.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> TimedMediaHandler includes a [[Special:MyLanguage/Extension:TimedMediaHandler/ogv.js|JavaScript compatibility shim]] for Ogg audio/video that works in Safari, Internet Explorer 10/11, and Microsoft Edge browsers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Third-party users of MediaWiki may also wish to manually enable MP4 H.264/AAC support for native video and audio playback in Safari/IE/Edge, but when using these formats you may need a patent license from MPEG-LA for internet broadcasting. </div> == Installation == <span lang="en" dir="ltr" class="mw-content-ltr">You will want a recent version of ''ffmpeg'' in order to support encoding to WebM (with the latest version of VP9).</span> {{ExtensionInstall |TimedMediaHandler |db-update=yes |composer=yes |oldreg= wfLoadExtension( 'TimedMediaHandler' ); $wgFFmpegLocation = '/usr/bin/ffmpeg'; // Häufigster ffmpeg-Pfad auf Linux |custom-steps= * [[#Configuration|Konfiguriere nach Bedarf.]] * <span lang="en" dir="ltr" class="mw-content-ltr">You may need to increase the allowed memory in {{ll|Manual:$wgMaxShellMemory|$wgMaxShellMemory}}.</span><!-- What is the recommended number?? --> }} <div lang="en" dir="ltr" class="mw-content-ltr"> The extension will automatically add supported file types (except for mp4) to {{ll|Manual:$wgFileExtensions|$wgFileExtensions}}, so you do not need to manually add video file types. </div> {{Note|1= <div lang="en" dir="ltr" class="mw-content-ltr"> After downloading this extension, please note that it requires {{ll|Composer}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> So, after installation change to the directory containing the extension e.g. "../extensions/TimedMediaHandler/" and run <code>composer install --no-dev</code>, or when updating: <code>composer update --no-dev</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Alternatively as well as preferably add the line <code>"extensions/TimedMediaHandler/composer.json"</code> to the "composer.local.json" file in the root directory of your wiki like e.g. </div> <syntaxhighlight lang="json"> { "extra": { "merge-plugin": { "include": [ "extensions/TimedMediaHandler/composer.json" ] } } } </syntaxhighlight> }} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Comparison of Wikipedia media encoding options=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of 2018, Wikimedia sites use VP9. </div> Sortiert nach Bandbreitenstufe: {| class="wikitable" ! Bitrate ! Mbit/s ! WebM VP8 ! WebM VP9 |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Super Low</span> | 0.08 | | 160p |- ! Sehr niedrig | 0.16 | 160p | 240p |- ! Niedrig | 0.25 | 240p | 360p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Moderate</span> | 0.5 | 360p | 480p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Medium</span> | 1.0 | 480p | 720p |- ! Hoch | 2.0 | 720p | 1080p |- ! Sehr hoch | 4.0 | 1080p | 1440p |- ! <span lang="en" dir="ltr" class="mw-content-ltr">Super high</span> | 8.0 | | 2160p |} Detaillierte Optionen: {| class="wikitable" |- style="text-align:center;" ! colspan="2" style="text-align:{{dir|{{pagelang}}|right|left}}"| Name !! 160P !240P!! 360P !! 480P !! 720P !! 1080P !160P !240P!! 360P !! 480P !! 720P !! 1080P !1440P!! 2160P |- style="text-align:center" | colspan="2" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Container''' || colspan="14" | WebM |- style="text-align:center" | rowspan="4" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Video''' || style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Codierung''' || colspan="6" | VP8 | colspan="8" |VP9 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Maximale Breite''' (Pixel) || 288 |426|| 640 || 854 || 1280 || 1920 |288 |426|| 640 || 854 || 1280 || 1920 |2560|| 4096 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Maximale Höhe''' (Pixel) || 160 |240|| 360 || 480 || 720 || 1080 |160 |240|| 360 || 480 || 720 || 1080 |1440|| 2160 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}"| '''Bitrate''' (Mbit/s) || 0.16 |0.25|| 0.5 || 1.0 || 2.0 || 4.0 |0.08 |0.16|| 0.25 || 0.5 || 1.0 || 2.0 |4.0|| 8.0 |- style="text-align:center" | rowspan="4" style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Audio''' || style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Codierung''' | colspan="6" |Vorbis | colspan="8" |Opus |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Kanäle''' | colspan="6" |2&nbsp;(stereo) | colspan="8" |(pass-through) |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | <span lang="en" dir="ltr" class="mw-content-ltr">'''Sampling rate'''</span> (Hz) | colspan="6" |44100 | colspan="8" |48000 |- style="text-align:center" | style="background:#f2f2f2; text-align:{{dir|{{pagelang}}|right|left}}" | '''Qualität''' || - ||| 1 || 2 || 3 || - | colspan="8" |(default) |} {{anchor|Configuration}} === Konfiguration === {{update}} {{Note|1='''<span lang="en" dir="ltr" class="mw-content-ltr">This section is out of date -- please update me</span>'''|2=reminder}} <div lang="en" dir="ltr" class="mw-content-ltr"> Here are some configuration variables which may be useful: </div> <syntaxhighlight lang="php"> // The minimum size for an embed video player (smaller than this size uses a pop-up player). $wgMinimumVideoPlayerSize = 200; // If transcoding is enabled for this wiki (if disabled, no transcode jobs are added and no transcode status is displayed). // Note if remote embedding an asset we will still check if the remote repo has transcoding enabled and associated flavors // for that media embed. $wgEnableTranscode = true; // The total amout of time a transcoding shell command can take: $wgTranscodeBackgroundTimeLimit = 3600 * 8; // Maximum amount of virtual memory available to transcoding processes in KB $wgTranscodeBackgroundMemoryLimit = 2 * 1024 * 1024; // 2GB avconv, ffmpeg2theora mmap resources so virtual memory needs to be high enough // Maximum file size transcoding processes can create, in KB $wgTranscodeBackgroundSizeLimit = 3 * 1024 * 1024; // 3GB // Number of threads to use in avconv for transcoding $wgFFmpegThreads = 1; // The NS for TimedText (registered on MediaWiki.org) // https://www.mediawiki.org/wiki/Extension_namespace_registration // Note commons pre-dates TimedMediaHandler and should set $wgTimedTextNS = 102 in LocalSettings.php $wgTimedTextNS = 710; // Set TimedText namespace for ForeignDBViaLBRepo on a per wikiID basis // $wgTimedTextForeignNamespaces = array( 'commonswiki' => 102 ); $wgTimedTextForeignNamespaces = array(); /** * Default enabled transcodes * * -If set to empty array, no derivatives will be created * -Derivative keys encode settings are defined in WebVideoTranscode.php * * -These transcodes are *in addition to* the source file. * -Only derivatives with smaller width than the source asset size will be created * -Regardless of source size at least one WebM and Ogg source will be created from the $wgEnabledTranscodeSet * -Derivative jobs are added to the MediaWiki JobQueue the first time the asset is uploaded * -Derivative should be listed min to max */ // Starting from 1.31 // All valid string values are listed in the extension's extension.json file $wgEnabledTranscodeSet = [ '160p.webm' => true, '240p.webm' => true, '360p.webm' => true, '480p.webm' => true, '720p.webm' => true, '1080p.webm' => true, ]; $wgEnabledAudioTranscodeSet = [ 'ogg' => true, // ogg+vorbis 'opus' => false, // ogg+opus 'mp3' => true, // raw mp3 'm4a' => false, // mp4+aac (mp4a.40.5) ]; // If mp3 source assets can be ingested: $wgTmhEnableMp3Uploads = true; // If mp4 source assets can be ingested: $wgTmhEnableMp4Uploads = false; // If you use ffmpeg 2 can be set it to true $wgUseFFmpeg2 = false; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> For transcoding, make sure you have {{phpi|$wgMaxShellMemory}}, {{phpi|$wgMaxShellTime}}, {{phpi|$wgMaxShellFileSize}} are large enough to allow encoding jobs to run and save output. Default values are most likely too low. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Running transcode jobs=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Because transcode jobs are resource intensive they will not run as part of normal job queue (see {{PhabT|T29336}}) Instead they must be requested by the <code>--type</code> argument: </div> <syntaxhighlight lang="php"> php maintenance/runJobs.php --type webVideoTranscode </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">If running this command causes it to hang forever, you may need to set {{phpi|$wgTranscodeBackgroundTimeLimit {{=}} 0;}} in LocalSettings.php.</span> Siehe {{phabricator|T206957}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ===Encoding nodes=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To be able to transcode many videos you might want to run multiple encoding nodes that connect to the master db and access your file store directly. You will need to install ffmpeg. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Minimal install under Debian and Ubuntu === </div> <syntaxhighlight lang="bash"> apt install ffmpeg </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">Plus, add this to your {{ll|Manual:LocalSettings.php|LocalSettings.php}} (tested for [https://devuan.org/os/debian-fork/ascii-stable-announce-060818 Devuan ASCII] {{Webarchive|url=https://web.archive.org/web/20180923085518/https://devuan.org/os/debian-fork/ascii-stable-announce-060818 |date=2018-09-23 }} only):</span> <syntaxhighlight lang="php"> $wgFFmpegLocation = '/usr/bin/ffmpeg'; </syntaxhighlight> == Fehlerbehebung == {{Note|1='''Dieser Abschnitt muss erweitert werden'''|2=reminder}} ;{{anchor|wgMaxShellMemory}}"<code>ffmpeg</code> – <span lang="en" dir="ltr" class="mw-content-ltr">failed to map segment from shared object</span>" :<span lang="en" dir="ltr" class="mw-content-ltr">You need to increase the allowed memory in {{ll|Manual:$wgMaxShellMemory|$wgMaxShellMemory}}.</span><!-- What is the recommended number?? --> ;"Klasse 'getID3' nicht gefunden" :<span lang="en" dir="ltr" class="mw-content-ltr">You need to install the extension's PHP dependencies using Composer, see the Installation section above.</span> ;"<span lang="en" dir="ltr" class="mw-content-ltr">Unrecognized option 'max_muxing_queue_size'</span>" :<span lang="en" dir="ltr" class="mw-content-ltr">You may be using ffmpeg 2.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need add <source lang=php inline>$wgUseFFmpeg2 = true;</source> to your <code>LocalSettings.php</code>.</span> {{OnWikimedia}} {{Used by|canasta=1|fandom=1|miraheze=1}} [[Category:Media handling extensions{{#translation:}}]] [[Category:Video player extensions{{#translation:}}]] [[Category:Audio player extensions{{#translation:}}]] l46p8wla7z853aqgpxoqmc8mhzb8qmi Extension:Tab Override/de 102 1438077 5387037 4856725 2022-07-28T19:56:35Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki <languages /> {{Extension|templatemode= |status = unmaintained |type1 = Interface |type2 = skin |hook1 = BeforePageDisplay |username = mtinsley |author = Bill Bryant, [[User:Mtinsley|Mathew Tinsley]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows you to use the tab key as you normally would in a text-editor</span> |version = 2.0.1 |update = 2010-04-12 |mediawiki = 1.7.0 |license = GPL |download = [https://web.archive.org/web/20130525071721/http://tinsology.net/wp-content/uploads/2010/04/tab-override.zip Erweiterung herunterladen] |readme = [https://web.archive.org/web/20150416114134/http://tinsology.net/plugins/tab-override/ ReadMe] |changelog = [https://web.archive.org/web/20150416114134/http://tinsology.net/plugins/tab-override/ Changelog] }} <div lang="en" dir="ltr" class="mw-content-ltr"> ==What can this extension do?== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Tab Override allows you to use the tab key as you normally would in a text editor or IDE.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In other words, pressing the tab key inserts a tab character rather than removing focus from the text area.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This makes writing source code much easier.</span> == Verwendung == <span lang="en" dir="ltr" class="mw-content-ltr">No configuration required.</span> <span lang="en" dir="ltr" class="mw-content-ltr">After it is installed you can test it by editing a page and pressing the tab key in the textarea.</span> == Installation == <div lang="en" dir="ltr" class="mw-content-ltr"> To install this extension, add the following to {{ll|Manual:LocalSettings.php|LocalSettings.php}}: </div> <syntaxhighlight lang="php"> require_once("$IP/extensions/tab-override/tab-override.php"); </syntaxhighlight> apxwnqyebyu0gzdy6f8t2blc4emkih0 5387039 5387037 2022-07-28T19:56:40Z ThisCarthing 17456337 Created page with "== Was kann diese Erweiterung machen? ==" wikitext text/x-wiki <languages /> {{Extension|templatemode= |status = unmaintained |type1 = Interface |type2 = skin |hook1 = BeforePageDisplay |username = mtinsley |author = Bill Bryant, [[User:Mtinsley|Mathew Tinsley]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows you to use the tab key as you normally would in a text-editor</span> |version = 2.0.1 |update = 2010-04-12 |mediawiki = 1.7.0 |license = GPL |download = [https://web.archive.org/web/20130525071721/http://tinsology.net/wp-content/uploads/2010/04/tab-override.zip Erweiterung herunterladen] |readme = [https://web.archive.org/web/20150416114134/http://tinsology.net/plugins/tab-override/ ReadMe] |changelog = [https://web.archive.org/web/20150416114134/http://tinsology.net/plugins/tab-override/ Changelog] }} == Was kann diese Erweiterung machen? == <span lang="en" dir="ltr" class="mw-content-ltr">Tab Override allows you to use the tab key as you normally would in a text editor or IDE.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In other words, pressing the tab key inserts a tab character rather than removing focus from the text area.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This makes writing source code much easier.</span> == Verwendung == <span lang="en" dir="ltr" class="mw-content-ltr">No configuration required.</span> <span lang="en" dir="ltr" class="mw-content-ltr">After it is installed you can test it by editing a page and pressing the tab key in the textarea.</span> == Installation == <div lang="en" dir="ltr" class="mw-content-ltr"> To install this extension, add the following to {{ll|Manual:LocalSettings.php|LocalSettings.php}}: </div> <syntaxhighlight lang="php"> require_once("$IP/extensions/tab-override/tab-override.php"); </syntaxhighlight> jz6hjp9uzm57anfsq81uqawu57imch0 5387041 5387039 2022-07-28T19:57:07Z ThisCarthing 17456337 Created page with "Keine Konfiguration notwendig." wikitext text/x-wiki <languages /> {{Extension|templatemode= |status = unmaintained |type1 = Interface |type2 = skin |hook1 = BeforePageDisplay |username = mtinsley |author = Bill Bryant, [[User:Mtinsley|Mathew Tinsley]] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows you to use the tab key as you normally would in a text-editor</span> |version = 2.0.1 |update = 2010-04-12 |mediawiki = 1.7.0 |license = GPL |download = [https://web.archive.org/web/20130525071721/http://tinsology.net/wp-content/uploads/2010/04/tab-override.zip Erweiterung herunterladen] |readme = [https://web.archive.org/web/20150416114134/http://tinsology.net/plugins/tab-override/ ReadMe] |changelog = [https://web.archive.org/web/20150416114134/http://tinsology.net/plugins/tab-override/ Changelog] }} == Was kann diese Erweiterung machen? == <span lang="en" dir="ltr" class="mw-content-ltr">Tab Override allows you to use the tab key as you normally would in a text editor or IDE.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In other words, pressing the tab key inserts a tab character rather than removing focus from the text area.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This makes writing source code much easier.</span> == Verwendung == Keine Konfiguration notwendig. <span lang="en" dir="ltr" class="mw-content-ltr">After it is installed you can test it by editing a page and pressing the tab key in the textarea.</span> == Installation == <div lang="en" dir="ltr" class="mw-content-ltr"> To install this extension, add the following to {{ll|Manual:LocalSettings.php|LocalSettings.php}}: </div> <syntaxhighlight lang="php"> require_once("$IP/extensions/tab-override/tab-override.php"); </syntaxhighlight> k4qd9k1k33m0mwvyygx2q6q5zn1okch Extension:SupybotNotify/de 102 1438080 5386875 4856729 2022-07-28T19:33:12Z ThisCarthing 17456337 Created page with "==Code==" wikitext text/x-wiki <languages /> {{Extension code in wiki}} {{Extension |type = hook |status = unmaintained |hook1 = RecentChange_save |username = ianweller |author = Ian Weller |description = <span lang="en" dir="ltr" class="mw-content-ltr">Sends recent changes through a Supybot with the Notify plugin to an IRC channel</span> |version = 1.0 |update = 2011-05-28 |mediawiki = 1.14+ |license = GPL-2.0+ |download = {{ll|Extension:SupybotNotify/Version 1.0}} }} <div lang="en" dir="ltr" class="mw-content-ltr"> ==What can this extension do?== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This extension sends recent changes through a [http://www.supybot.org/ Supybot] with the [http://git.fedorahosted.org/git/?p=supybot-notify.git Notify plugin] ([https://fedorahosted.org/releases/s/u/supybot-notify/ download]) to IRC channels. </div> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> Install, configure and forget. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Download instructions== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please select the version you want [[#Code|below]] and copy and paste the resulting code in {{phpi|$IP/extensions/SupybotNotify.php}}. </div> {{$IP}} == Installation == <div lang="en" dir="ltr" class="mw-content-ltr"> To install this extension, add the following to {{ll|Manual:LocalSettings.php|LocalSettings.php}}: </div> <syntaxhighlight lang="php"> // Change this if Notify isn't running on localhost //$wgSupybotNotifyHost = '127.0.0.1'; // Change this if Notify isn't running on port 5050 //$wgSupybotNotifyPort = 5050; // Add channels like so //$wgSupybotNotifyChannels[] = '#channel name'; require_once("$IP/extensions/SupybotNotify.php"); </syntaxhighlight> {{anchor|Code}} ==Code== * {{ll|Extension:SupybotNotify/Version 1.0}} decjsgg2926mubbozu9dfn6ubmkgunj Extension:SendGrid/de 102 1438111 5386923 5261647 2022-07-28T19:44:02Z ThisCarthing 17456337 Created page with "== Teste deine Einstellungen ==" wikitext text/x-wiki <languages /> {{Extension |status = stable |download = {{WikimediaDownload|SendGrid}} |description = Ermöglicht MediaWiki, die SendGrid-API für die E-Mail-Verteilung zu verwenden. |author = Derick Alangi |username = X-Savitar |version = 3.0 |compatibility policy = rel |mediawiki = 1.34+ |php = 5.6+ |composer = sendgrid/sendgrid |type1 = notify |readme = {{git file|project=mediawiki/extensions/SendGrid|branch=master|file=README.md|text=README}} |phabricator = MediaWiki-extensions-SendGrid }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''SendGrid''' extension enables MediaWiki to send emails through SendGrid's API service. </div> == Installation == {{ExtensionInstall |registration=yes |repo-name=SendGrid }} {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">You will have to run <code>composer update</code> in <code>extensions/SendGrid/</code> folder so that composer can pick up and install the required SendGrid dependencies for the extension to run smoothly.</span>}} == Konfiguration == <span lang="en" dir="ltr" class="mw-content-ltr">You need to have an account on <code>www.sendgrid.com</code> and a valid API key in order to successfully send emails via SendGrid using this extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Instructions to generate an API key can be found in the [https://sendgrid.com/docs/User_Guide/Settings/api_keys.html SendGrid API key documentation].</span> {{warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Security Warning''': Do not put your SendGrid API key directly in the <code>SendGrid/extension.json</code> as this will be a vulnerability allowing someone else to be able to use your account/key to send emails or perform other bad stuff.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Configuration on MediaWiki-Vagrant === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once your MediaWiki-Vagrant environment is setup correctly, do the following to get SendGrid to work properly with your new environment; </div> * <span lang="en" dir="ltr" class="mw-content-ltr">On your terminal, run: <code>vagrant roles enable sendgrid</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> In your SendGrid account settings, generate an API key. With a valid API Key, configure your API key in {{ll|Manual:LocalSettings.php|LocalSettings.php}}: </div> <syntaxhighlight lang="php"> $wgSendGridAPIKey = "YOUR_API_KEY_HERE"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> If you're using this extension with SMTP, make sure to configure your SMTP like below: </div> <syntaxhighlight lang="php"> $wgSMTP = [ 'host'=> "smtp.yoursmtp.org", 'IDHost' => "yourhost.org", 'port' => 587, 'auth' => true, 'username' => "yourSMTPusername", 'password' => "yourSMTPpassword" ]; </syntaxhighlight> == Teste deine Einstellungen == <div lang="en" dir="ltr" class="mw-content-ltr"> Go to <code>Special:EmailUser</code> and send an email to your own address to verify that the extension is working. You'll receive an email from the address you inputed and check to see if it's sent via the SendGrid API (for example; <code>Your Name example@domain.com ''via'' sendgrid.net </code>). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Usage by production wikis == </div> <span lang="en" dir="ltr" class="mw-content-ltr">This extension is used by wikis listed here:</span> https://wikiapiary.com/wiki/Extension:SendGrid (<span lang="en" dir="ltr" class="mw-content-ltr">via WikiApiary</span>) 7a1r5v8ucz9m7eblr5scn7zuivr0zln Extension:RottenLinks/de 102 1438135 5386925 5383345 2022-07-28T19:44:19Z ThisCarthing 17456337 Created page with "Beispiel:" wikitext text/x-wiki <languages /> {{Extension |image = Ext-RottenLinks (2019).png |status = stable |hook1 = LoadExtensionSchemaUpdates |mediawiki = 1.35.3+ |php=7.2+ |needs-updatephp = Yes |version = continuous updates |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides the Special page Special:RottenLinks.</span> |maintainer = Miraheze system administrators |download = {{GithubDownload|Miraheze|RottenLinks|translatewiki=0}} |readme = [https://github.com/miraheze/RottenLinks/blob/master/README.md README] |changelog = [https://github.com/miraheze/RottenLinks/blob/master/CHANGELOG CHANGELOG] |translate = |rights = |parameters=<nowiki/> * $wgRottenLinksBadCodes * $wgRottenLinksCurlTimeout * $wgRottenLinksExcludeProtocols * $wgRottenLinksExcludeWebsites * $wgRottenLinksExternalLinkTarget |license = GPL-3.0-or-later |phabricator = |pagedrive1 = true }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''RottenLinks''' extension provides the special page "Special:RottenLinks", which shows a table of all external links on your wiki pages, and tells you their status. </div> <span lang="en" dir="ltr" class="mw-content-ltr">For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator].</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [https://phabricator.miraheze.org/tag/rottenlinks/ here for the workboard].</span> == Installation == {{ExtensionInstall |download-link=[https://github.com/miraheze/RottenLinks Erweiterung herunterladen] |db-update=true |registration=required |custom-steps=* [[#Configuration|Konfiguriere nach Bedarf.]] * <span lang="en" dir="ltr" class="mw-content-ltr">Run the following script to populate the special page "Special:RottenLinks":</span><syntaxhighlight lang="bash">php extensions/RottenLinks/maintenance/updateExternalLinks.php</syntaxhighlight> }} {{anchor|Configuration}} == Konfiguration == ; <code>$wgRottenLinksBadCodes</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Holds a list of HTTP codes that are considered bad.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to {{phpi|[ "0", "400", "401", "403", "404", "405", "502", "503", "504" ]}}.</span> ; <code>$wgRottenLinksCurlTimeout</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Sets the timeout for cURL in seconds.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to <code>30</code>.</span> ; <code>$wgRottenLinksHTTPProxy </code> : <span lang="en" dir="ltr" class="mw-content-ltr">Sets a [[w:Proxy server#Web proxy servers|proxy]] to use for requests.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to {{phpi|""}} (use no proxy).</span> Beispiel: <syntaxhighlight lang=php inline>$wgRottenLinksHTTPProxy = "http://username:password@proxy.example.com:8080";</syntaxhighlight> ; <code>$wgRottenLinksExcludeProtocols</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Holds a list of protocols that should not be checked for validity.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to {{phpi|[ "tel", "mailto" ]}}.</span> ; <code>$wgRottenLinksExternalLinkTarget</code> : <span lang="en" dir="ltr" class="mw-content-ltr">Sets the external link target (<code>_self</code> for the current tab or <code>_blank</code> for new tab).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to <code>_self</code>.</span> ; <code>$wgRottenLinksExcludeWebsites </code> : <span lang="en" dir="ltr" class="mw-content-ltr">List of websites to blacklist checking of response codes for.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to <code>false</code>.</span> Omit the protocol, e.g. use <syntaxhighlight lang=php inline>$wgRottenLinksExcludeWebsites = [ "www.example.com" ];</syntaxhighlight> == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> Run the "updateExternalLinks.php" script provided with the extension every time you would like to create or update the list of rotten links shown on special page "Special:RottenLinks". </div> {{Used by|canasta=1|miraheze=1}} {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Wiki farm extensions]] cbhywjxazlwp2bhubatj04kd7ri5aid Extension:PollNY/de 102 1438181 5386958 5238373 2022-07-28T19:48:00Z ThisCarthing 17456337 Created page with "Benötigt die $1-Erweiterung." wikitext text/x-wiki <languages/> {{Extension |status = stable |image = |type = special |description = <span lang="en" dir="ltr" class="mw-content-ltr">Advanced polling system that uses special pages and allows embedding polls to wiki pages</span> |author = Aaron Wright, David Pean, {{u|Jack Phoenix}} |version = 3.6.0 |update = 2020-01-02 |mediawiki = {{MW lts branch number}}+ |download = {{WikimediaDownload}} |readme = |changelog = |example = |phabricator = PollNY }} <div lang="en" dir="ltr" class="mw-content-ltr"> The '''PollNY''' extension defines a new namespace for polls (NS_POLL, the namespace number is 300 by default) and 6 new special pages for poll creation/administration. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Polls can be embedded on normal wiki pages with the {{tag|pollembed|open}} tag.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Syntax is:</span> <code class="mw-highlight">&lt;{{#tag:span|pollembed|class=nt}} {{attr|title|2="<span lang="en" dir="ltr" class="mw-content-ltr">Name of the poll</span>"}} /&gt;</code> <div lang="en" dir="ltr" class="mw-content-ltr"> Special:AdminPoll can be used by users with 'polladmin' rights to view all polls and administer them, Special:CreatePoll is used to create new polls, Special:RandomPoll takes you to a randomly chosen poll, Special:UpdatePoll is like action=edit for polls and Special:ViewPoll can be used by all users to view available polls. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These new special pages (except for Special:UpdatePoll) will show up on [[Special:SpecialPages]] in the "Polls" section. </div> == Abhängigkeiten == * {{ll|Extension:SocialProfile}} <div lang="en" dir="ltr" class="mw-content-ltr"> * New database tables: poll_choice, poll_question and poll_user_vote </div> == Installation == {{ExtensionInstall |db-update = true |registration=required }} == Benutzerrechte == <span lang="en" dir="ltr" class="mw-content-ltr">This extension adds one new user right, <code>polladmin</code>, which allows accessing Special:AdminPoll to administer polls created through Special:CreatePoll.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default sysops have this user right.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==User points== </div> * {{phpi|$wgUserStatsPointValues['poll_vote']}} &mdash; <span lang="en" dir="ltr" class="mw-content-ltr">set this to something to give out points for answering existing polls.</span> == Parameter == * {{phpi|$wgPollDisplay['comments']}} &mdash; <span lang="en" dir="ltr" class="mw-content-ltr">whether to display comments on poll pages or not.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to <code>false</code>.</span> Benötigt die {{ll|Extension:Comments|nsp=0}}-Erweiterung. * {{phpi|$wgCreatePollThresholds}} &mdash; <span lang="en" dir="ltr" class="mw-content-ltr">for example <code>'edits' => 5</code> if you want to require users to have at least 5 edits before they can create new polls.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Defaults to an empty array (no restrictions).</span> {{Social tools}} [[Category:Poll extensions{{#translation:}}]] gt5bv6qovtc8qk26cnzh7zebtss5vhd Extension:OfflineExtension/de 102 1438224 5386883 4856099 2022-07-28T19:35:09Z ThisCarthing 17456337 Created page with "== Funktionen ==" wikitext text/x-wiki <languages /> {{Extension|templatemode = |status = unmaintained |type1 = <!-- implementation type, see [[Template:Extension]] for details --> |hook1 = BeforePageDisplay |username = <!-- optional, but strongly recommended --> |author = Srijan Agarwal {{int|and}}{{int|word-separator}}Gianluca Rigoletti |description = <span lang="en" dir="ltr" class="mw-content-ltr">Extension for adding offline support to Wiki Editor</span> |image = |imagesize = 220px |version = 0.1.0 |update = |mediawiki = 1.25+ |php = |needs-updatephp = |composer = |table1 = |table2 = |license = GPL-2.0+ |changelog = |example = |namespace = |parameters = |download = {{GithubDownload|Srijancse|OfflineExtension}} |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |phabricator = }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''OfflineExtension''' is an extension for [[:en:WikiToLearn|WikiToLearn]] that will add offline support to the current Wiki Editor. </div> == Funktionen == <span lang="en" dir="ltr" class="mw-content-ltr">This extension notifies the user and their internet connectivity status.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If submitted while offline, it will parse Wikitext to HTML and then renders it.</span> == Installation == <div lang="en" dir="ltr" class="mw-content-ltr"> * [https://github.com/Srijancse/OfflineExtension Download] and place the file(s) in a directory called <code>OfflineExtension</code> in your <code>extensions/</code> folder. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Add the following code at the bottom of your <code>LocalSettings.php</code>: </div> <syntaxhighlight lang="php"> require_once "$IP/extensions/OfflineExtension/OfflineExtension.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> * Navigate to Special:Version on your wiki to verify that the extension is successfully installed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == WikiText tags supported == </div> <span lang="en" dir="ltr" class="mw-content-ltr">Wikitext is written in a lightweight markup language with specific syntax rules.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The tags supported by the Offline Extension can be found here:</span> https://github.com/Srijancse/OfflineExtension/wiki <div lang="en" dir="ltr" class="mw-content-ltr"> == Known issues == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Parsing WikiTables to HTML hasn't been added to the parser yet. It is under development. </div> 3im5wfr7u77jse4dy50vppg2d9yay8m 5386885 5386883 2022-07-28T19:35:15Z ThisCarthing 17456337 Created page with "== Bekannte Probleme ==" wikitext text/x-wiki <languages /> {{Extension|templatemode = |status = unmaintained |type1 = <!-- implementation type, see [[Template:Extension]] for details --> |hook1 = BeforePageDisplay |username = <!-- optional, but strongly recommended --> |author = Srijan Agarwal {{int|and}}{{int|word-separator}}Gianluca Rigoletti |description = <span lang="en" dir="ltr" class="mw-content-ltr">Extension for adding offline support to Wiki Editor</span> |image = |imagesize = 220px |version = 0.1.0 |update = |mediawiki = 1.25+ |php = |needs-updatephp = |composer = |table1 = |table2 = |license = GPL-2.0+ |changelog = |example = |namespace = |parameters = |download = {{GithubDownload|Srijancse|OfflineExtension}} |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |phabricator = }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''OfflineExtension''' is an extension for [[:en:WikiToLearn|WikiToLearn]] that will add offline support to the current Wiki Editor. </div> == Funktionen == <span lang="en" dir="ltr" class="mw-content-ltr">This extension notifies the user and their internet connectivity status.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If submitted while offline, it will parse Wikitext to HTML and then renders it.</span> == Installation == <div lang="en" dir="ltr" class="mw-content-ltr"> * [https://github.com/Srijancse/OfflineExtension Download] and place the file(s) in a directory called <code>OfflineExtension</code> in your <code>extensions/</code> folder. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Add the following code at the bottom of your <code>LocalSettings.php</code>: </div> <syntaxhighlight lang="php"> require_once "$IP/extensions/OfflineExtension/OfflineExtension.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> * Navigate to Special:Version on your wiki to verify that the extension is successfully installed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == WikiText tags supported == </div> <span lang="en" dir="ltr" class="mw-content-ltr">Wikitext is written in a lightweight markup language with specific syntax rules.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The tags supported by the Offline Extension can be found here:</span> https://github.com/Srijancse/OfflineExtension/wiki == Bekannte Probleme == <div lang="en" dir="ltr" class="mw-content-ltr"> * Parsing WikiTables to HTML hasn't been added to the parser yet. It is under development. </div> g97pmsjyit7lkmfmobfcwegj626qegv Extension:3DAlloy/de 102 1438600 5386913 5379398 2022-07-28T19:42:42Z ThisCarthing 17456337 Created page with "Ändere den $1-Parameter:" wikitext text/x-wiki <languages /> {{Extension |author = [[User:Martynov Maxim|Dolfinus]] |license = MIT |type1 = parser function |type2 = tag |type3 = contenthandler |type4 = link |image = 3DAlloy.png |status = stable |mediawiki = 1.25+ |download={{GithubDownload|dolfinus|3DAlloy|mastertarball=1}} (for MW 1.33 and below use mw-1.33 branch) |needs-updatephp = no |version = 1.6 |example = <span lang="en" dir="ltr" class="mw-content-ltr">[https://en.crystalls.info/File:Cube.json Example of 3D Viewer at file page]</span> |readme = [https://github.com/dolfinus/3DAlloy/master/README.md README] |update = 2022-01-30 |description = Fügt Unterstützung für die Anzeige von 3D-Dateien in deinem MediaWiki hinzu |parameters = $wg3DAlloy |hook1=ParserMakeImageParams |hook2=ParserFirstCallInit |hook3=ImageBeforeProduceHTML |hook4=ImageOpenShowImageInlineBefore |hook5=BeforePageDisplay |hook6=BeforePageDisplayMobile |tags={{tag|3d|open}} }} == Beschreibung == <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki extension which allows to add 3D models viewer to site pages. Based on [https://github.com/mrdoob/three.js/ THREE.js], renders image with CanvasRenderer. There you can see [https://en.crystalls.info/Template:Cube example 3D model page]. </div> == Unterstützte Dateierweiterungen == THREE.js-Modellformat: * .json * .3djson * .3dj * .three THREE.js-Modellpuffer-Geometrieformat: * .buff * .buffjson OBJ-Dateiformat: * .obj STL-(Binär-)Dateiformat: * .stl * .stlb == Installation == {{ExtensionInstall |registration=required |download-link=[https://github.com/dolfinus/3DAlloy/archive/master.zip Erweiterung herunterladen] |custom-steps= * Ändere den {{ll|Manual:$wgFileExtensions|$wgFileExtensions}}-Parameter: <syntaxhighlight lang="php"> $wgFileExtensions = array_merge( $wgFileExtensions, array( 'json', '3dj', '3djson', 'three', 'buff', 'buffjson', 'obj', 'stl', 'stlb' ) ); </syntaxhighlight> }} == Verwendung == <div lang="en" dir="ltr" class="mw-content-ltr"> === As Image Handler === </div> <pre class="wiki"> [[File:Model.json|300x300px|color=,opacity=,...]] </pre> === Als Parser-Funktion === <pre class="wiki"> {{#3d:Model.json}} {{#3d:Model.json|width}} {{#3d:Model.json|width|height}} ... {{#3d:Model.json|width|height|color|opacity|zoom|pan|norotate|scale|z|style|class}} </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of uploaded filename you can use an url for file located in external site. </div> === Als Parser-Tag === <syntaxhighlight lang=html> <3d file="Model.json" width="" height="" ... ></3d> </syntaxhighlight> or <syntaxhighlight lang=html> <3d width="" height="" ... >Model.json</3d> </syntaxhighlight> Du kannst auch url statt eines kurzen Dateinamens verwenden. == Parameter == {|class="wikitable" ! Name ! Beschreibung !align="right"| Default value |- | width | Canvasbreite in Pixel |align="right"| 300 |- | height | Canvashöhe in Pixel |align="right"| 300 |- | color | Modell-RGB-Farbe in hex |align="right"| 0xff00ff |- | opacity | Modelldeckkraft als Dezimalzahl zwischen 0...1 |align="right"| 0.8 |- | zoom | <span lang="en" dir="ltr" class="mw-content-ltr">If true or 1, canvas can be zoomed</span> |align="right"| false |- | pan | <span lang="en" dir="ltr" class="mw-content-ltr">If true or 1, canvas can be panned</span> |align="right"| false |- | norotate | <span lang="en" dir="ltr" class="mw-content-ltr">If true or 1, model does not rotate</span> |align="right"| false |- | scale | <span lang="en" dir="ltr" class="mw-content-ltr">Model scale as decimal between 0...1</span> |align="right"| 1 |- | z | Modell-Z-Koordinate |align="right"| 75 |- | style | <span lang="en" dir="ltr" class="mw-content-ltr">Additional canvas CSS style</span> |align="right"| |- | class | Weitere Canvas-HTML-Klasse |align="right"| |} <div lang="en" dir="ltr" class="mw-content-ltr"> Width and height can be set to ''0'' value, so size of viewer will be set according to user screen dimensions. </div> === Konfigurieren === <div lang="en" dir="ltr" class="mw-content-ltr"> All default values can be changed in your {{ll|Manual:LocalSettings.php|LocalSettings.php}} file: </div> <syntaxhighlight lang="php"> $wg3DAlloy["width"] = 500; $wg3DAlloy["height"] = 400; ... $wg3DAlloy["class"] = 'someclass'; </syntaxhighlight> == Steuerung und Hotkeys == {|class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Action</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Controls</span> |- | Kameradrehung | <span lang="en" dir="ltr" class="mw-content-ltr">Swipe, left mouse key hold and move</span> |- | Kamerazoom (falls der Zoom aktiviert ist) | <span lang="en" dir="ltr" class="mw-content-ltr">Mouse wheel, hold wheel and move, pinch</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Camera pan</span> <span lang="en" dir="ltr" class="mw-content-ltr">(if pan enabled)</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Right key hold and move</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Model rotate</span> | ←↑→↓-Tasten |- | <span lang="en" dir="ltr" class="mw-content-ltr">Model rotation reset</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Home key</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Model rotation play/pause</span> | Doppelklick, doppelt tippen |- | <span lang="en" dir="ltr" class="mw-content-ltr">Model rotation play/pause all models at page</span> | Enter-, Leerzeichen-Tasten |- | <span lang="en" dir="ltr" class="mw-content-ltr">Model rotation speed</span> | - und +-Tasten |} <div lang="en" dir="ltr" class="mw-content-ltr"> Hotkeys automatically disables while you edit or submit wiki page. </div> [[Category:3D_extensions{{#translation:}}]] c9sgsuqh3u2fmfj2hpab6vtmmk7jxud Extension:Chartie/de 102 1438624 5386870 5373364 2022-07-28T19:32:51Z ThisCarthing 17456337 Created page with "== Installieren ==" wikitext text/x-wiki <languages/> {{Extension |author = [[User:Martynov Maxim|Dolfinus]] |license=MIT |type1 = parser function |type2 = tag |type3 = |type4 = link |image = Chartie_extension.png |status = stable |mediawiki = 1.25+ |download={{GithubDownload|dolfinus|Chartie|mastertarball=1}} |needs-updatephp = no |version = 1.0 |example = <span lang="en" dir="ltr" class="mw-content-ltr">[https://en.crystalls.info/Solubility_graph Example of line chart to wiki page]</span> |readme = [https://github.com/dolfinus/Chartie/master/README.md README] |update = 2017-02-13 |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds support of line charts at your MediaWiki</span> |parameters = $wgChartie |hook1=ParserMakeImageParams |hook2=ParserFirstCallInit |hook3=ImageBeforeProduceHTML |hook4=ImageOpenShowImageInlineBefore |hook5=BeforePageDisplay |hook6=BeforePageDisplayMobile |tags={{tag|chart|open}} }} == Beschreibung == <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki extension which allows to add simple line charts to site pages. Based on [https://github.com/d3/d3 d3.js], renders image as SVG. There you can see [https://en.crystalls.info/Solubility_graph example chart page]. </div> == Beispiel == Beispiel einer Liniendiagrammansicht [[File:Chartie_extension.png|noframe|none]] == Supported file extensions == CSV * .csv == Installieren == {{ExtensionInstall |registration=required |download-link=[https://github.com/dolfinus/Chartie/archive/master.zip Erweiterung herunterladen] |custom-steps= * <span lang="en" dir="ltr" class="mw-content-ltr">Modify {{ll|Manual:$wgFileExtensions|$wgFileExtensions}} parameter:</span> <syntaxhighlight lang="php"> $wgFileExtensions = array_merge( $wgFileExtensions, array( 'csv' ) ); </syntaxhighlight> }} == Verwendung == === Als Bild-Handler === <pre class="wiki">[[File:Data.csv|800x350px|legend_title=,x_title=,...]]</pre> === Als Parser-Funktion === <pre class="wiki"> {{#chart: Name;x_value1;y_value1 Name;x_value2;y_value2 ...}} </pre> oder <pre class="wiki"> {{#chart:Data.csv}} </pre> mit Parameter: <pre class="wiki"> {{#chart:Data.csv|width}} {{#chart:Data.csv|width|height}} ... {{#chart:Data.csv|width|height|legend_title|x_type|x_title|x_unit|x_null|y_type|y_title|y_unit|y_null|delimiter|style|class}} </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of uploaded filename you also can use an url for file located in external site. </div> === Als Parser-Tag === <syntaxhighlight lang=html> <chart data="Data.csv" width="" height="" ... ></chart> </syntaxhighlight> oder <syntaxhighlight lang=html> <chart width="" height="" ... >Data.csv</chart> </syntaxhighlight> oder <syntaxhighlight lang=html> <chart width="" height="" ... > Name;x_value1;y_value1 Name;x_value2;y_value2 </chart> </syntaxhighlight> Du kannst auch url statt eines kurzen Dateinamens verwenden. == Parameter == {|class="wikitable" ! Name ! Beschreibung !align="{{dir|{{pagelang}}|left|right}}"| Standardwert |- | width | Diagramm-Container-Breite |align="{{dir|{{pagelang}}|left|right}}"| 865 |- | height | Diagramm-Container-Höhe |align="{{dir|{{pagelang}}|left|right}}"| 360 |- | legend_title | Titel des Legendenblocks: |align="{{dir|{{pagelang}}|left|right}}"| Lösungsmittel: |- | x_type | Typ des x-Achsenwerts |align="{{dir|{{pagelang}}|left|right}}"| temp |- | x_title | Titel für die x-Achse |align="{{dir|{{pagelang}}|left|right}}"| Temperatur |- | x_unit | Einheit für die x-Achse |align="{{dir|{{pagelang}}|left|right}}"| C |- | x_null | Falls es auf true ist, verwende 0 als Anfang der x-Achse. |align="{{dir|{{pagelang}}|left|right}}"| false |- | y_type | Typ des y-Achsenwerts |align="{{dir|{{pagelang}}|left|right}}"| solub |- | y_title | Titel für die Y-Achse |align="{{dir|{{pagelang}}|left|right}}"| Löslichkeit |- | y_unit | Einheit für y-Achse |align="{{dir|{{pagelang}}|left|right}}"| g/100g |- | y_null | Falls es auf true ist, verwende 0 als Anfang der y-Achse. |align="{{dir|{{pagelang}}|left|right}}"| false |- | delimiter | <span lang="en" dir="ltr" class="mw-content-ltr">Delimiter for csv file</span> |align="{{dir|{{pagelang}}|left|right}}"| ; |- | style | <span lang="en" dir="ltr" class="mw-content-ltr">Chart container CSS style</span> |align="{{dir|{{pagelang}}|left|right}}"| |- | class | Diagrammcontainer-HTML-Klasse |align="{{dir|{{pagelang}}|left|right}}"| |} <div lang="en" dir="ltr" class="mw-content-ltr"> Width and height can be set to ''auto'', so size of container will be set according to user screen dimensions. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Type of axis defines available units list, that could be converted to each one. If you want to use your own units, set axis type to ''general''. If you want to no use unit convertation at all, set axis type to ''no''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, axis titles and units are automatically sets its value, based on type (as =type name and =first unit in list):</span> === Achsenarten und Einheiten === {|class="wikitable" ! Typ ! Einheiten |- | general | a,f,p,n,u,m,c,d, ,K,M,G,T,P (Präfixe) |- | time | <span lang="en" dir="ltr" class="mw-content-ltr">s,min,hour,day,month,year</span> |- | mass | mg,ct,g,oz,lb,kg,ton |- | length | mm,cm,in,ft,yd,m,km,mile |- | area | mm2,cm2,in2,dm2,ft2,yd2,m2,a,da,acre,ha,km2,mile2 |- | volume | mm3,cm3,pt,qt,l,gal,br,m3,km3 |- | speed | mps,knot,mph,fps,kph,kps,c |- | temp | C,K,F,Ra |- | solub | g/100g,% |} === Lokalisierungen === Aktuell wird die Erweiterung auch auf Russisch übersetzt, sodass du die Lokalisierten Einheitennamen verwenden kannst (zum Beispiel ‘кг’ statt ‘kg’). Eine volle Liste von Lokalisierungen kann im Ordner ''i18n'', sie werden nach Langs benannt. === Konfigurieren === Alle Standardwerte können in deiner {{ll|Manual:LocalSettings.php|LocalSettings.php}}-Datei verändert werden: <syntaxhighlight lang="php"> $wgChartie["width"] = 865; $wgChartie["height"] = 360; ... $wgChartie["class"] = 'someclass'; </syntaxhighlight> == Steuerungen == {|class="wikitable" ! Aktion ! Steuerungen |- | <span lang="en" dir="ltr" class="mw-content-ltr">Mouse over line, touch line</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Show tooltip with extrapolated value</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Mouse over line dots, touch dot</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Show tooltip with exact value</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Click on axis title</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Show values from min / from zero</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Click on axis unit</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Convert values to new unit</span> |- | Linie doppelklicken | Die angegebene Linie verstecken |- | <span lang="en" dir="ltr" class="mw-content-ltr">Click or touch legend item</span> | Verstecke/Zeige die angegebene Linie |- | <span lang="en" dir="ltr" class="mw-content-ltr">Click on legend title</span> | Verstecke/Zeige alle Linien |} [[Category:Graph_extensions{{#translation:}}]] [[Category:Tag_extensions{{#translation:}}]] [[Category:Parser_function_extensions{{#translation:}}]] idlggkaaevd38pqsptjvr2b6c3ce86q 5386872 5386870 2022-07-28T19:33:03Z ThisCarthing 17456337 Created page with "Ändere den $1-Parameter:" wikitext text/x-wiki <languages/> {{Extension |author = [[User:Martynov Maxim|Dolfinus]] |license=MIT |type1 = parser function |type2 = tag |type3 = |type4 = link |image = Chartie_extension.png |status = stable |mediawiki = 1.25+ |download={{GithubDownload|dolfinus|Chartie|mastertarball=1}} |needs-updatephp = no |version = 1.0 |example = <span lang="en" dir="ltr" class="mw-content-ltr">[https://en.crystalls.info/Solubility_graph Example of line chart to wiki page]</span> |readme = [https://github.com/dolfinus/Chartie/master/README.md README] |update = 2017-02-13 |description = <span lang="en" dir="ltr" class="mw-content-ltr">Adds support of line charts at your MediaWiki</span> |parameters = $wgChartie |hook1=ParserMakeImageParams |hook2=ParserFirstCallInit |hook3=ImageBeforeProduceHTML |hook4=ImageOpenShowImageInlineBefore |hook5=BeforePageDisplay |hook6=BeforePageDisplayMobile |tags={{tag|chart|open}} }} == Beschreibung == <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki extension which allows to add simple line charts to site pages. Based on [https://github.com/d3/d3 d3.js], renders image as SVG. There you can see [https://en.crystalls.info/Solubility_graph example chart page]. </div> == Beispiel == Beispiel einer Liniendiagrammansicht [[File:Chartie_extension.png|noframe|none]] == Supported file extensions == CSV * .csv == Installieren == {{ExtensionInstall |registration=required |download-link=[https://github.com/dolfinus/Chartie/archive/master.zip Erweiterung herunterladen] |custom-steps= * Ändere den {{ll|Manual:$wgFileExtensions|$wgFileExtensions}}-Parameter: <syntaxhighlight lang="php"> $wgFileExtensions = array_merge( $wgFileExtensions, array( 'csv' ) ); </syntaxhighlight> }} == Verwendung == === Als Bild-Handler === <pre class="wiki">[[File:Data.csv|800x350px|legend_title=,x_title=,...]]</pre> === Als Parser-Funktion === <pre class="wiki"> {{#chart: Name;x_value1;y_value1 Name;x_value2;y_value2 ...}} </pre> oder <pre class="wiki"> {{#chart:Data.csv}} </pre> mit Parameter: <pre class="wiki"> {{#chart:Data.csv|width}} {{#chart:Data.csv|width|height}} ... {{#chart:Data.csv|width|height|legend_title|x_type|x_title|x_unit|x_null|y_type|y_title|y_unit|y_null|delimiter|style|class}} </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of uploaded filename you also can use an url for file located in external site. </div> === Als Parser-Tag === <syntaxhighlight lang=html> <chart data="Data.csv" width="" height="" ... ></chart> </syntaxhighlight> oder <syntaxhighlight lang=html> <chart width="" height="" ... >Data.csv</chart> </syntaxhighlight> oder <syntaxhighlight lang=html> <chart width="" height="" ... > Name;x_value1;y_value1 Name;x_value2;y_value2 </chart> </syntaxhighlight> Du kannst auch url statt eines kurzen Dateinamens verwenden. == Parameter == {|class="wikitable" ! Name ! Beschreibung !align="{{dir|{{pagelang}}|left|right}}"| Standardwert |- | width | Diagramm-Container-Breite |align="{{dir|{{pagelang}}|left|right}}"| 865 |- | height | Diagramm-Container-Höhe |align="{{dir|{{pagelang}}|left|right}}"| 360 |- | legend_title | Titel des Legendenblocks: |align="{{dir|{{pagelang}}|left|right}}"| Lösungsmittel: |- | x_type | Typ des x-Achsenwerts |align="{{dir|{{pagelang}}|left|right}}"| temp |- | x_title | Titel für die x-Achse |align="{{dir|{{pagelang}}|left|right}}"| Temperatur |- | x_unit | Einheit für die x-Achse |align="{{dir|{{pagelang}}|left|right}}"| C |- | x_null | Falls es auf true ist, verwende 0 als Anfang der x-Achse. |align="{{dir|{{pagelang}}|left|right}}"| false |- | y_type | Typ des y-Achsenwerts |align="{{dir|{{pagelang}}|left|right}}"| solub |- | y_title | Titel für die Y-Achse |align="{{dir|{{pagelang}}|left|right}}"| Löslichkeit |- | y_unit | Einheit für y-Achse |align="{{dir|{{pagelang}}|left|right}}"| g/100g |- | y_null | Falls es auf true ist, verwende 0 als Anfang der y-Achse. |align="{{dir|{{pagelang}}|left|right}}"| false |- | delimiter | <span lang="en" dir="ltr" class="mw-content-ltr">Delimiter for csv file</span> |align="{{dir|{{pagelang}}|left|right}}"| ; |- | style | <span lang="en" dir="ltr" class="mw-content-ltr">Chart container CSS style</span> |align="{{dir|{{pagelang}}|left|right}}"| |- | class | Diagrammcontainer-HTML-Klasse |align="{{dir|{{pagelang}}|left|right}}"| |} <div lang="en" dir="ltr" class="mw-content-ltr"> Width and height can be set to ''auto'', so size of container will be set according to user screen dimensions. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Type of axis defines available units list, that could be converted to each one. If you want to use your own units, set axis type to ''general''. If you want to no use unit convertation at all, set axis type to ''no''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, axis titles and units are automatically sets its value, based on type (as =type name and =first unit in list):</span> === Achsenarten und Einheiten === {|class="wikitable" ! Typ ! Einheiten |- | general | a,f,p,n,u,m,c,d, ,K,M,G,T,P (Präfixe) |- | time | <span lang="en" dir="ltr" class="mw-content-ltr">s,min,hour,day,month,year</span> |- | mass | mg,ct,g,oz,lb,kg,ton |- | length | mm,cm,in,ft,yd,m,km,mile |- | area | mm2,cm2,in2,dm2,ft2,yd2,m2,a,da,acre,ha,km2,mile2 |- | volume | mm3,cm3,pt,qt,l,gal,br,m3,km3 |- | speed | mps,knot,mph,fps,kph,kps,c |- | temp | C,K,F,Ra |- | solub | g/100g,% |} === Lokalisierungen === Aktuell wird die Erweiterung auch auf Russisch übersetzt, sodass du die Lokalisierten Einheitennamen verwenden kannst (zum Beispiel ‘кг’ statt ‘kg’). Eine volle Liste von Lokalisierungen kann im Ordner ''i18n'', sie werden nach Langs benannt. === Konfigurieren === Alle Standardwerte können in deiner {{ll|Manual:LocalSettings.php|LocalSettings.php}}-Datei verändert werden: <syntaxhighlight lang="php"> $wgChartie["width"] = 865; $wgChartie["height"] = 360; ... $wgChartie["class"] = 'someclass'; </syntaxhighlight> == Steuerungen == {|class="wikitable" ! Aktion ! Steuerungen |- | <span lang="en" dir="ltr" class="mw-content-ltr">Mouse over line, touch line</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Show tooltip with extrapolated value</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Mouse over line dots, touch dot</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Show tooltip with exact value</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Click on axis title</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Show values from min / from zero</span> |- | <span lang="en" dir="ltr" class="mw-content-ltr">Click on axis unit</span> | <span lang="en" dir="ltr" class="mw-content-ltr">Convert values to new unit</span> |- | Linie doppelklicken | Die angegebene Linie verstecken |- | <span lang="en" dir="ltr" class="mw-content-ltr">Click or touch legend item</span> | Verstecke/Zeige die angegebene Linie |- | <span lang="en" dir="ltr" class="mw-content-ltr">Click on legend title</span> | Verstecke/Zeige alle Linien |} [[Category:Graph_extensions{{#translation:}}]] [[Category:Tag_extensions{{#translation:}}]] [[Category:Parser_function_extensions{{#translation:}}]] gk2albcwrc0z7uzahc9jwh4v437vnpw Wikimedia Product/nan 0 1438859 5387587 5358204 2022-07-29T03:25:57Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198">Kòng-hiàn</span>]] * [[Readers|<span style="color:#2aa198">Tho̍k-tsiá</span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) == Tsí-piau == <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p Q4: 4-gue̍h tsì 6-gue̍h] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p Q1: 7-gue̍h tsì 9-gue̍h] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p Q2: 10-gue̍h tsì 12-gue̍h] |} == Bo̍k-piau == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|Q1: 2019 7-gue̍h tsì 9-gue̍h]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|Q2: 2019 10-gue̍h tsì 12-gue̍h]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|Q3: 2020 1-gue̍h 3 9-gue̍h]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|Q4: 2020 4-gue̍h tsì 6-gue̍h]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|Q1: 2018 7-gue̍h tsì 9-gue̍h]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|Q2: 2018 10-gue̍h tsì 12-gue̍h]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|Q3: 2019 1-gue̍h tsì 3-gue̍h]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|Q4: 2019 4-gue̍h tsì 6-gue̍h]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|Q1: 2017 7-gue̍h tsì 9-gue̍h]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|Q2: 2017 10-gue̍h tsì 12-gue̍h]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|Q3: 2018 1-gue̍h tsì 3-gue̍h]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|Q4: 2018 4-gue̍h tsì 6-gue̍h]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] g2mdha0is4xlha4xkx0mg1rm6wyd6nr Extension:EventLogging/ja 102 1440846 5387147 5381729 2022-07-28T21:07:44Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = アナリティクスのイベントを記録するためのフレームワークを提供 |version = 継続的な更新 |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} EventLogging拡張機能は、ユーザーがどのようにMediaWikiサイトを操作しているかについて、構造化されたデータを収集することを可能にします。 == 特徴 == * EventLoggingは、JavaScriptによるクライアントサイドロギングと、PHPによるサーバーサイドロギングをサポートしています。 * ログの動作は{{ll|Extension:EventStreamConfig}}を使って動的に設定できます。 * イベントは、スキーマのgitリポジトリに格納されているバージョン管理されたJSONSchemasによって定義されたJSONオブジェクトです。 * この拡張機能には、これらのイベントを転送、解析、またはロードするためのバックエンドコードは一切含まれていません。 別のサービスである[[wikitech:Event Platform/EventGate|EventGate]]は、この機能を実装し、Kafkaにイベントを挿入する処理を行います。 イベントは、様々な取り込みパイプラインを介して、下流のデータストア(Hiveなど)に永続化されます。 これらのコンポーネントの詳細は、ウィキメディア財団の構成に固有のものです。 == ウィキメディアでのEventLogging == <div class="mw-translate-fuzzy"> ウィキメディア財団は、[[wikitech:Analytics/Systems/EventLogging|利用者データを収集、集約、保存、分析するための広範なシステム]]の一部として、[[2|プライバシーポリシー]]と[[3|データ保持ガイドライン]]で定められた範囲内で、EventLogging拡張機能を使用しています。 </div> このページでは、EventLogging拡張機能の一般的な使い方について説明します。 ウィキメディア財団では、WMF専用のバックエンドコンポーネントと[https://schema.wikimedia.org/#!/ schema repositories]でEventLoggingを使用しています。 ウィキメディア特有の維持されている文書については、[[wikitech:Analytics/Systems/EventLogging]]と[[wikitech:Event Platform]]を参照してください。 ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Configuring the schema location === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, the extension will look for schemas on [[m:Special:MyLanguage/Meta-Wiki|Meta-Wiki]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The relevant default settings are:</span> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</span> <span lang="en" dir="ltr" class="mw-content-ltr">E.g. to use the <code>Schema</code> namespace of the local wiki, set</span> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">(and ensure the user account that will create the schemas is [[Special:MyLanguage/Manual:Autoconfirmed users|autoconfirmed]]).</span> == EventLoggingでイベントを記録する == * {{ll|Extension:EventLogging/Guide}} - EventLoggingスキーマの開発・導入など、様々な活動を行っています。 * {{ll|Extension:EventLogging/Programming}} - イベントを記録するコードを書く開発者のためのヒントと提案 == EventLogging拡張機能の開発 == == 開発者向け注記 == 開発者であれば、開発用のWikiでEventLoggingを設定して使用し、本番での使用をシミュレートしたいと思うでしょう。 ==== Dockerの使用 ==== ''{{ll|MediaWiki-Docker/Configuration recipes/EventLogging}} を参照'' ==== mediawiki-vagrantを使用 ==== mediawiki-vagrantを使って開発する場合、必要なものはすべて<code>eventlogging</code>ロールにまとめられています。 有効にするには、次のように実行します。 <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> ==== JavaScript開発のために ==== JavaScriptクライアントで作業する場合は、開発しているフォルダから<code>npm install</code>で依存関係をインストールする必要があります。 そうすると、例えば<code>npm test</code>をリントに使えます。 下記の「テストの実行方法」では、JavaScriptのテスト結果を確認する方法を紹介しています。 <div lang="en" dir="ltr" class="mw-content-ltr"> When adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered. </div> ==== テストの実行方法 ==== PHPテスト、Pythonテスト、JavaScriptテストがあります。 JavaScriptのテストを実行するには、開発wikiの「Special:JavaScriptTest/qunit」をご覧ください。 ({{ll|Manual:JavaScript unit testing}}を参照) PHPのテストを実行するには、PHPUnitを使用します。 インストールされていることを確認してから <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] 7ryt33p8wh0wtb062z7edk5v1huf2zq Reading/Web/Desktop Improvements/Updates/Talk to Web/vi 0 1443654 5387124 5383465 2022-07-28T20:35:33Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Lưu trữ |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} bawn9hy8df3fnq2y218vwr5y1obuywv Extension:PageAuthors 102 1443909 5386614 5385203 2022-07-28T16:53:56Z Sophivorus 106343 Update version number wikitext text/x-wiki <languages/> {{Extension | status = stable | type = parser function | username = Sophivorus | description = <translate><!--T:1--> Get a sensible list of page authors</translate> | update = 2022-07-28 | version = 1.2 | license = GPL-3.0-or-later | mediawiki = 1.35+ | php = 7+ | download = {{WikimediaDownload}} | needs-updatephp = No | example = [https://www.appropedia.org] }} The '''PageAuthors''' extension introduces a magic word <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> that returns a list of the main page authors of a page, sorted by number of bytes added. The extension is highly configurable so you can fine-tune what counts as an author. <translate> == Installation == <!--T:2--> </translate> {{ExtensionInstall | registration = required }} <translate> == Usage == <!--T:3--> </translate> Simply add <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> to any page and you will get a comma-separated list of the main authors of the current page, sorted by number of bytes added. See [[#Configuration|#Configuration]] to define your own criteria of what counts as an author. You can also do <code><nowiki>{{PAGEAUTHORS:Some page}}</nowiki></code> to get the list of authors for some page other than the current one. The list of authors can be further processed using [[Extension:Arrays]] or the [[Extension:Page Forms/Page Forms and templates##arraymap|#arraymap function of the PageForms extension]], for example to link to the relevant user pages. {{anchor|Configuration}} <translate> == Configuration == <!--T:4--> </translate> Each configuration is shown with its default value: * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerAuthor = 100;</syntaxhighlight> ― Minimum number of bytes added that each author must reach in order to be considered an author. * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerEdit = 10;</syntaxhighlight> ― Minimum number of bytes that each edit must reach in order to be counted towards the author's total. Having a positive value here already means that edits that reduce content don't count, which is usually desirable because even though synthesizing and removing problematic content is often valuable, we wouldn't say that makes you an ''author'' of the existing content. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreMinorEdits = true;</syntaxhighlight> ― Whether to ignore edits marked as minor. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBlocked = true;</syntaxhighlight> ― Whether to ignore blocked users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreAnons = true;</syntaxhighlight> ― Whether to ignore anonymous users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBots = true;</syntaxhighlight> ― Whether to ignore bots. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSystemUsers = true;</syntaxhighlight> ― Whether to ignore system users (such as in mass imports). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSummaryPatterns = [ '/Undo.*/', '/Revert.*/' ];</syntaxhighlight> ― Ignore edits with edit summaries that match these [https://www.php.net/manual/en/reference.pcre.pattern.syntax.php PHP regex patterns]. By default, edits with edit summaries that start with 'Undo' or 'Revert' will be ignored (these match the default edit summaries when doing a revert or a rollback in an English wiki). So for example, if some vandal blanks a page and then a user reverts it, the revert won't count towards the byte count of the user. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreUsers = [];</syntaxhighlight> ― Ignore edits by these users (without "User:" prefix). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreGroups = [];</syntaxhighlight> ― Ignore edits by these groups. * <syntaxhighlight lang=php inline>$wgPageAuthorsDelimiter = ', ';</syntaxhighlight> ― Delimiter between authors. <translate> == See also == <!--T:5--> </translate> * [[Manual:$wgMaxCredits]] - A built-in option to list the latest author followed by others in order of most recent edit, in the wiki footer. * [[Extension:Contributors]] - Lists authors by edit count. This is not reliable because some users tend to do few but big edits while others tend to do many small ones. Extreme but real cases include pages where the initial author creates the entire page in a single huge edit while other later editors make multiple edits fixing trivial issues. * [[Extension:SemanticExtraSpecialProperties]] - The _EUSER property lists authors by chronological order. This is not reliable either because while it's often the case that the first few editors are the main authors, it also happens that later editors contribute significantly and may even rewrite the entire page. jyjemehnokydt8q9m337huun72c9l6j Growth/FAQ/fr 0 1446757 5387834 5378638 2022-07-29T10:15:19Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''Bienvenue sur la Foire aux questions (FAQ) de l'équipe Croissance.''' Nous espérons que vous trouverez les informations dont vous avez besoin. Toutefois, si ce n'est pas le cas, [[Talk:Growth|faites-le nous savoir]]. ''Note pour les traducteurs : cette page est mise à jour régulièrement, ce qui peut avoir un impact sur votre travail. Nous faisons de notre mieux pour éviter ces perturbations.'' == Généralités == {{Anchor|features}} === Quelles sont les fonctionnalités sur lesquelles vous travaillez ? === * [[Special:MyLanguage/Growth/Feature summary#NH| '''Page d'accueil du nouvel arrivant''']] : une nouvelle page spéciale, le meilleur endroit pour un nouvel arrivant pour commencer. Elle comprend : ** [[Special:MyLanguage/Growth/Feature summary#NT|'''Tâches des nouveaux arrivants''']] : un flux de suggestions de tâches qui aident les nouveaux à apprendre à éditer. Les débutants ont fait des éditions [[NEWTEA|productives]] grâce à ce flux ! [[Help:Growth/Tools/Suggested edits|En savoir plus sur cet outil]]. ** '''Module de mentorat''' [module optionnel] : chaque nouvel arrivant a un lien direct avec un utilisateur expérimenté. Ainsi, ils peuvent poser des questions sur l'édition de Wikipédia, sans avoir à chercher où demander de l'aide. ** '''Module d'impact''' : l'utilisateur voit le nombre de vues des articles qu'il a édité. * [[Special:MyLanguage/Growth/Feature summary#HP|'''Panneau d'aide''']] : une plateforme pour fournir des ressources aux nouveaux arrivants pendant qu'ils éditent. S'ils choisissent l'une des tâches suggérées sur la page d'accueil des nouveaux arrivants, ils sont guidés pas à pas dans le processus d'édition. * '''[[Growth/Understanding first day|Sondage de bienvenue]]''' : les communautés peuvent savoir pourquoi les nouveaux arrivants créent un compte sur Wikipédia. Vous pouvez consulter ''[[Special:MyLanguage/Growth/Feature summary|notre résumé des fonctionnalités]]''' pour en savoir plus. === Sur quels wikis les fonctionnalités de croissance ont-elles été déployées ? === Vous pouvez trouver une liste de wikis sur notre [[Special:MyLanguage/Growth/Deployment table|Tableau de déploiement]]. Cette page liste également l'activation des fonctionnalités par wiki. {{anchor|NEWTEA}} === Les fonctionnalités de Croissance sont-elles efficaces ? === [[NEWTEA|L'équipe Growth a trouvé des preuves de l'efficacité de ces nouvelles fonctionnalités]]. En bref, la fonctionnalité de croissance "tâches des nouveaux arrivants" conduit à des augmentations dans : * la probabilité que les nouveaux arrivants modifient leur premier article (+11,6 %) * la probabilité qu'ils soient retenus comme éditeurs * le nombre de modifications apportées au cours des deux premières semaines sur le wiki (+22%) Nous constatons également que la qualité de leurs éditions est comparable à celle d'un groupe de contrôle. Sur base de ces résultats, nous pensons que toutes les Wikipédias devraient envisager de déployer des fonctionnalités de Croissance. Ce déploiement a été achevé en octobre 2021. {{anchor|translate}} === L'interface est partiellement traduite. Comment puis-je changer cela ? === [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] Il faut compter jusqu'à une semaine pour que les nouvelles traductions soient déployées. Les noms de pages spéciales nécessitent un processus spécial. Pour les chaînes de caractères suivantes, [[Talk:Growth|vous pouvez nous contacter]] directement avec les traductions : <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. {{anchor|enable|test}} === Puis-je tester les fonctionnalités ? === [[Growth/Deployment table|Sur les wikis où les fonctionnalités de Croissance sont disponibles]], et aussi sur [https://test.wikipedia.org test.wikipedia.org], allez dans vos [[Special:Preferences#mw-prefsection-personal|préférences utilisateur]] sur un de ces wikis et ensuite : * activez le '''Panneau d'aide''' dans l'onglet ''{{int|prefs-editing}}''. * activer la '''Page d'accueil du nouvel arrivant''' dans l'onglet ''{{int|prefs-personal}}''. L'activation de la page d'accueil des nouveaux arrivants vous donne accès aux '''tâches des nouveaux arrivants'''. N'oubliez pas d'activer ''les deux'' options des préférences : les modifications suggérées que vous trouvez sur la page d'accueil nécessitent le Panneau d'aide pour fonctionner. {{anchor|get}} === Comment mon wiki peut-il obtenir les fonctionnalités ? === Les fonctionnalités de Growth sont actuellement disponibles sur toutes les Wikipédias. Tout wiki hébergé par Wikimédia peut demander à disposer de [[#features|ces fonctionnalités]] avec les conditions suivantes. Comme détaillé sur [[Special:MyLanguage/Growth/Communities#Our%20focus|notre objectif]], nous travaillerons avec les wikis suivants par ordre de priorité : # Wikipédias de l'ensemble de nos '''[[#pilot|wikis pilotes]]''' – nous traitons tous les commentaires qu'elles nous communiquent. # Wikipédias - elles obtiennent les fonctionnalités telles qu'elles sont, mais nous pouvons prendre en compte les suggestions d'amélioration de ces wikis. # Tous les autres projets Wikimedia - ils obtiennent les fonctionnalités telles qu'elles sont, et l'équipe n'aura pas le temps de donner la priorité aux améliorations spécifiques à ces wikis. === Prévoyez-vous de déployer les fonctionnalités en dehors de Wikipédia ? === Nous accueillons toute communauté Wikimedia qui souhaite mettre en œuvre des fonctionnalités de croissance sur son wiki. Cependant, plutôt que de simplement déployer les fonctionnalités telles quelles, nous voulons fournir une solution adaptée aux wikis concernés. Veuillez nous contacter [[Talk:Growth|sur la page de discussion de l'équipe]] pour discuter de la manière dont nous pouvons modifier les outils pour qu'ils fonctionnent pour votre projet Wikimedia. Nous envisageons de travailler avec les [[Growth/Communities/Wikisource|communautés Wikisource]]. {{anchor|pilot|ambassador}} <div class="mw-translate-fuzzy"> === Pouvez-vous préciser ce que sont les « Wikis pilotes » et les « Ambassadeurs » ? === </div> Les '''Wikis pilotes''' sont des wikis qui ont une collaboration étroite avec l'équipe Croissance. Ils sont impliqués dans le développement et l'examen préliminaire des projets. Ils testent également tous les prototypes en premier. L'équipe Croissance peut contacter d'autres wikis pour certaines de ces étapes. <div class="mw-translate-fuzzy"> En date du {{ymd|2022|3|1}}, nos wikis pilotes sont : {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div class="mw-translate-fuzzy"> Afin d'avoir un meilleur processus de communication avec nos wikis pilotes, l'équipe Croissance emploie des volontaires à temps partiel, les '''Ambassadeurs'''. Ces ambassadeurs ont été recrutés au sein de la communauté. Les ambassadeurs peuvent également contacter les « wikis voisins » pour une collaboration similaire à celle des « wikis pilotes ». </div> <div class="mw-translate-fuzzy"> Les ambassadeurs facilitent la communication entre l'équipe Croissance et leur communauté. Ils aident l'équipe Croissance à comprendre la diversité de nos wikis, et ils aident leurs communautés à faire appel à l'équipe Croissance et à accueillir les nouveaux arrivants. </div> === Puis-je utiliser les fonctions de Croissance sur mobile ? Sur les applications officielles (iOS, Android) ? === Les fonctionnalités de croissance sont conçues pour être utilisées à la fois sur la version de bureau et la version mobile de Wikipédia. Elles ne sont pas disponibles sur les applications officielles (iOS, Android). == Accès aux fonctionnalités == {{anchor|ABtest}} === Comment les nouveaux comptes peuvent-ils obtenir les fonctionnalités ? === <div class="mw-translate-fuzzy"> Sur les wikis [[Growth/Deployment table|où les fonctionnalités de Croissance ont été déployées]], et où aucun [[A/B testing|Test A/B]] n'est actif, 100% des nouveaux comptes obtiennent les fonctionnalités. </div> Sur les wikis [[Growth/Deployment table|où les fonctionnalités de Croissance ont été déployées]] et où un [[A/B testing|test A/B]] est actif, 80% des nouveaux comptes obtiendront les fonctionnalités automatiquement ; les 20% restants feront partie d'un groupe de contrôle. Ce groupe de contrôle existe pour que l'équipe Croissance puisse comparer les deux expériences. <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> === Comment les comptes existants peuvent-ils obtenir les fonctionnalités ? === Sur les wikis [[Growth/Deployment table|où les fonctionnalités de Croissance ont été déployées]], tout le monde peut trouver les fonctionnalités [[#enable|dans leurs préférences]]. === J'organise un atelier. Comment puis-je contrôler si mes étudiants obtiennent les fonctionnalités lorsqu'ils créent un compte ? === Il est possible de disposer d'un paramètre de lien pour contrôler l'accès aux fonctionnalités : * <code>Special:CreateAccount?geEnabled=1</code> forcera les fonctionnalités de Croissance à la création du compte * <code>Special:CreateAccount?geEnabled=0</code> forcera l'expérience par défaut lors de la création du compte. Bien entendu, ce paramètre devrait avoir un usage très limité. Il aurait un impact sur les données collectées par l'équipe Croissance concernant la création de comptes et l'utilisation des fonctionnalités. Si vous prévoyez d'utiliser ces paramètres, [[Talk:Growth|veuillez nous en informer]]. {{anchor|Homepage}} == Page d'accueil == ''Les éléments suivants ne sont valables que pour les wikis [[Growth/Deployment table|où les fonctionnalités de Croissance ont été déployées]].'' === Comment accéder à la page d'accueil ? === Si vous avez récemment créé votre compte sur Wikipédia, la page d'accueil est accessible en cliquant sur votre nom d'utilisateur, le lien situé en haut à droite de n'importe quelle page. Si vous avez déjà un compte sur Wikipédia, vous devez activer la page d'accueil dans vos préférences. Lorsque c'est fait, la page d'accueil est accessible en cliquant sur votre nom d'utilisateur, ou sur le lien de votre page de discussion. Vous y trouverez un nouvel onglet qui mène à votre page d'accueil. Vous avez également la possibilité, dans vos préférences, d'accéder directement à votre page d'accueil lorsque vous cliquez sur votre nom d'utilisateur. === Mon adresse électronique est demandée, ou mon adresse électronique est affichée en haut de la page d'accueil. Pourquoi ? === Nous partons du principe que la plupart des gens savent comment utiliser une adresse électronique. Par conséquent, nous encourageons les utilisateurs à ajouter leur adresse électronique afin qu'ils puissent recevoir des [[Special:MyLanguage/Help:Notifications|notifications]], comme lorsqu'ils sont mentionnés par d'autres utilisateurs sur le wiki. L'adresse électronique ne sera pas visible par les autres utilisateurs. La communication avec les autres utilisateurs se fait sur le wiki. === Les liens d'aide affichés sur la page d'accueil ne sont pas pertinents. Comment les modifier ? === Ces liens sont [[#HP|les mêmes que sur le panneau d'aide]]. <div class="mw-translate-fuzzy"> Un administrateur d'interface peut changer ces liens en utilisant <code>Special:EditGrowthConfig</code>. </div> Nous pouvons vous aider dans cette tâche. [[Talk:Growth|Veuillez nous contacter]] avec votre demande ; veuillez fournir un lien vers la discussion communautaire qui a mené à ce changement. == Modifications suggérées == === Comment fonctionnent les modifications suggérées ? === ==== Comment les sujets et les tâches sont suggérés ? ==== Nous vous suggérons des articles qui combinent à la fois les sujets sélectionnés et les tâches sur lesquelles vous aimeriez travailler. Si vous ne sélectionnez que les types de tâches, vous obtenez tous les articles dont le modèle correspond au type de tâche. Par exemple, si vous ne sélectionnez aucun sujet et « Petites corrections » comme tâche, vous obtiendrez jusqu'à 200 articles nécessitant des petites corrections, quel que soit le sujet. Si vous sélectionnez « Europe » comme sujet et « Petites corrections » comme tâche, vous aurez jusqu'à 200 articles sur l'Europe qui ont un modèle relatif aux petites corrections. Si vous ajoutez « Développer l'article » à la sélection précédente, vous avez des articles qui portent sur l'Europe et qui demandent soit de petites corrections, soit un développement. Si vous ajoutez « Asie » à la sélection précédente, vous aurez des articles soit sur l'Europe, soit sur l'Asie et qui demandent soit de petites corrections, soit une expansion. === Supervision et dépannage de SuggestedEdits === ==== Puis-je surveiller les articles qui ont été modifiés en tant que modifications suggérées ? ==== Les articles édités en tant que modifications suggérées sont marqués comme tels dans les modifications récentes et la liste de surveillance. ==== Comment contrôler quels sujets ou quelles tâches nécessitent plus d'articles ? ==== Veuillez utiliser <code>Special:NewcomerTasksInfo</code>. ==== Je n'ai pas de tâche pour une combinaison donnée. Est-ce normal ? ==== Certains sujets n'ont pas beaucoup d'articles. Par conséquent, ils ont moins d'articles étiquetés avec des modèles de maintenance, ce qui conduit à un choix limité. ==== Un utilisateur utilise les outils de manière non constructive. Que puis-je faire ? ==== Dans l'ensemble, les utilisateurs effectuent [[#NEWTEA|des modifications plus constructives]] en utilisant les fonctions de croissance. Cependant, on peut voir un utilisateur donné qui ne suit pas les conseils et utilise les outils de manière inappropriée. La manière la plus appropriée de gérer ces situations est d'appliquer la procédure habituelle pour les comportements non constructifs : # essayer de comprendre ce que l'utilisateur essaie de faire, # contactez cet utilisateur, expliquez-lui la situation, demandez-lui des précisions et orientez-le vers une autre voie si elle existe, # si le comportement non constructif persiste, bloquez l'utilisateur. Si des modifications non constructives répétitives et similaires sont effectuées sur votre wiki, [[Talk:Growth|s'il vous plaît, faites-le nous savoir]]. Ajoutez à votre message quelques ''diffs'' comme exemples de modifications non constructives afin que l'équipe de Croissance puisse analyser la situation et réfléchir à une solution. ==== J'ai activé la page d'accueil dans mes préférences utilisateur. Lorsque je sélectionne un article à améliorer sur la page d'accueil, je ne vois pas d'indications sur l'article. ==== Avez-vous activé le panneau d'aide dans vos préférences ? Si oui, [[Talk:Growth|vous pouvez nous informer de ce problème]]. {{anchor|config}} === Configuration des modifications suggérées === ==== Comment offrir plus de tâches aux nouveaux arrivants ? ==== Les nouveaux arrivants sont invités à travailler sur 5 tâches de maintenance, classées par niveau de difficulté : {| class="wikitable" !'''Tâche''' !Niveau de difficulté !But de la tâche |- |Petites corrections |facile |correction orthographique, grammaticale et de style |- |Ajout de liens |facile |ajouter des liens entre les articles |- |Mise à jour des articles |moyen |actualiser les contenus existants |- |Ajouter des références |moyen |trouver des sources pour les articles existants |- |Développer un article |difficile |développer les ébauches pour en faire des articles sourcés |} Les tâches sont répertoriées en fonction des modèles de maintenance. Pour augmenter le nombre de tâches disponibles, vous pouvez : * Ajoutez d'autres modèles qui correspondent à la définition de la tâche sur <code>Special:EditGrowthConfig</code> dans votre wiki. * Ajoutez des modèles de maintenance à plus d'articles sur votre wiki. Parfois, les tâches faciles ne sont pas disponibles parce que des éditeurs expérimentés y travaillent. Nous conseillons aux utilisateurs expérimentés de travailler sur des tâches plus difficiles à la place, afin de laisser aux nouveaux venus la chance de faire leurs premières éditions. ==== Peut-on suggérer un nouveau type de tâche ou attribuer un niveau de difficulté différent à une tâche existante ? ==== Ce n'est pas possible pour le moment. [[Talk:Growth|Veuillez nous faire part]] de votre potentiel projet. === Tâches structurées - Ajouter un lien === ''Les éléments suivants ne sont valables que pour les wikis [[Special:MyLanguage/Growth/Deployment table|où ''Tâches structurées - Ajouter un lien'' a été déployé]].'' ==== Quelle est la différence entre "ajouter un lien" et "Tâches structurées - Ajouter un lien" ? ==== <span class="mw-translate-fuzzy">"Ajouter un lien" montre aux utilisateurs un article où plus de liens internes sont nécessaires. Ce "Ajouter un lien" est une tâche basée sur des modèles de maintenance.</span> Les nouveaux arrivants doivent comprendre ce qu'il faut faire, ce qui peut rendre les choses compliquées pour eux : qu'est-ce qu'un bon lien, où le mettre... ? Même si des conseils étaient affichés dans le panneau d'aide, tous les liens n'étaient pas exacts et, parfois, certains liens externes étaient également ajoutés. Par conséquent, l'équipe Croissance s'efforce d'améliorer ce processus, en réduisant le nombre de difficultés auxquelles les gens peuvent être confrontés. Nous fournissons une meilleure orientation et nous suggérons un ensemble de liens qui pourraient potentiellement être ajoutés. Ces liens sont affichés sur des mots spécifiques dans un article. Les utilisateurs doivent décider si un lien doit être ajouté ou non. Ces liens sont suggérés par une machine. ==== Quels wikis ont Tâches structurées - Ajouter un lien ? ==== Vous pouvez trouver la liste dans le [[Special:MyLanguage/Growth/Deployment table|tableau de déploiement]]. ==== Quelle est la précision des prédictions de Tâches structurées - Ajouter un lien ? ==== Les prédictions sont, en moyenne, précises à 70%. Certaines personnes nous ont demandé s'il serait possible d'avoir une meilleure prédiction. Ce serait possible, mais cela diminuerait l'intérêt de la tâche. Nous encourageons les nouveaux arrivants à comprendre pourquoi un lien suggéré serait (ou ne serait pas) intéressant pour les lecteurs, et à décider s'ils doivent l'inclure. Un taux de prédiction plus élevé enlèverait tout intérêt à la tâche, puisque l'inclusion de liens serait la réponse par défaut. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> === Tâches structurées - Ajouter une image === ''Ce projet est un travail en cours, en phase de développement. Vous pouvez en savoir plus sur ce projet en visitant [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|sa page de projet]].'' ==== Quel est le but de « Tâches structurées - Ajouter une image » ? ==== Basé sur le même principe que "Modifications suggérées - Ajouter un lien", ce projet vise à supprimer davantage d'obstacles à l'insertion d'images. ==== Quelles règles définissent le travail effectué par « Tâches structurées - Ajouter une image » ? ==== Nous avons plusieurs règles : * Les images sont choisies si elles sont utilisées sur d'autres Wikipédias. Par exemple, si plusieurs articles dans différentes langues, liés au même élément de Wikdata, utilisent la même image, alors nous suggérons l'image. * Seuls les articles où aucune image n'est affichée sont pris en considération pour l'ajout d'images. * Les articles avec une infobox mais sans image ne sont pas pris en compte pour le moment. ==== Quels types d'utilisateurs ont été contactés pour tester ce nouveau concept ? ==== Au cours du processus de conception, plusieurs types d'utilisateurs ont été impliqués. * Pendant le processus de développement : Les membres de l'équipe Croissance (qui comprennent plusieurs éditeurs actifs de Wikis) et nos [[#ambassadors|Ambassadeurs]] (à ce moment du processus : {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}). * Pour tester les premiers prototypes, nous nous sommes concentrés sur les deux types de rédacteurs que nos fonctionnalités ciblent. ** les personnes qui ne sont pas des éditeurs de wiki (en utilisant UserTesting.com, en anglais et en espagnol) ** des utilisateurs expérimentés impliqués dans les premiers pas des nouveaux arrivants, venant de [[#pilot|nos wikis pilotes]] comme des personnes de la Wikipédia en espagnol. {{anchor|HP}} == Panneau d’aide == === Nous voulons modifier certains liens affichés dans le panneau d'aide. Comment le faire ? === <div class="mw-translate-fuzzy"> Un administrateur d'interface peut changer ces liens en utilisant <code>Special:EditGrowthConfig</code>. </div> Nous pouvons vous aider dans cette tâche. [[Talk:Growth|Veuillez nous contacter]] avec votre demande ; veuillez fournir un lien vers la discussion communautaire qui a mené à ce changement. Ces liens sont [[#Homepage|également utilisés sur la page d'accueil]]. === Où vont les questions postées à l'aide du panneau d'aide ? === Par défaut, ces questions sont transmises au service d'assistance local. S'il existe à la fois un service d'assistance et une liste de mentors, c'est à la communauté qu'il appartient de décider : * les nouveaux messages doivent aller aux mentors des nouveaux arrivants, * les nouveaux messages doivent être publiés au service d'aide. <div class="mw-translate-fuzzy"> Un administrateur d'interface peut modifier cette configuration en utilisant <code>Special:EditGrowthConfig</code>. </div> === Notre communauté a décidé que tous les messages postés sur le panneau d'aide devaient aller au service d'aide. Ce n'est pas le cas sur certaines pages. Pourquoi ? === Nous avons observé que les nouveaux arrivants tentent parfois de contacter leur mentor en feuilletant un message sur leur propre page de discussion (User:New contacte User:Experienced en postant sur User_talk:New). Par conséquent, nous proposons de contacter le mentor lorsque les gens utilisent le panneau d'aide de leur propre page de discussion. {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> == Configuration et fonctionnement du système de mentorat == === Mon wiki n'a pas le système de mentorat de Croissance. Comment puis-je le mettre en place ? === Les étapes suivantes sont un résumé du processus. Le processus complet est décrit sur [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|cette page dédiée]]. Tout d'abord, vous devez vérifier si les outils de Croissance sont [[Growth/Deployment table|déployés sur votre wiki]]. Si ce n'est pas encore le cas, veuillez consulter [[#get|comment obtenir les fonctionnalités]]. Ensuite, vous devez trouver d'autres mentors qui se portent volontaires. Tous les mentors doivent s'inscrire sur une page spécifique, en utilisant [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|une syntaxe spécifique]]. Si votre communauté a mis en place un programme de mentorat à l'aide des fonctionnalités de Croissance, la page de votre wiki devrait être répertoriée sous [[D:Q14339834|cet élément Wikidata]]. <div class="mw-translate-fuzzy"> Dans votre wiki, un administrateur d'interface doit ajouter la liste des mentors à la page de configuration (<code>Special:EditGrowthConfig</code>). </div> === Combien de mentors un wiki a-t-il besoin ? === Sur base de nos observations, nous conseillons d'avoir un mentor pour chaque groupe de 500 nouveaux utilisateurs que votre wiki reçoit par mois. Par exemple, si votre wiki compte 2 500 nouveaux comptes par mois, vous devriez avoir au moins 5 mentors. Nous recommandons d'avoir au moins 3 mentors. <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> === Comment les mentors sont assignés aux nouveaux arrivants ? === Chaque nouveau compte reçoit un mentor choisi au hasard dans une liste de volontaires. === Combien de messages un mentor reçoit-il par semaine ? === C'est difficile à savoir. Cela dépend de la motivation des nouveaux arrivants, et du nombre de mentors pour le wiki. En moyenne, nous observons entre 0 et 6 messages par semaine, avec quelques fluctuations entre les semaines. === Avez-vous envisagé d'attribuer un mentor uniquement aux personnes qui ont déjà effectué des modifications ? === Nous ne savons pas ce dont chaque nouvel arrivant a besoin. [[Special:MyLanguage/New Editor Experiences|Sur base de cette recherche]], certains nouveaux utilisateurs ont besoin d'une confirmation de leur droit d'édition avant de faire leur première édition. D'autres aimeraient avoir plus d'informations sur l'édition avant de commencer à éditer. Par conséquent, nous fournissons un mentor à chaque nouveau compte. C'est ensuite au nouvel arrivant de contacter son mentor. {{anchor|existing}} === Notre wiki a déjà un projet de mentorat. Le système de mentorat de Croissance le remplace-t-il ? === Nous supposons que votre système de mentorat est une liste d'utilisateurs expérimentés qui sont disponibles pour les nouveaux utilisateurs motivés, qui ont des questions spécifiques sur des sujets précis. La plupart sont [[d:Q3919128|répertoriés sur Wikidata]]. C'est à votre communauté de trouver la bonne façon d'intégrer la fonction de mentorat de Croissance. Voici quelques options : '''Remplacer votre système de mentorat par le nouveau.''' Si votre système de mentorat n'a pas beaucoup de succès, il pourrait être remplacé par les fonctionnalités de l'équipe Croissance. '''Faire en sorte que les deux systèmes fonctionnent ensemble''' Vous pouvez imaginer avoir deux fonctions : * Le mentorat de Croissance s'occupe des questions de base des nouveaux arrivants, * Le mentorat existant peut prendre en charge les nouveaux arrivants qui sont plus impliqués. Dans ce cas, vous devrez peut-être traduire localement l'interface des fonctionnalités de Croissance en utilisant vos propres termes. === Où puis-je m'inscrire comme mentor ? === Si votre communauté a mis en place un programme de mentorat en utilisant les fonctionnalités de Croissance, la page de votre wiki devrait être répertoriée sur [[D:Q14339834|cet élément Wikidata]]. <span class="mw-translate-fuzzy">Votre communauté a peut-être défini certaines conditions pour devenir un mentor. Habituellement, il est demandé d'avoir une assez bonne expérience de l'édition du wiki (500 éditions et 90 jours de présence).</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} === Comment me présenter en tant que mentor ? === Lorsque vous vous inscrivez pour devenir un mentor, la syntaxe suivante doit être utilisée, avec : <code>* <nowiki>[[</nowiki>User:Nom d'utilisateur<nowiki>]]</nowiki>|Description</code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|En savoir plus]] {{anchor|reassign}} === Peut-on réassigner un nouveau venu à un autre mentor ? === Oui, c'est possible avec <code>Special:ClaimMentee</code>. {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> === Un mentor vient de démissionner. Peut-on réassigner tous les nouveaux arrivants à d'autres mentors ? === <div class="mw-translate-fuzzy"> Vous pouvez utiliser <code>Special:ClaimMentee</code> pour réassigner mais si vous voulez réassigner tous les nouveaux arrivants, [[Talk:Growth|s'il vous plaît contactez nous]] directement. </div> {{anchor|magicword}} === Comment afficher le mentor d'un utilisateur donné ? / Comment ajouter le nom du mentor à notre message de bienvenue ? === Tapez le mot magique <code><nowiki>{{#mentor:Foo}}</nowiki></code> dans une page Wikitexte, et visualisez. "Foo" doit être remplacé par le nom d'utilisateur que vous ciblez. Cela affichera le nom du mentor de Foo. Ce mot magique peut être utilisé dans un modèle : message de bienvenue, messages de la page de discussion de l'utilisateur, boîte utilisateur, etc. [[#reassign|Si le mentor change]], le mot magique choisit le nom du nouveau mentor. Vous pouvez « [[Special:MyLanguage/Help:Substitution|subst:]] » ce message si nécessaire : <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Le mentor de Foo sera alors sauvegardé comme Wikitexte. === Nous avons renommé notre liste de mentors et maintenant nous ne recevons aucune question des nouveaux arrivants. Comment réparer cela ? === Avez-vous mis à jour <code>Special:EditGrowthConfig</code> avec le nouveau nom de la page ? == Interactions entre les mentors et les nouveaux arrivants == {{Anchor|questions}} === Quels types de questions les nouveaux arrivants posent-ils ? === D'après les observations que nous avons faites, les questions portent principalement sur l'édition de base. Certaines questions sont des interactions sociales (« Bonjour »), provenant d'utilisateurs qui essaient les outils pour vérifier si quelqu'un répondrait. Nous vous encourageons à répondre à ces salutations, car elles peuvent être le début de certaines interactions. Sur base de l'expérience des communautés, l'équipe Croissance a travaillé [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|sur un guide pour les mentors]] pour pouvoir répondre à ces questions. === Les nouveaux arrivants n'ont pas répondu à mes messages. Pourquoi ? === Il y a deux cas possibles : * Avez-vous mentionné l'utilisateur dans votre réponse ? Les nouveaux arrivants ne savent pas comment utiliser la liste de suivi ou d'autres outils pour surveiller les changements. La page d'accueil propose un moyen de revenir à la page de discussion du mentor, mais le fait de le mentionner est le plus efficace. Un ping déclenchera une notification, ce qui est le moyen le plus efficace de faire savoir aux nouveaux arrivants qu'ils ont reçu une réponse à leurs messages. * Les nouveaux arrivants ne viennent pas quotidiennement sur les wikis. Certains d'entre eux répondront après quelques jours, d'autres après quelques semaines. Mentors, veuillez considérer ceci quand vous archivez votre page de discussion. === A qui puis-je demander si mon mentor ne me répond pas ? === Si votre mentor n'est pas disponible, vous pouvez poser votre question au service d'assistance local ou à tout autre utilisateur expérimenté. === Je peux demander à avoir un autre mentor ? === <div class="mw-translate-fuzzy"> Vous pouvez contacter un autre mentor et lui demander de devenir votre mentor. Si vous êtes d'accord, le mentor [[#reassign|fera le changement]]. </div> === En tant que mentor, comment puis-je surveiller les nouveaux arrivants qui me sont assignés ? === Nous travaillons actuellement sur le [[Growth/Mentor dashboard|Tableau de bord des mentors]]. Ce tableau de bord est disponible sur toutes les Wikipedias où [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|une liste des mentors a été créée et activée]]. === Puis-je filtrer l'activité de mes mentorés dans les Modifications récentes, ou dans ma Liste de suivi ? === Sur les wikis où le tableau de bord des mentors est déployé, un nouveau filtre est disponible pour les mentors. Ils peuvent suivre l'activité de leurs mentorés dans leur Liste de suivi et dans les Modifications récentes. Pour des raisons de confidentialité, ce filtre ne peut pas être consulté par quelqu'un d'autre que le mentor lui-même. Ce filtre ne filtre que les mentorés assignés au mentor. Ce filtre n'est pas visible pour les personnes qui ne sont pas [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|listées comme mentors]]. <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> 7tfshyigll24j8n5udmw6xlmzw6ty9s Extension:PageAuthors/en 102 1473668 5387162 5385396 2022-07-28T21:09:03Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension | status = stable | type = parser function | username = Sophivorus | description = Get a sensible list of page authors | update = 2022-07-28 | version = 1.2 | license = GPL-3.0-or-later | mediawiki = 1.35+ | php = 7+ | download = {{WikimediaDownload}} | needs-updatephp = No | example = [https://www.appropedia.org] }} The '''PageAuthors''' extension introduces a magic word <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> that returns a list of the main page authors of a page, sorted by number of bytes added. The extension is highly configurable so you can fine-tune what counts as an author. == Installation == {{ExtensionInstall | registration = required }} == Usage == Simply add <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> to any page and you will get a comma-separated list of the main authors of the current page, sorted by number of bytes added. See [[#Configuration|#Configuration]] to define your own criteria of what counts as an author. You can also do <code><nowiki>{{PAGEAUTHORS:Some page}}</nowiki></code> to get the list of authors for some page other than the current one. The list of authors can be further processed using [[Extension:Arrays]] or the [[Extension:Page Forms/Page Forms and templates##arraymap|#arraymap function of the PageForms extension]], for example to link to the relevant user pages. {{anchor|Configuration}} == Configuration == Each configuration is shown with its default value: * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerAuthor = 100;</syntaxhighlight> ― Minimum number of bytes added that each author must reach in order to be considered an author. * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerEdit = 10;</syntaxhighlight> ― Minimum number of bytes that each edit must reach in order to be counted towards the author's total. Having a positive value here already means that edits that reduce content don't count, which is usually desirable because even though synthesizing and removing problematic content is often valuable, we wouldn't say that makes you an ''author'' of the existing content. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreMinorEdits = true;</syntaxhighlight> ― Whether to ignore edits marked as minor. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBlocked = true;</syntaxhighlight> ― Whether to ignore blocked users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreAnons = true;</syntaxhighlight> ― Whether to ignore anonymous users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBots = true;</syntaxhighlight> ― Whether to ignore bots. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSystemUsers = true;</syntaxhighlight> ― Whether to ignore system users (such as in mass imports). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSummaryPatterns = [ '/Undo.*/', '/Revert.*/' ];</syntaxhighlight> ― Ignore edits with edit summaries that match these [https://www.php.net/manual/en/reference.pcre.pattern.syntax.php PHP regex patterns]. By default, edits with edit summaries that start with 'Undo' or 'Revert' will be ignored (these match the default edit summaries when doing a revert or a rollback in an English wiki). So for example, if some vandal blanks a page and then a user reverts it, the revert won't count towards the byte count of the user. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreUsers = [];</syntaxhighlight> ― Ignore edits by these users (without "User:" prefix). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreGroups = [];</syntaxhighlight> ― Ignore edits by these groups. * <syntaxhighlight lang=php inline>$wgPageAuthorsDelimiter = ', ';</syntaxhighlight> ― Delimiter between authors. == See also == * [[Manual:$wgMaxCredits]] - A built-in option to list the latest author followed by others in order of most recent edit, in the wiki footer. * [[Extension:Contributors]] - Lists authors by edit count. This is not reliable because some users tend to do few but big edits while others tend to do many small ones. Extreme but real cases include pages where the initial author creates the entire page in a single huge edit while other later editors make multiple edits fixing trivial issues. * [[Extension:SemanticExtraSpecialProperties]] - The _EUSER property lists authors by chronological order. This is not reliable either because while it's often the case that the first few editors are the main authors, it also happens that later editors contribute significantly and may even rewrite the entire page. mdnjmeftuqrqf3h9e5ehvd6cj0w5v1k Extension:PageAuthors/ja 102 1473670 5387163 5385397 2022-07-28T21:09:05Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension | status = stable | type = parser function | username = Sophivorus | description = <span lang="en" dir="ltr" class="mw-content-ltr">Get a sensible list of page authors</span> | update = 2022-07-28 | version = 1.2 | license = GPL-3.0-or-later | mediawiki = 1.35+ | php = 7+ | download = {{WikimediaDownload}} | needs-updatephp = No | example = [https://www.appropedia.org] }} The '''PageAuthors''' extension introduces a magic word <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> that returns a list of the main page authors of a page, sorted by number of bytes added. The extension is highly configurable so you can fine-tune what counts as an author. == インストール == {{ExtensionInstall | registration = required }} == 使用法 == Simply add <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> to any page and you will get a comma-separated list of the main authors of the current page, sorted by number of bytes added. See [[#Configuration|#Configuration]] to define your own criteria of what counts as an author. You can also do <code><nowiki>{{PAGEAUTHORS:Some page}}</nowiki></code> to get the list of authors for some page other than the current one. The list of authors can be further processed using [[Extension:Arrays]] or the [[Extension:Page Forms/Page Forms and templates##arraymap|#arraymap function of the PageForms extension]], for example to link to the relevant user pages. {{anchor|Configuration}} == 設定 == Each configuration is shown with its default value: * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerAuthor = 100;</syntaxhighlight> ― Minimum number of bytes added that each author must reach in order to be considered an author. * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerEdit = 10;</syntaxhighlight> ― Minimum number of bytes that each edit must reach in order to be counted towards the author's total. Having a positive value here already means that edits that reduce content don't count, which is usually desirable because even though synthesizing and removing problematic content is often valuable, we wouldn't say that makes you an ''author'' of the existing content. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreMinorEdits = true;</syntaxhighlight> ― Whether to ignore edits marked as minor. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBlocked = true;</syntaxhighlight> ― Whether to ignore blocked users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreAnons = true;</syntaxhighlight> ― Whether to ignore anonymous users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBots = true;</syntaxhighlight> ― Whether to ignore bots. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSystemUsers = true;</syntaxhighlight> ― Whether to ignore system users (such as in mass imports). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSummaryPatterns = [ '/Undo.*/', '/Revert.*/' ];</syntaxhighlight> ― Ignore edits with edit summaries that match these [https://www.php.net/manual/en/reference.pcre.pattern.syntax.php PHP regex patterns]. By default, edits with edit summaries that start with 'Undo' or 'Revert' will be ignored (these match the default edit summaries when doing a revert or a rollback in an English wiki). So for example, if some vandal blanks a page and then a user reverts it, the revert won't count towards the byte count of the user. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreUsers = [];</syntaxhighlight> ― Ignore edits by these users (without "User:" prefix). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreGroups = [];</syntaxhighlight> ― Ignore edits by these groups. * <syntaxhighlight lang=php inline>$wgPageAuthorsDelimiter = ', ';</syntaxhighlight> ― Delimiter between authors. == 関連項目 == * [[Manual:$wgMaxCredits]] - A built-in option to list the latest author followed by others in order of most recent edit, in the wiki footer. * [[Extension:Contributors]] - Lists authors by edit count. This is not reliable because some users tend to do few but big edits while others tend to do many small ones. Extreme but real cases include pages where the initial author creates the entire page in a single huge edit while other later editors make multiple edits fixing trivial issues. * [[Extension:SemanticExtraSpecialProperties]] - The _EUSER property lists authors by chronological order. This is not reliable either because while it's often the case that the first few editors are the main authors, it also happens that later editors contribute significantly and may even rewrite the entire page. n7f0dfwgdmhrumsyfv37sviciz1us6j Extension:NaylorAMS/en 102 1473789 5387603 5224519 2022-07-29T03:26:11Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{PluggableAuth Plugin}} {{Extension|templatemode = |name = NaylorAMS |status = stable |type1 = user identity |type2 = |hook1 = |hook2 = |newhook1 = |newhook2 = |username = |author = [[User:MyWikis-JeffreyWang|Jeffrey Wang]] for MyWikis LLC |maintainer = [https://www.mywikis.com MyWikis LLC] |description = Allows authentication using Naylor Association Management Software (Timberlake) |image = |imagesize = |version = 0.1.0 |update = |version preview = |update preview = |compatibility policy = master |mediawiki = 1.31+ |php = 7.0+ |needs-updatephp = no |composer = |table1 = |table2 = |license = GPL-2.0 |download = {{WikimediaDownload}}{{GithubDownload|mywikis|NaylorAMS|mastertarball=1}} |readme = {{git file|project=mediawiki/extensions/NaylorAMS|file=README|branch=HEAD|text=README}} |changelog = |example = |namespace = |parameters = <!-- configuration parameters, for use in LocalSettings.php --> |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |phabricator = |vagrant-role = }} The '''Naylor AMS''' extension extends {{ll|Extension:PluggableAuth|PluggableAuth}} to provide authentication for organizations using [https://www.naylor.com/member-management-solutions/association-management-software/ Naylor Association Management Software] (codename Timberlake). This extension will take the username, first and last name, and email address of a user from your organization's Naylor database and create a local MediaWiki account with the same username, email, and full name if one doesn't exist; otherwise, if a user with the same username exists, it logs them back into the local MediaWiki account. == Installation == {{Note|1=This extension requires {{ll|Extension:PluggableAuth|PluggableAuth}} 5.x to be installed first.}} The PHP cURL extension is required for this MediaWiki extension. {{ExtensionInstall |download-link = [https://github.com/mywikis/NaylorAMS/archive/main.tar.gz Download] |registration = required }} == Configuration parameters == For more information about these terms, please refer to the [https://masie.membershipsoftware.org/files/Naylor%20API%20Documentation.pdf Naylor AMS API documentation]. ; $wgNaylorAMS_BaseUrl : The base URL for your login system, provided by Naylor. Do not add a trailing slash at the end of the string. ('''required''') ; $wgNaylorAMS_SecurityKey : The security key provided by Naylor. ('''required''') ; $wgNaylorAMS_UsernameDenyList : An array of strings, with each string containing a local username. Used to prevent login via SSO to local-only accounts. Case sensitive; needs to follow MediaWiki username conventions. By default, the log in button says "Log in with Naylor AMS". To change the label, edit MediaWiki:Naylorams-loginbtn-text. == Disclaimer == This extension is ''not'' maintained by Naylor, nor has it been sponsored by Naylor. It was written by and is maintained by [https://www.mywikis.com/ MyWikis LLC] for the purpose of serving its customers who use Naylor AMS. In addition, the extension is currently not compatible with PluggableAuth 6.0 and above. Use the latest version of PluggableAuth 5.x in the meantime. == See also == * {{ll|Extension:PluggableAuth}} * {{ll|Extension:SimpleSAMLphp}} * {{ll|Extension:LDAPAuthentication2}} {{Used by|mywikis=1}} [[Category:Extensions by MyWikis{{#translation:}}]] [[Category:PluggableAuth plugins{{#translation:}}]] elsew8pwkpqtdaycps7zlqome4mrm8s Extension:NaylorAMS/ja 102 1473791 5387604 5224520 2022-07-29T03:26:11Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{PluggableAuth Plugin}} {{Extension|templatemode = |name = NaylorAMS |status = stable |type1 = user identity |type2 = |hook1 = |hook2 = |newhook1 = |newhook2 = |username = |author = [[User:MyWikis-JeffreyWang|Jeffrey Wang]] for MyWikis LLC |maintainer = [https://www.mywikis.com MyWikis LLC] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows authentication using Naylor Association Management Software (Timberlake)</span> |image = |imagesize = |version = 0.1.0 |update = |version preview = |update preview = |compatibility policy = master |mediawiki = 1.31+ |php = 7.0+ |needs-updatephp = no |composer = |table1 = |table2 = |license = GPL-2.0 |download = {{WikimediaDownload}}{{GithubDownload|mywikis|NaylorAMS|mastertarball=1}} |readme = {{git file|project=mediawiki/extensions/NaylorAMS|file=README|branch=HEAD|text=README}} |changelog = |example = |namespace = |parameters = <!-- configuration parameters, for use in LocalSettings.php --> |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |phabricator = |vagrant-role = }} The '''Naylor AMS''' extension extends {{ll|Extension:PluggableAuth|PluggableAuth}} to provide authentication for organizations using [https://www.naylor.com/member-management-solutions/association-management-software/ Naylor Association Management Software] (codename Timberlake). This extension will take the username, first and last name, and email address of a user from your organization's Naylor database and create a local MediaWiki account with the same username, email, and full name if one doesn't exist; otherwise, if a user with the same username exists, it logs them back into the local MediaWiki account. == インストール == {{Note|1=This extension requires {{ll|Extension:PluggableAuth|PluggableAuth}} 5.x to be installed first.}} The PHP cURL extension is required for this MediaWiki extension. {{ExtensionInstall |download-link = [https://github.com/mywikis/NaylorAMS/archive/main.tar.gz Download] |registration = required }} == 構成パラメーター == For more information about these terms, please refer to the [https://masie.membershipsoftware.org/files/Naylor%20API%20Documentation.pdf Naylor AMS API documentation]. ; $wgNaylorAMS_BaseUrl : The base URL for your login system, provided by Naylor. Do not add a trailing slash at the end of the string. ('''required''') ; $wgNaylorAMS_SecurityKey : The security key provided by Naylor. ('''required''') ; $wgNaylorAMS_UsernameDenyList : An array of strings, with each string containing a local username. Used to prevent login via SSO to local-only accounts. Case sensitive; needs to follow MediaWiki username conventions. By default, the log in button says "Log in with Naylor AMS". To change the label, edit MediaWiki:Naylorams-loginbtn-text. == 免責事項 == This extension is ''not'' maintained by Naylor, nor has it been sponsored by Naylor. It was written by and is maintained by [https://www.mywikis.com/ MyWikis LLC] for the purpose of serving its customers who use Naylor AMS. In addition, the extension is currently not compatible with PluggableAuth 6.0 and above. Use the latest version of PluggableAuth 5.x in the meantime. == 関連項目 == * {{ll|Extension:PluggableAuth}} * {{ll|Extension:SimpleSAMLphp}} * {{ll|Extension:LDAPAuthentication2}} {{Used by|mywikis=1}} [[Category:Extensions by MyWikis{{#translation:}}]] [[Category:PluggableAuth plugins{{#translation:}}]] 5o70xo4sm8scg036zxpso0osyrqqji5 Extension:NaylorAMS/ru 102 1475420 5387606 5224521 2022-07-29T03:26:13Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{PluggableAuth Plugin}} {{Extension|templatemode = |name = NaylorAMS |status = stable |type1 = user identity |type2 = |hook1 = |hook2 = |newhook1 = |newhook2 = |username = |author = [[User:MyWikis-JeffreyWang|Jeffrey Wang]] for MyWikis LLC |maintainer = [https://www.mywikis.com MyWikis LLC] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows authentication using Naylor Association Management Software (Timberlake)</span> |image = |imagesize = |version = 0.1.0 |update = |version preview = |update preview = |compatibility policy = master |mediawiki = 1.31+ |php = 7.0+ |needs-updatephp = no |composer = |table1 = |table2 = |license = GPL-2.0 |download = {{WikimediaDownload}}{{GithubDownload|mywikis|NaylorAMS|mastertarball=1}} |readme = {{git file|project=mediawiki/extensions/NaylorAMS|file=README|branch=HEAD|text=README}} |changelog = |example = |namespace = |parameters = <!-- configuration parameters, for use in LocalSettings.php --> |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |phabricator = |vagrant-role = }} The '''Naylor AMS''' extension extends {{ll|Extension:PluggableAuth|PluggableAuth}} to provide authentication for organizations using [https://www.naylor.com/member-management-solutions/association-management-software/ Naylor Association Management Software] (codename Timberlake). This extension will take the username, first and last name, and email address of a user from your organization's Naylor database and create a local MediaWiki account with the same username, email, and full name if one doesn't exist; otherwise, if a user with the same username exists, it logs them back into the local MediaWiki account. == Установка == {{Note|1=This extension requires {{ll|Extension:PluggableAuth|PluggableAuth}} 5.x to be installed first.}} The PHP cURL extension is required for this MediaWiki extension. {{ExtensionInstall |download-link = [https://github.com/mywikis/NaylorAMS/archive/main.tar.gz Download] |registration = required }} == Конфигурационные параметры == For more information about these terms, please refer to the [https://masie.membershipsoftware.org/files/Naylor%20API%20Documentation.pdf Naylor AMS API documentation]. ; $wgNaylorAMS_BaseUrl : The base URL for your login system, provided by Naylor. Do not add a trailing slash at the end of the string. ('''required''') ; $wgNaylorAMS_SecurityKey : The security key provided by Naylor. ('''required''') ; $wgNaylorAMS_UsernameDenyList : An array of strings, with each string containing a local username. Used to prevent login via SSO to local-only accounts. Case sensitive; needs to follow MediaWiki username conventions. By default, the log in button says "Log in with Naylor AMS". To change the label, edit MediaWiki:Naylorams-loginbtn-text. == Отказ от ответственности == This extension is ''not'' maintained by Naylor, nor has it been sponsored by Naylor. It was written by and is maintained by [https://www.mywikis.com/ MyWikis LLC] for the purpose of serving its customers who use Naylor AMS. In addition, the extension is currently not compatible with PluggableAuth 6.0 and above. Use the latest version of PluggableAuth 5.x in the meantime. <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * {{ll|Extension:PluggableAuth}} * {{ll|Extension:SimpleSAMLphp}} * {{ll|Extension:LDAPAuthentication2}} {{Used by|mywikis=1}} [[Category:Extensions by MyWikis{{#translation:}}]] [[Category:PluggableAuth plugins{{#translation:}}]] r5ym4ouc1jyl3kvf91t0q9y3uqmklcd Extension:PageAuthors/ru 102 1475453 5387166 5385399 2022-07-28T21:09:08Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension | status = stable | type = parser function | username = Sophivorus | description = <span lang="en" dir="ltr" class="mw-content-ltr">Get a sensible list of page authors</span> | update = 2022-07-28 | version = 1.2 | license = GPL-3.0-or-later | mediawiki = 1.35+ | php = 7+ | download = {{WikimediaDownload}} | needs-updatephp = No | example = [https://www.appropedia.org] }} The '''PageAuthors''' extension introduces a magic word <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> that returns a list of the main page authors of a page, sorted by number of bytes added. The extension is highly configurable so you can fine-tune what counts as an author. == Установка == {{ExtensionInstall | registration = required }} == Использование == Simply add <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> to any page and you will get a comma-separated list of the main authors of the current page, sorted by number of bytes added. See [[#Configuration|#Configuration]] to define your own criteria of what counts as an author. You can also do <code><nowiki>{{PAGEAUTHORS:Some page}}</nowiki></code> to get the list of authors for some page other than the current one. The list of authors can be further processed using [[Extension:Arrays]] or the [[Extension:Page Forms/Page Forms and templates##arraymap|#arraymap function of the PageForms extension]], for example to link to the relevant user pages. {{anchor|Configuration}} == Настройка == Each configuration is shown with its default value: * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerAuthor = 100;</syntaxhighlight> ― Minimum number of bytes added that each author must reach in order to be considered an author. * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerEdit = 10;</syntaxhighlight> ― Minimum number of bytes that each edit must reach in order to be counted towards the author's total. Having a positive value here already means that edits that reduce content don't count, which is usually desirable because even though synthesizing and removing problematic content is often valuable, we wouldn't say that makes you an ''author'' of the existing content. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreMinorEdits = true;</syntaxhighlight> ― Whether to ignore edits marked as minor. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBlocked = true;</syntaxhighlight> ― Whether to ignore blocked users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreAnons = true;</syntaxhighlight> ― Whether to ignore anonymous users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBots = true;</syntaxhighlight> ― Whether to ignore bots. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSystemUsers = true;</syntaxhighlight> ― Whether to ignore system users (such as in mass imports). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSummaryPatterns = [ '/Undo.*/', '/Revert.*/' ];</syntaxhighlight> ― Ignore edits with edit summaries that match these [https://www.php.net/manual/en/reference.pcre.pattern.syntax.php PHP regex patterns]. By default, edits with edit summaries that start with 'Undo' or 'Revert' will be ignored (these match the default edit summaries when doing a revert or a rollback in an English wiki). So for example, if some vandal blanks a page and then a user reverts it, the revert won't count towards the byte count of the user. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreUsers = [];</syntaxhighlight> ― Ignore edits by these users (without "User:" prefix). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreGroups = [];</syntaxhighlight> ― Ignore edits by these groups. * <syntaxhighlight lang=php inline>$wgPageAuthorsDelimiter = ', ';</syntaxhighlight> ― Delimiter between authors. == См. также == * [[Manual:$wgMaxCredits]] - A built-in option to list the latest author followed by others in order of most recent edit, in the wiki footer. * [[Extension:Contributors]] - Lists authors by edit count. This is not reliable because some users tend to do few but big edits while others tend to do many small ones. Extreme but real cases include pages where the initial author creates the entire page in a single huge edit while other later editors make multiple edits fixing trivial issues. * [[Extension:SemanticExtraSpecialProperties]] - The _EUSER property lists authors by chronological order. This is not reliable either because while it's often the case that the first few editors are the main authors, it also happens that later editors contribute significantly and may even rewrite the entire page. 7u6pfwdvzpaup0s7mw22fg96ajgu0tb Extension:PageAuthors/nan 102 1476770 5387164 5385398 2022-07-28T21:09:06Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension | status = stable | type = parser function | username = Sophivorus | description = Tit-tshú ia̍h-bīn tsok-tsiá ê ha̍p-lí tshing-tuann | update = 2022-07-28 | version = 1.2 | license = GPL-3.0-or-later | mediawiki = 1.35+ | php = 7+ | download = {{WikimediaDownload}} | needs-updatephp = No | example = [https://www.appropedia.org] }} The '''PageAuthors''' extension introduces a magic word <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> that returns a list of the main page authors of a page, sorted by number of bytes added. The extension is highly configurable so you can fine-tune what counts as an author. == An-tsong == {{ExtensionInstall | registration = required }} == Sú-iōng == Simply add <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> to any page and you will get a comma-separated list of the main authors of the current page, sorted by number of bytes added. See [[#Configuration|#Configuration]] to define your own criteria of what counts as an author. You can also do <code><nowiki>{{PAGEAUTHORS:Some page}}</nowiki></code> to get the list of authors for some page other than the current one. The list of authors can be further processed using [[Extension:Arrays]] or the [[Extension:Page Forms/Page Forms and templates##arraymap|#arraymap function of the PageForms extension]], for example to link to the relevant user pages. {{anchor|Configuration}} == Phuè-tī == Each configuration is shown with its default value: * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerAuthor = 100;</syntaxhighlight> ― Minimum number of bytes added that each author must reach in order to be considered an author. * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerEdit = 10;</syntaxhighlight> ― Minimum number of bytes that each edit must reach in order to be counted towards the author's total. Having a positive value here already means that edits that reduce content don't count, which is usually desirable because even though synthesizing and removing problematic content is often valuable, we wouldn't say that makes you an ''author'' of the existing content. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreMinorEdits = true;</syntaxhighlight> ― Whether to ignore edits marked as minor. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBlocked = true;</syntaxhighlight> ― Whether to ignore blocked users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreAnons = true;</syntaxhighlight> ― Whether to ignore anonymous users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBots = true;</syntaxhighlight> ― Whether to ignore bots. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSystemUsers = true;</syntaxhighlight> ― Whether to ignore system users (such as in mass imports). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSummaryPatterns = [ '/Undo.*/', '/Revert.*/' ];</syntaxhighlight> ― Ignore edits with edit summaries that match these [https://www.php.net/manual/en/reference.pcre.pattern.syntax.php PHP regex patterns]. By default, edits with edit summaries that start with 'Undo' or 'Revert' will be ignored (these match the default edit summaries when doing a revert or a rollback in an English wiki). So for example, if some vandal blanks a page and then a user reverts it, the revert won't count towards the byte count of the user. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreUsers = [];</syntaxhighlight> ― Ignore edits by these users (without "User:" prefix). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreGroups = [];</syntaxhighlight> ― Ignore edits by these groups. * <syntaxhighlight lang=php inline>$wgPageAuthorsDelimiter = ', ';</syntaxhighlight> ― Delimiter between authors. == Tsham-ua̍t == * [[Manual:$wgMaxCredits]] - A built-in option to list the latest author followed by others in order of most recent edit, in the wiki footer. * [[Extension:Contributors]] - Lists authors by edit count. This is not reliable because some users tend to do few but big edits while others tend to do many small ones. Extreme but real cases include pages where the initial author creates the entire page in a single huge edit while other later editors make multiple edits fixing trivial issues. * [[Extension:SemanticExtraSpecialProperties]] - The _EUSER property lists authors by chronological order. This is not reliable either because while it's often the case that the first few editors are the main authors, it also happens that later editors contribute significantly and may even rewrite the entire page. prwukt6roqbwtmippunpplblej34wi5 Growth/FAQ/ru 0 1482861 5387840 5378643 2022-07-29T10:15:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''Добро пожаловать в ЧАВО Команды Роста!''' Надеемся, что здесь вы найдёте ответы на все вопросы, которые у вас появятся. Если это не так, [[Talk:Growth|дайте нам знать]]. ''Примечание для переводчиков: эта страница регулярно обновляется, что может усложнить вашу работу. Мы стараемся избежать таких неудобств.'' == Основное == {{Anchor|features}} === Над чем вы работаете? === * [[Special:MyLanguage/Growth/Feature summary#NH|'''Домашняя страница новичка''']]: новая служебная страница, помогающая новичку освоиться в Википедии. На ней находятся: ** <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NT|'''Newcomer tasks''']]: a feed of task suggestions that help newcomers learn to edit. Newcomers have been making [[NEWTEA|productive edits]] through this feed! [[Help:Growth/Tools/Suggested edits|Know more about this tool]].</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Mentorship module''' [optional module]: each newcomers has a direct link to an experienced user. This way, they can ask questions about editing Wikipedia, less the need to find where to ask for assistance.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Impact module''': the user sees how many pages views articles they edit received.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#HP|'''Help panel''']]: a platform to provide resources to newcomers while they are editing. If they choose one of the suggested tasks on the newcomer homepage, they are guided step-by-step on the process of editing.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''[[Growth/Understanding first day|Welcome Survey]]''': communities can know why newcomers create an account on Wikipedia.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You can have a look at '''[[Special:MyLanguage/Growth/Feature summary|our features summary]]''' to know more about it. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === On which wikis Growth features have been deployed? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find a list of wikis on our [[Special:MyLanguage/Growth/Deployment table|Deployment table]]. This page lists features activation per wiki as well. </div> {{anchor|NEWTEA}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Are Growth features effective? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[NEWTEA|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that newcomers make their first article edit (+11.6%)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that they are retained as editors</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the number of edits they make during their first couple of weeks on the wiki (+22%)</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This deployment has been achieved in October 2021.</span> {{anchor|translate}} <div lang="en" dir="ltr" class="mw-content-ltr"> === The interface is partially translated. How can I change this? === </div> [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] <div lang="en" dir="ltr" class="mw-content-ltr"> It takes up to one week to see new translations being deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Special pages names require a special process. For the following strings, [[Talk:Growth|please contact us]] directly with the translations: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. </div> {{anchor|enable|test}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I test the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[Growth/Deployment table|On wikis where the Growth features are available]], and also on [https://test.wikipedia.org test.wikipedia.org], go to your [[Special:Preferences#mw-prefsection-personal|user preferences]] on one of these wikis and then: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Help panel''' in the ''{{int|prefs-editing}}'' tab.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Newcomer homepage''' in the ''{{int|prefs-personal}}'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work.</span> {{anchor|get}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can my wiki get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[#features|these features]], with the following conditions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Do you plan to deploy the features outside of Wikipedia? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Please contact us [[Talk:Growth|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> We are considering working with [[Growth/Communities/Wikisource|Wikisource communities]]. </div> {{anchor|pilot|ambassador}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can you clarify what "Pilot wikis", "Control group wikis" and "Ambassadors" are? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''Pilot wikis''' are wikis who have a close collaboration with the Growth team. They are involved in projects definitions and early review of the projects. They also test all prototypes first. The Growth team can contact some other wikis for some of these steps. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, our pilot wikis are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I use the Growth features on mobile ? On the official apps (iOS, Android)? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Access to the features == </div> {{anchor|ABtest}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can new accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where no [[A/B testing|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where an [[A/B testing|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How can existing accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], anyone can find the features [[#enable|in their Preferences]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === I host a workshop. How can I control if my students get the features when they create an account? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is possible to have a link parameter to control access to the features: </div> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=1</code> will force Growth features at account creation</span> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=0</code> will force the default experience at account creation</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[Talk:Growth|Please let us know]] if you plan to use these parameters. </div> {{anchor|Homepage}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Homepage == </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> === How to access the Homepage? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My email is requested, or my email is displayed at the top of the Homepage. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[Special:MyLanguage/Help:Notifications|notifications]], like when they are mentioned by other users on wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The email address won't be visible by other users. Communication with other users all happen on the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === The help links displayed on the homepage are not relevant. How to change them? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#HP|the same as on the Help panel]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Suggested edits == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How does Suggested Edits work ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How topics and tasks are suggested? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === SuggestedEdits' supervision and troubleshooting === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can I monitor which articles have been edited as Suggested edits? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to monitor which topics or which tasks need more articles? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please use <code>Special:NewcomerTasksInfo</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I don't have any task for a given combination. Is it normal? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== A user uses the tools in an nonconstructive way. What can I do? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Overall, users make [[#NEWTEA|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">try to understand what the use tries to do,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">contact this user, explain the situation, ask them for details and guide them to a different path if it exists,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">if the nonconstructive behavior persists, then block the user.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If repetitive and similar nonconstructive edits are made at your wiki, [[Talk:Growth|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you activated the Help panel in your preferences? If yes, [[Talk:Growth|please let us know about this issue]]. </div> {{anchor|config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Suggested edits configuration === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to provide more tasks for newcomers? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: </div> {| class="wikitable" !'''<span lang="en" dir="ltr" class="mw-content-ltr">Task</span>''' !<span lang="en" dir="ltr" class="mw-content-ltr">Level of difficulty</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Goal of the task</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Copyedit article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">fix spelling, grammar and tone</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add Links</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">add links between articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Update article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">bring existing articles up-to-date</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add References</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">find sources for existing articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Expand article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">hard</span> |<span lang="en" dir="ltr" class="mw-content-ltr">expand stubs to become sourced articles</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Add other templates that match the definition of the task to <code>Special:EditGrowthConfig</code> on your wiki</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add maintenance templates to more articles on your wiki.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is not possible at the moment. [[Talk:Growth|Please let us know]] about your potential project. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add a link === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Special:MyLanguage/Growth/Deployment table|where ''Structured tasks - Add a link'' has been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">"Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users have to decide if a link should be added or not added. These links are suggested by a machine.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which wikis have Structured tasks - Add a link ? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the accuracy of Structured tasks - Add a link predictions? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The predictions are, on average, accurate at 70%. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add an image === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the purpose of "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which rules define the work done by "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have several rules: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Only articles where no image is displayed are taken into consideration for images addition.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Articles with an infobox but no image aren't taken into consideration for now.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which types of users have been contacted to test this new concept ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">people who aren't wiki editors (using UserTesting.com, in English and Spanish)</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia.</span> {{anchor|HP}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Help panel == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We want to change some links displayed on the Help panel. How to do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#Homepage|also used on the Homepage]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where does questions posted using the Help panel goes? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, these questions go the the local Help desk. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should go the newcomer's mentors,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should be posted at the help desk.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change this configuration using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page.</span> {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration and operation of the mentoring system == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My wiki doesn't have the Growth mentoring system. How can I set it up? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The next steps are a summary of the process. The full process is described on [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|this dedicated page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, you need to check if the Growth tools are [[Growth/Deployment table|deployed at your wiki]]. If it is not yet the case, please see [[#get|how to get the features]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Then, you have to find some other mentors to volunteer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All mentors have to sign-up on a specific page, using [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a specific syntax]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> At your wiki, an admin has to add the mentor list to the configuration page (<code>Special:EditGrowthConfig</code>). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many mentors does a wiki need? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We recommend to have at least 3 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How mentors are assigned to newcomers? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Each new account receives a mentor randomly taken from a list of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many messages does a mentor receive per week? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Have you considered to assign a mentor only to people who already made some edits? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We don't know what each newcomer needs. [[Special:MyLanguage/New Editor Experiences|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. </div> {{anchor|existing}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[d:Q3919128|listed on Wikidata]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: </div> '''<span lang="en" dir="ltr" class="mw-content-ltr">Replace your mentoring system with the new one</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">If your mentoring system hasn't much success, it could be replaced by the Growth team features.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">Have both systems working together</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">You can imagine to have two roles:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Growth mentoring takes care of the newcomers basic questions,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The existing mentoring can take care of newcomers who are more involved.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> In this case, you might have to locally translate the interface for Growth features using your own terms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where can I signup as a mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Your community may have defined some conditions to become a mentor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How do I introduce myself as a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you sign up to become a mentor, the following syntax must be used, with: </div> <code>* <nowiki>[[</nowiki><span lang="en" dir="ltr" class="mw-content-ltr">User:Username</span><nowiki>]]</nowiki>|<span lang="en" dir="ltr" class="mw-content-ltr">Description</span></code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|<span lang="en" dir="ltr" class="mw-content-ltr">Read more about this</span>]] {{anchor|reassign}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can we reassign a newcomer to a different mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes, it is possible using <code>Special:ClaimMentee</code>. </div> {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === A mentor just quit. Can we reassign all their newcomer to different mentors? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can use <code>Special:ClaimMentee</code> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[Talk:Growth|please contact us]] directly. </div> {{anchor|magicword}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Type the magic word <code><nowiki>{{#mentor:Foo}}</nowiki></code> in a wikitext page, and preview. "Foo" has to be replaced by the username you target. This will display the name of Foo's mentor. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[#reassign|If the mentor changes]], then the magic word picks the new mentor's name. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can "[[Special:MyLanguage/Help:Substitution|subst:]]" this message if needed: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Foo's mentor will then be saved as wikitext. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you updated <code>Special:EditGrowthConfig</code> with the new page name? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Interactions between mentors and newcomers == </div> {{Anchor|questions}} <div lang="en" dir="ltr" class="mw-content-ltr"> === What kinds of questions do newcomers ask? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> From the observations we have made, questions are mostly about basic editing. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on communities experiences, the Growth team worked [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|on a guide for mentors]] who have to reply to these questions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Newcomers haven't replied to my messages. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Two possible cases there: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can I ask if my mentor is not responding to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I ask to have a different mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[#reassign|make the change]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, how can I monitor the newcomers assigned to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are currently working on a [[Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is available at all Wikipedias where [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|a list of mentors has been created and activated]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At wikis where the mentor dashboard is deployed, a new filter is available for mentors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They can monitor their mentees' activity in Watchlist and RecentChanges.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|not listed as mentors]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> tah7myz73ewrpgjlhkg1g0v8pqb6oxo Manual:Installation guide/hy 100 1487238 5386653 5381090 2022-07-28T17:14:29Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki/hy]] eci37ngmg2b0zbkecaybn8fpvk8b59g 5386690 5386653 2022-07-28T17:25:53Z Pppery 5901069 Changed redirect target from [[Manual:Installing MediaWiki/hy]] to [[Manual:Installing MediaWiki]] wikitext text/x-wiki #REDIRECT [[Manual:Installing MediaWiki]] 8wae392cwc84ue6hheoggvol6nlzf6u Translations:Manual:Installation guide/11/hy 1198 1487283 5387297 5013687 2022-07-28T21:58:49Z Baris6161TURK 17188421 wikitext text/x-wiki Պատկերի մանրապատկերում պահանջում է լրացուցիչ ծրագրեր։ $1 (պահանջվում է VisualEditor) և այլ ծառայություններն ունեն իրենց սեփական պահանջները։ fvxvxizceqjibx883c2isk9hjemw6u4 Translations:Manual:Installation guide/11/de-formal 1198 1487665 5387298 5015269 2022-07-28T21:59:00Z Baris6161TURK 17188421 wikitext text/x-wiki Image thumbnailing erfordert zusätzliche Programme. $1 (erforderlich von VisualEditor) und andere Dienste haben ihre eigenen Anforderungen. 6u6ovie0276brxgjx06ds6xboeigwju Wikimedia Product/fi 0 1487982 5387576 5358194 2022-07-29T03:25:44Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span></span>]] * [[Readers|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Readers</span></span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Programs</span> === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''<span lang="en" dir="ltr" class="mw-content-ltr">Other:</span>''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|Verkko]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Page:</span> [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Goals</span> == {|class="wikitable" |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2019–2020</span> | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2018–2019</span> | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2017–2018</span> | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2016–2017</span> | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2017</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2017</span>]] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">2015–2016</span> | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2015</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2016</span>]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2016</span>]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] 8gdobxc7lvrz7ut7042vot42wxwxu7i Extension:PageAuthors/cs 102 1490618 5387161 5385394 2022-07-28T21:09:03Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension | status = stable | type = parser function | username = Sophivorus | description = <span lang="en" dir="ltr" class="mw-content-ltr">Get a sensible list of page authors</span> | update = 2022-07-28 | version = 1.2 | license = GPL-3.0-or-later | mediawiki = 1.35+ | php = 7+ | download = {{WikimediaDownload}} | needs-updatephp = No | example = [https://www.appropedia.org] }} The '''PageAuthors''' extension introduces a magic word <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> that returns a list of the main page authors of a page, sorted by number of bytes added. The extension is highly configurable so you can fine-tune what counts as an author. == Instalace == {{ExtensionInstall | registration = required }} == Použití == Simply add <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> to any page and you will get a comma-separated list of the main authors of the current page, sorted by number of bytes added. See [[#Configuration|#Configuration]] to define your own criteria of what counts as an author. You can also do <code><nowiki>{{PAGEAUTHORS:Some page}}</nowiki></code> to get the list of authors for some page other than the current one. The list of authors can be further processed using [[Extension:Arrays]] or the [[Extension:Page Forms/Page Forms and templates##arraymap|#arraymap function of the PageForms extension]], for example to link to the relevant user pages. {{anchor|Configuration}} == Konfigurace == Each configuration is shown with its default value: * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerAuthor = 100;</syntaxhighlight> ― Minimum number of bytes added that each author must reach in order to be considered an author. * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerEdit = 10;</syntaxhighlight> ― Minimum number of bytes that each edit must reach in order to be counted towards the author's total. Having a positive value here already means that edits that reduce content don't count, which is usually desirable because even though synthesizing and removing problematic content is often valuable, we wouldn't say that makes you an ''author'' of the existing content. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreMinorEdits = true;</syntaxhighlight> ― Whether to ignore edits marked as minor. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBlocked = true;</syntaxhighlight> ― Whether to ignore blocked users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreAnons = true;</syntaxhighlight> ― Whether to ignore anonymous users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBots = true;</syntaxhighlight> ― Whether to ignore bots. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSystemUsers = true;</syntaxhighlight> ― Whether to ignore system users (such as in mass imports). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSummaryPatterns = [ '/Undo.*/', '/Revert.*/' ];</syntaxhighlight> ― Ignore edits with edit summaries that match these [https://www.php.net/manual/en/reference.pcre.pattern.syntax.php PHP regex patterns]. By default, edits with edit summaries that start with 'Undo' or 'Revert' will be ignored (these match the default edit summaries when doing a revert or a rollback in an English wiki). So for example, if some vandal blanks a page and then a user reverts it, the revert won't count towards the byte count of the user. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreUsers = [];</syntaxhighlight> ― Ignore edits by these users (without "User:" prefix). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreGroups = [];</syntaxhighlight> ― Ignore edits by these groups. * <syntaxhighlight lang=php inline>$wgPageAuthorsDelimiter = ', ';</syntaxhighlight> ― Delimiter between authors. == Viz též == * [[Manual:$wgMaxCredits]] - A built-in option to list the latest author followed by others in order of most recent edit, in the wiki footer. * [[Extension:Contributors]] - Lists authors by edit count. This is not reliable because some users tend to do few but big edits while others tend to do many small ones. Extreme but real cases include pages where the initial author creates the entire page in a single huge edit while other later editors make multiple edits fixing trivial issues. * [[Extension:SemanticExtraSpecialProperties]] - The _EUSER property lists authors by chronological order. This is not reliable either because while it's often the case that the first few editors are the main authors, it also happens that later editors contribute significantly and may even rewrite the entire page. gob0yi9fto2k6qqdpv3akgbc8ugnl5u MediaWiki 1.39/Roadmap 0 1495875 5386606 5382638 2022-07-28T16:26:01Z 105.105.76.253 1.39.wmf.22 is deployed to group 1 wikitext text/x-wiki {{Wikimedia engineering project information | name = MediaWiki 1.39 | description = Deployment of MediaWiki 1.39.0-wmf.XX versions and release of [[MediaWiki 1.39]] | start = 2022-03-21 | end = 2022-08-22 | group = [[Wikimedia Release Engineering Team|Release Engineering]] | previous = [[MediaWiki 1.38/Roadmap|MediaWiki 1.38]] | next = [[MediaWiki 1.40/Roadmap|MediaWiki 1.40]] | projectpage = MediaWiki 1.39 | display = {{{display|}}} }} == Timeline == Wikimedia deployments of MediaWiki 1.39 alpha versions will happen on weekly intervals, within a longer stretch (approximately 6 months) between publishing releases of the installer for third-party users. '''Current status:''' {{In progress}} {{-}} == Schedule for the deployments == See [[wikitech:Deployments]] for current schedule, dates, and times. See [https://versions.toolforge.org/ status board] for current status. Below is a summary: {{WMFReleaseTableHead}} {{WMFReleaseTableRow|25|2022-08-15|}} {{WMFReleaseTableRow|23|2022-08-01|}} {{WMFReleaseTableRow|22|2022-07-25|1}} {{WMFReleaseTableRow|21|2022-07-18|2}} {{WMFReleaseTableRow|19|2022-07-04|2}} {{WMFReleaseTableRow|18|2022-06-27|2}} {{WMFReleaseTableRow|17|2022-06-20|2}} {{WMFReleaseTableRow|16|2022-06-13|2}} {{WMFReleaseTableRow|15|2022-06-06|2}} {{WMFReleaseTableRow|14|2022-05-30|2}} {{WMFReleaseTableRow|13|2022-05-23|2}} {{WMFReleaseTableRow|12|2022-05-16|2}} {{WMFReleaseTableRow|10|2022-05-02|2}} {{WMFReleaseTableRow|9|2022-04-25|2|Deployed on 2022-04-26|Deployed on 2022-04-27|Deployed on 2022-04-28}} {{WMFReleaseTableRow|8|2022-04-18|2}} {{WMFReleaseTableRow|7|2022-04-11|2}} {{WMFReleaseTableRow|6|2022-04-04|2}} {{WMFReleaseTableRow|5|2022-03-29|2}} {{WMFReleaseTableRow|4|2022-03-23|2||Deployed on 2022-03-23|Deployed on 2022-03-23}} {{WMFReleaseTableRow|3|2022-03-22|2||Deployed on 2022-03-22|Deployed on 2022-03-22}} {{WMFReleaseTableRow|2|2022-03-22|2||Deployed on 2022-03-22|Deployed on 2022-03-22}} {{WMFReleaseTableRow|1|2022-03-21|2||Deployed on 2022-03-21|Deployed on 2022-03-22}} {{WMFReleaseTableFooter}} 2co7r69q5twfajhmrymgre0g36qz4yd 5387221 5386606 2022-07-28T21:22:04Z Jdforrester (WMF) 574543 We're extending the 1.39 alphas for a few weeks more. wikitext text/x-wiki {{Wikimedia engineering project information | name = MediaWiki 1.39 | description = Deployment of MediaWiki 1.39.0-wmf.XX versions and release of [[MediaWiki 1.39]] | start = 2022-03-21 | end = 2022-09-05 | group = [[Wikimedia Release Engineering Team|Release Engineering]] | previous = [[MediaWiki 1.38/Roadmap|MediaWiki 1.38]] | next = [[MediaWiki 1.40/Roadmap|MediaWiki 1.40]] | projectpage = MediaWiki 1.39 | display = {{{display|}}} }} == Timeline == Wikimedia deployments of MediaWiki 1.39 alpha versions will happen on weekly intervals, within a longer stretch (approximately 6 months) between publishing releases of the installer for third-party users. '''Current status:''' {{In progress}} {{-}} == Schedule for the deployments == See [[wikitech:Deployments]] for current schedule, dates, and times. See [https://versions.toolforge.org/ status board] for current status. Below is a summary: {{WMFReleaseTableHead}} {{WMFReleaseTableRow|28|2022-09-05|}} {{WMFReleaseTableRow|27|2022-08-29|}} {{WMFReleaseTableRow|26|2022-08-22|}} {{WMFReleaseTableRow|25|2022-08-15|}} {{WMFReleaseTableRow|23|2022-08-01|}} {{WMFReleaseTableRow|22|2022-07-25|1}} {{WMFReleaseTableRow|21|2022-07-18|2}} {{WMFReleaseTableRow|19|2022-07-04|2}} {{WMFReleaseTableRow|18|2022-06-27|2}} {{WMFReleaseTableRow|17|2022-06-20|2}} {{WMFReleaseTableRow|16|2022-06-13|2}} {{WMFReleaseTableRow|15|2022-06-06|2}} {{WMFReleaseTableRow|14|2022-05-30|2}} {{WMFReleaseTableRow|13|2022-05-23|2}} {{WMFReleaseTableRow|12|2022-05-16|2}} {{WMFReleaseTableRow|10|2022-05-02|2}} {{WMFReleaseTableRow|9|2022-04-25|2|Deployed on 2022-04-26|Deployed on 2022-04-27|Deployed on 2022-04-28}} {{WMFReleaseTableRow|8|2022-04-18|2}} {{WMFReleaseTableRow|7|2022-04-11|2}} {{WMFReleaseTableRow|6|2022-04-04|2}} {{WMFReleaseTableRow|5|2022-03-29|2}} {{WMFReleaseTableRow|4|2022-03-23|2||Deployed on 2022-03-23|Deployed on 2022-03-23}} {{WMFReleaseTableRow|3|2022-03-22|2||Deployed on 2022-03-22|Deployed on 2022-03-22}} {{WMFReleaseTableRow|2|2022-03-22|2||Deployed on 2022-03-22|Deployed on 2022-03-22}} {{WMFReleaseTableRow|1|2022-03-21|2||Deployed on 2022-03-21|Deployed on 2022-03-22}} {{WMFReleaseTableFooter}} h11xf47ev4ssxyhs24j7uvcmikf7pss 5387744 5387221 2022-07-29T08:10:05Z 105.105.76.253 /* Schedule for the deployments */1.39.wmf.22 was deployed to group 2 wikitext text/x-wiki {{Wikimedia engineering project information | name = MediaWiki 1.39 | description = Deployment of MediaWiki 1.39.0-wmf.XX versions and release of [[MediaWiki 1.39]] | start = 2022-03-21 | end = 2022-09-05 | group = [[Wikimedia Release Engineering Team|Release Engineering]] | previous = [[MediaWiki 1.38/Roadmap|MediaWiki 1.38]] | next = [[MediaWiki 1.40/Roadmap|MediaWiki 1.40]] | projectpage = MediaWiki 1.39 | display = {{{display|}}} }} == Timeline == Wikimedia deployments of MediaWiki 1.39 alpha versions will happen on weekly intervals, within a longer stretch (approximately 6 months) between publishing releases of the installer for third-party users. '''Current status:''' {{In progress}} {{-}} == Schedule for the deployments == See [[wikitech:Deployments]] for current schedule, dates, and times. See [https://versions.toolforge.org/ status board] for current status. Below is a summary: {{WMFReleaseTableHead}} {{WMFReleaseTableRow|28|2022-09-05|}} {{WMFReleaseTableRow|27|2022-08-29|}} {{WMFReleaseTableRow|26|2022-08-22|}} {{WMFReleaseTableRow|25|2022-08-15|}} {{WMFReleaseTableRow|23|2022-08-01|}} {{WMFReleaseTableRow|22|2022-07-25|2}} {{WMFReleaseTableRow|21|2022-07-18|2}} {{WMFReleaseTableRow|19|2022-07-04|2}} {{WMFReleaseTableRow|18|2022-06-27|2}} {{WMFReleaseTableRow|17|2022-06-20|2}} {{WMFReleaseTableRow|16|2022-06-13|2}} {{WMFReleaseTableRow|15|2022-06-06|2}} {{WMFReleaseTableRow|14|2022-05-30|2}} {{WMFReleaseTableRow|13|2022-05-23|2}} {{WMFReleaseTableRow|12|2022-05-16|2}} {{WMFReleaseTableRow|10|2022-05-02|2}} {{WMFReleaseTableRow|9|2022-04-25|2|Deployed on 2022-04-26|Deployed on 2022-04-27|Deployed on 2022-04-28}} {{WMFReleaseTableRow|8|2022-04-18|2}} {{WMFReleaseTableRow|7|2022-04-11|2}} {{WMFReleaseTableRow|6|2022-04-04|2}} {{WMFReleaseTableRow|5|2022-03-29|2}} {{WMFReleaseTableRow|4|2022-03-23|2||Deployed on 2022-03-23|Deployed on 2022-03-23}} {{WMFReleaseTableRow|3|2022-03-22|2||Deployed on 2022-03-22|Deployed on 2022-03-22}} {{WMFReleaseTableRow|2|2022-03-22|2||Deployed on 2022-03-22|Deployed on 2022-03-22}} {{WMFReleaseTableRow|1|2022-03-21|2||Deployed on 2022-03-21|Deployed on 2022-03-22}} {{WMFReleaseTableFooter}} 5fb1ebgrr58n20e48mbfxnvovxo6hq4 Talk pages project/Usability/Prototype/Topic Containers 0 1502973 5387133 5180017 2022-07-28T20:45:40Z SGrabarczuk (WMF) 9240933 -empty line wikitext text/x-wiki <languages /> [[<translate nowrap><!--T:39--> File:Topic Container Screenshot.png</translate>|alt=<translate><!--T:1--> Screenshot showing proposed design of a new way of displaying section headings on talk pages.</translate>|thumb|400px|<translate><!--T:2--> This project will change the appearance of talk page section heading and introduce new information about the discussions that happen within them.</translate>]] <big><translate><!--T:3--> Welcome!</translate></big> <translate><!--T:4--> This page has instructions for testing a <strong>desktop prototype</strong> of a new part of the [[<tvar name=1>Special:MyLanguage/Talk pages project</tvar>|Talk pages project]].</translate> <translate><!--T:5--> This new project changes the <code>==Section headings==</code> on talk pages.</translate> <strong><translate><!--T:6--> Goals:</translate></strong> # <translate><!--T:7--> <strong>People who are new to editing</strong> quickly recognize that talk pages are places to communicate with other volunteers.</translate> # <translate><!--T:8--> <strong>People who are experienced with editing</strong> can quickly find the conversations they want to join.</translate> {{anchor|Try the prototype}} <translate> == Try the prototype == <!--T:9--> </translate> # <translate><!--T:10--> Visit this <strong>test</strong> wiki:</translate> <strong><mark><translate><!--T:35--> [https://patchdemo.wmflabs.org/wikis/7eb90cd880/wiki/Talk:DiscussionTools]</translate></mark></strong> # <translate><!--T:11--> Log in to the wiki.</translate> <translate><!--T:37--> You can use one of these accounts. The password for these accounts is <code>testsecret‎</code></translate> #* <code><translate><!--T:40--> Alice</translate></code> #* <code><translate><!--T:41--> Bob</translate></code> #* <code><translate><!--T:42--> Carol</translate></code> #* <code><translate><!--T:43--> Erin</translate></code> # <translate><!--T:36--> Visit this <mark><strong>[https://patchdemo.wmflabs.org/wikis/7eb90cd880/wiki/Talk:DiscussionTools article talk page]</strong></mark> or this <mark><strong>[https://patchdemo.wmflabs.org/wikis/7eb90cd880/wiki/User_talk:Bob user talk page]</strong></mark>.</translate> # <translate><!--T:13--> Try to find the discussion that has been edited most recently.</translate> # <translate><!--T:14--> Try to find the discussion that has the most people participating in it.</translate> # <translate><!--T:15--> Try to find the discussion with the most comments.</translate> # <translate><!--T:16--> Scroll back to the discussion you identified in "Step 4." and figure out how you would do the following:</translate> ## <translate><!--T:17--> Subscribe to the discussion, so that you will be notified when new comments are posted in it.</translate> ## <translate><!--T:18--> Post a reply in the discussion.</translate> ## <translate><!--T:19--> Edit the reply you posted.</translate> # ✅ <translate><!--T:20--> That is it!</translate> <translate><!--T:21--> You are now ready to [[<tvar name=1>#Share your feedback</tvar>|share your feedback]].</translate> {{anchor|Share your feedback}} <translate> == Share your feedback == <!--T:38--> </translate> {| class="wikitable float{{dir|{{pagelang}}|left|right}}" |+ | style="background-color:#ffffee;" |<translate><!--T:22--> If you prefer, you can send an e-mail message instead:</translate> talkpageconsultation{{@}}wikimedia.org |} <translate><!--T:23--> After you complete the instructions listed in the [[<tvar name=1>#Try the prototype</tvar>|Try the prototype]] section, please share your thoughts.</translate> # <translate><!--T:24--> Go to [<tvar name=1>https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype/Topic_Containers</tvar> the talk page].</translate> # <translate><!--T:25--> Click the <code>Start a new topic</code> textbox.</translate> # <translate><!--T:26--> Type <code>Feedback: YOUR USERNAME</code></translate> # <translate><!--T:27--> Write answers to these questions. <strong>You can write in your language.</strong></translate> ## <em><translate><!--T:28--> What did you find unexpected about the prototype?</translate></em> ## <em><translate><!--T:29--> Which – if any – of the steps in the "Try the Prototype" section were you uncertain about?</translate></em> ## <em><translate><!--T:30--> What do you appreciate about the prototype?</translate></em> ## <em><translate><!--T:31--> What do you wish was different about the prototype?</translate></em> ## <em><translate><!--T:32--> OPTIONAL: Can you imagine this design <em>not</em> working on some pages? If you can, please share links to these pages. It would be very helpful.</translate></em> # <translate><!--T:33--> Click the blue "<tvar name=1>{{int|flow-newtopic-save}}</tvar>" button.</translate> # ✅ <translate><!--T:34--> You are done!</translate> bnhcqnht9q3rk9cvh8hwwcjc1pejbr7 Growth/FAQ/fa 0 1503245 5387833 5378637 2022-07-29T10:15:16Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''به سؤالات متداول تیم توسعه خوش آمدید (سؤالات متداول).''' امیدواریم اطلاعات مورد نیاز خود را پیدا کنید. با این حال، اگر چنین نیست، [[Talk:Growth|به ما اطلاع دهید]]. ''توجه برای مترجمان: این صفحه به طور منظم به‌روز می‌شود، که ممکن است بر کار شما تأثیر بگذارد. ما تمام تلاش خود را می‌کنیم تا از این اختلالات جلوگیری کنیم.'' == عمومی == {{Anchor|features}} === روی کدام ویژگی‌ها کار می‌کنید؟ === * [[Special:MyLanguage/Growth/Feature summary#NH|'''صفحهٔ اصلی تازه‌وارد''']]: یک صفحهٔ ویژه جدید، بهترین مکان برای شروع یک تازه‌وارد. که شامل: ** <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NT|'''Newcomer tasks''']]: a feed of task suggestions that help newcomers learn to edit. Newcomers have been making [[NEWTEA|productive edits]] through this feed! [[Help:Growth/Tools/Suggested edits|Know more about this tool]].</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Mentorship module''' [optional module]: each newcomers has a direct link to an experienced user. This way, they can ask questions about editing Wikipedia, less the need to find where to ask for assistance.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Impact module''': the user sees how many pages views articles they edit received.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#HP|'''Help panel''']]: a platform to provide resources to newcomers while they are editing. If they choose one of the suggested tasks on the newcomer homepage, they are guided step-by-step on the process of editing.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''[[Growth/Understanding first day|Welcome Survey]]''': communities can know why newcomers create an account on Wikipedia.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You can have a look at '''[[Special:MyLanguage/Growth/Feature summary|our features summary]]''' to know more about it. </div> === ویژگی‌های توسعه در کدام ویکی‌ها مستقر شده است؟ === <div lang="en" dir="ltr" class="mw-content-ltr"> You can find a list of wikis on our [[Special:MyLanguage/Growth/Deployment table|Deployment table]]. This page lists features activation per wiki as well. </div> {{anchor|NEWTEA}} === آیا ویژگی‌های توسعه موثر هستند؟ === <div lang="en" dir="ltr" class="mw-content-ltr"> [[NEWTEA|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that newcomers make their first article edit (+11.6%)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that they are retained as editors</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the number of edits they make during their first couple of weeks on the wiki (+22%)</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This deployment has been achieved in October 2021.</span> {{anchor|translate}} === رابط تا حدی ترجمه شده است. چگونه می‌توانم این را تغییر دهم؟ === [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] <div lang="en" dir="ltr" class="mw-content-ltr"> It takes up to one week to see new translations being deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Special pages names require a special process. For the following strings, [[Talk:Growth|please contact us]] directly with the translations: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. </div> {{anchor|enable|test}} === آیا می‌توانم ویژگی‌ها را آزمایش کنم؟ === <div lang="en" dir="ltr" class="mw-content-ltr"> [[Growth/Deployment table|On wikis where the Growth features are available]], and also on [https://test.wikipedia.org test.wikipedia.org], go to your [[Special:Preferences#mw-prefsection-personal|user preferences]] on one of these wikis and then: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Help panel''' in the ''{{int|prefs-editing}}'' tab.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Newcomer homepage''' in the ''{{int|prefs-personal}}'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work.</span> {{anchor|get}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can my wiki get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[#features|these features]], with the following conditions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Do you plan to deploy the features outside of Wikipedia? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Please contact us [[Talk:Growth|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> We are considering working with [[Growth/Communities/Wikisource|Wikisource communities]]. </div> {{anchor|pilot|ambassador}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can you clarify what "Pilot wikis", "Control group wikis" and "Ambassadors" are? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''Pilot wikis''' are wikis who have a close collaboration with the Growth team. They are involved in projects definitions and early review of the projects. They also test all prototypes first. The Growth team can contact some other wikis for some of these steps. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, our pilot wikis are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I use the Growth features on mobile ? On the official apps (iOS, Android)? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Access to the features == </div> {{anchor|ABtest}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can new accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where no [[A/B testing|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where an [[A/B testing|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How can existing accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], anyone can find the features [[#enable|in their Preferences]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === I host a workshop. How can I control if my students get the features when they create an account? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is possible to have a link parameter to control access to the features: </div> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=1</code> will force Growth features at account creation</span> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=0</code> will force the default experience at account creation</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[Talk:Growth|Please let us know]] if you plan to use these parameters. </div> {{anchor|Homepage}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Homepage == </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> === How to access the Homepage? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My email is requested, or my email is displayed at the top of the Homepage. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[Special:MyLanguage/Help:Notifications|notifications]], like when they are mentioned by other users on wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The email address won't be visible by other users. Communication with other users all happen on the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === The help links displayed on the homepage are not relevant. How to change them? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#HP|the same as on the Help panel]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Suggested edits == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How does Suggested Edits work ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How topics and tasks are suggested? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === SuggestedEdits' supervision and troubleshooting === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can I monitor which articles have been edited as Suggested edits? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to monitor which topics or which tasks need more articles? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please use <code>Special:NewcomerTasksInfo</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I don't have any task for a given combination. Is it normal? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== A user uses the tools in an nonconstructive way. What can I do? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Overall, users make [[#NEWTEA|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">try to understand what the use tries to do,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">contact this user, explain the situation, ask them for details and guide them to a different path if it exists,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">if the nonconstructive behavior persists, then block the user.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If repetitive and similar nonconstructive edits are made at your wiki, [[Talk:Growth|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you activated the Help panel in your preferences? If yes, [[Talk:Growth|please let us know about this issue]]. </div> {{anchor|config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Suggested edits configuration === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to provide more tasks for newcomers? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: </div> {| class="wikitable" !'''<span lang="en" dir="ltr" class="mw-content-ltr">Task</span>''' !<span lang="en" dir="ltr" class="mw-content-ltr">Level of difficulty</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Goal of the task</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Copyedit article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">fix spelling, grammar and tone</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add Links</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">add links between articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Update article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">bring existing articles up-to-date</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add References</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">find sources for existing articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Expand article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">hard</span> |<span lang="en" dir="ltr" class="mw-content-ltr">expand stubs to become sourced articles</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Add other templates that match the definition of the task to <code>Special:EditGrowthConfig</code> on your wiki</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add maintenance templates to more articles on your wiki.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is not possible at the moment. [[Talk:Growth|Please let us know]] about your potential project. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add a link === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Special:MyLanguage/Growth/Deployment table|where ''Structured tasks - Add a link'' has been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">"Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users have to decide if a link should be added or not added. These links are suggested by a machine.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which wikis have Structured tasks - Add a link ? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the accuracy of Structured tasks - Add a link predictions? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The predictions are, on average, accurate at 70%. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add an image === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the purpose of "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which rules define the work done by "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have several rules: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Only articles where no image is displayed are taken into consideration for images addition.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Articles with an infobox but no image aren't taken into consideration for now.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which types of users have been contacted to test this new concept ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">people who aren't wiki editors (using UserTesting.com, in English and Spanish)</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia.</span> {{anchor|HP}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Help panel == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We want to change some links displayed on the Help panel. How to do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#Homepage|also used on the Homepage]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where does questions posted using the Help panel goes? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, these questions go the the local Help desk. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should go the newcomer's mentors,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should be posted at the help desk.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change this configuration using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page.</span> {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration and operation of the mentoring system == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My wiki doesn't have the Growth mentoring system. How can I set it up? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The next steps are a summary of the process. The full process is described on [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|this dedicated page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, you need to check if the Growth tools are [[Growth/Deployment table|deployed at your wiki]]. If it is not yet the case, please see [[#get|how to get the features]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Then, you have to find some other mentors to volunteer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All mentors have to sign-up on a specific page, using [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a specific syntax]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> At your wiki, an admin has to add the mentor list to the configuration page (<code>Special:EditGrowthConfig</code>). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many mentors does a wiki need? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We recommend to have at least 3 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How mentors are assigned to newcomers? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Each new account receives a mentor randomly taken from a list of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many messages does a mentor receive per week? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Have you considered to assign a mentor only to people who already made some edits? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We don't know what each newcomer needs. [[Special:MyLanguage/New Editor Experiences|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. </div> {{anchor|existing}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[d:Q3919128|listed on Wikidata]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: </div> '''<span lang="en" dir="ltr" class="mw-content-ltr">Replace your mentoring system with the new one</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">If your mentoring system hasn't much success, it could be replaced by the Growth team features.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">Have both systems working together</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">You can imagine to have two roles:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Growth mentoring takes care of the newcomers basic questions,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The existing mentoring can take care of newcomers who are more involved.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> In this case, you might have to locally translate the interface for Growth features using your own terms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where can I signup as a mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Your community may have defined some conditions to become a mentor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How do I introduce myself as a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you sign up to become a mentor, the following syntax must be used, with: </div> <code>* <nowiki>[[</nowiki><span lang="en" dir="ltr" class="mw-content-ltr">User:Username</span><nowiki>]]</nowiki>|<span lang="en" dir="ltr" class="mw-content-ltr">Description</span></code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|<span lang="en" dir="ltr" class="mw-content-ltr">Read more about this</span>]] {{anchor|reassign}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can we reassign a newcomer to a different mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes, it is possible using <code>Special:ClaimMentee</code>. </div> {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === A mentor just quit. Can we reassign all their newcomer to different mentors? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can use <code>Special:ClaimMentee</code> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[Talk:Growth|please contact us]] directly. </div> {{anchor|magicword}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Type the magic word <code><nowiki>{{#mentor:Foo}}</nowiki></code> in a wikitext page, and preview. "Foo" has to be replaced by the username you target. This will display the name of Foo's mentor. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[#reassign|If the mentor changes]], then the magic word picks the new mentor's name. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can "[[Special:MyLanguage/Help:Substitution|subst:]]" this message if needed: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Foo's mentor will then be saved as wikitext. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you updated <code>Special:EditGrowthConfig</code> with the new page name? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Interactions between mentors and newcomers == </div> {{Anchor|questions}} <div lang="en" dir="ltr" class="mw-content-ltr"> === What kinds of questions do newcomers ask? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> From the observations we have made, questions are mostly about basic editing. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on communities experiences, the Growth team worked [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|on a guide for mentors]] who have to reply to these questions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Newcomers haven't replied to my messages. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Two possible cases there: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can I ask if my mentor is not responding to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I ask to have a different mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[#reassign|make the change]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, how can I monitor the newcomers assigned to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are currently working on a [[Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is available at all Wikipedias where [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|a list of mentors has been created and activated]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At wikis where the mentor dashboard is deployed, a new filter is available for mentors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They can monitor their mentees' activity in Watchlist and RecentChanges.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|not listed as mentors]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> 107sw17rngn7s9r55i6yfj54426z7qk Edit Discovery 0 1505152 5387090 5370000 2022-07-28T20:23:49Z PPelberg (WMF) 16721796 /* Active Entry Points */ Adding New Topic Tool A/B test result wikitext text/x-wiki {{Wikimedia engineering project information | name = Edit Discovery | description = An inventory of the contribution opportunities present within Wikimedia projects. | start = | end = | group = [[Editing]], [[Growth]], [[Inuka team|Inuka Team]], [[Wikimedia Language engineering|Language Team]] [[Structured Data Across Wikimedia]], [[Readers/Web/Team|Web Team]], [[Wikimedia Apps]] | lead = | team = | Phabricator = | updates = | progress = | previous = | next = | backlog = | projectpage = | display = {{{display|}}} }}There are many paths people can take to contribute to Wikimedia projects. This page offers an overview of the various entry points to said paths that are present within Wikimedia project interfaces. == Objectives == This page, and the practice of maintaining it, is designed to equip [[Wikimedia Product|Wikimedia Foundation Product Teams]] with the information they need to help volunteers intuitively discover opportunities to improve Wikimedia Projects. Initially, this page is intended for [[Wikimedia Product#Product teams|Product Department staff]] who are seeking to expose a new contribution opportunity to volunteers. This page will enable these staff members to evaluate all of the existing editing entry points so that they can decide to do one of the following: # '''Create''' a new entry point # '''Integrate''' with an existing entry point # '''Consolidate''' existing entry points == Entry Point Catalog == === Active Entry Points === ''This section contains a list of editing entry points that are '''currently''' present within Wikimedia project interfaces, across platforms and devices. For definitions of each of the columns in the table below, please see the Glossary.'' {| class="wikitable sortable" |+ !Entry Point Name !Contribution Type !Platform(s) !Screenshot(s) !Performance !Availability !Notes |- |Section edit link |Article edit |Web (desktop + mobile), Apps (iOS, Android) |[[File:Section_edit_affordance_(mobile_web).jpg|border|325x325px|Section edit (mobile web)]][[File:Section_edit_affordance_(iOS).jpg|border|325x325px]] |'''{{Highlight|#TODO}}''' |Everyone (logged in + out) |This entry point contains many different edit opportunities. |- |Full-page edit link |Article edit |Web (desktop) |[[File:WikiEditor-edit tab-en.png|frameless]] |'''{{Highlight|#TODO}}''' |Everyone (logged in + out) |This entry point contains many different edit opportunities. |- |Edit selected content |Article edit |iOS, Android |[[File:In-context_edit_affordance_(iOS).jpg|325x325px]] |'''{{Highlight|#TODO}}''' |Everyone (logged in + out) |This entry point contains many different edit opportunities. It also opens the editing interface in the precise place someone was in while reading. |- |Add topic |Start new discussion topic on a page where discussions are hosted |Web (desktop, mobile) |[[File:DiscussionTools New Discussion blank 2021.png|frameless]] |[[Talk pages project/Glossary|Junior Contributors]] who open the [[Talk pages project/Feature summary|New Topic Tool]] are '''~1.3 times more likely''' to successfully publish a new topic than Junior Contributors who open the existing add new section workflow<ref>[[Talk pages project/New discussion#Analysis 2: Impact]]</ref> |Everyone (logged in + out) |This entry point is scoped to a singular edit type: starting a new section/discussion on a page that hosts discussions. |- |Reply |Reply to a specific comment on a page where discussions happen |Web (desktop) |[[File:Reply tool version 2b screenshot.png|frameless]] |People who have made <100 cumulative edits were '''7.2 times more likely to publish a comment''' on desktop than those using page editing.<ref>[[Talk pages project/Replying#Analysis 3: Impact|Talk pages project/Replying#Analysis: Impact]]</ref> |Everyone (logged in + out. ''Details:[[Talk pages project/Deployment Status|Deployment Status]])'' |This entry point is scoped to a singular edit type: posting a response to a comment on a page that hosts discussions. |- |Create page via red link |Create a page that does not currently exist |Web (mobile) |[[File:Create new page mobile.png|alt=A screenshot showing the card that appears when people using Wikipedia's mobile website tap a red link.|frameless|270x270px]] |'''{{Highlight|#TODO}}''' |Everyone (logged in + out. ''Details:[[Talk pages project/Deployment Status|Deployment Status]])'' |This entry point supports many types of changes. Although, it is presented to people as having a singular purpose: to create a page that does not currently exist. |- |User homepage |A feed of numerous edits people can make. Each edit is scoped to a particular kind of change. |[[Growth/Personalized first day/Newcomer tasks|Web]] (mobile, desktop), [[Wikimedia Apps/Suggested edits|Android App]] |[[File:Screenshot of newcomer tasks module in Czech Wikipedia 2020-01-22.png|alt=Screenshot of Mediawiki's newcomer tasks module in Czech Wikipedia on 2020-01-22|frameless|195x195px]][[File:Suggested edits home april 2021.png|alt=A screenshot showing the Wikipedia Android app's suggested edits feed|frameless]] |'''{{Highlight|#TODO}}''' |'''{{Highlight|#TODO}}''' |This entry point offers people a variety of edits people they can choose to make. Each edit suggestion is scoped to a particular kind of change (e.g. adding reference(s), adding link(s), adding image(s), etc.). |- |New Translation |Translate an article from one language to another language |Web (desktop) |[[File:Special-Contributions page header.png|frameless]] |'''{{Highlight|#TODO}}''' |'''{{Highlight|#TODO}}''' |This entry point is scoped to a singular edit type: translating an article from one language into another. |- |Translation as alternative to create article from scratch |Translation (new article) |Web (desktop and mobile) |[[File:Translation as alternative to create.png|frameless]][[File:Translation as alternative to create on mobile.png|frameless|196x196px]] | |If there is a relevant suggestion based on the title it is shown in the invite. Otherwise, the invite is shown only once for the user. |Desktop ([[phab:T216500|T216500]]) and Mobile ([[phab:T298084|T298084]]) |- |Review recent translations |Proofreading, and Translation (expand) |Web (mobile) |[[File:Review translation notice.png|frameless|238x238px]][[File:Review translation instructions.png|frameless|238x238px]][[File:Review translation expand.png|frameless|238x238px]] |Research suggests that users can easily and quickly discover it and interpret as a signal that some action was needed for the article [https://meta.wikimedia.org/wiki/Research:Section_Translation_Entry_Points_Design_Research#Recently_translated_notice] |Logged-in users on mobile. Articles published as a translation in the last 10 days, with less than 5 edits. The article has no other notices (to give priority to community added ones), and is not a redirect. |[[phab:T287236|T287236]] |- |Translate a section the user recently edited in another language |Translation (expand) |Web (mobile) |[[File:Recently_edited_in_another_language_invite.png|frameless]] | |On mobile, the user is in a page that they have edited in another language recently in their 10 latest significant edits (+500 bytes or more) for a section missing in the current language. |[[phab:T287025|T287025]] |- |Surface missing languages to translate |Translation (new article) |Web (desktop and mobile) |[[File:Suggested missing languages on desktop.png|frameless]][[File:Suggested missing languages on mobile.png|frameless|238x238px]] | |Articles missing on a language relevant to the user. |Desktop ([[phab:T290972|T290972]]) and Mobile ([[phab:T298032|T298032]]). |- |Search for missing language to translate |Translation (new article) |Web (mobile) |[[File:Mobile language search empty state.png|frameless]] |Research shows that searching for the availability of an article in a given language is often an initial step in the translation process.[https://meta.wikimedia.org/wiki/Research:Section_Translation_Entry_Points_Design_Research#Language_switcher][https://meta.wikimedia.org/wiki/Research:Multilingual_Editor_Experiences_in_Small_Wikis] |Logged-in users on mobile. Searching for a language the article is not available in (and mobile translation is supported). |[[phab:T286470|T286470]] |- |More options from language selector |Translation (new article) |Web (desktop) |[[File:Language selector with access to more options.png|frameless]][[File:Language selector listing more options.png|frameless]] | |The Language selector provides access to additional options from the bottom corner. Logged-in users on desktop where Content Translation is available have an option to translate the page into more languages. |[[phab:T289840|T289840]] |- |Post-publish follow-up |Translation (expand), and Proofreading (secondary) |Web (mobile) |[[File:Post-publish_followup_translation.png|frameless]] | |Logged-in user after publishing a translation for an article/section on mobile. |[[phab:T241592|T241592]] |- |Post-edit suggestion |[[Growth/Personalized first day/Newcomer tasks|Suggested Edits]] |Web (mobile + desktop) |[[File:Screenshot_of_edit_another_suggestion_modal.png|frameless]] |In [[phab:T301603|analysis of the "add a link" funnel]], we saw that 28% of desktop users and 11% of mobile users choose to do another task from the "post-edit dialog". |Any logged in user who has [[Help:Growth/Tools/Enable the Homepage|enabled the Newcomer Homepage]] and completed a Suggested Edit. |[[phab:T301603|T301603]] |} === Inactive Entry Points === ''This section will contain a list of editing entry points that are '''no longer''' present within Wikimedia project interfaces, across platforms and devices.'' == Glossary == * <code>Entry Point Name</code>: name of entry point * <code>Contribution Type</code>: what content the entry point will lead people to change/contribute to ** ''Examples: Article, file, discussion, image, infobox, etc.'' * <code>Platform(s)</code>: the platform(s) the entry point is available on ** ''Examples: mobile web, desktop web, Android, iOS, KaiOS, etc.'' * <code>Screenshot(s)</code>: image(s) of the entry point being described * <code>Performance</code>: what data/evidence do we have to help us understand the impact a given entry point has on people's likelihood to: A) make a constructive contribution and B) return to make more contributions ** ''Examples: links to analyses, qualitative research studies, etc.'' * <code>Availability</code>: the conditions that must be met for an entry point to be available ** ''Examples: account state (logged in/out), the tool(s) used to publish a piece of content (e.g. Content Translation: [[phab:T287236]]), the time that has elapsed since an article was published, the presence of issues/edit suggestion within the content someone is viewing ([[phab:T265163|phab:T265163)]], user experience level, etc.'' * <code>Notes</code>: a free-form field for any information that may not fit in an existing column. ** ''Examples:'' ''attributes of an entry point: "persistent," "opportunistic," "proactive," etc.'' == See also == * [https://www.figma.com/proto/ya1q7364j0HFopqvZ1L2h0/Entry-Point-Design-Kit?page-id=0%3A1&node-id=5%3A15&viewport=273%2C48%2C0.23&scaling=contain Entry Point Design Kit] * [https://docs.google.com/presentation/d/1Os2gy2tklpQwQf9eg2KmIH3S5uP6RL-WDUlbYHg25R4/edit#slide=id.gd3bb112cdb_0_494 Growth features: Entry point exploration] == References == <references /> q3zn0jluf89ilt0xv6v6dzhmkapbihm Manual:Installing MediaWiki/pl 100 1510852 5387502 5384975 2022-07-28T22:45:24Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{InstallationNav}} <div lang="en" dir="ltr" class="mw-content-ltr"> This page covers all steps to manually install and configure MediaWiki. </div> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki can be difficult to install if you do not have any experience with Apache (web server software), PHP and MySQL/MariaDB (database).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The [[#Appendices|Appendices]] section below offers [[#Alternatives to manual installation|easier alternatives to manual installation]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The [[#Appendices|Appendices]] section below also provides installation notes for specific system configurations. </div> {{Note|<span lang="en" dir="ltr" class="mw-content-ltr">If you are already running MediaWiki, see the [[Special:MyLanguage/Manual:Upgrading|Upgrade guide]].</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Check the installation requirements == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Check that your system meets the [[Special:MyLanguage/Manual:Installation requirements|installation requirements]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Make sure to also check the {{ll|Release notes}} of the MediaWiki version that you plan to install. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Download the MediaWiki software == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download the MediaWiki tar file from the [[Special:MyLanguage/Download|official download page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generally, if you're using a production environment, you want to be running the latest stable release, which is MediaWiki {{MW stable release number}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Extract the MediaWiki software == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The downloaded file is in <code>.zip</code> or in <code>.tar.gz</code> file format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You need to uncompress this archive file before use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can uncompress the file locally (and then upload via FTP to the server) or directly on your server.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> On Windows, uncompressing is usually done with software such as [https://www.7-zip.org/ 7-Zip] (free), [http://www.winzip.com/ WinZip], [https://www.rarlab.com/ WinRAR] or [https://www.izarc.org/ IZArc] (free). </div> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux and Mac OS X, you can uncompress the file using the command:</span> <code>tar -xf mediawiki-*.tar.'''gz'''</code> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you uncompress the archive file while being the root/admin user, you may want to change file ownership afterwards, depending on your setup.</span> <span lang="en" dir="ltr" class="mw-content-ltr">On Linux systems, the command would be using [[w:chown|chown]] as the following:</span> <code>chown -R &lt;new_owner_user> &lt;mediawiki_folder></code>}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Upload files to your web server== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have not already uploaded the files to your [[Special:MyLanguage/Manual:Installation requirements#Web server|web server]] (or copied, if your web server software runs locally on your <code>localhost</code>), do so now. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Upload the files to your web server's web directory either by: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # directly copying the unzipped folder or </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # by using an FTP client such as [https://filezilla-project.org/ FileZilla] (Windows, OSX and Linux) or [https://cyberduck.io/ Cyberduck] (Windows and OSX). </div> # <span lang="en" dir="ltr" class="mw-content-ltr">by using software already provided by your [[Special:MyLanguage/Hosting services|hosting service]], such as the ''cPanel File Manager''</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If your upload tool has a "change file names to lowercase" option, then you must disable this. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you use the Apache HTTPD web server, the correct directory is specified in your <code>httpd.conf</code> file in the [https://httpd.apache.org/docs/current/mod/core.html#documentroot <code>DocumentRoot</code>] directive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">By default, this is <code>/var/www/</code> or {{tmpl|0=<code>&lt;$1>/htdocs</code>|apache-folder}}.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The exact location of the Apache server settings and directories file <code>httpd.conf</code> depends on your operating system.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Debian and Ubuntu, the file for Apache server settings and directories is <code>/etc/apache2/apache2.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">In Red Hat and Fedora, the file is <code>/etc/httpd/conf/httpd.conf</code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Rename the uploaded folder to whatever you would like to have in the URL.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If your web server is running as <code>http://localhost</code> for example, renaming to <code>/w/</code> directory would mean you would access your wiki at <code>http://localhost/w/index.php</code>.</span> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Do not use <code>/wiki/</code> if you want to set it up as a [[Special:MyLanguage/Manual:Short URL|Short URL]] after running the [[Special:MyLanguage/Manual:Config script|installation script]].</span>}} {{anchor|Create a database}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Set up the database == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> MediaWiki's [[Special:MyLanguage/Manual:Config script|installation script]] will ask you for a database name and database username, so MediaWiki can store the content of the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have a database server and know the password for the "root" (admin) user, skip to the [[#Run the installation script|#Run the installation script]] section below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you don't know the password for the root user, for example if you are on a [[Special:MyLanguage/Hosting services|hosted server]], you will have to create a new database before you run the MediaWiki installation script in the next section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">SQLite, MariaDB/MySQL, and PostgreSQL are supported databases.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're unsure which database to choose, use MariaDB.</span> After finishing the database setup, continue with [[#Run the installation script]] below. ===SQLite=== <div lang="en" dir="ltr" class="mw-content-ltr"> No further setup is required for [[Special:MyLanguage/Manual:SQLite|SQLite]] if the <code>pdo-sqlite</code> module for PHP is installed on the system. </div> <span lang="en" dir="ltr" class="mw-content-ltr">On the SQLite installation page, choose a database name (which can be anything) and the SQLite database directory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For the database directory, the installer will attempt to use a subdirectory outside of the document root and create it if needed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this directory is not safe (for example, web-readable), change it manually to avoid making it accessible to everyone on the web.</span> ===MariaDB/MySQL=== Create the [[Special:MyLanguage/Manual:MariaDB|MariaDB]]/[[Special:MyLanguage/Manual:MySQL|MySQL]] database and database user. There are several ways: * Use a [[Special:MyLanguage/Manual:Installation requirements#Control panel|control panel]] software offered by your [[Special:MyLanguage/Hosting services|Hosting service]] (example: [[w:PhpMyAdmin|PhpMyAdmin]]) * Use [[w:Secure Shell|ssh]] to log into your host and type the commands below into a MySQL prompt. <span lang="en" dir="ltr" class="mw-content-ltr">See the corresponding documentation of your hosting provider.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Alternatively, contact your [[Special:MyLanguage/Hosting services|hosting provider]] to have them create an account for you.</span> The following commands create a database named <tvar name=wikidb><code>my_wiki</code></tvar>, a user named <tvar name=wikiuser><code>wikiuser</code></tvar>, and set permissions for the user on that database. <syntaxhighlight lang="MySQL"> CREATE DATABASE my_wiki; CREATE USER 'wikiuser'@'localhost' IDENTIFIED BY 'database_password'; GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'localhost' WITH GRANT OPTION; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Only if your database is not running on the same server as your web server, you need to give the appropriate web server hostname (<code>mediawiki.example.com</code> in the example below): </div> <syntaxhighlight lang="MySQL"> GRANT ALL PRIVILEGES ON my_wiki.* TO 'wikiuser'@'mediawiki.example.com' IDENTIFIED BY 'database_password'; </syntaxhighlight> {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">MySQL/MariaDB logs all queries in a history file. It will include the database password for the user account.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this concerns you, delete and disable the <code>.mysql_history</code> file after running these queries by following the [https://dev.mysql.com/doc/refman/8.0/en/mysql-logging.html#mysql-logging-history-file MySQL documentation].</span>}} ===PostgreSQL=== <span lang="en" dir="ltr" class="mw-content-ltr">If you are using [[Special:MyLanguage/Manual:PostgreSQL|PostgreSQL]], you will need to either have a database and user created for you, or supply the name of a PostgreSQL user with "superuser" privileges to the configuration form.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often, this is the database user named <code>postgres</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> The following commands on a Linux command-line, as the postgres user, create a database user named <code>wikiuser</code>, and a database named <code>my_wiki</code> owned by the user named <code>wikiuser</code>. </div> createuser -S -D -R -P -E wikiuser <span lang="en" dir="ltr" class="mw-content-ltr">(then enter the database password)</span> createdb -O wikiuser my_wiki <div lang="en" dir="ltr" class="mw-content-ltr"> or as superuser (default postgres) execute the following commands at the database prompt: </div> <syntaxhighlight lang="sql"> CREATE USER wikiuser WITH NOCREATEDB NOCREATEROLE NOSUPERUSER ENCRYPTED PASSWORD 'database_password'; CREATE DATABASE my_wiki WITH OWNER wikiuser; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Beware of the [[phab:tag/postgreSQL|list of known issues when running MediaWiki with PostgreSQL]]. </div> {{anchor|Run the installation script}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Run the installation script == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Next, complete the installation of MediaWiki by going to the URL of your MediaWiki installation in your web browser: Follow the instructions in {{ll|Manual:Config script}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Further configuration== </div> * {{ll|Manual:System administration#Configuration}} - <span lang="en" dir="ltr" class="mw-content-ltr">Additional configuration</span> * {{ll|Manual:Administrators}} - <span lang="en" dir="ltr" class="mw-content-ltr">Wiki administration</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Keep up to date! == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Once installed, make sure you stay up to date with releases, and keep your server secure! </div> {{Clickable button 2|<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to the MediaWiki release announcements mailing list.</span>|class=mw-ui-progressive|url=https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/}} {{anchor|Appendices|Installing an existing wiki|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Appendices == </div> {{anchor|Alternatives to manual installation|Alternative to manual installation}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Alternatives to manual installation === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Instead of manually installing MediaWiki, alternative options might be easier: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Software bundles#MediaWiki software appliances|pre-integrated software appliances]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Hosting services|hosting services with 1-click installation, or wiki farms]]</span> :{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">Hosting services which provide automatical installation of applications such as MediaWiki may offer outdated versions or have other issues. If you encounter problems, it ''does not'' mean that you cannot install MediaWiki. It means that you should install MediaWiki manually.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> See also the {{ll|comparison of distribution options}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === System-specific instructions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The pages listed on {{ll|Manual:OS specific help}} give more detailed installation instructions aimed at specific systems. </div> <span lang="en" dir="ltr" class="mw-content-ltr">However, by and large these per-system docs are less maintained and might not always be up to date.</span> <span lang="en" dir="ltr" class="mw-content-ltr">First consult {{ll|Manual:Installing MediaWiki|nsp=0}} (this page) before looking at per-system installation documentation.</span> {{anchor|Wiki families (multiple wikis)}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Running multiple wikis === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> {{anchor|Installing an existing wiki}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Importing an existing wiki database === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Refer to [[Special:MyLanguage/Manual:FAQ#Installation and configuration|Manual:FAQ#Installation and configuration]]. </div> == Zobacz też == * {{ll|Manual:Upgrading|nsp=0}} * {{ll|Manual:Uninstallation|nsp=0}} [[Category:Installation{{#translation:}}|{{PAGENAME}}]] [[Category:MediaWiki administration{{#translation:}}]] rgevy4fp7glttxaxm35dh5y14rbj8q9 Manual:Combating spam/pl 100 1510915 5387479 5200692 2022-07-28T22:40:20Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} <span lang="en" dir="ltr" class="mw-content-ltr">Like all current dynamic web sites, wikis are a common target for spammers wishing to promote products or websites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki offers a number of features designed to [[Special:MyLanguage/Manual:Combating vandalism|combat vandalism in general]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">On this page we deal specifically with [[m:Wiki spam|wiki spam]], which is often automated.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Overview == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Common tools used to combat wiki spam typically fall into these categories: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Requiring log in and/or a CAPTCHA on certain operations, such as edits, adding external links, or new user creation </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits from known blacklisted IP addresses or IPs running open proxies </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits which add specific unwanted keywords or external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking specific username and page title patterns commonly used by spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits by new or anonymous users to specific often-targeted pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Whitelisting known-good editors (such as admins, regular contributors) while placing restrictions on new or anonymous users </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Cleanup scripts or bulk deletion ({{ll|Extension:Nuke}}) of existing posts from recently-banned spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Note that many of these features are not activated by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</span> <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It helps to raise the bar a little.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Quickest solutions to try first== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Fighting spam should not be too hard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to quickly and drastically reduce spam, try these few steps first.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install the [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] extension to block known spammer IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam setup basics== </div> {{anchor|CAPTCHA}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===CAPTCHA=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * all edits </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * edits adding new, unrecognized external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * user registration </div> <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Individual page protection=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. <div lang="en" dir="ltr" class="mw-content-ltr"> === Abuse filter === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Open proxies === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Apache configuration changes === </div> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Other ideas == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> == Zobacz też == *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. <div lang="en" dir="ltr" class="mw-content-ltr"> === Extensions === </div> *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users <div lang="en" dir="ltr" class="mw-content-ltr"> === Settings === </div> * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External links === </div> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] pa346jx7a6nzl2lyzub7l88fvjso2qv Extension:Highlight Links in Category/pl 102 1511162 5387155 5345730 2022-07-28T21:07:59Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''Highlight Links in Category''' is an extension that adds a CSS class to links pointing to members of a category. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Installation== </div> {{ExtensionInstall|HighlightLinksInCategory|registration=required}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Configuration parameters== </div> ; $wgHighlightLinksInCategory : <span lang="en" dir="ltr" class="mw-content-ltr">This global is an array that configures which categories get an added CSS class. The keys are the Category names, which must include underscores instead of spaces. Do not include the Category: namespace. The value for each key is the CSS class you would like to add to that category. For example:</span> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want add more than one class, separate the class names with spaces, like </div> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can add as many of these as you want, but from a UX perspective it's probably not awesome to add 500 different style links. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If $wgHighlightLinksInCategory is not set or empty, this extension will do nothing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're running a wiki farm and need to turn it off on some wikis, set <syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight>; using {{phpi|false}} could lead to incorrect behavior.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Styling== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Simply add the styles you need for these links to MediaWiki:Common.css on your wiki. For example: </div> {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want one category to override another, you'll have to specify it with CSS. </div> {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> Or alternatively, you could have defined the original <code>a.templates</code> rule as <code>a.templates:not(.disambig)</code> instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There's also the link icon approach: </div> {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==User Toggles== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An easy way to set up toggling this highlighting on or off is to make a [[Extension:Gadgets|Gadget]] with CSS in it. Yes, this is a personalization extension that outsources the personalization part to other extensions; I can still sleep at night. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==How this works== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Right after MediaWiki determines which linked pages exist (to make redlinks), it runs the <code>GetLinkColours</code> hook (see LinkHolderArray.php).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As we have a list of all of the page ids which are linked on that page, we can run one database query to see which of these links are in the set of categories we want to highlight.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Because the query only happens on an index of the <code>categorylinks</code> table, it's reasonably fast.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then CSS classes are assigned based on the result, using the configuration values the user sets in <code>$wgHighlightLinksInCategory</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Explaining how CSS works is outside the scope of this document. </div> == Znane problemy == <div lang="en" dir="ltr" class="mw-content-ltr"> * CSS styles are not added in Flow, because it doesn't appear to call the GetLinkColors hook there. </div> == Zobacz też == <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:Category:LinkEnd extensions]] - which customize links in other ways </div> {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] 4yojm9dgy91yrnlo2vv8nfqwijf2rkq Extension:NaylorAMS/pl 102 1511410 5387605 5224518 2022-07-29T03:26:13Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{PluggableAuth Plugin}} {{Extension|templatemode = |name = NaylorAMS |status = stable |type1 = user identity |type2 = |hook1 = |hook2 = |newhook1 = |newhook2 = |username = |author = [[User:MyWikis-JeffreyWang|Jeffrey Wang]] for MyWikis LLC |maintainer = [https://www.mywikis.com MyWikis LLC] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows authentication using Naylor Association Management Software (Timberlake)</span> |image = |imagesize = |version = 0.1.0 |update = |version preview = |update preview = |compatibility policy = master |mediawiki = 1.31+ |php = 7.0+ |needs-updatephp = no |composer = |table1 = |table2 = |license = GPL-2.0 |download = {{WikimediaDownload}}{{GithubDownload|mywikis|NaylorAMS|mastertarball=1}} |readme = {{git file|project=mediawiki/extensions/NaylorAMS|file=README|branch=HEAD|text=README}} |changelog = |example = |namespace = |parameters = <!-- configuration parameters, for use in LocalSettings.php --> |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |phabricator = |vagrant-role = }} The '''Naylor AMS''' extension extends {{ll|Extension:PluggableAuth|PluggableAuth}} to provide authentication for organizations using [https://www.naylor.com/member-management-solutions/association-management-software/ Naylor Association Management Software] (codename Timberlake). This extension will take the username, first and last name, and email address of a user from your organization's Naylor database and create a local MediaWiki account with the same username, email, and full name if one doesn't exist; otherwise, if a user with the same username exists, it logs them back into the local MediaWiki account. <div lang="en" dir="ltr" class="mw-content-ltr"> == Installation == </div> {{Note|1=This extension requires {{ll|Extension:PluggableAuth|PluggableAuth}} 5.x to be installed first.}} The PHP cURL extension is required for this MediaWiki extension. {{ExtensionInstall |download-link = [https://github.com/mywikis/NaylorAMS/archive/main.tar.gz Download] |registration = required }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration parameters == </div> For more information about these terms, please refer to the [https://masie.membershipsoftware.org/files/Naylor%20API%20Documentation.pdf Naylor AMS API documentation]. ; $wgNaylorAMS_BaseUrl : The base URL for your login system, provided by Naylor. Do not add a trailing slash at the end of the string. ('''required''') ; $wgNaylorAMS_SecurityKey : The security key provided by Naylor. ('''required''') ; $wgNaylorAMS_UsernameDenyList : An array of strings, with each string containing a local username. Used to prevent login via SSO to local-only accounts. Case sensitive; needs to follow MediaWiki username conventions. By default, the log in button says "Log in with Naylor AMS". To change the label, edit MediaWiki:Naylorams-loginbtn-text. <div lang="en" dir="ltr" class="mw-content-ltr"> == Disclaimer == </div> This extension is ''not'' maintained by Naylor, nor has it been sponsored by Naylor. It was written by and is maintained by [https://www.mywikis.com/ MyWikis LLC] for the purpose of serving its customers who use Naylor AMS. In addition, the extension is currently not compatible with PluggableAuth 6.0 and above. Use the latest version of PluggableAuth 5.x in the meantime. == Zobacz też == * {{ll|Extension:PluggableAuth}} * {{ll|Extension:SimpleSAMLphp}} * {{ll|Extension:LDAPAuthentication2}} {{Used by|mywikis=1}} [[Category:Extensions by MyWikis{{#translation:}}]] [[Category:PluggableAuth plugins{{#translation:}}]] i75z7kut7x8sy7l6tjobjk5p4yp0ttv Extension:PageAuthors/pl 102 1511417 5387165 5385400 2022-07-28T21:09:06Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension | status = stable | type = parser function | username = Sophivorus | description = <span lang="en" dir="ltr" class="mw-content-ltr">Get a sensible list of page authors</span> | update = 2022-07-28 | version = 1.2 | license = GPL-3.0-or-later | mediawiki = 1.35+ | php = 7+ | download = {{WikimediaDownload}} | needs-updatephp = No | example = [https://www.appropedia.org] }} The '''PageAuthors''' extension introduces a magic word <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> that returns a list of the main page authors of a page, sorted by number of bytes added. The extension is highly configurable so you can fine-tune what counts as an author. <div lang="en" dir="ltr" class="mw-content-ltr"> == Installation == </div> {{ExtensionInstall | registration = required }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Usage == </div> Simply add <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> to any page and you will get a comma-separated list of the main authors of the current page, sorted by number of bytes added. See [[#Configuration|#Configuration]] to define your own criteria of what counts as an author. You can also do <code><nowiki>{{PAGEAUTHORS:Some page}}</nowiki></code> to get the list of authors for some page other than the current one. The list of authors can be further processed using [[Extension:Arrays]] or the [[Extension:Page Forms/Page Forms and templates##arraymap|#arraymap function of the PageForms extension]], for example to link to the relevant user pages. {{anchor|Configuration}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration == </div> Each configuration is shown with its default value: * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerAuthor = 100;</syntaxhighlight> ― Minimum number of bytes added that each author must reach in order to be considered an author. * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerEdit = 10;</syntaxhighlight> ― Minimum number of bytes that each edit must reach in order to be counted towards the author's total. Having a positive value here already means that edits that reduce content don't count, which is usually desirable because even though synthesizing and removing problematic content is often valuable, we wouldn't say that makes you an ''author'' of the existing content. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreMinorEdits = true;</syntaxhighlight> ― Whether to ignore edits marked as minor. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBlocked = true;</syntaxhighlight> ― Whether to ignore blocked users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreAnons = true;</syntaxhighlight> ― Whether to ignore anonymous users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBots = true;</syntaxhighlight> ― Whether to ignore bots. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSystemUsers = true;</syntaxhighlight> ― Whether to ignore system users (such as in mass imports). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSummaryPatterns = [ '/Undo.*/', '/Revert.*/' ];</syntaxhighlight> ― Ignore edits with edit summaries that match these [https://www.php.net/manual/en/reference.pcre.pattern.syntax.php PHP regex patterns]. By default, edits with edit summaries that start with 'Undo' or 'Revert' will be ignored (these match the default edit summaries when doing a revert or a rollback in an English wiki). So for example, if some vandal blanks a page and then a user reverts it, the revert won't count towards the byte count of the user. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreUsers = [];</syntaxhighlight> ― Ignore edits by these users (without "User:" prefix). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreGroups = [];</syntaxhighlight> ― Ignore edits by these groups. * <syntaxhighlight lang=php inline>$wgPageAuthorsDelimiter = ', ';</syntaxhighlight> ― Delimiter between authors. == Zobacz też == * [[Manual:$wgMaxCredits]] - A built-in option to list the latest author followed by others in order of most recent edit, in the wiki footer. * [[Extension:Contributors]] - Lists authors by edit count. This is not reliable because some users tend to do few but big edits while others tend to do many small ones. Extreme but real cases include pages where the initial author creates the entire page in a single huge edit while other later editors make multiple edits fixing trivial issues. * [[Extension:SemanticExtraSpecialProperties]] - The _EUSER property lists authors by chronological order. This is not reliable either because while it's often the case that the first few editors are the main authors, it also happens that later editors contribute significantly and may even rewrite the entire page. km1u86ya2w66lnedj241qikvuh9kpgj Extension:CampaignEvents/Api 102 1512213 5386379 5355950 2022-07-28T13:26:55Z CMelo (WMF) 17549215 /* Parameters */ wikitext text/x-wiki {{Draft}} This page lists all endpoints available for the [[Extension:CampaignEvents]] extension. Note that all POST, PUT, and DELETE endpoints can be used either with the [[Special:MyLanguage/Extension:OAuth|OAuth extension]] authorization process, or with cookie-based authentication. If using cookie-based authentication, the request body should contain a CSRF token, specified as <code>"token": "token-goes-here"</code>. To get a CSRF token, see the [[Special:MyLanguage/API:Tokens|Action API]]. == Enable an event registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>POST</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "id": <ID of the registration> }</code> |} Enables an event registration. === Request schema === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>event_page</code> <small>required | title</small> | Title of the associated event page. Must be a page on the current wiki. |- | <code>chat_url</code> <small>optional | string</small> | Invite link for a chat group <!-- |- | <code>tracking_tool_name</code> <small>optional | string</small> | Name of a tracking tool to enable for the registration |- | <code>tracking_tool_url</code> <small>optional | string</small> | URL of the tracking tool --> |- | <code>start_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") |- | <code>end_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") <!-- |- | <code>type</code> <small>required | string</small> | The type of the event --> |- | <code>online_meeting</code> <small>optional | boolean</small> | Whether the event is online |- | <code>inperson_meeting</code> <small>optional | boolean</small> | Whether the event is in-person |- | <code>meeting_url</code> <small>optional | string</small> | For online events, the URL of the video call |- | <code>meeting_country</code> <small>optional | string</small> | For in-person events, the country where the event takes place |- | <code>meeting_address</code> <small>optional | string</small> | For in-person events, the full address where the event takes place |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 201 | Success: the event registration was enabled. The Location header shall point to the registration reource. |- ! 400 | The event data is invalid |- ! 400 | The provided CSRF token does not match |- ! 403 | You cannot enable event registrations |- ! 403 | You cannot enable event registration for the given event page |} == Edit an event registration == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/edit_event_registration</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>PUT</code> ! style="text-align:left;" |Returns | Nothing |} Edits an event registration. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>id</code> <small>required | integer</small> | ID of the event registration |} === Request schema === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>event_page</code> <small>required | title</small> | Title of the associated event page. Must be a page on the current wiki. |- |<code>status</code> <small>required | string</small> |Status of the event ("open", "closed") |- | <code>chat_url</code> <small>optional | string</small> | Invite link for a chat group <!-- |- | <code>tracking_tool_name</code> <small>optional | string</small> | Name of a tracking tool to enable for the registration |- | <code>tracking_tool_url</code> <small>optional | string</small> | URL of the tracking tool --> |- | <code>start_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") |- | <code>end_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") <!-- |- | <code>type</code> <small>required | string</small> | The type of the event --> |- | <code>online_meeting</code> <small>optional | boolean</small> | Whether the event is online |- | <code>inperson_meeting</code> <small>optional | boolean</small> | Whether the event is in-person |- | <code>meeting_url</code> <small>optional | string</small> | For online events, the URL of the video call |- | <code>meeting_country</code> <small>optional | string</small> | For in-person events, the country where the event takes place |- | <code>meeting_address</code> <small>optional | string</small> | For in-person events, the full address where the event takes place |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 204 | Success: the event registration was edited. |- ! 400 | The event data is invalid |- ! 400 | The provided CSRF token does not match |- ! 400 | The event page is not on another wiki, and the registration should be edited from there |- ! 403 | You cannot edit event registrations |- ! 403 | You cannot edit an event registration for the given event page |- ! 404 | The given ID does not correspond to an existing event registration |} == List all registrations from an organizer == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/organizer/<user_name>/event_registrations</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>GET</code> ! style="text-align:left;" |Returns | JSON object with an array of event registrations: <pre> [ { "event_id": "<Id of the event>", "event_name": "<Name of the event>", } ]</pre> If the event is deleted, there's an additional <code>"event_deleted": true</code> element. |} Lists all the event registrations from an organizer. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>user_name</code> <small>required | user</small> | The username of the organizer |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 201 | Success: list all the events. |- ! 404 | The user does not exist. |} == List all registrations a participant has registered for == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/participant/<user_name>/event_registrations</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>GET</code> ! style="text-align:left;" |Returns | JSON object with an array of event registrations: <pre> [ { "event_id": "<ID of the event>", "event_name": "<Name of the event>", } ]</pre> If the event is deleted, there's an additional <code>"event_deleted": true</code> element. |} Lists all the event registrations a participant has registered for. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>user_name</code> <small>required | user</small> | The username of the Participant |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 201 | Success: list all the events. |- ! 404 | The user does not exist. |} == Register as a participant == {{Note|When using this endpoint on Wikimedia projects, you agree to the [https://foundation.wikimedia.org/wiki/Terms_of_Use Terms of Use] and [https://foundation.wikimedia.org/wiki/Privacy_policy Privacy Policy]}} {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants/self</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>PUT</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "modified": <whether the action resulted in any modification> }</code> |} Registers the user as a participant to an event. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 400 | The provided CSRF token does not match |- ! 400 | The event registration is not open |- ! 400 | The event has already ended |- ! 400 | The event was deleted |- ! 403 | You cannot register for events |- ! 404 | The given ID does not correspond to an existing event registration |} == Cancel registration as a participant == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants/self</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>DELETE</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "modified": <whether the action resulted in any modification> }</code> |} Cancels the registration as a participant to an event. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 400 | The event has already ended |- ! 400 | The provided CSRF token does not match |- ! 400 | The event was deleted |- ! 403 | You are not allowed to cancel your registration for this event |- ! 404 | The given ID does not correspond to an existing event registration |} == Delete a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>DELETE</code> ! style="text-align:left;"|Returns | Nothing |} Deletes an event registration. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 204 | Success |- ! 400 | The provided CSRF token does not match |- ! 403 | You are not allowed to delete the registration |- ! 404 | The given ID does not correspond to an existing event registration |- ! 404 | The event registration is already deleted |} == List the organizers of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/organizers</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | Array of objects: <code>{ "user_id": <ID>, "roles": [ "creator", "organizer", ... ] }</code> |} Returns a list of organizers of a given event registration. This is hard-limited to 50 results. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |} == List the participants of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | Array of objects: <code>{participant_id: <participant id>, user_id: <central user ID>, user_name: <user name>, user_registered_at: <Date>}</code> |} Returns a list of participants of a given event registration. This is hard-limited to 50 results. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |- |<code>last_participant_id</code><small><nowiki>optional | query</nowiki></small> |Default null, if null get the first 20 participants, if not null get next 20 participants (this is not the user id) |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |} == Get details of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | JSON object with the same keys that you can use to edit a registration: <pre> { "id": <ID>, "name": <name>, "event_page": <event page title>, "event_page_wiki": <ID of the wiki where the event page is located>, "chat_url": <url>, "status": <status>, "start_time": <timestamp in MW format>, "end_time": <timestamp in MW format>, "online_meeting": <bool, whether the event is online>, "inperson_meeting": <bool, whether the event is in-person>, "meeting_url": <url>, "meeting_country": <country>, "meeting_address": <address> }</pre> |} Returns the details of a given event registration. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |- ! 404 | The event registration was deleted |} 0njgpa79j8tzil64pcybtoxzwlefp0i 5386382 5386379 2022-07-28T13:30:15Z CMelo (WMF) 17549215 /* List the participants of a registration */ wikitext text/x-wiki {{Draft}} This page lists all endpoints available for the [[Extension:CampaignEvents]] extension. Note that all POST, PUT, and DELETE endpoints can be used either with the [[Special:MyLanguage/Extension:OAuth|OAuth extension]] authorization process, or with cookie-based authentication. If using cookie-based authentication, the request body should contain a CSRF token, specified as <code>"token": "token-goes-here"</code>. To get a CSRF token, see the [[Special:MyLanguage/API:Tokens|Action API]]. == Enable an event registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>POST</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "id": <ID of the registration> }</code> |} Enables an event registration. === Request schema === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>event_page</code> <small>required | title</small> | Title of the associated event page. Must be a page on the current wiki. |- | <code>chat_url</code> <small>optional | string</small> | Invite link for a chat group <!-- |- | <code>tracking_tool_name</code> <small>optional | string</small> | Name of a tracking tool to enable for the registration |- | <code>tracking_tool_url</code> <small>optional | string</small> | URL of the tracking tool --> |- | <code>start_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") |- | <code>end_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") <!-- |- | <code>type</code> <small>required | string</small> | The type of the event --> |- | <code>online_meeting</code> <small>optional | boolean</small> | Whether the event is online |- | <code>inperson_meeting</code> <small>optional | boolean</small> | Whether the event is in-person |- | <code>meeting_url</code> <small>optional | string</small> | For online events, the URL of the video call |- | <code>meeting_country</code> <small>optional | string</small> | For in-person events, the country where the event takes place |- | <code>meeting_address</code> <small>optional | string</small> | For in-person events, the full address where the event takes place |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 201 | Success: the event registration was enabled. The Location header shall point to the registration reource. |- ! 400 | The event data is invalid |- ! 400 | The provided CSRF token does not match |- ! 403 | You cannot enable event registrations |- ! 403 | You cannot enable event registration for the given event page |} == Edit an event registration == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/edit_event_registration</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>PUT</code> ! style="text-align:left;" |Returns | Nothing |} Edits an event registration. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>id</code> <small>required | integer</small> | ID of the event registration |} === Request schema === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>event_page</code> <small>required | title</small> | Title of the associated event page. Must be a page on the current wiki. |- |<code>status</code> <small>required | string</small> |Status of the event ("open", "closed") |- | <code>chat_url</code> <small>optional | string</small> | Invite link for a chat group <!-- |- | <code>tracking_tool_name</code> <small>optional | string</small> | Name of a tracking tool to enable for the registration |- | <code>tracking_tool_url</code> <small>optional | string</small> | URL of the tracking tool --> |- | <code>start_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") |- | <code>end_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") <!-- |- | <code>type</code> <small>required | string</small> | The type of the event --> |- | <code>online_meeting</code> <small>optional | boolean</small> | Whether the event is online |- | <code>inperson_meeting</code> <small>optional | boolean</small> | Whether the event is in-person |- | <code>meeting_url</code> <small>optional | string</small> | For online events, the URL of the video call |- | <code>meeting_country</code> <small>optional | string</small> | For in-person events, the country where the event takes place |- | <code>meeting_address</code> <small>optional | string</small> | For in-person events, the full address where the event takes place |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 204 | Success: the event registration was edited. |- ! 400 | The event data is invalid |- ! 400 | The provided CSRF token does not match |- ! 400 | The event page is not on another wiki, and the registration should be edited from there |- ! 403 | You cannot edit event registrations |- ! 403 | You cannot edit an event registration for the given event page |- ! 404 | The given ID does not correspond to an existing event registration |} == List all registrations from an organizer == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/organizer/<user_name>/event_registrations</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>GET</code> ! style="text-align:left;" |Returns | JSON object with an array of event registrations: <pre> [ { "event_id": "<Id of the event>", "event_name": "<Name of the event>", } ]</pre> If the event is deleted, there's an additional <code>"event_deleted": true</code> element. |} Lists all the event registrations from an organizer. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>user_name</code> <small>required | user</small> | The username of the organizer |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 201 | Success: list all the events. |- ! 404 | The user does not exist. |} == List all registrations a participant has registered for == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/participant/<user_name>/event_registrations</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>GET</code> ! style="text-align:left;" |Returns | JSON object with an array of event registrations: <pre> [ { "event_id": "<ID of the event>", "event_name": "<Name of the event>", } ]</pre> If the event is deleted, there's an additional <code>"event_deleted": true</code> element. |} Lists all the event registrations a participant has registered for. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>user_name</code> <small>required | user</small> | The username of the Participant |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 201 | Success: list all the events. |- ! 404 | The user does not exist. |} == Register as a participant == {{Note|When using this endpoint on Wikimedia projects, you agree to the [https://foundation.wikimedia.org/wiki/Terms_of_Use Terms of Use] and [https://foundation.wikimedia.org/wiki/Privacy_policy Privacy Policy]}} {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants/self</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>PUT</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "modified": <whether the action resulted in any modification> }</code> |} Registers the user as a participant to an event. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 400 | The provided CSRF token does not match |- ! 400 | The event registration is not open |- ! 400 | The event has already ended |- ! 400 | The event was deleted |- ! 403 | You cannot register for events |- ! 404 | The given ID does not correspond to an existing event registration |} == Cancel registration as a participant == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants/self</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>DELETE</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "modified": <whether the action resulted in any modification> }</code> |} Cancels the registration as a participant to an event. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 400 | The event has already ended |- ! 400 | The provided CSRF token does not match |- ! 400 | The event was deleted |- ! 403 | You are not allowed to cancel your registration for this event |- ! 404 | The given ID does not correspond to an existing event registration |} == Delete a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>DELETE</code> ! style="text-align:left;"|Returns | Nothing |} Deletes an event registration. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 204 | Success |- ! 400 | The provided CSRF token does not match |- ! 403 | You are not allowed to delete the registration |- ! 404 | The given ID does not correspond to an existing event registration |- ! 404 | The event registration is already deleted |} == List the organizers of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/organizers</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | Array of objects: <code>{ "user_id": <ID>, "roles": [ "creator", "organizer", ... ] }</code> |} Returns a list of organizers of a given event registration. This is hard-limited to 50 results. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |} == List the participants of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | Array of objects: <syntaxhighlight lang="json"> [{"participant_id": "<participant id>", "user_id": "<central user ID>", "user_name": "<user name>", "user_registered_at": "<Date>"}] </syntaxhighlight> |} Returns a list of participants of a given event registration. This is hard-limited to 50 results. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |- |<code>last_participant_id</code><small><nowiki>optional | query</nowiki></small> |Default null, if null get the first 20 participants, if not null get next 20 participants (this is not the user id) |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |} == Get details of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | JSON object with the same keys that you can use to edit a registration: <pre> { "id": <ID>, "name": <name>, "event_page": <event page title>, "event_page_wiki": <ID of the wiki where the event page is located>, "chat_url": <url>, "status": <status>, "start_time": <timestamp in MW format>, "end_time": <timestamp in MW format>, "online_meeting": <bool, whether the event is online>, "inperson_meeting": <bool, whether the event is in-person>, "meeting_url": <url>, "meeting_country": <country>, "meeting_address": <address> }</pre> |} Returns the details of a given event registration. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |- ! 404 | The event registration was deleted |} b51j12814if1f8n1cs67x6fam6b9vj8 5386383 5386382 2022-07-28T13:34:18Z CMelo (WMF) 17549215 /* List the participants of a registration */ wikitext text/x-wiki {{Draft}} This page lists all endpoints available for the [[Extension:CampaignEvents]] extension. Note that all POST, PUT, and DELETE endpoints can be used either with the [[Special:MyLanguage/Extension:OAuth|OAuth extension]] authorization process, or with cookie-based authentication. If using cookie-based authentication, the request body should contain a CSRF token, specified as <code>"token": "token-goes-here"</code>. To get a CSRF token, see the [[Special:MyLanguage/API:Tokens|Action API]]. == Enable an event registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>POST</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "id": <ID of the registration> }</code> |} Enables an event registration. === Request schema === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>event_page</code> <small>required | title</small> | Title of the associated event page. Must be a page on the current wiki. |- | <code>chat_url</code> <small>optional | string</small> | Invite link for a chat group <!-- |- | <code>tracking_tool_name</code> <small>optional | string</small> | Name of a tracking tool to enable for the registration |- | <code>tracking_tool_url</code> <small>optional | string</small> | URL of the tracking tool --> |- | <code>start_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") |- | <code>end_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") <!-- |- | <code>type</code> <small>required | string</small> | The type of the event --> |- | <code>online_meeting</code> <small>optional | boolean</small> | Whether the event is online |- | <code>inperson_meeting</code> <small>optional | boolean</small> | Whether the event is in-person |- | <code>meeting_url</code> <small>optional | string</small> | For online events, the URL of the video call |- | <code>meeting_country</code> <small>optional | string</small> | For in-person events, the country where the event takes place |- | <code>meeting_address</code> <small>optional | string</small> | For in-person events, the full address where the event takes place |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 201 | Success: the event registration was enabled. The Location header shall point to the registration reource. |- ! 400 | The event data is invalid |- ! 400 | The provided CSRF token does not match |- ! 403 | You cannot enable event registrations |- ! 403 | You cannot enable event registration for the given event page |} == Edit an event registration == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/edit_event_registration</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>PUT</code> ! style="text-align:left;" |Returns | Nothing |} Edits an event registration. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>id</code> <small>required | integer</small> | ID of the event registration |} === Request schema === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>event_page</code> <small>required | title</small> | Title of the associated event page. Must be a page on the current wiki. |- |<code>status</code> <small>required | string</small> |Status of the event ("open", "closed") |- | <code>chat_url</code> <small>optional | string</small> | Invite link for a chat group <!-- |- | <code>tracking_tool_name</code> <small>optional | string</small> | Name of a tracking tool to enable for the registration |- | <code>tracking_tool_url</code> <small>optional | string</small> | URL of the tracking tool --> |- | <code>start_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") |- | <code>end_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") <!-- |- | <code>type</code> <small>required | string</small> | The type of the event --> |- | <code>online_meeting</code> <small>optional | boolean</small> | Whether the event is online |- | <code>inperson_meeting</code> <small>optional | boolean</small> | Whether the event is in-person |- | <code>meeting_url</code> <small>optional | string</small> | For online events, the URL of the video call |- | <code>meeting_country</code> <small>optional | string</small> | For in-person events, the country where the event takes place |- | <code>meeting_address</code> <small>optional | string</small> | For in-person events, the full address where the event takes place |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 204 | Success: the event registration was edited. |- ! 400 | The event data is invalid |- ! 400 | The provided CSRF token does not match |- ! 400 | The event page is not on another wiki, and the registration should be edited from there |- ! 403 | You cannot edit event registrations |- ! 403 | You cannot edit an event registration for the given event page |- ! 404 | The given ID does not correspond to an existing event registration |} == List all registrations from an organizer == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/organizer/<user_name>/event_registrations</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>GET</code> ! style="text-align:left;" |Returns | JSON object with an array of event registrations: <pre> [ { "event_id": "<Id of the event>", "event_name": "<Name of the event>", } ]</pre> If the event is deleted, there's an additional <code>"event_deleted": true</code> element. |} Lists all the event registrations from an organizer. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>user_name</code> <small>required | user</small> | The username of the organizer |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 201 | Success: list all the events. |- ! 404 | The user does not exist. |} == List all registrations a participant has registered for == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/participant/<user_name>/event_registrations</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>GET</code> ! style="text-align:left;" |Returns | JSON object with an array of event registrations: <pre> [ { "event_id": "<ID of the event>", "event_name": "<Name of the event>", } ]</pre> If the event is deleted, there's an additional <code>"event_deleted": true</code> element. |} Lists all the event registrations a participant has registered for. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>user_name</code> <small>required | user</small> | The username of the Participant |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 201 | Success: list all the events. |- ! 404 | The user does not exist. |} == Register as a participant == {{Note|When using this endpoint on Wikimedia projects, you agree to the [https://foundation.wikimedia.org/wiki/Terms_of_Use Terms of Use] and [https://foundation.wikimedia.org/wiki/Privacy_policy Privacy Policy]}} {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants/self</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>PUT</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "modified": <whether the action resulted in any modification> }</code> |} Registers the user as a participant to an event. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 400 | The provided CSRF token does not match |- ! 400 | The event registration is not open |- ! 400 | The event has already ended |- ! 400 | The event was deleted |- ! 403 | You cannot register for events |- ! 404 | The given ID does not correspond to an existing event registration |} == Cancel registration as a participant == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants/self</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>DELETE</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "modified": <whether the action resulted in any modification> }</code> |} Cancels the registration as a participant to an event. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 400 | The event has already ended |- ! 400 | The provided CSRF token does not match |- ! 400 | The event was deleted |- ! 403 | You are not allowed to cancel your registration for this event |- ! 404 | The given ID does not correspond to an existing event registration |} == Delete a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>DELETE</code> ! style="text-align:left;"|Returns | Nothing |} Deletes an event registration. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 204 | Success |- ! 400 | The provided CSRF token does not match |- ! 403 | You are not allowed to delete the registration |- ! 404 | The given ID does not correspond to an existing event registration |- ! 404 | The event registration is already deleted |} == List the organizers of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/organizers</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | Array of objects: <code>{ "user_id": <ID>, "roles": [ "creator", "organizer", ... ] }</code> |} Returns a list of organizers of a given event registration. This is hard-limited to 50 results. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |} == List the participants of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | Array of objects: <syntaxhighlight lang="json"> [ { "participant_id": "<participant id>", "user_id": "<central user ID>", "user_name": "<user name>", "user_registered_at": "<Date>" } ] </syntaxhighlight> |} Returns a list of participants of a given event registration. This is hard-limited to 50 results. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |- |<code>last_participant_id</code><small><nowiki>optional | query</nowiki></small> |Default null, if null get the first 20 participants, if not null get next 20 participants (this is not the user id) |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |} == Get details of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | JSON object with the same keys that you can use to edit a registration: <pre> { "id": <ID>, "name": <name>, "event_page": <event page title>, "event_page_wiki": <ID of the wiki where the event page is located>, "chat_url": <url>, "status": <status>, "start_time": <timestamp in MW format>, "end_time": <timestamp in MW format>, "online_meeting": <bool, whether the event is online>, "inperson_meeting": <bool, whether the event is in-person>, "meeting_url": <url>, "meeting_country": <country>, "meeting_address": <address> }</pre> |} Returns the details of a given event registration. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |- ! 404 | The event registration was deleted |} r70asnk8kmqobrgv4gtuni1ua95niiw 5386588 5386383 2022-07-28T15:57:39Z CMelo (WMF) 17549215 /* Parameters */ wikitext text/x-wiki {{Draft}} This page lists all endpoints available for the [[Extension:CampaignEvents]] extension. Note that all POST, PUT, and DELETE endpoints can be used either with the [[Special:MyLanguage/Extension:OAuth|OAuth extension]] authorization process, or with cookie-based authentication. If using cookie-based authentication, the request body should contain a CSRF token, specified as <code>"token": "token-goes-here"</code>. To get a CSRF token, see the [[Special:MyLanguage/API:Tokens|Action API]]. == Enable an event registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>POST</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "id": <ID of the registration> }</code> |} Enables an event registration. === Request schema === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>event_page</code> <small>required | title</small> | Title of the associated event page. Must be a page on the current wiki. |- | <code>chat_url</code> <small>optional | string</small> | Invite link for a chat group <!-- |- | <code>tracking_tool_name</code> <small>optional | string</small> | Name of a tracking tool to enable for the registration |- | <code>tracking_tool_url</code> <small>optional | string</small> | URL of the tracking tool --> |- | <code>start_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") |- | <code>end_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") <!-- |- | <code>type</code> <small>required | string</small> | The type of the event --> |- | <code>online_meeting</code> <small>optional | boolean</small> | Whether the event is online |- | <code>inperson_meeting</code> <small>optional | boolean</small> | Whether the event is in-person |- | <code>meeting_url</code> <small>optional | string</small> | For online events, the URL of the video call |- | <code>meeting_country</code> <small>optional | string</small> | For in-person events, the country where the event takes place |- | <code>meeting_address</code> <small>optional | string</small> | For in-person events, the full address where the event takes place |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 201 | Success: the event registration was enabled. The Location header shall point to the registration reource. |- ! 400 | The event data is invalid |- ! 400 | The provided CSRF token does not match |- ! 403 | You cannot enable event registrations |- ! 403 | You cannot enable event registration for the given event page |} == Edit an event registration == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/edit_event_registration</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>PUT</code> ! style="text-align:left;" |Returns | Nothing |} Edits an event registration. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>id</code> <small>required | integer</small> | ID of the event registration |} === Request schema === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>event_page</code> <small>required | title</small> | Title of the associated event page. Must be a page on the current wiki. |- |<code>status</code> <small>required | string</small> |Status of the event ("open", "closed") |- | <code>chat_url</code> <small>optional | string</small> | Invite link for a chat group <!-- |- | <code>tracking_tool_name</code> <small>optional | string</small> | Name of a tracking tool to enable for the registration |- | <code>tracking_tool_url</code> <small>optional | string</small> | URL of the tracking tool --> |- | <code>start_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") |- | <code>end_time</code> <small>required | timestamp</small> | Timestamp of the event start time, in MW format (e.g., "20220414160000") <!-- |- | <code>type</code> <small>required | string</small> | The type of the event --> |- | <code>online_meeting</code> <small>optional | boolean</small> | Whether the event is online |- | <code>inperson_meeting</code> <small>optional | boolean</small> | Whether the event is in-person |- | <code>meeting_url</code> <small>optional | string</small> | For online events, the URL of the video call |- | <code>meeting_country</code> <small>optional | string</small> | For in-person events, the country where the event takes place |- | <code>meeting_address</code> <small>optional | string</small> | For in-person events, the full address where the event takes place |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 204 | Success: the event registration was edited. |- ! 400 | The event data is invalid |- ! 400 | The provided CSRF token does not match |- ! 400 | The event page is not on another wiki, and the registration should be edited from there |- ! 403 | You cannot edit event registrations |- ! 403 | You cannot edit an event registration for the given event page |- ! 404 | The given ID does not correspond to an existing event registration |} == List all registrations from an organizer == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/organizer/<user_name>/event_registrations</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>GET</code> ! style="text-align:left;" |Returns | JSON object with an array of event registrations: <pre> [ { "event_id": "<Id of the event>", "event_name": "<Name of the event>", } ]</pre> If the event is deleted, there's an additional <code>"event_deleted": true</code> element. |} Lists all the event registrations from an organizer. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>user_name</code> <small>required | user</small> | The username of the organizer |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 201 | Success: list all the events. |- ! 404 | The user does not exist. |} == List all registrations a participant has registered for == {| style="width: 100%;" |- ! style="text-align:left;" |Route | <code>/campaignevents/v0/participant/<user_name>/event_registrations</code> ! style="text-align:left;" |Content type | <code>application/json</code> |- ! style="text-align:left;" |Method | <code>GET</code> ! style="text-align:left;" |Returns | JSON object with an array of event registrations: <pre> [ { "event_id": "<ID of the event>", "event_name": "<Name of the event>", } ]</pre> If the event is deleted, there's an additional <code>"event_deleted": true</code> element. |} Lists all the event registrations a participant has registered for. === Parameters === {| class="wikitable" style="width: 100%;" | style="width: 20%;" | <code>user_name</code> <small>required | user</small> | The username of the Participant |} === Responses === {| class="wikitable" style="width: 100%;" ! style="width: 20%;" | 201 | Success: list all the events. |- ! 404 | The user does not exist. |} == Register as a participant == {{Note|When using this endpoint on Wikimedia projects, you agree to the [https://foundation.wikimedia.org/wiki/Terms_of_Use Terms of Use] and [https://foundation.wikimedia.org/wiki/Privacy_policy Privacy Policy]}} {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants/self</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>PUT</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "modified": <whether the action resulted in any modification> }</code> |} Registers the user as a participant to an event. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 400 | The provided CSRF token does not match |- ! 400 | The event registration is not open |- ! 400 | The event has already ended |- ! 400 | The event was deleted |- ! 403 | You cannot register for events |- ! 404 | The given ID does not correspond to an existing event registration |} == Cancel registration as a participant == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants/self</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>DELETE</code> ! style="text-align:left;"|Returns | JSON object: <code>{ "modified": <whether the action resulted in any modification> }</code> |} Cancels the registration as a participant to an event. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 400 | The event has already ended |- ! 400 | The provided CSRF token does not match |- ! 400 | The event was deleted |- ! 403 | You are not allowed to cancel your registration for this event |- ! 404 | The given ID does not correspond to an existing event registration |} == Delete a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>DELETE</code> ! style="text-align:left;"|Returns | Nothing |} Deletes an event registration. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 204 | Success |- ! 400 | The provided CSRF token does not match |- ! 403 | You are not allowed to delete the registration |- ! 404 | The given ID does not correspond to an existing event registration |- ! 404 | The event registration is already deleted |} == List the organizers of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/organizers</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | Array of objects: <code>{ "user_id": <ID>, "roles": [ "creator", "organizer", ... ] }</code> |} Returns a list of organizers of a given event registration. This is hard-limited to 50 results. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |} == List the participants of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}/participants</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | Array of objects: <syntaxhighlight lang="json"> [ { "participant_id": "<participant id>", "user_id": "<central user ID>", "user_name": "<user name>", "user_registered_at": "<Date>" } ] </syntaxhighlight> |} Returns a list of participants of a given event registration. This is hard-limited to 50 results. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |- |<code>last_participant_id</code> <small><nowiki>optional | query</nowiki></small> |Default null, if null get the first 20 participants, if not null get next 20 participants (this is not the user id) |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |} == Get details of a registration == {| style="width: 100%;" |- ! style="text-align:left;"|Route | <code>/campaignevents/v0/event_registration/{id}</code> ! style="text-align:left;"|Content type | <code>application/json</code> |- ! style="text-align:left;"|Method | <code>GET</code> ! style="text-align:left;"|Returns | JSON object with the same keys that you can use to edit a registration: <pre> { "id": <ID>, "name": <name>, "event_page": <event page title>, "event_page_wiki": <ID of the wiki where the event page is located>, "chat_url": <url>, "status": <status>, "start_time": <timestamp in MW format>, "end_time": <timestamp in MW format>, "online_meeting": <bool, whether the event is online>, "inperson_meeting": <bool, whether the event is in-person>, "meeting_url": <url>, "meeting_country": <country>, "meeting_address": <address> }</pre> |} Returns the details of a given event registration. === Parameters === {| class="wikitable" style="width: 100%;" |style="width: 20%;"| <code>id</code> <small>required | path</small> | ID of the event registration |} === Responses === {| class="wikitable" style="width: 100%;" !style="width: 20%;"| 200 | Success |- ! 404 | The given ID does not correspond to an existing event registration |- ! 404 | The event registration was deleted |} c49hyde7pu6z3chcq4zd2pmefrj79ub Manual:Combating spam/fi 100 1513653 5387475 5200690 2022-07-28T22:40:17Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{RightTOC}} <span lang="en" dir="ltr" class="mw-content-ltr">Like all current dynamic web sites, wikis are a common target for spammers wishing to promote products or websites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki offers a number of features designed to [[Special:MyLanguage/Manual:Combating vandalism|combat vandalism in general]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">On this page we deal specifically with [[m:Wiki spam|wiki spam]], which is often automated.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Overview == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Common tools used to combat wiki spam typically fall into these categories: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Requiring log in and/or a CAPTCHA on certain operations, such as edits, adding external links, or new user creation </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits from known blacklisted IP addresses or IPs running open proxies </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits which add specific unwanted keywords or external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking specific username and page title patterns commonly used by spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Blocking edits by new or anonymous users to specific often-targeted pages </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Whitelisting known-good editors (such as admins, regular contributors) while placing restrictions on new or anonymous users </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Cleanup scripts or bulk deletion ({{ll|Extension:Nuke}}) of existing posts from recently-banned spambots </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Normally a combination of various methods will be used, in an attempt to keep the number of spam, robot and open-proxy edits to a minimum while limiting the amount of disruption caused to legitimate users of the site. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Note that many of these features are not activated by default.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you are running a MediaWiki installation on your server/host, then you are the only one who can make the necessary configuration changes!</span> <span lang="en" dir="ltr" class="mw-content-ltr">By all means ask your users to help [[m:Special:MyLanguage/Wiki Spam#Watching out for wiki spam|watch out for wiki spam]] (and do so yourself) but these days spam can easily overwhelm small wiki communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It helps to raise the bar a little.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should also note however, that none of these solutions can be considered completely spam-proof.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Checking "{{int|recentchanges}}" ([[Special:RecentChanges]]) regularly is an effective practice.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Quickest solutions to try first== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Fighting spam should not be too hard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you want to quickly and drastically reduce spam, try these few steps first.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install the [[Special:MyLanguage/Extension:StopForumSpam|StopForumSpam]] extension to block known spammer IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Install and set up the basic antivandalism extensions (already shipped with [[Special:MyLanguage/Download|last releases]]), in particular {{ll|Extension:ConfirmEdit}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[Special:MyLanguage/Extension:ConfirmEdit#QuestyCaptcha|Configure QuestyCaptcha]] and [[Special:MyLanguage/Extension:ConfirmEdit#Configuration|change default settings]] if needed for your wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Enable {{ll|Manual:$wgDnsBlacklistUrls|$wgDnsBlacklistUrls}}, can be used to block open proxies, Tor exit nodes or VPNs on specific actions like editing or account creation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you still have problems, read the rest of this page for further solutions and post a message on [[m:Mailing lists/Overview#mediawiki-l|mediawiki-l]] for help. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam setup basics== </div> {{anchor|CAPTCHA}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===CAPTCHA=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">One of the more common methods of weeding out automated submissions is to use a [[w:CAPTCHA|CAPTCHA]], a system that tries to distinguish humans from automated systems by asking the user to solve a task that is difficult for machines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{ll|Extension:ConfirmEdit|ConfirmEdit}} extension for MediaWiki provides an extensible [[CAPTCHA]] framework which can be triggered on a number of events, including</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * all edits </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * edits adding new, unrecognized external links </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * user registration </div> <span lang="en" dir="ltr" class="mw-content-ltr">The extension ships with a default test, but this is a reference implementation, and is not intended for production use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Wiki operators installing ConfirmEdit on a public wiki are advised to use one of the CAPTCHA modules contained within the extension (there are five in total).</span> <span lang="en" dir="ltr" class="mw-content-ltr">The most robust CAPTCHAs available today are your custom QuestyCaptcha questions, if you tailor them tightly to your wiki's audience and update them frequently.</span> <span lang="en" dir="ltr" class="mw-content-ltr">ReCaptcha is nowadays beaten by most spammers<ref>Example: «Automatically solve captchas: GSA Captcha Breaker + Mega Ocr (Solves Recaptcha!)» says senukexcr.</ref>; the Asirra CAPTCHA, which asks the user to distinguish cats and dogs, is particularly obnoxious to users but may be effective.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is important to note that CAPTCHAs can block more than undesirable bots: if a script is unable to pass a CAPTCHA, then so is a screen reader, or other software or aid used by the blind or visually impaired.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the options in CAPTCHA, the "reCAPTCHA" widget, includes an alternative audio CAPTCHA for such cases - but some computer users fail hearing tests ''and'' reading tests, so this is not a complete solution.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You should consider the implications of such a barrier, and possibly provide an alternative means for affected users to create accounts and contribute, which is a legal requirement in some jurisdictions.</span><ref> <span lang="en" dir="ltr" class="mw-content-ltr">For example, [https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards Section 508 Standards for Electronic and Information Technology]</span> </ref> <span lang="en" dir="ltr" class="mw-content-ltr">Also it will not completely spam-proof your wiki; [[w:CAPTCHA|according to Wikipedia]] "Spammers pay about $0.80 to $1.20 for each 1,000 solved CAPTCHAs to companies employing human solvers in Bangladesh, China, India, and many other developing nations."</span> <span lang="en" dir="ltr" class="mw-content-ltr">For this reason it should be combined with other mechanisms.</span> ===rel="nofollow"=== <div lang="en" dir="ltr" class="mw-content-ltr"> Under the default configuration, MediaWiki adds <code>rel="nofollow"</code> to external links in wiki pages, to indicate that these are user-supplied, might contain spam, and should therefore not be used to influence page ranking algorithms. Popular search engines such as [http://www.google.com Google] honour this attribute. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can switch ''off'' this behaviour on a site-wide basis using {{ll|Manual:$wgNoFollowLinks|$wgNoFollowLinks}} or on a per-namespace basis using the {{ll|Manual:$wgNoFollowNsExceptions|$wgNoFollowNsExceptions}} configuration variable. </div> Use of the <code>rel="nofollow"</code> attribute alone will not stop spammers attempting to ''add'' marketing to a page, but it will at least prevent them from benefiting through increased page rank; we know for sure that some check this. Nonetheless, it should never be relied upon as the primary method of controlling spam as its effectiveness is inherently limited. It does not keep spam off your site. See [https://web.archive.org/web/20061207155806/http://wiki.chongqed.org/NoIndexHistory NoIndexHistory]. Note that putting it on all external links is a rather heavy handed anti-spam tactic, which you may decide not to use (switch off the rel=nofollow option). See [[m:Nofollow|Nofollow]] for a debate about this. It's good to have this as the installation default though. It means lazy administrators who are not thinking about spam problems, will tend to have this option enabled. For more information, see [[Manual:Costs and benefits of using nofollow]]. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Antispam routine: tailored measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Every spammer is different, even though they all look boringly similar. If the general countermeasures are not enough, before taking extreme steps make use of the tools which allow you to deal with the specific problems you have. </div> {{anchor|Individual page protection}} <div lang="en" dir="ltr" class="mw-content-ltr"> ===Individual page protection=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Often, the same page will be hit repeatedly by spambots. Common patterns observed in spambot-created pagenames include talk page, often outside main space (e.g. Category_talk: are little-used, so make common targets), and other discussion pages </div> <span lang="en" dir="ltr" class="mw-content-ltr">As most abusive edits on wikis which don't require registration to edit are from anonymous sources, blocking edits to these specific pages by anyone other than established users can prevent re-creation of deleted spamdump pages.</span> Typically, any page which is already a regular visitor to [[special:log/delete]] on an individual wiki is a good candidate for page protection. *[[Manual:Administrators#Protection|Semi-protection]] of individual pages. **In addition, this can be combined with changing the [[Special:MyLanguage/Manual:$wgAutoConfirmAge|minimum requirements]] for MediaWiki to identify users as 'autoconfirmed'. *One may apply [[Manual:Administrators#Protection|cascading protection]] to one or more pages that have links to the most frequently spammed pages. One can also use this trick to set up a handy list for use by admins. <div lang="en" dir="ltr" class="mw-content-ltr"> === Abuse filter === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> {{ll|Extension:AbuseFilter}} allows privileged users to create rules to target the specific type of spam your wiki is receiving, and automatically prevent the action and/or block the user. </div> <span lang="en" dir="ltr" class="mw-content-ltr">It can examine many properties of the edit, such as the username, user's age, text added, links added, and so on.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is most effective in cases where you have one or more skilled administrators who are willing to assist in helping you fight spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The abuse filter can be effective even against human-assisted spammers, but requires continual maintenance to respond to new types of attacks.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Examples for combating automatic spam can be found on [[Manual:Combating spam/AbuseFilter examples]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===SpamBlacklist=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The above approach will become too cumbersome if you attempt to block more than a handful of spammy URLs. A better approach is to have a long blacklist identifying many known spamming URLs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A popular extension for MediaWiki is the {{ll|Extension:SpamBlacklist|SpamBlacklist}} extension which blocks edits that add blacklisted URLs to pages: it allows such a list to be constructed on-wiki with the assistance of privileged users, and allows the use of lists retrieved from external sources (by default, it uses the extensive [[m:Spam blacklist]]). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The {{ll|Extension:TitleBlacklist|TitleBlacklist}} extension may also be useful, as a means to prevent re-creation of specific groups of pages which are being used by the 'bots to dump linkspam. </div> === Avoimet välityspalvelimet === <div lang="en" dir="ltr" class="mw-content-ltr"> Open proxies are a danger mostly because they're used as a way to circumvent countermeasures targeted to specific abuser; see also [[m:No open proxies]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some bots exist, e.g. on Wikimedia wikis, to detect and block open proxies IPs, but their code is often not public.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most such blocks are performed manually, when noticing the abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It's hence important to be able to tell whether an abusing IP is an open proxy or something else, to decide how to deal with it; even more so if it's an IP used by a registered user, retrieved with the {{ll|Extension:CheckUser|CheckUser}} extension.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Several extensions, particularly the {{ll|Extension:Tor block|Tor block}} extension, blocks a range of open proxies. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Since 1.22, {{ll|Manual:$wgApplyIpBlocksToXff|$wgApplyIpBlocksToXff}} is available to make blocks more effective. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Hardcore measures== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following measures are for the more technical savvy sysadmins who know what they're doing: they're harder to set up properly and monitor; if implemented badly, they may be too old to be still effective, or even counterproductive for your wiki. </div> === $wgSpamRegex === <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki provides a means to filter the text of edits in order to block undesirable additions, through the <code>{{ll|Manual:$wgSpamRegex|$wgSpamRegex}}</code> configuration variable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can use this to block additional snippets of text or markup associated with common spam attacks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Typically it's used to exclude URLs (or parts of URLS) which you do not want to allow users to link to.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users are presented with an explanatory message, indicating which part of their edit text is not allowed.</span> <span lang="en" dir="ltr" class="mw-content-ltr">{{ll|Extension:SpamRegex}} allows editing of this variable on-wiki.</span> <syntaxhighlight lang="php"> $wgSpamRegex = "/online-casino|buy-viagra|adipex|phentermine|adult-website\.com|display:none|overflow:\s*auto;\s*height:\s*[0-4]px;/i"; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">This prevents any mention of 'online-casino' or 'buy-viagra' or 'adipex' or 'phentermine'.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The '/i' at the end makes the search case insensitive.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will also block edits which attempt to add hidden or overflowing elements, which is a common "trick" used in a lot of mass-edit attacks to attempt to hide the spam from viewers.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Apache configuration changes === </div> <span lang="en" dir="ltr" class="mw-content-ltr">In addition to changing your MediaWiki configuration, if you are running MediaWiki on Apache, you can make changes to your Apache web server configuration to help stop spam.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These settings are generally either placed in your virtual host configuration file, or in a file called [http://httpd.apache.org/docs/current/howto/htaccess.html .htaccess] in the same location as LocalSettings.php (note that if you have a shared web host, they must enable AllowOverride to allow you to use an .htaccess file).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Filtering by user agent ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you block a spammer on your wiki, search your site's access log by IP to determine which user agent string that IP supplied. For example: </div> :<code>grep ^195.230.18.188 /var/log/apache2/access.log</code> The access log location for your virtual host is generally set using the [http://httpd.apache.org/docs/current/mod/mod_log_config.html#CustomLog CustomLog] directive. Once you find the accesses, you'll see some lines like this: :<code>195.230.18.188 - - [16/Apr/2012:16:50:44 +0000] "POST /index.php?title=FlemmingCoakley601&action=submit HTTP/1.1" 200 24093 "-" ""</code> The user agent is the last quoted string on the line, in this case an empty string. Some spammers will use user agent strings used by real browsers, while others will use malformed or blank user agent strings. If they are in the latter category, you can block them by adding this to your .htaccess file (adapted from [http://www.umasswiki.com/wiki/UMassWiki:Blocking_Spam_in_MediaWiki this page]): <pre>SetEnvIf User-Agent ^regular expression matching user agent string goes here$ spammer=yes Order allow,deny allow from all deny from env=spammer</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> This will return a 403 Forbidden error to any IP connecting with a user agent matching the specified regular expression. Take care to escape all necessary regexp characters in the user agent string such as . ( ) - with backslashes (\). To match blank user agents, just use "^$". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Even if the spammer's user agent string is used by real browsers, if it is old or rarely encountered, you can use rewrite rules to redirect users to an error page, advising them to upgrade their browser: </div> <pre>RewriteCond %{HTTP_USER_AGENT} "Mozilla/5\.0 \(Windows; U; Windows NT 5\.1; en\-US; rv:1\.9\.0\.14\) Gecko/2009082707 Firefox/3\.0\.14 \(\.NET CLR 3\.5\.30729\)" RewriteCond %{REQUEST_URI} !^/forbidden/pleaseupgrade.html RewriteRule ^(.*)$ /forbidden/pleaseupgrade.html [L] </pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Preventing blocked spammers from consuming resources ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> A persistent spammer or one with a broken script may continue to try to spam your wiki after they have been blocked, needlessly consuming resources. </div> <span lang="en" dir="ltr" class="mw-content-ltr">By adding a [http://httpd.apache.org/docs/2.2/howto/access.html deny from] pragma such as the following to your <code>.htaccess</code> file, you can prevent them from loading pages at all, returning a 403 Forbidden error instead:</span> <pre>Order allow,deny allow from all deny from 195.230.18.188</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> ===IP address blacklists=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Much of the most problematic spam received on MediaWiki sites comes from addresses long known by other webmasters as bot or open proxy sites, though there's only anecdotal evidence for this. These bots typically generate large numbers of automated registrations to forum sites, comment spam to blogs and page vandalism to wikis: most often linkspam, although existing content is sometimes blanked, prepended with random gibberish characters or edited in such a way as to break existing Unicode text. </div> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively simple [[#CAPTCHA|CAPTCHA]] may significantly reduce the problem, as may blocking the creation of [[#Individual page protection|certain often-spammed pages]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">These measures do not eliminate the problem, however, and at some point tightening security for all users will inconvenience legitimate contributors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> It may be preferable, instead of relying solely on CAPTCHA or other precautions which affect all users, to target specifically those IPs already known by other site masters to be havens of net.abuse. Many lists are already available, for instance [http://www.stopforumspam.com/downloads stopforumspam.com] has a list of "All IPs in CSV" which (as of feb. 2012) contains about 200,000 IPs of known spambots. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== CPU usage and overload ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that, when many checks are performed on attempted edits or pageviews, bots may easily overload your wiki disrupting it more than they would if it was unprotected. Keep an eye on the resource cost of your protections. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== DNSBL ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can set MediaWiki to check each editing IP address against one or more DNSBLs (DNS-based blacklists), which requires no maintenance but slightly increases edit latency.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example, you can add this line to your LocalSettings.php to block many open proxies and known forum spammers:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'dnsbl.tornevall.org' ); </syntaxhighlight> For details of these DNSBLs, see [http://www.spamhaus.org/xbl/ Spamhaus: XBL] and [http://dnsbl.tornevall.org/ dnsbl.tornevall.org]. For a list of DNSBLs, see [[:wikipedia:Comparison_of_DNS_blacklists|Comparison of DNS blacklists]]. See also {{ll|Manual:$wgEnableDnsBlacklist}}, {{ll|Manual:$wgDnsBlacklistUrls}}. <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bad Behavior and Project HoneyPot ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Bad Behavior is a first defense line blocking all requests by known spammers identified via HTTP headers, IP address, and other metadata; it is available as a MediaWiki extension, see {{ll|Extension:Bad Behavior}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For maximum effectiveness, it should be combined with an [http://www.projecthoneypot.org/httpbl.php http:BL API Key], which you can get by [http://www.projecthoneypot.org/create_account.php signing up for Project Honey Pot], a distributed spam tracking project. To join Project HoneyPot you will need to add a publicly accessible file to your webserver, then use the following extension code in your LocalSettings.php (or an included PHP file) to embed a link to it in every page: </div> {{warning|1=This is known to [[Thread:Extension talk:LiquidThreads/Edit/History/Delete on top of each other (paragraph inserted)|break LiquidThreads]]. Do not use them together.}} <syntaxhighlight lang="php"> $wgHooks['ParserAfterTidy'][] = 'fnInsertLinksToHoneyPot'; $wgHoneyPotPath = '/ciralix.php'; function fnInsertLinksToHoneyPot( &$parser, &$text ) { global $wgHoneyPotPath; $text .= "<a href=\"$wgHoneyPotPath\"><!-- hijacker --></a>"; return true; } </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Set $wgHoneyPotPath to the path of the honeypot page in your LocalSettings.php (e.g. "/ciralix.php"). You may change the form of the link above to any of the alternatives suggested by Project HoneyPot. You may need to log in to Project HoneyPot to see those alternative ways to make honeypot links invisible to humans. </div>[http://www.projecthoneypot.org/board/read.php?f=4&i=179&t=19][http://www.projecthoneypot.org/manage_honey_pots.php] <div lang="en" dir="ltr" class="mw-content-ltr"> Once you're signed up, choose Services&rarr;HTTP Blacklist to get an http:BL API Key, and put your key in Bad Behavior's settings.ini. </div> ==== $wgProxyList ==== {{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">This particular technique will substantially increase page load time and server load if the IP list is large. Use with caution.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can set the variable {{wg|ProxyList}} to a list of IPs to ban. This can be populated periodically from an external source using a cron script such as the following: </div> <syntaxhighlight lang="bash"> #!/bin/bash cd /your/web/root wget https://www.stopforumspam.com/downloads/listed_ip_30_ipv46.gz gzip -d listed_ip_30_ipv46.gz cat > bannedips.php << 'EOF' <?php $wgProxyList = array( EOF sed -e 's/^/ "/; s/$/",/' < listed_ip_30_ipv46 >> bannedips.php printf '%s\n' '");' >> bannedips.php rm -f listed_ip_30_ipv46 </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You then set in your LocalSettings.php:</span> <syntaxhighlight lang="php"> require_once "$IP/bannedips.php"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to save these commands in a file called e.g. <code>updateBannedIPs.sh</code>, so you can run it periodically. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also use a '''PHP-only''' solution to download the ip-list from stopforumspam. To do so check the PHP script available [http://www.pschmidt.it/vim_source/updateBanned_php.txt here]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you do this and you use APC cache for caching, you may need to increase apc.shm_size in your php.ini to accommodate such a large list. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You have just banned one hundred forty thousand spammers, all hopefully without any disruptive effect on your legitimate users, and said «adieu» to a lot of the worst of the known spammers on the Internet. Good riddance! That should make things a wee bit quieter, at least for a while… </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Honeypots, DNS BLs and HTTP BLs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> 140,000 dead spammers. Not bad, but any proper [[w:Bastard Operator From Hell|BOFH]] at this point would be bored and eagerly looking for the 140,001st spam IP to randomly block. And why not? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Fortunately, dynamically-updated lists of spambots, open proxies and other problem IPs are widely available. Many also allow usernames or email addresses (for logged-in users) to be automatically checked against the same blacklists. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> One form of blacklist which may be familiar to MediaWiki administrators is the DNS BL. Hosted on a domain name server, a DNS blacklist is a database of IP addresses. An address lookup determines if an IP attempting to register or edit is an already-known source of net abuse. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options in MediaWiki provide a primitive example of access to a DNS blacklist.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set the following settings in {{ll|Manual:LocalSettings.php|LocalSettings.php}} and IP addresses listed as HTTP spam are blocked:</span> <syntaxhighlight lang="php"> $wgEnableDnsBlacklist = true; $wgDnsBlacklistUrls = array( 'xbl.spamhaus.org', 'opm.tornevall.org' ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> The DNS blacklist operates as follows: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * A wiki gets an edit or new-user registration request from some random IP address (for example, in the format '123.45.67.89') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The four IP address bytes are placed into reverse order, then followed by the name of the desired DNS blacklist server </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The resulting address is requested from the domain name server (in this example, '89.67.45.123.zen.spamhaus.org.' and '89.67.45.123.dnsbl.tornevall.org.') </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * The server returns not found (NXDOMAIN) if the address is not on the blacklist. If is on either blacklist, the edit is blocked. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The lookup in an externally-hosted blacklist typically adds no more than a few seconds to the time taken to save an edit.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Unlike {{wg|ProxyKey}} settings, which must be loaded on each page read or write, the use of the DNS blacklist only takes place during registration or page edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This leaves the speed at which the system can service page read requests (the bulk of your traffic) unaffected.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> While the original SORBS was primarily intended for dealing with open web proxies and email spam, there are other lists specific to web spam (forums, blog comments, wiki edits) which therefore may be more suitable: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://dnsbl.tornevall.org/index.php?do=usage .opm.tornevall.org.] operates in a very similar manner to SORBS DNSBL, but targets open proxies and web-form spamming. Much of its content is consolidated from other existing lists of abusive IPs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [http://www.projecthoneypot.org/httpbl_api .dnsbl.httpbl.org.] specifically targets 'bots which harvest email addresses from web pages for bulk mail lists, leave comment spam or attempt to steal passwords using dictionary attacks. It requires the user register with projecthoneypot.org for a 12-character API key. If this key (for example) were 'myapitestkey', a lookup which would otherwise look like '89.67.45.123.http.dnsbl.sorbs.net.' or '89.67.45.123.opm.tornevall.org.' would need to be 'myapitestkey.89.67.45.123.dnsbl.httpbl.org.' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Web-based blacklists can identify spammer's email addresses and user information beyond a simple IP address, but there is no standard format for the reply from an HTTP blacklist server. For instance, a request for [http://botscout.com/code.htm http://botscout.com/test/?ip=123.45.67.89] would return "Y|IP|4" if the address is blacklisted ('N' or blank if OK), while a web request for [http://www.stopforumspam.com/apis http://www.stopforumspam.com/api?ip=123.45.67.89] would return "ip yes 2009-04-16 23:11:19 41" if the address is blacklisted (the time, date and count can be ignored) or blank if the address is good. </div> <span lang="en" dir="ltr" class="mw-content-ltr">With no one standard format by which a blacklist server responds to an enquiry, no built-in support for most on-line lists of known spambots exists in the stock MediaWiki package.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The inability to specify more than one blacklist server further limits the usefulness of the built-in {{wg|EnableDnsBlacklist}} and {{wg|DnsBlacklistUrls}} options.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Since [[rev:58061]], MediaWiki has been able to check multiple DNSBLs by defining <code>$wgDnsBlacklistUrls</code> as an array.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most blacklist operators provide very limited software support (often targeted to non-wiki applications, such as phpBB or Wordpress).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As the same spambots create similar problems on most open-content websites, the worst offenders attacking MediaWiki sites will also be busily targeting thousands of non-wiki sites with spam in blog comments, forum posts and guestbook entries.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automatic query of multiple blacklist sites is therefore already in widespread use protecting various other forms of open-content sites and the spambot names, ranks and IP addresses are by now already all too well known.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A relatively small number of spambots appear to be behind a large percentage of the overall problem.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Even where admins take no prisoners, a pattern where the same spambot IP which posted linkspam to the wiki a second ago is spamming blog comments somewhere else now and will be spamming forum posts a few seconds from now on a site half a world away has been duly noted.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One shared external blacklist entry can silence one problematic 'bot from posting on thousands of sites.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> This greatly reduces the number of individual IPs which need to be manually blocked, one wiki and one forum at a time, by local administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== But what's this about honeypots? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some anti-spam sites, such as projecthoneypot.org, provide code which you are invited to include in your own website pages. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Typically, the pages contain one or more unique, randomised and hidden email addresses or links, intended not for your human visitors but for spambots.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Each time the page is served, the embedded addresses are automatically changed, allowing individual pieces of spam to be directly and conclusively matched to the IP address of bots which harvested the addresses from your sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The IP address which the bot used to view your site is automatically submitted to the operators of the blacklist service.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Often a link to a fake 'comment' or 'guest book' is also hidden as a trap to bots which post spam to web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[w:Honeypot_(computing)|Honeypot (computing)]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once the address of the spammer is known, it is added to the blacklists (see above) so that you and others will in future have one less unwanted robotic visitor to your sites. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> While honeypot scripts and blacklist servers can automate much of the task of identifying and dealing with spambot IPs, most blacklist sites do provide links to web pages on which one can manually search for information about an IP address or report an abusive IP as a spambot. It may be advisable to include some of these links on the special:blockip pages of your wiki for the convenience of your site's administrators. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== More lists of proxy and spambot IPs ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Typically, feeding the address of any bot or open proxy into a search engine will return many lists on which these abusive IPs have already been reported. </div> <span lang="en" dir="ltr" class="mw-content-ltr">In some cases, the lists will be part of anti-spam sites, in others a site advocating the use of open proxies will list not only the proxy which has been being abused to spam your wiki installation but hundreds of other proxies like it which are also open for abuse.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It is also possible to block wiki registrations from anonymised sources such as Tor proxies (Tor Project - torproject.org), from bugmenot users or from email addresses (listed by undisposable.net) intended solely for one-time use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See also [http://www.sdsc.edu/~jeff/spam/2008/bc-20080301.html Blacklists Compared - 1 March 2008] and spamfaq.net for lists of blacklists.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Do keep in mind that lists intended for spam email abatement will generate many false positives if installed to block comment spam on wikis or other web forms.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Automated use of a list that blacklists all known dynamic user IP address blocks, for instance, could render your wiki all but unusable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To link to IP blacklist sites from the [[Special:Blockip]] page of your wiki (as a convenience to admins wishing to manually check if a problem address is an already-known 'bot):</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add one line to {{ll|Manual:LocalSettings.php|LocalSettings.php}} to set:</span> <code>{{ll|Manual:$wgNamespacesWithSubpages|$wgNamespacesWithSubpages}}[NS_SPECIAL] = true;</code> # <span lang="en" dir="ltr" class="mw-content-ltr">Add the following text in [[MediaWiki:Blockiptext]] to display:</span> "<code><nowiki>Check this IP at [http://whois.domaintools.com/{{SUBPAGENAME}} Domain Tools], [http://openrbl.org/?i={{SUBPAGENAME}} OpenRBL], [http://www.projecthoneypot.org/ip_{{SUBPAGENAME}} Project Honeypot], [http://www.spamcop.net/w3m?action=checkblock&ip={{SUBPAGENAME}} Spam Cop], [http://www.spamhaus.org/query/bl?ip={{SUBPAGENAME}} Spamhaus], [http://www.stopforumspam.com/ipcheck/{{SUBPAGENAME}} Stop Forum Spam].</nowiki></code>" <span lang="en" dir="ltr" class="mw-content-ltr">This will add an invitation to "check this IP at: Domain Tools, OpenRBL, Project Honeypot, Spam Cop, Spamhaus, Stop Forum Spam" to the page from which admins ask to block an IP. An IP address is sufficient information to make comments on Project Honeypot against spambots, Stop Forum Spam is less suited to reporting anon-IP problems as it requires username, IP and email under which a problem 'bot is attempting to register on your sites. The policies and capabilities of other blacklist-related websites may vary.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Note that blocking the address of the spambot posting to your site is not the same as blocking the URLs of [[Special:MyLanguage/Extension:SpamBlacklist#External block list servers (RBL's)|specific external links]] being [[Extension:SpamRegex|spammed]] in the edited text. Do both. Both approaches used in combination, as a means to supplement (but not replace) other anti-spam tools such as [[Extension:TitleBlacklist|title or username blacklists]] and [[Extension:ConfirmEdit|tests]] which attempt to determine whether an edit is made by a human or a robot (captchas, [[Extension:Bad Behavior|bad behaviour]] or [[Extension:AkismetKlik|akismet]]) can be a very effective means to separate spambots from real, live human visitors.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == If spam has won the battle == </div> <span lang="en" dir="ltr" class="mw-content-ltr">You can still win the war! MediaWiki offers you the tools to do so; just consolidate your positions until you're ready to attack again.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See {{ll|Manual:Combating vandalism}} and in particular [[Manual:Combating vandalism#Cleaning up|Cleaning up]], [[Manual:Combating vandalism#Restrict editing|Restrict editing]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> See ''External links'' for other tools without MediaWiki support. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Other ideas == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This page lists features which are currently included, or available as patches, but on the [[Talk:Anti-spam features|discussion page]] you will find many other ideas for anti-spam features which ''could'' be added to MediaWiki, or which are under development. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==See also== </div> *[[Manual:Combating vandalism]] contains more general advice *[[Manual:Preventing access]] *[[Manual:User rights]] *[[Spam Filter]] * [http://thread.gmane.org/gmane.org.wikimedia.mediawiki/41614/focus=41697 A message on our mailing list] of a successful setup avoiding spam and allow editing to non-registered users. <div lang="en" dir="ltr" class="mw-content-ltr"> === Extensions === </div> *{{ll|Extension:AbuseFilter|AbuseFilter}} &mdash; allows edit prevention and blocking based on a variety of criteria *{{ll|Extension:Bad Behavior|Bad Behavior}} *A slimmed down {{ll|Extension:ConfirmAccount#Minimal_settings|ConfirmAccount}} can be used to moderate new user registrations, (doesn't require captchas). *{{ll|Extension:CheckUser|CheckUser}} &mdash; allows, among other things, the checking of the underlying IP addresses of account spammers to block them. Allows mass-blocking of spammers from similar locations. *{{ll|Extension:FlaggedRevs|FlaggedRevs}} *{{ll|Extension:SpamRegex|SpamRegex}} &mdash; allows basic blocking of edits containing spam domains with a single regex *{{ll|Extension:StopForumSpam|StopForumSpam}} &mdash; allows for checking edits against the StopForumSpam service and allows for submitting data back to it when blocking users. *[[:Category:Spam management extensions|Category:Spam management extensions]] &mdash; category exhaustively listing spam management extensions *{{ll|Extension:Moderation|Moderation}} &mdash; don't show edits to normal users until approved by a moderator. This extension has the advantage that spam links are ''never'' shown to the public, so not creating incentive to post spam. Useful only on some wiki farms: *{{ll|Extension:GlobalBlocking|GlobalBlocking}} Commercial services: *{{ll|Extension:Antispam|Antispam}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Bundled in the installer ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The standard tarball available for [[download]] now contains most of the main anti-spam extensions, including the following: </div> *{{ll|Extension:ConfirmEdit|ConfirmEdit}} &mdash; adds various types of CAPTCHAs to your wiki **{{ll|Extension:QuestyCaptcha|QuestyCaptcha}} &mdash; CAPTCHA based on answering questions *{{ll|Extension:Nuke|Nuke}} &mdash; removes all contributions by a user or IP *{{ll|Extension:SpamBlacklist|SpamBlacklist}} &mdash; prevents edits containing spam domains, list is editable on-wiki by privileged users <div lang="en" dir="ltr" class="mw-content-ltr"> === Settings === </div> * {{ll|Manual:$wgDnsBlacklistUrls}} * {{ll|Manual:$wgEmailConfirmToEdit}} * {{ll|Manual:$wgEnableDnsBlacklist}} * {{ll|Manual:$wgGroupPermissions}} * {{ll|Manual:$wgProxyList}} * {{ll|Manual:$wgSpamRegex}} * {{ll|Manual:$wgApplyIpBlocksToXff}} <div lang="en" dir="ltr" class="mw-content-ltr"> === External links === </div> * [https://www.noisebridge.net/wiki/Secretaribot Some pywikipediabot scripts to aid in vandalism-fighting]. <references/> [[Category:Spam management{{#translation:}}|*]] [[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]] [[Category:Edit{{#translation:}}]] h3uewiemjer8c3is0usj5vfzewc54eo Growth/FAQ/cs 0 1513838 5387831 5378633 2022-07-29T10:15:14Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''<span lang="en" dir="ltr" class="mw-content-ltr">Welcome to the Growth team Frequently Asked Questions (FAQ).</span>''' Věříme, že najdete všechny informace, které potřebujete. Pokud vám tady něco chybí, [[Talk:Growth|dejte nám vědět]]. ''Poznámka pro překladatele: Tato stránka je často aktualizována, což může zesložitit vaši práci. Děláme vše proto, abychom tyto problémy minimalizovali.'' == Obecné == {{Anchor|features}} === Na jakých funkcích pracujete? === * [[Special:MyLanguage/Growth/Feature summary#NH|'''Domovská stránka''']]: nová speciální stránka – nejlepší místo, kde může nováček začít. Obsahuje následující: ** <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NT|'''Newcomer tasks''']]: a feed of task suggestions that help newcomers learn to edit. Newcomers have been making [[NEWTEA|productive edits]] through this feed! [[Help:Growth/Tools/Suggested edits|Know more about this tool]].</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Mentorship module''' [optional module]: each newcomers has a direct link to an experienced user. This way, they can ask questions about editing Wikipedia, less the need to find where to ask for assistance.</span> ** '''Modul dosahu''': uživatel vidí, kolikrát byly jím editované články navštíveny. * [[Special:MyLanguage/Growth/Feature summary#HP|'''Panel potřebuji pomoc''']]: platforma, která nováčkům poskytuje pomoc v editačním rozhraní. Pokud si na své domovské stránce vyberou některý z editačních tipů, panel zobrazí nápovědu rozdělenou do několika kroků, která nováčkům s editací pomáhá. * '''[[Growth/Understanding first day|Uvítací dotazník]]''': díky dotazníku mohou komunity vědět, proč si nováčci vytvářejí na Wikipedii účet. Můžete se podívat na '''[[Special:MyLanguage/Growth/Feature summary|shrnutí našich funkcí]]''', pokud vás zajímá více. === Na jakých projektech jsou funkce týmu Growth nasazeny? === Můžete se také podívat na [[Special:MyLanguage/Growth/Deployment table|seznam projektů]], na kterých jsou funkce týmu Growth dostupné. {{anchor|NEWTEA}} === Jsou funkce týmu Growth efektivní? === <div lang="en" dir="ltr" class="mw-content-ltr"> [[NEWTEA|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in: </div> * pravděpodobnost, že nováček uloží první editaci v článku (+11,6&nbsp;%) * pravděpodobnost, že u Wikipedie zůstanou * počet editací, které provedou během prvních několika týdnů od reigstrace (+22&nbsp;%) <span lang="en" dir="ltr" class="mw-content-ltr">We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features.</span> Nasazení proběhlo v říjnu 2021. {{anchor|translate}} === Rozhraní je přeložené jen částečně. Jak to mohu změnit? === [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] Než se nové překlady projeví, trvá to až jeden týden. Názvy speciálních stránek se překládají odlišně. Pokud chcete přeložit některý z následujících řetězců, [[Talk:Growth|dejte nám vědět]] jejich překlady: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. {{anchor|enable|test}} === Mohu si funkce sám vyzkoušet? === <div lang="en" dir="ltr" class="mw-content-ltr"> [[Growth/Deployment table|On wikis where the Growth features are available]], and also on [https://test.wikipedia.org test.wikipedia.org], go to your [[Special:Preferences#mw-prefsection-personal|user preferences]] on one of these wikis and then: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Help panel''' in the ''{{int|prefs-editing}}'' tab.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Newcomer homepage''' in the ''{{int|prefs-personal}}'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work.</span> {{anchor|get}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can my wiki get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[#features|these features]], with the following conditions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us.</span> # Wikipedie – dostávají naše funkce v podobě, v jaké jsou nyní k dispozici. Můžeme ale zvážit implementaci návrhů, které od těchto projektů dostaneme. # <span lang="en" dir="ltr" class="mw-content-ltr">All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</span> === Máte v plánu funkce týmu Growth nasadit i mimo Wikipedie? === <span lang="en" dir="ltr" class="mw-content-ltr">We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Please contact us [[Talk:Growth|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> We are considering working with [[Growth/Communities/Wikisource|Wikisource communities]]. </div> {{anchor|pilot|ambassador}} === Můžete vysvětlit, co jsou to „pilotní projekty“, „projekty s kontrolní skupinou“ a „ambasadoři“? === '''Pilotní projekty''' jsou projekty, které s týmem Growth mají navázanou úzkou spolupráci. Spolupracují na přípravě projektů a jsou jim předloženy ke konzultaci co nejdříve, jakmile je to možné. Mohou také jako první otestovat všechny prototypy. Growth tým také občas podle potřeby kontaktuje i některé další projekty navíc, a umožní jim účast v některých fázích vývoje projektu. K {{ymd|2022|3|1}} jsou našimi pilotními projekty: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". </div> Ambasadoři týmu Growth usnadňují komunikaci mezi týmem Growth a svou komunitou. Také pomáhají týmu Growth pochopit odlišnosti mezi jednotlivými projekty. V neposlední řadě také své komunitě pomáhají s používáním Growth funkcí a s uvítáním nováčků. === Mohu používat funkce týmu Growth na mobilu, například v rámci oficiálních aplikací pro iOS nebo Android? === <div lang="en" dir="ltr" class="mw-content-ltr"> Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). </div> == Přístup k funkcím == {{anchor|ABtest}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can new accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where no [[A/B testing|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where an [[A/B testing|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How can existing accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], anyone can find the features [[#enable|in their Preferences]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === I host a workshop. How can I control if my students get the features when they create an account? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is possible to have a link parameter to control access to the features: </div> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=1</code> will force Growth features at account creation</span> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=0</code> will force the default experience at account creation</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[Talk:Growth|Please let us know]] if you plan to use these parameters. </div> {{anchor|Homepage}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Homepage == </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> === How to access the Homepage? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My email is requested, or my email is displayed at the top of the Homepage. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[Special:MyLanguage/Help:Notifications|notifications]], like when they are mentioned by other users on wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The email address won't be visible by other users. Communication with other users all happen on the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === The help links displayed on the homepage are not relevant. How to change them? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#HP|the same as on the Help panel]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Suggested edits == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How does Suggested Edits work ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How topics and tasks are suggested? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === SuggestedEdits' supervision and troubleshooting === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can I monitor which articles have been edited as Suggested edits? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to monitor which topics or which tasks need more articles? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please use <code>Special:NewcomerTasksInfo</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I don't have any task for a given combination. Is it normal? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== A user uses the tools in an nonconstructive way. What can I do? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Overall, users make [[#NEWTEA|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">try to understand what the use tries to do,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">contact this user, explain the situation, ask them for details and guide them to a different path if it exists,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">if the nonconstructive behavior persists, then block the user.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If repetitive and similar nonconstructive edits are made at your wiki, [[Talk:Growth|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you activated the Help panel in your preferences? If yes, [[Talk:Growth|please let us know about this issue]]. </div> {{anchor|config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Suggested edits configuration === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to provide more tasks for newcomers? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: </div> {| class="wikitable" !'''<span lang="en" dir="ltr" class="mw-content-ltr">Task</span>''' !<span lang="en" dir="ltr" class="mw-content-ltr">Level of difficulty</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Goal of the task</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Copyedit article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">fix spelling, grammar and tone</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add Links</span> |<span lang="en" dir="ltr" class="mw-content-ltr">easy</span> |<span lang="en" dir="ltr" class="mw-content-ltr">add links between articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Update article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">bring existing articles up-to-date</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add References</span> |<span lang="en" dir="ltr" class="mw-content-ltr">medium</span> |<span lang="en" dir="ltr" class="mw-content-ltr">find sources for existing articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Expand article</span> |<span lang="en" dir="ltr" class="mw-content-ltr">hard</span> |<span lang="en" dir="ltr" class="mw-content-ltr">expand stubs to become sourced articles</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Add other templates that match the definition of the task to <code>Special:EditGrowthConfig</code> on your wiki</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add maintenance templates to more articles on your wiki.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is not possible at the moment. [[Talk:Growth|Please let us know]] about your potential project. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add a link === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Special:MyLanguage/Growth/Deployment table|where ''Structured tasks - Add a link'' has been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">"Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users have to decide if a link should be added or not added. These links are suggested by a machine.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which wikis have Structured tasks - Add a link ? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the accuracy of Structured tasks - Add a link predictions? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The predictions are, on average, accurate at 70%. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add an image === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the purpose of "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which rules define the work done by "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have several rules: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Only articles where no image is displayed are taken into consideration for images addition.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Articles with an infobox but no image aren't taken into consideration for now.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which types of users have been contacted to test this new concept ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">people who aren't wiki editors (using UserTesting.com, in English and Spanish)</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia.</span> {{anchor|HP}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Help panel == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We want to change some links displayed on the Help panel. How to do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#Homepage|also used on the Homepage]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where does questions posted using the Help panel goes? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, these questions go the the local Help desk. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should go the newcomer's mentors,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should be posted at the help desk.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change this configuration using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page.</span> {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration and operation of the mentoring system == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My wiki doesn't have the Growth mentoring system. How can I set it up? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The next steps are a summary of the process. The full process is described on [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|this dedicated page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, you need to check if the Growth tools are [[Growth/Deployment table|deployed at your wiki]]. If it is not yet the case, please see [[#get|how to get the features]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Then, you have to find some other mentors to volunteer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All mentors have to sign-up on a specific page, using [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a specific syntax]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> At your wiki, an admin has to add the mentor list to the configuration page (<code>Special:EditGrowthConfig</code>). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many mentors does a wiki need? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We recommend to have at least 3 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How mentors are assigned to newcomers? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Each new account receives a mentor randomly taken from a list of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many messages does a mentor receive per week? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Have you considered to assign a mentor only to people who already made some edits? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We don't know what each newcomer needs. [[Special:MyLanguage/New Editor Experiences|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. </div> {{anchor|existing}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[d:Q3919128|listed on Wikidata]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: </div> '''<span lang="en" dir="ltr" class="mw-content-ltr">Replace your mentoring system with the new one</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">If your mentoring system hasn't much success, it could be replaced by the Growth team features.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">Have both systems working together</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">You can imagine to have two roles:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Growth mentoring takes care of the newcomers basic questions,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The existing mentoring can take care of newcomers who are more involved.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> In this case, you might have to locally translate the interface for Growth features using your own terms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where can I signup as a mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Your community may have defined some conditions to become a mentor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How do I introduce myself as a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you sign up to become a mentor, the following syntax must be used, with: </div> <code>* <nowiki>[[</nowiki><span lang="en" dir="ltr" class="mw-content-ltr">User:Username</span><nowiki>]]</nowiki>|<span lang="en" dir="ltr" class="mw-content-ltr">Description</span></code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|<span lang="en" dir="ltr" class="mw-content-ltr">Read more about this</span>]] {{anchor|reassign}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can we reassign a newcomer to a different mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes, it is possible using <code>Special:ClaimMentee</code>. </div> {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === A mentor just quit. Can we reassign all their newcomer to different mentors? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can use <code>Special:ClaimMentee</code> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[Talk:Growth|please contact us]] directly. </div> {{anchor|magicword}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Type the magic word <code><nowiki>{{#mentor:Foo}}</nowiki></code> in a wikitext page, and preview. "Foo" has to be replaced by the username you target. This will display the name of Foo's mentor. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[#reassign|If the mentor changes]], then the magic word picks the new mentor's name. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can "[[Special:MyLanguage/Help:Substitution|subst:]]" this message if needed: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Foo's mentor will then be saved as wikitext. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you updated <code>Special:EditGrowthConfig</code> with the new page name? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Interactions between mentors and newcomers == </div> {{Anchor|questions}} <div lang="en" dir="ltr" class="mw-content-ltr"> === What kinds of questions do newcomers ask? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> From the observations we have made, questions are mostly about basic editing. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on communities experiences, the Growth team worked [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|on a guide for mentors]] who have to reply to these questions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Newcomers haven't replied to my messages. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Two possible cases there: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can I ask if my mentor is not responding to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I ask to have a different mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[#reassign|make the change]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, how can I monitor the newcomers assigned to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are currently working on a [[Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is available at all Wikipedias where [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|a list of mentors has been created and activated]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At wikis where the mentor dashboard is deployed, a new filter is available for mentors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They can monitor their mentees' activity in Watchlist and RecentChanges.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|not listed as mentors]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> la04pvv9q8qmc2pmw9rophrzevfaq9k Manual:Extension registration/cs 100 1516187 5386481 5375681 2022-07-28T14:34:13Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{MW version|version=1.25|comment=and after|gerrit change=166705}} '''Registrace rozšíření''' je mechanismus, který používá MediaWiki pro načítání [[Special:MyLanguage/Manual:Extensions|rozšíření]] a [[Special:MyLanguage/Manual:Skins|vzhledů]]. Konfigurační data vložíte do souboru s názvem <code>extension.json</code> nebo <code>skin.json</code> do kořenového adresáře vašeho rozšíření nebo vzhledu a MediaWiki je použije k registraci rozšíření a vzhledů. {{anchor|Migration for extension developers}} == Migrace pro správce webu == Před MediaWiki 1.25 byla konfigurace pro rozšíření a vzhledy prováděna v souboru PHP pomocí názvu přípony nebo vzhledu, například <code>MyExtension.php</code> nebo <code>MySkin.php</code>. <syntaxhighlight lang="php"> require_once "$IP/extensions/Hello/Hello.php"; require_once "$IP/extensions/FooBar/FooBar.php"; $wgFooBarEnable = true; require_once "$IP/skins/Baz/Baz.php"; require_once "/tmp/extension/some/where/else/BarFoo/BarFoo.php"; </syntaxhighlight> To lze převést na: <syntaxhighlight lang="php"> wfLoadExtensions( [ 'Hello', 'FooBar' ] ); $wgFooBarEnable = true; wfLoadSkin( 'Baz' ); wfLoadExtension( 'BarFoo', '/tmp/extension/some/where/else/BarFoo/extension.json' ); </syntaxhighlight> === Custom locations === Toto je nutné provést před načtením jakýchkoli rozšíření nebo vzhledů z nestandardních umístění adresáře: : Pokud svá rozšíření uchováváte na jiném místě než <code>$IP/extensions</code>, musíte přepsat {{wg|ExtensionDirectory}} nebo použít druhý parametr {{phpi|wfLoadExtension()}} k určení adresáře, ve kterém chcete rozšíření najít. :: If one or more of your extensions are stored in additional locations, use the second parameter of {{phpi|wfLoadExtension()}} to specify the location of the <code>.json</code> file for ''each'' of those extensions. ::: ''Note: {{phpi|wfLoadExtensions()}} '''(plural)''' always uses {{wg|ExtensionDirectory}} and cannot be overridden.'' :<syntaxhighlight lang="php"> $wgExtensionDirectory = '/some/path'; wfLoadExtension( 'FooBar' ); // Hledá /some/path/FooBar/extension.json wfLoadExtension( 'Hello', '/some/other/path/HelloV2/Hello.json' ); // Looks for /some/other/path/HelloV2/Hello.json </syntaxhighlight> : <span class="mw-translate-fuzzy">Pokud vaše vzhledy nejsou v <code>$IP/skins</code>, musíte přepsat špatně pojmenované {{wg|StyleDirectory}}.</span> :: If one or more of your skins are stored in additional locations, use the second parameter of {{phpi|wfLoadSkin()}} to specify the location of the <code>.json</code> file for ''each'' of those skins. :::''Note: {{phpi|wfLoadSkins()}} '''(plural)''' always uses {{wg|StyleDirectory}} and cannot be overridden.'' :<syntaxhighlight lang="php"> $wgStyleDirectory = '/my/skins'; wfLoadSkins( [ 'BarBaz', 'BazBar' ] ); // Vyhledá /my/skins/BarBaz/skin.json a /my/skins/BazBar/skin.json wfLoadSkin( 'BamBam', '/yet/another/path/BamBam/skin.json' ); // Looks for /yet/another/path/BamBam/skin.json </syntaxhighlight> == Migrace pro vývojáře rozšíření == Od MW 1.30 mohou být ID jmenného prostoru definovaná lokálně v <code>extension.json</code> před načtením rozšíření přepsána definováním příslušné konstanty v <code>LocalSettings.php</code>. Zvažte například následující deklaraci jmenného prostoru v souboru <code>extension.json</code>: <syntaxhighlight lang="javascript"> "namespaces": [ { "id": 1212, "constant": "NS_FOO", "name": "Foo" }, { "id": 1213, "constant": "NS_FOO_TALK", "name": "Foo_Talk" } ] </syntaxhighlight> To by ve výchozím nastavení způsobilo, že konstanta NS_FOO bude definována na hodnotu 1212. Toto však lze přepsat definováním příslušné konstanty v LocalSettings.php: <syntaxhighlight lang="php"> define( 'NS_FOO', 6688 ); define( 'NS_FOO_TALK', 6689 ); wfLoadExtension( "Foo" ); </syntaxhighlight> To by způsobilo, že jmenný prostor "Foo" bude registrován s ID 6688 namísto 1212. Při přepisování ID jmenného prostoru nezapomeňte, že všechny jmenné prostory talk musí mít lichá ID a ID jmenného prostoru talk musí být vždy ID jmenného prostoru subjektu plus jedna. :''Viz také [https://tools.wmflabs.org/extreg-wos/ registrace na stránce rozšíření (nyní superschopnosti)].'' Skript <code>{{ll|Manual:convertExtensionToRegistration.php|maintenance/convertExtensionToRegistration.php}}</code> vám pomůže s migrací ze vstupních bodů PHP do souboru metadat JSON. Pokud vaše rozšíření podporuje starší verze MediaWiki, měli byste si ponechat vstupní bod PHP <code>''FooBar/FooBar''.php</code>, dokud neukončíte podporu pro tyto starší verze. Ukázky příkazových řádků: <syntaxhighlight lang="shell-session"> $ cd core $ php maintenance/convertExtensionToRegistration.php extensions/MassMessage/MassMessage.php $ php maintenance/convertExtensionToRegistration.php skins/MonoBook/MonoBook.php --skin </syntaxhighlight> Možná budete muset odinstalovat své rozšíření z <code>LocalSettings.php</code>, pokud se zobrazí chyby, že konstanty nebo funkce nelze předefinovat. Soubor vstupního bodu PHP (FooBar.php) byste měli nahradit něčím podobným, jako je následující, aby nedošlo k přerušení wiki během procesu upgradu. <syntaxhighlight lang="php"> <?php if ( function_exists( 'wfLoadExtension' ) ) { wfLoadExtension( 'FooBar' ); // Udržujte i18n globals, aby se mergeMessageFileList.php nezměnil $wgMessagesDirs['FooBar'] = __DIR__ . '/i18n'; $wgExtensionMessagesFiles['FooBarAlias'] = __DIR__ . '/FooBar.alias.php'; wfWarn( 'Deprecated PHP entry point used for the FooBar extension. ' . 'Please use wfLoadExtension() instead, ' . 'see https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Extension_registration for more details.' ); return; } else { die( 'This version of the FooBar extension requires MediaWiki 1.29+' ); } </syntaxhighlight> Nebo vzhledů <syntaxhighlight lang="php"> <?php if ( function_exists( 'wfLoadSkin' ) ) { wfLoadSkin( 'FooBar' ); // Udržujte i18n globals, aby se mergeMessageFileList.php nezměnil $wgMessagesDirs['FooBar'] = __DIR__ . '/i18n'; $wgExtensionMessagesFiles['FooBarAlias'] = __DIR__ . '/FooBar.alias.php'; wfWarn( 'Deprecated PHP entry point used for the FooBar skin. Please use wfLoadSkin instead, ' . 'see https://www.mediawiki.org/wiki/Extension_registration for more details.' ); return; } else { die( 'This version of the FooBar skin requires MediaWiki 1.25+' ); } </syntaxhighlight> === Uchovávání dokumentace === Vstupní body PHP mají obvykle nějakou dokumentaci konfiguračních nastavení, která je užitečná a neměla by se ztratit. Bohužel JSON nepodporuje komentáře. Doporučuje se přenést konfigurační dokumentaci do souboru <code>README</code> v úložišti rozšíření. Konfiguraci byste také měli zdokumentovat na wiki na stránce Rozšíření:''MyExtension''. Část dokumentace je také možné zahrnout přímo do souboru <code>extension.json</code>. Registrace rozšíření ignoruje jakýkoli klíč v <code>extension.json</code> začínající znakem '<code>@</code>' ve struktuře nejvyšší úrovně, takže do těchto částí souboru JSON můžete vkládat komentáře. Například: <syntaxhighlight lang="javascript"> { "@note": "This file must be kept in sync with LocalisationUpdate.php", "@name": ... </syntaxhighlight> Verze 1 formátu <code>extension.json</code> také umožňovala <code>@note</code> v sekci <code>config</code>, ale to již není doporučeno ani podporováno ve verzi 2. Místo toho by mělo být použito pole <code>description</code> konfigurační proměnné. Toto by mělo být použito pouze pro krátké poznámky a komentáře. == Funkce == Pokud načítáte velký počet rozšíření, registrace rozšíření poskytne zvýšení výkonu, pokud máte nainstalováno [[Special:MyLanguage/Manual:Performance tuning|APC]] (nebo APCu). Rozšíření načtená společně s <code>wfLoadExtension'''s'''</code> (s množným číslem -s) budou uložena do mezipaměti společně. === Atributy === Opakujícím se problémem je, jak něco "zaregistrovat" s jinou příponou. Obvykle to znamenalo, že jste museli načíst jedno rozšíření před druhým. VisualEditor má například <code>$wgVisualEditorPluginModules</code>, který umožňuje rozšířením přidávat své moduly. Ve vstupním bodě VisualEditoru však má: <syntaxhighlight lang="php"> $wgVisualEditorPluginModules = []; </syntaxhighlight> To znamená, že pokud se nějaké rozšíření připojí k poli před načtením VisualEditoru, VE vymaže svůj záznam v tomto poli. Některá rozšíření závisela na konkrétním pořadí načítání, jiná to obcházela pomocí {{wg|ExtensionFunctions}}. Registrace rozšíření řeší tento problém pomocí "atributů". V rozšíření Math by jeho <code>extension.json</code> mělo něco jako: <syntaxhighlight lang="javascript"> { "VisualEditorPluginModules": [ "ext.math.visualEditor" ] } </syntaxhighlight> Počínaje verzí 2 musí být atributy definovány v samostatné sekci <code>attributes</code>. <code>Attributes</code> musí být objekt s názvem rozšíření jako klíčem a objektem párů atribut/hodnota jako hodnotou. Pamatujte, že klíč v podobjektu nesmí obsahovat název rozšíření! <syntaxhighlight lang="json"> { "attributes": { "VisualEditor": { "PluginModules": [ "ext.math.visualEditor" ] } }, "manifest_version": 2 } </syntaxhighlight> Když chce VisualEditor získat přístup k tomuto atributu, použije: <syntaxhighlight lang="php"> ExtensionRegistry::getInstance()->getAttribute( 'VisualEditorPluginModules' ); </syntaxhighlight> === Požadavky (závislosti) === Registrace rozšíření má sekci <code>requires</code> (vyžaduje), která funguje podobně jako sekce <code>require</code> [[Composer]]u. Umožňuje vývojáři rozšíření specifikovat několik požadavků na rozšíření, jako je konkrétní verze MediaWiki (nebo vyšší/menší než) nebo jiné rozšíření/vzhled. Chcete-li například přidat závislost na verzi MediaWiki, která je větší než 1.26.0, můžete do <code>extension.json</code> přidat následující kód: <ref>https://github.com/wikimedia/mediawiki/blob/78091899db2315916502421fdd2972f1d73237b3/docs/extension.schema.json#L273-L282</ref> <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.26.0" } } </syntaxhighlight> Klíč objektu <code>requires</code> je název závislosti (před MediaWiki 1.29.0 byla podporována pouze <code>MediaWiki</code>), hodnota je platné omezení verze (formát je [https://getcomposer.org/doc/articles/versions.md podle volby autora]). V MediaWiki 1.29.0 a vyšší můžete také přidat závislosti na vzhledech a dalších rozšířeních, jako jsou: <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.29.0", "extensions": { "ExampleExtension": "*" }, "skins": { "ExampleSkin": "*" } } } </syntaxhighlight> {{Note|1=<nowiki/> * Rozšíření a vzhledy uvedené zde, aby fungovaly, musí také používat systém registrace rozšíření popsaný na této stránce. * Řetězec přidaný k určení přípony nebo vzhledu musí být shodný s řetězcem uvedeným v poli "name" příslušného souboru "extension.json" nebo "skin.json". * Pro rozšíření využívající [[continuous integration|kontinuální integrace]] Wikimedie, je také třeba přidat závislosti do {{git file|project=integration/config |file=zuul/parameter_functions.py}} }} In MediaWiki 1.33.0(?!??) and above you can also add dependencies on PHP like so: <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.33.0", "platform": { "php": ">= 7.0.3" } } } </syntaxhighlight> === Zkontrolujte, zda je rozšíření načteno, aniž by bylo ve skutečnosti vyžadováno === Mnoho rozšíření může poskytovat funkce, které fungují pouze v případě, že je načteno i jiné rozšíření, aniž by tuto funkci skutečně potřebovali pro fungování základní funkce rozšíření. Jako příklad: Pokud je načteno rozšíření B, může rozšíření A poskytovat skutečný WYSIWYG editor, jinak bude používat jednoduchou textovou oblast. Rozšíření A může těžit z rozšíření B (pokud je načteno), ale ke správnému fungování nevyžaduje, aby bylo načteno. Za tímto účelem obvykle zkontrolujete, zda je rozšíření načteno, spíše než jej přidáte jako ''tvrdou'' závislost. Pro implementaci standardizovaného způsobu kontroly, zda je rozšíření načteno nebo ne (bez nutnosti práce navíc v rozšíření, která je v jiném rozšíření měkkou závislostí), lze použít registraci rozšíření. Implementuje metodu <code>isLoaded</code>, která vrací jednoduchý boolean, pokud je rozšíření načteno nebo ne (aby to fungovalo, musí být rozšíření načteno s registrací rozšíření). Příklad: <syntaxhighlight lang="php"> if ( ExtensionRegistry::getInstance()->isLoaded( 'ExtensionB' ) ) { // do things only, if extension B is loaded } </syntaxhighlight> {{MW version|version=1.32|comment=and after|gerrit change=455752}} Od [[MediaWiki 1.32]] je také možné zkontrolovat, zda je rozšíření načteno a zda splňuje dané omezení verze: <syntaxhighlight lang="php"> if ( ExtensionRegistry::getInstance()->isLoaded( 'ExtensionB', '>=1.2' ) ) { // do things only, if extension B is loaded and has a version of 1.2 or greater. } </syntaxhighlight> Pokud byste chtěli zkontrolovat, zda je v dřívějších verzích MediaWiki načtena konkrétní verze rozšíření, lze podobné informace extrahovat pomocí metody <code>getAllThings</code>, která vrací informace o kreditu pro všechna načtená rozšíření. Příklad: <syntaxhighlight lang="php"> $bVersion = ExtensionRegistry::getInstance()->getAllThings()['ExtensionB']['version'] ?? null; if ( $bVersion !== null && version_compare( $bVersion, '2.1.0', '>=' ) ) { // do things only, if extension B is loaded and has a version number greater than or equal to 2.1.0 } </syntaxhighlight> Alternativně, pokud rozšíření B definuje speciální konstantu určenou pro tento účel během načítání, je možné zkontrolovat, zda je definována: <syntaxhighlight lang="php"> if ( defined( 'ExtensionBVersion' ) ) { // You could also check for a version, if the constant holds the version // do things only, if extension B is loaded } </syntaxhighlight> Křehčím způsobem, kterému je třeba se vyhnout, je zkontrolovat, zda specifická třída rozšíření B existuje nebo ne, např. pomocí tohoto kódu: <syntaxhighlight lang="php"> if ( class_exists( 'ExtensionBHooks' ) ) { // do things only, if extension B its classes exist } </syntaxhighlight> To může přestat fungovat, pokud přípona existuje v systému souborů, ale není načtena, např. pokud byl pro automatické načítání použit composer. Pokud byla třída přejmenována nebo přestane existovat (např. protože není balíček public), dojde také k přerušení. Obecně je upřednostňováno sdílení kódu prostřednictvím komponent pro composer namísto rozšíření. Pokud třídy rozšíření potřebují pouze existovat, ale rozšíření nemusí být konfigurováno ani načteno, pro to, co chcete dělat, je to silný indikátor toho, že by tento kód měl být rozdělen na komponentu composer, na kterou byste se měli spolehnout. namísto. === Configs (Vaše nastavení rozšíření/vzhledů) === {{See also|Manual:Configuration for developers}} {{See also|Manual:Extension.json/Schema#config}} Ve výchozím nastavení <code>extension.json</code> předpokládá, že vaše konfigurační nastavení začíná předponou "wg". Pokud tomu tak není, můžete předponu přepsat pomocí speciálního klíče: <syntaxhighlight lang="json"> { "config": { "_prefix": "eg", "MyExtSetting": true } } </syntaxhighlight> To by použilo předponu "eg" a nastavilo globální proměnnou <code>$egMyExtSetting</code> na hodnotu true. Počínaje zveřejněním verze 2 poskytuje konfigurační sekce registrace rozšíření mnohem více funkcí a umožňuje vám popsat možnosti konfigurace mnohem podrobněji. Namísto jediného klíče -> úložiště hodnot pro možnosti konfigurace můžete také přidat následující informace. Obecná struktura <code>config</code> se mírně mění na následující, více objektově orientovanou verzi: <syntaxhighlight lang="json"> { "config_prefix": "eg", "config": { "MyExtSetting": { "value": true, "path": false, "description": "The description for the configuration", "descriptionmsg": "myextension-config-myextsetting", "public": true } }, "manifest_version": 2 } </syntaxhighlight> ==== Hodnota ==== Hodnota konfigurace se přesunula na toto místo. Toto je jediný požadovaný klíč pro konfigurační objekt. ==== Cesta ==== Booleovská hodnota klíče <code>path</code> identifikuje, zda má být hodnota konfigurační volby interpretována jako cesta souborového systému vzhledem ke kořenu adresáře rozšíření. Pokud je například hodnota konfigurace <code>myFile.png</code> a <code>path</code> je pravdivá, skutečná hodnota bude <code>/path/to/the/wiki/extensions/MyExtension/myFile.png</code>. ==== Popis ==== Klíč <code>description</code> pro možnost konfigurace může obsahovat nelokalizovaný řetězec, který lze použít k vysvětlení možnosti konfigurace dalším vývojářům nebo uživatelům (správcům systému) vašeho rozšíření. It may also be used as tooltip text on the parameters section of the extension infobox on the MediaWiki.org extension description page. Hodnota klíče popisu obvykle není vystavena frontendu wiki, ale podívejte se do přehledu, kde najdete další informace, jak by se tato funkce mohla v budoucnu používat! Existuje také možnost přidat klíč zprávy interního lokalizačního systému MediaWiki jako popis (<code>descriptionmsg</code>), který bude v budoucnu použit k odhalení popisu v rozhraní instalace MediaWiki. ==== veřejné / soukromé ==== Tato volba je booleovská, jejíž výchozí hodnota je false, což znamená, že konfigurační volba a hodnota jsou označeny jako "private". Tato hodnota se momentálně nikde nepoužívá, podívejte se do přehledu, kde se o této možnosti dozvíte více. ==== Výhled ==== {{tracked|T155155}} Výše uvedené změny jsou také přípravnými kroky pro vylepšenou správu konfigurace v MediaWiki. Výše uvedené změny nám umožňují např. odhalit možnosti konfigurace rozšíření v uživatelském rozhraní MediaWiki. K tomu je zapotřebí zpráva s lokalizovaným popisem (<code>descriptionmsg</code> a <code>description</code>) a indikace, zda má být konfigurační volba (<code>public</code>) veřejná nebo ne. === Automatické zjišťování testů jednotek === MediaWiki umožňuje libovolné rozšíření pro [[Special:MyLanguage/Manual:PHP unit testing/Writing unit tests for extensions|registraci testů phpunit]]. Bez registrace rozšíření byste museli zaregistrovat obslužný program pro háček {{ll|Manual:Hooks/UnitTestsList|UnitTestsList}}, který by vypadal asi takto: <syntaxhighlight lang="php"> public static function onUnitTestsList( array &$paths ) { $paths[] = __DIR__ . '/tests/phpunit/'; } </syntaxhighlight> (jak je popsáno v příručce). Tento kód však vypadá stejně pro mnoho rozšíření, takže byste to mohli nazvat zbytečnou duplikací kódu. Pokud vaše rozšíření používá registraci rozšíření a vaše testy phpunit jsou umístěny v podadresáři <code>tests/phpunit/</code> vašeho rozšíření, wraper phpunit MediaWiki automaticky objeví testy jednotek pomocí registrace rozšíření. Proto již nemusíte háček registrovat a nemusíte specifikovat, že vaše testy jednotek jsou uloženy ve výchozím adresáři. == Přizpůsobení registrace == :''See [[Manual:Extension.json/Schema#callback]].'' == Také composer.json == Pokud má rozšíření nebo vzhled knihovny závislosti, může je mít také soubor <code>composer.json</code>, viz {{ll|Manual:Composer.json best practices}}. Použijte pole <code>load_composer_autoloader</code>, aby MediaWiki používala automatické načítání Composer, když je to vhodné. Některá pole metadat se překrývají mezi <code>extension.json</code> a <code>composer.json</code> (diskutované v {{task|T89456}}), včetně: * <code>url</code> a <code>homepage</code> * <code>license-name</code> a <code>license</code> == Správce kódu == {{Component|mediawiki-configuration}} == Související stránky == * {{ll|Manual:Extension.json/Schema}} * Hlášení chyb v projektu [[phab:tag/mediawiki-configuration/|MediaWiki-Configuration]]. * Staré verze [[Special:MyLanguage/Manual:Developing extensions#Setup|Manual:Developing extensions#Setup]] (před květnem 2015) a {{wg|ExtensionCredits}} popisují starý přístup deklarování informací o rozšíření v kódu PHP a proměnných * {{ll|Manual:Extension registration/Limitations|2=Známá omezení}} * {{ll|Manual:Extension registration/Architecture|2=Přehled architektury}} * <code>[[phab:diffusion/MW/browse/master/docs/extension.schema.v2.json|docs/extension.schema.v2.json]]</code> je schéma pro <code>extension.json</code> (a skin.json). * [[Requests for comment/Extension registration|RfC]] o implementaci registrace rozšíření * [[toollabs:extreg-wos|Zeď superschopností pro registraci rozšíření!]] — přehled rozšíření, která je ještě třeba převést. * {{task|T98668}} — Sledovací karta pro převod všech rozšíření a vzhledů na Gitu pro použití registrace rozšíření. == Odkazy == {{reflist}} [[Category:Extension registration{{#translation:}}]] [[Category:Extension creation{{#translation:}}]] 2m4xtsk3oxrh07duu6biqmpzsamndam 5386483 5386481 2022-07-28T14:35:41Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{MW version|version=1.25|comment=and after|gerrit change=166705}} '''Registrace rozšíření''' je mechanismus, který používá MediaWiki pro načítání [[Special:MyLanguage/Manual:Extensions|rozšíření]] a [[Special:MyLanguage/Manual:Skins|vzhledů]]. Konfigurační data vložíte do souboru s názvem <code>extension.json</code> nebo <code>skin.json</code> do kořenového adresáře vašeho rozšíření nebo vzhledu a MediaWiki je použije k registraci rozšíření a vzhledů. {{anchor|Migration for extension developers}} == Migrace pro správce webu == Před MediaWiki 1.25 byla konfigurace pro rozšíření a vzhledy prováděna v souboru PHP pomocí názvu přípony nebo vzhledu, například <code>MyExtension.php</code> nebo <code>MySkin.php</code>. <syntaxhighlight lang="php"> require_once "$IP/extensions/Hello/Hello.php"; require_once "$IP/extensions/FooBar/FooBar.php"; $wgFooBarEnable = true; require_once "$IP/skins/Baz/Baz.php"; require_once "/tmp/extension/some/where/else/BarFoo/BarFoo.php"; </syntaxhighlight> To lze převést na: <syntaxhighlight lang="php"> wfLoadExtensions( [ 'Hello', 'FooBar' ] ); $wgFooBarEnable = true; wfLoadSkin( 'Baz' ); wfLoadExtension( 'BarFoo', '/tmp/extension/some/where/else/BarFoo/extension.json' ); </syntaxhighlight> === Custom locations === Toto je nutné provést před načtením jakýchkoli rozšíření nebo vzhledů z nestandardních umístění adresáře: : Pokud svá rozšíření uchováváte na jiném místě než <code>$IP/extensions</code>, musíte přepsat {{wg|ExtensionDirectory}} nebo použít druhý parametr {{phpi|wfLoadExtension()}} k určení adresáře, ve kterém chcete rozšíření najít. :: If one or more of your extensions are stored in additional locations, use the second parameter of {{phpi|wfLoadExtension()}} to specify the location of the <code>.json</code> file for ''each'' of those extensions. ::: ''Note: {{phpi|wfLoadExtensions()}} '''(plural)''' always uses {{wg|ExtensionDirectory}} and cannot be overridden.'' :<syntaxhighlight lang="php"> $wgExtensionDirectory = '/some/path'; wfLoadExtension( 'FooBar' ); // Hledá $wgExtensionDirectory za /some/path/FooBar/extension.json wfLoadExtension( 'Hello', '/some/other/path/HelloV2/Hello.json' ); // Looks for /some/other/path/HelloV2/Hello.json </syntaxhighlight> : <span class="mw-translate-fuzzy">Pokud vaše vzhledy nejsou v <code>$IP/skins</code>, musíte přepsat špatně pojmenované {{wg|StyleDirectory}}.</span> :: If one or more of your skins are stored in additional locations, use the second parameter of {{phpi|wfLoadSkin()}} to specify the location of the <code>.json</code> file for ''each'' of those skins. :::''Note: {{phpi|wfLoadSkins()}} '''(plural)''' always uses {{wg|StyleDirectory}} and cannot be overridden.'' :<syntaxhighlight lang="php"> $wgStyleDirectory = '/my/skins'; wfLoadSkins( [ 'BarBaz', 'BazBar' ] ); // Vyhledá /my/skins/BarBaz/skin.json a /my/skins/BazBar/skin.json wfLoadSkin( 'BamBam', '/yet/another/path/BamBam/skin.json' ); // Looks for /yet/another/path/BamBam/skin.json </syntaxhighlight> == Migrace pro vývojáře rozšíření == Od MW 1.30 mohou být ID jmenného prostoru definovaná lokálně v <code>extension.json</code> před načtením rozšíření přepsána definováním příslušné konstanty v <code>LocalSettings.php</code>. Zvažte například následující deklaraci jmenného prostoru v souboru <code>extension.json</code>: <syntaxhighlight lang="javascript"> "namespaces": [ { "id": 1212, "constant": "NS_FOO", "name": "Foo" }, { "id": 1213, "constant": "NS_FOO_TALK", "name": "Foo_Talk" } ] </syntaxhighlight> To by ve výchozím nastavení způsobilo, že konstanta NS_FOO bude definována na hodnotu 1212. Toto však lze přepsat definováním příslušné konstanty v LocalSettings.php: <syntaxhighlight lang="php"> define( 'NS_FOO', 6688 ); define( 'NS_FOO_TALK', 6689 ); wfLoadExtension( "Foo" ); </syntaxhighlight> To by způsobilo, že jmenný prostor "Foo" bude registrován s ID 6688 namísto 1212. Při přepisování ID jmenného prostoru nezapomeňte, že všechny jmenné prostory talk musí mít lichá ID a ID jmenného prostoru talk musí být vždy ID jmenného prostoru subjektu plus jedna. :''Viz také [https://tools.wmflabs.org/extreg-wos/ registrace na stránce rozšíření (nyní superschopnosti)].'' Skript <code>{{ll|Manual:convertExtensionToRegistration.php|maintenance/convertExtensionToRegistration.php}}</code> vám pomůže s migrací ze vstupních bodů PHP do souboru metadat JSON. Pokud vaše rozšíření podporuje starší verze MediaWiki, měli byste si ponechat vstupní bod PHP <code>''FooBar/FooBar''.php</code>, dokud neukončíte podporu pro tyto starší verze. Ukázky příkazových řádků: <syntaxhighlight lang="shell-session"> $ cd core $ php maintenance/convertExtensionToRegistration.php extensions/MassMessage/MassMessage.php $ php maintenance/convertExtensionToRegistration.php skins/MonoBook/MonoBook.php --skin </syntaxhighlight> Možná budete muset odinstalovat své rozšíření z <code>LocalSettings.php</code>, pokud se zobrazí chyby, že konstanty nebo funkce nelze předefinovat. Soubor vstupního bodu PHP (FooBar.php) byste měli nahradit něčím podobným, jako je následující, aby nedošlo k přerušení wiki během procesu upgradu. <syntaxhighlight lang="php"> <?php if ( function_exists( 'wfLoadExtension' ) ) { wfLoadExtension( 'FooBar' ); // Udržujte i18n globals, aby se mergeMessageFileList.php nezměnil $wgMessagesDirs['FooBar'] = __DIR__ . '/i18n'; $wgExtensionMessagesFiles['FooBarAlias'] = __DIR__ . '/FooBar.alias.php'; wfWarn( 'Deprecated PHP entry point used for the FooBar extension. ' . 'Please use wfLoadExtension() instead, ' . 'see https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Extension_registration for more details.' ); return; } else { die( 'This version of the FooBar extension requires MediaWiki 1.29+' ); } </syntaxhighlight> Nebo vzhledů <syntaxhighlight lang="php"> <?php if ( function_exists( 'wfLoadSkin' ) ) { wfLoadSkin( 'FooBar' ); // Udržujte i18n globals, aby se mergeMessageFileList.php nezměnil $wgMessagesDirs['FooBar'] = __DIR__ . '/i18n'; $wgExtensionMessagesFiles['FooBarAlias'] = __DIR__ . '/FooBar.alias.php'; wfWarn( 'Deprecated PHP entry point used for the FooBar skin. Please use wfLoadSkin instead, ' . 'see https://www.mediawiki.org/wiki/Extension_registration for more details.' ); return; } else { die( 'This version of the FooBar skin requires MediaWiki 1.25+' ); } </syntaxhighlight> === Uchovávání dokumentace === Vstupní body PHP mají obvykle nějakou dokumentaci konfiguračních nastavení, která je užitečná a neměla by se ztratit. Bohužel JSON nepodporuje komentáře. Doporučuje se přenést konfigurační dokumentaci do souboru <code>README</code> v úložišti rozšíření. Konfiguraci byste také měli zdokumentovat na wiki na stránce Rozšíření:''MyExtension''. Část dokumentace je také možné zahrnout přímo do souboru <code>extension.json</code>. Registrace rozšíření ignoruje jakýkoli klíč v <code>extension.json</code> začínající znakem '<code>@</code>' ve struktuře nejvyšší úrovně, takže do těchto částí souboru JSON můžete vkládat komentáře. Například: <syntaxhighlight lang="javascript"> { "@note": "This file must be kept in sync with LocalisationUpdate.php", "@name": ... </syntaxhighlight> Verze 1 formátu <code>extension.json</code> také umožňovala <code>@note</code> v sekci <code>config</code>, ale to již není doporučeno ani podporováno ve verzi 2. Místo toho by mělo být použito pole <code>description</code> konfigurační proměnné. Toto by mělo být použito pouze pro krátké poznámky a komentáře. == Funkce == Pokud načítáte velký počet rozšíření, registrace rozšíření poskytne zvýšení výkonu, pokud máte nainstalováno [[Special:MyLanguage/Manual:Performance tuning|APC]] (nebo APCu). Rozšíření načtená společně s <code>wfLoadExtension'''s'''</code> (s množným číslem -s) budou uložena do mezipaměti společně. === Atributy === Opakujícím se problémem je, jak něco "zaregistrovat" s jinou příponou. Obvykle to znamenalo, že jste museli načíst jedno rozšíření před druhým. VisualEditor má například <code>$wgVisualEditorPluginModules</code>, který umožňuje rozšířením přidávat své moduly. Ve vstupním bodě VisualEditoru však má: <syntaxhighlight lang="php"> $wgVisualEditorPluginModules = []; </syntaxhighlight> To znamená, že pokud se nějaké rozšíření připojí k poli před načtením VisualEditoru, VE vymaže svůj záznam v tomto poli. Některá rozšíření závisela na konkrétním pořadí načítání, jiná to obcházela pomocí {{wg|ExtensionFunctions}}. Registrace rozšíření řeší tento problém pomocí "atributů". V rozšíření Math by jeho <code>extension.json</code> mělo něco jako: <syntaxhighlight lang="javascript"> { "VisualEditorPluginModules": [ "ext.math.visualEditor" ] } </syntaxhighlight> Počínaje verzí 2 musí být atributy definovány v samostatné sekci <code>attributes</code>. <code>Attributes</code> musí být objekt s názvem rozšíření jako klíčem a objektem párů atribut/hodnota jako hodnotou. Pamatujte, že klíč v podobjektu nesmí obsahovat název rozšíření! <syntaxhighlight lang="json"> { "attributes": { "VisualEditor": { "PluginModules": [ "ext.math.visualEditor" ] } }, "manifest_version": 2 } </syntaxhighlight> Když chce VisualEditor získat přístup k tomuto atributu, použije: <syntaxhighlight lang="php"> ExtensionRegistry::getInstance()->getAttribute( 'VisualEditorPluginModules' ); </syntaxhighlight> === Požadavky (závislosti) === Registrace rozšíření má sekci <code>requires</code> (vyžaduje), která funguje podobně jako sekce <code>require</code> [[Composer]]u. Umožňuje vývojáři rozšíření specifikovat několik požadavků na rozšíření, jako je konkrétní verze MediaWiki (nebo vyšší/menší než) nebo jiné rozšíření/vzhled. Chcete-li například přidat závislost na verzi MediaWiki, která je větší než 1.26.0, můžete do <code>extension.json</code> přidat následující kód: <ref>https://github.com/wikimedia/mediawiki/blob/78091899db2315916502421fdd2972f1d73237b3/docs/extension.schema.json#L273-L282</ref> <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.26.0" } } </syntaxhighlight> Klíč objektu <code>requires</code> je název závislosti (před MediaWiki 1.29.0 byla podporována pouze <code>MediaWiki</code>), hodnota je platné omezení verze (formát je [https://getcomposer.org/doc/articles/versions.md podle volby autora]). V MediaWiki 1.29.0 a vyšší můžete také přidat závislosti na vzhledech a dalších rozšířeních, jako jsou: <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.29.0", "extensions": { "ExampleExtension": "*" }, "skins": { "ExampleSkin": "*" } } } </syntaxhighlight> {{Note|1=<nowiki/> * Rozšíření a vzhledy uvedené zde, aby fungovaly, musí také používat systém registrace rozšíření popsaný na této stránce. * Řetězec přidaný k určení přípony nebo vzhledu musí být shodný s řetězcem uvedeným v poli "name" příslušného souboru "extension.json" nebo "skin.json". * Pro rozšíření využívající [[continuous integration|kontinuální integrace]] Wikimedie, je také třeba přidat závislosti do {{git file|project=integration/config |file=zuul/parameter_functions.py}} }} In MediaWiki 1.33.0(?!??) and above you can also add dependencies on PHP like so: <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.33.0", "platform": { "php": ">= 7.0.3" } } } </syntaxhighlight> === Zkontrolujte, zda je rozšíření načteno, aniž by bylo ve skutečnosti vyžadováno === Mnoho rozšíření může poskytovat funkce, které fungují pouze v případě, že je načteno i jiné rozšíření, aniž by tuto funkci skutečně potřebovali pro fungování základní funkce rozšíření. Jako příklad: Pokud je načteno rozšíření B, může rozšíření A poskytovat skutečný WYSIWYG editor, jinak bude používat jednoduchou textovou oblast. Rozšíření A může těžit z rozšíření B (pokud je načteno), ale ke správnému fungování nevyžaduje, aby bylo načteno. Za tímto účelem obvykle zkontrolujete, zda je rozšíření načteno, spíše než jej přidáte jako ''tvrdou'' závislost. Pro implementaci standardizovaného způsobu kontroly, zda je rozšíření načteno nebo ne (bez nutnosti práce navíc v rozšíření, která je v jiném rozšíření měkkou závislostí), lze použít registraci rozšíření. Implementuje metodu <code>isLoaded</code>, která vrací jednoduchý boolean, pokud je rozšíření načteno nebo ne (aby to fungovalo, musí být rozšíření načteno s registrací rozšíření). Příklad: <syntaxhighlight lang="php"> if ( ExtensionRegistry::getInstance()->isLoaded( 'ExtensionB' ) ) { // do things only, if extension B is loaded } </syntaxhighlight> {{MW version|version=1.32|comment=and after|gerrit change=455752}} Od [[MediaWiki 1.32]] je také možné zkontrolovat, zda je rozšíření načteno a zda splňuje dané omezení verze: <syntaxhighlight lang="php"> if ( ExtensionRegistry::getInstance()->isLoaded( 'ExtensionB', '>=1.2' ) ) { // do things only, if extension B is loaded and has a version of 1.2 or greater. } </syntaxhighlight> Pokud byste chtěli zkontrolovat, zda je v dřívějších verzích MediaWiki načtena konkrétní verze rozšíření, lze podobné informace extrahovat pomocí metody <code>getAllThings</code>, která vrací informace o kreditu pro všechna načtená rozšíření. Příklad: <syntaxhighlight lang="php"> $bVersion = ExtensionRegistry::getInstance()->getAllThings()['ExtensionB']['version'] ?? null; if ( $bVersion !== null && version_compare( $bVersion, '2.1.0', '>=' ) ) { // do things only, if extension B is loaded and has a version number greater than or equal to 2.1.0 } </syntaxhighlight> Alternativně, pokud rozšíření B definuje speciální konstantu určenou pro tento účel během načítání, je možné zkontrolovat, zda je definována: <syntaxhighlight lang="php"> if ( defined( 'ExtensionBVersion' ) ) { // You could also check for a version, if the constant holds the version // do things only, if extension B is loaded } </syntaxhighlight> Křehčím způsobem, kterému je třeba se vyhnout, je zkontrolovat, zda specifická třída rozšíření B existuje nebo ne, např. pomocí tohoto kódu: <syntaxhighlight lang="php"> if ( class_exists( 'ExtensionBHooks' ) ) { // do things only, if extension B its classes exist } </syntaxhighlight> To může přestat fungovat, pokud přípona existuje v systému souborů, ale není načtena, např. pokud byl pro automatické načítání použit composer. Pokud byla třída přejmenována nebo přestane existovat (např. protože není balíček public), dojde také k přerušení. Obecně je upřednostňováno sdílení kódu prostřednictvím komponent pro composer namísto rozšíření. Pokud třídy rozšíření potřebují pouze existovat, ale rozšíření nemusí být konfigurováno ani načteno, pro to, co chcete dělat, je to silný indikátor toho, že by tento kód měl být rozdělen na komponentu composer, na kterou byste se měli spolehnout. namísto. === Configs (Vaše nastavení rozšíření/vzhledů) === {{See also|Manual:Configuration for developers}} {{See also|Manual:Extension.json/Schema#config}} Ve výchozím nastavení <code>extension.json</code> předpokládá, že vaše konfigurační nastavení začíná předponou "wg". Pokud tomu tak není, můžete předponu přepsat pomocí speciálního klíče: <syntaxhighlight lang="json"> { "config": { "_prefix": "eg", "MyExtSetting": true } } </syntaxhighlight> To by použilo předponu "eg" a nastavilo globální proměnnou <code>$egMyExtSetting</code> na hodnotu true. Počínaje zveřejněním verze 2 poskytuje konfigurační sekce registrace rozšíření mnohem více funkcí a umožňuje vám popsat možnosti konfigurace mnohem podrobněji. Namísto jediného klíče -> úložiště hodnot pro možnosti konfigurace můžete také přidat následující informace. Obecná struktura <code>config</code> se mírně mění na následující, více objektově orientovanou verzi: <syntaxhighlight lang="json"> { "config_prefix": "eg", "config": { "MyExtSetting": { "value": true, "path": false, "description": "The description for the configuration", "descriptionmsg": "myextension-config-myextsetting", "public": true } }, "manifest_version": 2 } </syntaxhighlight> ==== Hodnota ==== Hodnota konfigurace se přesunula na toto místo. Toto je jediný požadovaný klíč pro konfigurační objekt. ==== Cesta ==== Booleovská hodnota klíče <code>path</code> identifikuje, zda má být hodnota konfigurační volby interpretována jako cesta souborového systému vzhledem ke kořenu adresáře rozšíření. Pokud je například hodnota konfigurace <code>myFile.png</code> a <code>path</code> je pravdivá, skutečná hodnota bude <code>/path/to/the/wiki/extensions/MyExtension/myFile.png</code>. ==== Popis ==== Klíč <code>description</code> pro možnost konfigurace může obsahovat nelokalizovaný řetězec, který lze použít k vysvětlení možnosti konfigurace dalším vývojářům nebo uživatelům (správcům systému) vašeho rozšíření. It may also be used as tooltip text on the parameters section of the extension infobox on the MediaWiki.org extension description page. Hodnota klíče popisu obvykle není vystavena frontendu wiki, ale podívejte se do přehledu, kde najdete další informace, jak by se tato funkce mohla v budoucnu používat! Existuje také možnost přidat klíč zprávy interního lokalizačního systému MediaWiki jako popis (<code>descriptionmsg</code>), který bude v budoucnu použit k odhalení popisu v rozhraní instalace MediaWiki. ==== veřejné / soukromé ==== Tato volba je booleovská, jejíž výchozí hodnota je false, což znamená, že konfigurační volba a hodnota jsou označeny jako "private". Tato hodnota se momentálně nikde nepoužívá, podívejte se do přehledu, kde se o této možnosti dozvíte více. ==== Výhled ==== {{tracked|T155155}} Výše uvedené změny jsou také přípravnými kroky pro vylepšenou správu konfigurace v MediaWiki. Výše uvedené změny nám umožňují např. odhalit možnosti konfigurace rozšíření v uživatelském rozhraní MediaWiki. K tomu je zapotřebí zpráva s lokalizovaným popisem (<code>descriptionmsg</code> a <code>description</code>) a indikace, zda má být konfigurační volba (<code>public</code>) veřejná nebo ne. === Automatické zjišťování testů jednotek === MediaWiki umožňuje libovolné rozšíření pro [[Special:MyLanguage/Manual:PHP unit testing/Writing unit tests for extensions|registraci testů phpunit]]. Bez registrace rozšíření byste museli zaregistrovat obslužný program pro háček {{ll|Manual:Hooks/UnitTestsList|UnitTestsList}}, který by vypadal asi takto: <syntaxhighlight lang="php"> public static function onUnitTestsList( array &$paths ) { $paths[] = __DIR__ . '/tests/phpunit/'; } </syntaxhighlight> (jak je popsáno v příručce). Tento kód však vypadá stejně pro mnoho rozšíření, takže byste to mohli nazvat zbytečnou duplikací kódu. Pokud vaše rozšíření používá registraci rozšíření a vaše testy phpunit jsou umístěny v podadresáři <code>tests/phpunit/</code> vašeho rozšíření, wraper phpunit MediaWiki automaticky objeví testy jednotek pomocí registrace rozšíření. Proto již nemusíte háček registrovat a nemusíte specifikovat, že vaše testy jednotek jsou uloženy ve výchozím adresáři. == Přizpůsobení registrace == :''See [[Manual:Extension.json/Schema#callback]].'' == Také composer.json == Pokud má rozšíření nebo vzhled knihovny závislosti, může je mít také soubor <code>composer.json</code>, viz {{ll|Manual:Composer.json best practices}}. Použijte pole <code>load_composer_autoloader</code>, aby MediaWiki používala automatické načítání Composer, když je to vhodné. Některá pole metadat se překrývají mezi <code>extension.json</code> a <code>composer.json</code> (diskutované v {{task|T89456}}), včetně: * <code>url</code> a <code>homepage</code> * <code>license-name</code> a <code>license</code> == Správce kódu == {{Component|mediawiki-configuration}} == Související stránky == * {{ll|Manual:Extension.json/Schema}} * Hlášení chyb v projektu [[phab:tag/mediawiki-configuration/|MediaWiki-Configuration]]. * Staré verze [[Special:MyLanguage/Manual:Developing extensions#Setup|Manual:Developing extensions#Setup]] (před květnem 2015) a {{wg|ExtensionCredits}} popisují starý přístup deklarování informací o rozšíření v kódu PHP a proměnných * {{ll|Manual:Extension registration/Limitations|2=Známá omezení}} * {{ll|Manual:Extension registration/Architecture|2=Přehled architektury}} * <code>[[phab:diffusion/MW/browse/master/docs/extension.schema.v2.json|docs/extension.schema.v2.json]]</code> je schéma pro <code>extension.json</code> (a skin.json). * [[Requests for comment/Extension registration|RfC]] o implementaci registrace rozšíření * [[toollabs:extreg-wos|Zeď superschopností pro registraci rozšíření!]] — přehled rozšíření, která je ještě třeba převést. * {{task|T98668}} — Sledovací karta pro převod všech rozšíření a vzhledů na Gitu pro použití registrace rozšíření. == Odkazy == {{reflist}} [[Category:Extension registration{{#translation:}}]] [[Category:Extension creation{{#translation:}}]] 0n2c40d03qt8zuiqeyaxuuzcxrtm1ho 5386485 5386483 2022-07-28T14:36:38Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{MW version|version=1.25|comment=and after|gerrit change=166705}} '''Registrace rozšíření''' je mechanismus, který používá MediaWiki pro načítání [[Special:MyLanguage/Manual:Extensions|rozšíření]] a [[Special:MyLanguage/Manual:Skins|vzhledů]]. Konfigurační data vložíte do souboru s názvem <code>extension.json</code> nebo <code>skin.json</code> do kořenového adresáře vašeho rozšíření nebo vzhledu a MediaWiki je použije k registraci rozšíření a vzhledů. {{anchor|Migration for extension developers}} == Migrace pro správce webu == Před MediaWiki 1.25 byla konfigurace pro rozšíření a vzhledy prováděna v souboru PHP pomocí názvu přípony nebo vzhledu, například <code>MyExtension.php</code> nebo <code>MySkin.php</code>. <syntaxhighlight lang="php"> require_once "$IP/extensions/Hello/Hello.php"; require_once "$IP/extensions/FooBar/FooBar.php"; $wgFooBarEnable = true; require_once "$IP/skins/Baz/Baz.php"; require_once "/tmp/extension/some/where/else/BarFoo/BarFoo.php"; </syntaxhighlight> To lze převést na: <syntaxhighlight lang="php"> wfLoadExtensions( [ 'Hello', 'FooBar' ] ); $wgFooBarEnable = true; wfLoadSkin( 'Baz' ); wfLoadExtension( 'BarFoo', '/tmp/extension/some/where/else/BarFoo/extension.json' ); </syntaxhighlight> === Custom locations === Toto je nutné provést před načtením jakýchkoli rozšíření nebo vzhledů z nestandardních umístění adresáře: : Pokud svá rozšíření uchováváte na jiném místě než <code>$IP/extensions</code>, musíte přepsat {{wg|ExtensionDirectory}} nebo použít druhý parametr {{phpi|wfLoadExtension()}} k určení adresáře, ve kterém chcete rozšíření najít. :: If one or more of your extensions are stored in additional locations, use the second parameter of {{phpi|wfLoadExtension()}} to specify the location of the <code>.json</code> file for ''each'' of those extensions. ::: ''Note: {{phpi|wfLoadExtensions()}} '''(plural)''' always uses {{wg|ExtensionDirectory}} and cannot be overridden.'' :<syntaxhighlight lang="php"> $wgExtensionDirectory = '/some/path'; wfLoadExtension( 'FooBar' ); // Hledá $wgExtensionDirectory za /some/path/FooBar/extension.json wfLoadExtension( 'Hello', '/some/other/path/HelloV2/Hello.json' ); // Looks for /some/other/path/HelloV2/Hello.json </syntaxhighlight> : Pokud vaše vzhledy nejsou v <code>$IP/skins</code>, musíte přepsat špatně pojmenovaný {{wg|StyleDirectory}}, ''nebo použít druhý parametr <code>wfLoadSkin()</code>'', abyste určili adresář, ve kterém se má vzhled najít. :: If one or more of your skins are stored in additional locations, use the second parameter of {{phpi|wfLoadSkin()}} to specify the location of the <code>.json</code> file for ''each'' of those skins. :::''Note: {{phpi|wfLoadSkins()}} '''(plural)''' always uses {{wg|StyleDirectory}} and cannot be overridden.'' :<syntaxhighlight lang="php"> $wgStyleDirectory = '/my/skins'; wfLoadSkins( [ 'BarBaz', 'BazBar' ] ); // Vyhledá /my/skins/BarBaz/skin.json a /my/skins/BazBar/skin.json wfLoadSkin( 'BamBam', '/yet/another/path/BamBam/skin.json' ); // Looks for /yet/another/path/BamBam/skin.json </syntaxhighlight> == Migrace pro vývojáře rozšíření == Od MW 1.30 mohou být ID jmenného prostoru definovaná lokálně v <code>extension.json</code> před načtením rozšíření přepsána definováním příslušné konstanty v <code>LocalSettings.php</code>. Zvažte například následující deklaraci jmenného prostoru v souboru <code>extension.json</code>: <syntaxhighlight lang="javascript"> "namespaces": [ { "id": 1212, "constant": "NS_FOO", "name": "Foo" }, { "id": 1213, "constant": "NS_FOO_TALK", "name": "Foo_Talk" } ] </syntaxhighlight> To by ve výchozím nastavení způsobilo, že konstanta NS_FOO bude definována na hodnotu 1212. Toto však lze přepsat definováním příslušné konstanty v LocalSettings.php: <syntaxhighlight lang="php"> define( 'NS_FOO', 6688 ); define( 'NS_FOO_TALK', 6689 ); wfLoadExtension( "Foo" ); </syntaxhighlight> To by způsobilo, že jmenný prostor "Foo" bude registrován s ID 6688 namísto 1212. Při přepisování ID jmenného prostoru nezapomeňte, že všechny jmenné prostory talk musí mít lichá ID a ID jmenného prostoru talk musí být vždy ID jmenného prostoru subjektu plus jedna. :''Viz také [https://tools.wmflabs.org/extreg-wos/ registrace na stránce rozšíření (nyní superschopnosti)].'' Skript <code>{{ll|Manual:convertExtensionToRegistration.php|maintenance/convertExtensionToRegistration.php}}</code> vám pomůže s migrací ze vstupních bodů PHP do souboru metadat JSON. Pokud vaše rozšíření podporuje starší verze MediaWiki, měli byste si ponechat vstupní bod PHP <code>''FooBar/FooBar''.php</code>, dokud neukončíte podporu pro tyto starší verze. Ukázky příkazových řádků: <syntaxhighlight lang="shell-session"> $ cd core $ php maintenance/convertExtensionToRegistration.php extensions/MassMessage/MassMessage.php $ php maintenance/convertExtensionToRegistration.php skins/MonoBook/MonoBook.php --skin </syntaxhighlight> Možná budete muset odinstalovat své rozšíření z <code>LocalSettings.php</code>, pokud se zobrazí chyby, že konstanty nebo funkce nelze předefinovat. Soubor vstupního bodu PHP (FooBar.php) byste měli nahradit něčím podobným, jako je následující, aby nedošlo k přerušení wiki během procesu upgradu. <syntaxhighlight lang="php"> <?php if ( function_exists( 'wfLoadExtension' ) ) { wfLoadExtension( 'FooBar' ); // Udržujte i18n globals, aby se mergeMessageFileList.php nezměnil $wgMessagesDirs['FooBar'] = __DIR__ . '/i18n'; $wgExtensionMessagesFiles['FooBarAlias'] = __DIR__ . '/FooBar.alias.php'; wfWarn( 'Deprecated PHP entry point used for the FooBar extension. ' . 'Please use wfLoadExtension() instead, ' . 'see https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Extension_registration for more details.' ); return; } else { die( 'This version of the FooBar extension requires MediaWiki 1.29+' ); } </syntaxhighlight> Nebo vzhledů <syntaxhighlight lang="php"> <?php if ( function_exists( 'wfLoadSkin' ) ) { wfLoadSkin( 'FooBar' ); // Udržujte i18n globals, aby se mergeMessageFileList.php nezměnil $wgMessagesDirs['FooBar'] = __DIR__ . '/i18n'; $wgExtensionMessagesFiles['FooBarAlias'] = __DIR__ . '/FooBar.alias.php'; wfWarn( 'Deprecated PHP entry point used for the FooBar skin. Please use wfLoadSkin instead, ' . 'see https://www.mediawiki.org/wiki/Extension_registration for more details.' ); return; } else { die( 'This version of the FooBar skin requires MediaWiki 1.25+' ); } </syntaxhighlight> === Uchovávání dokumentace === Vstupní body PHP mají obvykle nějakou dokumentaci konfiguračních nastavení, která je užitečná a neměla by se ztratit. Bohužel JSON nepodporuje komentáře. Doporučuje se přenést konfigurační dokumentaci do souboru <code>README</code> v úložišti rozšíření. Konfiguraci byste také měli zdokumentovat na wiki na stránce Rozšíření:''MyExtension''. Část dokumentace je také možné zahrnout přímo do souboru <code>extension.json</code>. Registrace rozšíření ignoruje jakýkoli klíč v <code>extension.json</code> začínající znakem '<code>@</code>' ve struktuře nejvyšší úrovně, takže do těchto částí souboru JSON můžete vkládat komentáře. Například: <syntaxhighlight lang="javascript"> { "@note": "This file must be kept in sync with LocalisationUpdate.php", "@name": ... </syntaxhighlight> Verze 1 formátu <code>extension.json</code> také umožňovala <code>@note</code> v sekci <code>config</code>, ale to již není doporučeno ani podporováno ve verzi 2. Místo toho by mělo být použito pole <code>description</code> konfigurační proměnné. Toto by mělo být použito pouze pro krátké poznámky a komentáře. == Funkce == Pokud načítáte velký počet rozšíření, registrace rozšíření poskytne zvýšení výkonu, pokud máte nainstalováno [[Special:MyLanguage/Manual:Performance tuning|APC]] (nebo APCu). Rozšíření načtená společně s <code>wfLoadExtension'''s'''</code> (s množným číslem -s) budou uložena do mezipaměti společně. === Atributy === Opakujícím se problémem je, jak něco "zaregistrovat" s jinou příponou. Obvykle to znamenalo, že jste museli načíst jedno rozšíření před druhým. VisualEditor má například <code>$wgVisualEditorPluginModules</code>, který umožňuje rozšířením přidávat své moduly. Ve vstupním bodě VisualEditoru však má: <syntaxhighlight lang="php"> $wgVisualEditorPluginModules = []; </syntaxhighlight> To znamená, že pokud se nějaké rozšíření připojí k poli před načtením VisualEditoru, VE vymaže svůj záznam v tomto poli. Některá rozšíření závisela na konkrétním pořadí načítání, jiná to obcházela pomocí {{wg|ExtensionFunctions}}. Registrace rozšíření řeší tento problém pomocí "atributů". V rozšíření Math by jeho <code>extension.json</code> mělo něco jako: <syntaxhighlight lang="javascript"> { "VisualEditorPluginModules": [ "ext.math.visualEditor" ] } </syntaxhighlight> Počínaje verzí 2 musí být atributy definovány v samostatné sekci <code>attributes</code>. <code>Attributes</code> musí být objekt s názvem rozšíření jako klíčem a objektem párů atribut/hodnota jako hodnotou. Pamatujte, že klíč v podobjektu nesmí obsahovat název rozšíření! <syntaxhighlight lang="json"> { "attributes": { "VisualEditor": { "PluginModules": [ "ext.math.visualEditor" ] } }, "manifest_version": 2 } </syntaxhighlight> Když chce VisualEditor získat přístup k tomuto atributu, použije: <syntaxhighlight lang="php"> ExtensionRegistry::getInstance()->getAttribute( 'VisualEditorPluginModules' ); </syntaxhighlight> === Požadavky (závislosti) === Registrace rozšíření má sekci <code>requires</code> (vyžaduje), která funguje podobně jako sekce <code>require</code> [[Composer]]u. Umožňuje vývojáři rozšíření specifikovat několik požadavků na rozšíření, jako je konkrétní verze MediaWiki (nebo vyšší/menší než) nebo jiné rozšíření/vzhled. Chcete-li například přidat závislost na verzi MediaWiki, která je větší než 1.26.0, můžete do <code>extension.json</code> přidat následující kód: <ref>https://github.com/wikimedia/mediawiki/blob/78091899db2315916502421fdd2972f1d73237b3/docs/extension.schema.json#L273-L282</ref> <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.26.0" } } </syntaxhighlight> Klíč objektu <code>requires</code> je název závislosti (před MediaWiki 1.29.0 byla podporována pouze <code>MediaWiki</code>), hodnota je platné omezení verze (formát je [https://getcomposer.org/doc/articles/versions.md podle volby autora]). V MediaWiki 1.29.0 a vyšší můžete také přidat závislosti na vzhledech a dalších rozšířeních, jako jsou: <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.29.0", "extensions": { "ExampleExtension": "*" }, "skins": { "ExampleSkin": "*" } } } </syntaxhighlight> {{Note|1=<nowiki/> * Rozšíření a vzhledy uvedené zde, aby fungovaly, musí také používat systém registrace rozšíření popsaný na této stránce. * Řetězec přidaný k určení přípony nebo vzhledu musí být shodný s řetězcem uvedeným v poli "name" příslušného souboru "extension.json" nebo "skin.json". * Pro rozšíření využívající [[continuous integration|kontinuální integrace]] Wikimedie, je také třeba přidat závislosti do {{git file|project=integration/config |file=zuul/parameter_functions.py}} }} In MediaWiki 1.33.0(?!??) and above you can also add dependencies on PHP like so: <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.33.0", "platform": { "php": ">= 7.0.3" } } } </syntaxhighlight> === Zkontrolujte, zda je rozšíření načteno, aniž by bylo ve skutečnosti vyžadováno === Mnoho rozšíření může poskytovat funkce, které fungují pouze v případě, že je načteno i jiné rozšíření, aniž by tuto funkci skutečně potřebovali pro fungování základní funkce rozšíření. Jako příklad: Pokud je načteno rozšíření B, může rozšíření A poskytovat skutečný WYSIWYG editor, jinak bude používat jednoduchou textovou oblast. Rozšíření A může těžit z rozšíření B (pokud je načteno), ale ke správnému fungování nevyžaduje, aby bylo načteno. Za tímto účelem obvykle zkontrolujete, zda je rozšíření načteno, spíše než jej přidáte jako ''tvrdou'' závislost. Pro implementaci standardizovaného způsobu kontroly, zda je rozšíření načteno nebo ne (bez nutnosti práce navíc v rozšíření, která je v jiném rozšíření měkkou závislostí), lze použít registraci rozšíření. Implementuje metodu <code>isLoaded</code>, která vrací jednoduchý boolean, pokud je rozšíření načteno nebo ne (aby to fungovalo, musí být rozšíření načteno s registrací rozšíření). Příklad: <syntaxhighlight lang="php"> if ( ExtensionRegistry::getInstance()->isLoaded( 'ExtensionB' ) ) { // do things only, if extension B is loaded } </syntaxhighlight> {{MW version|version=1.32|comment=and after|gerrit change=455752}} Od [[MediaWiki 1.32]] je také možné zkontrolovat, zda je rozšíření načteno a zda splňuje dané omezení verze: <syntaxhighlight lang="php"> if ( ExtensionRegistry::getInstance()->isLoaded( 'ExtensionB', '>=1.2' ) ) { // do things only, if extension B is loaded and has a version of 1.2 or greater. } </syntaxhighlight> Pokud byste chtěli zkontrolovat, zda je v dřívějších verzích MediaWiki načtena konkrétní verze rozšíření, lze podobné informace extrahovat pomocí metody <code>getAllThings</code>, která vrací informace o kreditu pro všechna načtená rozšíření. Příklad: <syntaxhighlight lang="php"> $bVersion = ExtensionRegistry::getInstance()->getAllThings()['ExtensionB']['version'] ?? null; if ( $bVersion !== null && version_compare( $bVersion, '2.1.0', '>=' ) ) { // do things only, if extension B is loaded and has a version number greater than or equal to 2.1.0 } </syntaxhighlight> Alternativně, pokud rozšíření B definuje speciální konstantu určenou pro tento účel během načítání, je možné zkontrolovat, zda je definována: <syntaxhighlight lang="php"> if ( defined( 'ExtensionBVersion' ) ) { // You could also check for a version, if the constant holds the version // do things only, if extension B is loaded } </syntaxhighlight> Křehčím způsobem, kterému je třeba se vyhnout, je zkontrolovat, zda specifická třída rozšíření B existuje nebo ne, např. pomocí tohoto kódu: <syntaxhighlight lang="php"> if ( class_exists( 'ExtensionBHooks' ) ) { // do things only, if extension B its classes exist } </syntaxhighlight> To může přestat fungovat, pokud přípona existuje v systému souborů, ale není načtena, např. pokud byl pro automatické načítání použit composer. Pokud byla třída přejmenována nebo přestane existovat (např. protože není balíček public), dojde také k přerušení. Obecně je upřednostňováno sdílení kódu prostřednictvím komponent pro composer namísto rozšíření. Pokud třídy rozšíření potřebují pouze existovat, ale rozšíření nemusí být konfigurováno ani načteno, pro to, co chcete dělat, je to silný indikátor toho, že by tento kód měl být rozdělen na komponentu composer, na kterou byste se měli spolehnout. namísto. === Configs (Vaše nastavení rozšíření/vzhledů) === {{See also|Manual:Configuration for developers}} {{See also|Manual:Extension.json/Schema#config}} Ve výchozím nastavení <code>extension.json</code> předpokládá, že vaše konfigurační nastavení začíná předponou "wg". Pokud tomu tak není, můžete předponu přepsat pomocí speciálního klíče: <syntaxhighlight lang="json"> { "config": { "_prefix": "eg", "MyExtSetting": true } } </syntaxhighlight> To by použilo předponu "eg" a nastavilo globální proměnnou <code>$egMyExtSetting</code> na hodnotu true. Počínaje zveřejněním verze 2 poskytuje konfigurační sekce registrace rozšíření mnohem více funkcí a umožňuje vám popsat možnosti konfigurace mnohem podrobněji. Namísto jediného klíče -> úložiště hodnot pro možnosti konfigurace můžete také přidat následující informace. Obecná struktura <code>config</code> se mírně mění na následující, více objektově orientovanou verzi: <syntaxhighlight lang="json"> { "config_prefix": "eg", "config": { "MyExtSetting": { "value": true, "path": false, "description": "The description for the configuration", "descriptionmsg": "myextension-config-myextsetting", "public": true } }, "manifest_version": 2 } </syntaxhighlight> ==== Hodnota ==== Hodnota konfigurace se přesunula na toto místo. Toto je jediný požadovaný klíč pro konfigurační objekt. ==== Cesta ==== Booleovská hodnota klíče <code>path</code> identifikuje, zda má být hodnota konfigurační volby interpretována jako cesta souborového systému vzhledem ke kořenu adresáře rozšíření. Pokud je například hodnota konfigurace <code>myFile.png</code> a <code>path</code> je pravdivá, skutečná hodnota bude <code>/path/to/the/wiki/extensions/MyExtension/myFile.png</code>. ==== Popis ==== Klíč <code>description</code> pro možnost konfigurace může obsahovat nelokalizovaný řetězec, který lze použít k vysvětlení možnosti konfigurace dalším vývojářům nebo uživatelům (správcům systému) vašeho rozšíření. It may also be used as tooltip text on the parameters section of the extension infobox on the MediaWiki.org extension description page. Hodnota klíče popisu obvykle není vystavena frontendu wiki, ale podívejte se do přehledu, kde najdete další informace, jak by se tato funkce mohla v budoucnu používat! Existuje také možnost přidat klíč zprávy interního lokalizačního systému MediaWiki jako popis (<code>descriptionmsg</code>), který bude v budoucnu použit k odhalení popisu v rozhraní instalace MediaWiki. ==== veřejné / soukromé ==== Tato volba je booleovská, jejíž výchozí hodnota je false, což znamená, že konfigurační volba a hodnota jsou označeny jako "private". Tato hodnota se momentálně nikde nepoužívá, podívejte se do přehledu, kde se o této možnosti dozvíte více. ==== Výhled ==== {{tracked|T155155}} Výše uvedené změny jsou také přípravnými kroky pro vylepšenou správu konfigurace v MediaWiki. Výše uvedené změny nám umožňují např. odhalit možnosti konfigurace rozšíření v uživatelském rozhraní MediaWiki. K tomu je zapotřebí zpráva s lokalizovaným popisem (<code>descriptionmsg</code> a <code>description</code>) a indikace, zda má být konfigurační volba (<code>public</code>) veřejná nebo ne. === Automatické zjišťování testů jednotek === MediaWiki umožňuje libovolné rozšíření pro [[Special:MyLanguage/Manual:PHP unit testing/Writing unit tests for extensions|registraci testů phpunit]]. Bez registrace rozšíření byste museli zaregistrovat obslužný program pro háček {{ll|Manual:Hooks/UnitTestsList|UnitTestsList}}, který by vypadal asi takto: <syntaxhighlight lang="php"> public static function onUnitTestsList( array &$paths ) { $paths[] = __DIR__ . '/tests/phpunit/'; } </syntaxhighlight> (jak je popsáno v příručce). Tento kód však vypadá stejně pro mnoho rozšíření, takže byste to mohli nazvat zbytečnou duplikací kódu. Pokud vaše rozšíření používá registraci rozšíření a vaše testy phpunit jsou umístěny v podadresáři <code>tests/phpunit/</code> vašeho rozšíření, wraper phpunit MediaWiki automaticky objeví testy jednotek pomocí registrace rozšíření. Proto již nemusíte háček registrovat a nemusíte specifikovat, že vaše testy jednotek jsou uloženy ve výchozím adresáři. == Přizpůsobení registrace == :''See [[Manual:Extension.json/Schema#callback]].'' == Také composer.json == Pokud má rozšíření nebo vzhled knihovny závislosti, může je mít také soubor <code>composer.json</code>, viz {{ll|Manual:Composer.json best practices}}. Použijte pole <code>load_composer_autoloader</code>, aby MediaWiki používala automatické načítání Composer, když je to vhodné. Některá pole metadat se překrývají mezi <code>extension.json</code> a <code>composer.json</code> (diskutované v {{task|T89456}}), včetně: * <code>url</code> a <code>homepage</code> * <code>license-name</code> a <code>license</code> == Správce kódu == {{Component|mediawiki-configuration}} == Související stránky == * {{ll|Manual:Extension.json/Schema}} * Hlášení chyb v projektu [[phab:tag/mediawiki-configuration/|MediaWiki-Configuration]]. * Staré verze [[Special:MyLanguage/Manual:Developing extensions#Setup|Manual:Developing extensions#Setup]] (před květnem 2015) a {{wg|ExtensionCredits}} popisují starý přístup deklarování informací o rozšíření v kódu PHP a proměnných * {{ll|Manual:Extension registration/Limitations|2=Známá omezení}} * {{ll|Manual:Extension registration/Architecture|2=Přehled architektury}} * <code>[[phab:diffusion/MW/browse/master/docs/extension.schema.v2.json|docs/extension.schema.v2.json]]</code> je schéma pro <code>extension.json</code> (a skin.json). * [[Requests for comment/Extension registration|RfC]] o implementaci registrace rozšíření * [[toollabs:extreg-wos|Zeď superschopností pro registraci rozšíření!]] — přehled rozšíření, která je ještě třeba převést. * {{task|T98668}} — Sledovací karta pro převod všech rozšíření a vzhledů na Gitu pro použití registrace rozšíření. == Odkazy == {{reflist}} [[Category:Extension registration{{#translation:}}]] [[Category:Extension creation{{#translation:}}]] b33feud1sj2a1qk0uu0j1c17h3qutr4 5386487 5386485 2022-07-28T14:38:50Z ENeRZet 17359278 wikitext text/x-wiki <languages /> {{MW version|version=1.25|comment=and after|gerrit change=166705}} '''Registrace rozšíření''' je mechanismus, který používá MediaWiki pro načítání [[Special:MyLanguage/Manual:Extensions|rozšíření]] a [[Special:MyLanguage/Manual:Skins|vzhledů]]. Konfigurační data vložíte do souboru s názvem <code>extension.json</code> nebo <code>skin.json</code> do kořenového adresáře vašeho rozšíření nebo vzhledu a MediaWiki je použije k registraci rozšíření a vzhledů. {{anchor|Migration for extension developers}} == Migrace pro správce webu == Před MediaWiki 1.25 byla konfigurace pro rozšíření a vzhledy prováděna v souboru PHP pomocí názvu přípony nebo vzhledu, například <code>MyExtension.php</code> nebo <code>MySkin.php</code>. <syntaxhighlight lang="php"> require_once "$IP/extensions/Hello/Hello.php"; require_once "$IP/extensions/FooBar/FooBar.php"; $wgFooBarEnable = true; require_once "$IP/skins/Baz/Baz.php"; require_once "/tmp/extension/some/where/else/BarFoo/BarFoo.php"; </syntaxhighlight> To lze převést na: <syntaxhighlight lang="php"> wfLoadExtensions( [ 'Hello', 'FooBar' ] ); $wgFooBarEnable = true; wfLoadSkin( 'Baz' ); wfLoadExtension( 'BarFoo', '/tmp/extension/some/where/else/BarFoo/extension.json' ); </syntaxhighlight> === Custom locations === Toto je nutné provést před načtením jakýchkoli rozšíření nebo vzhledů z nestandardních umístění adresáře: : Pokud svá rozšíření uchováváte na jiném místě než <code>$IP/extensions</code>, musíte přepsat {{wg|ExtensionDirectory}} nebo použít druhý parametr {{phpi|wfLoadExtension()}} k určení adresáře, ve kterém chcete rozšíření najít. :: If one or more of your extensions are stored in additional locations, use the second parameter of {{phpi|wfLoadExtension()}} to specify the location of the <code>.json</code> file for ''each'' of those extensions. ::: ''Note: {{phpi|wfLoadExtensions()}} '''(plural)''' always uses {{wg|ExtensionDirectory}} and cannot be overridden.'' :<syntaxhighlight lang="php"> $wgExtensionDirectory = '/some/path'; wfLoadExtension( 'FooBar' ); // Hledá $wgExtensionDirectory za /some/path/FooBar/extension.json wfLoadExtension( 'Hello', '/some/other/path/HelloV2/Hello.json' ); // Looks for /some/other/path/HelloV2/Hello.json </syntaxhighlight> : Pokud vaše vzhledy nejsou v <code>$IP/skins</code>, musíte přepsat špatně pojmenovaný {{wg|StyleDirectory}}, ''nebo použít druhý parametr <code>wfLoadSkin()</code>'', abyste určili adresář, ve kterém se má vzhled najít. :: If one or more of your skins are stored in additional locations, use the second parameter of {{phpi|wfLoadSkin()}} to specify the location of the <code>.json</code> file for ''each'' of those skins. :::''Note: {{phpi|wfLoadSkins()}} '''(plural)''' always uses {{wg|StyleDirectory}} and cannot be overridden.'' :<syntaxhighlight lang="php"> $wgStyleDirectory = '/my/skins'; wfLoadSkins( [ 'BarBaz', 'BazBar' ] ); // Vyhledá v $wgStyleDirectory za oba /my/skins/BarBaz/skin.json a /my/skins/BazBar/skin.json wfLoadSkin( 'BamBam', '/yet/another/path/BamBam/skin.json' ); // Looks for /yet/another/path/BamBam/skin.json </syntaxhighlight> == Migrace pro vývojáře rozšíření == Od MW 1.30 mohou být ID jmenného prostoru definovaná lokálně v <code>extension.json</code> před načtením rozšíření přepsána definováním příslušné konstanty v <code>LocalSettings.php</code>. Zvažte například následující deklaraci jmenného prostoru v souboru <code>extension.json</code>: <syntaxhighlight lang="javascript"> "namespaces": [ { "id": 1212, "constant": "NS_FOO", "name": "Foo" }, { "id": 1213, "constant": "NS_FOO_TALK", "name": "Foo_Talk" } ] </syntaxhighlight> To by ve výchozím nastavení způsobilo, že konstanta NS_FOO bude definována na hodnotu 1212. Toto však lze přepsat definováním příslušné konstanty v LocalSettings.php: <syntaxhighlight lang="php"> define( 'NS_FOO', 6688 ); define( 'NS_FOO_TALK', 6689 ); wfLoadExtension( "Foo" ); </syntaxhighlight> To by způsobilo, že jmenný prostor "Foo" bude registrován s ID 6688 namísto 1212. Při přepisování ID jmenného prostoru nezapomeňte, že všechny jmenné prostory talk musí mít lichá ID a ID jmenného prostoru talk musí být vždy ID jmenného prostoru subjektu plus jedna. :''Viz také [https://tools.wmflabs.org/extreg-wos/ registrace na stránce rozšíření (nyní superschopnosti)].'' Skript <code>{{ll|Manual:convertExtensionToRegistration.php|maintenance/convertExtensionToRegistration.php}}</code> vám pomůže s migrací ze vstupních bodů PHP do souboru metadat JSON. Pokud vaše rozšíření podporuje starší verze MediaWiki, měli byste si ponechat vstupní bod PHP <code>''FooBar/FooBar''.php</code>, dokud neukončíte podporu pro tyto starší verze. Ukázky příkazových řádků: <syntaxhighlight lang="shell-session"> $ cd core $ php maintenance/convertExtensionToRegistration.php extensions/MassMessage/MassMessage.php $ php maintenance/convertExtensionToRegistration.php skins/MonoBook/MonoBook.php --skin </syntaxhighlight> Možná budete muset odinstalovat své rozšíření z <code>LocalSettings.php</code>, pokud se zobrazí chyby, že konstanty nebo funkce nelze předefinovat. Soubor vstupního bodu PHP (FooBar.php) byste měli nahradit něčím podobným, jako je následující, aby nedošlo k přerušení wiki během procesu upgradu. <syntaxhighlight lang="php"> <?php if ( function_exists( 'wfLoadExtension' ) ) { wfLoadExtension( 'FooBar' ); // Udržujte i18n globals, aby se mergeMessageFileList.php nezměnil $wgMessagesDirs['FooBar'] = __DIR__ . '/i18n'; $wgExtensionMessagesFiles['FooBarAlias'] = __DIR__ . '/FooBar.alias.php'; wfWarn( 'Deprecated PHP entry point used for the FooBar extension. ' . 'Please use wfLoadExtension() instead, ' . 'see https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Extension_registration for more details.' ); return; } else { die( 'This version of the FooBar extension requires MediaWiki 1.29+' ); } </syntaxhighlight> Nebo vzhledů <syntaxhighlight lang="php"> <?php if ( function_exists( 'wfLoadSkin' ) ) { wfLoadSkin( 'FooBar' ); // Udržujte i18n globals, aby se mergeMessageFileList.php nezměnil $wgMessagesDirs['FooBar'] = __DIR__ . '/i18n'; $wgExtensionMessagesFiles['FooBarAlias'] = __DIR__ . '/FooBar.alias.php'; wfWarn( 'Deprecated PHP entry point used for the FooBar skin. Please use wfLoadSkin instead, ' . 'see https://www.mediawiki.org/wiki/Extension_registration for more details.' ); return; } else { die( 'This version of the FooBar skin requires MediaWiki 1.25+' ); } </syntaxhighlight> === Uchovávání dokumentace === Vstupní body PHP mají obvykle nějakou dokumentaci konfiguračních nastavení, která je užitečná a neměla by se ztratit. Bohužel JSON nepodporuje komentáře. Doporučuje se přenést konfigurační dokumentaci do souboru <code>README</code> v úložišti rozšíření. Konfiguraci byste také měli zdokumentovat na wiki na stránce Rozšíření:''MyExtension''. Část dokumentace je také možné zahrnout přímo do souboru <code>extension.json</code>. Registrace rozšíření ignoruje jakýkoli klíč v <code>extension.json</code> začínající znakem '<code>@</code>' ve struktuře nejvyšší úrovně, takže do těchto částí souboru JSON můžete vkládat komentáře. Například: <syntaxhighlight lang="javascript"> { "@note": "This file must be kept in sync with LocalisationUpdate.php", "@name": ... </syntaxhighlight> Verze 1 formátu <code>extension.json</code> také umožňovala <code>@note</code> v sekci <code>config</code>, ale to již není doporučeno ani podporováno ve verzi 2. Místo toho by mělo být použito pole <code>description</code> konfigurační proměnné. Toto by mělo být použito pouze pro krátké poznámky a komentáře. == Funkce == Pokud načítáte velký počet rozšíření, registrace rozšíření poskytne zvýšení výkonu, pokud máte nainstalováno [[Special:MyLanguage/Manual:Performance tuning|APC]] (nebo APCu). Rozšíření načtená společně s <code>wfLoadExtension'''s'''</code> (s množným číslem -s) budou uložena do mezipaměti společně. === Atributy === Opakujícím se problémem je, jak něco "zaregistrovat" s jinou příponou. Obvykle to znamenalo, že jste museli načíst jedno rozšíření před druhým. VisualEditor má například <code>$wgVisualEditorPluginModules</code>, který umožňuje rozšířením přidávat své moduly. Ve vstupním bodě VisualEditoru však má: <syntaxhighlight lang="php"> $wgVisualEditorPluginModules = []; </syntaxhighlight> To znamená, že pokud se nějaké rozšíření připojí k poli před načtením VisualEditoru, VE vymaže svůj záznam v tomto poli. Některá rozšíření závisela na konkrétním pořadí načítání, jiná to obcházela pomocí {{wg|ExtensionFunctions}}. Registrace rozšíření řeší tento problém pomocí "atributů". V rozšíření Math by jeho <code>extension.json</code> mělo něco jako: <syntaxhighlight lang="javascript"> { "VisualEditorPluginModules": [ "ext.math.visualEditor" ] } </syntaxhighlight> Počínaje verzí 2 musí být atributy definovány v samostatné sekci <code>attributes</code>. <code>Attributes</code> musí být objekt s názvem rozšíření jako klíčem a objektem párů atribut/hodnota jako hodnotou. Pamatujte, že klíč v podobjektu nesmí obsahovat název rozšíření! <syntaxhighlight lang="json"> { "attributes": { "VisualEditor": { "PluginModules": [ "ext.math.visualEditor" ] } }, "manifest_version": 2 } </syntaxhighlight> Když chce VisualEditor získat přístup k tomuto atributu, použije: <syntaxhighlight lang="php"> ExtensionRegistry::getInstance()->getAttribute( 'VisualEditorPluginModules' ); </syntaxhighlight> === Požadavky (závislosti) === Registrace rozšíření má sekci <code>requires</code> (vyžaduje), která funguje podobně jako sekce <code>require</code> [[Composer]]u. Umožňuje vývojáři rozšíření specifikovat několik požadavků na rozšíření, jako je konkrétní verze MediaWiki (nebo vyšší/menší než) nebo jiné rozšíření/vzhled. Chcete-li například přidat závislost na verzi MediaWiki, která je větší než 1.26.0, můžete do <code>extension.json</code> přidat následující kód: <ref>https://github.com/wikimedia/mediawiki/blob/78091899db2315916502421fdd2972f1d73237b3/docs/extension.schema.json#L273-L282</ref> <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.26.0" } } </syntaxhighlight> Klíč objektu <code>requires</code> je název závislosti (před MediaWiki 1.29.0 byla podporována pouze <code>MediaWiki</code>), hodnota je platné omezení verze (formát je [https://getcomposer.org/doc/articles/versions.md podle volby autora]). V MediaWiki 1.29.0 a vyšší můžete také přidat závislosti na vzhledech a dalších rozšířeních, jako jsou: <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.29.0", "extensions": { "ExampleExtension": "*" }, "skins": { "ExampleSkin": "*" } } } </syntaxhighlight> {{Note|1=<nowiki/> * Rozšíření a vzhledy uvedené zde, aby fungovaly, musí také používat systém registrace rozšíření popsaný na této stránce. * Řetězec přidaný k určení přípony nebo vzhledu musí být shodný s řetězcem uvedeným v poli "name" příslušného souboru "extension.json" nebo "skin.json". * Pro rozšíření využívající [[continuous integration|kontinuální integrace]] Wikimedie, je také třeba přidat závislosti do {{git file|project=integration/config |file=zuul/parameter_functions.py}} }} In MediaWiki 1.33.0(?!??) and above you can also add dependencies on PHP like so: <syntaxhighlight lang="json"> { "requires": { "MediaWiki": ">= 1.33.0", "platform": { "php": ">= 7.0.3" } } } </syntaxhighlight> === Zkontrolujte, zda je rozšíření načteno, aniž by bylo ve skutečnosti vyžadováno === Mnoho rozšíření může poskytovat funkce, které fungují pouze v případě, že je načteno i jiné rozšíření, aniž by tuto funkci skutečně potřebovali pro fungování základní funkce rozšíření. Jako příklad: Pokud je načteno rozšíření B, může rozšíření A poskytovat skutečný WYSIWYG editor, jinak bude používat jednoduchou textovou oblast. Rozšíření A může těžit z rozšíření B (pokud je načteno), ale ke správnému fungování nevyžaduje, aby bylo načteno. Za tímto účelem obvykle zkontrolujete, zda je rozšíření načteno, spíše než jej přidáte jako ''tvrdou'' závislost. Pro implementaci standardizovaného způsobu kontroly, zda je rozšíření načteno nebo ne (bez nutnosti práce navíc v rozšíření, která je v jiném rozšíření měkkou závislostí), lze použít registraci rozšíření. Implementuje metodu <code>isLoaded</code>, která vrací jednoduchý boolean, pokud je rozšíření načteno nebo ne (aby to fungovalo, musí být rozšíření načteno s registrací rozšíření). Příklad: <syntaxhighlight lang="php"> if ( ExtensionRegistry::getInstance()->isLoaded( 'ExtensionB' ) ) { // do things only, if extension B is loaded } </syntaxhighlight> {{MW version|version=1.32|comment=and after|gerrit change=455752}} Od [[MediaWiki 1.32]] je také možné zkontrolovat, zda je rozšíření načteno a zda splňuje dané omezení verze: <syntaxhighlight lang="php"> if ( ExtensionRegistry::getInstance()->isLoaded( 'ExtensionB', '>=1.2' ) ) { // do things only, if extension B is loaded and has a version of 1.2 or greater. } </syntaxhighlight> Pokud byste chtěli zkontrolovat, zda je v dřívějších verzích MediaWiki načtena konkrétní verze rozšíření, lze podobné informace extrahovat pomocí metody <code>getAllThings</code>, která vrací informace o kreditu pro všechna načtená rozšíření. Příklad: <syntaxhighlight lang="php"> $bVersion = ExtensionRegistry::getInstance()->getAllThings()['ExtensionB']['version'] ?? null; if ( $bVersion !== null && version_compare( $bVersion, '2.1.0', '>=' ) ) { // do things only, if extension B is loaded and has a version number greater than or equal to 2.1.0 } </syntaxhighlight> Alternativně, pokud rozšíření B definuje speciální konstantu určenou pro tento účel během načítání, je možné zkontrolovat, zda je definována: <syntaxhighlight lang="php"> if ( defined( 'ExtensionBVersion' ) ) { // You could also check for a version, if the constant holds the version // do things only, if extension B is loaded } </syntaxhighlight> Křehčím způsobem, kterému je třeba se vyhnout, je zkontrolovat, zda specifická třída rozšíření B existuje nebo ne, např. pomocí tohoto kódu: <syntaxhighlight lang="php"> if ( class_exists( 'ExtensionBHooks' ) ) { // do things only, if extension B its classes exist } </syntaxhighlight> To může přestat fungovat, pokud přípona existuje v systému souborů, ale není načtena, např. pokud byl pro automatické načítání použit composer. Pokud byla třída přejmenována nebo přestane existovat (např. protože není balíček public), dojde také k přerušení. Obecně je upřednostňováno sdílení kódu prostřednictvím komponent pro composer namísto rozšíření. Pokud třídy rozšíření potřebují pouze existovat, ale rozšíření nemusí být konfigurováno ani načteno, pro to, co chcete dělat, je to silný indikátor toho, že by tento kód měl být rozdělen na komponentu composer, na kterou byste se měli spolehnout. namísto. === Configs (Vaše nastavení rozšíření/vzhledů) === {{See also|Manual:Configuration for developers}} {{See also|Manual:Extension.json/Schema#config}} Ve výchozím nastavení <code>extension.json</code> předpokládá, že vaše konfigurační nastavení začíná předponou "wg". Pokud tomu tak není, můžete předponu přepsat pomocí speciálního klíče: <syntaxhighlight lang="json"> { "config": { "_prefix": "eg", "MyExtSetting": true } } </syntaxhighlight> To by použilo předponu "eg" a nastavilo globální proměnnou <code>$egMyExtSetting</code> na hodnotu true. Počínaje zveřejněním verze 2 poskytuje konfigurační sekce registrace rozšíření mnohem více funkcí a umožňuje vám popsat možnosti konfigurace mnohem podrobněji. Namísto jediného klíče -> úložiště hodnot pro možnosti konfigurace můžete také přidat následující informace. Obecná struktura <code>config</code> se mírně mění na následující, více objektově orientovanou verzi: <syntaxhighlight lang="json"> { "config_prefix": "eg", "config": { "MyExtSetting": { "value": true, "path": false, "description": "The description for the configuration", "descriptionmsg": "myextension-config-myextsetting", "public": true } }, "manifest_version": 2 } </syntaxhighlight> ==== Hodnota ==== Hodnota konfigurace se přesunula na toto místo. Toto je jediný požadovaný klíč pro konfigurační objekt. ==== Cesta ==== Booleovská hodnota klíče <code>path</code> identifikuje, zda má být hodnota konfigurační volby interpretována jako cesta souborového systému vzhledem ke kořenu adresáře rozšíření. Pokud je například hodnota konfigurace <code>myFile.png</code> a <code>path</code> je pravdivá, skutečná hodnota bude <code>/path/to/the/wiki/extensions/MyExtension/myFile.png</code>. ==== Popis ==== Klíč <code>description</code> pro možnost konfigurace může obsahovat nelokalizovaný řetězec, který lze použít k vysvětlení možnosti konfigurace dalším vývojářům nebo uživatelům (správcům systému) vašeho rozšíření. It may also be used as tooltip text on the parameters section of the extension infobox on the MediaWiki.org extension description page. Hodnota klíče popisu obvykle není vystavena frontendu wiki, ale podívejte se do přehledu, kde najdete další informace, jak by se tato funkce mohla v budoucnu používat! Existuje také možnost přidat klíč zprávy interního lokalizačního systému MediaWiki jako popis (<code>descriptionmsg</code>), který bude v budoucnu použit k odhalení popisu v rozhraní instalace MediaWiki. ==== veřejné / soukromé ==== Tato volba je booleovská, jejíž výchozí hodnota je false, což znamená, že konfigurační volba a hodnota jsou označeny jako "private". Tato hodnota se momentálně nikde nepoužívá, podívejte se do přehledu, kde se o této možnosti dozvíte více. ==== Výhled ==== {{tracked|T155155}} Výše uvedené změny jsou také přípravnými kroky pro vylepšenou správu konfigurace v MediaWiki. Výše uvedené změny nám umožňují např. odhalit možnosti konfigurace rozšíření v uživatelském rozhraní MediaWiki. K tomu je zapotřebí zpráva s lokalizovaným popisem (<code>descriptionmsg</code> a <code>description</code>) a indikace, zda má být konfigurační volba (<code>public</code>) veřejná nebo ne. === Automatické zjišťování testů jednotek === MediaWiki umožňuje libovolné rozšíření pro [[Special:MyLanguage/Manual:PHP unit testing/Writing unit tests for extensions|registraci testů phpunit]]. Bez registrace rozšíření byste museli zaregistrovat obslužný program pro háček {{ll|Manual:Hooks/UnitTestsList|UnitTestsList}}, který by vypadal asi takto: <syntaxhighlight lang="php"> public static function onUnitTestsList( array &$paths ) { $paths[] = __DIR__ . '/tests/phpunit/'; } </syntaxhighlight> (jak je popsáno v příručce). Tento kód však vypadá stejně pro mnoho rozšíření, takže byste to mohli nazvat zbytečnou duplikací kódu. Pokud vaše rozšíření používá registraci rozšíření a vaše testy phpunit jsou umístěny v podadresáři <code>tests/phpunit/</code> vašeho rozšíření, wraper phpunit MediaWiki automaticky objeví testy jednotek pomocí registrace rozšíření. Proto již nemusíte háček registrovat a nemusíte specifikovat, že vaše testy jednotek jsou uloženy ve výchozím adresáři. == Přizpůsobení registrace == :''See [[Manual:Extension.json/Schema#callback]].'' == Také composer.json == Pokud má rozšíření nebo vzhled knihovny závislosti, může je mít také soubor <code>composer.json</code>, viz {{ll|Manual:Composer.json best practices}}. Použijte pole <code>load_composer_autoloader</code>, aby MediaWiki používala automatické načítání Composer, když je to vhodné. Některá pole metadat se překrývají mezi <code>extension.json</code> a <code>composer.json</code> (diskutované v {{task|T89456}}), včetně: * <code>url</code> a <code>homepage</code> * <code>license-name</code> a <code>license</code> == Správce kódu == {{Component|mediawiki-configuration}} == Související stránky == * {{ll|Manual:Extension.json/Schema}} * Hlášení chyb v projektu [[phab:tag/mediawiki-configuration/|MediaWiki-Configuration]]. * Staré verze [[Special:MyLanguage/Manual:Developing extensions#Setup|Manual:Developing extensions#Setup]] (před květnem 2015) a {{wg|ExtensionCredits}} popisují starý přístup deklarování informací o rozšíření v kódu PHP a proměnných * {{ll|Manual:Extension registration/Limitations|2=Známá omezení}} * {{ll|Manual:Extension registration/Architecture|2=Přehled architektury}} * <code>[[phab:diffusion/MW/browse/master/docs/extension.schema.v2.json|docs/extension.schema.v2.json]]</code> je schéma pro <code>extension.json</code> (a skin.json). * [[Requests for comment/Extension registration|RfC]] o implementaci registrace rozšíření * [[toollabs:extreg-wos|Zeď superschopností pro registraci rozšíření!]] — přehled rozšíření, která je ještě třeba převést. * {{task|T98668}} — Sledovací karta pro převod všech rozšíření a vzhledů na Gitu pro použití registrace rozšíření. == Odkazy == {{reflist}} [[Category:Extension registration{{#translation:}}]] [[Category:Extension creation{{#translation:}}]] 7094a74e0yvvzyybyzbdke5wdpjm0gg Talk pages project/Usability/Prototype/Topic Containers/en 0 1516563 5387135 5180021 2022-07-28T20:45:50Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:Topic Container Screenshot.png|alt=Screenshot showing proposed design of a new way of displaying section headings on talk pages.|thumb|400px|This project will change the appearance of talk page section heading and introduce new information about the discussions that happen within them.]] <big>Welcome!</big> This page has instructions for testing a <strong>desktop prototype</strong> of a new part of the [[Special:MyLanguage/Talk pages project|Talk pages project]]. This new project changes the <code>==Section headings==</code> on talk pages. <strong>Goals:</strong> # <strong>People who are new to editing</strong> quickly recognize that talk pages are places to communicate with other volunteers. # <strong>People who are experienced with editing</strong> can quickly find the conversations they want to join. {{anchor|Try the prototype}} == Try the prototype == # Visit this <strong>test</strong> wiki: <strong><mark>[https://patchdemo.wmflabs.org/wikis/7eb90cd880/wiki/Talk:DiscussionTools]</mark></strong> # Log in to the wiki. You can use one of these accounts. The password for these accounts is <code>testsecret‎</code> #* <code>Alice</code> #* <code>Bob</code> #* <code>Carol</code> #* <code>Erin</code> # Visit this <mark><strong>[https://patchdemo.wmflabs.org/wikis/7eb90cd880/wiki/Talk:DiscussionTools article talk page]</strong></mark> or this <mark><strong>[https://patchdemo.wmflabs.org/wikis/7eb90cd880/wiki/User_talk:Bob user talk page]</strong></mark>. # Try to find the discussion that has been edited most recently. # Try to find the discussion that has the most people participating in it. # Try to find the discussion with the most comments. # Scroll back to the discussion you identified in "Step 4." and figure out how you would do the following: ## Subscribe to the discussion, so that you will be notified when new comments are posted in it. ## Post a reply in the discussion. ## Edit the reply you posted. # ✅ That is it! You are now ready to [[#Share your feedback|share your feedback]]. {{anchor|Share your feedback}} == Share your feedback == {| class="wikitable float{{dir|{{pagelang}}|left|right}}" |+ | style="background-color:#ffffee;" |If you prefer, you can send an e-mail message instead: talkpageconsultation{{@}}wikimedia.org |} After you complete the instructions listed in the [[#Try the prototype|Try the prototype]] section, please share your thoughts. # Go to [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype/Topic_Containers the talk page]. # Click the <code>Start a new topic</code> textbox. # Type <code>Feedback: YOUR USERNAME</code> # Write answers to these questions. <strong>You can write in your language.</strong> ## <em>What did you find unexpected about the prototype?</em> ## <em>Which – if any – of the steps in the "Try the Prototype" section were you uncertain about?</em> ## <em>What do you appreciate about the prototype?</em> ## <em>What do you wish was different about the prototype?</em> ## <em>OPTIONAL: Can you imagine this design <em>not</em> working on some pages? If you can, please share links to these pages. It would be very helpful.</em> # Click the blue "{{int|flow-newtopic-save}}" button. # ✅ You are done! kyuqkk0qakg9kgu2deq859awmqri5yo Translations:Reading/Web/Desktop Improvements/220/zh 1198 1516982 5387654 5115219 2022-07-29T04:23:10Z Chubit 17346826 wikitext text/x-wiki MediaWiki.org(本维基) lasz53v0k1d276y5ojz9mft3bt9a9jm Growth/FAQ/gu 0 1516994 5387835 5378639 2022-07-29T10:15:20Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Growth/Navbar}} '''<span lang="en" dir="ltr" class="mw-content-ltr">Welcome to the Growth team Frequently Asked Questions (FAQ).</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">We hope you will find the information you need. However, if it is not the case, [[Talk:Growth|let us know]].</span> ''<span lang="en" dir="ltr" class="mw-content-ltr">Note for translators: this page is updated regularly, which may impact your work. We are doing our best to avoid these disturbances.</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> == General == </div> {{Anchor|features}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Which features are you working on? === </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NH|'''Newcomer homepage''']]: a new special page, the best place for a newcomer to get started. It includes:</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#NT|'''Newcomer tasks''']]: a feed of task suggestions that help newcomers learn to edit. Newcomers have been making [[NEWTEA|productive edits]] through this feed! [[Help:Growth/Tools/Suggested edits|Know more about this tool]].</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Mentorship module''' [optional module]: each newcomers has a direct link to an experienced user. This way, they can ask questions about editing Wikipedia, less the need to find where to ask for assistance.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">'''Impact module''': the user sees how many pages views articles they edit received.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Special:MyLanguage/Growth/Feature summary#HP|'''Help panel''']]: a platform to provide resources to newcomers while they are editing. If they choose one of the suggested tasks on the newcomer homepage, they are guided step-by-step on the process of editing.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''[[Growth/Understanding first day|Welcome Survey]]''': communities can know why newcomers create an account on Wikipedia.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> You can have a look at '''[[Special:MyLanguage/Growth/Feature summary|our features summary]]''' to know more about it. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === On which wikis Growth features have been deployed? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find a list of wikis on our [[Special:MyLanguage/Growth/Deployment table|Deployment table]]. This page lists features activation per wiki as well. </div> {{anchor|NEWTEA}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Are Growth features effective? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[NEWTEA|The Growth team found evidence of the effectiveness of these new features]]. In short; Growth feature "newcomer tasks" leads to increases in: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that newcomers make their first article edit (+11.6%)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the probability that they are retained as editors</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the number of edits they make during their first couple of weeks on the wiki (+22%)</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also find that the quality of their edits is comparable to that of a control group. Based on this, we believe that all Wikipedias should consider deploying Growth features.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This deployment has been achieved in October 2021.</span> {{anchor|translate}} <div lang="en" dir="ltr" class="mw-content-ltr"> === The interface is partially translated. How can I change this? === </div> [https://translatewiki.net/w/i.php?title=Special:Translate&group=ext-growthexperiments&language=&filter=&action=translate <span lang="en" dir="ltr" class="mw-content-ltr">Interface translations are hosted at translatewiki.net.</span>] <div lang="en" dir="ltr" class="mw-content-ltr"> It takes up to one week to see new translations being deployed. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Special pages names require a special process. For the following strings, [[Talk:Growth|please contact us]] directly with the translations: <code>Special:WelcomeSurvey</code>, <code>Special:Homepage</code>, <code>Special:Impact</code>, <code>Special:ClaimMentee</code>. </div> {{anchor|enable|test}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I test the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[Growth/Deployment table|On wikis where the Growth features are available]], and also on [https://test.wikipedia.org test.wikipedia.org], go to your [[Special:Preferences#mw-prefsection-personal|user preferences]] on one of these wikis and then: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Help panel''' in the ''{{int|prefs-editing}}'' tab.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">enable the '''Newcomer homepage''' in the ''{{int|prefs-personal}}'' tab. Enabling the Newcomer homepage gives you access to '''Newcomer tasks'''.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Don't forget to enable ''both'' preferences options: Suggested edits you find on the Homepage need the Help panel to work.</span> {{anchor|get}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can my wiki get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Growth features are now available at all Wikipedias. But any wiki hosted by Wikimedia can request to have [[#features|these features]], with the following conditions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As detailed on [[Special:MyLanguage/Growth/Communities#Our%20focus|our focus]], we will work with the following wikis by order of priority: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias in the set of our '''[[#pilot|pilot wikis]]''' – we address all the feedback they give us.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedias – they get the features as they are, but we may consider suggestions of improvements from those wikis.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">All other Wikimedia projects – they get the features as they are, and the team will not have time to prioritize improvements specific to those wikis.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Do you plan to deploy the features outside of Wikipedia? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We welcome any Wikimedia community that wants to implement Growth features on their wiki. However, rather than simply deploying the features as they are, we want to provide a solution tailored to the wikis involved.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Please contact us [[Talk:Growth|on the team talk page]] to discuss how we can modify the tools to work for your Wikimedia project.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> We are considering working with [[Growth/Communities/Wikisource|Wikisource communities]]. </div> {{anchor|pilot|ambassador}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can you clarify what "Pilot wikis", "Control group wikis" and "Ambassadors" are? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''Pilot wikis''' are wikis who have a close collaboration with the Growth team. They are involved in projects definitions and early review of the projects. They also test all prototypes first. The Growth team can contact some other wikis for some of these steps. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, our pilot wikis are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have completed this list with a few wikis to have a more diverse and representative group to collect data: the '''control group wikis'''. This group is [[Special:MyLanguage/Growth/FAQ#ABtest|under an A/B test process]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As of {{ymd|2022|3|1}}, the control group is composed of the Pilot wikis listed above, plus the following wikis: {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order to have a better communication process with our pilot wikis, the Growth team employs part-time contractors, the '''Ambassadors'''. These ambassadors have been recruited from the community. Ambassadors can also contact "control group wikis" for a similar collaboration as "pilot wikis". </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Ambassadors ease the communication between the Growth team and their community. They help the Growth team to understand the diversity of our wikis, and they assist their communities in using the Growth tools and welcoming newcomers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I use the Growth features on mobile ? On the official apps (iOS, Android)? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Growth features are built to be used on both desktop and mobile version of Wikipedia. They aren't available on the official apps (iOS, Android). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Access to the features == </div> {{anchor|ABtest}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can new accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where no [[A/B testing|A/B test]] is active, 100% of new account get the features. This is the case for quite all Wikipedias. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], and where an [[A/B testing|A/B test]] is active, 80% of new accounts will get the features automatically; the remaining 20% will be part of a control group. This control group exists so that the Growth team can compare both experiences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Wikis concerned by this A/B test are: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-eswiki}}, {{int|project-localized-name-ptwiki}}, {{int|project-localized-name-fawiki}}, {{int|project-localized-name-trwiki}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How can existing accounts get the features? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On wikis [[Growth/Deployment table|where the Growth features have been deployed]], anyone can find the features [[#enable|in their Preferences]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === I host a workshop. How can I control if my students get the features when they create an account? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is possible to have a link parameter to control access to the features: </div> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=1</code> will force Growth features at account creation</span> * <span lang="en" dir="ltr" class="mw-content-ltr"><code>Special:CreateAccount?geEnabled=0</code> will force the default experience at account creation</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Of course, this parameter should have a very limited use. It would impact the data collected by Growth team around account creation and the usage of the features. [[Talk:Growth|Please let us know]] if you plan to use these parameters. </div> {{anchor|Homepage}} == મુખપૃષ્ઠ == ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Growth/Deployment table|where the Growth features have been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> === How to access the Homepage? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you recently created your account on Wikipedia, the homepage is accessible by clicking on your username, the link located at the top right of any page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you already have an account on Wikipedia, you need to enable the homepage in your preferences. When done, the homepage is accessible by clicking on your username, or on your talk page link. There, you will find a new tab that goes to your homepage. You also have an option in your preferences to go directly to your homepage when you click on your username. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My email is requested, or my email is displayed at the top of the Homepage. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that most people know how to use an email. As a consequence, we encourage users to add their email so that they can get [[Special:MyLanguage/Help:Notifications|notifications]], like when they are mentioned by other users on wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The email address won't be visible by other users. Communication with other users all happen on the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === The help links displayed on the homepage are not relevant. How to change them? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#HP|the same as on the Help panel]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Suggested edits == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How does Suggested Edits work ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How topics and tasks are suggested? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We suggest articles that are a combination of both the selected topics and the tasks you'd like to work on. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you only select task types, you get all articles that have the template corresponding to the task type. For instance, if you select no topic and "Copyedit" as a task, you will have up to 200 articles about copyediting, about any topic. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you select "Europe" as a topic and "Copyedit" as a task, you will have up to 200 articles about Europe that have a template about copyediting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Expand article" to the previous selection, you have articles that are about Europe, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you add "Asia" to the previous selection, you will have article either about Europe ''or'' Asia, and either about copyediting and expanding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === SuggestedEdits' supervision and troubleshooting === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can I monitor which articles have been edited as Suggested edits? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Articles edited as Suggested Edits are tagged as such in Recent Changes and Watchlist. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to monitor which topics or which tasks need more articles? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Please use <code>Special:NewcomerTasksInfo</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I don't have any task for a given combination. Is it normal? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some topics don't have a lot of articles. As a consequence, they have less articles being tagged with maintenance templates, leading to a limited choice. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== A user uses the tools in an nonconstructive way. What can I do? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Overall, users make [[#NEWTEA|more constructive edits]] using the Growth features. However, you can see a given user who doesn't follow the guidance, and uses the tools in an inappropriate manner. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The most appropriate way to handle these situation is to apply the usual process for nonconstructive behavior: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">try to understand what the use tries to do,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">contact this user, explain the situation, ask them for details and guide them to a different path if it exists,</span> # <span lang="en" dir="ltr" class="mw-content-ltr">if the nonconstructive behavior persists, then block the user.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If repetitive and similar nonconstructive edits are made at your wiki, [[Talk:Growth|please let us know]]. Add to your message some diffs as examples of nonconstructive edits so that the Growth team can analyse the situation and think about a solution. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== I enabled the Homepage in my user preferences. When I select an article to improve on the Homepage, I don't see any guidance on the article. ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you activated the Help panel in your preferences? If yes, [[Talk:Growth|please let us know about this issue]]. </div> {{anchor|config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Suggested edits configuration === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to provide more tasks for newcomers? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Newcomers are invited to work on 5 maintenance tasks, ranked by level of difficulty: </div> {| class="wikitable" !'''<span lang="en" dir="ltr" class="mw-content-ltr">Task</span>''' !<span lang="en" dir="ltr" class="mw-content-ltr">Level of difficulty</span> !<span lang="en" dir="ltr" class="mw-content-ltr">Goal of the task</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Copyedit article</span> |સહેલું |<span lang="en" dir="ltr" class="mw-content-ltr">fix spelling, grammar and tone</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add Links</span> |સહેલું |<span lang="en" dir="ltr" class="mw-content-ltr">add links between articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Update article</span> |મધ્યમ |<span lang="en" dir="ltr" class="mw-content-ltr">bring existing articles up-to-date</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Add References</span> |મધ્યમ |<span lang="en" dir="ltr" class="mw-content-ltr">find sources for existing articles</span> |- |<span lang="en" dir="ltr" class="mw-content-ltr">Expand article</span> |અઘરું |<span lang="en" dir="ltr" class="mw-content-ltr">expand stubs to become sourced articles</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> Tasks are listed based on maintenance templates. To increase the number of tasks being available, you can: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Add other templates that match the definition of the task to <code>Special:EditGrowthConfig</code> on your wiki</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Add maintenance templates to more articles on your wiki.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Sometimes, easy tasks are not available because experienced editors work on them. We advise experienced users to work on more difficult tasks instead, to let newcomers having a chance to make their first edits. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Can we suggest a new task type, or assign a different difficulty level to an existing task? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is not possible at the moment. [[Talk:Growth|Please let us know]] about your potential project. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add a link === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">The following items are only valid for the wikis [[Special:MyLanguage/Growth/Deployment table|where ''Structured tasks - Add a link'' has been deployed]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the difference between "add a link" and "Structured tasks - Add a link"? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">"Add a link" shows users an article where more internal links are needed. This "Add a link" is a task based on maintenance templates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers have to understand what to do, which can make things being complicated for them: what is a good link, where to link...? Even with some guidance being displayed on the Help panel, not all links were accurate, and, sometimes, some external links were added too.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, the Growth team works on improving this process, by reducing the number of difficulties people can face. We provide a better guidance and we suggest a set of links that could potentially be added. These links are shown on specific words in an article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users have to decide if a link should be added or not added. These links are suggested by a machine.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which wikis have Structured tasks - Add a link ? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can find the list in the [[Special:MyLanguage/Growth/Deployment table|deployment table]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the accuracy of Structured tasks - Add a link predictions? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The predictions are, on average, accurate at 70%. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some people asked us if it would be possible to have a better prediction. It would be possible, but it would diminish the interest of the task. We encourage newcomers to understand why a suggested link would be (or wouldn't be) interesting for readers, and to decide weather they should include it. Higher prediction rate would remove any interest for the task, since including links would be the default answer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Is there a limitation to the number of articles one can edit per day? ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">We received some feedback about some users making a lot of links additions, without much consideration to the quality of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we have setup some quality gates.</span> <span lang="en" dir="ltr" class="mw-content-ltr">As of January 2022, a user can edit up to 25 articles per day.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== There can be multiple added links in one edit, which does not make it easy to undo one wrong link. Is there a solution? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are aware of this problem, and we work on solutions to address it. In the meantime, you can use [[:m:Special:MyLanguage/User:Jon Harald Søby/diffedit|Diffedit]] to just edit this one wrong link. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Structured tasks - Add an image === </div> ''<span lang="en" dir="ltr" class="mw-content-ltr">This project is a work in progress, into development stages. You can know more about this project by visiting [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|its project page]].</span>'' <div lang="en" dir="ltr" class="mw-content-ltr"> ==== What is the purpose of "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on the same principle as "Suggested edits - Add a link", this project focuses on removing more barriers regarding images insertion. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which rules define the work done by "Structured tasks - Add an image"? ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We have several rules: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Images are chosen if they are used at other Wikipedias. For instance, if several articles in different languages, connected to the same Wikdata item, use the same image, then we suggest the image.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Only articles where no image is displayed are taken into consideration for images addition.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Articles with an infobox but no image aren't taken into consideration for now.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Which types of users have been contacted to test this new concept ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> During the design process, several types users have been involved. </div> * <span lang="en" dir="ltr" class="mw-content-ltr">During the definition process: Growth team members (which include several active wiki editors) and our [[#ambassadors|Ambassadors]] (at this time of the process: {{int|project-localized-name-arwiki}}, {{int|project-localized-name-bnwiki}}, {{int|project-localized-name-cswiki}}, {{int|project-localized-name-viwiki}}).</span> * <span lang="en" dir="ltr" class="mw-content-ltr">To test early prototypes, we focused on the two types of editors our features target.</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">people who aren't wiki editors (using UserTesting.com, in English and Spanish)</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">experienced users involved in newcomers' first steps, coming from [[#pilot|our pilot wikis]] so as people from Spanish Wikipedia.</span> {{anchor|HP}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Help panel == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We want to change some links displayed on the Help panel. How to do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change these links using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We can assist you in this task. [[Talk:Growth|Please contact us]] with your request; please provide a link to the community discussion that led to this change. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These links are [[#Homepage|also used on the Homepage]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where does questions posted using the Help panel goes? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, these questions go the the local Help desk. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If both a Help desk and a list of mentors exist, then it is up to the community to decide whether: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should go the newcomer's mentors,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">new messages should be posted at the help desk.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> An admin can change this configuration using <code>Special:EditGrowthConfig</code>. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Our community decided that all messages posted on the Help panel should go to the Help desk. It is not the case at some pages. Why? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">We have observed that newcomers sometimes try to contact their mentor leafing a message at their own talk page (user:New contacts User:Experienced by posting at User_talk:New).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As a consequence, we offer to contact the mentor when people use the Help panel on their own talk page.</span> {{anchor|mentoring}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration of the features == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We would like to change something on the configuration of the Growth features. How can we do it? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At your wiki, any admin can edit the configuration page (<code>Special:EditGrowthConfig</code>).</span> <span lang="en" dir="ltr" class="mw-content-ltr">Of course, be sure that the change is based on a community consensus.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[Talk:Growth|Please let us know]] if you have any question about the Growth features that you would like to change, or why you are changing the configuration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Sharing your feedback with us will help improve the Growth features.</span> {{anchor|add-link-config}} <div lang="en" dir="ltr" class="mw-content-ltr"> === I changed the configuration for "Add links between articles" in Special:EditGrowthConfig, but it isn't working. === </div> <span lang="en" dir="ltr" class="mw-content-ltr">Some of the configuration settings (such as the list of sections to exclude) are applied when a new suggestion is generated. They are then added to the Suggested Edits queue, and do not affect suggestions already in the queue.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Old suggestions remain in the queue until they are shown to a user. As the queue typically contains tens of thousands of items, it might take very long for all suggestions with the old configuration to be flushed out of the system. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a consequence, we encourage you to edit the list of excluded sections carefully, to add the maximum of needed sections to the list at once. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Phab:T313642|T313642]] for plans to improve this situation. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Configuration and operation of the mentoring system == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === My wiki doesn't have the Growth mentoring system. How can I set it up? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The next steps are a summary of the process. The full process is described on [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|this dedicated page]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> First, you need to check if the Growth tools are [[Growth/Deployment table|deployed at your wiki]]. If it is not yet the case, please see [[#get|how to get the features]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Then, you have to find some other mentors to volunteer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> All mentors have to sign-up on a specific page, using [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#create|a specific syntax]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> At your wiki, an admin has to add the mentor list to the configuration page (<code>Special:EditGrowthConfig</code>). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many mentors does a wiki need? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on our observation, we advise to have one mentor for each group of 500 new users your wiki gets per month. For instance, if your wiki has 2,500 new accounts per month, you should have at least 5 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We recommend to have at least 3 mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can be a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to each community to decide on criteria to become a mentor. We advise community members to keep the criteria simple and encouraging, so that more mentors would signup. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Most communities protect the signup page so that only people with a certain number of edits can signup as mentors. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits. We suggest to use the autopatrolled level (500 edits and 90 days of presence). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How mentors are assigned to newcomers? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Each new account receives a mentor randomly taken from a list of volunteers. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === How many messages does a mentor receive per week? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is difficult to know. It depends on how motivated newcomers are, and on the number of mentors for the wiki. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On average, we observe between 0 to 6 messages per week, with some fluctuations between weeks. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Have you considered to assign a mentor only to people who already made some edits? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We don't know what each newcomer needs. [[Special:MyLanguage/New Editor Experiences|Based on this research]], some new users need a confirmation of their right to edit before making their first edit. Some other editors may like to have more information about editing before starting editing. As a consequence, we provide a mentor to each new account. It is then up to the newcomer to contact their mentor. </div> {{anchor|existing}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Our wiki already has a mentoring project. Is the Growth mentoring system replacing it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We assume that your mentoring system is a list of experienced users who are available for motivated new users, who have specific questions about specific topics. Most are [[d:Q3919128|listed on Wikidata]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is up to your community to find the right way to integrate the Growth mentoring feature. Some options include: </div> '''<span lang="en" dir="ltr" class="mw-content-ltr">Replace your mentoring system with the new one</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">If your mentoring system hasn't much success, it could be replaced by the Growth team features.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">Have both systems working together</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">You can imagine to have two roles:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Growth mentoring takes care of the newcomers basic questions,</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The existing mentoring can take care of newcomers who are more involved.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> In this case, you might have to locally translate the interface for Growth features using your own terms. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Where can I signup as a mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your community has setup a mentorship program using the Growth features, the page for your wiki should be listed under [[D:Q14339834|this Wikidata item]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Your community may have defined some conditions to become a mentor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We advise communities to protect the list of mentors so that unexperienced users would signup as mentors after a couple of edits.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We suggest to use the autopatrolled level (500 edits and 90 days of presence).</span> {{anchor|mentorsyntax}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How do I introduce myself as a mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you sign up to become a mentor, the following syntax must be used, with: </div> <code>* <nowiki>[[</nowiki><span lang="en" dir="ltr" class="mw-content-ltr">User:Username</span><nowiki>]]</nowiki>|<span lang="en" dir="ltr" class="mw-content-ltr">Description</span></code> [[Special:MyLanguage/Growth/Communities/How to configure the mentors' list#presentation|<span lang="en" dir="ltr" class="mw-content-ltr">Read more about this</span>]] {{anchor|reassign}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Can we reassign a newcomer to a different mentor? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Yes, it is possible using <code>Special:ClaimMentee</code>. </div> {{anchor|pause}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I have to pause my mentorship activity. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to [[Special:MyLanguage/Growth/Mentor dashboard|<code>Special:MentorDashboard</code>]] and pause your activity. </div> {{anchor|quit}} <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, I would like to quit mentorship. How can I do it? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to <code>Special:QuitMentorship</code> and quit from there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This link is accessible from your [[Special:MyLanguage/Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === A mentor just quit. Can we reassign all their newcomer to different mentors? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can use <code>Special:ClaimMentee</code> to claim active mentees, but if you want to reassign all newcomers assigned to this mentor, [[Talk:Growth|please contact us]] directly. </div> {{anchor|magicword}} <div lang="en" dir="ltr" class="mw-content-ltr"> === How can I display the mentor of a given user? / How to add the mentor name to our welcome message? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Type the magic word <code><nowiki>{{#mentor:Foo}}</nowiki></code> in a wikitext page, and preview. "Foo" has to be replaced by the username you target. This will display the name of Foo's mentor. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This magic word can be used in a template: welcome message, user talk page messages, userbox, etc. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> [[#reassign|If the mentor changes]], then the magic word picks the new mentor's name. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can "[[Special:MyLanguage/Help:Substitution|subst:]]" this message if needed: <code><nowiki>{{subst:#mentor:Foo}}</nowiki></code>. Foo's mentor will then be saved as wikitext. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === We renamed our mentors list and now we get no questions from newcomers. How to fix this? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Have you updated <code>Special:EditGrowthConfig</code> with the new page name? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Interactions between mentors and newcomers == </div> {{Anchor|questions}} <div lang="en" dir="ltr" class="mw-content-ltr"> === What kinds of questions do newcomers ask? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> From the observations we have made, questions are mostly about basic editing. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Some questions are social interactions ("hello"), coming from users who try the tools to check if someone would respond. We encourage you to respond to these greetings, since they can be the beginning of some interactions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Based on communities experiences, the Growth team worked [[Special:MyLanguage/Growth/Communities/How to interact with newcomers|on a guide for mentors]] who have to reply to these questions. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Newcomers haven't replied to my messages. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Two possible cases there: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Have you mentioned the user when responding? Newcomers don't know how to use the watchlist or other tools to monitor changes. The Homepage shows a way to come back to the mentor's talk page but mentioning them is most sucessful. A ping will action a notification, which is the most successful way to let newcomers know that they have an reply to their messages.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Newcomers don't come daily on the wikis. Some of them will respond after a few days, some others after a few weeks. Mentors, please consider this when you archive your user talk page.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === Who can I ask if my mentor is not responding to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If your mentor is not available you can ask your question to the local help desk, or to any other experienced user. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I ask to have a different mentor ? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can contact another mentor and ask them to become your mentor. If they agree, the mentor will [[#reassign|make the change]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === As a mentor, how can I monitor the newcomers assigned to me? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We are currently working on a [[Growth/Mentor dashboard|Mentor dashboard]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It is available at all Wikipedias where [[special:MyLanguage/Growth/Communities/How_to_configure_the_mentors%27_list#create|a list of mentors has been created and activated]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Can I filter my mentees' activity in RecentChanges, or in my Watchlist? === </div> <span lang="en" dir="ltr" class="mw-content-ltr">At wikis where the mentor dashboard is deployed, a new filter is available for mentors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">They can monitor their mentees' activity in Watchlist and RecentChanges.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|not listed as mentors]].</span> <div lang="en" dir="ltr" class="mw-content-ltr"> === A very experienced user is one of my mentees. Why? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For technical reasons, we assign a mentor to everyone, including experienced users. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Are all my mentees assigned to me being visible in my list of mentees? === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Your list will only display users who have turned the Homepage on. </div> ncmevyn476ue3noot892edjas2ulc8o Talk pages project/Usability/Prototype/Topic Containers/ar 0 1517439 5387134 5181160 2022-07-28T20:45:49Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:DiscussionTools topic containers March 2022-ar.png|alt=لقطة من الشاشة تبيّن التصميم المقترح لطريقة جديدة لعرض عناوين الأقسام على صفحات النقاش.|thumb|400px|سوف يغيّر المشروع من مظهر عناوين أقسام صفحات النقاش ويضيف كذلك معلومات جديدة عن النقاش الدائر في تلك الأقسام.]] <big>مرحبا!</big> تحتوي هذه الصفحة على تعليمات عن تجريب <strong>نموذج أولي للأجهزة المكتبية</strong> لجزء جديد من [[Special:MyLanguage/Talk pages project|مشروع صفحات النقاش]]. يغيّر هذا المشروع من <code>==عناوين الفقرات==</code> الموجودة في صفحات النقاش. <strong>الأهداف:</strong> # يتيسر على <strong>الأفراد الوافدين الجدد في جهود التعديل</strong> استيعاب أن صفحات النقاش هي مساحات للتواصل مع متطوعين آخرين. # يتيسر على <strong>الأفراد المتمرسين في مجال التعديل</strong> البحث عن النقاش الذي يرغبون في المشاركة فيه. {{anchor|Try the prototype}} == جرّب النموذج الأولي == # زر موقع ويكي <strong>الاختبار</strong> هذا: <strong><mark>[https://patchdemo.wmflabs.org/wikis/a3bfaaaf94/wiki/%D9%86%D9%82%D8%A7%D8%B4:%D8%A7%D9%84%D8%B5%D9%81%D8%AD%D8%A9_%D8%A7%D9%84%D8%B1%D8%A6%D9%8A%D8%B3%D9%8A%D8%A9?uselang=ar]</mark></strong> # تسجيل الدخول إلى الويكي. يمكنكم استخدام أحد هذه الحسابات. كلمة السر هي <code>سر‎</code> #* <code>خالد</code> #* <code>إلياس</code> #* <code>فاطمة</code> #* <code>رانيا</code> # اذهب إلى <mark><strong>[https://patchdemo.wmflabs.org/wikis/a3bfaaaf94/wiki/%D9%86%D9%82%D8%A7%D8%B4:%D9%86%D9%8A%D9%88%D9%8A%D9%88%D8%B1%D9%83 صفحة نقاش المقالة]</strong></mark> هذه أو <mark><strong>[https://patchdemo.wmflabs.org/wikis/a3bfaaaf94/wiki/%D9%86%D9%82%D8%A7%D8%B4_%D8%A7%D9%84%D9%85%D8%B3%D8%AA%D8%AE%D8%AF%D9%85%D8%A9:%D8%B1%D8%A7%D9%86%D9%8A%D8%A7 صفحة نقاش المستخدم]</strong></mark> هذه. # ابحث عن النقاش الذي جرى عليه أحدث تعديل مؤخرًا. # ابحث عن النقاش الذي شارك فيه أكبر عدد من الأفراد. # ابحث عن النقاش الذي يحتوي على أكبر عدد من التعليقات. # عد إلى النقاش الذي حددته في «الخطوة الرابعة» واستكشف كيف يمكنك عمل ما يلي: ## الاشتراك في النقاش، حتى يصل إليك إشعار بالتعليقات الجديدة حينما تنشر فيه. ## نشر رد على النقاش. ## تعديل الرد الذي نشرته. # ✅ هذا كل شيء! أنت جاهز الآن [[#Share your feedback|لمشاركة رأيك وملاحظاتك]]. {{anchor|Share your feedback}} == شارك آراءك وملاحظاتك == {| class="wikitable float{{dir|{{pagelang}}|left|right}}" |+ | style="background-color:#ffffee;" |يمكنك أن ترسل رسالة بريد إلكتروني بدلًا من ذلك، إن كان هذا ما تفضله: talkpageconsultation{{@}}wikimedia.org |} بعد الانتهاء من التعليمات المبينة في قسم [[#Try the prototype|جرّب النموذج الأولي]]، يرجى مشاركة رأيك. # عد إلى [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype/Topic_Containers صفحة النقاش]. # اضغط على مربع النص <code>بدء موضوع جديد</code>. # اكتب <code>آراء وملاحظات: اسم مستخدمك</code> # اكتب الإجابات عن هذه الأسئلة. يمكنك كتابة آرائك وملاحظاتك <strong>بلغتك أنت</strong>. ## <em>ما الذي وجدته غير متوقع في النموذج الأولي؟</em> ## <em>ما هي الخطوات المذكورة في قسم «جرّب النموذج الأولي» التي لم تكن متيقنًا من مقصدها؟</em> ## <em>ما الذي تعتبره مفيدًا في النموذج الأولي؟</em> ## <em>ما الذي ترغب في أن يكون مختلفًا في النموذج الأولي؟</em> ## <em>اختياري: هل تظن أن هذا التصميم <em>لا</em> يعمل على بعض الصفحات؟ لو ظننت ذلك، يرجى مشاركة روابط إلى هذه الصفحات. سيكون هذا الأمر مفيدًا.</em> # اضغط على زرّ «{{int|flow-newtopic-save}}» الأزرق. # ✅ انتهى الأمر! pvp7enz1vbo52bcu0d4rf19r3opfc5t Translations:Reading/Web/Desktop Improvements/Updates/197/es 1198 1526033 5387705 5142273 2022-07-29T06:08:31Z Zapipedia (WMF) 17560702 wikitext text/x-wiki ==== $1: Feedback de las herramientas de la Página ==== s7aegokym616wehk8zwb1wqjgwk4hlv Translations:Reading/Web/Desktop Improvements/220/es 1198 1530031 5387377 5156842 2022-07-28T22:12:48Z Zapipedia (WMF) 17560702 wikitext text/x-wiki MediaWiki.org (esta wiki) qioihzm7vrplde3mks6pqztoyalg4ll Wikimedia Product/th 0 1533883 5387596 5358215 2022-07-29T03:26:04Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> {{Tech header|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Wikimedia Product''' staff [[foundationsite:role/staff-contractors/|employed by the Wikimedia Foundation]] build, improve and maintain the features of [[m:Special:MyLanguage/Wikimedia projects|Wikimedia sites]].</span>{{flatlist|class=center |style=margin:1em; font-weight: bold| * [[Contributors|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span></span>]] * [[Readers|<span style="color:#2aa198"><span lang="en" dir="ltr" class="mw-content-ltr">Readers</span></span>]] }}}} {{TOC {{dir|ltr=right|rtl=left}}}} == <span lang="en" dir="ltr" class="mw-content-ltr">Across Product</span> == * [[Special:MyLanguage/Product Principles|<span lang="en" dir="ltr" class="mw-content-ltr">Product Principles</span>]] * [[Special:MyLanguage/Wikimedia Product Guidance]] (<span lang="en" dir="ltr" class="mw-content-ltr">formerly:</span> [[Special:MyLanguage/Technical Collaboration Guidance|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Collaboration Guidance</span>]]) * [[Special:MyLanguage/Design/Statement of purpose|<span lang="en" dir="ltr" class="mw-content-ltr">Design Statement of Purpose</span>]] * [[m:Special:MyLanguage/Research:FAQ#Where do I find data or statistics about a specific Product Audience?|<span lang="en" dir="ltr" class="mw-content-ltr">Data and research information for products</span>]] * [[Special:MyLanguage/Wikimedia Research/Showcase|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly Research Showcases</span>]] === โปรแกรม === * [[m:Special:MyLanguage/Communications/Audience research|<span lang="en" dir="ltr" class="mw-content-ltr">Audience Research</span>]] * [[m:Special:MyLanguage/Community health initiative|<span lang="en" dir="ltr" class="mw-content-ltr">Community Health Initiative</span>]] (2017–2019; superseded by [[m:Special:MyLanguage/Anti Harassment Program|Anti Harassment Program]]) * [[Special:MyLanguage/New Editor Experiences|<span lang="en" dir="ltr" class="mw-content-ltr">New Editor Experiences</span>]] (2017–2018) * [[m:Special:MyLanguage/New Readers|<span lang="en" dir="ltr" class="mw-content-ltr">New Readers</span>]] — <span lang="en" dir="ltr" class="mw-content-ltr">on-going research that focuses on understanding potential Wikimedia readers in countries where access to the Internet is quickly growing.</span> (2016–2019) * [[c:Special:MyLanguage/Commons:Structured data/Sloan Grant|<span lang="en" dir="ltr" class="mw-content-ltr">Structured Data on Commons</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Project Pages</span> === Projects in 2018–2019. '''[[metawiki:Wikimedia Foundation Annual Plan/2018-2019/Audiences#New Content|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: New Content</span>]]''' * [[Special:MyLanguage/Reading/Web/Advanced mobile contributions|<span lang="en" dir="ltr" class="mw-content-ltr">Advanced Mobile Contributions</span>]] * [[Special:MyLanguage/Android editing features|<span lang="en" dir="ltr" class="mw-content-ltr">Android Editing Features</span>]] * [[Special:MyLanguage/Content translation/V2|<span lang="en" dir="ltr" class="mw-content-ltr">Content Translation, V2</span>]] * [[Special:MyLanguage/Growth/Growth team updates|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] * [[Special:MyLanguage/Language tools|<span lang="en" dir="ltr" class="mw-content-ltr">Improve Translate Extension and Translate Wiki process</span>]] * [[Special:MyLanguage/Wikimedia Apps/Team/iOS/Editing program|<span lang="en" dir="ltr" class="mw-content-ltr">iOS Editing</span>]] * [[Special:MyLanguage/VisualEditor on mobile|<span lang="en" dir="ltr" class="mw-content-ltr">Visual based mobile editing</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Better Use of Data|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Better Use of Data</span>''']] * [[Special:MyLanguage/Wikimedia Product/Better use of data|<span lang="en" dir="ltr" class="mw-content-ltr">Better use of Data</span>]] * [[Special:MyLanguage/Wikimedia Reading Infrastructure team/Data collection, Instrumentation|<span lang="en" dir="ltr" class="mw-content-ltr">Data collection: Instrumentation</span>]] * [[Special:MyLanguage/Wikimedia Product/Report stewardship|<span lang="en" dir="ltr" class="mw-content-ltr">Report stewardship</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Community Wishlist|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Community Wishlist</span>''']] * [[m:Special:MyLanguage/Community Tech#Projects|<span lang="en" dir="ltr" class="mw-content-ltr">Wishlist</span>]] * [[m:Special:MyLanguage/Community Tech/Grant metrics_tool|<span lang="en" dir="ltr" class="mw-content-ltr">Support for smaller user groups</span>]] * [[m:Special:MyLanguage/Community Tech/Tools for program and event organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Tech tools for program and event organizers</span>]] [[m:Special:MyLanguage/Community health initiative/Annual plan FY18-19|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Anti-Harassment Tools</span>''']] * [[m:Special:MyLanguage/Community health initiative/Improved tools and workflows to report harassment|<span lang="en" dir="ltr" class="mw-content-ltr">Reporting system</span>]] [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences#Wikidata|'''<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan goal: Wikidata</span>''']] '''อื่น ๆ:''' * [https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19 <span lang="en" dir="ltr" class="mw-content-ltr">Annual Pan goal: Platform Evolution CDP</span>] ** [[Special:MyLanguage/Reading/Web/Projects/Invest in the MobileFrontend & MinervaNeue frontend architecture|<span lang="en" dir="ltr" class="mw-content-ltr">Invest in the MobileFrontend & MinervaNeue frontend architecture</span>]] ** [[Special:MyLanguage/Parsing/Parser Unification|<span lang="en" dir="ltr" class="mw-content-ltr">Parser unification</span>]] * [[Special:MyLanguage/Wikimedia Product/TemplateStyles|<span lang="en" dir="ltr" class="mw-content-ltr">TemplateStyles</span>]] * [[m:Special:MyLanguage/Movement Organizers|<span lang="en" dir="ltr" class="mw-content-ltr">Movement Organizers Study</span>]] (2019) <div lang="en" dir="ltr" class="mw-content-ltr"> == Metrics == </div> <span lang="en" dir="ltr" class="mw-content-ltr">The [[Special:MyLanguage/Product Analytics|Product Analytics]] tracks a set of key metrics designed to give a high-level picture of the movement's health.</span> [[File:June 2022 Wikimedia movement metrics.pdf|alt=|none|thumb|850x850px|<span lang="en" dir="ltr" class="mw-content-ltr">The monthly report on key metrics tracking the overall health of the Wikimedia movement.</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Product teams</span> == <span lang="en" dir="ltr" class="mw-content-ltr">A Product team covers a set of features developed according to specific user flows and needs.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build collaborative, inclusive tools for creating and editing free knowledge.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:tag/contributors-team/|#Contributors-Team]] <span lang="en" dir="ltr" class="mw-content-ltr">(rarely used)</span> * หน้า: [[Special:MyLanguage/Contributors|<span lang="en" dir="ltr" class="mw-content-ltr">Contributors</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== <span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/project/view/3757/ #Anti-Harassment (AHT Sprint 35)] * หน้า: [[Special:MyLanguage/Anti-Harassment Tools|<span lang="en" dir="ltr" class="mw-content-ltr">Anti-Harassment Tools</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span> ====== * [[phab:project/board/1274/|<span lang="en" dir="ltr" class="mw-content-ltr">Phabricator board</span>]] * หน้า: [[m:Special:MyLanguage/Community Tech|<span lang="en" dir="ltr" class="mw-content-ltr">Community Tech</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Editing</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task boards:</span> [[phab:project/view/4864/|#FY2021-22 Kanban Board]] [https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-wplwgfnusdjw2d4btgx6&statuses=open()&group=none&order=newest#R #Editing-team] * หน้า: [[Special:MyLanguage/Editing team|<span lang="en" dir="ltr" class="mw-content-ltr">Editing team</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Growth</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:project/board/1114/|#Growth-Team]] * หน้า: [[Special:MyLanguage/Growth|<span lang="en" dir="ltr" class="mw-content-ltr">Growth</span>]] ====== <span lang="en" dir="ltr" class="mw-content-ltr">Language</span> ====== * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [[phab:tag/contenttranslation-release8/|#ContentTranslation-Release8]] * หน้า: [[Special:MyLanguage/Wikimedia Language engineering|<span lang="en" dir="ltr" class="mw-content-ltr">Wikimedia Language engineering</span>]] === <span lang="en" dir="ltr" class="mw-content-ltr">Readers</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We build exceptional learning and reading experiences for the sum of all knowledge.</span> * หน้า: [[Special:MyLanguage/Readers|<span lang="en" dir="ltr" class="mw-content-ltr">Readers</span>]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator task board:</span> [https://phabricator.wikimedia.org/tag/reading/ #reading] * <span lang="en" dir="ltr" class="mw-content-ltr">Teams:</span> ====== [[Special:MyLanguage/Wikimedia Apps/Team/Android|<span lang="en" dir="ltr" class="mw-content-ltr">Android</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Apps/Team/iOS|<span lang="en" dir="ltr" class="mw-content-ltr">iOS</span>]] ====== ====== [[Special:MyLanguage/Parsing|<span lang="en" dir="ltr" class="mw-content-ltr">Parsing</span>]] ====== ====== [[Special:MyLanguage/Wikimedia Reading Infrastructure team|<span lang="en" dir="ltr" class="mw-content-ltr">Product Infrastructure</span>]] ====== ====== [[Special:MyLanguage/Reading/Web/Team|<span lang="en" dir="ltr" class="mw-content-ltr">Web</span>]] ====== * [[Reading/Component responsibility|<span lang="en" dir="ltr" class="mw-content-ltr">Reading code responsibility</span>]] <gallery widths="440" heights="250"> File:Wikimedia monthly pageviews (desktop+mobile), 2013-.png|<span lang="en" dir="ltr" class="mw-content-ltr">Monthly page views, May 2013–January 2019.</span> File:Wikimedia pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Total page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia desktop pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Desktop page views in year-over-year comparison, May 2013–February 2019.</span> File:Wikimedia mobile pageviews year-over-year comparison (since May 2013).png|<span lang="en" dir="ltr" class="mw-content-ltr">Mobile page views in year-over-year comparison, May 2013–February 2019.</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We are dedicated to guiding delivery processes and facilitating team health through good practices.</span> หน้า: [[Special:MyLanguage/Wikimedia Product/Technical Program Management|<span lang="en" dir="ltr" class="mw-content-ltr">Technical Program Management</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[m:User:Ggellerman (WMF)|Grace Gellerman]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make sharing of all human knowledge easy and joyful. For everyone.</span> หน้า: [[Special:MyLanguage/Design#Product Design|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Director:</span> [[User:MNovotny_(WMF)|Margeigh Novotny]] === <span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">We make recommendations based on results of analyses, advocate for ethical data practices, and educate on topics around data and statistics.</span> หน้า: [[Special:MyLanguage/Product Analytics|<span lang="en" dir="ltr" class="mw-content-ltr">Product Analytics</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Kate Zimmerman === <span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span> === <!--<span lang="en" dir="ltr" class="mw-content-ltr">''[intro text here]''</span>--> หน้า: [[Special:MyLanguage/Design#Design Strategy|<span lang="en" dir="ltr" class="mw-content-ltr">Product Design Strategy</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> Margeigh Novotny === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata is a free and open knowledge base that can be read and edited by both humans and machines. This project is maintained by the Software Development & Engineering department at [[WMDE Engineering|Wikimedia Deutschland]].</span> * หน้า: [[d:Wikidata:Main Page|Wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Lead:</span> [[User:Lydia Pintscher (WMDE)|Lydia Pintscher]] * <span lang="en" dir="ltr" class="mw-content-ltr">Phabricator bugs & tasks board:</span> [[phab:project/profile/71/|#wikidata]] * <span lang="en" dir="ltr" class="mw-content-ltr">Discussion List:</span> wikidata@lists.wikimedia.org {|class="wikitable" |+ <span lang="en" dir="ltr" class="mw-content-ltr">Wikidata Team Goals</span> |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2017</span> | [https://docs.google.com/presentation/d/1R0IjxAYNfIxS0jgkQHeDg3J6K7uDDTQ18rhaYPjZ7H0/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2017</span>] | [https://docs.google.com/presentation/d/1gSRPhfjC7M6MkS6W-IFC9jF8bSLuYNsjNeTpyZmH358/edit#slide=id.g1651e065b0_0_206 <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [//upload.wikimedia.org/wikipedia/commons/0/0f/Audiences_2_check-in_Q1_October_2017.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [//upload.wikimedia.org/wikipedia/commons/8/8a/CommTech_QCI_Q2_Jan_2018.pdf <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |- !scope="row"| <span lang="en" dir="ltr" class="mw-content-ltr">WMDE Fiscal Year 2016</span> | [https://docs.google.com/presentation/d/1-9KhRNI1N2EQQE-inFROhkP9VcY4F6bvL61c8pYcOgQ/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q1: January–March 2016</span>] | [https://docs.google.com/presentation/d/12__eFDAd0LFGLaNlDzXR7KzQiUip5aUJELnP2Rwv0c4/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q2: April–June</span>] | [https://docs.google.com/presentation/d/10WT6D3hqgiRmFYzN2W-5JBcjs3e9SmzMMqDKwYhoicE/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q3: July–September</span>] | [https://docs.google.com/presentation/d/1mJ7AwQq3TJNJ2LhbYCMWjNr97qqK7yxURQfakvloRT8/edit#slide=id.p <span lang="en" dir="ltr" class="mw-content-ltr">Q4: October–December</span>] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Goals</span> == {|class="wikitable" |- !scope="row"| 2019–2020 | [[Special:MyLanguage/Wikimedia Product/2019-20 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2019-20 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2019</span>]] | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2020</span>]]--> | <!--[[Special:MyLanguage/Wikimedia Product/2019-20 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2020</span>]]--> |- !scope="row"| 2018–2019 | [[Special:MyLanguage/Wikimedia Product/2018-19 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2019</span>]] | [[Special:MyLanguage/Wikimedia Product/2018-19 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2019</span>]] |- !scope="row"| 2017–2018 | [[Special:MyLanguage/Wikimedia Product/2017-18 Q1 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q1: July–September 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q2 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q2: October–December 2017</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q3 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q3: January–March 2018</span>]] | [[Special:MyLanguage/Wikimedia Product/2017-18 Q4 Goals|<span lang="en" dir="ltr" class="mw-content-ltr">Q4: April–June 2018</span>]] |- !scope="row"| 2016–2017 | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q1 Goals|Q1: กรกฏาคม–กันยายน 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q2 Goals|Q2: ตุลาคม–ธันวาคม 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q3 Goals|Q3: มกราคม–มีนาคม 2017]] | [[Special:MyLanguage/Wikimedia Engineering/2016-17 Q4 Goals|Q4: เมษายน–มิถุนายน 2017]] |- !scope="row"| 2015–2016 | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q1 Goals|Q1: กรกฏาคม–กันยายน 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q2 Goals|Q2: ตุลาคม–ธันวาคม 2015]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q3 Goals|Q3: มกราคม–มีนาคม 2016]] | [[Special:MyLanguage/Wikimedia Engineering/2015-16 Q4 Goals|Q4: เมษายน–มิถุนายน 2016]] |} == <span lang="en" dir="ltr" class="mw-content-ltr">Annual Roadmap</span> == * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2018-2019/Audiences|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2018–2019</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2017-2018/Final/Programs/Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2017–2018</span>]] * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2016-2017/Final#Product|<span lang="en" dir="ltr" class="mw-content-ltr">Annual Plan for Product 2016–2017</span>]] * [[Special:MyLanguage/Wikimedia Product/2016 Product Summary|<span lang="en" dir="ltr" class="mw-content-ltr">2016 Product Summary</span>]] * [[m:Special:MyLanguage/2015 Wikimedia Foundation Product and Technology Highlights|<span lang="en" dir="ltr" class="mw-content-ltr">2015 Product & Technology Review</span>]] [[Category:WMF Projects{{#translation:}}]] 8egtn6lupv02fy2ezmd2jayhxorsnav Talk pages project/Usability/Prototype 0 1535613 5387137 5370896 2022-07-28T21:03:59Z Whatamidoing (WMF) 927293 Change link wikitext text/x-wiki <languages /> [[<translate nowrap><!--T:35--> File:Usability_Improvement_annotated_mockup_(desktop).jpg</translate>|alt=<translate><!--T:36--> A mockup showing the proposed new design for desktop wikitext talk pages.</translate>|center|thumb|600x600px|<translate><!--T:37--> Mockup of new design for '''desktop''' wikitext talk pages.</translate>]] <big><translate><!--T:1--> Welcome!</translate></big> <translate><!--T:2--> This page has instructions for testing design changes to wikitext talk pages.</translate> <translate><!--T:63--> These design changes are a part of the <tvar name=1>{{ll|Talk pages project}}</tvar> and an effort to make talk pages easier for people to recognize and use.</translate> <translate> == Try the prototype == <!--T:4--> </translate> # <translate><!--T:7--> Visit this {{<tvar name=1>tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:New_York $1]</mark></tvar>|article talk page}} or this {{<tvar name=2>tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Bob $1]</mark></tvar>|user talk page}} on the special prototype wiki.</translate> # <translate><!--T:8--> Find the discussion that has been edited most recently.</translate> # <translate><!--T:9--> Find the discussion that has the most people participating in it.</translate> # <translate><!--T:10--> Find the discussion with the most comments.</translate> # <translate><!--T:11--> Scroll back to the discussion you identified in "Step 4." Figure out how you would do the following:</translate> ## <translate><!--T:12--> Post a reply in the discussion.</translate> ## <translate><!--T:13--> Edit the reply you posted.</translate> # <translate><!--T:14--> Next, start a discussion about a new topic.</translate> # ✅ <translate><!--T:15--> You are now ready to share your feedback.</translate> == <translate><!--T:38--> Design</translate> == <gallery mode="slideshow" showthumbnails> <translate nowrap><!--T:39--> File:Usability Improvement mockup (mobile).jpg</translate>|alt=<translate><!--T:40--> Mockup showing the proposed design for mobile wikitext talk pages</translate>|<translate><!--T:41--> Mockup of proposed '''mobile''' wikitext talk page design</translate> <translate nowrap><!--T:42--> File:Usability Improvement annotated mockup (mobile overview).jpg</translate>|alt=<translate><!--T:43--> Mockup showing the proposed design for the mobile wikitext talk pages landing page view</translate>|<translate><!--T:44--> Annotated mockup of proposed '''mobile''' wikitext talk page design</translate> <translate nowrap><!--T:45--> File:Usability Improvement annotated mockup (mobile discussion).jpg</translate>|alt=<translate><!--T:46--> Annotated mockup showing the proposed design for the mobile wikitext talk pages individual discussion view</translate>|<translate><!--T:47--> Annotated mockup of proposed '''mobile''' wikitext talk page design</translate> <translate nowrap><!--T:48--> File:Usability Improvement mockup (desktop).jpg</translate>|alt=<translate><!--T:49--> Mockup showing the proposed design for desktop wikitext talk pages</translate>|<translate><!--T:50--> Mockup of proposed design for '''desktop''' wikitext talk pages</translate> <translate nowrap><!--T:51--> File:Usability Improvement annotated mockup (desktop).jpg</translate>|alt=<translate><!--T:52--> Annotated mockup showing the proposed design for desktop wikitext talk pages</translate>|<translate><!--T:53--> Annotated mockup of proposed design for '''desktop''' wikitext talk pages</translate> <translate nowrap><!--T:54--> File:DiscussionTools Usability topic container screenshot en 2022-04-29.png</translate>|alt=<translate><!--T:55--> Detail of change</translate>|<translate><!--T:56--> Proposed change to the top of discussion sections</translate> <translate nowrap><!--T:57--> File:DiscussionTools Usability page frame screenshot en 2022-04-29.png</translate>|alt=<translate><!--T:58--> Detail of change</translate>|<translate><!--T:59--> Proposed change to the top of talk pages</translate> <translate nowrap><!--T:60--> File:DiscussionTools Usability Table of Contents screenshot en 2022-04-29.png</translate>|alt=<translate><!--T:61--> Detail of change</translate>|<translate><!--T:62--> Proposed change to Table of Contents ('''[[Vector 2022]] only''')</translate> </gallery> <translate> == Share your feedback == <!--T:16--> </translate> {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |<translate><!--T:17--> If you prefer, you can send an e-mail message instead: </translate> talkpageconsultation{{@}}wikimedia.org |} <translate><!--T:18--> Please share your thoughts.</translate> # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:<translate nowrap><!--T:34--> YOUR USERNAME</translate>}} <translate><!--T:19--> Click here to start a new topic on the talk page.</translate>] # <translate><!--T:20--> Type <code>Feedback: YOUR USERNAME</code></translate>. # <translate><!--T:21--> Write answers to these questions.</translate> <strong><translate><!--T:22--> You can write in your language.</translate></strong> ## <translate><!--T:23--> Did you use mobile device or a laptop to test the prototype?</translate> ## <translate><!--T:24--> What did you find unexpected about the prototype?</translate> ## <translate><!--T:25--> Which steps in the "Try the Prototype" section did you find difficult to complete?</translate> ## <translate><!--T:26--> What do you like about the prototype?</translate> ## <translate><!--T:27--> What do you wish was different about the prototype?</translate> ## <translate><!--T:28--> (Optional) Can you imagine this design not working on some pages? If you can, please share links to these pages? It would be very helpful.</translate> # <translate><!--T:29--> Click the blue "<tvar name=button>{{int|discussiontools-replywidget-newtopic}}</tvar>" button.</translate> # ✅ <translate><!--T:30--> You are done! Thank you!</translate> 73xm4c1pe4vv3w0wt9e6edakaxvcde2 Talk pages project/Usability/Prototype/en 0 1535645 5387256 5370937 2022-07-28T21:38:03Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:Usability_Improvement_annotated_mockup_(desktop).jpg|alt=A mockup showing the proposed new design for desktop wikitext talk pages.|center|thumb|600x600px|Mockup of new design for '''desktop''' wikitext talk pages.]] <big>Welcome!</big> This page has instructions for testing design changes to wikitext talk pages. These design changes are a part of the {{ll|Talk pages project}} and an effort to make talk pages easier for people to recognize and use. == Try the prototype == # Visit this {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:New_York $1]</mark>|article talk page}} or this {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Bob $1]</mark>|user talk page}} on the special prototype wiki. # Find the discussion that has been edited most recently. # Find the discussion that has the most people participating in it. # Find the discussion with the most comments. # Scroll back to the discussion you identified in "Step 4." Figure out how you would do the following: ## Post a reply in the discussion. ## Edit the reply you posted. # Next, start a discussion about a new topic. # ✅ You are now ready to share your feedback. == Design == <gallery mode="slideshow" showthumbnails> File:Usability Improvement mockup (mobile).jpg|alt=Mockup showing the proposed design for mobile wikitext talk pages|Mockup of proposed '''mobile''' wikitext talk page design File:Usability Improvement annotated mockup (mobile overview).jpg|alt=Mockup showing the proposed design for the mobile wikitext talk pages landing page view|Annotated mockup of proposed '''mobile''' wikitext talk page design File:Usability Improvement annotated mockup (mobile discussion).jpg|alt=Annotated mockup showing the proposed design for the mobile wikitext talk pages individual discussion view|Annotated mockup of proposed '''mobile''' wikitext talk page design File:Usability Improvement mockup (desktop).jpg|alt=Mockup showing the proposed design for desktop wikitext talk pages|Mockup of proposed design for '''desktop''' wikitext talk pages File:Usability Improvement annotated mockup (desktop).jpg|alt=Annotated mockup showing the proposed design for desktop wikitext talk pages|Annotated mockup of proposed design for '''desktop''' wikitext talk pages File:DiscussionTools Usability topic container screenshot en 2022-04-29.png|alt=Detail of change|Proposed change to the top of discussion sections File:DiscussionTools Usability page frame screenshot en 2022-04-29.png|alt=Detail of change|Proposed change to the top of talk pages File:DiscussionTools Usability Table of Contents screenshot en 2022-04-29.png|alt=Detail of change|Proposed change to Table of Contents ('''[[Vector 2022]] only''') </gallery> == Share your feedback == {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |If you prefer, you can send an e-mail message instead: talkpageconsultation{{@}}wikimedia.org |} Please share your thoughts. # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:YOUR USERNAME}} Click here to start a new topic on the talk page.] # Type <code>Feedback: YOUR USERNAME</code>. # Write answers to these questions. <strong>You can write in your language.</strong> ## Did you use mobile device or a laptop to test the prototype? ## What did you find unexpected about the prototype? ## Which steps in the "Try the Prototype" section did you find difficult to complete? ## What do you like about the prototype? ## What do you wish was different about the prototype? ## (Optional) Can you imagine this design not working on some pages? If you can, please share links to these pages? It would be very helpful. # Click the blue "{{int|discussiontools-replywidget-newtopic}}" button. # ✅ You are done! Thank you! 3lr99mahpsds7nrdupg03ye0yqmqr04 Reading/Web/Desktop Improvements/Updates/Talk to Web/id 0 1537711 5387113 5383454 2022-07-28T20:35:25Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Arsip |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 6io6s36ok1e39btnxa9d3a3o2yfbxgu Reading/Web/Desktop Improvements/Updates/Talk to Web/de 0 1537713 5387107 5383449 2022-07-28T20:35:19Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> == Zeitplan == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - reguläres Treffen</span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC (vorläufig) - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - reguläres Treffen <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archiv |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} a90utdiru7yt782g98dyzjm9682q3x9 Reading/Web/Desktop Improvements/Updates/Talk to Web/it 0 1537715 5387114 5383456 2022-07-28T20:35:26Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archivio |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} quvll0tx66usd62tjoqa54jpq0i2pwv Reading/Web/Desktop Improvements/Updates/Talk to Web/ko 0 1537717 5387117 5383458 2022-07-28T20:35:27Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=보존문서 |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 9rdi7lxpnybivwq3ybso9k3iuub5olv Technical Community Newsletter/2022/July 0 1539705 5387095 5204697 2022-07-28T20:28:30Z HLepp (WMF) 17555175 /* Upcoming conferences and workshops */ wikitext text/x-wiki {{Noise|1= *[[Technical Community Newsletter/Subscribe|Subscribe to the Technical Community Newsletter]] *[[Technical Community Newsletter|Read past issues and contribute to upcoming issues]] }} {{Draft}} == Notes on this issue == The Wikimedia Technical Community Newsletter shares highlights and news from the past quarter and information about events coming up in the next quarter. == Features == * 🌟 More than 1,000,000 comments have been posted on wiki with the [[Help:DiscussionTools|Reply tool]]. == What's new == == Community metrics == == Upcoming conferences and workshops == The [[wikimania:Hackathon|Wikimania 2022 Hackathon]] is a free, online event open to the general public to work together on technical projects, learn new skills, and meet other technical contributors. Registration is open! === Free and Open Source === == Get involved! == Are you interested in learning more or volunteering to improve Wikimedia Technology? [[mw:How_to_contribute | Get involved]]! ntxrzshx80eweem4oc2gfrdpvnpoa7n 5387906 5387095 2022-07-29T11:31:56Z MSeckington (WMF) 17523560 Added community metrics wikitext text/x-wiki {{Noise|1= *[[Technical Community Newsletter/Subscribe|Subscribe to the Technical Community Newsletter]] *[[Technical Community Newsletter|Read past issues and contribute to upcoming issues]] }} {{Draft}} == Notes on this issue == The Wikimedia Technical Community Newsletter shares highlights and news from the past quarter and information about events coming up in the next quarter. == Features == * 🌟 More than 1,000,000 comments have been posted on wiki with the [[Help:DiscussionTools|Reply tool]]. == What's new == == Community metrics == === Phabricator and Gerrit === * [[mw:Phabricator|Phabricator]]: Number of tasks created in Q1/2022: 6586 * Phabricator: Number of tasks closed in Q1/2022: 5780 * Phabricator: Number of different people who created tasks in Q1/2022: 1032 * Phabricator: Number of different people who closed tasks in Q1/2022: 483 * [[mw:Gerrit|Gerrit]]: [https://wikimedia.biterg.io/goto/ffaa743644a0c6558b23bb799c9ecd69 370 people wrote patches] ([https://wikimedia.biterg.io/goto/f4ec2750193e1cf318e1bf25d1a844b7 156 of them being volunteers]) in Q2/2022. == Upcoming conferences and workshops == The [[wikimania:Hackathon|Wikimania 2022 Hackathon]] is a free, online event open to the general public to work together on technical projects, learn new skills, and meet other technical contributors. Registration is open! === Free and Open Source === == Get involved! == Are you interested in learning more or volunteering to improve Wikimedia Technology? [[mw:How_to_contribute | Get involved]]! 83trv7lx5xforgb0ksm0lpx06jjrv4o 5387909 5387906 2022-07-29T11:45:48Z MSeckington (WMF) 17523560 Moved Wikimania Hackathon wikitext text/x-wiki {{Noise|1= *[[Technical Community Newsletter/Subscribe|Subscribe to the Technical Community Newsletter]] *[[Technical Community Newsletter|Read past issues and contribute to upcoming issues]] }} {{Draft}} == Notes on this issue == The Wikimedia Technical Community Newsletter shares highlights and news from the past quarter and information about events coming up in the next quarter. == Features == * The [[wikimania:Hackathon|Wikimania 2022 Hackathon]] is a free, online event open where anyone interested in Wikimedia technology can work together on projects, learn new skills, and meet other technical contributors. Don’t miss this opportunity to come together with other Wikimedia technical community members! Registration is now open! * 🌟 More than 1,000,000 comments have been posted on wiki with the [[Help:DiscussionTools|Reply tool]]. == What's new == == Community metrics == === Phabricator and Gerrit === * [[mw:Phabricator|Phabricator]]: Number of tasks created in Q1/2022: 6586 * Phabricator: Number of tasks closed in Q1/2022: 5780 * Phabricator: Number of different people who created tasks in Q1/2022: 1032 * Phabricator: Number of different people who closed tasks in Q1/2022: 483 * [[mw:Gerrit|Gerrit]]: [https://wikimedia.biterg.io/goto/ffaa743644a0c6558b23bb799c9ecd69 370 people wrote patches] ([https://wikimedia.biterg.io/goto/f4ec2750193e1cf318e1bf25d1a844b7 156 of them being volunteers]) in Q2/2022. == Upcoming conferences and workshops == === Free and Open Source === == Get involved! == Are you interested in learning more or volunteering to improve Wikimedia Technology? [[mw:How_to_contribute | Get involved]]! jcomjzvvty2j4ne2tp5s3s75pdjcppu 5387910 5387909 2022-07-29T11:48:28Z MSeckington (WMF) 17523560 Added recent blog posts wikitext text/x-wiki {{Noise|1= *[[Technical Community Newsletter/Subscribe|Subscribe to the Technical Community Newsletter]] *[[Technical Community Newsletter|Read past issues and contribute to upcoming issues]] }} {{Draft}} == Notes on this issue == The Wikimedia Technical Community Newsletter shares highlights and news from the past quarter and information about events coming up in the next quarter. == Features == * The [[wikimania:Hackathon|Wikimania 2022 Hackathon]] is a free, online event open where anyone interested in Wikimedia technology can work together on projects, learn new skills, and meet other technical contributors. Don’t miss this opportunity to come together with other Wikimedia technical community members! Registration is now open! * 🌟 More than 1,000,000 comments have been posted on wiki with the [[Help:DiscussionTools|Reply tool]]. == What's new == == Community metrics == === Phabricator and Gerrit === * [[mw:Phabricator|Phabricator]]: Number of tasks created in Q1/2022: 6586 * Phabricator: Number of tasks closed in Q1/2022: 5780 * Phabricator: Number of different people who created tasks in Q1/2022: 1032 * Phabricator: Number of different people who closed tasks in Q1/2022: 483 * [[mw:Gerrit|Gerrit]]: [https://wikimedia.biterg.io/goto/ffaa743644a0c6558b23bb799c9ecd69 370 people wrote patches] ([https://wikimedia.biterg.io/goto/f4ec2750193e1cf318e1bf25d1a844b7 156 of them being volunteers]) in Q2/2022. == Recent blog posts on the Tech Blog == * [https://techblog.wikimedia.org/2022/05/06/modernizing-our-tech-stack-for-serving-maps-at-wikipedia/ Modernizing our tech stack for serving maps at Wikipedia ] * [https://techblog.wikimedia.org/2022/06/13/explore-wiki-project-data-faster-with-mwsql/ Explore wiki project data faster with mwsql ] * [https://techblog.wikimedia.org/2022/06/15/new-discovery-tool-for-technical-documentation/ New discovery tool for technical documentation ] * [https://techblog.wikimedia.org/2022/06/28/what-is-in-an-edit-automated-detection-of-edit-types-on-wikipedia/ What is in an edit? Automated detection of edit types on Wikipedia ] * [https://techblog.wikimedia.org/2022/07/15/building-dreamers-how-and-why-we-opened-a-datacenter-in-france/ Building DReaMeRS: How and why we opened a datacenter in France ] == Get involved! == Are you interested in learning more or volunteering to improve Wikimedia Technology? [[mw:How_to_contribute | Get involved]]! 2u008aqx0zor9t59pb572gxqzsov3px 5387911 5387910 2022-07-29T11:51:10Z MSeckington (WMF) 17523560 Fixed blog post links wikitext text/x-wiki {{Noise|1= *[[Technical Community Newsletter/Subscribe|Subscribe to the Technical Community Newsletter]] *[[Technical Community Newsletter|Read past issues and contribute to upcoming issues]] }} {{Draft}} == Notes on this issue == The Wikimedia Technical Community Newsletter shares highlights and news from the past quarter and information about events coming up in the next quarter. == Features == * The [[wikimania:Hackathon|Wikimania 2022 Hackathon]] is a free, online event open where anyone interested in Wikimedia technology can work together on projects, learn new skills, and meet other technical contributors. Don’t miss this opportunity to come together with other Wikimedia technical community members! Registration is now open! * 🌟 More than 1,000,000 comments have been posted on wiki with the [[Help:DiscussionTools|Reply tool]]. == What's new == == Community metrics == === Phabricator and Gerrit === * [[mw:Phabricator|Phabricator]]: Number of tasks created in Q1/2022: 6586 * Phabricator: Number of tasks closed in Q1/2022: 5780 * Phabricator: Number of different people who created tasks in Q1/2022: 1032 * Phabricator: Number of different people who closed tasks in Q1/2022: 483 * [[mw:Gerrit|Gerrit]]: [https://wikimedia.biterg.io/goto/ffaa743644a0c6558b23bb799c9ecd69 370 people wrote patches] ([https://wikimedia.biterg.io/goto/f4ec2750193e1cf318e1bf25d1a844b7 156 of them being volunteers]) in Q2/2022. == Recent blog posts on the Tech Blog == * [https://techblog.wikimedia.org/2022/05/06/modernizing-our-tech-stack-for-serving-maps-at-wikipedia/ Modernizing our tech stack for serving maps at Wikipedia] * [https://techblog.wikimedia.org/2022/06/13/explore-wiki-project-data-faster-with-mwsql/ Explore wiki project data faster with mwsql] * [https://techblog.wikimedia.org/2022/06/15/new-discovery-tool-for-technical-documentation/ New discovery tool for technical documentation] * [https://techblog.wikimedia.org/2022/06/28/what-is-in-an-edit-automated-detection-of-edit-types-on-wikipedia/ What is in an edit? Automated detection of edit types on Wikipedia] * [https://techblog.wikimedia.org/2022/07/15/building-dreamers-how-and-why-we-opened-a-datacenter-in-france/ Building DReaMeRS: How and why we opened a datacenter in France] == Get involved! == Are you interested in learning more or volunteering to improve Wikimedia Technology? [[mw:How_to_contribute | Get involved]]! bk7915607f238066qwm6dwkupt2hx8z 5387912 5387911 2022-07-29T11:57:38Z MSeckington (WMF) 17523560 Added Developer Portal launch wikitext text/x-wiki {{Noise|1= *[[Technical Community Newsletter/Subscribe|Subscribe to the Technical Community Newsletter]] *[[Technical Community Newsletter|Read past issues and contribute to upcoming issues]] }} {{Draft}} == Notes on this issue == The Wikimedia Technical Community Newsletter shares highlights and news from the past quarter and information about events coming up in the next quarter. == Features == * The new [https://developer.wikimedia.org/ Wikimedia Developer Portal] has launched! Find technical documentation, and connect with the developer community behind Wikipedia and other Wikimedia projects. * The [[wikimania:Hackathon|Wikimania 2022 Hackathon]] is a free, online event open where anyone interested in Wikimedia technology can work together on projects, learn new skills, and meet other technical contributors. Don’t miss this opportunity to come together with other Wikimedia technical community members! Registration is now open! * 🌟 More than 1,000,000 comments have been posted on wiki with the [[Help:DiscussionTools|Reply tool]]. == What's new == == Community metrics == === Phabricator and Gerrit === * [[mw:Phabricator|Phabricator]]: Number of tasks created in Q1/2022: 6586 * Phabricator: Number of tasks closed in Q1/2022: 5780 * Phabricator: Number of different people who created tasks in Q1/2022: 1032 * Phabricator: Number of different people who closed tasks in Q1/2022: 483 * [[mw:Gerrit|Gerrit]]: [https://wikimedia.biterg.io/goto/ffaa743644a0c6558b23bb799c9ecd69 370 people wrote patches] ([https://wikimedia.biterg.io/goto/f4ec2750193e1cf318e1bf25d1a844b7 156 of them being volunteers]) in Q2/2022. == Recent blog posts on the Tech Blog == * [https://techblog.wikimedia.org/2022/05/06/modernizing-our-tech-stack-for-serving-maps-at-wikipedia/ Modernizing our tech stack for serving maps at Wikipedia] * [https://techblog.wikimedia.org/2022/06/13/explore-wiki-project-data-faster-with-mwsql/ Explore wiki project data faster with mwsql] * [https://techblog.wikimedia.org/2022/06/15/new-discovery-tool-for-technical-documentation/ New discovery tool for technical documentation] * [https://techblog.wikimedia.org/2022/06/28/what-is-in-an-edit-automated-detection-of-edit-types-on-wikipedia/ What is in an edit? Automated detection of edit types on Wikipedia] * [https://techblog.wikimedia.org/2022/07/15/building-dreamers-how-and-why-we-opened-a-datacenter-in-france/ Building DReaMeRS: How and why we opened a datacenter in France] == Get involved! == Are you interested in learning more or volunteering to improve Wikimedia Technology? [[mw:How_to_contribute | Get involved]]! euwoh6shaw3kl4mvsl7k8rk85hlis2f Talk pages project/Usability/Prototype/ja 0 1541430 5387258 5370944 2022-07-28T21:38:05Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:Usability_Improvement_annotated_mockup_(desktop).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">A mockup showing the proposed new design for desktop wikitext talk pages.</span>|center|thumb|600x600px|<span lang="en" dir="ltr" class="mw-content-ltr">Mockup of new design for '''desktop''' wikitext talk pages.</span>]] <big>ようこそ!</big> <span lang="en" dir="ltr" class="mw-content-ltr">This page has instructions for testing design changes to wikitext talk pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These design changes are a part of the {{ll|Talk pages project}} and an effort to make talk pages easier for people to recognize and use.</span> == プロトタイプを試す == # <span lang="en" dir="ltr" class="mw-content-ltr">Visit this {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:New_York $1]</mark>|article talk page}} or this {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Bob $1]</mark>|user talk page}} on the special prototype wiki.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Find the discussion that has been edited most recently.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Find the discussion that has the most people participating in it.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Find the discussion with the most comments.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Scroll back to the discussion you identified in "Step 4." Figure out how you would do the following:</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Post a reply in the discussion.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Edit the reply you posted.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Next, start a discussion about a new topic.</span> # ✅ <span lang="en" dir="ltr" class="mw-content-ltr">You are now ready to share your feedback.</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Design</span> == <gallery mode="slideshow" showthumbnails> File:Usability Improvement mockup (mobile).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for mobile wikitext talk pages</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement annotated mockup (mobile overview).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for the mobile wikitext talk pages landing page view</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement annotated mockup (mobile discussion).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup showing the proposed design for the mobile wikitext talk pages individual discussion view</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement mockup (desktop).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for desktop wikitext talk pages</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Mockup of proposed design for '''desktop''' wikitext talk pages</span> File:Usability Improvement annotated mockup (desktop).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup showing the proposed design for desktop wikitext talk pages</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed design for '''desktop''' wikitext talk pages</span> File:DiscussionTools Usability topic container screenshot en 2022-04-29.png|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Detail of change</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to the top of discussion sections</span> File:DiscussionTools Usability page frame screenshot en 2022-04-29.png|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Detail of change</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to the top of talk pages</span> File:DiscussionTools Usability Table of Contents screenshot en 2022-04-29.png|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Detail of change</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to Table of Contents ('''[[Vector 2022]] only''')</span> </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Share your feedback == </div> {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |<span lang="en" dir="ltr" class="mw-content-ltr">If you prefer, you can send an e-mail message instead:</span> talkpageconsultation{{@}}wikimedia.org |} <span lang="en" dir="ltr" class="mw-content-ltr">Please share your thoughts.</span> # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:あなたの利用者名}} <span lang="en" dir="ltr" class="mw-content-ltr">Click here to start a new topic on the talk page.</span>] # <span lang="en" dir="ltr" class="mw-content-ltr">Type <code>Feedback: YOUR USERNAME</code></span>. # <span lang="en" dir="ltr" class="mw-content-ltr">Write answers to these questions.</span> <strong><span lang="en" dir="ltr" class="mw-content-ltr">You can write in your language.</span></strong> ## <span lang="en" dir="ltr" class="mw-content-ltr">Did you use mobile device or a laptop to test the prototype?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">What did you find unexpected about the prototype?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Which steps in the "Try the Prototype" section did you find difficult to complete?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">What do you like about the prototype?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">What do you wish was different about the prototype?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">(Optional) Can you imagine this design not working on some pages? If you can, please share links to these pages? It would be very helpful.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Click the blue "{{int|discussiontools-replywidget-newtopic}}" button.</span> # ✅ <span lang="en" dir="ltr" class="mw-content-ltr">You are done! Thank you!</span> febesqtfm947d0zz7mvjqiemqobkhkl MediaWiki 1.40/Roadmap 0 1542457 5387219 5360010 2022-07-28T21:21:11Z Jdforrester (WMF) 574543 Pushing back everything by a month. wikitext text/x-wiki {{Wikimedia engineering project information | name = MediaWiki 1.40 | description = Deployment of MediaWiki 1.40.0-wmf.XX versions and release of [[MediaWiki 1.40]] | start = 2022-09-05 | end = | group = [[Wikimedia Release Engineering Team|Release Engineering]] | previous = [[MediaWiki 1.39/Roadmap|MediaWiki 1.39]] | next = [[MediaWiki 1.41/Roadmap|MediaWiki 1.41]] | projectpage = MediaWiki 1.40 | display = {{{display|}}} }} == Timeline == Wikimedia deployments of MediaWiki 1.40 alpha versions will happen on weekly intervals, within a longer stretch (approximately 6 months) between publishing releases of the installer for third-party users. '''Current status:''' {{To do}} {{-}} == Schedule for the deployments == See [[wikitech:Deployments]] for current schedule, dates, and times. See [https://versions.toolforge.org/ status board] for current status. {{WMFReleaseTableHead}} {{WMFReleaseTableRow|4|2022-10-03|}} {{WMFReleaseTableRow|3|2022-09-26|}} {{WMFReleaseTableRow|2|2022-09-19|}} {{WMFReleaseTableRow|1|2022-09-12|}} {{WMFReleaseTableFooter}} d17e7y2eylozhn3on3qevp1z9q49dgd 5387220 5387219 2022-07-28T21:21:43Z Jdforrester (WMF) 574543 +1 wikitext text/x-wiki {{Wikimedia engineering project information | name = MediaWiki 1.40 | description = Deployment of MediaWiki 1.40.0-wmf.XX versions and release of [[MediaWiki 1.40]] | start = 2022-09-12 | end = | group = [[Wikimedia Release Engineering Team|Release Engineering]] | previous = [[MediaWiki 1.39/Roadmap|MediaWiki 1.39]] | next = [[MediaWiki 1.41/Roadmap|MediaWiki 1.41]] | projectpage = MediaWiki 1.40 | display = {{{display|}}} }} == Timeline == Wikimedia deployments of MediaWiki 1.40 alpha versions will happen on weekly intervals, within a longer stretch (approximately 6 months) between publishing releases of the installer for third-party users. '''Current status:''' {{To do}} {{-}} == Schedule for the deployments == See [[wikitech:Deployments]] for current schedule, dates, and times. See [https://versions.toolforge.org/ status board] for current status. {{WMFReleaseTableHead}} {{WMFReleaseTableRow|4|2022-10-03|}} {{WMFReleaseTableRow|3|2022-09-26|}} {{WMFReleaseTableRow|2|2022-09-19|}} {{WMFReleaseTableRow|1|2022-09-12|}} {{WMFReleaseTableFooter}} ekt0630ghn6786xsjyau5qvdnvud0xc Reading/Web/Desktop Improvements/Updates/Talk to Web/es 0 1543317 5387108 5385622 2022-07-28T20:35:21Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} Hemos planteado dos tipos de encuentros: * '''Las estándar''' son para cualquier persona interesada en el proyecto. Se realizan en inglés. Compartimos actualizaciones, recogemos feedback y respondemos preguntas. Todo el mundo es bienvenido. * '''Encuentros con traducción simultánea''', dedicados a comunidades Wikimedia específicas. Esperamos que a estos encuentros específicos acuda una buena representación de dichas comunidades para poder centrarnos en cómo Vector 2022 se integrará en sus wikis. Igualmente, cualquier persona es bienvenida. '''<span class="mw-translate-fuzzy">[https://wikimedia.zoom.us/j/5304280674 Haz clic aquí para unirte] / [https://wikimedia.zoom.us/u/kc2hamfYz9 Marca por tu ubicación] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' Estos enlaces funcionan para todos los encuentros excepto el de Wikimania. == Agenda == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - encuentro estándar</span> * {{ymd|2022|8|2}}, 17:00 UTC - encuentro con traducción simultánea en ruso * {{ymd|2022|8|4}}, 17:00 UTC - encuentro con traducción simultánea en árabe * {{ymd|2022|8|4}}, 19:00 UTC - encuentro con traducción simultánea en español * {{ymd|2022|8|13}}, 8:05 UTC - Sesión de Wikimanía sobre Vector 2022 * {{ymd|2022|8|18}}, 10:00 UTC (por confirmar) - encuentro con traducción simultánea en chino * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - encuentro estándar (en inglés) <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archivo |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 43woyb8ex9252wdgf5hpjhjt28qk9od 5387130 5387108 2022-07-28T20:35:42Z SGrabarczuk (WMF) 9240933 wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} Hemos planteado dos tipos de encuentros: * '''Las estándar''' son para cualquier persona interesada en el proyecto. Se realizan en inglés. Compartimos actualizaciones, recogemos feedback y respondemos preguntas. Todo el mundo es bienvenido. * '''Encuentros con traducción simultánea''', dedicados a comunidades Wikimedia específicas. Esperamos que a estos encuentros específicos acuda una buena representación de dichas comunidades para poder centrarnos en cómo Vector 2022 se integrará en sus wikis. Igualmente, cualquier persona es bienvenida. '''[https://wikimedia.zoom.us/j/5304280674 Haz clic aquí para unirte] / [https://wikimedia.zoom.us/u/kc2hamfYz9 marca por tu ubicación] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].''' Estos enlaces funcionan para todos los encuentros excepto el de Wikimania. == Agenda == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - encuentro estándar</span> * {{ymd|2022|8|2}}, 17:00 UTC - encuentro con traducción simultánea en ruso * {{ymd|2022|8|4}}, 17:00 UTC - encuentro con traducción simultánea en árabe * {{ymd|2022|8|4}}, 19:00 UTC - encuentro con traducción simultánea en español * {{ymd|2022|8|13}}, 8:05 UTC - Sesión de Wikimanía sobre Vector 2022 * {{ymd|2022|8|18}}, 10:00 UTC (por confirmar) - encuentro con traducción simultánea en chino * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - encuentro estándar (en inglés) <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archivo |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} g6hy5m3begnew5bu22xieew8g2w1yix 5387367 5387130 2022-07-28T22:11:35Z Zapipedia (WMF) 17560702 wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} Hemos planteado dos tipos de encuentros: * '''Los estándar''' son para cualquier persona interesada en el proyecto. Se realizan en inglés. Compartimos actualizaciones, recogemos feedback y respondemos preguntas. Todo el mundo es bienvenido. * '''Encuentros con traducción simultánea''', dedicados a comunidades Wikimedia específicas. Esperamos que a estos encuentros específicos acuda una buena representación de dichas comunidades para poder centrarnos en cómo Vector 2022 se integrará en sus wikis. Igualmente, cualquier persona es bienvenida. '''[https://wikimedia.zoom.us/j/5304280674 Haz clic aquí para unirte] / [https://wikimedia.zoom.us/u/kc2hamfYz9 marca por tu ubicación] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].''' Estos enlaces funcionan para todos los encuentros excepto el de Wikimania. == Agenda == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - encuentro estándar</span> * {{ymd|2022|8|2}}, 17:00 UTC - encuentro con traducción simultánea en ruso * {{ymd|2022|8|4}}, 17:00 UTC - encuentro con traducción simultánea en árabe * {{ymd|2022|8|4}}, 19:00 UTC - encuentro con traducción simultánea en español * {{ymd|2022|8|13}}, 8:05 UTC - Sesión de Wikimanía sobre Vector 2022 * {{ymd|2022|8|18}}, 10:00 UTC (por confirmar) - encuentro con traducción simultánea en chino * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - encuentro estándar (en inglés) <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archivo |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} egcywbnnv6ux9dxatw5cu5dv1i632y7 Reading/Web/Desktop Improvements/Updates/Talk to Web/ru 0 1543320 5387120 5383461 2022-07-28T20:35:30Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span class="mw-translate-fuzzy">[https://wikimedia.zoom.us/j/5304280674 Присоединиться к встрече] / [https://wikimedia.zoom.us/u/kc2hamfYz9 соединиться по местному телефону] / [https://etherpad.wikimedia.org/p/web-team-office-hours заметки].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Архив |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 32a594wsnfo5jidmsrorwgk9n29qawu Talk pages project/Usability/Prototype/ms 0 1546645 5387261 5370945 2022-07-28T21:38:07Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:Usability_Improvement_annotated_mockup_(desktop).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">A mockup showing the proposed new design for desktop wikitext talk pages.</span>|center|thumb|600x600px|Conta rekabentuk baharu untuk laman bincang teks wiki '''tasmeja'''.]] <big><span lang="en" dir="ltr" class="mw-content-ltr">Welcome!</span></big> <span lang="en" dir="ltr" class="mw-content-ltr">This page has instructions for testing design changes to wikitext talk pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These design changes are a part of the {{ll|Talk pages project}} and an effort to make talk pages easier for people to recognize and use.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Try the prototype == </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Visit this {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:New_York $1]</mark>|article talk page}} or this {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Bob $1]</mark>|user talk page}} on the special prototype wiki.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Find the discussion that has been edited most recently.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Find the discussion that has the most people participating in it.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Find the discussion with the most comments.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Scroll back to the discussion you identified in "Step 4." Figure out how you would do the following:</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Post a reply in the discussion.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Edit the reply you posted.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Next, start a discussion about a new topic.</span> # ✅ <span lang="en" dir="ltr" class="mw-content-ltr">You are now ready to share your feedback.</span> == Rekabentuk == <gallery mode="slideshow" showthumbnails> File:Usability Improvement mockup (mobile).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for mobile wikitext talk pages</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement annotated mockup (mobile overview).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for the mobile wikitext talk pages landing page view</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement annotated mockup (mobile discussion).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup showing the proposed design for the mobile wikitext talk pages individual discussion view</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement mockup (desktop).jpg|alt=Conta yang menunjukkan rekabentuk terusul untuk laman bincang teks wiki tasmeja|Conta rekabentuk terusul untuk laman bincang teks wiki'''tasmeja'''. File:Usability Improvement annotated mockup (desktop).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup showing the proposed design for desktop wikitext talk pages</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed design for '''desktop''' wikitext talk pages</span> File:DiscussionTools Usability topic container screenshot en 2022-04-29.png|alt=Butiran perubahan|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to the top of discussion sections</span> File:DiscussionTools Usability page frame screenshot en 2022-04-29.png|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Detail of change</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to the top of talk pages</span> File:DiscussionTools Usability Table of Contents screenshot en 2022-04-29.png|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Detail of change</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to Table of Contents ('''[[Vector 2022]] only''')</span> </gallery> <div lang="en" dir="ltr" class="mw-content-ltr"> == Share your feedback == </div> {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |<span lang="en" dir="ltr" class="mw-content-ltr">If you prefer, you can send an e-mail message instead:</span> talkpageconsultation{{@}}wikimedia.org |} <span lang="en" dir="ltr" class="mw-content-ltr">Please share your thoughts.</span> # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:YOUR USERNAME}} <span lang="en" dir="ltr" class="mw-content-ltr">Click here to start a new topic on the talk page.</span>] # <span lang="en" dir="ltr" class="mw-content-ltr">Type <code>Feedback: YOUR USERNAME</code></span>. # <span lang="en" dir="ltr" class="mw-content-ltr">Write answers to these questions.</span> <strong><span lang="en" dir="ltr" class="mw-content-ltr">You can write in your language.</span></strong> ## <span lang="en" dir="ltr" class="mw-content-ltr">Did you use mobile device or a laptop to test the prototype?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">What did you find unexpected about the prototype?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Which steps in the "Try the Prototype" section did you find difficult to complete?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">What do you like about the prototype?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">What do you wish was different about the prototype?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">(Optional) Can you imagine this design not working on some pages? If you can, please share links to these pages? It would be very helpful.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Click the blue "{{int|discussiontools-replywidget-newtopic}}" button.</span> # ✅ <span lang="en" dir="ltr" class="mw-content-ltr">You are done! Thank you!</span> a7rxv2q0njkw972goeik1knqg3v2muj Extension:Highlight Links in Category/ms 102 1546756 5387153 5345727 2022-07-28T21:07:59Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension|templatemode = |status = stable |type1 = interface |type2 = mywiki |hook1 = GetLinkColours |hook2 = |username = BrentLaabs |author = Brent Laabs |description = Adds a CSS class to links pointing to members of a category |image = Highlightlinksincategory.png |imagesize = 250 |version = 0.9.0 |update = 2021-05-29 |version preview = |update preview = |mediawiki = 1.25+ |php = |needs-updatephp = No |composer = |table1 = |table2 = |license = MIT |download = {{GithubDownload|labster|HighlightLinksInCategory}} |readme = [https://github.com/labster/HighlightLinksInCategory/blob/master/README.md readme] |changelog = [https://github.com/labster/HighlightLinksInCategory repository] |example = https://allthetropes.org/ |namespace = |parameters = $wgHighlightLinksInCategory |tags = |rights = |compatibility = |bugzilla = }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''Highlight Links in Category''' is an extension that adds a CSS class to links pointing to members of a category. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For reporting an issue or a bug, please use [https://phabricator.miraheze.org Miraheze Phabricator]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Installation== </div> {{ExtensionInstall|HighlightLinksInCategory|registration=required}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Configuration parameters== </div> ; $wgHighlightLinksInCategory : <span lang="en" dir="ltr" class="mw-content-ltr">This global is an array that configures which categories get an added CSS class. The keys are the Category names, which must include underscores instead of spaces. Do not include the Category: namespace. The value for each key is the CSS class you would like to add to that category. For example:</span> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "Disambiguation_pages" => 'disambig', "Templates" => 'templates', ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want add more than one class, separate the class names with spaces, like </div> {{#tag:syntaxhighlight| $wgHighlightLinksInCategory = array( "My_Cat" => "class1 class2 class3" ); |lang=php}} <div lang="en" dir="ltr" class="mw-content-ltr"> You can add as many of these as you want, but from a UX perspective it's probably not awesome to add 500 different style links. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If $wgHighlightLinksInCategory is not set or empty, this extension will do nothing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you're running a wiki farm and need to turn it off on some wikis, set <syntaxhighlight lang=php inline>$wgHighlightLinksInCategory = null</syntaxhighlight>; using {{phpi|false}} could lead to incorrect behavior.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Styling== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Simply add the styles you need for these links to MediaWiki:Common.css on your wiki. For example: </div> {{#tag:syntaxhighlight| a.disambig { color: rebeccapurple } a.templates { font-weight: bold; background-color: #efe; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want one category to override another, you'll have to specify it with CSS. </div> {{#tag:syntaxhighlight| a.templates.disambig { font-weight: normal; background-color: transparent; color: rebeccapurple; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> Or alternatively, you could have defined the original <code>a.templates</code> rule as <code>a.templates:not(.disambig)</code> instead. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There's also the link icon approach: </div> {{#tag:syntaxhighlight| a.superlink { background-image: url(super.png); padding-left: 16px; } |lang=css}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==User Toggles== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> An easy way to set up toggling this highlighting on or off is to make a [[Extension:Gadgets|Gadget]] with CSS in it. Yes, this is a personalization extension that outsources the personalization part to other extensions; I can still sleep at night. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==How this works== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Right after MediaWiki determines which linked pages exist (to make redlinks), it runs the <code>GetLinkColours</code> hook (see LinkHolderArray.php).</span> <span lang="en" dir="ltr" class="mw-content-ltr">As we have a list of all of the page ids which are linked on that page, we can run one database query to see which of these links are in the set of categories we want to highlight.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Because the query only happens on an index of the <code>categorylinks</code> table, it's reasonably fast.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then CSS classes are assigned based on the result, using the configuration values the user sets in <code>$wgHighlightLinksInCategory</code>.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Explaining how CSS works is outside the scope of this document. </div> == Hal tertahu == <div lang="en" dir="ltr" class="mw-content-ltr"> * CSS styles are not added in Flow, because it doesn't appear to call the GetLinkColors hook there. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==See also== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * [[:Category:LinkEnd extensions]] - which customize links in other ways </div> {{By Miraheze}} [[Category:Extensions by Miraheze{{#translation:}}]] [[Category:Simple extensions{{#translation:}}]] [[Category:Category extensions{{#translation:}}|{{PAGENAME}}]] rs3mvepzqw7e8oe1hxphlfoame6p80d Talk pages project/Replying/Prototype testing/de 0 1551540 5386807 5232165 2022-07-28T19:12:07Z ThisCarthing 17456337 Created page with "Testziele" wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> Throughout the course of [[Special:MyLanguage/Talk pages project/replying|this project]], the {{ll|Editing team}} will be developing a series of prototypes. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> These prototypes are intended to help answer questions like: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * How does the prototype work compared to how contributors expect it to work? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * What enhancements could be made to improve the prototype? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * What edge cases have not yet been considered that need to be designed for before this version can be deployed? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This page is where you test the different prototypes the team is developing and help answer the questions listed above. </div> == Reply tool version 2.0 == This is a usability test of [[mw:Talk_pages_project/replying#Version_2.0|Version 2.0]] of the Reply tool. We appreciate the effort you are putting in to help improve how the tool looks and functions. Below you will find information about: *The purpose of this usability test: [[mw:Talk_pages_project/Replying/Prototype_testing#Test_goals|Test goals]]. *How to participate in the test: [[mw:Talk_pages_project/Replying/Prototype_testing#Test_instructions|Test instructions]]. ===Test goals=== The purpose of this test is to answer these questions: *''For people who have experience using Wikipedia talk pages, what are their impressions of Version 2.0 of the Reply tool?'' *''Are the tool's features easy to discover?'' *''Are the tool's features intuitive to use?'' ===Test instructions=== #'''Complete''' the tasks described in the table below titled, ''Testing Reply tool version 2.0.'' #'''Post''' the feedback you have to the Replying tool's project talk page here: https://w.wiki/RZf (this link may take longer than expected to load). === Testing Reply tool version 2.0=== {| class="wikitable" |+ !Task # !Task description !Feedback questions* |- |1. |On a desktop computer, go to this talk page: https://en.wikipedia.beta.wmflabs.org/wiki/Talk:Dogs?dtvisual=1 | - |- |2. |'''Find''' the section heading, "How can we make this article better?" | - |- |3 |'''Click''' any one of the "Reply" links that appear in this section. | - |- |4. |'''Pause''' and take a minute to look at the Reply tool. |''What are your initial impressions of the tool? What stands out to you? Do you find something particularly eye-catching? Confusing?'' |- |5. |'''Type a comment''' using the Reply tool's <code>visual</code> mode and format (bold, italicize, etc.) some portion of the text you have just written. |''Can you figure out how to do so? What do you think of this experience?'' |- |6. |In <code>visual</code> mode, '''ping someone''' who has '''already''' commented in this section. |''Can you figure out how to do so? What do you think of this experience?'' |- |7. |Next, '''ping another person'''. This time, ping someone who has '''not already''' commented in this section. |''Can you figure out how to ping someone who has <u>not</u> already commented in this section? What do you think of this experience?'' |- |8. |'''Delete the ping''' you created in Task 7. |''Can you figure out how to delete the ping you created in Task 7? What do you think of this experience?'' |- |9. |Now, imagine you want to '''see how the comment''' you have just written will '''appear in wikitext'''. |''Can you figure out how to see the comment you were writing in the <code>visual</code> mode, in the <code>source</code> mode before posting it to the talk page? Does the wikitext look how you expected?'' |- |10. |Imagine you are satisfied with the comment you've written. Go ahead and '''post it in the discussion.''' |''Can you figure out how to do so?'' |- |11. |Check to see the '''comment was posted.''' |''Does the comment appear on the talk page as you expected?'' |- |12. |Go to the talk page's history, and '''inspect the diff''' you just created. |''Does the diff look as you expected?'' |} * ''Please post the feedback you have to the Replying tool's project talk page by clicking here: https://w.wiki/RZf'' <div lang="en" dir="ltr" class="mw-content-ltr"> == Reply tool version 1.0 == </div> <span lang="en" dir="ltr" class="mw-content-ltr">This is the first structured test of version of 1.0 of the prototype for replying to specific comments on talk pages.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The team is thankful for the effort you are putting in to try an <em>early</em> version of this software.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Below you will find information about: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Why tests like these matter: </div> '''[[#Test goals|Testziele]]''' <div lang="en" dir="ltr" class="mw-content-ltr"> * How to participate in the test: </div> '''[[#Test instructions|<span lang="en" dir="ltr" class="mw-content-ltr">Test instructions</span>]]''' <div lang="en" dir="ltr" class="mw-content-ltr"> * What the feedback you share will be used for: </div> '''[[#Your feedback|<span lang="en" dir="ltr" class="mw-content-ltr">Your feedback</span>]]''' {{anchor|Test goals}} === Testziele === <div lang="en" dir="ltr" class="mw-content-ltr"> This is a structured tested designed to answer questions like: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * How does the prototype work compared to how contributors expect it to work? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * What enhancements could be made to improve the prototype in [[Special:MyLanguage/Talk pages project/replying#Versions|future versions]]? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * What uses have not yet been considered that need to be designed for before this version can be deployed? </div> {{anchor|Test instructions}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Test instructions === </div> '''Schritt 1:''' <span lang="en" dir="ltr" class="mw-content-ltr">Read through the [[#Before you start|Before you start]] and [[#Test|Test]] sections.</span> '''Schritt 2:''' <span lang="en" dir="ltr" class="mw-content-ltr">Complete the tasks listed in the [[#Tasks to complete|Tasks to complete]] section.</span> '''Schritt 3:''' <span lang="en" dir="ltr" class="mw-content-ltr">Review the questions listed in the [[#Your feedback|Your feedback]] section.</span> '''Schritt 4:''' <span lang="en" dir="ltr" class="mw-content-ltr">Share your thoughts (in any language) about the prototype here:</span> '''[[Topic:Vcwvt3bq03o5gv8h]]''' {{anchor|Before you start}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Before you start ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Before getting started, there are a couple of things to keep in mind: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # All of the steps below will take place in [[Special:MyLanguage/Beta Cluster|a test environment]], so you will not actually be editing or vandalizing Wikipedia. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # This test may seem simple. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This is because we are trying to keep the test consistent for contributors across experience levels.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> # Feel free to experiment in ways not described in the "Tasks" section. </div> <span lang="en" dir="ltr" class="mw-content-ltr">Although, if you encounter an error or something unexpected, please provide enough context for us to be able to recreate the issue/experience.</span> {{anchor|Test}} ==== Test ==== <span lang="en" dir="ltr" class="mw-content-ltr">Imagine that you come to an article on [https://en.wikipedia.beta.wmflabs.org/wiki/Dogs Wikipedia about dogs].</span> <span lang="en" dir="ltr" class="mw-content-ltr">You wonder, "''What could be controversial about this topic?''" and click on the "Talk" tab to view conversations about this article.</span> <span lang="en" dir="ltr" class="mw-content-ltr">There, you notice a comment from someone else that you want to respond to...</span> <div lang="en" dir="ltr" class="mw-content-ltr"> Once you've completed the tasks below, please review the "Questions" and share your experience on the project talk page here: </div> LINK. {{anchor|Task to complete}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Tasks to complete ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # On a desktop computer, go to this talk page: </div><br/> https://en.wikipedia.beta.wmflabs.org/wiki/Talk:Dogs <div lang="en" dir="ltr" class="mw-content-ltr"> # Find the section heading, '''"How can we make this article better?"''' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # Within this section, there is a discussion happening. </div> <span lang="en" dir="ltr" class="mw-content-ltr">'''Reply to any comment''' in the discussion (you can write anything for the purpose of this test).</span> # '''<span lang="en" dir="ltr" class="mw-content-ltr">Publish your response.</span>''' <div lang="en" dir="ltr" class="mw-content-ltr"> # '''Find your published response''' on the page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # Imagine that you notice an error in the response that you wrote. </div> '''<span lang="en" dir="ltr" class="mw-content-ltr">Go back in, fix it, and publish the changes.</span>''' <div lang="en" dir="ltr" class="mw-content-ltr"> # '''Find your published response''' on the page. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # '''Start typing another short reply''', but this time imagine that you changed your mind mid-reply and decided that you don’t want to write a reply. Try to '''cancel out'''. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # Now click to '''view the page history tab'''. </div> # '''<span lang="en" dir="ltr" class="mw-content-ltr">Find your reply.</span>''' {{anchor|Your feedback}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Your feedback === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> When you are finished testing out the prototype, please go to the [[Talk:Talk pages project/replying|Replying talk page]] and post your answers to the questions below in this thread: </div> '''[[Topic:Vcwvt3bq03o5gv8h]]'''. <div lang="en" dir="ltr" class="mw-content-ltr"> # Do you think that you completed the Tasks above correctly? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # Was there anything painful or not obvious about this experience? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # How does replying with the replying prototype compare with the current experience for replying to comments on talk pages on desktop? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # What other additional comments, concerns, or ideas would you like to make known? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # How do you typically use talk pages (across namespaces)? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # How often do you typically participate on/edit talk pages? Daily? Weekly? Monthly? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The feedback you share as part of this test will be used to refine the existing version of this feature and help set the requirements for future versions of this feature and others. </div> [[Category:Talk pages project{{#translation:}}]] 7dlmro7gx0uap3brpiqjn9uacremgzi Talk pages project/Usability/Prototype/hi 0 1551990 5387259 5370940 2022-07-28T21:38:05Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:Usability_Improvement_annotated_mockup_(desktop).jpg|alt=डेस्कटॉप विकीटेक्स्ट टॉक पेजों के लिए प्रस्तावित नए डिज़ाइन को दर्शाने वाला एक मॉकअप।|center|thumb|600x600px|''डेस्कटॉप''' विकिपाठ वार्ता पृष्ठों के लिए नए डिजाइन का मॉकअप।]] <big>स्वागत!</big> इस पृष्ठ में विकिपाठ्य-पाठ के वार्ता पृष्ठों में डिज़ाइन परिवर्तनों के परीक्षण के लिए निर्देश दिए गए हैं। ये डिज़ाइन परिवर्तन {{ll|Talk pages project}} का एक हिस्सा हैं और लोगों के लिए टॉक पेजों को पहचानने और उपयोग करने में आसान बनाने का एक प्रयास है। == प्रोटोटाइप का प्रयास करें == # विशेष प्रोटोटाइप विकी पर इस {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:New_York $1]</mark>|लेख वार्ता पृष्ठ}} या इस {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Bob $1]</mark>|उपयोगकर्ता वार्ता पृष्ठ}} पर जाएं। # वह चर्चा ढूंढें जिसे हाल ही में संपादित किया गया है। # उस चर्चा का पता लगाएं जिसमें सबसे अधिक लोग भाग ले रहे हैं। # सबसे अधिक टिप्पणियों के साथ चर्चा खोजें। # "चरण 4" में आपके द्वारा पहचानी गई चर्चा पर वापस स्क्रॉल करें। पता लगाएँ कि आप निम्नलिखित कैसे करेंगे: ## चर्चा में उत्तर पोस्ट करें। ## आपके द्वारा पोस्ट किए गए उत्तर को संपादित करें। # इसके बाद, एक नए विषय के बारे में चर्चा शुरू करें। # ✅ अब आप अपनी प्रतिक्रिया साझा करने के लिए तैयार हैं। == डिज़ाइन == <gallery mode="slideshow" showthumbnails> File:Usability Improvement mockup (mobile).jpg|alt=मोबाइल wikitext टॉक पेजों के लिए प्रस्तावित डिज़ाइन दिखाने वाला मॉकअप|प्रस्तावित '''मोबाइल''' विकिपाठ वार्ता पृष्ठ डिजाइन का मॉकअप File:Usability Improvement annotated mockup (mobile overview).jpg|alt=मोबाइल विकिटेक्स्ट टॉक पेज लैंडिंग पेज व्यू के लिए प्रस्तावित डिज़ाइन दिखाने वाला मॉकअप|प्रस्तावित '''मोबाइल''' विकिपाठ वार्ता पृष्ठ डिजाइन का एनोटेटेड मॉकअप File:Usability Improvement annotated mockup (mobile discussion).jpg|alt=मोबाइल विकीटेक्स्ट टॉक पेजों के लिए व्यक्तिगत चर्चा दृश्य के लिए प्रस्तावित डिज़ाइन को दर्शाने वाला एनोटेट मॉकअप|प्रस्तावित '''मोबाइल''' विकिपाठ वार्ता पृष्ठ डिजाइन का एनोटेटेड मॉकअप File:Usability Improvement mockup (desktop).jpg|alt=डेस्कटॉप विकीटेक्स्ट टॉक पेजों के लिए प्रस्तावित डिज़ाइन दिखाने वाला मॉकअप|'''डेस्कटॉप''' विकिपाठ वार्ता पृष्ठों के लिए प्रस्तावित डिजाइन का मॉकअप File:Usability Improvement annotated mockup (desktop).jpg|alt=एनोटेटेड मॉकअप, जो डेस्कटॉप विकिपाठ वार्ता पृष्ठों के लिए प्रस्तावित डिज़ाइन दिखा रहा है|'''डेस्कटॉप''' विकिपाठ टॉक पेजों के लिए प्रस्तावित डिजाइन का एनोटेटेड मॉकअप File:DiscussionTools Usability topic container screenshot en 2022-04-29.png|alt=परिवर्तन का विवरण|चर्चा अनुभागों के शीर्ष पर प्रस्तावित परिवर्तन File:DiscussionTools Usability page frame screenshot en 2022-04-29.png|alt=परिवर्तन का विवरण|वार्ता पृष्ठों के शीर्ष पर प्रस्तावित परिवर्तन File:DiscussionTools Usability Table of Contents screenshot en 2022-04-29.png|alt=परिवर्तन का विवरण|विषय-सूची में प्रस्तावित परिवर्तन ('''[[वेक्टर 2022]] केवल '''') </gallery> == अपनी प्रतिक्रिया साझा करें == {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |यदि आप चाहें, तो आप इसके बजाय एक ई-मेल संदेश भेज सकते हैं: talkpageconsultation{{@}}wikimedia.org |} कृपया अपने विचार साझा करें। # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:तुम्हारा प्रयोगकर्ती नाम}} वार्ता पृष्ठ पर एक नया विषय शुरू करने के लिए यहां क्लिक करें।] # टाइप करें <code>प्रतिक्रिया: आपका उपयोगकर्ता नाम</code>. # इन प्रश्नों के उत्तर लिखिए। <strong>आप अपनी भाषा में लिख सकते हैं।</strong> ## क्या आपने प्रोटोटाइप का परीक्षण करने के लिए मोबाइल डिवाइस या लैपटॉप का उपयोग किया था? ## प्रोटोटाइप के बारे में आपको क्या अप्रत्याशित लगा? ## "प्रोटोटाइप आज़माएं" अनुभाग के किन चरणों को पूरा करना आपको कठिन लगा? ## आपको प्रोटोटाइप के बारे में क्या पसंद है? ## आप क्या चाहते हैं कि प्रोटोटाइप के बारे में अलग था? ## (वैकल्पिक) क्या आप कल्पना कर सकते हैं कि यह डिज़ाइन कुछ पृष्ठों पर काम नहीं कर रहा है? यदि आप कर सकते हैं, तो कृपया इन पृष्ठों के लिंक साझा करें? यह बहुत मददगार होगा। # नीले "$बटन" बटन पर क्लिक करें। # ✅ आप कर चुके हैं! आपको धन्यवाद! oagy0eksrd0kj0pb0u2osh7sl5kli7y Translations:Reading/Web/Desktop Improvements/225/zh 1198 1552601 5387652 5280528 2022-07-29T04:22:55Z Chubit 17346826 wikitext text/x-wiki 我们希望我们的改进在2022年8月/9月成为所有wiki的默认设置。 fboffzhrao6iiku76jduiop8iunnn64 Translations:Structured Data Across Wikimedia/Page display title/de 1198 1554305 5386794 5238285 2022-07-28T19:07:40Z ThisCarthing 17456337 wikitext text/x-wiki Strukturierte Daten in Wikimedia h3d4evoglnb0bevkbhtgap4drx91zpf Structured Data Across Wikimedia/de 0 1554306 5386796 5298459 2022-07-28T19:07:44Z ThisCarthing 17456337 Created page with "Hintergrund" wikitext text/x-wiki <languages /> {{Wikimedia engineering project information | name = Structured Data Across Wikimedia | description = A project to structure content on wikitext pages in a way that will be machine-recognizable and -relatable, to make reading, editing, and searching easier and more accessible across projects and on the Internet. | start = 2021-02-01 | end = 2023-06-30 | group = | lead = | team =<br/> * [[User:SWakiyama (WMF)|Shari Wakiyama]], Director of Product Management * Alexandra Ugolnikova - Product Manager * [[User:CBogen (WMF)|Carly Bogen]] - Program Manager * [[User:CParle (WMF)|Cormac Parle]] - Software Engineer * [[User:Etonkovidova|Elena Tonkovidova]] - Test Engineer * Mark Holmquist - Engineering Manager * Matthias Mullie - Software Engineer * [[User:MFossati (WMF)|Marco Fossati]] - Software Engineer * Sneha Patel - UX Designer * [[User:Seddon (WMF)|Joseph Seddon]] - Software Engineer * Connie Chen - Data Scientist * [[User:Sannita (WMF)|Luca Martinelli]] - Community Relations Specialist | Phabricator = Structured-Data-Backlog | updates = | progress = | previous = | next = | projectpage = | display = {{{display|}}} }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''Structured Data Across Wikimedia''' ('''SDAW''') is a project that will help us to structure content on wikitext pages in a way that will be machine-recognizable and -relatable, to make reading, editing, and searching easier and more accessible across projects and on the Internet. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It will help users associate contents between Wikimedia projects, help readers dive deeper in the Wikimedia knowledge ecosystem, and help contributors disseminate information across projects and beyond them in a Wikidata-like way. The project will also provide a venue for experimentation with computer-aided editing tools to make editing easier and more accessible to more editors around the world. </div> == Hintergrund == <div lang="en" dir="ltr" class="mw-content-ltr"> This project is a follow-up to similar development that was completed on Commons, as part of the previous [[Structured Data on Commons|Structured Data on Commons]] (SDC) grant, and will be partially funded by a three year grant from the Sloan Foundation. Work on SDC made us aware of the need for more advanced metadata for all content and APIs to provide better search results, which would make in turn content more accessible, discoverable, translatable and usable for other needs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The project has three high level goals: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">To '''allow machines to recognize Wikimedia content and to suggest relationships to other Wikimedia content'''. We are exploring this first via the [[Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions|image suggestion project]].</span> # <span lang="en" dir="ltr" class="mw-content-ltr">To '''design a way to structure articles and pages to enable new content formats''' – such as content served in smaller, easily digestible pieces that is more accessible for readers to use and share.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">To '''give Wikimedia users a more inviting, more efficient way to search and find content''', building on [[:commons:Commons:Structured data/Media search|MediaSearch]], and exploring new ways to improve search across Wikipedias using Structured Data.</span> == Was sich ändert == {{See also|Special:MyLanguage/Structured Data Across Wikimedia/Potential use cases}} <span lang="en" dir="ltr" class="mw-content-ltr">The goal of the project is to design and prototype a new system that aims to be flexible enough to serve all the kinds of metadata we might need to support in the near future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We identified three main projects that we will develop, as part of our work:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">''Image suggestion'', a feature for experienced users to help illustrate Wikipedia articles;</span> # <span lang="en" dir="ltr" class="mw-content-ltr">''Sectional metadata'', also known as ''Section topics'', in order to describe what a section of a Wikipedia article is about;</span> # <span lang="en" dir="ltr" class="mw-content-ltr">''Search improvements'', that will use structured content to give users a more inviting and efficient way to search and find content on the Wikipedias.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Image suggestion</span> === {{See also|Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions}} <span lang="en" dir="ltr" class="mw-content-ltr">The Image Suggestion UI aims at developing systems for structured data across all Wikimedia projects.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This work will build on the work already begun as part of the [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|“Add an image” structured task project]]. However, its focus will be shifted towards improving the processes for experienced contributors. In particular, we will target users who have edited or watched a particular article or set of articles, since they are likely to be experts in the topic and to have interest in seeing that article(s) improve.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Section topics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">The Section Topics project will identify sections in an article and create topics accordingly for those sections, drawing on several elements:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">an algorithm that detects Wikidata items based on the section’s blue links (which will be developed in partnership with the Structured Data, Research, Machine Learning, and Data Platform teams);</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the ability to automatically identify sections in an article (which will be developed in partnership with the Structured Data and Data Platform teams);</span> * <span lang="en" dir="ltr" class="mw-content-ltr">section-level image suggestions, which will use the blue-links algorithm and section identification infrastructure above, and be delivered both via the newcomer experience and via notifications for experienced contributors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This last point will build upon the [[Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions|prior image suggestions work]] and will be developed in partnership with the Structured Data, Machine Learning, Data Platform, Research, Search, and Growth teams.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These elements will not change, nor impact the current editing experience for users. All these activities will be automatic and will not depend on any action from users who edit an article. Currently, this project is still in the investigating phase, and there are still aspects that may require further investigation and/or feedback from users.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Based on the viability of those options, the project also aims at:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">using section topics to improve our SEO reach with outside search engines (in partnership with the Web team)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">establishing partnerships with the larger Wikimedia community to show the impact of our new tools (in partnership with the Structured Data, Growth, and Community Programs (GLAM/Campaigns) teams).</span> === Suchverbesserungen === {{See also|Special:MyLanguage/Structured Data Across Wikimedia/Search Improvements}} <span lang="en" dir="ltr" class="mw-content-ltr">The Search Improvements project will use structured content to give users a more inviting and more efficient way to search and find content on the Wikipedias. By improving [[Special:Search|Special:Search]], we want to enable users to find the information they are looking for, or that they may not have noticed, or previously come across through existing search.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We aim to identify and define incremental “special search” improvements that use structured content, to assist users in finding the content they are looking for, especially in those language wikis that have fewer articles.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">What do we ''not'' want to do?</span> === # <span lang="en" dir="ltr" class="mw-content-ltr">Leave users out of the process</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Overwhelm users with too much new content to moderate</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add any additional bias to Wikimedia projects</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add additional vectors for vandalism</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Introduce too much complexity into our systems</span> == Status-Updates == ==={{date|2022|06}} === * <span lang="en" dir="ltr" class="mw-content-ltr">The [[:File:Sloan Grant Report June 2022.pdf|second year report]] for Structured Data Across Wikimedia has been published.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">DPLA was awarded SDAW grant funding to drive the reuse of described and attributed images. You can read more about it at DPLA's [[:commons:Commons:Digital Public Library of America/2022 SDAW project|2022 SDAW project announcement]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">A general consultation about [[Special:MyLanguage/Structured Data Across Wikimedia/Search Improvements|Search improvements]] is launched.</span> === {{date|2022|03}} === * <span lang="en" dir="ltr" class="mw-content-ltr">Project pages updated to reflect the new current status of the initiative and the three main projects to be developed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Indonesian Wikipedia joins in as the third tester community.</span> === {{date|2022|02}} === * <span lang="en" dir="ltr" class="mw-content-ltr">Establishing contact with Portuguese and Russian Wikipedia community as first tester communities for [[Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions|Image Suggestions]].</span> === {{date|2021|11}} === * <span lang="en" dir="ltr" class="mw-content-ltr">Project is moving to a first test stage, that is experimenting with the use of notifications to alert users of [[Structured Data Across Wikimedia/Image Suggestions#What we want to do|potential useful images]] for Wikipedia articles.</span> === Mai-August 2021 === * <span lang="en" dir="ltr" class="mw-content-ltr">Looking for feedback about the [[Structured Data Across Wikimedia/Image Suggestions/2021-02|Image Suggestions project]], through individual invitations and a [[Structured Data Across Wikimedia/Image Suggestions/Feedback August 2021|month-long RfC]] specifically targeted to 4 Wikipedias + Commons</span> === {{date|2021|2}} === * <span lang="en" dir="ltr" class="mw-content-ltr">Looking for feedback about [[#Feedback|these ideas]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Working on rough wireframes and mockups to help explore these ideas.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Exploring infrastructure to support this work via the Technical Decision Making Forum process. See {{Phabricator|T274181}}.</span> === Zweites Halbjahr 2020 === * <span lang="en" dir="ltr" class="mw-content-ltr">Building [[c:Special:MediaSearch|MediaSearch]] on Commons.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Structured Data Across Wikimedia/MediaSearch test|MediaSearch A/B test]] - conducted between 10 and 17 September 2020.</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Feedback</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Project feedback is and will always be welcome. We are especially interested in your ideas about the extent to which you want to keep the “human-in-the-loop” throughout the topical metadata creation process. We are looking forward to hearing from you about the following open questions:</span> # [[Topic:W4dlr38iqmnnswci|<span lang="en" dir="ltr" class="mw-content-ltr">Your expectations about the project</span>]] ## <span lang="en" dir="ltr" class="mw-content-ltr">What do users expect from this project? What are the necessary actions to be addressed?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">How do you envision this metadata being used? Can you think of ways it would aid in your workflows?</span> # [[Topic:W4dm6tt474srmqzg|<span lang="en" dir="ltr" class="mw-content-ltr">Metadata moderation</span>]] ## <span lang="en" dir="ltr" class="mw-content-ltr">Is moderation necessary to avoid vandalism and/or bias?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">If moderation is necessary, how can it be effectively managed?</span> # [[Topic:W4dmvmdd5w1f2iyx|<span lang="en" dir="ltr" class="mw-content-ltr">Adding and confirming metadata</span>]] ## <span lang="en" dir="ltr" class="mw-content-ltr">Do users want to be able to ''approve or reject'' metadata suggested by the automated system?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Do users want to be able to ''add additional metadata'' beyond what is suggested by the automated system?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Do you think it may just be sufficient for users to have the opportunity to send feedback with suggestions on how to improve the machine generated metadata, when necessary?</span> # [[Topic:W4dmxixr6jqhwcid|<span lang="en" dir="ltr" class="mw-content-ltr">Privileges for visualising and editing</span>]] ## <span lang="en" dir="ltr" class="mw-content-ltr">Do we want metadata to be ''visible'' for all users or only for certain classes of users?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Do we want metadata to be ''editable'' for all users or only for certain classes of users?</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, more specific feedback about related projects can generally be left on the projects' talk pages:</span> * [[c:Commons talk:Structured data/Media search|<span lang="en" dir="ltr" class="mw-content-ltr">MediaSearch on Commons</span>]] * [[Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions|<span lang="en" dir="ltr" class="mw-content-ltr">Image Suggestions</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Funding</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Partial funding for this work is provided by a [[c:File:2020 Structured Data Across Wikimedia proposal.pdf|follow-up restricted grant]] from the [[d:Q1200258|Alfred P. Sloan Foundation]], to further the work done by the first round of funding to develop [[c:Commons:Structured data/Sloan Grant|Structured Data on Commons]].</span> [[Category:Structured Data Across Wikimedia|*]] 7dfomfve5vk33m4o11mg8lowpqcvynr 5386798 5386796 2022-07-28T19:07:56Z ThisCarthing 17456337 Created page with "Bildvorschlag" wikitext text/x-wiki <languages /> {{Wikimedia engineering project information | name = Structured Data Across Wikimedia | description = A project to structure content on wikitext pages in a way that will be machine-recognizable and -relatable, to make reading, editing, and searching easier and more accessible across projects and on the Internet. | start = 2021-02-01 | end = 2023-06-30 | group = | lead = | team =<br/> * [[User:SWakiyama (WMF)|Shari Wakiyama]], Director of Product Management * Alexandra Ugolnikova - Product Manager * [[User:CBogen (WMF)|Carly Bogen]] - Program Manager * [[User:CParle (WMF)|Cormac Parle]] - Software Engineer * [[User:Etonkovidova|Elena Tonkovidova]] - Test Engineer * Mark Holmquist - Engineering Manager * Matthias Mullie - Software Engineer * [[User:MFossati (WMF)|Marco Fossati]] - Software Engineer * Sneha Patel - UX Designer * [[User:Seddon (WMF)|Joseph Seddon]] - Software Engineer * Connie Chen - Data Scientist * [[User:Sannita (WMF)|Luca Martinelli]] - Community Relations Specialist | Phabricator = Structured-Data-Backlog | updates = | progress = | previous = | next = | projectpage = | display = {{{display|}}} }} <div lang="en" dir="ltr" class="mw-content-ltr"> '''Structured Data Across Wikimedia''' ('''SDAW''') is a project that will help us to structure content on wikitext pages in a way that will be machine-recognizable and -relatable, to make reading, editing, and searching easier and more accessible across projects and on the Internet. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It will help users associate contents between Wikimedia projects, help readers dive deeper in the Wikimedia knowledge ecosystem, and help contributors disseminate information across projects and beyond them in a Wikidata-like way. The project will also provide a venue for experimentation with computer-aided editing tools to make editing easier and more accessible to more editors around the world. </div> == Hintergrund == <div lang="en" dir="ltr" class="mw-content-ltr"> This project is a follow-up to similar development that was completed on Commons, as part of the previous [[Structured Data on Commons|Structured Data on Commons]] (SDC) grant, and will be partially funded by a three year grant from the Sloan Foundation. Work on SDC made us aware of the need for more advanced metadata for all content and APIs to provide better search results, which would make in turn content more accessible, discoverable, translatable and usable for other needs. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The project has three high level goals: </div> # <span lang="en" dir="ltr" class="mw-content-ltr">To '''allow machines to recognize Wikimedia content and to suggest relationships to other Wikimedia content'''. We are exploring this first via the [[Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions|image suggestion project]].</span> # <span lang="en" dir="ltr" class="mw-content-ltr">To '''design a way to structure articles and pages to enable new content formats''' – such as content served in smaller, easily digestible pieces that is more accessible for readers to use and share.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">To '''give Wikimedia users a more inviting, more efficient way to search and find content''', building on [[:commons:Commons:Structured data/Media search|MediaSearch]], and exploring new ways to improve search across Wikipedias using Structured Data.</span> == Was sich ändert == {{See also|Special:MyLanguage/Structured Data Across Wikimedia/Potential use cases}} <span lang="en" dir="ltr" class="mw-content-ltr">The goal of the project is to design and prototype a new system that aims to be flexible enough to serve all the kinds of metadata we might need to support in the near future.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We identified three main projects that we will develop, as part of our work:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">''Image suggestion'', a feature for experienced users to help illustrate Wikipedia articles;</span> # <span lang="en" dir="ltr" class="mw-content-ltr">''Sectional metadata'', also known as ''Section topics'', in order to describe what a section of a Wikipedia article is about;</span> # <span lang="en" dir="ltr" class="mw-content-ltr">''Search improvements'', that will use structured content to give users a more inviting and efficient way to search and find content on the Wikipedias.</span> === Bildvorschlag === {{See also|Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions}} <span lang="en" dir="ltr" class="mw-content-ltr">The Image Suggestion UI aims at developing systems for structured data across all Wikimedia projects.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This work will build on the work already begun as part of the [[Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add an image|“Add an image” structured task project]]. However, its focus will be shifted towards improving the processes for experienced contributors. In particular, we will target users who have edited or watched a particular article or set of articles, since they are likely to be experts in the topic and to have interest in seeing that article(s) improve.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Section topics</span> === <span lang="en" dir="ltr" class="mw-content-ltr">The Section Topics project will identify sections in an article and create topics accordingly for those sections, drawing on several elements:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">an algorithm that detects Wikidata items based on the section’s blue links (which will be developed in partnership with the Structured Data, Research, Machine Learning, and Data Platform teams);</span> * <span lang="en" dir="ltr" class="mw-content-ltr">the ability to automatically identify sections in an article (which will be developed in partnership with the Structured Data and Data Platform teams);</span> * <span lang="en" dir="ltr" class="mw-content-ltr">section-level image suggestions, which will use the blue-links algorithm and section identification infrastructure above, and be delivered both via the newcomer experience and via notifications for experienced contributors.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This last point will build upon the [[Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions|prior image suggestions work]] and will be developed in partnership with the Structured Data, Machine Learning, Data Platform, Research, Search, and Growth teams.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These elements will not change, nor impact the current editing experience for users. All these activities will be automatic and will not depend on any action from users who edit an article. Currently, this project is still in the investigating phase, and there are still aspects that may require further investigation and/or feedback from users.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Based on the viability of those options, the project also aims at:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">using section topics to improve our SEO reach with outside search engines (in partnership with the Web team)</span> * <span lang="en" dir="ltr" class="mw-content-ltr">establishing partnerships with the larger Wikimedia community to show the impact of our new tools (in partnership with the Structured Data, Growth, and Community Programs (GLAM/Campaigns) teams).</span> === Suchverbesserungen === {{See also|Special:MyLanguage/Structured Data Across Wikimedia/Search Improvements}} <span lang="en" dir="ltr" class="mw-content-ltr">The Search Improvements project will use structured content to give users a more inviting and more efficient way to search and find content on the Wikipedias. By improving [[Special:Search|Special:Search]], we want to enable users to find the information they are looking for, or that they may not have noticed, or previously come across through existing search.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We aim to identify and define incremental “special search” improvements that use structured content, to assist users in finding the content they are looking for, especially in those language wikis that have fewer articles.</span> === <span lang="en" dir="ltr" class="mw-content-ltr">What do we ''not'' want to do?</span> === # <span lang="en" dir="ltr" class="mw-content-ltr">Leave users out of the process</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Overwhelm users with too much new content to moderate</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add any additional bias to Wikimedia projects</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Add additional vectors for vandalism</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Introduce too much complexity into our systems</span> == Status-Updates == ==={{date|2022|06}} === * <span lang="en" dir="ltr" class="mw-content-ltr">The [[:File:Sloan Grant Report June 2022.pdf|second year report]] for Structured Data Across Wikimedia has been published.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">DPLA was awarded SDAW grant funding to drive the reuse of described and attributed images. You can read more about it at DPLA's [[:commons:Commons:Digital Public Library of America/2022 SDAW project|2022 SDAW project announcement]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">A general consultation about [[Special:MyLanguage/Structured Data Across Wikimedia/Search Improvements|Search improvements]] is launched.</span> === {{date|2022|03}} === * <span lang="en" dir="ltr" class="mw-content-ltr">Project pages updated to reflect the new current status of the initiative and the three main projects to be developed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Indonesian Wikipedia joins in as the third tester community.</span> === {{date|2022|02}} === * <span lang="en" dir="ltr" class="mw-content-ltr">Establishing contact with Portuguese and Russian Wikipedia community as first tester communities for [[Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions|Image Suggestions]].</span> === {{date|2021|11}} === * <span lang="en" dir="ltr" class="mw-content-ltr">Project is moving to a first test stage, that is experimenting with the use of notifications to alert users of [[Structured Data Across Wikimedia/Image Suggestions#What we want to do|potential useful images]] for Wikipedia articles.</span> === Mai-August 2021 === * <span lang="en" dir="ltr" class="mw-content-ltr">Looking for feedback about the [[Structured Data Across Wikimedia/Image Suggestions/2021-02|Image Suggestions project]], through individual invitations and a [[Structured Data Across Wikimedia/Image Suggestions/Feedback August 2021|month-long RfC]] specifically targeted to 4 Wikipedias + Commons</span> === {{date|2021|2}} === * <span lang="en" dir="ltr" class="mw-content-ltr">Looking for feedback about [[#Feedback|these ideas]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Working on rough wireframes and mockups to help explore these ideas.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Exploring infrastructure to support this work via the Technical Decision Making Forum process. See {{Phabricator|T274181}}.</span> === Zweites Halbjahr 2020 === * <span lang="en" dir="ltr" class="mw-content-ltr">Building [[c:Special:MediaSearch|MediaSearch]] on Commons.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Structured Data Across Wikimedia/MediaSearch test|MediaSearch A/B test]] - conducted between 10 and 17 September 2020.</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Feedback</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Project feedback is and will always be welcome. We are especially interested in your ideas about the extent to which you want to keep the “human-in-the-loop” throughout the topical metadata creation process. We are looking forward to hearing from you about the following open questions:</span> # [[Topic:W4dlr38iqmnnswci|<span lang="en" dir="ltr" class="mw-content-ltr">Your expectations about the project</span>]] ## <span lang="en" dir="ltr" class="mw-content-ltr">What do users expect from this project? What are the necessary actions to be addressed?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">How do you envision this metadata being used? Can you think of ways it would aid in your workflows?</span> # [[Topic:W4dm6tt474srmqzg|<span lang="en" dir="ltr" class="mw-content-ltr">Metadata moderation</span>]] ## <span lang="en" dir="ltr" class="mw-content-ltr">Is moderation necessary to avoid vandalism and/or bias?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">If moderation is necessary, how can it be effectively managed?</span> # [[Topic:W4dmvmdd5w1f2iyx|<span lang="en" dir="ltr" class="mw-content-ltr">Adding and confirming metadata</span>]] ## <span lang="en" dir="ltr" class="mw-content-ltr">Do users want to be able to ''approve or reject'' metadata suggested by the automated system?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Do users want to be able to ''add additional metadata'' beyond what is suggested by the automated system?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Do you think it may just be sufficient for users to have the opportunity to send feedback with suggestions on how to improve the machine generated metadata, when necessary?</span> # [[Topic:W4dmxixr6jqhwcid|<span lang="en" dir="ltr" class="mw-content-ltr">Privileges for visualising and editing</span>]] ## <span lang="en" dir="ltr" class="mw-content-ltr">Do we want metadata to be ''visible'' for all users or only for certain classes of users?</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Do we want metadata to be ''editable'' for all users or only for certain classes of users?</span> <span lang="en" dir="ltr" class="mw-content-ltr">Also, more specific feedback about related projects can generally be left on the projects' talk pages:</span> * [[c:Commons talk:Structured data/Media search|<span lang="en" dir="ltr" class="mw-content-ltr">MediaSearch on Commons</span>]] * [[Special:MyLanguage/Structured Data Across Wikimedia/Image Suggestions|<span lang="en" dir="ltr" class="mw-content-ltr">Image Suggestions</span>]] == <span lang="en" dir="ltr" class="mw-content-ltr">Funding</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Partial funding for this work is provided by a [[c:File:2020 Structured Data Across Wikimedia proposal.pdf|follow-up restricted grant]] from the [[d:Q1200258|Alfred P. Sloan Foundation]], to further the work done by the first round of funding to develop [[c:Commons:Structured data/Sloan Grant|Structured Data on Commons]].</span> [[Category:Structured Data Across Wikimedia|*]] mskarcrg5vy1za9xjdfgeg3sgxxi651 Extension:EventLogging/de 102 1554348 5387144 5381727 2022-07-28T21:07:41Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides a framework for logging analytics events</span> |version = Laufende Aktualisierungen |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} <div lang="en" dir="ltr" class="mw-content-ltr"> The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. </div> == Funktionen == * <span lang="en" dir="ltr" class="mw-content-ltr">EventLogging supports client-side logging from JavaScript and server-side logging from PHP.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Logging behavior can be dynamically configured using {{ll|Extension:EventStreamConfig}}.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The extension does not include any back-end code for transporting, parsing, or loading these events.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A separate service, [[wikitech:Event Platform/EventGate|EventGate]], implements this functionality and deals with inserting events into Kafka.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The details of these components are specific to Wikimedia Foundation's configuration.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == EventLogging at Wikimedia == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Wikimedia Foundation uses the EventLogging extension as part of a [[wikitech:Analytics/Systems/EventLogging|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[m:Special:MyLanguage/Privacy policy|privacy policy]] and [[m:Special:MyLanguage/Data retention guidelines|data retention guidelines]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This page is about general use of the EventLogging extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Wikimedia Foundation uses EventLogging with WMF specific backend components and [https://schema.wikimedia.org/#!/ schema repositories].</span> <span lang="en" dir="ltr" class="mw-content-ltr">For Wikimedia specific and maintained documentation, see [[wikitech:Analytics/Systems/EventLogging]] and [[wikitech:Event Platform]].</span> ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Configuring the schema location === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, the extension will look for schemas on [[m:Special:MyLanguage/Meta-Wiki|Meta-Wiki]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The relevant default settings are:</span> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</span> <span lang="en" dir="ltr" class="mw-content-ltr">E.g. to use the <code>Schema</code> namespace of the local wiki, set</span> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">(and ensure the user account that will create the schemas is [[Special:MyLanguage/Manual:Autoconfirmed users|autoconfirmed]]).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Logging events using EventLogging == </div> * {{ll|Extension:EventLogging/Guide}} - <span lang="en" dir="ltr" class="mw-content-ltr">to developing and deploying EventLogging schemas, and more</span> * {{ll|Extension:EventLogging/Programming}} - <span lang="en" dir="ltr" class="mw-content-ltr">tips and suggestions for developers writing code to log events</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Developing the EventLogging extension == </div> === Entwickler-Einrichtung === <div lang="en" dir="ltr" class="mw-content-ltr"> As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. </div> ==== Mit Docker ==== ''Siehe {{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}'' ==== Mit mediawiki-vagrant ==== <span lang="en" dir="ltr" class="mw-content-ltr">If you develop using mediawiki-vagrant, everything you need is encapsulated in the <code>eventlogging</code> role.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable it, run:</span> <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> ==== Für JavaScript-Entwicklung ==== <span lang="en" dir="ltr" class="mw-content-ltr">If working on the JavaScript client, you'll need to install dependencies with <code>npm install</code> from the folder you're developing in.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then you can use <code>npm test</code> to run ESLint for example.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The "How to run tests" section below points out how to see JavaScript test results.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> When adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered. </div> === Wie man Tests ausführt === Es gibt PHP-Tests, Python-Tests und JavaScript-Tests. Um JavaScript-Tests auszuführen, besuche Special:JavaScriptTest/qunit auf deinem Entwicklungswiki. (Siehe {{ll|Manual:JavaScript unit testing}}.) Um PHP-Tests auszuführen, verwenden wir PHPUnit. Stelle sicher, dass es installiert ist, dann: <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] p2j7ruqlh1t0y4nw50x4dvhyxqi51h3 Extension:EasyTimeline/installation/de 102 1556344 5386863 5351034 2022-07-28T19:31:20Z ThisCarthing 17456337 Created page with "== Ploticus herunterladen ==" wikitext text/x-wiki <languages/> <div lang="en" dir="ltr" class="mw-content-ltr"> This section deals with issues on how to activate {{ll|Extension:EasyTimeline|EasyTimeline}} in other MediaWiki installations. </div> <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline is an extension to the MediaWiki software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However you need to do a few things in order to activate it.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">When you run MediaWiki on another platform than Linux, the following may not apply or be incomplete.</span>}} == Ploticus herunterladen == <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline uses the open source program [http://ploticus.sourceforge.net/doc/welcome.html Ploticus], which is not included in the MediaWiki installation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Download the proper version for your OS:</span> http://ploticus.sourceforge.net/doc/download.html <span lang="en" dir="ltr" class="mw-content-ltr">Or, if you are on Ubuntu with shell access, you can simply do</span> <code>sudo apt install ploticus</code> <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline expects the Ploticus executable to be located at <code>/usr/bin/ploticus</code>, if it is not just make sure it's executable and put the appropriate location in <code>$wgTimelinePloticusCommand</code> described below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Download PHP/PERL scripts== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ''EasyTimeline.pl'' is the actual plug-in, written in perl. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ''Timeline.php'' is the MediaWiki php wrapper that invokes the perl script with proper arguments, and feeds generated image and image map (if applicable) to the html output. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download it from [[Special:ExtensionDistributor/timeline]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ...or if you have shell access, go to your extensions directory, and type ... </div> <code>git clone -b REL1_28 https://gerrit.wikimedia.org/r/mediawiki/extensions/timeline.git</code> <span lang="en" dir="ltr" class="mw-content-ltr">Do not use the EasyTimeline.pl script, or its compiled version, from the authors support page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These are meant for offline usage (= outside WikiMedia).</span> == Schriftarten installieren == <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline by default uses the font <code>FreeSans.ttf</code>, which can be downloaded from [https://www.gnu.org/software/freefont/ GNU FreeFont]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or, if you are on Ubuntu with shell access, you can simply do </div> <nowiki>sudo apt install fonts-freefont-ttf</nowiki> <div lang="en" dir="ltr" class="mw-content-ltr"> To make sure EasyTimeline can find <code>FreeSans.ttf</code>, set <code>GDFONTPATH</code>, described below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Configure MediaWiki== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Load extension === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Add the following to you {{ll|Manual:LocalSettings.php|LocalSettings.php}} file: </div> <syntaxhighlight lang="php"> wfLoadExtension( "timeline" ); // Add EasyTimeline extension </syntaxhighlight> === Ploticus === <span lang="en" dir="ltr" class="mw-content-ltr">On RHEL/CentOS, for instance, <code>/usr/bin/pl</code> is the ploticus executable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the ploticus location on your system does not match the defaults listed at the top of <code>extensions/timeline/extension.json</code>, you will need to explicitly set the paths, e.g.</span> Add the following to you '''{{ll|Manual:LocalSettings.php|LocalSettings.php}}''' file: <syntaxhighlight lang="php"> $wgTimelinePloticusCommand = "/usr/bin/pl"; // alternate location of ploticus, depending on OS </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Alternatively you may create symlinks to the alternate location. </div> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The extension's default settings for ploticus and perl:</span>}} <syntaxhighlight lang="php"> $wgTimelinePloticusCommand = "/usr/bin/ploticus"; $wgTimelinePerlCommand = "/usr/bin/perl"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Font=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Add the following to your '''{{ll|Manual:LocalSettings.php|LocalSettings.php}}''' file to make sure EasyTimeline finds the font: </div> <syntaxhighlight lang="php"> putenv("GDFONTPATH=/usr/share/fonts/truetype/freefont"); // Directory containing FreeSans.ttf. </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> If <code>FreeSans.ttf</code> is not available, instead set: </div> <syntaxhighlight lang="php"> $wgTimelineFontFile = 'ascii'; // Use the internal Ploticus font </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Image directory=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Create a directory for timeline images and ensure it's read/writable by your web server's user.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example if your web server user is "www-data", you would do:</span> <syntaxhighlight lang=bash> cd (wiki root directory) mkdir images/timeline chown www-data images/timeline </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Known problems== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Command Variables are Non-Transclusion=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">This problem occurs when an editor attempts to add certain words inside of the timeline which may be commands under document.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One such example word instance would be for the word '''construction'''; when used in a timeline as a dated entry, an error type occurs, rendering the word ''construction'' as a command and not a clickable link.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Charts not clickable=== </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This bug has been resolved in Ploticus 2.32</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> If that still does not resolve problems you may want to simply edit EasyTimeline.pl to: </div> <syntaxhighlight lang="perl"> $MapPNG = $true ; # switched when link or hint found </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> since it doesn't seem to apply when wikistyled links are just used on text tags and it can be annoying to figure that out. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Windows only: ''Timeline error: Executable not found. Command line was:''=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you are getting an error something like </div> Timeline error: Executable not found. Command line was: "C:/Perl/bin/perl.exe" "C:/Apache2/htdocs/wiki/extensions/timeline/EasyTimeline.pl" -i "C:/Apache2/htdocs/wiki/images/timeline/bebc64ea32049f9fe1f251640849a318" -m -P "C:/pl232win32/bin/pl.exe" -T "C:/Apache2/htdocs/wiki/images/tmp" -A "/wiki/$1" <div lang="en" dir="ltr" class="mw-content-ltr"> try going into your php file (usually at Timeline.php or EasyTimeline.php) and changing </div> <syntaxhighlight lang="php"> $ret = `{$cmdline}`; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">into</span> <syntaxhighlight lang="php"> $ret = `"{$cmdline}"`; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You may also have modified the extension directory name, which will result in the same error even with the above fix.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set timelineFile to something like this in LocalSettings.php:</span> <syntaxhighlight lang="php"> $wgTimelineTimelineFile = "$IP\\extensions\\EasyTimeline\\EasyTimeline.pl"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Windows only: set path to perl=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">When your mediawiki installation runs on Windows you will need to update Timeline.php.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set <syntaxhighlight lang="php" inline>$wgTimelinePerlCommand</syntaxhighlight> to the path to perl.exe.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The default is /usr/bin/perl, this needs to be changed for Windows.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===No texts displayed=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline contains a quick fix for unicode support.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requires free font FreeSans.ttf.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Maybe you do not have that font in a directory where Ploticus looks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You might try to find where that is on your system: see Ploticus docs online.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If you want a different font with reasonable code point coverage, try [http://dejavu-fonts.org/ DejaVu], either Sans Condensed or Sans Extra-Light depending on your preferences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Tweaking GDFONTPATH==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On a Ubuntu system with <code>ttf-freefont</code> installed, the following change to Timeline.php will set <code>GDFONTPATH</code> as required by Ploticus to render text with FreeSans.ttf. </div> <syntaxhighlight lang="php"> $cmdline = 'GDFONTPATH=/usr/share/fonts/truetype/freefont' . ' ' . wfEscapeShellArg( $wgTimelinePerlCommand, $IP . "/extensions/timeline/EasyTimeline.pl" ) . " -i " . wfEscapeShellArg( $fname ) . " -m -P " . wfEscapeShellArg( $wgTimelinePloticusCommand ) . " -T " . wfEscapeShellArg( $wgTmpDirectory ) . " -A " . wfEscapeShellArg( $wgArticlePath ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ... or simply add "<syntaxhighlight lang="php" inline>putenv("GDFONTPATH=/usr/share/fonts/truetype/freefont");</syntaxhighlight>" to your LocalSettings.php. </div> [[Category:Graphical Timelines{{#translation:}}]] emr8zdfuhvaf2tni2koyo1dy9h7opdv 5386865 5386863 2022-07-28T19:31:27Z ThisCarthing 17456337 Created page with "=== Schriftart ===" wikitext text/x-wiki <languages/> <div lang="en" dir="ltr" class="mw-content-ltr"> This section deals with issues on how to activate {{ll|Extension:EasyTimeline|EasyTimeline}} in other MediaWiki installations. </div> <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline is an extension to the MediaWiki software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However you need to do a few things in order to activate it.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">When you run MediaWiki on another platform than Linux, the following may not apply or be incomplete.</span>}} == Ploticus herunterladen == <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline uses the open source program [http://ploticus.sourceforge.net/doc/welcome.html Ploticus], which is not included in the MediaWiki installation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Download the proper version for your OS:</span> http://ploticus.sourceforge.net/doc/download.html <span lang="en" dir="ltr" class="mw-content-ltr">Or, if you are on Ubuntu with shell access, you can simply do</span> <code>sudo apt install ploticus</code> <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline expects the Ploticus executable to be located at <code>/usr/bin/ploticus</code>, if it is not just make sure it's executable and put the appropriate location in <code>$wgTimelinePloticusCommand</code> described below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Download PHP/PERL scripts== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ''EasyTimeline.pl'' is the actual plug-in, written in perl. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ''Timeline.php'' is the MediaWiki php wrapper that invokes the perl script with proper arguments, and feeds generated image and image map (if applicable) to the html output. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download it from [[Special:ExtensionDistributor/timeline]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ...or if you have shell access, go to your extensions directory, and type ... </div> <code>git clone -b REL1_28 https://gerrit.wikimedia.org/r/mediawiki/extensions/timeline.git</code> <span lang="en" dir="ltr" class="mw-content-ltr">Do not use the EasyTimeline.pl script, or its compiled version, from the authors support page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These are meant for offline usage (= outside WikiMedia).</span> == Schriftarten installieren == <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline by default uses the font <code>FreeSans.ttf</code>, which can be downloaded from [https://www.gnu.org/software/freefont/ GNU FreeFont]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or, if you are on Ubuntu with shell access, you can simply do </div> <nowiki>sudo apt install fonts-freefont-ttf</nowiki> <div lang="en" dir="ltr" class="mw-content-ltr"> To make sure EasyTimeline can find <code>FreeSans.ttf</code>, set <code>GDFONTPATH</code>, described below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Configure MediaWiki== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Load extension === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Add the following to you {{ll|Manual:LocalSettings.php|LocalSettings.php}} file: </div> <syntaxhighlight lang="php"> wfLoadExtension( "timeline" ); // Add EasyTimeline extension </syntaxhighlight> === Ploticus === <span lang="en" dir="ltr" class="mw-content-ltr">On RHEL/CentOS, for instance, <code>/usr/bin/pl</code> is the ploticus executable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the ploticus location on your system does not match the defaults listed at the top of <code>extensions/timeline/extension.json</code>, you will need to explicitly set the paths, e.g.</span> Add the following to you '''{{ll|Manual:LocalSettings.php|LocalSettings.php}}''' file: <syntaxhighlight lang="php"> $wgTimelinePloticusCommand = "/usr/bin/pl"; // alternate location of ploticus, depending on OS </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Alternatively you may create symlinks to the alternate location. </div> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The extension's default settings for ploticus and perl:</span>}} <syntaxhighlight lang="php"> $wgTimelinePloticusCommand = "/usr/bin/ploticus"; $wgTimelinePerlCommand = "/usr/bin/perl"; </syntaxhighlight> === Schriftart === <div lang="en" dir="ltr" class="mw-content-ltr"> Add the following to your '''{{ll|Manual:LocalSettings.php|LocalSettings.php}}''' file to make sure EasyTimeline finds the font: </div> <syntaxhighlight lang="php"> putenv("GDFONTPATH=/usr/share/fonts/truetype/freefont"); // Directory containing FreeSans.ttf. </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> If <code>FreeSans.ttf</code> is not available, instead set: </div> <syntaxhighlight lang="php"> $wgTimelineFontFile = 'ascii'; // Use the internal Ploticus font </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Image directory=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Create a directory for timeline images and ensure it's read/writable by your web server's user.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example if your web server user is "www-data", you would do:</span> <syntaxhighlight lang=bash> cd (wiki root directory) mkdir images/timeline chown www-data images/timeline </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Known problems== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Command Variables are Non-Transclusion=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">This problem occurs when an editor attempts to add certain words inside of the timeline which may be commands under document.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One such example word instance would be for the word '''construction'''; when used in a timeline as a dated entry, an error type occurs, rendering the word ''construction'' as a command and not a clickable link.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Charts not clickable=== </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This bug has been resolved in Ploticus 2.32</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> If that still does not resolve problems you may want to simply edit EasyTimeline.pl to: </div> <syntaxhighlight lang="perl"> $MapPNG = $true ; # switched when link or hint found </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> since it doesn't seem to apply when wikistyled links are just used on text tags and it can be annoying to figure that out. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Windows only: ''Timeline error: Executable not found. Command line was:''=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you are getting an error something like </div> Timeline error: Executable not found. Command line was: "C:/Perl/bin/perl.exe" "C:/Apache2/htdocs/wiki/extensions/timeline/EasyTimeline.pl" -i "C:/Apache2/htdocs/wiki/images/timeline/bebc64ea32049f9fe1f251640849a318" -m -P "C:/pl232win32/bin/pl.exe" -T "C:/Apache2/htdocs/wiki/images/tmp" -A "/wiki/$1" <div lang="en" dir="ltr" class="mw-content-ltr"> try going into your php file (usually at Timeline.php or EasyTimeline.php) and changing </div> <syntaxhighlight lang="php"> $ret = `{$cmdline}`; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">into</span> <syntaxhighlight lang="php"> $ret = `"{$cmdline}"`; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You may also have modified the extension directory name, which will result in the same error even with the above fix.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set timelineFile to something like this in LocalSettings.php:</span> <syntaxhighlight lang="php"> $wgTimelineTimelineFile = "$IP\\extensions\\EasyTimeline\\EasyTimeline.pl"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Windows only: set path to perl=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">When your mediawiki installation runs on Windows you will need to update Timeline.php.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set <syntaxhighlight lang="php" inline>$wgTimelinePerlCommand</syntaxhighlight> to the path to perl.exe.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The default is /usr/bin/perl, this needs to be changed for Windows.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===No texts displayed=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline contains a quick fix for unicode support.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requires free font FreeSans.ttf.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Maybe you do not have that font in a directory where Ploticus looks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You might try to find where that is on your system: see Ploticus docs online.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If you want a different font with reasonable code point coverage, try [http://dejavu-fonts.org/ DejaVu], either Sans Condensed or Sans Extra-Light depending on your preferences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Tweaking GDFONTPATH==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On a Ubuntu system with <code>ttf-freefont</code> installed, the following change to Timeline.php will set <code>GDFONTPATH</code> as required by Ploticus to render text with FreeSans.ttf. </div> <syntaxhighlight lang="php"> $cmdline = 'GDFONTPATH=/usr/share/fonts/truetype/freefont' . ' ' . wfEscapeShellArg( $wgTimelinePerlCommand, $IP . "/extensions/timeline/EasyTimeline.pl" ) . " -i " . wfEscapeShellArg( $fname ) . " -m -P " . wfEscapeShellArg( $wgTimelinePloticusCommand ) . " -T " . wfEscapeShellArg( $wgTmpDirectory ) . " -A " . wfEscapeShellArg( $wgArticlePath ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ... or simply add "<syntaxhighlight lang="php" inline>putenv("GDFONTPATH=/usr/share/fonts/truetype/freefont");</syntaxhighlight>" to your LocalSettings.php. </div> [[Category:Graphical Timelines{{#translation:}}]] nr7vqukegg9zya6h4mfynetisp8swrm 5386867 5386865 2022-07-28T19:32:31Z ThisCarthing 17456337 Created page with "== Bekannte Probleme ==" wikitext text/x-wiki <languages/> <div lang="en" dir="ltr" class="mw-content-ltr"> This section deals with issues on how to activate {{ll|Extension:EasyTimeline|EasyTimeline}} in other MediaWiki installations. </div> <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline is an extension to the MediaWiki software.</span> <span lang="en" dir="ltr" class="mw-content-ltr">However you need to do a few things in order to activate it.</span> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">When you run MediaWiki on another platform than Linux, the following may not apply or be incomplete.</span>}} == Ploticus herunterladen == <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline uses the open source program [http://ploticus.sourceforge.net/doc/welcome.html Ploticus], which is not included in the MediaWiki installation.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Download the proper version for your OS:</span> http://ploticus.sourceforge.net/doc/download.html <span lang="en" dir="ltr" class="mw-content-ltr">Or, if you are on Ubuntu with shell access, you can simply do</span> <code>sudo apt install ploticus</code> <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline expects the Ploticus executable to be located at <code>/usr/bin/ploticus</code>, if it is not just make sure it's executable and put the appropriate location in <code>$wgTimelinePloticusCommand</code> described below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Download PHP/PERL scripts== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ''EasyTimeline.pl'' is the actual plug-in, written in perl. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ''Timeline.php'' is the MediaWiki php wrapper that invokes the perl script with proper arguments, and feeds generated image and image map (if applicable) to the html output. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Download it from [[Special:ExtensionDistributor/timeline]] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ...or if you have shell access, go to your extensions directory, and type ... </div> <code>git clone -b REL1_28 https://gerrit.wikimedia.org/r/mediawiki/extensions/timeline.git</code> <span lang="en" dir="ltr" class="mw-content-ltr">Do not use the EasyTimeline.pl script, or its compiled version, from the authors support page.</span> <span lang="en" dir="ltr" class="mw-content-ltr">These are meant for offline usage (= outside WikiMedia).</span> == Schriftarten installieren == <div lang="en" dir="ltr" class="mw-content-ltr"> EasyTimeline by default uses the font <code>FreeSans.ttf</code>, which can be downloaded from [https://www.gnu.org/software/freefont/ GNU FreeFont]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Or, if you are on Ubuntu with shell access, you can simply do </div> <nowiki>sudo apt install fonts-freefont-ttf</nowiki> <div lang="en" dir="ltr" class="mw-content-ltr"> To make sure EasyTimeline can find <code>FreeSans.ttf</code>, set <code>GDFONTPATH</code>, described below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==Configure MediaWiki== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Load extension === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Add the following to you {{ll|Manual:LocalSettings.php|LocalSettings.php}} file: </div> <syntaxhighlight lang="php"> wfLoadExtension( "timeline" ); // Add EasyTimeline extension </syntaxhighlight> === Ploticus === <span lang="en" dir="ltr" class="mw-content-ltr">On RHEL/CentOS, for instance, <code>/usr/bin/pl</code> is the ploticus executable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If the ploticus location on your system does not match the defaults listed at the top of <code>extensions/timeline/extension.json</code>, you will need to explicitly set the paths, e.g.</span> Add the following to you '''{{ll|Manual:LocalSettings.php|LocalSettings.php}}''' file: <syntaxhighlight lang="php"> $wgTimelinePloticusCommand = "/usr/bin/pl"; // alternate location of ploticus, depending on OS </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Alternatively you may create symlinks to the alternate location. </div> {{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">The extension's default settings for ploticus and perl:</span>}} <syntaxhighlight lang="php"> $wgTimelinePloticusCommand = "/usr/bin/ploticus"; $wgTimelinePerlCommand = "/usr/bin/perl"; </syntaxhighlight> === Schriftart === <div lang="en" dir="ltr" class="mw-content-ltr"> Add the following to your '''{{ll|Manual:LocalSettings.php|LocalSettings.php}}''' file to make sure EasyTimeline finds the font: </div> <syntaxhighlight lang="php"> putenv("GDFONTPATH=/usr/share/fonts/truetype/freefont"); // Directory containing FreeSans.ttf. </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> If <code>FreeSans.ttf</code> is not available, instead set: </div> <syntaxhighlight lang="php"> $wgTimelineFontFile = 'ascii'; // Use the internal Ploticus font </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Image directory=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">Create a directory for timeline images and ensure it's read/writable by your web server's user.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For example if your web server user is "www-data", you would do:</span> <syntaxhighlight lang=bash> cd (wiki root directory) mkdir images/timeline chown www-data images/timeline </syntaxhighlight> == Bekannte Probleme == <div lang="en" dir="ltr" class="mw-content-ltr"> ===Command Variables are Non-Transclusion=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">This problem occurs when an editor attempts to add certain words inside of the timeline which may be commands under document.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One such example word instance would be for the word '''construction'''; when used in a timeline as a dated entry, an error type occurs, rendering the word ''construction'' as a command and not a clickable link.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Charts not clickable=== </div> {{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This bug has been resolved in Ploticus 2.32</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> If that still does not resolve problems you may want to simply edit EasyTimeline.pl to: </div> <syntaxhighlight lang="perl"> $MapPNG = $true ; # switched when link or hint found </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> since it doesn't seem to apply when wikistyled links are just used on text tags and it can be annoying to figure that out. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Windows only: ''Timeline error: Executable not found. Command line was:''=== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you are getting an error something like </div> Timeline error: Executable not found. Command line was: "C:/Perl/bin/perl.exe" "C:/Apache2/htdocs/wiki/extensions/timeline/EasyTimeline.pl" -i "C:/Apache2/htdocs/wiki/images/timeline/bebc64ea32049f9fe1f251640849a318" -m -P "C:/pl232win32/bin/pl.exe" -T "C:/Apache2/htdocs/wiki/images/tmp" -A "/wiki/$1" <div lang="en" dir="ltr" class="mw-content-ltr"> try going into your php file (usually at Timeline.php or EasyTimeline.php) and changing </div> <syntaxhighlight lang="php"> $ret = `{$cmdline}`; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">into</span> <syntaxhighlight lang="php"> $ret = `"{$cmdline}"`; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">You may also have modified the extension directory name, which will result in the same error even with the above fix.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set timelineFile to something like this in LocalSettings.php:</span> <syntaxhighlight lang="php"> $wgTimelineTimelineFile = "$IP\\extensions\\EasyTimeline\\EasyTimeline.pl"; </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ===Windows only: set path to perl=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">When your mediawiki installation runs on Windows you will need to update Timeline.php.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Set <syntaxhighlight lang="php" inline>$wgTimelinePerlCommand</syntaxhighlight> to the path to perl.exe.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The default is /usr/bin/perl, this needs to be changed for Windows.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ===No texts displayed=== </div> <span lang="en" dir="ltr" class="mw-content-ltr">EasyTimeline contains a quick fix for unicode support.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This requires free font FreeSans.ttf.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Maybe you do not have that font in a directory where Ploticus looks.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You might try to find where that is on your system: see Ploticus docs online.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> If you want a different font with reasonable code point coverage, try [http://dejavu-fonts.org/ DejaVu], either Sans Condensed or Sans Extra-Light depending on your preferences. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ====Tweaking GDFONTPATH==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> On a Ubuntu system with <code>ttf-freefont</code> installed, the following change to Timeline.php will set <code>GDFONTPATH</code> as required by Ploticus to render text with FreeSans.ttf. </div> <syntaxhighlight lang="php"> $cmdline = 'GDFONTPATH=/usr/share/fonts/truetype/freefont' . ' ' . wfEscapeShellArg( $wgTimelinePerlCommand, $IP . "/extensions/timeline/EasyTimeline.pl" ) . " -i " . wfEscapeShellArg( $fname ) . " -m -P " . wfEscapeShellArg( $wgTimelinePloticusCommand ) . " -T " . wfEscapeShellArg( $wgTmpDirectory ) . " -A " . wfEscapeShellArg( $wgArticlePath ); </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ... or simply add "<syntaxhighlight lang="php" inline>putenv("GDFONTPATH=/usr/share/fonts/truetype/freefont");</syntaxhighlight>" to your LocalSettings.php. </div> [[Category:Graphical Timelines{{#translation:}}]] rid7kfh9wgt977uupqoojzgbfyhm9k5 Extension:Graph/Demo/de 102 1556434 5386893 5384561 2022-07-28T19:39:10Z ThisCarthing 17456337 Created page with "== Mit der RESTBase-API ==" wikitext text/x-wiki <languages /> __TOC__ <span lang="en" dir="ltr" class="mw-content-ltr">This page shows some examples of what {{ll|Extension:Graph|Graph}} extension can produce.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Graphs use [http://vega.github.io/vega/ Vega grammar] ([https://github.com/vega/vega/wiki documentation]) as underlying technology.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Vega team is working on [http://vega.github.io/ other tools] to make Graphs easier to use.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For interactive graphs [https://github.com/vega/vega/wiki/Tutorial this tutorial] will explain building graphs step by step.</span> <span lang="en" dir="ltr" class="mw-content-ltr">For other graph ideas, see [http://vega.github.io/vega-editor/?spec=bar Vega examples].</span> == Graph-Vorlagen == <span lang="en" dir="ltr" class="mw-content-ltr">The easiest way to use graphs is via pre-built templates such as the [[:en:Template:Graph:Chart|Graph:Chart]] (available on many Wikipedias), or more specialized [[:en:Template:Graph:PieChart|PieChart]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Graph:Chart supports many common graph types such as line, area, and pie charts:</span> <pre style="font-size:90%;">{{Graph:Chart|width=600|height=100|xAxisTitle=X|yAxisTitle=Y |type=rect|x=1,2,3,4,5,6,7,8|y=10,12,6,14,2,10,7,9}} {{Graph:Chart|width=100|height=100|type=pie|legend=Legende |x=A,B,C,D,E,F,G,H,I|y1=100,200,150,300,100,100,150,50,200 |y2=7,8,9,8,8,9,10,9,5|showValues=}} {{Graph:Chart|width=400|height=100|xAxisTitle=X|yAxisTitle=Y |legend=Legend|type=stackedarea|x=1,2,3,4,5,6|y1=10,12,6,14,2,10 |y2=2,4,6,8,13,11|interpolate=monotone|colors=seagreen,orchid}}</pre> {{Graph:Chart|width=400|height=100|xAxisTitle=X|yAxisTitle=Y |type=rect|x=1,2,3,4,5,6,7,8|y=10,12,6,14,2,10,7,9}} {{Graph:Chart|width=100|height=100|type=pie|legend=Legende |x=A,B,C,D,E,F,G,H,I|y1=100,200,150,300,100,100,150,50,200 |y2=7,8,9,8,8,9,10,9,5|showValues=}} {{Graph:Chart|width=400|height=100|xAxisTitle=X|yAxisTitle=Y |legend=Legend|type=stackedarea|x=1,2,3,4,5,6|y1=10,12,6,14,2,10 |y2=2,4,6,8,13,11|interpolate=monotone|colors=seagreen,orchid}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Vega 2.0 interactive examples == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> See [[Extension:Graph/Interactive Graph Tutorial|tutorial]] how to build this: </div> {{Extension:Graph/Demo/HistoricalFertilityRates}} [[Extension:Graph/Demo/Dimpvis]] {{Extension:Graph/Demo/Dimpvis}} [[Extension:Graph/Demo/Airports]] {{Extension:Graph/Demo/Airports}} [[Extension:Graph/Demo/OverviewDetail]] {{Extension:Graph/Demo/OverviewDetail}} [[Extension:Graph/Demo/IndexChart]] {{Extension:Graph/Demo/IndexChart}} == Mit der RESTBase-API == <span lang="en" dir="ltr" class="mw-content-ltr">Show pageview graphs for a range of dates, using pageview analytics API.</span> Siehe {{ll|Template:Graph:PageViews}}. '''<span lang="en" dir="ltr" class="mw-content-ltr">Current page and en.wikipedia.org's main page for the last 30 days</span>''' <pre> {{Template:Graph:PageViews}} {{Template:Graph:PageViews|30|Main Page|en.wikipedia.org}} </pre> {{Template:Graph:PageViews}} {{Template:Graph:PageViews|30|Main Page|en.wikipedia.org}} <div lang="en" dir="ltr" class="mw-content-ltr"> ''' Current page and en.wikipedia main page for the last 30 days - per type''' </div> {{Extension:Graph/Demo/Pageviews2|mediawiki|{{FULLPAGENAME}}|30}} {{Extension:Graph/Demo/Pageviews2|en.wikipedia|Main Page|30}} === Mit Verwendung der MediaWiki-API === <span lang="en" dir="ltr" class="mw-content-ltr">This graph shows edit history for a wiki page.</span> Siehe {{template|Graph:PageHistory}}. {| ! Aktuelle Seite ! [[wikipedia:Albert Einstein|Albert Einstein]] von en.wikipedia.org |- | {{ Graph:PageHistory | width=500 | height=300 }} | {{ Graph:PageHistory | Albert Einstein | wiki=en.wikipedia.org | width=500 | height=300 }} |} <span lang="en" dir="ltr" class="mw-content-ltr">This graph shows the number of pages in each subcategory.</span> <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Extension:Graph/Demo/CategoryPie|graph source code]].</span> {| ! [[:Category:Extensions by category|Category:'''Extensions by category''']]. ! [[:en:Category:People|Category:'''People''']] von en.wikipedia.org |- | {{Extension:Graph/Demo/CategoryPie|Extensions by category}} | {{Extension:Graph/Demo/CategoryPie|People|en.wikipedia.org}} |} <div lang="en" dir="ltr" class="mw-content-ltr"> == Using Wikidata Query Service API == </div> Siehe [[Extension:Graph/Demo/Sparql|weitere Beispiele]]. {{Extension:Graph/Demo/Sparql/Largest disasters}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Trees == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Cartesian tree === </div> [[Extension:Graph/Demo/CartesianTree]] {{Extension:Graph/Demo/CartesianTree}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Radial tree === </div> [[Extension:Graph/Demo/RadialTree]] {{Extension:Graph/Demo/RadialTree}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Dendrogram === </div> [[Extension:Graph/Demo/Dendrogram]] {{Extension:Graph/Demo/Dendrogram}} <div lang="en" dir="ltr" class="mw-content-ltr"> ==Timeline / lifeline== </div> <graph> { "width": 800, "height": 200, "data": [ { "name": "people", "values": [ {"label":"Washington", "born":-7506057600000, "died":-5366196000000, "enter":-5701424400000, "leave":-5453884800000}, {"label":"Adams", "born":-7389766800000, "died":-4528285200000, "enter":-5453884800000, "leave":-5327740800000}, {"label":"Jefferson", "born":-7154586000000, "died":-4528285200000, "enter":-5327740800000, "leave":-5075280000000}, {"label":"Madison", "born":-6904544400000, "died":-4213184400000, "enter":-5075280000000, "leave":-4822819200000}, {"label":"Monroe", "born":-6679904400000, "died":-4370518800000, "enter":-4822819200000, "leave":-4570358400000} ] }, { "name": "events", "format": {"type":"json", "parse":{"when":"date"}}, "values": [ {"name":"Decl. of Independence", "when":"July 4, 1776"}, {"name":"U.S. Constitution", "when":"3/4/1789"}, {"name":"Louisiana Purchase", "when":"April 30, 1803"}, {"name":"Monroe Doctrine", "when":"Dec 2, 1823"} ] } ], "scales": [ { "name": "y", "type": "ordinal", "range": "height", "domain": {"data": "people", "field": "label"} }, { "name": "x", "type": "time", "range": "width", "round": true, "nice": "year", "domain": {"data": "people", "field": ["born", "died"]} } ], "axes": [ { "type": "x", "scale": "x", "properties": {"labels": {"fontSize": {"value": 18}}} } ], "marks": [ { "type": "text", "from": {"data": "events"}, "properties": { "enter": { "x": {"scale": "x", "field": "when"}, "y": {"value": -10}, "angle": {"value": -25}, "fill": {"value": "#000"}, "text": {"field": "name"}, "font": {"value": "Helvetica Neue"}, "fontSize": {"value": 20} } } }, { "type": "rect", "from": {"data": "events"}, "properties": { "enter": { "x": {"scale": "x", "field": "when"}, "y": {"value": -8}, "width": {"value": 1}, "height": {"field": {"group": "height"}, "offset": 8}, "fill": {"value": "#888"} } } }, { "type": "text", "from": {"data": "people"}, "properties": { "enter": { "x": {"scale": "x", "field": "born"}, "y": {"scale": "y", "field": "label", "offset": -3}, "fill": {"value": "#000"}, "text": {"field": "label"}, "font": {"value": "Helvetica Neue"}, "fontSize": {"value": 20} } } }, { "type": "rect", "from": {"data": "people"}, "properties": { "enter": { "x": {"scale": "x", "field": "born"}, "x2": {"scale": "x", "field": "died"}, "y": {"scale": "y", "field": "label"}, "height": {"value": 2}, "fill": {"value": "#557"} } } }, { "type": "rect", "from": {"data": "people"}, "properties": { "enter": { "x": {"scale": "x", "field": "enter"}, "x2": {"scale": "x", "field": "leave"}, "y": {"scale": "y", "field": "label", "offset":-1}, "height": {"value": 4}, "fill": {"value": "#e44"} } } } ] }</graph> <div lang="en" dir="ltr" class="mw-content-ltr"> == More maps examples == </div> <span lang="en" dir="ltr" class="mw-content-ltr">This transcludes the page [[Extension:Graph/Demo/Map]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">The {{tag|graph|open}} tag's JSON data on that page specifies that its <code>countries</code> data comes from a separate URL, [[Extension:Graph/Demo/RawData:WorldMap-iso2-json]], that contains map data in JSON format.</span> <span lang="en" dir="ltr" class="mw-content-ltr">One of the elements in the {{tag|graph|open}} tag's JSON data specifies a highlight color for each country, in the format <code>"''country-code''":"''highlight-color''"</code>:</span> <syntaxhighlight lang="javascript"> {"BR":"pink","US":"blue","CN":"red","DZ":"green","AU":"purple"} </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> Vega usually works with data in the format <syntaxhighlight lang="javascript" inline>[{"id":"country-code", "v":"highlight-color"}, ...]</syntaxhighlight>, so I created a helper Lua function to convert the data: </div> <pre>{{#invoke:Graph:Utils|expandDict|{"BR":"pink","US":"blue","CN":"red","DZ":"green","AU":"purple"} }}</pre> <div lang="en" dir="ltr" class="mw-content-ltr"> The Lua function's output is data in Vega's format: </div> {{#tag:syntaxhighlight| {{#invoke:Graph:Utils|expandDict|{"BR":"pink","US":"blue","CN":"red","DZ":"green","AU":"purple"} }} |lang=javascript }} {{Extension:Graph/Demo/Map|{{#invoke:Graph:Utils|expandDict|{"BR":"pink","US":"blue","CN":"red","DZ":"green","AU":"purple"} }} | scale=90}} <span lang="en" dir="ltr" class="mw-content-ltr">Here is a more complex data processing example: [[Extension:Graph/Demo/MapTemplate|MapTemplate]] is expanded with the data from Lua which takes it from the 2010 population distribution in the world (data based on [http://esa.un.org/wpp/ UN data]).</span> <span lang="en" dir="ltr" class="mw-content-ltr">To generate this graph, I use Lua module [[:Module:Graph:Utils|Graph:Utils]]'s function <code>parseCsv</code> to extract the year 2010 column from the [[Extension:Graph/Demo/RawData:PopulationByCountryHistoric-csv]] page (in csv format), and pass that data as the first unnamed parameter to the [[Extension:Graph/Demo/MapTemplate|MapTemplate]] graph.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Additional optional parameter specifies that it should be scaled to 80%.</span> <pre style="font-size:90%;">{{Extension:Graph/Demo/MapTemplate|{{#invoke:Graph:Utils|parseCsv|Extension:Graph/Demo/RawData:PopulationByCountryHistoric-csv|2010}}|scale=180}}</pre> {{Extension:Graph/Demo/MapTemplate|type=sqrt|colors=["#ffff65","#cb0000"]|scale=180}} <span lang="en" dir="ltr" class="mw-content-ltr">Note how the legend it wrongly positioned.</span> <span lang="en" dir="ltr" class="mw-content-ltr">That won't happen at lower scales.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Passing MediaWiki template parameters == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you're using a wiki page as a template, you can pass [[Help:Templates#Parameters|parameters]] to it, like any other MediaWiki template. </div> <span lang="en" dir="ltr" class="mw-content-ltr">As an example, the graph specification in {{ll|Extension:Graph/Demo/TemplateSample|TemplateSample}} does not hardcode a fill color for <code>marks.properties.update.fill.value</code>; instead it sets the fill color to <code><nowiki>{{{1|#ccc}}}</nowiki></code>.</span> <span lang="en" dir="ltr" class="mw-content-ltr">So if you visit that page or transclude it with no parameter, the graph fills with color <code style="background-color:#ccc">#ccc</code>; but if you transclude that page you can specify the fill color as the first template parameter.</span> <pre style="font-size:90%;"> {{Extension:Graph/Demo/TemplateSample}} {{Extension:Graph/Demo/TemplateSample | blue}} {{Extension:Graph/Demo/TemplateSample | #f00dee}} </pre> {{Extension:Graph/Demo/TemplateSample}} {{Extension:Graph/Demo/TemplateSample |blue}} {{Extension:Graph/Demo/TemplateSample |#f00dee}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Using a template for repeated graphs === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This is very useful if you have multiple graphs of the same form: you can put the verbose graph JSON and additional repetive wikitext in a template and only pass the parameters to it that vary, such as title and values. [[Talk:MediaWiki Developer Summit 2015/Lessons learned#Template_test | See a sample of this approach]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Overlaying two types of data == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Falkensee graph sample, see [[Extension:Graph/Demo/falkensee|code]]. </div> {{Extension:Graph/Demo/falkensee}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Embedded directly with {{tag|graph|open}} == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This example is a {{tag|graph|open}} tag containing the graph JSON inside the current page. </div> <graph> { "version": 2, "width": 400, "height": 200, "padding": {"top": 10, "left": 30, "bottom": 30, "right": 10}, "data": [ { "name": "table", "values": [ {"x": 1, "y": 28}, {"x": 2, "y": 55}, {"x": 3, "y": 43}, {"x": 4, "y": 91}, {"x": 5, "y": 81}, {"x": 6, "y": 53}, {"x": 7, "y": 19}, {"x": 8, "y": 87}, {"x": 9, "y": 52}, {"x": 10, "y": 48}, {"x": 11, "y": 24}, {"x": 12, "y": 49}, {"x": 13, "y": 87}, {"x": 14, "y": 66}, {"x": 15, "y": 17}, {"x": 16, "y": 27}, {"x": 17, "y": 68}, {"x": 18, "y": 16}, {"x": 19, "y": 49}, {"x": 20, "y": 15} ] } ], "scales": [ { "name": "x", "type": "ordinal", "range": "width", "domain": {"data": "table", "field": "x"} }, { "name": "y", "range": "height", "nice": true, "domain": {"data": "table", "field": "y"} } ], "axes": [ {"type": "x", "scale": "x"}, {"type": "y", "scale": "y"} ], "marks": [ { "type": "rect", "from": {"data": "table"}, "properties": { "enter": { "x": {"scale": "x", "field": "x"}, "width": {"scale": "x", "band": true, "offset": -1}, "y": {"scale": "y", "field": "y"}, "y2": {"scale": "y", "value": 0} }, "update": { "fill": {"value": "steelblue"} }, "hover": { "fill": {"value": "red"} } } } ] }</graph> <div lang="en" dir="ltr" class="mw-content-ltr"> == Horizontal bar graph == </div> [[Extension:Graph/Demo/HorizontalBarGraphSample]] {{Extension:Graph/Demo/HorizontalBarGraphSample}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Editing graph data == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Editing JSON by hand is fiddly and prone to error, so you should use a JSON checker such as [http://jsonlint.com/ JSONLint] or a JSON editor such as the [http://vega.github.io/vega-editor/ Vega Live Editor] to edit JSON before you copy and paste it into the wiki page. If the {{tag|graph|open}} tag's data is directly embedded in the page such as the example above, then if you use VisualEditor to edit the page you can directly edit graph data. </div> [[Category:Extension:Graph{{#translation:}}|Demo]] fnv8ecfthusbbu4yrujl296ayxt5dmz Talk pages project/Usability/Prototype/fr 0 1556964 5386721 5370941 2022-07-28T18:43:21Z Whatamidoing (WMF) 927293 wikitext text/x-wiki <languages /> [[File:Usability_Improvement_annotated_mockup_(desktop).jpg|alt=Une maquette montrant le nouveau design proposé pour les pages de discussion wikicode pour bureau.|center|thumb|600x600px|Maquette du nouveau design pour les pages de discussion wikicode pour '''bureau'''.]] <big>Bienvenue.</big> Cette page contient des instructions pour tester les changements de conception des pages de discussion wikicode. Ces modifications de conception font partie du {{ll|Talk pages project}} et visent à rendre les pages de discussion plus faciles à reconnaître et à utiliser. == Essayez le prototype == # Visitez cette [https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:%C3%89tat_de_New_York?setlang=fr&useskin=vector-2022 page de discussion d’article] ou cette [https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Carole?uselang=fr&useskin=vector-2022 page de discussion d’utilisateur] sur le wiki spécial des prototypes. # Trouvez la discussion qui a été modifiée le plus récemment. # Trouvez la discussion qui a eu le plus de participants. # Trouvez la discussion avec le plus de commentaires. # Revenez à la discussion que vous avez identifiée à « l’étape 4 ». Déterminez comment vous procéderiez pour faire comme suit : ## Postez une réponse à la discussion. ## Modifiez la réponse que vous avez publiée. # Ensuite, démarrez une discussion sur un nouveau sujet. # ✅ Vous êtes maintenant prêt à partager vos impressions. == Design == <gallery mode="slideshow" showthumbnails> File:Usability Improvement mockup (mobile).jpg|alt=Maquette montrant la conception proposée pour les pages de discussion wikicode mobiles.|Maquette de la conception proposée de la page de discussion wikicode destinée aux '''mobiles'''. File:Usability Improvement annotated mockup (mobile overview).jpg|alt=Maquette montrant la conception proposée pour la vue de la page de destination des pages de discussion du wikicode mobile.|Maquette annotée de la conception proposée de la page de discussion wikicode '''mobile'''. File:Usability Improvement annotated mockup (mobile discussion).jpg|alt=Maquette annotée montrant la conception proposée pour la vue de discussion individuelle des pages de discussion wikicode mobile.|Maquette annotée de la conception proposée de la page de discussion du wikicode '''mobile'''. File:Usability Improvement mockup (desktop).jpg|alt=Maquette montrant la conception proposée pour les pages de discussion wikicode de bureau.|Maquette de la conception proposée pour les pages de discussion wikicode de '''bureau'''. File:Usability Improvement annotated mockup (desktop).jpg|alt=Maquette annotée montrant la conception proposée pour les pages de discussion wikicode de bureau.|Maquette annotée de la conception proposée pour les pages de discussion wikicode pour '''bureau'''. File:DiscussionTools Usability topic container screenshot en 2022-04-29.png|alt=Détail des modifications|Modification proposée en haut des sections de discussion. File:DiscussionTools Usability page frame screenshot en 2022-04-29.png|alt=Détail des modifications|Modification proposée en haut des pages de discussion. File:DiscussionTools Usability Table of Contents screenshot en 2022-04-29.png|alt=Détail des modifications|Modification proposée à la table des matières ('''seulement pour [[Reading/Web/Desktop Improvements/Fr|Vector 2022]]'''). </gallery> == Donnez votre avis == {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |Si vous préférez, vous pouvez envoyer un courriel à la place : talkpageconsultation{{@}}wikimedia.org |} S’il vous plaît, partagez vos pensées. # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:VOTRE NOM D’UTILISATEUR}} Cliquez ici pour démarrer un nouveau sujet sur la page de discussion.] # Tapez <code>Commentaires : VOTRE NOM D’UTILISATEUR</code>. # Rédigez des réponses à ces questions. <strong>Vous pouvez écrire dans votre langue.</strong> ## Avez-vous utilisé un appareil mobile ou un ordinateur portable pour tester le prototype ? ## Qu’avez-vous trouvé d’inattendu à propos du prototype ? ## Quelles étapes de la section « Essayer le prototype » avez-vous trouvé difficiles à réaliser ? ## Qu’est-ce qui vous plaît dans le prototype ? ## Qu’est-ce que vous souhaiteriez de différent dans le prototype ? ## (Facultatif) Pouvez-vous imaginer que ce design puisse ne pas fonctionner sur certaines pages ? Si oui, veuillez partager les liens vers ces pages ? Cela serait très utile. # Cliquez sur le bouton bleu « {{int|discussiontools-replywidget-newtopic}} ». # ✅ Vous avez terminé ! Merci. n9vh5348m2cq03tcdgfm4pupykdjhjv Translations:Talk pages project/Usability/Prototype/7/fr 1198 1556979 5386720 5260296 2022-07-28T18:43:20Z Whatamidoing (WMF) 927293 wikitext text/x-wiki Visitez cette [https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:%C3%89tat_de_New_York?setlang=fr&useskin=vector-2022 page de discussion d’article] ou cette [https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Carole?uselang=fr&useskin=vector-2022 page de discussion d’utilisateur] sur le wiki spécial des prototypes. pjsqkirjp4lvqiyhwo6xawt4mnhtm27 Template:InstallationNav/sk 10 1557249 5387209 5384796 2022-07-28T21:17:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> <onlyinclude><!-- --><div style="text-align: center;"><!-- --><div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative">[[File:MediaWiki-2020-icon.svg|35px|link=]]</span> '''{{ll|Manual:Installing MediaWiki|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install MediaWiki</span>}}:''' <!-- -->{{ll|Manual:Installation requirements|2=<span lang="en" dir="ltr" class="mw-content-ltr">Requirements</span>}} &bull; <!-- -->{{ll|Download}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Extract the MediaWiki software|2=<span lang="en" dir="ltr" class="mw-content-ltr">Extract</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Upload files to your web server|2=<span lang="en" dir="ltr" class="mw-content-ltr">Upload</span>}} &bull; <!-- -->{{ll|Manual:Installing MediaWiki#Set up the database|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set up database</span>}} &bull; <!-- -->{{ll|Manual:Config script|2=<span lang="en" dir="ltr" class="mw-content-ltr">Install</span>}} &bull; <!-- -->{{ll|Manual:System administration#Configuration|2=<span lang="en" dir="ltr" class="mw-content-ltr">Configure</span>}} &bull; <!-- -->{{ll|Customization|2=Prispôsobiť}} <!-- --></div> <div style="display: inline-block; margin-top: 0.5em; padding: 0.3em 0.5em; background-color:#f9f9ff; border:1px solid #9999aa;"><!-- --><span style="position:relative;">[[File:Help-browser.svg|35px|link=]]</span> <!-- -->{{ll|FAQ#Installation and configuration|2= <span lang="en" dir="ltr" class="mw-content-ltr">FAQ</span>}} &bull; <!-- -->{{ll|Manual:Common errors and symptoms#Installation Errors|2= <span lang="en" dir="ltr" class="mw-content-ltr">Common issues</span>}} &bull; <!-- -->{{ll|Communication|2=<span lang="en" dir="ltr" class="mw-content-ltr">Get help and support</span>}}<!-- --></div> </div><p style="clear: both;"></p><!-- --></onlyinclude> [[Category:Info templates{{#translation:}}|{{PAGENAME}}]] [[Category:Navigation templates{{#translation:}}|{{PAGENAME}}]] 9ooq7x44mgwx8td1wqerotf9ry4hyun Translations:Manual:Extension registration/45/cs 1198 1560393 5386484 5257293 2022-07-28T14:36:37Z ENeRZet 17359278 wikitext text/x-wiki Pokud vaše vzhledy nejsou v $1, musíte přepsat špatně pojmenovaný $2, ''nebo použít druhý parametr $3'', abyste určili adresář, ve kterém se má vzhled najít. hhmz0iv6d2wdi5sq77f7d7d9mgrrf7u Translations:Manual:Extension registration/46/cs 1198 1560394 5386480 5257295 2022-07-28T14:34:11Z ENeRZet 17359278 wikitext text/x-wiki Toto je nutné provést před načtením jakýchkoli rozšíření nebo vzhledů z nestandardních umístění adresáře: 9137328lw9zrm3s6p2ep9tvwayxj3g3 Translations:Manual:Extension registration/143/cs 1198 1560395 5386482 5257297 2022-07-28T14:35:40Z ENeRZet 17359278 wikitext text/x-wiki Hledá $2 za $1 hx5h844dwpibn8b4h288vt9259o3x96 Translations:Manual:Extension registration/144/cs 1198 1560396 5386486 5257299 2022-07-28T14:38:49Z ENeRZet 17359278 wikitext text/x-wiki Vyhledá v $3 za oba $1 a $2 3lvq7996uwnbe4zodbfxkh24jmbde7d Extension:SocialProfile/de 102 1560938 5386954 5306305 2022-07-28T19:46:56Z ThisCarthing 17456337 Created page with "Mit $1" wikitext text/x-wiki <languages/> {{Extension |name = Social Profile |status = stable |type1 = Special |type2 = Database |type3 = Ajax |author = * [[Special:Contributions/Awrigh01~mediawikiwiki|Aaron Wright]] * {{u|UltrasonicNXT|Adam Carter}} * David Pean * {{u|Jack Phoenix}} |image = Social-tools-logo-concept-1.png |imagesize = 100px |version = 1.14 |update = Laufende Aktualisierungen (see [[social tools/MediaWiki compatibility]] |mediawiki = {{MW lts branch number}}+ |needs-updatephp = yes |download = {{WikimediaDownload|server=gerritonly}} |changelog = |description = <span lang="en" dir="ltr" class="mw-content-ltr">Incorporates multiple social features into MediaWiki for communities</span> |parameters = * $wgUserPageChoice * $wgUpdateProfileInRecentChanges * $wgUploadAvatarInRecentChanges * $wgUserProfileDisplay * $wgUserProfileThresholds * $wgUserLevels * $wgNamespacesForEditPoints * $wgUserStatsPointValues |license = GPL-2.0+ |example = [https://en.brickimedia.org/wiki/Main_Page Brickipedia, the LEGO Wiki] |rights = * avatarremove * awardsmanage * editothersprofiles * giftadmin * updatepoints * userboard-delete |hook1 = BeforePageDisplay |hook2 = CanonicalNamespaces |hook3 = LoadExtensionSchemaUpdates |hook4 = BeforeCreateEchoEvent |hook5 = EchoGetDefaultNotifiedUsers |hook6 = EchoGetBundleRules |hook7 = ParserFirstCallInit |hook8 = DifferenceEngineShowDiff |hook9 = DifferenceEngineShowDiffPage |hook10 = DifferenceEngineOldHeader |hook11 = DifferenceEngineNewHeader |hook12 = OutputPageBodyAttributes |newhook1 = UserProfileBeginLeft |newhook2 = UserProfileEndLeft |newhook3 = UserProfileBeginRight |newhook4 = UserProfileRightSideAfterActivity |newhook5 = UserProfileEndRight |newhook6 = UserProfileGetProfileHeaderLinks |newhook7 = SpecialUpdateProfile::saveSettings_pref |newhook8 = BasicProfileChanged |newhook9 = PersonalInterestsChanged |newhook10 = SpecialUpdateProfile::displayPreferencesForm |newhook11 = NewAvatarUploaded |newhook12 = NewFriendAccepted |newhook13 = NewFoeAccepted |newhook14 = RelationshipRemovedByUserID |bugzilla = SocialProfile |phabricator = SocialProfile |CheckUsageNameOverride = SocialProfile }} <span lang="en" dir="ltr" class="mw-content-ltr">The '''SocialProfile''' extension incorporates a social profile, user board, and basic profile info into MediaWiki, specifically avatars, befriending, foeing, user board, board blast, user levels rank system, awards and gifts.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The package also notifies users via email when other users request them as a friend or foe and/or sends them a message.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * For '''technical documentation''' (if you are a system administrator), see {{ll|Extension:SocialProfile/Technical documentation}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * For '''developer information''', see {{ll|Extension:SocialProfile/Developer information}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * For '''help on using SocialProfile''', see {{ll|Help:Extension:SocialProfile}} (currently a draft). </div> == Installieren == {{Note|1=<nowiki/> <div lang="en" dir="ltr" class="mw-content-ltr"> * If you use the [[Special:ExtensionDistributor|ExtensionDistributor]] to download SocialProfile, make sure that you select "master (latest development version)"; older versions are guaranteed to have lots of bugs and they are unmaintained, while trunk is always up-to-date and contains the newest features and bugfixes! </div> <span lang="en" dir="ltr" class="mw-content-ltr">See [[Special:MyLanguage/Social tools/MediaWiki compatibility|social tools' MediaWiki compatibility policy]] for more info.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * You can also use git, like so: </div> {{git clone}} }} {{ExtensionInstall |download-link = {{plain link|1={{fullurl:Special:ExtensionDistributor|extdistname=SocialProfile&extdistversion=master}}|2=Lade den Hauptzweig herunter}} |db-update = yes |custom-steps = <div lang="en" dir="ltr" class="mw-content-ltr"> *The following directories should exist under the wiki's {{wg|UploadDirectory}}: </div> ** <code>avatars/</code> — <span lang="en" dir="ltr" class="mw-content-ltr">the directory where all user-uploaded avatar images are stored</span> ** <code>awards/</code> — <span lang="en" dir="ltr" class="mw-content-ltr">system gift (award) and normal gift images will be stored here</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ** Move the directory <code>awards/</code> from <code>extensions/SocialProfile</code> into the images directory that is used in your MediaWiki installation. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This directory should be writable.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The images included in this folder by default can be used for awards if you upload them through ''Special:SystemGiftManagerLogo'', but they won't show up as "defaults" the same way avatar default images do show up.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> ** Move the directory <code>avatars</code> from <code>extensions/SocialProfile</code> into the images directory used in your MediaWiki installation. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This directory should be writable.</span> Mit <code>sudo chown -R apache:apache ./avatars/ && sudo chown -R apache:apache ./awards/</code> }} == Parser functions == * {{#avatar:Username}} - retrieves the avatar picture for the specified user. * {{#randomuserswithavatars}} * {{#newusers}} == User Options == * echo-subscriptions-web-social-rel (requires Echo extension installed) * echo-subscriptions-email-social-rel (requires Echo extension installed) == Configuration variables== <syntaxhighlight lang=php> $wgUserProfileDisplay['board'] = true; $wgUserProfileDisplay['foes'] = true; $wgUserProfileDisplay['friends'] = true; $wgUserProfileDisplay['avatar'] = true; // If set to false, disables both avatar display and upload $wgUserBoard = true; $wgFriendingEnabled = true; $wgAvatarKey = $wgDBname; $wgUserPageChoice = true; $wgUserProfileAvatarsInDiffs = true; </syntaxhighlight> ==Special Pages == * SpecialEditProfile * SpecialPopulateUserProfiles * RemoveAvatar * SpecialToggleUserPage * SpecialUpdateProfile * SpecialUploadAvatar == Anmerkungen == <div lang="en" dir="ltr" class="mw-content-ltr"> * '''Upgrading''' - If you are upgrading from SocialProfile version 1.2 or older, you'll need to create four new database tables manually: <code>gift</code>, <code>system_gift</code>, <code>user_gift</code>, <code>user_system_gift</code>. </div> <span lang="en" dir="ltr" class="mw-content-ltr">If you're upgrading from 1.3, you'll need to create <code>user_system_messages</code> database table.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> * Since {{rev|93317}}, SocialProfile's namespaces are automagically<!-- (sic!) --> registered, so you do ''not'' need to add them to {{wg|ExtraNamespaces}}. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * SocialProfile uses either {{ll|Manual:Image administration#Image thumbnailing|ImageMagick}} or PHP's built-in GD library (since {{rev|93067}}), depending on which one is available, for creating the resized avatar, award and gift image files. </div> == Known Limitations == * Avatars do not work on private wikis using [[Manual:Image_authorization|image_auth.php]] (ref: [https://phabricator.wikimedia.org/T163529 T163529]) == Fehler melden == * {{ll|Social tools/Contributing and reporting bugs}} == Bildschirmfotos == * {{ll|Extension:SocialProfile/Screenshots}} - ''<span lang="en" dir="ltr" class="mw-content-ltr">For screenshots of the extension and some very brief descriptions of the features.</span>'' {{Social tools}} {{Used by|canasta=1}} [[Category:Extensions by Fandom{{#translation:}}]] 7ipcr4xornkfnfn2gvsagnvyil6vu1k Translations:Manual:Installation guide/11/nl 1198 1570174 5387299 5283040 2022-07-28T21:59:13Z Baris6161TURK 17188421 wikitext text/x-wiki Voor image thumbnailing zijn aanvullende programma's vereist. $1 (verplicht bij VisualEditor) en andere services hebben hun eigen systeemvereisten. or9vaoxi4bpi22i9cjya3z0edc5buki Extension:NaylorAMS/de 102 1571713 5387601 5342525 2022-07-29T03:26:09Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{PluggableAuth Plugin}} {{Extension|templatemode = |name = NaylorAMS |status = stable |type1 = user identity |type2 = |hook1 = |hook2 = |newhook1 = |newhook2 = |username = |author = [[User:MyWikis-JeffreyWang|Jeffrey Wang]] for MyWikis LLC |maintainer = [https://www.mywikis.com MyWikis LLC] |description = <span lang="en" dir="ltr" class="mw-content-ltr">Allows authentication using Naylor Association Management Software (Timberlake)</span> |image = |imagesize = |version = 0.1.0 |update = |version preview = |update preview = |compatibility policy = master |mediawiki = 1.31+ |php = 7.0+ |needs-updatephp = no |composer = |table1 = |table2 = |license = GPL-2.0 |download = {{WikimediaDownload}}{{GithubDownload|mywikis|NaylorAMS|mastertarball=1}} |readme = {{git file|project=mediawiki/extensions/NaylorAMS|file=README|branch=HEAD|text=README}} |changelog = |example = |namespace = |parameters = <!-- configuration parameters, for use in LocalSettings.php --> |tags = |rights = <!-- user rights, for use with $wgGroupPermissions --> |compatibility = |phabricator = |vagrant-role = }} The '''Naylor AMS''' extension extends {{ll|Extension:PluggableAuth|PluggableAuth}} to provide authentication for organizations using [https://www.naylor.com/member-management-solutions/association-management-software/ Naylor Association Management Software] (codename Timberlake). This extension will take the username, first and last name, and email address of a user from your organization's Naylor database and create a local MediaWiki account with the same username, email, and full name if one doesn't exist; otherwise, if a user with the same username exists, it logs them back into the local MediaWiki account. == Installation == {{Note|1=This extension requires {{ll|Extension:PluggableAuth|PluggableAuth}} 5.x to be installed first.}} The PHP cURL extension is required for this MediaWiki extension. {{ExtensionInstall |download-link = [https://github.com/mywikis/NaylorAMS/archive/main.tar.gz Download] |registration = required }} == Konfigurationsparameter == For more information about these terms, please refer to the [https://masie.membershipsoftware.org/files/Naylor%20API%20Documentation.pdf Naylor AMS API documentation]. ; $wgNaylorAMS_BaseUrl : The base URL for your login system, provided by Naylor. Do not add a trailing slash at the end of the string. ('''required''') ; $wgNaylorAMS_SecurityKey : The security key provided by Naylor. ('''required''') ; $wgNaylorAMS_UsernameDenyList : An array of strings, with each string containing a local username. Used to prevent login via SSO to local-only accounts. Case sensitive; needs to follow MediaWiki username conventions. By default, the log in button says "Log in with Naylor AMS". To change the label, edit MediaWiki:Naylorams-loginbtn-text. == Haftungsausschluss == This extension is ''not'' maintained by Naylor, nor has it been sponsored by Naylor. It was written by and is maintained by [https://www.mywikis.com/ MyWikis LLC] for the purpose of serving its customers who use Naylor AMS. In addition, the extension is currently not compatible with PluggableAuth 6.0 and above. Use the latest version of PluggableAuth 5.x in the meantime. == Siehe auch == * {{ll|Extension:PluggableAuth}} * {{ll|Extension:SimpleSAMLphp}} * {{ll|Extension:LDAPAuthentication2}} {{Used by|mywikis=1}} [[Category:Extensions by MyWikis{{#translation:}}]] [[Category:PluggableAuth plugins{{#translation:}}]] ov3w512j98ki0b46u4dg4ywty4gdqbr Extension:PageAuthors/de 102 1571724 5387160 5385395 2022-07-28T21:09:03Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension | status = stable | type = parser function | username = Sophivorus | description = <span lang="en" dir="ltr" class="mw-content-ltr">Get a sensible list of page authors</span> | update = 2022-07-28 | version = 1.2 | license = GPL-3.0-or-later | mediawiki = 1.35+ | php = 7+ | download = {{WikimediaDownload}} | needs-updatephp = No | example = [https://www.appropedia.org] }} The '''PageAuthors''' extension introduces a magic word <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> that returns a list of the main page authors of a page, sorted by number of bytes added. The extension is highly configurable so you can fine-tune what counts as an author. == Installation == {{ExtensionInstall | registration = required }} == Verwendung == Simply add <code><nowiki>{{PAGEAUTHORS}}</nowiki></code> to any page and you will get a comma-separated list of the main authors of the current page, sorted by number of bytes added. See [[#Configuration|#Configuration]] to define your own criteria of what counts as an author. You can also do <code><nowiki>{{PAGEAUTHORS:Some page}}</nowiki></code> to get the list of authors for some page other than the current one. The list of authors can be further processed using [[Extension:Arrays]] or the [[Extension:Page Forms/Page Forms and templates##arraymap|#arraymap function of the PageForms extension]], for example to link to the relevant user pages. {{anchor|Configuration}} == Konfiguration == Each configuration is shown with its default value: * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerAuthor = 100;</syntaxhighlight> ― Minimum number of bytes added that each author must reach in order to be considered an author. * <syntaxhighlight lang=php inline>$wgPageAuthorsMinBytesPerEdit = 10;</syntaxhighlight> ― Minimum number of bytes that each edit must reach in order to be counted towards the author's total. Having a positive value here already means that edits that reduce content don't count, which is usually desirable because even though synthesizing and removing problematic content is often valuable, we wouldn't say that makes you an ''author'' of the existing content. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreMinorEdits = true;</syntaxhighlight> ― Whether to ignore edits marked as minor. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBlocked = true;</syntaxhighlight> ― Whether to ignore blocked users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreAnons = true;</syntaxhighlight> ― Whether to ignore anonymous users. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreBots = true;</syntaxhighlight> ― Whether to ignore bots. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSystemUsers = true;</syntaxhighlight> ― Whether to ignore system users (such as in mass imports). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreSummaryPatterns = [ '/Undo.*/', '/Revert.*/' ];</syntaxhighlight> ― Ignore edits with edit summaries that match these [https://www.php.net/manual/en/reference.pcre.pattern.syntax.php PHP regex patterns]. By default, edits with edit summaries that start with 'Undo' or 'Revert' will be ignored (these match the default edit summaries when doing a revert or a rollback in an English wiki). So for example, if some vandal blanks a page and then a user reverts it, the revert won't count towards the byte count of the user. * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreUsers = [];</syntaxhighlight> ― Ignore edits by these users (without "User:" prefix). * <syntaxhighlight lang=php inline>$wgPageAuthorsIgnoreGroups = [];</syntaxhighlight> ― Ignore edits by these groups. * <syntaxhighlight lang=php inline>$wgPageAuthorsDelimiter = ', ';</syntaxhighlight> ― Delimiter between authors. == Siehe auch == * [[Manual:$wgMaxCredits]] - A built-in option to list the latest author followed by others in order of most recent edit, in the wiki footer. * [[Extension:Contributors]] - Lists authors by edit count. This is not reliable because some users tend to do few but big edits while others tend to do many small ones. Extreme but real cases include pages where the initial author creates the entire page in a single huge edit while other later editors make multiple edits fixing trivial issues. * [[Extension:SemanticExtraSpecialProperties]] - The _EUSER property lists authors by chronological order. This is not reliable either because while it's often the case that the first few editors are the main authors, it also happens that later editors contribute significantly and may even rewrite the entire page. ep4ivzhwrqdixmfcpd5pa9bz51blfdb Help:Extension:UniversalLanguageSelector/Input methods/vai-transliteration/de 12 1574829 5386739 5292475 2022-07-28T18:52:20Z ThisCarthing 17456337 Created page with "Anmerkungen:" wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> It's possible to type in the Vai alphabet without installing any software or changing any system configuration. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This layout is based on the transliteration layout made by KeyMan, with some corrections and extensions. It is supposed to work on desktop and laptop computers, in all modern browsers with JavaScript enabled. These instructions are not intended for mobile phones and tables; on mobile devices, Vai is supported by the Gboard app. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that if squares or question marks appear instead of Vai letters, your system lacks a Vai font, and you must install one. </div> Geh wie gefolgt vor, um das Layout zu aktivieren: # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. #* <span lang="en" dir="ltr" class="mw-content-ltr">If the little keyboard icon doesn't appear, do the following: Click the gear icon near the "Languages" list in the sidebar, click "Input", click "Enable input tools", and click "Apply settings".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ꕙꔤ" appears at the top of the list, select "Vai transliteration".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ꕙꔤ" doesn't appear at the top of the list, do the following:</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click "..." at the bottom of the list. A panel will appear.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Find "ꕙꔤ" in the panel. Click it.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "Vai transliteration".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the keyboard, press Ctrl-M, or repeat the steps above. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To type every syllable, follow the instructions in the table below. If a syllable is just a vowel, type e, i, a, o, u, x, q. For syllables that begin with a consonant, type the consonant and then the vowel. If the syllable is nasalized, type a tilde (~) in the end. See the table in the end of the document for instructions for typing the special characters ꘋ, ꘌ, ꘍, ꘎, ꘏, ꘓ, ꘘ. </div> {| class="wikitable" style="font-size: xx-large" !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Start with this</span> ↓</span> ! colspan="7" |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Continue with this</span> ↓</span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Finish with this</span> ↓</span> |- ! !e !i !a !o !u !x !q ! |- ! ! colspan="5" style="text-align: end" | <span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">''alternative'' →</span></span> !O !E ! |- ! |ꔀ |ꔤ |ꕉ |ꕱ |ꖕ |ꖺ |ꗡ ! |- ! |ꔁ |ꔥ |ꕊ |ꕲ |ꖖ |ꖻ |ꗢ !~ |- !ng | | |ꕋ | | |ꖼ |ꗣ !~ |- !h |ꔂ |ꔦ |ꕌ |ꕳ |ꖗ |ꖽ |ꗤ ! |- !h | |ꔧ |ꕍ | |ꖘ |ꖾ |ꗥ !~ |- !w |ꔃ |ꔨ |ꕎ |ꕴ |ꖙ |ꖿ |ꗦ ! |- !w |ꔄ |ꔩ |ꕏ |ꕵ |ꖚ |ꗀ |ꗧ !~ |- !p |ꔅ |ꔪ |ꕐ |ꕶ |ꖛ |ꗁ |ꗨ ! |- !bh |ꔆ |ꔫ |ꕑ |ꕷ |ꖜ |ꗂ |ꗩ ! |- !b |ꔇ |ꔬ |ꕒ |ꕸ |ꖝ |ꗃ |ꗪ ! |- !mb |ꔈ |ꔭ |ꕓ |ꕹ |ꖞ |ꗄ |ꗫ ! |- !kp |ꔉ |ꔮ |ꕔ |ꕺ |ꖟ |ꗅ |ꗬ ! |- !kp | | |ꕕ | | | |ꗭ !~ |- !mgb |ꔊ |ꔯ |ꕖ |ꕻ |ꖠ |ꗆ |ꗮ ! |- !gb |ꔋ |ꔰ |ꕗ |ꕼ |ꖡ |ꗇ |ꗯ ! |- !gb | | | | | |ꗈ |ꗰ !~ |- !f |ꔌ |ꔱ |ꕘ |ꕽ |ꖢ |ꗉ |ꗱ ! |- !v |ꔍ |ꔲ |ꕙ |ꕾ |ꖣ |ꗊ |ꗲ ! |- !t |ꔎ |ꔳ |ꕚ |ꕿ |ꖤ |ꗋ |ꗳ ! |- !th |ꔏ |ꔴ |ꕛ |ꖀ |ꖥ |ꗌ |ꗴ ! |- !d |ꔐ |ꔵ |ꕜ |ꖁ |ꖦ |ꗍ |ꗵ ! |- !dh |ꔑ |ꔶ |ꕝ |ꖂ |ꖧ |ꗎ |ꗶ ! |- !l |ꔒ |ꔷ |ꕞ |ꖃ |ꖨ |ꗏ |ꗷ ! |- !r |ꔓ |ꔸ |ꕟ |ꖄ |ꖩ |ꗐ |ꗸ ! |- !dl <span style="font-size: large">''oder''</span> D |ꔔ |ꔹ |ꕠ |ꖅ |ꖪ |ꗑ |ꗹ ! |- !nd |ꔕ |ꔺ |ꕡ |ꖆ |ꖫ |ꗒ |ꗺ ! |- !s |ꔖ |ꔻ |ꕢ |ꖇ |ꖬ |ꗓ |ꗻ ! |- !sh |ꔗ |ꔼ |ꕣ |ꖈ |ꖭ |ꗔ |ꗼ ! |- !z |ꔘ |ꔽ |ꕤ |ꖉ |ꖮ |ꗕ |ꗽ ! |- !zh |ꔙ |ꔾ |ꕥ |ꖊ |ꖯ |ꗖ |ꗾ ! |- !c |ꔚ |ꔿ |ꕦ |ꖋ |ꖰ |ꗗ |ꗿ ! |- !j |ꔛ |ꕀ |ꕧ |ꖌ |ꖱ |ꗘ |ꘀ ! |- !nj |ꔜ |ꕁ |ꕨ |ꖍ |ꖲ |ꗙ |ꘁ ! |- !y |ꔝ |ꕂ |ꕩ |ꖎ |ꖳ |ꗚ |ꘂ ! |- !k |ꔞ |ꕃ |ꕪ |ꖏ |ꖴ |ꗛ |ꘃ ! |- !k | | |ꕫ | | | | !~ |- !ng |ꔟ |ꕄ |ꕬ |ꖐ |ꖵ |ꗜ |ꘄ ! |- !ngg | | | | | | |ꘅ !~ |- !g |ꔠ |ꕅ |ꕭ |ꖑ |ꖶ |ꗝ |ꘆ ! |- !g | | | | | | |ꘇ !~ |- !m |ꔡ |ꕆ |ꕮ |ꖒ |ꖷ |ꗞ |ꘈ ! |- !n |ꔢ |ꕇ |ꕯ |ꖓ |ꖸ |ꗟ |ꘉ ! |- !ny |ꔣ |ꕈ |ꕰ |ꖔ |ꖹ |ꗠ |ꘊ ! |- ! ! colspan="5" style="text-align: end" | <span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">''alternative'' →</span></span> !O !E ! |- ! !e !i !a !o !u !x !q ! |} === <span lang="en" dir="ltr" class="mw-content-ltr">Other</span> === {| class="wikitable" style="font-size: xx-large" !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin characters</span></span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai characters</span></span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Comment</span></span> |- !N |ꘋ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Syllable-final ng. Can also be typed using X.</span></span> |- != |ꘌ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai syllable lengthener.</span></span> |- !== |= |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Equals sign.</span></span> |- !, |꘍ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai comma.</span></span> |- !,, |, |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin comma.</span></span> |- !. |꘎ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai full stop.</span></span> |- !.. |. |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin full stop.</span></span> |- !! |꘎꘎ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai exclamation mark (double full stop).</span></span> |- !<nowiki>!!</nowiki> |! |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin exclamation mark.</span></span> |- !? |꘏ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai question mark.</span></span> |- !?? |? |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin question mark.</span></span> |- !FENG |ꘓ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">FEENG logogram.</span></span> |- !FAA |ꘘ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">FAA logogram.</span></span> |} Anmerkungen: * <span lang="en" dir="ltr" class="mw-content-ltr">ꘋ can also be typed using X.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The vowels ꖺ (Ɔ) and ꗡ (Ɛ) can be typed using x and q, and also using capital O and E. So typing "gbq" is equivalent to typing "gbE", and both produce the Vai character ꗯ.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">"dl" is equivalent to "D". So typing "dla" is equivalent to typing "Da", and both produce the Vai character ꕠ.</span> hx02i71wdtgebed9edw8642afdmupnf 5386741 5386739 2022-07-28T18:52:35Z ThisCarthing 17456337 Created page with "ꘋ kann auch mit X getippt werden." wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> It's possible to type in the Vai alphabet without installing any software or changing any system configuration. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This layout is based on the transliteration layout made by KeyMan, with some corrections and extensions. It is supposed to work on desktop and laptop computers, in all modern browsers with JavaScript enabled. These instructions are not intended for mobile phones and tables; on mobile devices, Vai is supported by the Gboard app. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that if squares or question marks appear instead of Vai letters, your system lacks a Vai font, and you must install one. </div> Geh wie gefolgt vor, um das Layout zu aktivieren: # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. #* <span lang="en" dir="ltr" class="mw-content-ltr">If the little keyboard icon doesn't appear, do the following: Click the gear icon near the "Languages" list in the sidebar, click "Input", click "Enable input tools", and click "Apply settings".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ꕙꔤ" appears at the top of the list, select "Vai transliteration".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ꕙꔤ" doesn't appear at the top of the list, do the following:</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click "..." at the bottom of the list. A panel will appear.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Find "ꕙꔤ" in the panel. Click it.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "Vai transliteration".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the keyboard, press Ctrl-M, or repeat the steps above. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To type every syllable, follow the instructions in the table below. If a syllable is just a vowel, type e, i, a, o, u, x, q. For syllables that begin with a consonant, type the consonant and then the vowel. If the syllable is nasalized, type a tilde (~) in the end. See the table in the end of the document for instructions for typing the special characters ꘋ, ꘌ, ꘍, ꘎, ꘏, ꘓ, ꘘ. </div> {| class="wikitable" style="font-size: xx-large" !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Start with this</span> ↓</span> ! colspan="7" |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Continue with this</span> ↓</span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Finish with this</span> ↓</span> |- ! !e !i !a !o !u !x !q ! |- ! ! colspan="5" style="text-align: end" | <span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">''alternative'' →</span></span> !O !E ! |- ! |ꔀ |ꔤ |ꕉ |ꕱ |ꖕ |ꖺ |ꗡ ! |- ! |ꔁ |ꔥ |ꕊ |ꕲ |ꖖ |ꖻ |ꗢ !~ |- !ng | | |ꕋ | | |ꖼ |ꗣ !~ |- !h |ꔂ |ꔦ |ꕌ |ꕳ |ꖗ |ꖽ |ꗤ ! |- !h | |ꔧ |ꕍ | |ꖘ |ꖾ |ꗥ !~ |- !w |ꔃ |ꔨ |ꕎ |ꕴ |ꖙ |ꖿ |ꗦ ! |- !w |ꔄ |ꔩ |ꕏ |ꕵ |ꖚ |ꗀ |ꗧ !~ |- !p |ꔅ |ꔪ |ꕐ |ꕶ |ꖛ |ꗁ |ꗨ ! |- !bh |ꔆ |ꔫ |ꕑ |ꕷ |ꖜ |ꗂ |ꗩ ! |- !b |ꔇ |ꔬ |ꕒ |ꕸ |ꖝ |ꗃ |ꗪ ! |- !mb |ꔈ |ꔭ |ꕓ |ꕹ |ꖞ |ꗄ |ꗫ ! |- !kp |ꔉ |ꔮ |ꕔ |ꕺ |ꖟ |ꗅ |ꗬ ! |- !kp | | |ꕕ | | | |ꗭ !~ |- !mgb |ꔊ |ꔯ |ꕖ |ꕻ |ꖠ |ꗆ |ꗮ ! |- !gb |ꔋ |ꔰ |ꕗ |ꕼ |ꖡ |ꗇ |ꗯ ! |- !gb | | | | | |ꗈ |ꗰ !~ |- !f |ꔌ |ꔱ |ꕘ |ꕽ |ꖢ |ꗉ |ꗱ ! |- !v |ꔍ |ꔲ |ꕙ |ꕾ |ꖣ |ꗊ |ꗲ ! |- !t |ꔎ |ꔳ |ꕚ |ꕿ |ꖤ |ꗋ |ꗳ ! |- !th |ꔏ |ꔴ |ꕛ |ꖀ |ꖥ |ꗌ |ꗴ ! |- !d |ꔐ |ꔵ |ꕜ |ꖁ |ꖦ |ꗍ |ꗵ ! |- !dh |ꔑ |ꔶ |ꕝ |ꖂ |ꖧ |ꗎ |ꗶ ! |- !l |ꔒ |ꔷ |ꕞ |ꖃ |ꖨ |ꗏ |ꗷ ! |- !r |ꔓ |ꔸ |ꕟ |ꖄ |ꖩ |ꗐ |ꗸ ! |- !dl <span style="font-size: large">''oder''</span> D |ꔔ |ꔹ |ꕠ |ꖅ |ꖪ |ꗑ |ꗹ ! |- !nd |ꔕ |ꔺ |ꕡ |ꖆ |ꖫ |ꗒ |ꗺ ! |- !s |ꔖ |ꔻ |ꕢ |ꖇ |ꖬ |ꗓ |ꗻ ! |- !sh |ꔗ |ꔼ |ꕣ |ꖈ |ꖭ |ꗔ |ꗼ ! |- !z |ꔘ |ꔽ |ꕤ |ꖉ |ꖮ |ꗕ |ꗽ ! |- !zh |ꔙ |ꔾ |ꕥ |ꖊ |ꖯ |ꗖ |ꗾ ! |- !c |ꔚ |ꔿ |ꕦ |ꖋ |ꖰ |ꗗ |ꗿ ! |- !j |ꔛ |ꕀ |ꕧ |ꖌ |ꖱ |ꗘ |ꘀ ! |- !nj |ꔜ |ꕁ |ꕨ |ꖍ |ꖲ |ꗙ |ꘁ ! |- !y |ꔝ |ꕂ |ꕩ |ꖎ |ꖳ |ꗚ |ꘂ ! |- !k |ꔞ |ꕃ |ꕪ |ꖏ |ꖴ |ꗛ |ꘃ ! |- !k | | |ꕫ | | | | !~ |- !ng |ꔟ |ꕄ |ꕬ |ꖐ |ꖵ |ꗜ |ꘄ ! |- !ngg | | | | | | |ꘅ !~ |- !g |ꔠ |ꕅ |ꕭ |ꖑ |ꖶ |ꗝ |ꘆ ! |- !g | | | | | | |ꘇ !~ |- !m |ꔡ |ꕆ |ꕮ |ꖒ |ꖷ |ꗞ |ꘈ ! |- !n |ꔢ |ꕇ |ꕯ |ꖓ |ꖸ |ꗟ |ꘉ ! |- !ny |ꔣ |ꕈ |ꕰ |ꖔ |ꖹ |ꗠ |ꘊ ! |- ! ! colspan="5" style="text-align: end" | <span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">''alternative'' →</span></span> !O !E ! |- ! !e !i !a !o !u !x !q ! |} === <span lang="en" dir="ltr" class="mw-content-ltr">Other</span> === {| class="wikitable" style="font-size: xx-large" !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin characters</span></span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai characters</span></span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Comment</span></span> |- !N |ꘋ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Syllable-final ng. Can also be typed using X.</span></span> |- != |ꘌ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai syllable lengthener.</span></span> |- !== |= |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Equals sign.</span></span> |- !, |꘍ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai comma.</span></span> |- !,, |, |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin comma.</span></span> |- !. |꘎ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai full stop.</span></span> |- !.. |. |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin full stop.</span></span> |- !! |꘎꘎ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai exclamation mark (double full stop).</span></span> |- !<nowiki>!!</nowiki> |! |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin exclamation mark.</span></span> |- !? |꘏ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai question mark.</span></span> |- !?? |? |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin question mark.</span></span> |- !FENG |ꘓ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">FEENG logogram.</span></span> |- !FAA |ꘘ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">FAA logogram.</span></span> |} Anmerkungen: * ꘋ kann auch mit X getippt werden. * <span lang="en" dir="ltr" class="mw-content-ltr">The vowels ꖺ (Ɔ) and ꗡ (Ɛ) can be typed using x and q, and also using capital O and E. So typing "gbq" is equivalent to typing "gbE", and both produce the Vai character ꗯ.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">"dl" is equivalent to "D". So typing "dla" is equivalent to typing "Da", and both produce the Vai character ꕠ.</span> g646jccax5frwu4kbpk1mxwrcztaf1x 5386743 5386741 2022-07-28T18:52:51Z ThisCarthing 17456337 Created page with "Klicke "..." am Ende der Liste. Ein Menü wird erscheinen." wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> It's possible to type in the Vai alphabet without installing any software or changing any system configuration. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This layout is based on the transliteration layout made by KeyMan, with some corrections and extensions. It is supposed to work on desktop and laptop computers, in all modern browsers with JavaScript enabled. These instructions are not intended for mobile phones and tables; on mobile devices, Vai is supported by the Gboard app. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that if squares or question marks appear instead of Vai letters, your system lacks a Vai font, and you must install one. </div> Geh wie gefolgt vor, um das Layout zu aktivieren: # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. #* <span lang="en" dir="ltr" class="mw-content-ltr">If the little keyboard icon doesn't appear, do the following: Click the gear icon near the "Languages" list in the sidebar, click "Input", click "Enable input tools", and click "Apply settings".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ꕙꔤ" appears at the top of the list, select "Vai transliteration".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ꕙꔤ" doesn't appear at the top of the list, do the following:</span> ## Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. ## <span lang="en" dir="ltr" class="mw-content-ltr">Find "ꕙꔤ" in the panel. Click it.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "Vai transliteration".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the keyboard, press Ctrl-M, or repeat the steps above. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To type every syllable, follow the instructions in the table below. If a syllable is just a vowel, type e, i, a, o, u, x, q. For syllables that begin with a consonant, type the consonant and then the vowel. If the syllable is nasalized, type a tilde (~) in the end. See the table in the end of the document for instructions for typing the special characters ꘋ, ꘌ, ꘍, ꘎, ꘏, ꘓ, ꘘ. </div> {| class="wikitable" style="font-size: xx-large" !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Start with this</span> ↓</span> ! colspan="7" |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Continue with this</span> ↓</span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Finish with this</span> ↓</span> |- ! !e !i !a !o !u !x !q ! |- ! ! colspan="5" style="text-align: end" | <span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">''alternative'' →</span></span> !O !E ! |- ! |ꔀ |ꔤ |ꕉ |ꕱ |ꖕ |ꖺ |ꗡ ! |- ! |ꔁ |ꔥ |ꕊ |ꕲ |ꖖ |ꖻ |ꗢ !~ |- !ng | | |ꕋ | | |ꖼ |ꗣ !~ |- !h |ꔂ |ꔦ |ꕌ |ꕳ |ꖗ |ꖽ |ꗤ ! |- !h | |ꔧ |ꕍ | |ꖘ |ꖾ |ꗥ !~ |- !w |ꔃ |ꔨ |ꕎ |ꕴ |ꖙ |ꖿ |ꗦ ! |- !w |ꔄ |ꔩ |ꕏ |ꕵ |ꖚ |ꗀ |ꗧ !~ |- !p |ꔅ |ꔪ |ꕐ |ꕶ |ꖛ |ꗁ |ꗨ ! |- !bh |ꔆ |ꔫ |ꕑ |ꕷ |ꖜ |ꗂ |ꗩ ! |- !b |ꔇ |ꔬ |ꕒ |ꕸ |ꖝ |ꗃ |ꗪ ! |- !mb |ꔈ |ꔭ |ꕓ |ꕹ |ꖞ |ꗄ |ꗫ ! |- !kp |ꔉ |ꔮ |ꕔ |ꕺ |ꖟ |ꗅ |ꗬ ! |- !kp | | |ꕕ | | | |ꗭ !~ |- !mgb |ꔊ |ꔯ |ꕖ |ꕻ |ꖠ |ꗆ |ꗮ ! |- !gb |ꔋ |ꔰ |ꕗ |ꕼ |ꖡ |ꗇ |ꗯ ! |- !gb | | | | | |ꗈ |ꗰ !~ |- !f |ꔌ |ꔱ |ꕘ |ꕽ |ꖢ |ꗉ |ꗱ ! |- !v |ꔍ |ꔲ |ꕙ |ꕾ |ꖣ |ꗊ |ꗲ ! |- !t |ꔎ |ꔳ |ꕚ |ꕿ |ꖤ |ꗋ |ꗳ ! |- !th |ꔏ |ꔴ |ꕛ |ꖀ |ꖥ |ꗌ |ꗴ ! |- !d |ꔐ |ꔵ |ꕜ |ꖁ |ꖦ |ꗍ |ꗵ ! |- !dh |ꔑ |ꔶ |ꕝ |ꖂ |ꖧ |ꗎ |ꗶ ! |- !l |ꔒ |ꔷ |ꕞ |ꖃ |ꖨ |ꗏ |ꗷ ! |- !r |ꔓ |ꔸ |ꕟ |ꖄ |ꖩ |ꗐ |ꗸ ! |- !dl <span style="font-size: large">''oder''</span> D |ꔔ |ꔹ |ꕠ |ꖅ |ꖪ |ꗑ |ꗹ ! |- !nd |ꔕ |ꔺ |ꕡ |ꖆ |ꖫ |ꗒ |ꗺ ! |- !s |ꔖ |ꔻ |ꕢ |ꖇ |ꖬ |ꗓ |ꗻ ! |- !sh |ꔗ |ꔼ |ꕣ |ꖈ |ꖭ |ꗔ |ꗼ ! |- !z |ꔘ |ꔽ |ꕤ |ꖉ |ꖮ |ꗕ |ꗽ ! |- !zh |ꔙ |ꔾ |ꕥ |ꖊ |ꖯ |ꗖ |ꗾ ! |- !c |ꔚ |ꔿ |ꕦ |ꖋ |ꖰ |ꗗ |ꗿ ! |- !j |ꔛ |ꕀ |ꕧ |ꖌ |ꖱ |ꗘ |ꘀ ! |- !nj |ꔜ |ꕁ |ꕨ |ꖍ |ꖲ |ꗙ |ꘁ ! |- !y |ꔝ |ꕂ |ꕩ |ꖎ |ꖳ |ꗚ |ꘂ ! |- !k |ꔞ |ꕃ |ꕪ |ꖏ |ꖴ |ꗛ |ꘃ ! |- !k | | |ꕫ | | | | !~ |- !ng |ꔟ |ꕄ |ꕬ |ꖐ |ꖵ |ꗜ |ꘄ ! |- !ngg | | | | | | |ꘅ !~ |- !g |ꔠ |ꕅ |ꕭ |ꖑ |ꖶ |ꗝ |ꘆ ! |- !g | | | | | | |ꘇ !~ |- !m |ꔡ |ꕆ |ꕮ |ꖒ |ꖷ |ꗞ |ꘈ ! |- !n |ꔢ |ꕇ |ꕯ |ꖓ |ꖸ |ꗟ |ꘉ ! |- !ny |ꔣ |ꕈ |ꕰ |ꖔ |ꖹ |ꗠ |ꘊ ! |- ! ! colspan="5" style="text-align: end" | <span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">''alternative'' →</span></span> !O !E ! |- ! !e !i !a !o !u !x !q ! |} === <span lang="en" dir="ltr" class="mw-content-ltr">Other</span> === {| class="wikitable" style="font-size: xx-large" !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin characters</span></span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai characters</span></span> !<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Comment</span></span> |- !N |ꘋ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Syllable-final ng. Can also be typed using X.</span></span> |- != |ꘌ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai syllable lengthener.</span></span> |- !== |= |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Equals sign.</span></span> |- !, |꘍ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai comma.</span></span> |- !,, |, |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin comma.</span></span> |- !. |꘎ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai full stop.</span></span> |- !.. |. |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin full stop.</span></span> |- !! |꘎꘎ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai exclamation mark (double full stop).</span></span> |- !<nowiki>!!</nowiki> |! |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin exclamation mark.</span></span> |- !? |꘏ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Vai question mark.</span></span> |- !?? |? |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">Latin question mark.</span></span> |- !FENG |ꘓ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">FEENG logogram.</span></span> |- !FAA |ꘘ |<span style="font-size: large"><span lang="en" dir="ltr" class="mw-content-ltr">FAA logogram.</span></span> |} Anmerkungen: * ꘋ kann auch mit X getippt werden. * <span lang="en" dir="ltr" class="mw-content-ltr">The vowels ꖺ (Ɔ) and ꗡ (Ɛ) can be typed using x and q, and also using capital O and E. So typing "gbq" is equivalent to typing "gbE", and both produce the Vai character ꗯ.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">"dl" is equivalent to "D". So typing "dla" is equivalent to typing "Da", and both produce the Vai character ꕠ.</span> byl4yo1qro91p2a94s6q7gjxpyc1woe Manual:Pywikibot/category redirect.py/de 100 1574857 5387858 5292530 2022-07-29T10:22:52Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> '''category_redirect.py''' is a {{ll|Manual:Pywikibot|Pywikibot}} script used to move pages out of redirected categories. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The bot will look for categories that are marked with a category redirect template, take the first parameter of the template as the target of the redirect, and move all pages and subcategories of the category there. It also changes hard redirects into soft redirects, and fixes double redirects. A log is written under &lt;userpage>/category_redirect_log. Only category pages that haven't been edited for a certain cooldown period (7 days by default) are taken into account. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following parameters are supported: </div> {{Pywikibot command table beginning}} {{option|delay:#|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set an amount of days. If the category is edited more recenty than given days, ignore it. Default is 7</span>}} {{option|tiny|2=<span lang="en" dir="ltr" class="mw-content-ltr">Only loops over [[:d:Q8099903|Category:Wikipedia non-empty soft redirected categories]] and moves all images, pages and categories in redirect categories to the target category</span>}} {{Pywikibot command table end}} == Verwendung == <syntaxhighlight lang=shell-session> $ python pwb.py category_redirect [options] </syntaxhighlight> {{Manual:Pywikibot/Global Options}} [[Category:Pywikibot scripts{{#translation:}}|category_redirect]] j1xsjq0n50y2f2ggkz6f3n203aajuxq Extension:EventLogging/pl 102 1575475 5387149 5381731 2022-07-28T21:07:44Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = <span lang="en" dir="ltr" class="mw-content-ltr">Provides a framework for logging analytics events</span> |version = <span lang="en" dir="ltr" class="mw-content-ltr">continuous updates</span> |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} <div lang="en" dir="ltr" class="mw-content-ltr"> The EventLogging extension makes it possible to collect structured data on how users interact with MediaWiki sites. </div> == Funkcje == * <span lang="en" dir="ltr" class="mw-content-ltr">EventLogging supports client-side logging from JavaScript and server-side logging from PHP.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Logging behavior can be dynamically configured using {{ll|Extension:EventStreamConfig}}.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The events are JSON objects defined by versioned JSONSchemas stored in a schema git repository.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">The extension does not include any back-end code for transporting, parsing, or loading these events.</span> <span lang="en" dir="ltr" class="mw-content-ltr">A separate service, [[wikitech:Event Platform/EventGate|EventGate]], implements this functionality and deals with inserting events into Kafka.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Events are then persisted in downstream datastores (e.g. Hive) via various ingestion pipelines.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The details of these components are specific to Wikimedia Foundation's configuration.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == EventLogging at Wikimedia == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The Wikimedia Foundation uses the EventLogging extension as part of a [[wikitech:Analytics/Systems/EventLogging|broader system for collecting, aggregating, storing, and analyzing user data]] within the limits set out by our [[m:Special:MyLanguage/Privacy policy|privacy policy]] and [[m:Special:MyLanguage/Data retention guidelines|data retention guidelines]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This page is about general use of the EventLogging extension.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The Wikimedia Foundation uses EventLogging with WMF specific backend components and [https://schema.wikimedia.org/#!/ schema repositories].</span> <span lang="en" dir="ltr" class="mw-content-ltr">For Wikimedia specific and maintained documentation, see [[wikitech:Analytics/Systems/EventLogging]] and [[wikitech:Event Platform]].</span> ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} <div lang="en" dir="ltr" class="mw-content-ltr"> === Configuring the schema location === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> By default, the extension will look for schemas on [[m:Special:MyLanguage/Meta-Wiki|Meta-Wiki]]. </div> <span lang="en" dir="ltr" class="mw-content-ltr">The relevant default settings are:</span> <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">To use local schemas, or schemas from the central wiki of your own wikifarm, you need to override these.</span> <span lang="en" dir="ltr" class="mw-content-ltr">E.g. to use the <code>Schema</code> namespace of the local wiki, set</span> <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> <span lang="en" dir="ltr" class="mw-content-ltr">(and ensure the user account that will create the schemas is [[Special:MyLanguage/Manual:Autoconfirmed users|autoconfirmed]]).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Logging events using EventLogging == </div> * {{ll|Extension:EventLogging/Guide}} - <span lang="en" dir="ltr" class="mw-content-ltr">to developing and deploying EventLogging schemas, and more</span> * {{ll|Extension:EventLogging/Programming}} - <span lang="en" dir="ltr" class="mw-content-ltr">tips and suggestions for developers writing code to log events</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Developing the EventLogging extension == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Developer setup === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> As a developer, you will want to set up and use EventLogging on your development wiki to simulate its use in production. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== Using Docker ==== </div> ''Zobacz {{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}'' ==== Używanie mediawiki-vagrant ==== <span lang="en" dir="ltr" class="mw-content-ltr">If you develop using mediawiki-vagrant, everything you need is encapsulated in the <code>eventlogging</code> role.</span> <span lang="en" dir="ltr" class="mw-content-ltr">To enable it, run:</span> <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== For JavaScript development ==== </div> <span lang="en" dir="ltr" class="mw-content-ltr">If working on the JavaScript client, you'll need to install dependencies with <code>npm install</code> from the folder you're developing in.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Then you can use <code>npm test</code> to run ESLint for example.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The "How to run tests" section below points out how to see JavaScript test results.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> When adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== How to run tests ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There are PHP tests, Python tests, and JavaScript tests. </div> <span lang="en" dir="ltr" class="mw-content-ltr">To run JavaScript tests, visit Special:JavaScriptTest/qunit on your development wiki.</span> (Zobacz {{ll|Manual:JavaScript unit testing}}.) <span lang="en" dir="ltr" class="mw-content-ltr">To run PHP tests, we use PHPUnit.</span> Upewnij się, że to jest zainstalowane, a potem: <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] cjjwzjts84z3ddwt6hy0yailtajp0ew Reading/Web/Desktop Improvements/Updates/Talk to Web/tr 0 1576496 5387122 5383462 2022-07-28T20:35:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Arşiv |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} goedyojjzme0mfsp617rn2ja7mpizte Reading/Web/Desktop Improvements/Updates/Talk to Web/yo 0 1576498 5387126 5383466 2022-07-28T20:35:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Ojú-ewé àfipamọ́ |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} ge8tajn227elzqpgvko6cs4s0gtlw49 Reading/Web/Desktop Improvements/Updates/Talk to Web/cs 0 1576500 5387106 5383450 2022-07-28T20:35:18Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Archiv |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 2kuwujhi2dw5w50dv9a09gkxfkygqyl Reading/Web/Desktop Improvements/Updates/Talk to Web/zh 0 1576502 5387127 5383467 2022-07-28T20:35:34Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> == 時間軸 == * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - 大會</span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC (暫定) - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - 大會 <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=存档 |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} tczbeikzmel5ochv9pbxbhx3ntas0jb Talk pages project/Usability/Prototype/es 0 1576600 5387257 5370938 2022-07-28T21:38:03Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:Usability_Improvement_annotated_mockup_(desktop).jpg|alt=Un bosquejo (o modelo) que muestra el nuevo diseño propuesto (desktop) del wikitexto de las páginas de discusión.|center|thumb|600x600px|Bosquejo ('mockup') del nuevo diseño para el wikitexto '''desktop''', de las páginas de discusión.]] <big>¡Bienvenido!</big> Esta página tiene instrucciones para probar cambios de diseño del wikitexto de las páginas de discusión. Estos cambios de diseño son una parte del {{ll|Talk pages project}} y un esfuerzo para hacer que sean que éstas sean más fáciles de reconocer y usar. == Prueba el prototipo == # Visita esta {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:New_York $1]</mark>|página de discusión de artículo}} o esta {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Bob $1]</mark>|página de discusión (usuario)}} con la versión nueva de la wiki: el prototipo. # Encuentra la discusión (la editada) más reciente. # Encuentra la discusión en la que más gente participe. # Encuentra la discusión con más comentarios. # Vuelve a la discusión en la que te fijaste, en el "paso 4". Averigua cómo harías lo siguiente: ## Publica una respuesta en esa discusión. ## Edita la respuesta que publicaste. # Lo siguiente, comienza un nuevo tema (nueva discusión). # ✅ Ahora estás preparado para compartir tu ''feedback'' (retroalimentación, colaboración). == Diseño == <gallery mode="slideshow" showthumbnails> Archivo:Bosquejo (modelo) de mejora de la usabilidad (móvil).jpg|alt=Un bosquejo (o modelo) que muestra el nuevo diseño propuesto ''(no-mobile / desktop)'' del wikitexto de las páginas de discusión.|Bosquejo de la propuesta de diseño para el wikitexto de las páginas de discusión '''(mobile wikitext)''' / wikitexto móvil (no de escritorio). Archivo:Bosquejo (modelo) de mejora de la usabilidad (comentarios sobre wiki-móvil).jpg|alt=Maqueta (bosquejo) que muestra el diseño propuesto para la vista de la página de inicio de las páginas de discusión de wikitexto móvil.|Bosquejo (maqueta) comentado del diseño de la página de discusión del ''wikitexto '''móvil''''' propuesto. Archivo: maqueta comentada de mejora (para las discusiones wikitexto-móvil).jpg|alt=Maqueta (bosquejo) que muestra el diseño propuesto para la vista de discusión individual de las páginas de discusión de wikitexto móvil|Bosquejo (maqueta) comentado del diseño de la página de discusión con ''wikitexto '''móvil''''' propuesto. Archivo:Bosquejo (maqueta) de mejora de la usabilidad ''(desktop)'' de escritorio (no móvil).jpg|alt=bosquejo (o maqueta) que muestra el diseño propuesto del wikitexto de las páginas de discusión ''(desktop)''.|Bosquejo ''("mockup")'' del nuevo diseño para el wikitexto de páginas de discusión '''''(desktop)'''''. Archivo:Mejora de la usabilidad ''(desktop)'' bosquejo comentado.jpg|alt=bosquejo (o maqueta) que muestra el diseño propuesto del wikitexto para las páginas de discusión ''(desktop)''.|Maqueta (bosquejo) comentada del nuevo diseño para el wikitexto de páginas de discusión ''(desktop)''. Archivo:contenedor del tema de la usabilidad de las herramientas ''(DiscussionTools),'' · captura de pantalla de 2022-04-29.png|alt=Detalle del cambio|Cambio propuesto en la parte superior de las secciones de discusión. Archivo:captura de pantalla del marco ''(frame)'' de la usabilidad de la página de herramientas ''(DiscussionTools),'' 2022-04-29.png|alt=Detalle del cambio|Cambio propuesto, en la parte superior de las páginas de discusión. Archivo:Tabla de contenidos ''(TOC)'' o índice, de la usabilidad de la página de herramientas ''(DiscussionTools)'' su captura de pantalla de 2022-04-29.png|alt=Detalle del cambio|Cambio propuesto del índice de: ''[[Vector 2022]] only'' ([[Vector 2022]] sólo) </gallery> == participa, colabora, sugiere ''(feedback)'', aquí puedes hacerlo == {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |Si lo prefieres: nos puedes enviar un ''(e-mail)'' correo electrónico: talkpageconsultation{{@}}wikimedia.org |} Comparte tus pensamientos. # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:Su nombre de usuario ''(USERNAME)''}} Haz clic aquí, para comenzar un tema nuevo en la página de discusión.] # Teclea <code>Feedback: tu nombre de usuario (USERNAME)</code>. # Escribe respuestas a estas cuestiones. <strong>Puedes escribir en tu lengua o idioma.</strong> ## ¿Utilizas un dispositivo móvil o un PC portátil para probar el prototipo? ## Sobre el prototipo, ¿qué no esperabas encontrarte? ¿Sorpresas? ## ¿Qué pasos de la sección '''Prueba el prototipo''' encontraste eran difíciles de completar? ## ¿Qué te gusta del prototipo? ## ¿Qué le gustaría que fuera diferente en el prototipo? ## (Opcional) ¿Te imaginas que este diseño no funcione en algunas páginas? Si puedes, por favor comparte enlaces a estas páginas. Sería muy útil. ¡Participa, colabora! (Es la filosofía wiki) # Haz clic en el botón "{{int|discussiontools-replywidget-newtopic}}" azul. # ✅ ¡Ya terminaste! ¡Gracias! 74bwnlgdcai2zu0iyfl7mn059dphrpo Reading/Web/Desktop Improvements/Features/Visual Refinements 0 1584782 5386682 5335066 2022-07-28T17:20:40Z AHollender (WMF) 12905271 /* Menus */ added % signs for extra clarity wikitext text/x-wiki {{Reading/Web/Desktop Improvements/Header|1={{Reading/Web/Desktop Improvements/Features/Navigation}}}} Now that all of the major functional changes to the interface are complete, we would like to focus on the final look and feel of the new interface, ensuring that our final design is accessible, fitting to the personality and purpose of our wikis, and easy to use == Background and Goals == Over the past two years we have made various structural changes to the interface. We have moved the [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Search|search box]], the [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|language switcher]], and the [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Table of contents|table of contents]]. We have organized certain links and tools into menus. And we have [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width|limited the content width]], added a [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Sticky Header|sticky header]], and moved the page title above the page toolbar. Now, with all of these various elements situated in the updated interface, we are turning our attention to the overall look. Some initial questions our team has been considering are: * How can we use visual design to improve the interface? * Do we think there is value in the skin having some additional personality (like the blue lines and gradients in Legacy Vector)? * At what point there's too much of it, such that it might become distracting or make the interface confusing? * What if we do as little as possible, and take a super minimalist approach similar to the original Wikipedia interface? Historically our approach has been simple and functional. There is little styling (if any) to the HTML elements, which simplifies the interface both for people using it and for people designing and building it. It also means that our visual design is rather timeless. We don't chase the trends and don't need to make changes every couple of years. Looking at the screenshots below we can see how Monobook and Legacy Vector use visual design sparingly (mainly borders and background colors). == Proposed Changes == === Menus === We use several menus in our interface. Thus far our approach to how we style menus has not been consistent. We have an opportunity, with Vector 2022, to develop a more accessible and consistent approach to the styling of our menus. In their most simple form menus have two elements: a menu trigger, and menu items. We're considering blue vs. black (for both the menu trigger, and the menu options), and bold vs. non-bold (for the menu trigger). Link to prototype with options: https://di-visual-design-menus.web.app/Brown_bear {| class="wikitable" |+ |1) minimalist [[File:Vector 2022, minimalist.jpg|border|275x275px|frameless|alt=1) minimalist]] |2) article borders [[File:Vector 2022, content side lines.jpg|border|frameless|275x275px]] |3) article borders + header underline [[File:Vector 2022, content side lines and header line.jpg|border|frameless|275x275px]] |- |4) table of contents line + header underline [[File:Vector 2022, table of contents line and header line.jpg|border|frameless|275x275px]] |5) table of contents line + page title underline [[File:Vector 2022, table of contents line and page header line.jpg|border|frameless|275x275px]] |6) article borders + header background (solid) [[File:Vector 2022, content side lines and header background (solid).jpg|border|frameless|275x275px]] |- |7) article borders + header background (gradient) [[File:Vector 2022, content side lines and header background (gradient).jpg|border|frameless|275x275px]] |8) outside article background (gradient) [[File:Vector 2022, outside content background (gradient).jpg|border|frameless|275x275px]] |9) outside article background (solid) [[File:Vector 2022, outside content background (solid).jpg|border|frameless|275x275px]] |} === Borders and backgrounds === Should we add borders and backgrounds to help divide up the regions of the interface, and if so how should they look? As we mentioned in the Background and context section above, both Monobook and Vector use backgrounds and borders to separate the interface from the content. Backgrounds and borders can also add personality to the interface. However, it is difficult to know how functional or necessary they are. We've created several options with progressively more/darker borders and backgrounds. Link to prototype with options: https://di-visual-design-borders-bgs.web.app/Zebra {| class="wikitable" |+ | 1) minimalist [[File:Vector 2022, minimalist.jpg|border|275x275px|frameless|alt=1) minimalist]] |2) article borders [[File:Vector 2022, content side lines.jpg|border|frameless|275x275px]] |3) article borders + header underline [[File:Vector 2022, content side lines and header line.jpg|border|frameless|275x275px]] |- | 4) table of contents line + header underline [[File:Vector 2022, table of contents line and header line.jpg|border|frameless|275x275px]] |5) table of contents line + page title underline [[File:Vector 2022, table of contents line and page header line.jpg|border|frameless|275x275px]] |6) article borders + header background (solid) [[File:Vector 2022, content side lines and header background (solid).jpg|border|frameless|275x275px]] |- |7) article borders + header background (gradient) [[File:Vector 2022, content side lines and header background (gradient).jpg|border|frameless|275x275px]] |8) outside article background (gradient) [[File:Vector 2022, outside content background (gradient).jpg|border|frameless|275x275px]] |9) outside article background (solid) [[File:Vector 2022, outside content background (solid).jpg|border|frameless|275x275px]] |} === Active section in the table of contents === The table of contents is now on the (left) side of the article, and is fixed in place so it remains visible as you scroll down the page. A new feature is that the table of contents indicates which section of the article you are currently reading (we call this the "active section"). Currently, following from a pattern used on the Article/Talk tabs, the active section in the table of contents is black, and the non-active sections are blue. We like this pattern because it is simple, not distracting, and used elsewhere. We could also use additional styling to indicate the active section. Link to prototype with options: https://di-visual-design-toc-active.web.app/Otter {| class="wikitable" |+ |1) minimalist [[File:TOC active section, minimalist (both).jpg|border|frameless|396x396px]] |2) bold [[File:TOC active section, bold (both).jpg|border|frameless|396x396px]] |3) background [[File:TOC active section, background (both).jpg|border|frameless|396x396px]] |4) line with border [[File:TOC active section, line (both).jpg|border|frameless|396x396px]] |- |5) line with border (2) [[File:TOC, background + line (both).jpg|border|frameless|396x396px]] | | | |} === Logo in the header === Monobook and Legacy Vector both feature a square Wikipedia logo with a large globe. Given the various changes to Vector 2022 a smaller, rectangular logo in the corner may fit the layout better. However, we wanted to make sure to try various options. Please remember to try these options at various screen sizes, as the balance of the layout shifts depending on your screen size. Link to prototype with options: https://di-visual-design-header-logo.web.app/Panda {| class="wikitable" |+ |1) Rectangle logo left [[File:Vector 2022, minimalist.jpg|frameless|275x275px]] |2) Square logo left [[File:Vector 2022, square logo left.jpg|frameless|275x275px]] |3) Square logo left (gradient) [[File:Vector 2022, square logo left (gradient).jpg|frameless|275x275px]] |- |4) Rectangle logo center [[File:Vector 2022, rectangle logo center.jpg|frameless|275x275px]] | | |} === Link colors === The World Wide Web Consortium (W3C) have Web Content Accessibility Guidelines. These guidelines define a minimum contrast level for links: "For usability and accessibility, links should be underlined by default. Otherwise, link text must have at least 3:1 contrast with surrounding body text, and must present a non-color indicator (typically underline) on mouse hover and keyboard focus." Since we do not underline links by default, our link color choice must meet the 3:1 contrast requirement. In order to check the contrast of our links with our body text we can use the contrast checker provided by WebAIM. {| class="wikitable" |+Current link colors !Color !Contrast with body text <code>#202122</code> !Test result !Link to test result |- |blue links <code>#0645ad</code> |'''1.89''':1 |❌ '''Fail''' |link to results |- |visited links <code>#0b0080</code> |'''1.01''':1 |❌ '''Fail''' |link to results |} {| class="wikitable" |+Proposed link colors !Color !Contrast with body text <code>#202122</code> !Test result !Link to test result |- |blue links <code>#3366cc</code> |'''3''':1 |✅ '''Pass''' |link to results |- |visited links <code>#795cb2</code> |'''3.06''':1 |✅ '''Pass''' |link to results |} Additionally, the proposed blue link color is already part of the Wikimedia Design Style Guide, and is used on our mobile websites as well as in various project logos, so we would be gaining consistency. Link to prototype with proposed colors: https://di-visual-design-link-colors.web.app/Salmon {| class="wikitable" |+ |Current link colors [[File:Vector 2022 - current link colors 01.jpg|border|frameless|450x450px]] |Proposed colors [[File:Vector 2022 - proposed link colors.jpg|border|frameless|450x450px]] |} === Font size === The mission of our movement is to provide all of the world's knowledge to as many people as possible. Currently the majority of the knowledge we offer is in the form of text. Research has shown that typographic settings (such as font size, line length, and line height) influence the experience of reading, both in terms of general comfort (i.e. eye strain and fatigue), and comprehension and retention. Therefore it is important for us to use optimal typographic settings in our interface. An important factor to keep in mind when determining what is optimal for our projects is that people engage both in in-depth reading, as well as scanning of text. In a previous phase of the project we read research studies regarding the line length and concluded that between 90–140 characters per line is optimal for our projects ([[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Limiting content width#Goals%20and%20motivation|link to writeup]]). Recently we have spent time reading research studies about font size. The most convincing, and directly applicable, research we have found thus far is a 2016 study that used eye-tracking to evaluate the affects of font size and line spacing for people reading Wikipedia:<blockquote>Using a hybrid-measures design, we compared objective and subjective readability and comprehension of the articles for font sizes ranging from 10 to 26 points, and line spacings ranging from 0.8 to 1.8 (font: Arial). Our findings provide evidence that readability, measured via mean fixation duration, increased significantly with font size. Further, comprehension questions had significantly more correct responses for font sizes 18 and 26. These findings provide evidence that text-heavy websites should use fonts of size 18 or larger and use default line spacing when the goal is to make a web page easy to read and comprehend. Our results significantly differ from previous recommendations, presumably, because this is the first work to cover font sizes beyond 14 points.</blockquote>Firstly, we need to convert the measure used by the researchers (points) into the measure that browsers ultimately render (px). The conversion is: 1px = 72pt / 96. So the range studied in the research (10–26 points) is equivalent to 13.3–34px. Their conclusion, 18 points, is equal to 24px. '''So should we increase the font size to 24px?''' The research studied in-depth reading, however people often scan the page in order to find a certain piece of information. This is a different reading behavior, that arguably benefits from a smaller font size than in-depth reading does. Our conservative proposal, taking into account scanning, is to increase the font size to 16px to begin with. (We would be increasing the maximum width of the article as well, from 960px to 1050px.) As a next step, we will plan to conduct our own research to further study font size on Wikimedia wikis. Annotated bibliography of typography and readability research Link to prototype with proposed font size: https://di-visual-design-font-size.web.app/Hummingbird === Swapping the order of Page Title and Tabs === As we begin to think about our improving our navigational hierarchy, we recognize that the page title is the main framing for the content within a page - whether that's the history of a page, the ability to edit the page, etc. To create this expectation more easily, we will be moving the title above the tabs such as Discussion, Read, Edit, etc. With this change, we are improving two things. First, we are making it clear that the items in the tabs are related to the the page that's being viewed. By putting the page title first, this makes this connection easier to make. In addition, this change makes [[Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Language switching|switching languages]] easier by moving the language button into an even more prominent position at the top of the page. [[File:Screenshot_of_tab_and_title_order_on_English_Wikipedia_in_the_Vector_2022_skin.png|center|thumb|800x800px|Screenshot of tab and title order on English Wikipedia in the Vector 2022 skin]] == Qualitative Testing == In June and July 2022, we performed prototype testing with each of the prototypes linked above. This testing was performed across multiple languages and projects. The goal of the testing was to identify which of the available prototypes users found best for their individual use cases as well as overall usability. Below is a summary of our results: === Menus === Respondents overwhelmingly preferred the '''blue''' color for both menu triggers and menu items. Overall, there was also a preference for the regular blue menu triggers over the bold version. Link to prototype with options: https://di-visual-design-menus.web.app/Brown_bear {| class="wikitable" |'''Menu trigger color''' |blue |black |blue bold |black bold |- |'''Percentage''' |40.32 % |16.94 % |29.03 % |13.71 % |- |'''Total Responses''' |50 |21 |36 |17 |} {| class="wikitable" |'''Menu item color''' |blue |black |- |'''Percentage''' |83.74 % |16.26 % |- |'''Total Responses''' |103 |20 |} === Borders and Backgrounds === The large majority of respondents preferred either the '''Minimalist''' option, or the '''Outside article background solid''' option Link to prototype with options: https://di-visual-design-borders-bgs.web.app/Zebra {| class="wikitable" |'''Border and background style''' |Minimalist |ar borders |Title underline + toc line |Toc line + hd underline |Ar borders + h underline |Ar borders + h bg (solid) |Ar borders + h bg (gradient) |Outside ar bg (gradient) |Outside ar bg (solid) |- |'''Percentage''' |20.30 % |7.43 % |2.97 % |8.91 % |3.47 % |11.39 % |7.92 % |7.92 % |28.71 % |- |'''Total responses''' |41 |15 |6 |18 |7 |23 |16 |16 |58 |} === Active section in the table of contents === Overall, respondents preferred the '''bold''' option for the table of contents active section Link to prototype with options: https://di-visual-design-toc-active.web.app/Otter {| class="wikitable" |'''Active section style''' |1) minimalist |2) bold |3) background |4) line w/ border |5) line w/ border (2) |- |'''Percentage''' |10.47 % |38.95 % |8.14 % |23.84 % |18.60 % |- |'''Total responses''' |18 |67 |14 |41 |32 |} === Logo in the header === The majority of respondents preferred the '''rectangle, left''' version of the logo Link to prototype with options: https://di-visual-design-header-logo.web.app/Panda {| class="wikitable" |'''Logo Version''' |1) rectangle, left |2) square, left |3) rectangle, center |4) square, left (gradient) |- |'''Percentage''' |51.59 % |35.67 % |5.73 % |7.01 % |- |'''Total responses''' |81 |56 |9 |11 |} === Link Colors === A large majority of respondents preferred the new '''proposed link colors.''' Link to prototype with proposed colors: https://di-visual-design-link-colors.web.app/Salmon {| class="wikitable" |'''Link Color Option''' |current |proposed |yes change but need to darken |likes new purple but not blue |mixed |- |'''Percentage''' |20.83 % |62.50 % |9.17 % |3.33 % |4.17 % |- |'''Total Responses''' |25 |75 |11 |4 |5 |} === Font Size === A large majority of the respondents preferred the larger '''proposed font size of 16px'''. Some respondents made the request to make font size a preference. Link to prototype with proposed font size: https://di-visual-design-font-size.web.app/Hummingbird {| class="wikitable" |'''Font Size''' |current (14px) |proposed (16px) |should be a preference |mixed |- |'''Percentage''' |10.85 % |63.57 % |19.38 % |6.20 % |- |'''Total responses''' |14 |82 |25 |8 |} melho8hs84rsqr9de3qy6t71nb2rrrl Talk pages project/Usability/Prototype/hu 0 1586041 5387260 5370942 2022-07-28T21:38:05Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:Usability_Improvement_annotated_mockup_(desktop).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">A mockup showing the proposed new design for desktop wikitext talk pages.</span>|center|thumb|600x600px|<span lang="en" dir="ltr" class="mw-content-ltr">Mockup of new design for '''desktop''' wikitext talk pages.</span>]] <big>Üdvözlünk!</big> Ez a lap elmagyarázza, hogyan tesztelheted a wikiszöveges vitalapok designváltozásait. Ezek a változások a {{ll|Talk pages project}} részét képezik, és az a céljuk, hogy egyszerűbbé tegyék a vitalapok felismerését és használatát. == A prototípus kipróbálása == # Látogasd meg {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:New_York $1]</mark>|ezt a szócikkvitalapot}} vagy {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Bob $1]</mark>|ezt a szerkesztővitalapot}} a speciális prototípuswikin. # Találd meg a legutóbb szerkesztett megbeszélést. # Találd meg a legtöbb résztvevővel rendelkező megbeszélést. # Találd meg a legtöbb hozzászólással rendelkező megbeszélést. # Görgess vissza a 4. lépésben megtalált megbeszéléshez. Gondold végig, hogy miként: ## válaszolnál a megbeszélésben; valamint ## szerkesztenéd az elküldött válaszodat. # Most indíts megbeszélést egy új témáról. # ✅ Készen állsz a visszajelzésed megosztására. == Design == <gallery mode="slideshow" showthumbnails> File:Usability Improvement mockup (mobile).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for mobile wikitext talk pages</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement annotated mockup (mobile overview).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for the mobile wikitext talk pages landing page view</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement annotated mockup (mobile discussion).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup showing the proposed design for the mobile wikitext talk pages individual discussion view</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed '''mobile''' wikitext talk page design</span> File:Usability Improvement mockup (desktop).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for desktop wikitext talk pages</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Mockup of proposed design for '''desktop''' wikitext talk pages</span> File:Usability Improvement annotated mockup (desktop).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup showing the proposed design for desktop wikitext talk pages</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Annotated mockup of proposed design for '''desktop''' wikitext talk pages</span> File:DiscussionTools Usability topic container screenshot en 2022-04-29.png|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Detail of change</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to the top of discussion sections</span> File:DiscussionTools Usability page frame screenshot en 2022-04-29.png|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Detail of change</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to the top of talk pages</span> File:DiscussionTools Usability Table of Contents screenshot en 2022-04-29.png|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Detail of change</span>|<span lang="en" dir="ltr" class="mw-content-ltr">Proposed change to Table of Contents ('''[[Vector 2022]] only''')</span> </gallery> == Visszajelzésed megosztása == {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |Ha azt preferálod, küldhetsz e-mailt is: talkpageconsultation{{@}}wikimedia.org |} Kérjük, oszd meg a véleményed. # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:SZERKESZTŐNEVED}} Kattints ide új téma indításához a vitalapon.] # <span lang="en" dir="ltr" class="mw-content-ltr">Type <code>Feedback: YOUR USERNAME</code></span>. # Válaszold meg az alábbi kérdéseket. <strong>Nyugodtan írhatsz a saját nyelveden.</strong> ## Mobileszközt vagy laptop/asztali számítógépet használtál a teszteléshez? ## Mi volt váratlan a prototípusban? ## „A prototípus kipróbálása” szakasz mely lépései okoztak nehézséget? ## Mi tetszett a prototípusban? ## Mit lett volna máshogy jobb a prototípusban? ## (Opcionális) Van szerinted olyan lap, ahol nem működne ez a design? Ha igen, be tudod linkelni őket? Sokat segítene. # Kattints a kék „{{int|discussiontools-replywidget-newtopic}}” gombra. # ✅ Kész is vagy! Köszönjük! 72sl62q92q4lk0rrz877a21dxh4atwo Translations:Growth/FAQ/262/en 1198 1586159 5387830 5327638 2022-07-29T10:15:08Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki === Who can be a mentor? === 9q8hfcmwxsmvsfbxfpkwohhjeui98qb Talk pages project/Usability/Prototype/pl 0 1588309 5387262 5370947 2022-07-28T21:38:08Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages /> [[File:Usability_Improvement_annotated_mockup_(desktop).jpg|alt=Makieta przedstawiająca proponowany wygląd stron dyskusji.|center|thumb|600x600px|Makieta przedstawiająca proponowany wygląd stron dyskusji w wikikodzie, na komputerach stacjonarnych.]] <big>Witaj!</big> Tu znajduje się instrukcja testowania zmian w wyglądzie stron dyskusji w wikikodzie. Zmiany wyglądu to część {{ll|Talk pages project}}. Zmiana wyglądu ma na celu ułatwienie korzystania z nich, a także łatwiejsze odkrycie ich funkcji. == Wypróbuj prototyp == # Wejdź na {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/Talk:New_York $1]</mark>|tę stronę dyskusji artykułu}} lub tę {{tmpl|0=<mark>[https://patchdemo.wmflabs.org/wikis/6c2b1c9b3e/wiki/User_talk:Bob $1]</mark>|stronę dyskusji użytkownika}} na specjalnej wiki pokazowej. # Znajdź najczęściej edytowaną dyskusję. # Znajdź dyskusję, gdzie uczestniczyło najwięcej ludzi. # Znajdź dyskusję z największą ilością wypowiedzi. # Przewiń do dyskusji znalezionej w kroku czwartym. Zastanów się, jak chciałbyś zrobić poniższe: ## Umieszczenie odpowiedzi w dyskusji. ## Edytowanie umieszczonej wypowiedzi. # Teraz zacznij dyskusję na nowy temat. # ✅ Teraz możesz podzielić się uwagami. == Projekt == <gallery mode="slideshow" showthumbnails> File:Usability Improvement mockup (mobile).jpg|alt=Makieta przedstawiająca proponowany wygląd stron dyskusji w wersji mobilnej.|Makieta przedstawiająca proponowany wygląd stron dyskusji w wersji '''mobilnej'''. File:Usability Improvement annotated mockup (mobile overview).jpg|alt=<span lang="en" dir="ltr" class="mw-content-ltr">Mockup showing the proposed design for the mobile wikitext talk pages landing page view</span>|Makieta z oznaczeniami przedstawiająca proponowany wygląd stron dyskusji w wersji '''mobilnej'''. File:Usability Improvement annotated mockup (mobile discussion).jpg|alt=Makieta z oznaczeniami przedstawiająca proponowany wygląd stron dyskusji w wersji mobilnej - widok pojedynczej dyskusji (wątku).|Makieta z oznaczeniami przedstawiająca proponowany wygląd stron dyskusji w wersji '''mobilnej'''. File:Usability Improvement mockup (desktop).jpg|alt=Makieta przedstawiająca proponowany wygląd stron dyskusji w wikikodzie, na komputerach stacjonarnych.|Makieta przedstawiająca proponowany wygląd stron dyskusji w wikikodzie, na '''komputerach stacjonarnych'''. File:Usability Improvement annotated mockup (desktop).jpg|alt=Makieta przedstawiająca proponowany wygląd stron dyskusji w wikikodzie, na komputerach stacjonarnych.|Makieta przedstawiająca proponowany wygląd stron dyskusji w wikikodzie, na '''komputerach stacjonarnych'''. File:DiscussionTools Usability topic container screenshot en 2022-04-29.png|alt=Szczegół zmiany|Proponowana zmiana w sekcjach na górze dyskusji File:DiscussionTools Usability page frame screenshot en 2022-04-29.png|alt=Szczegół zmiany|Proponowana zmiana w sekcjach na górze dyskusji File:DiscussionTools Usability Table of Contents screenshot en 2022-04-29.png|alt=Szczegół zmiany|Proponowana zmiana spisu treści ('''tylko [[Vector 2022]]''') </gallery> == Podziel się uwagami == {| class="wikitable float{{dir|{{PAGELANGUAGE}}|left|right}}" |+ |Jeżeli chcesz, możesz wysłać e-mail: talkpageconsultation{{@}}wikimedia.org |} Prosimy o podzielenie się swoimi przemyśleniami. # [https://www.mediawiki.org/wiki/Talk:Talk_pages_project/Usability/Prototype?topiclist_preloadtitle=Feedback:+{{urlencode:TWOJA NAZWA UŻYTKOWNIKA}} Kliknij tutaj aby założyć nowy wątek na stronie dyskusji.] # Wpisz <code>Feedback: YOUR USERNAME</code>. # Napisz odpowiedzi na te pytania. <strong>Możesz pisać w swoim języku.</strong> ## Czy testowałeś ten prototyp na laptopie lub urządzeniu mobilnym? ## Czy znalazłeś coś nieoczekiwanego? ## Które z kroków w sekcji "Wypróbuj prototyp" sprawiły trudność? ## Co sądzisz o tym prototypie? ## <span lang="en" dir="ltr" class="mw-content-ltr">What do you wish was different about the prototype?</span> ## (Opcjonalne) Czy ten wygląd może nie sprawdzić się na niektórych stronach? Jeżeli to możliwe, podaj linki do tych stron? # Kliknij niebieski przycisk "{{int|discussiontools-replywidget-newtopic}}". # ✅ Gotowe! Dziękujemy! phiespgzrrcd0hgyvq97lsh42te801c Greenhouse experiment 0 1589979 5387255 5359522 2022-07-28T21:35:42Z SPatel (WMF) 17546935 /* Greenhouses */ wikitext text/x-wiki [[File:Generated greenhouses.png|center|frameless|401x401px|Generated greenhouses]] If we imagine the Movement, and the projects that comprise it, as a forest of interdependent ideas, then we imagine the Greenhouse Experiment as a small network of greenhouses amongst the old-growth trees. Inside these greenhouses, a few of us are collecting nascent ideas and curiosities so that they have opportunities to grow into something that can eventually benefit the wider forest (read: Movement). There are infinite "plots" available, so if experimenting with nurturing a practice of naming and exploring what you are curious about resonates with you, please read on about how to join us and build a greenhouse of your own! == Objectives and hypothesis == The Greenhouse Experiment has two objectives: # Identify what we need to think freely enough to conjure up potential futures for the Movement's projects # Develop ideas that will benefit the Movement in ways that align with its objectives, values, and priorities The Greenhouse Experiment is built on the hypothesis that: # Consistently taking note of and naming the tiny ideas and curiosities in the moments they occur to us # Locating these ideas in a public place, proximate to where volunteers and Wikimedia staff are already spending their time, ''and'' # Iterating upon these "gestures of mind" with input and support from other people ...will cause new ideas that are durable and valuable to take root in the Movement. == Building a greenhouse == To join the Greenhouse Experiment and create a greenhouse of your own, follow these steps: # Make sure you logged in to mediawiki.org # Visit: [[Special:MyPage/Greenhouse]] # Click or tap the Create link that appears at the top of the page # Add [https://commons.wikimedia.org/w/index.php?search=Greenhouse&title=Special:MediaSearch&go=Go&type=image an image of a greenhouse from Commons] that you like (or upload one to Commons yourself!) # Click the "Publish" button to create your greenhouse # Come back to this page and add a link to the Greenhouse you published to the "Greenhouses" section below # ✅ That's it! You're now ready to starting planting ideas ^ _ ^ == Greenhouses == * [[User:CMadeo (WMF)/Greenhouse|Carolyn's Greenhouse]] * [[User:PPelberg (WMF)/Greenhouse|Peter's Greenhouse]] * [[User:KSiebert (WMF)/Greenhouse|Karolin's GreenHouse]] * [[User:NKohli (WMF)/Greenhouse|Niharika's Greenhouse]] * [[User:IHurbainPalatin (WMF)/Greenhouse|Isabelle's Greenhouse]] * [https://www.mediawiki.org/wiki/User:SPatel_(WMF)/Greenhouse?useskin=vector-2022 Sneha's Greenhouse] * NAME == Background == We are using the "greenhouse" and "forest" metaphors to help us create a shared language around the practice of developing ideas and the experiences that come along with it. To this end, we find the "greenhouse" and "forest" concepts as helpful for establishing: * '''Ideas are living organisms with finite and varied lifespans'''. We expect a small percentage of what we plant in our greenhouses to outgrow them and take root in the wild. * '''Ideas start out fragile.''' We understand that young ideas require special care before we can expect them to be valuable and definitive enough to thrive in the wild. * '''Location matters.''' Ideas need to be nurtured and grown proximate to the environments they are meant to eventually thrive within. * '''Ideas need sunlight.''' We recognize that greenhouses need to be clear so that sunlight can make its way inside. This means we accept the vulnerability that can come with anyone being able to see what we are attempting to grow in our greenhouses at any point in time. * '''Ideas need fresh air.''' We commit to bringing ideas into contact with the outside world, else pathogens may accumulate that will harm their development and make them unfit for life in the wild. == References == Volunteers across the Movement have long been working to incubate new ideas and develop shared language around the practices involved with doing so. This experiment would not be possible without them. Some of the projects and writing we have been inspired by are listed below. If there is a project and or resource you think we should be aware of, please add it here: * [[wikispore:Main_Page|WikiSpore]] * [[incubator:Incubator:Main_Page|Wikimedia Incubator]] * [[:en:Wikipedia:WikiFarmer|WikiFarmer]] * [[metawiki:Grants:IdeaLab|Grants:IdeaLab]] * [[metawiki:Wishlists|Wishlists]] * [[metawiki:Grants:Project/Rapid/Browse applications|Grants:Project/Rapid/Browse applications]] * [[metawiki:Grants:Project/Browse applications|Grants:Project/Browse applications]] * [[metawiki:Category:Proposed research projects|Category:Proposed research projects]] * [[metawiki:Proposals for new projects|Proposals for new projects]] (ideas for entirely new wiki-sister-projects) * [[:en:User:Cscott/Ideas|User:Cscott/Ideas]] * [https://office.wikimedia.org/wiki/User:Quiddity_(WMF)#Features_we_want User:Quiddity_(WMF)#Features_we_want] (private wiki) * [[Wikimedia_User_Interface/Concepts]] by [[User:TheDJ]] snzylu4pf85gkuhyvlglkbvgmdbva70 Manual:Pywikibot/category redirect.py/ru 100 1590485 5387862 5340866 2022-07-29T10:22:53Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> '''category_redirect.py''' is a {{ll|Manual:Pywikibot|Pywikibot}} script used to move pages out of redirected categories. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The bot will look for categories that are marked with a category redirect template, take the first parameter of the template as the target of the redirect, and move all pages and subcategories of the category there. It also changes hard redirects into soft redirects, and fixes double redirects. A log is written under &lt;userpage>/category_redirect_log. Only category pages that haven't been edited for a certain cooldown period (7 days by default) are taken into account. </div> Допускаются следующие дополнительные условия: {{Pywikibot command table beginning}} {{option|delay:#|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set an amount of days. If the category is edited more recenty than given days, ignore it. Default is 7</span>}} {{option|tiny|2=<span lang="en" dir="ltr" class="mw-content-ltr">Only loops over [[:d:Q8099903|Category:Wikipedia non-empty soft redirected categories]] and moves all images, pages and categories in redirect categories to the target category</span>}} {{Pywikibot command table end}} == Использование == <syntaxhighlight lang=shell-session> $ python pwb.py category_redirect [options] </syntaxhighlight> {{Manual:Pywikibot/Global Options}} [[Category:Pywikibot scripts{{#translation:}}|category_redirect]] 89w3vwo7mwboowuu0q1xvty19j13oyy Template:Empty section/de 10 1592756 5387897 5349839 2022-07-29T10:40:31Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = {{notice|1=Dieser Abschnitt ist leer. <span class="mw-translate-fuzzy">Du kannst MediaWiki.org helfen, indem du Inhalt hinzufügst.</span>}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> n9m56l8hv4a154wz89s9izzrs8tivtn Reading/Web/Desktop Improvements/Updates/Talk to Web/ca 0 1595829 5387103 5383447 2022-07-28T20:35:16Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/>__NOTOC__ {{Reading/Web/Desktop Improvements/Header}} <span lang="en" dir="ltr" class="mw-content-ltr">We have planned two types of meetings:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The regular ones''' are for anyone interested in the project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We share updates, gather feedback, and answer questions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is equally welcomed.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">'''The ones with the simultaneous interpretation''' are dedicated for specific Wikimedia communities.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We hope to see a good representation of those, and we'd like to focus on Vector 2022 on their wikis.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Anyone is welcomed, too.</span> '''<span lang="en" dir="ltr" class="mw-content-ltr">[https://wikimedia.zoom.us/j/5304280674 Click here to join] / [https://wikimedia.zoom.us/u/kc2hamfYz9 dial by your location] / [https://etherpad.wikimedia.org/p/web-team-office-hours notes].</span>''' <span lang="en" dir="ltr" class="mw-content-ltr">These links work for all the meetings except the one at Wikimania.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == Timeline == </div> * {{Check}}<span style="color:gray;">{{ymd|2022|7|26}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span></span> * {{ymd|2022|8|2}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Russian</span> * {{ymd|2022|8|4}}, 17:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Arabic</span> * {{ymd|2022|8|4}}, 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Spanish</span> * {{ymd|2022|8|13}}, 8:05 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">Wikimania session about Vector 2022</span> * {{ymd|2022|8|18}}, 10:00 UTC <span lang="en" dir="ltr" class="mw-content-ltr">(tentative)</span> - <span lang="en" dir="ltr" class="mw-content-ltr">meeting with simultaneous interpretation in Chinese</span> * {{ymd|2022|8|23}}, 12:00 {{int|and}} 19:00 UTC - <span lang="en" dir="ltr" class="mw-content-ltr">regular meeting</span> <gallery mode="packed" heights="100px"> File:WP20Symbols community1.svg File:WP20 Symbol knowledge transfer.svg File:Wikipedia20 symbol community.svg File:WP20Symbols MediaWiki.svg </gallery> {{hidden |1=Arxiu |2= {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/26-07-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/28-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/13-06-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/17-05-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-04-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/29-03-2022}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-10-2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/Wikimania 2021}} {{:Reading/Web/Desktop Improvements/Updates/Talk to Web/12-08-2021}} }} 1en4vg497rtiy1wjbf8luo2o3vxtocr Help:Extension:UniversalLanguageSelector/Input methods/kbp-tilde/de 12 1603281 5386723 5378145 2022-07-28T18:48:26Z ThisCarthing 17456337 Created page with "Klicke "..." am Ende der Liste. Ein Menü wird erscheinen." wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> You can type in the Kabɩyɛ (Kabiye) alphabet with all the special letters! </div> Geh wie gefolgt vor, um dieses Tastaturlayout zu aktivieren: # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. # <span lang="en" dir="ltr" class="mw-content-ltr">If "Kabɩyɛ" appears at the top of the list, select "Kabɩyɛ tilde".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "Kabɩyɛ" doesn't appear at the top of the list, do the following:</span> ## Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. ## <span lang="en" dir="ltr" class="mw-content-ltr">Find "Kabɩyɛ" in the panel. Click it.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "Kabɩyɛ tilde".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the Kabɩyɛ keyboard, repeat the steps listed above. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To type Kabɩyɛ letters, type the tilde (<code>~</code>), and after it type the Latin letter from the following table. For example, to type Ɖ, type ~ and then D. The full list: </div> {| class="wikitable" style="text-align: center" !Um diesen Buchstaben zu tippen... !Tippe diese Tastaturtasten: |- |Ɖ |~D |- |ɖ |~d |- |Ɛ |~E |- |ɛ |~e |- |Ɣ |~G |- |ɣ |~g |- |Ɩ |~I |- |ɩ |~i |- |Ŋ |~N |- |ŋ |~n |- |Ɔ |~O |- |ɔ |~o |- |Ʋ |~V |- |ʋ |~v |} <span lang="en" dir="ltr" class="mw-content-ltr">To type accents above the letters, type the letter, and then type tilde (<code>~</code>) followed by <code>/</code>, <code>\</code>, or <code>{</code>. Examples:</span> {| class="wikitable" style="text-align: center" !Um diesen Buchstaben zu tippen... !Tippe diese Tastaturtasten: |- |ɛ̀ |~e~\ |- |è |e~\ |- |ɛ́ |~e~/ |- |é |e~/ |- |ñ |n~{ |} 4s7vaw86420i3gq1g17se2hh29ey1xt 5386725 5386723 2022-07-28T18:48:35Z ThisCarthing 17456337 Created page with "Finde "Kabɩyɛ" in dem Menü. Klicke es." wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> You can type in the Kabɩyɛ (Kabiye) alphabet with all the special letters! </div> Geh wie gefolgt vor, um dieses Tastaturlayout zu aktivieren: # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. # <span lang="en" dir="ltr" class="mw-content-ltr">If "Kabɩyɛ" appears at the top of the list, select "Kabɩyɛ tilde".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "Kabɩyɛ" doesn't appear at the top of the list, do the following:</span> ## Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. ## Finde "Kabɩyɛ" in dem Menü. Klicke es. ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "Kabɩyɛ tilde".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the Kabɩyɛ keyboard, repeat the steps listed above. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To type Kabɩyɛ letters, type the tilde (<code>~</code>), and after it type the Latin letter from the following table. For example, to type Ɖ, type ~ and then D. The full list: </div> {| class="wikitable" style="text-align: center" !Um diesen Buchstaben zu tippen... !Tippe diese Tastaturtasten: |- |Ɖ |~D |- |ɖ |~d |- |Ɛ |~E |- |ɛ |~e |- |Ɣ |~G |- |ɣ |~g |- |Ɩ |~I |- |ɩ |~i |- |Ŋ |~N |- |ŋ |~n |- |Ɔ |~O |- |ɔ |~o |- |Ʋ |~V |- |ʋ |~v |} <span lang="en" dir="ltr" class="mw-content-ltr">To type accents above the letters, type the letter, and then type tilde (<code>~</code>) followed by <code>/</code>, <code>\</code>, or <code>{</code>. Examples:</span> {| class="wikitable" style="text-align: center" !Um diesen Buchstaben zu tippen... !Tippe diese Tastaturtasten: |- |ɛ̀ |~e~\ |- |è |e~\ |- |ɛ́ |~e~/ |- |é |e~/ |- |ñ |n~{ |} qqi2mqhjiny91t9u94x787fdyeyg690 5386728 5386725 2022-07-28T18:49:04Z ThisCarthing 17456337 Created page with "Du kannst im Kabɩyɛ (Kabiye)-Alphabet mit allen Spezialbuchstaben tippen!" wikitext text/x-wiki <languages /> Du kannst im Kabɩyɛ (Kabiye)-Alphabet mit allen Spezialbuchstaben tippen! Geh wie gefolgt vor, um dieses Tastaturlayout zu aktivieren: # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. # <span lang="en" dir="ltr" class="mw-content-ltr">If "Kabɩyɛ" appears at the top of the list, select "Kabɩyɛ tilde".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "Kabɩyɛ" doesn't appear at the top of the list, do the following:</span> ## Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. ## Finde "Kabɩyɛ" in dem Menü. Klicke es. ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "Kabɩyɛ tilde".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the Kabɩyɛ keyboard, repeat the steps listed above. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To type Kabɩyɛ letters, type the tilde (<code>~</code>), and after it type the Latin letter from the following table. For example, to type Ɖ, type ~ and then D. The full list: </div> {| class="wikitable" style="text-align: center" !Um diesen Buchstaben zu tippen... !Tippe diese Tastaturtasten: |- |Ɖ |~D |- |ɖ |~d |- |Ɛ |~E |- |ɛ |~e |- |Ɣ |~G |- |ɣ |~g |- |Ɩ |~I |- |ɩ |~i |- |Ŋ |~N |- |ŋ |~n |- |Ɔ |~O |- |ɔ |~o |- |Ʋ |~V |- |ʋ |~v |} <span lang="en" dir="ltr" class="mw-content-ltr">To type accents above the letters, type the letter, and then type tilde (<code>~</code>) followed by <code>/</code>, <code>\</code>, or <code>{</code>. Examples:</span> {| class="wikitable" style="text-align: center" !Um diesen Buchstaben zu tippen... !Tippe diese Tastaturtasten: |- |ɛ̀ |~e~\ |- |è |e~\ |- |ɛ́ |~e~/ |- |é |e~/ |- |ñ |n~{ |} 0axe6s44efrvphgeccb22bo86izjssl Help:Extension:UniversalLanguageSelector/Input methods/nqo-transliteration/de 12 1603353 5386746 5374870 2022-07-28T18:53:18Z ThisCarthing 17456337 Created page with "Lateinischer Buchstabe" wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> It's possible to type N'Ko without installing any software. Using this method is recommended if you want to type in N'Ko, but you cannot enable an N'Ko keyboard on the computer that you are using. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This virtual keyboard layout uses transliteration: typing Latin letter with the sounds of N'Ko letters produces the N'Ko letter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Consult the table below for the complete correspondence of Latin and N'Ko letters in this layout.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you are familiar with the Latin keyboard, but you are not familiar with the standard PC or mobile N'Ko keyboard, then you should try using this keyboard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">There is also a layout based on the standard N'Ko keyboard, which is documented on the page [[Help:Extension:UniversalLanguageSelector/Input methods/nqo-standard-qwerty]]. Use any layout that is comfortable for you.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To make this layout work, follow these instructions: </div> # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. #* <span lang="en" dir="ltr" class="mw-content-ltr">If the little keyboard icon doesn't appear, do the following: Click the gear icon near the "Languages" list in the sidebar, click "Input", click "Enable input tools", and click "Apply settings".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ߒߞߏ" appears at the top of the list, select "N'Ko transliteration".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ߒߞߏ" doesn't appear at the top of the list, do the following:</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click "..." at the bottom of the list. A panel will appear.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Find "ߒߞߏ" in the panel. Click it.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "N'Ko transliteration".</span> <span lang="en" dir="ltr" class="mw-content-ltr">To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the keyboard, press Ctrl-M, or repeat the steps above.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The full list of keys and characters:</span> {| class="wikitable sortable" !Lateinischer Buchstabe !<span lang="en" dir="ltr" class="mw-content-ltr">N'Ko letter</span> |- |a |ߊ |- |b |ߓ |- |c |ߗ |- |c/ |ߩ |- |d |ߘ |- |e |ߍ |- |f |ߝ |- |g |ߜ |- |h |ߤ |- |i |ߌ |- |j |ߖ |- |j/ |ߨ |- |k |ߞ |- |l |ߟ |- |m |ߡ |- |n |ߣ |- |nn |ߠ |- |ny |ߢ |- |nyw |ߧ |- |o |ߐ |- |p |ߔ |- |q |ߔ |- |r |ߙ |- |r/ |ߪ |- |s |ߛ |- |t |ߕ |- |u |ߎ |- |v |ߴ |- |w |ߥ |- |y |ߦ |- |z |ߐ |- |E |ߋ |- |R |ߚ |- |O |ߏ |- |N |ߒ |- |1 |߁ |- |2 |߂ |- |3 |߃ |- |4 |߄ |- |5 |߅ |- |6 |߆ |- |7 |߇ |- |8 |߈ |- |9 |߉ |- |0 |߀ |- |` |ߑ |- |~ |<span dir="rtl">◌߬</span> |- | - |<span dir="rtl">◌߫</span> |- |... |߷ |- | -- | - |- |~~ |~ |- |\? |? |- |? |؟ |- |! |<span dir="rtl">◌߬</span> |- |# |<span dir="rtl">◌߰</span> |- |% |<span dir="rtl">◌߳</span> |- |< |<span dir="rtl">◌߱</span> |- |> |<span dir="rtl">◌߱</span> |- |^. |<span dir="rtl">◌߭</span> |- |^ |<span dir="rtl">◌߮</span> |- |,/ |ߺ |- |. |<span dir="rtl">◌߲</span> |- |, |߸ |- |/ |߶ |- |' |ߴ |- |" |ߵ |} 96zuzokt9hbuur5kqaxlxc27xa2mmil 5386748 5386746 2022-07-28T18:53:21Z ThisCarthing 17456337 Created page with "N'Ko-Buchstabe" wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> It's possible to type N'Ko without installing any software. Using this method is recommended if you want to type in N'Ko, but you cannot enable an N'Ko keyboard on the computer that you are using. </div> <span lang="en" dir="ltr" class="mw-content-ltr">This virtual keyboard layout uses transliteration: typing Latin letter with the sounds of N'Ko letters produces the N'Ko letter.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Consult the table below for the complete correspondence of Latin and N'Ko letters in this layout.</span> <span lang="en" dir="ltr" class="mw-content-ltr">If you are familiar with the Latin keyboard, but you are not familiar with the standard PC or mobile N'Ko keyboard, then you should try using this keyboard.</span> <span lang="en" dir="ltr" class="mw-content-ltr">There is also a layout based on the standard N'Ko keyboard, which is documented on the page [[Help:Extension:UniversalLanguageSelector/Input methods/nqo-standard-qwerty]]. Use any layout that is comfortable for you.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To make this layout work, follow these instructions: </div> # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. #* <span lang="en" dir="ltr" class="mw-content-ltr">If the little keyboard icon doesn't appear, do the following: Click the gear icon near the "Languages" list in the sidebar, click "Input", click "Enable input tools", and click "Apply settings".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ߒߞߏ" appears at the top of the list, select "N'Ko transliteration".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ߒߞߏ" doesn't appear at the top of the list, do the following:</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click "..." at the bottom of the list. A panel will appear.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Find "ߒߞߏ" in the panel. Click it.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "N'Ko transliteration".</span> <span lang="en" dir="ltr" class="mw-content-ltr">To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the keyboard, press Ctrl-M, or repeat the steps above.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The full list of keys and characters:</span> {| class="wikitable sortable" !Lateinischer Buchstabe !N'Ko-Buchstabe |- |a |ߊ |- |b |ߓ |- |c |ߗ |- |c/ |ߩ |- |d |ߘ |- |e |ߍ |- |f |ߝ |- |g |ߜ |- |h |ߤ |- |i |ߌ |- |j |ߖ |- |j/ |ߨ |- |k |ߞ |- |l |ߟ |- |m |ߡ |- |n |ߣ |- |nn |ߠ |- |ny |ߢ |- |nyw |ߧ |- |o |ߐ |- |p |ߔ |- |q |ߔ |- |r |ߙ |- |r/ |ߪ |- |s |ߛ |- |t |ߕ |- |u |ߎ |- |v |ߴ |- |w |ߥ |- |y |ߦ |- |z |ߐ |- |E |ߋ |- |R |ߚ |- |O |ߏ |- |N |ߒ |- |1 |߁ |- |2 |߂ |- |3 |߃ |- |4 |߄ |- |5 |߅ |- |6 |߆ |- |7 |߇ |- |8 |߈ |- |9 |߉ |- |0 |߀ |- |` |ߑ |- |~ |<span dir="rtl">◌߬</span> |- | - |<span dir="rtl">◌߫</span> |- |... |߷ |- | -- | - |- |~~ |~ |- |\? |? |- |? |؟ |- |! |<span dir="rtl">◌߬</span> |- |# |<span dir="rtl">◌߰</span> |- |% |<span dir="rtl">◌߳</span> |- |< |<span dir="rtl">◌߱</span> |- |> |<span dir="rtl">◌߱</span> |- |^. |<span dir="rtl">◌߭</span> |- |^ |<span dir="rtl">◌߮</span> |- |,/ |ߺ |- |. |<span dir="rtl">◌߲</span> |- |, |߸ |- |/ |߶ |- |' |ߴ |- |" |ߵ |} laamrpccv9p0b0zww5t5u19sx42uusd Help:Extension:UniversalLanguageSelector/Input methods/nqo-standard-qwerty/de 12 1603355 5386751 5374900 2022-07-28T18:53:47Z ThisCarthing 17456337 Created page with "Klicke "..." am Ende der Liste. Ein Menü wird erscheinen." wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> It's possible to type N'Ko without installing any software. Using this method is recommended if you want to type in N'Ko, but you cannot enable an N'Ko keyboard on the computer that you are using. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This virtual keyboard layout emulates the common N'Ko layout on PCs and in common mobile keyboard apps. If you are accustomed to typing it on such a layout and can type it quickly, you should probably use this one. There is also a transliteration layout, which is documented on the page [[Help:Extension:UniversalLanguageSelector/Input methods/nqo-transliteration]]. Use any layout that is comfortable for you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To make this layout work, follow these instructions: </div> # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. #* <span lang="en" dir="ltr" class="mw-content-ltr">If the little keyboard icon doesn't appear, do the following: Click the gear icon near the "Languages" list in the sidebar, click "Input", click "Enable input tools", and click "Apply settings".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ߒߞߏ" appears at the top of the list, select "N'Ko standard QWERTY".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ߒߞߏ" doesn't appear at the top of the list, do the following:</span> ## Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. ## <span lang="en" dir="ltr" class="mw-content-ltr">Find "ߒߞߏ" in the panel. Click it.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "N'Ko standard QWERTY".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the keyboard, press Ctrl-M, or repeat the steps above. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that this will only work if your operating system's keyboard layout is an English U.S. QWERTY layout. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The full list of keys and characters: </div> {| class="wikitable sortable" !Lateinischer Buchstabe !N'Ko-Buchstabe |- |q |ߔ |- |w |ߧ |- |e |ߠ |- |r |ߥ |- |t |ߦ |- |y |ߙ |- |u |ߗ |- |i |ߜ |- |o |ߢ |- |p |ߡ |- |[ |ߤ |- |] |ߒ |- |a |ߏ |- |s |ߎ |- |d |ߍ |- |f |ߌ |- |g |ߋ |- |h |ߊ |- |j |ߖ |- |k |ߝ |- |l |ߣ |- |; |ߕ |- |' |ߓ |- |z |ߐ |- |x |<span dir="rtl">◌߲</span> |- |c |ߵ |- |v |ߴ |- |b |<span dir="rtl">◌߬</span> |- |n |<span dir="rtl">◌߫</span> |- |m |ߟ |- |, |ߛ |- |. |ߘ |- |/ |ߞ |- |Q |ߩ |- |W |ߨ |- |Y |ߚ |- |I |÷ |- |O |× |- |P |ߪ |- |A |߶ |- |D |[ |- |F |] |- |G |( |- |H |) |- |J |ߺ |- |L |/ |- |Z |<span dir="rtl">◌߳</span> |- |X |<span dir="rtl">◌߱</span> |- |C |<span dir="rtl">◌߭</span> |- |V |<span dir="rtl">◌߮</span> |- |B |<span dir="rtl">◌߰</span> |- |N |<span dir="rtl">◌߯</span> |- |M |߸ |- |< |ߑ |- |? |؟ |- |` |߷ |- |1 |߁ |- |2 |߂ |- |3 |߃ |- |4 |߄ |- |5 |߅ |- |6 |߆ |- |7 |߇ |- |8 |߈ |- |9 |߉ |- |0 |߀ |} 16brhthejxq46xxc5v9bs3xkgamrg5e 5386753 5386751 2022-07-28T18:53:53Z ThisCarthing 17456337 Created page with "Die volle Liste von Tasten und Zeichen:" wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> It's possible to type N'Ko without installing any software. Using this method is recommended if you want to type in N'Ko, but you cannot enable an N'Ko keyboard on the computer that you are using. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This virtual keyboard layout emulates the common N'Ko layout on PCs and in common mobile keyboard apps. If you are accustomed to typing it on such a layout and can type it quickly, you should probably use this one. There is also a transliteration layout, which is documented on the page [[Help:Extension:UniversalLanguageSelector/Input methods/nqo-transliteration]]. Use any layout that is comfortable for you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To make this layout work, follow these instructions: </div> # Klicke das Suchfeld oben in der Seite. # Klicke auf das kleine Tastatursymbol, das in der Nähe des Suchfelds erscheint. #* <span lang="en" dir="ltr" class="mw-content-ltr">If the little keyboard icon doesn't appear, do the following: Click the gear icon near the "Languages" list in the sidebar, click "Input", click "Enable input tools", and click "Apply settings".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ߒߞߏ" appears at the top of the list, select "N'Ko standard QWERTY".</span> # <span lang="en" dir="ltr" class="mw-content-ltr">If "ߒߞߏ" doesn't appear at the top of the list, do the following:</span> ## Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. ## <span lang="en" dir="ltr" class="mw-content-ltr">Find "ߒߞߏ" in the panel. Click it.</span> ## <span lang="en" dir="ltr" class="mw-content-ltr">Click the little keyboard icon again, and select "N'Ko standard QWERTY".</span> <div lang="en" dir="ltr" class="mw-content-ltr"> To disable this special keyboard and go back to type usually, click the little keyboard icon and then click "Use native keyboard", or press Ctrl-M. To re-enable the keyboard, press Ctrl-M, or repeat the steps above. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Note that this will only work if your operating system's keyboard layout is an English U.S. QWERTY layout. </div> Die volle Liste von Tasten und Zeichen: {| class="wikitable sortable" !Lateinischer Buchstabe !N'Ko-Buchstabe |- |q |ߔ |- |w |ߧ |- |e |ߠ |- |r |ߥ |- |t |ߦ |- |y |ߙ |- |u |ߗ |- |i |ߜ |- |o |ߢ |- |p |ߡ |- |[ |ߤ |- |] |ߒ |- |a |ߏ |- |s |ߎ |- |d |ߍ |- |f |ߌ |- |g |ߋ |- |h |ߊ |- |j |ߖ |- |k |ߝ |- |l |ߣ |- |; |ߕ |- |' |ߓ |- |z |ߐ |- |x |<span dir="rtl">◌߲</span> |- |c |ߵ |- |v |ߴ |- |b |<span dir="rtl">◌߬</span> |- |n |<span dir="rtl">◌߫</span> |- |m |ߟ |- |, |ߛ |- |. |ߘ |- |/ |ߞ |- |Q |ߩ |- |W |ߨ |- |Y |ߚ |- |I |÷ |- |O |× |- |P |ߪ |- |A |߶ |- |D |[ |- |F |] |- |G |( |- |H |) |- |J |ߺ |- |L |/ |- |Z |<span dir="rtl">◌߳</span> |- |X |<span dir="rtl">◌߱</span> |- |C |<span dir="rtl">◌߭</span> |- |V |<span dir="rtl">◌߮</span> |- |B |<span dir="rtl">◌߰</span> |- |N |<span dir="rtl">◌߯</span> |- |M |߸ |- |< |ߑ |- |? |؟ |- |` |߷ |- |1 |߁ |- |2 |߂ |- |3 |߃ |- |4 |߄ |- |5 |߅ |- |6 |߆ |- |7 |߇ |- |8 |߈ |- |9 |߉ |- |0 |߀ |} mwd35nfg73yqspg1d2wxhmhdbw4riv1 Help:Extension:WikiEditor/Realtime Preview 12 1604995 5386868 5384408 2022-07-28T19:32:34Z NRodriguez (WMF) 17476091 adding better link wikitext text/x-wiki <languages/> {{distinguish|Manual:Live preview}} <translate><!--T:1--> '''Realtime Preview''' is a feature within [[<tvar name=1>Special:MyLanguage/Extension:WikiEditor</tvar>|WikiEditor]] that allows you to preview your changes in realtime as you are typing.</translate> <translate><!--T:2--> It was created by the Wikimedia Foundation's [[<tvar name=1>meta:Special:MyLanguage/Community Tech</tvar>|Community Tech team]] in response to the [[metawiki:Community_Wishlist_Survey_2021/Real_Time_Preview_for_Wikitext|#4 wish]] in the 2021 Community Wishlist Survey.</translate> <translate> == Usage == <!--T:3--> </translate> <translate><!--T:4--> First make sure you have [[<tvar name=1>Special:MyLanguage/Extension:WikiEditor</tvar>|WikiEditor]] enabled.</translate> <translate><!--T:5--> In your <tvar name=1>[[Special:Preferences#mw-prefsection-editing|{{int|preferences}}]]</tvar>, look for the "<tvar name=2>{{int|wikieditor-toolbar-preference}}</tvar>" preference.</translate> <translate><!--T:6--> Note that Realtime Preview is not compatible with the <tvar name=1>{{ll|2017 wikitext editor}}</tvar>.</translate> <translate><!--T:7--> Begin an edit.</translate> <translate><!--T:8--> Notice that in the toolbar, you will see a "<tvar name=1>{{int|wikieditor-realtimepreview-preview}}</tvar>" button.</translate> <translate><!--T:9--> Clicking this will activate Realtime Preview.</translate> <translate><!--T:10--> Once activated, a preview pane is shown next to the editor.</translate> <translate><!--T:11--> It will update anytime you stop typing.</translate> <translate><!--T:12--> You can also hover over the preview area and click on the "<tvar name=1>{{int|wikieditor-realtimepreview-reload}}</tvar>" button to manually reload changes, or use the "<tvar name=2>{{:MediaWiki:accesskey-wikieditor-realtimepreview}}</tvar>" [[<tvar name=3>Manual:Access keys</tvar>|access key]].</translate> <translate> == Limitations == <!--T:13--> </translate> * <translate><!--T:14--> Absolutely positioned elements are shown relative to the preview area and not the entire page. If you need to test what your changes look like for the entire page, use the normal "<tvar name=1>{{int|showpreview}}</tvar>" button.</translate> ([[phab:T310064]]) * <translate><!--T:15--> When using both Realtime Preview and the normal preview, some user interaction requiring JavaScript might apply to only one preview area and not the other, such as the "show" and "hide" links on collapsible content.</translate> ([[phab:T307475]]) * <translate><!--T:16--> If your browser window is too narrow, the feature is automatically disabled and you will have to use the normal "<tvar name=1>{{int|showpreview}}</tvar>" button to preview your changes.</translate> kxag37yvlfrlvgmbivze2d4899529tj 5387138 5386868 2022-07-28T21:05:56Z Shirayuki 472859 restore translation units wikitext text/x-wiki <languages/> {{distinguish|Manual:Live preview}} <translate><!--T:1--> '''Realtime Preview''' is a feature within [[<tvar name=1>Special:MyLanguage/Extension:WikiEditor</tvar>|WikiEditor]] that allows you to preview your changes in realtime as you are typing.</translate> <translate><!--T:2--> It was created by the Wikimedia Foundation's [[<tvar name=1>meta:Special:MyLanguage/Community Tech</tvar>|Community Tech team]] in response to the [[<tvar name=2>m:Special:MyLanguage/Community Wishlist Survey 2021/Real Time Preview for Wikitext</tvar>|#4 wish]] in the 2021 Community Wishlist Survey.</translate> <translate> == Usage == <!--T:3--> </translate> <translate><!--T:4--> First make sure you have [[<tvar name=1>Special:MyLanguage/Extension:WikiEditor</tvar>|WikiEditor]] enabled.</translate> <translate><!--T:5--> In your <tvar name=1>[[Special:Preferences#mw-prefsection-editing|{{int|preferences}}]]</tvar>, look for the "<tvar name=2>{{int|wikieditor-toolbar-preference}}</tvar>" preference.</translate> <translate><!--T:6--> Note that Realtime Preview is not compatible with the <tvar name=1>{{ll|2017 wikitext editor}}</tvar>.</translate> <translate><!--T:7--> Begin an edit.</translate> <translate><!--T:8--> Notice that in the toolbar, you will see a "<tvar name=1>{{int|wikieditor-realtimepreview-preview}}</tvar>" button.</translate> <translate><!--T:9--> Clicking this will activate Realtime Preview.</translate> <translate><!--T:10--> Once activated, a preview pane is shown next to the editor.</translate> <translate><!--T:11--> It will update anytime you stop typing.</translate> <translate><!--T:12--> You can also hover over the preview area and click on the "<tvar name=1>{{int|wikieditor-realtimepreview-reload}}</tvar>" button to manually reload changes, or use the "<tvar name=2>{{:MediaWiki:accesskey-wikieditor-realtimepreview}}</tvar>" [[<tvar name=3>Manual:Access keys</tvar>|access key]].</translate> <translate> == Limitations == <!--T:13--> </translate> * <translate><!--T:14--> Absolutely positioned elements are shown relative to the preview area and not the entire page. If you need to test what your changes look like for the entire page, use the normal "<tvar name=1>{{int|showpreview}}</tvar>" button.</translate> ([[phab:T310064]]) * <translate><!--T:15--> When using both Realtime Preview and the normal preview, some user interaction requiring JavaScript might apply to only one preview area and not the other, such as the "show" and "hide" links on collapsible content.</translate> ([[phab:T307475]]) * <translate><!--T:16--> If your browser window is too narrow, the feature is automatically disabled and you will have to use the normal "<tvar name=1>{{int|showpreview}}</tvar>" button to preview your changes.</translate> 9lct9retcdritptnow4ju2di9j2751j Extension:EventLogging/fr 102 1605110 5387145 5381726 2022-07-28T21:07:42Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{Extension |status = stable |type1 = special |type2 = database |type3 = ContentHandler |username = Ori.livneh |description = Fournit un environnement de travail pour tracer les événements analytiques |version = mises à jour continues |update = |compatibility policy = |mediawiki = 1.33+ |php = 5.5+ |needs-updatephp = No |download = {{WikimediaDownload}} |tags = |example = |compatibility = |bugzilla = EventLogging |vagrant-role = eventlogging }} L'extension EventLogging permet de collecter des données structurées sur la manière dont les utilisateurs interagisssent avec les sites MediaWiki. == Fonctionnalités == * EventLogging prend en charge la connexion à partir du JavaScript côté client et du côté serveur à partir de PHP. * Le comportement de la connexion peut être configuré dynamiquement en utilisant {{ll|Extension:EventStreamConfig}}. * Les événements sont des objets JSON définis par des schémas JSON versionnés (JSONSchemas) enregistrés dans dépôt Git de schémas. * L'extension n'inclut aucun code du serveur pour transporter, analyser ou charger ces événements. Un service séparé, [[wikitech:Event Platform/EventGate|EventGate]], implémente cette fonction et gère l'insertion des événements dans Kafka. Les événements sont ensuite persistants dans les dépôts de données descendantes (comme Hive) via divers pipeline d'absorbsion. Les détails de ces composants sont spécifiques à la configuration de la Fondation Wikimedia. == EventLogging pour Wikimedia == La Fondation Wikimedia utilise l'extension EventLogging comme partie d'un [[wikitech:Analytics/Systems/EventLogging|système plus large de collecte, d'agrégation, d'enregistrement et d'analyse des données utilisateur]] à l'intérieur des limites fixées par notre [[m:Special:MyLanguage/Privacy policy|politique de confidentialité]] et nos [[m:Special:MyLanguage/Data retention guidelines|règles de conservation des données]]. Cette page concerne l'utilisation générale de l'extension EventLogging. La Fondation Wikimedia utilise EventLogging avec des composants arrière spécifiques à la WMF ainsi que des [https://schema.wikimedia.org/#!/ dépôts de schémas]. Pour la documentation spécifique à Wikimedia et la documentation maintenue, voir [[wikitech:Analytics/Systems/EventLogging]] et [[wikitech:Event Platform]]. ==Installation== {{ExtensionInstall|registration=required|vagrant=eventlogging|localsettings=$wgEventLoggingBaseUri = '/beacon/event'; $wgEventLoggingServiceUri = '/beacon/intake-analytics';}} === Configurer l'emplacement des schemas === Par défaut, l'extension cherche les schémas sur [[m:Special:MyLanguage/Meta-Wiki|Meta-Wiki]]. Les paramètres par défaut significatifs sont : <syntaxhighlight lang="php"> # (default) $wgEventLoggingSchemaApiUri = 'https://meta.wikimedia.org/w/api.php'; # (default) $wgEventLoggingDBname = 'metawiki'; </syntaxhighlight> Pour utiliser des schémas locaux, ou des schémas du wiki central de votre propre ferme de wikis, il faut réécrire ces lignes. Par exemple pour utiliser l'espace de noms <code>Schema</code> du wiki local, déclarez : <syntaxhighlight lang="php"> $wgEventLoggingSchemaApiUri = $wgServer . '/w/api.php'; $wgEventLoggingDBname = $wgDBname; </syntaxhighlight> (et assurez-vous que le compte utilisateur qui va créer les schémas est [[Special:MyLanguage/Manual:Autoconfirmed users|autoconfirmé]]). == Tracer les événements avec EventLogging == * {{ll|Extension:EventLogging/Guide}} - pour développer et déployer les schémas EventLogging, et plus * {{ll|Extension:EventLogging/Programming}} - conseils et suggestions pour les développeurs qui écrivent du code pour tracer les événements == Développer l'extension EventLogging == === Configuration développeur === En tant que développeur, vous voudrez configurer et utiliser EventLogging sur votre wiki de développement pour simuler son utilisation en production. ==== Utiliser Docker ==== ''Voir {{ll|MediaWiki-Docker/Configuration recipes/EventLogging}}'' ==== Utiliser mediawiki-vagrant ==== Si vous développez avec mediawiki-vagrant, tout ce dont vous avez besoin est encapsulé dans le rôle <code>eventlogging</code>. Pour l'activer, exécutez : <syntaxhighlight lang="shell-session"> $ vagrant roles enable eventlogging $ vagrant provision </syntaxhighlight> ==== Pour les développements JavaScript ==== Si vous travaillez sur le client JavaScript, vous devrez installler les dépendances avec <code>npm install</code> à partir du dossier dans lequel vous développez. Puis vous pouvez utiliser <code>npm test</code> pour exécuter ESLint par exemple. La section « Comment exécuter les tests » ci-dessous montre comment voir le résultat des tests JavaScript. <div lang="en" dir="ltr" class="mw-content-ltr"> When adding the parameter <code>trackdebug=true</code> to the URL, the console in the browser's devtools will show the event logging being triggered. </div> ==== Comment exécuter les tests ==== Il existe des tests PHP, Python, et JavaScript. Pour exécuter les tests JavaScript, visitez Special:JavaScriptTest/qunit sur votre wiki de développement. (Voir {{ll|Manual:JavaScript unit testing}}). Pour exécuter les tests PHP, nous utilisons PHPUnit. Vérifiez qu'elle est installée, puis : <syntaxhighlight lang="shell-session"> $ vagrant ssh vagrant@mediawiki-vagrant:/vagrant/mediawiki/extensions/EventLogging/tests$ php /vagrant/mediawiki/tests/phpunit/phpunit.php EventLoggingExtensionFunctionsTest.php </syntaxhighlight> {{Used by|canasta=1|miraheze=1}} [[Category:Analytics extensions{{#translation:}}]] [[Category:Statistics extensions{{#translation:}}]] h66dvj0i234n2iuynch2yzkokvqy76m Translations:Manual:Installing MediaWiki/140/ja 1198 1605296 5387249 5381359 2022-07-28T21:33:51Z Shirayuki 472859 update wikitext text/x-wiki $1 も参照してください。 6cy14cjofivxpanawb9p3rt77jryrkp Translations:Reading/Web/Desktop Improvements/Updates/Talk to Web/37/en 1198 1606008 5387102 5383099 2022-07-28T20:35:14Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki [$link Click here to join] / [$dial dial by your location] / [$notes notes]. ndzqvjfxqghcr37mqxnlk1ajg282xhz Guidelines for a healthy code review culture 0 1606099 5387743 5383558 2022-07-29T06:57:57Z KSiebert (WMF) 17519594 wikitext text/x-wiki {{Development guideline}} Code review is emotional labor: we are emotional beings who are emotionally invested in this work, down to the code that we write. Giving and receiving feedback is hard, and we must all share this load to build a healthy code review culture. On the surface, code review is about preventing things from breaking and maintaining code health. In reality, it is (and should be) much more than that. == The goals of code review == # To work together to prevent defects or vulnerabilities from making it to production code # To promote maintainability, preventing future frustration and confusion # To provide an opportunity for education so collaborators can learn and grow, and to bring in new collaborators # To foster shared understanding, ownership, and accountability of the code through collaboration, leading to a more functional and fulfilled team of contributors Ultimately, code review is a dialogue, one that is especially critical to our movement since most of our work is done remotely and asynchronously. == What makes a code review culture healthy? == {{Quote|text=A healthy code review culture is one in which feedback is welcomed without fear.|sign=Cindy Cicalese, Principal Software Engineer, Wikimedia Foundation}}Let’s break this down: * ''Feedback is welcomed'': In a healthy code review culture, getting feedback means that a defect was caught before going to production, knowledge was shared, and people worked together to make the code better. Working in this kind of culture is fulfilling. * ''Without fear'': Psychological safety is the foundation of a healthy code review culture<ref name=":0">Kadam, Aniket (1 April 2018). [https://medium.com/@anikadamg/compassionate-coding-the-secret-of-high-perfomance-teams-34a158fd1390 "Compassionate Coding: (The secret of high performance teams)"] [https://medium.com/ ''Medium.com'']</ref>. People need to feel comfortable providing and receiving feedback. Submitting a patch or providing criticism can be intimidating, and this process requires trust. People who feel safe are more able to propose new ideas, experiment, and grow. People who don’t feel safe will eventually stop contributing and leave. We can create this kind of culture by defining our values and applying them to how we work. == Values of a healthy code review culture == === Respect and empathy over ego === * '''Our code does not define us:''' Coding is what we do, not who we are. Lead with compassion: start with yourself, then extend it to everyone. We are all doing the best we can right now.<ref name=":0" /> * '''Build trust:''' Kindness, empathy, and curiosity can build relationships between collaborators. Trust leads to psychological safety, which leads to great work and happy contributors. * '''Assume competence'''<ref>Kammer, Liz; Hodges, Maggie; Murillo, Ambar (06 November 2019). [https://testing.googleblog.com/2019/11/code-health-respectful-reviews-useful.html "Code Health: Respectful Reviews == Useful Reviews"]. ''[https://testing.googleblog.com Google Testing Blog].''</ref>''':''' Ask questions rather than assuming incompetence. You might be the one who is misunderstanding something. * '''Be aware of power dynamics:''' Listen to people who have less experience than you. Lift up quiet voices. Defer to others often. === Collaboration over competition === * '''Focus on collaboration:''' When you focus on working together, egos won’t get in the way. Collaboration empowers more people to contribute and leads to a better product. * '''Acknowledge the challenges of collaboration:''' Some of us find it difficult to manage our tone, some of us struggle with letting go and deferring to solutions we don't like, and some of us withhold critical but useful feedback for fear of seeming negative. Remember that everyone is different but we can all grow. * '''Embrace feedback as a gift:''' In a healthy culture, every piece of feedback will be welcomed as something that improved the code, taught us something, or made us think. * '''Encourage curiosity and experimentation:''' In a safe environment, we can learn, innovate, and have more fun through play. * '''Disagree with humility:''' When you disagree, state your opinion respectfully, and be open to having your mind changed. Ask yourself if something really, truly matters. Be willing to give alternate solutions a chance. === How you communicate matters === * '''Consider your tone:''' Tone impacts morale. It determines whether code review is a productive, encouraging, and fulfilling process, or an intimidating, frustrating, and hurtful one. A kind, respectful, and non-judgmental tone will make people more open to constructive feedback<ref>Orosz, Gergely (30 September 2019). [https://stackoverflow.blog/2019/09/30/how-to-make-good-code-reviews-better/ How to Make Good Code Reviews Better]. [https://stackoverflow.blog/ ''The Overflow''].</ref>.  The comments “X is wrong” and “have you considered Y?” have very different effects. * '''Don’t state opinion as fact:''' You might shut down discussion. Instead… * '''Ask questions and make recommendations:''' Provide context, explain how the code could be better, and outline the impact of changing it. Provide links to documentation—doing so demonstrates that you had to look it up at least once. * '''Ask "what do you think?"'''<ref>Ciavolino, Amy (25 July 2018). [https://kickstarter.engineering/a-guide-to-mindful-communication-in-code-reviews-48aab5282e5e A Guide to Mindful Communication in Code Reviews]. [https://kickstarter.engineering/ ''Kickstarter Engineering''].</ref> and listen to the response. * '''If you do state something as fact, make sure you’re right:''' Otherwise, the code author will waste time and be frustrated. Provide references if possible. If you’re not sure about something, ask questions instead. * '''Be clear about what’s a functional defect and what’s a preference:''' You might consider [https://conventionalcomments.org/ explicitly labeling your comments as such]. * '''Express gratitude and encouragement:''' “Positivity” is a loaded term, and advice like “add praise to every review” can seem fake or unnecessary. Instead, be aware of opportunities to provide praise: if you learned something or were impressed, say so. Gratitude and encouragement can be a part of every review: even a simple “Thanks for doing this” or “Nice work!” with your +2 makes a difference, because positive feedback motivates further contributions and makes people more open to critical feedback. * '''Leave out judgment and sarcasm:''' Review the code itself, not the author. Remember that everyone makes mistakes and has room to grow, and good collaborators help each other grow. Judgmental or sarcastic comments have no place in collaborative, productive code review. * '''Be aware of people you may be silencing:''' A culture of negativity and unrelenting criticism silences important voices. === Remember the bigger picture === * '''Don’t lose sight of context:''' Instead of focusing on obscure issues or nitpicks, focus on the overall place of the code within the codebase. Consider the larger goal by asking yourself “is this feedback valuable?” Line-by-line review is important but should be done within the context of the project as a whole. You may help the project more in the long run by encouraging a contributor rather than frustrating them. * '''Understand and adapt to different review contexts:''' For a significant, complex patch authored by a seasoned contributor, refining and strengthening the technical solution might be the primary goal. For a small patch uploaded by a new contributor, inclusion and education are more important. Adapt your language and level of criticism to the context at hand. * '''Avoid leaving an avalanche of comments'''<ref name=":1">Sankarram, Sandya (19 January 2018). [https://medium.com/@sandya.sankarram/unlearning-toxic-behaviors-in-a-code-review-culture-b7c295452a3c Unlearning toxic behaviors in a code review culture]. [https://medium.com/ ''Medium''].</ref>''':''' Leaving a lot of comments at once can be overwhelming for the author, especially if done by multiple reviewers. It’s easy to feel ganged-up on. If you find yourself leaving a double-digit number of comments, especially on a smaller patch, ask yourself if these comments are really necessary or adding value. If you do have to leave a lot of comments, acknowledge this, ideally by reaching out to the author privately. Offer help and be extra kind. * '''Let go:''' Gracefully accept compromise or defeat<ref>Atwood, Jeff (09 May 2006). [https://blog.codinghorror.com/the-ten-commandments-of-egoless-programming/ The Ten Commandments of Egoless Programming]. [https://blog.codinghorror.com/ ''Coding Horror''].</ref>. If it’s not part of documented standards, prioritize the code author’s preferences. Remember that there is no such thing as perfect code: a quest for unattainable perfection leads to frustrated contributors and slow progress. Ask yourself “what’s the worst case scenario if this code gets merged as-is?” Do your best, then move on. === Thoughtful efficiency === * '''Automate:''' Everything you automate is no longer a burden during code review. Automate as much as you can, and note repeated discussions as potential opportunities for automation. * '''Aim for clarity:''' Be clear about what you consider a blocker as opposed to a matter of preference or a request for clarification. Avoid euphemisms and incomplete sentences: clearly state what you mean and what you think needs to happen. Make it clear how conflicts will be resolved. * '''Keep patches small:''' Large patches are difficult to review and may languish in code review for too long. Authors should submit small patches, but reviewers should also avoid asking for unrelated work in a patch and should err on the side of resolving issues later when possible. Big picture or architectural discussions should happen elsewhere. * '''…but provide helpful review:''' Not enough feedback is a problem, too. Cursory reviews don’t spark discussion or foster education. If sufficient reviews aren’t happening, consider why: is it a question of resourcing, social dynamics, or something else? * '''Avoid nitpicking:''' Most nitpicks are unnecessary to the ultimate goal. Follow this process: ** For any comment, ask yourself if it’s a nitpick. ** If it is, consider deleting it. ** If you must nitpick, label the comment as such and make it non-blocking. ** Consider whether that nitpick could have been identified via tooling. * '''Respond quickly:''' Critical feedback goes over better if it’s provided promptly and followed up with quick responses to questions or updated code. === Refuse to normalize toxic behavior<ref name=":1" /> === * '''Use your privilege:''' Whatever form it may take, use the authority you have to lift up your collaborators and correct or reject toxic behavior. * '''Return to values:''' When you see a problem, point it out and back it up with a reference to these values. * '''Learn from your mistakes:''' We all have room to grow—apologize sincerely and learn from your mistake, then move on. * '''Don’t adapt to a toxic culture:''' We shouldn’t waste time policing how many emoji or exclamation points we use. Instead, we should question toxic cultures. * '''Get help when you need it:''' Contact the project maintainers or [[Code of Conduct#Report a problem|submit a report]] to the Code of Conduct Committee. == Recommended reading == * [https://medium.com/@anikadamg/compassionate-coding-the-secret-of-high-perfomance-teams-34a158fd1390 Compassionate coding: The secret of high performance teams] * [https://medium.com/@sandya.sankarram/unlearning-toxic-behaviors-in-a-code-review-culture-b7c295452a3c Unlearning toxic behaviors in a code review culture] * [https://blog.codinghorror.com/the-ten-commandments-of-egoless-programming/ The ten commandments of egoless programming] * [https://stackoverflow.blog/2019/09/30/how-to-make-good-code-reviews-better/ How to make good code reviews better] * [https://kickstarter.engineering/a-guide-to-mindful-communication-in-code-reviews-48aab5282e5e A guide to mindful communication in code reviews] * [https://conventionalcomments.org/ Conventional comments] * [[Nonviolent Code Review|Non-violent code review]] == Acknowledgements == Many thanks to everyone who provided ideas, feedback, and resources that went into creating these guidelines. == References == <references /> e76m4o2tke8at9x5051t2n4zpm0i21h Translations:Reading/Web/Desktop Improvements/Updates/Talk to Web/37/pt-br 1198 1606108 5387125 5383578 2022-07-28T20:35:34Z SGrabarczuk (WMF) 9240933 wikitext text/x-wiki [$link Clique aqui para participar] / [$dial discar a partir da sua localização] / [$notes notas]. 57dv2c3pnd0ebtp4f4lf4rzm5spmn3e Help:Extension:WikiEditor/Realtime Preview/en 12 1606496 5387140 5384426 2022-07-28T21:06:11Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{distinguish|Manual:Live preview}} '''Realtime Preview''' is a feature within [[Special:MyLanguage/Extension:WikiEditor|WikiEditor]] that allows you to preview your changes in realtime as you are typing. It was created by the Wikimedia Foundation's [[meta:Special:MyLanguage/Community Tech|Community Tech team]] in response to the [[m:Special:MyLanguage/Community Wishlist Survey 2021/Real Time Preview for Wikitext|#4 wish]] in the 2021 Community Wishlist Survey. == Usage == First make sure you have [[Special:MyLanguage/Extension:WikiEditor|WikiEditor]] enabled. In your [[Special:Preferences#mw-prefsection-editing|{{int|preferences}}]], look for the "{{int|wikieditor-toolbar-preference}}" preference. Note that Realtime Preview is not compatible with the {{ll|2017 wikitext editor}}. Begin an edit. Notice that in the toolbar, you will see a "{{int|wikieditor-realtimepreview-preview}}" button. Clicking this will activate Realtime Preview. Once activated, a preview pane is shown next to the editor. It will update anytime you stop typing. You can also hover over the preview area and click on the "{{int|wikieditor-realtimepreview-reload}}" button to manually reload changes, or use the "{{:MediaWiki:accesskey-wikieditor-realtimepreview}}" [[Manual:Access keys|access key]]. == Limitations == * Absolutely positioned elements are shown relative to the preview area and not the entire page. If you need to test what your changes look like for the entire page, use the normal "{{int|showpreview}}" button. ([[phab:T310064]]) * When using both Realtime Preview and the normal preview, some user interaction requiring JavaScript might apply to only one preview area and not the other, such as the "show" and "hide" links on collapsible content. ([[phab:T307475]]) * If your browser window is too narrow, the feature is automatically disabled and you will have to use the normal "{{int|showpreview}}" button to preview your changes. 3jd3wh056c6f4vqmvamb0rxg8vpu1o0 Help:Extension:WikiEditor/Realtime Preview/de 12 1606507 5387139 5384462 2022-07-28T21:06:11Z FuzzyBot 451990 Updating to match new version of source page wikitext text/x-wiki <languages/> {{distinguish|Manual:Live preview}} <span lang="en" dir="ltr" class="mw-content-ltr">'''Realtime Preview''' is a feature within [[Special:MyLanguage/Extension:WikiEditor|WikiEditor]] that allows you to preview your changes in realtime as you are typing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It was created by the Wikimedia Foundation's [[meta:Special:MyLanguage/Community Tech|Community Tech team]] in response to the [[m:Special:MyLanguage/Community Wishlist Survey 2021/Real Time Preview for Wikitext|#4 wish]] in the 2021 Community Wishlist Survey.</span> == Verwendung == Stelle zuerst sicher, dass du den [[Special:MyLanguage/Extension:WikiEditor|WikiEditor]] aktiviert hast. Suche in deinen [[Special:Preferences#mw-prefsection-editing|{{int|preferences}}]] für die Einstellung "{{int|wikieditor-toolbar-preference}}". Bemerke, das die Echtzeitvorschau nicht mit den {{ll|2017 wikitext editor}} kompatibel ist. Fange eine Bearbeitung an. Du kannst nun bemerken, dass du einen "{{int|wikieditor-realtimepreview-preview}}"-Knopf in der Werkzeugleiste finden kannst. <span lang="en" dir="ltr" class="mw-content-ltr">Clicking this will activate Realtime Preview.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Once activated, a preview pane is shown next to the editor.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It will update anytime you stop typing.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You can also hover over the preview area and click on the "{{int|wikieditor-realtimepreview-reload}}" button to manually reload changes, or use the "{{:MediaWiki:accesskey-wikieditor-realtimepreview}}" [[Manual:Access keys|access key]].</span> == Beschränkungen == * <span lang="en" dir="ltr" class="mw-content-ltr">Absolutely positioned elements are shown relative to the preview area and not the entire page. If you need to test what your changes look like for the entire page, use the normal "{{int|showpreview}}" button.</span> ([[phab:T310064]]) * <span lang="en" dir="ltr" class="mw-content-ltr">When using both Realtime Preview and the normal preview, some user interaction requiring JavaScript might apply to only one preview area and not the other, such as the "show" and "hide" links on collapsible content.</span> ([[phab:T307475]]) * <span lang="en" dir="ltr" class="mw-content-ltr">If your browser window is too narrow, the feature is automatically disabled and you will have to use the normal "{{int|showpreview}}" button to preview your changes.</span> srg0ogwjw868txvu3mjy0gc1yj10zij Inuka team/gpe 0 1606646 5386460 5385143 2022-07-28T14:24:30Z DaSupremo 1532535 Created page with "[[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top." wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. <span lang="en" dir="ltr" class="mw-content-ltr">Wikipedia Preview on partner websites would allow their readers to gain context while reading their pages and help people gain contextual knowledge from Wikipedia without necessarily clicking through to Wikipedia and learn more on Wikipedia with the option being available to read more on Wikipedia.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Similar to page previews but for external sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The code can be integrated into the site or if the external site uses Wordpress then they can use the Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikipedia for KaiOS|Wikipedia for KAIOS]] a Wikipedia reading app for smart feature phones. Released in 2 versions - 1) for India 2) for rest of the world.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]].</span> == Design Research == * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes in Indonesia with existing contributors gathered feedback from Indonesian editor communities on early concepts and designs for Wikistories, focusing on the experiences of potential Wikistories creators coming from the editing community</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] in Kenya, Nigeria and South Africa with new/potential contributors investigated the behavior of content creators and consumers in three African countries with distinct user behaviors and context especially relating to Wikimedia.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] to understand why and how these users use these phones.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We learnt that users chose to purchase these phones because they're affordable and allow access to apps like smartphones do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] 7l6k48q5i9vghv0w8id62cjwjj0zvjo 5386489 5386460 2022-07-28T14:39:05Z DaSupremo 1532535 Created page with "Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top." wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. <span lang="en" dir="ltr" class="mw-content-ltr">Similar to page previews but for external sites.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The code can be integrated into the site or if the external site uses Wordpress then they can use the Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikipedia for KaiOS|Wikipedia for KAIOS]] a Wikipedia reading app for smart feature phones. Released in 2 versions - 1) for India 2) for rest of the world.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]].</span> == Design Research == * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes in Indonesia with existing contributors gathered feedback from Indonesian editor communities on early concepts and designs for Wikistories, focusing on the experiences of potential Wikistories creators coming from the editing community</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] in Kenya, Nigeria and South Africa with new/potential contributors investigated the behavior of content creators and consumers in three African countries with distinct user behaviors and context especially relating to Wikimedia.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] to understand why and how these users use these phones.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We learnt that users chose to purchase these phones because they're affordable and allow access to apps like smartphones do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] 3sen2jjxlh6zlg5111yzpthrfnpcmm9 5386491 5386489 2022-07-28T14:39:50Z DaSupremo 1532535 Created page with "E be similar to page previews nanso give external sites." wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. <span lang="en" dir="ltr" class="mw-content-ltr">The code can be integrated into the site or if the external site uses Wordpress then they can use the Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikipedia for KaiOS|Wikipedia for KAIOS]] a Wikipedia reading app for smart feature phones. Released in 2 versions - 1) for India 2) for rest of the world.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]].</span> == Design Research == * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes in Indonesia with existing contributors gathered feedback from Indonesian editor communities on early concepts and designs for Wikistories, focusing on the experiences of potential Wikistories creators coming from the editing community</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] in Kenya, Nigeria and South Africa with new/potential contributors investigated the behavior of content creators and consumers in three African countries with distinct user behaviors and context especially relating to Wikimedia.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] to understand why and how these users use these phones.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We learnt that users chose to purchase these phones because they're affordable and allow access to apps like smartphones do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] hovm5znn9o1pudp0d9xih1fvh73jejy 5386493 5386491 2022-07-28T14:40:53Z DaSupremo 1532535 Created page with "Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]]" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikipedia for KaiOS|Wikipedia for KAIOS]] a Wikipedia reading app for smart feature phones. Released in 2 versions - 1) for India 2) for rest of the world.</span> <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]].</span> == Design Research == * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes in Indonesia with existing contributors gathered feedback from Indonesian editor communities on early concepts and designs for Wikistories, focusing on the experiences of potential Wikistories creators coming from the editing community</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] in Kenya, Nigeria and South Africa with new/potential contributors investigated the behavior of content creators and consumers in three African countries with distinct user behaviors and context especially relating to Wikimedia.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] to understand why and how these users use these phones.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We learnt that users chose to purchase these phones because they're affordable and allow access to apps like smartphones do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] ln8a2us1dg8yztfiyhmj7twzxindmeh 5386495 5386493 2022-07-28T14:42:00Z DaSupremo 1532535 Created page with "[[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world." wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]].</span> == Design Research == * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes in Indonesia with existing contributors gathered feedback from Indonesian editor communities on early concepts and designs for Wikistories, focusing on the experiences of potential Wikistories creators coming from the editing community</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] in Kenya, Nigeria and South Africa with new/potential contributors investigated the behavior of content creators and consumers in three African countries with distinct user behaviors and context especially relating to Wikimedia.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] to understand why and how these users use these phones.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We learnt that users chose to purchase these phones because they're affordable and allow access to apps like smartphones do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] p5ve9drxc8xmt3988ebyndqofdykpyq 5386498 5386495 2022-07-28T14:42:08Z DaSupremo 1532535 Created page with "[[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]." wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes in Indonesia with existing contributors gathered feedback from Indonesian editor communities on early concepts and designs for Wikistories, focusing on the experiences of potential Wikistories creators coming from the editing community</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] in Kenya, Nigeria and South Africa with new/potential contributors investigated the behavior of content creators and consumers in three African countries with distinct user behaviors and context especially relating to Wikimedia.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] to understand why and how these users use these phones.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We learnt that users chose to purchase these phones because they're affordable and allow access to apps like smartphones do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] 5lg9d481vdosvbb79fhmo3glh89tpim 5386505 5386498 2022-07-28T14:44:47Z DaSupremo 1532535 Created page with "[[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * <span lang="en" dir="ltr" class="mw-content-ltr">[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] in Kenya, Nigeria and South Africa with new/potential contributors investigated the behavior of content creators and consumers in three African countries with distinct user behaviors and context especially relating to Wikimedia.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] to understand why and how these users use these phones.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We learnt that users chose to purchase these phones because they're affordable and allow access to apps like smartphones do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] qh3tjlb2dca1habefnftawda1gsub4i 5386514 5386505 2022-07-28T14:50:01Z DaSupremo 1532535 Created page with "[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia." wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. <span lang="en" dir="ltr" class="mw-content-ltr">We learnt that users chose to purchase these phones because they're affordable and allow access to apps like smartphones do.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] aopx2dsy9ahs9ta975pq8vdco2illtx 5386518 5386514 2022-07-28T14:50:29Z DaSupremo 1532535 Created page with "We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do." wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. <span lang="en" dir="ltr" class="mw-content-ltr">We also learned the challenges they face trying to read Wikipedia within the native mobile browser.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] 0nfik6v08bf1xyil5zu82ifdzc76awj 5386520 5386518 2022-07-28T14:51:41Z DaSupremo 1532535 Created page with "We sanso mo de challenge dem dey face" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] o4opw4whlaj0qbnbupty63ou2jmdsn5 5386526 5386520 2022-07-28T14:52:30Z DaSupremo 1532535 wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. <span lang="en" dir="ltr" class="mw-content-ltr">Challenges included ability to scroll through content, text size on the screen, searching for content and lack of awareness that Wikipedia content is available in multiple languages</span> == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] 190csk1wl365axi1fd76zihs8qslmxe 5386534 5386526 2022-07-28T14:54:50Z DaSupremo 1532535 Created page with "Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Follow our work == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] tgezdv0jxb5omxc3kayulcg8277sp5z 5386536 5386534 2022-07-28T14:55:04Z DaSupremo 1532535 Created page with "== Follow wanna work ==" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> == Follow wanna work == * <span lang="en" dir="ltr" class="mw-content-ltr">Monthly/Quarterly status updates on project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]]</span> * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] 1w1ro6wgy24zyrw9ed3qyckiu9lyfgo 5386538 5386536 2022-07-28T14:55:26Z DaSupremo 1532535 Created page with "Monthly/Quarterly status updates for project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]] top" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> == Follow wanna work == * Monthly/Quarterly status updates for project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]] top * [[phab:project/profile/4301/|<span lang="en" dir="ltr" class="mw-content-ltr">What we are doing currently</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] ecnn01iaqh01gs36uvuil8yqkjfhw0u 5386542 5386538 2022-07-28T14:55:40Z DaSupremo 1532535 Created page with "What we dey do currently" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> == Follow wanna work == * Monthly/Quarterly status updates for project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]] top * [[phab:project/profile/4301/|What we dey do currently]] <div lang="en" dir="ltr" class="mw-content-ltr"> == Get Involved == </div> * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] hzcf7ubohzpo36zrpg7piu2afsd7g3v 5386544 5386542 2022-07-28T14:56:00Z DaSupremo 1532535 Created page with "== Make you Get Involved ==" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> == Follow wanna work == * Monthly/Quarterly status updates for project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]] top * [[phab:project/profile/4301/|What we dey do currently]] == Make you Get Involved == * <div lang="en" dir="ltr" class="mw-content-ltr"> == Contact us == </div> * [[Category:Inuka Projects{{#translation:}}]] o0d4sik5xgojnp4mx8uh6y67w620e0p 5386546 5386544 2022-07-28T14:56:10Z DaSupremo 1532535 Created page with "== Contact us ==" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} <div lang="en" dir="ltr" class="mw-content-ltr"> == Introduction == </div> Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> == Follow wanna work == * Monthly/Quarterly status updates for project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]] top * [[phab:project/profile/4301/|What we dey do currently]] == Make you Get Involved == * == Contact us == * [[Category:Inuka Projects{{#translation:}}]] 3oumy8k03i0jv6uc8vgkeml26rae8u7 5386550 5386546 2022-07-28T14:56:51Z DaSupremo 1532535 Created page with "== Introduction ==" wikitext text/x-wiki <languages/> {{Wikimedia engineering project information | name = Inuka (formerly New Readers) | description = Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. | start = 2019-07-01 | group = Product | lead = | members = {{plainlist| * [[metawiki:User:Runab_WMF|Runa Bhattacharjee]] * [[metawiki:User:Neil Shah-Quinn (WMF)|Neil Shah-Quinn]] * [[metawiki:User:Sbisson_(WMF)|Stephane Bisson]] * [[User:MMunyoki_(WMF)|Mary Munyoki]] * [[User:EAMedina (WMF)|Eduardo Medina]] * [[User:HTan (WMF)|Huei Tan]] * [[User:SGautam (WMF)|Sudhanshu Gautam]] * [[metawiki:User:UOzurumba_(WMF)|Uzoma Ozurumba]] *[[User:PWaigi (WMF)|Purity Waigi]] }} | Phabricator = inuka-team | updates = | progress = | backlog = }} == Introduction == Millions of people for emerging markets inside dey come online for de first time. E be imperative say wanna projects dey support den welcome fresh readers plus access to knowledge wey dey match how dem dey consume content for de internet top. De Wikimedia Foundation '''Inuka''' team, (na e be New Readers product team) dem form am for July 2019 inside wey e be part of de Product department. De team hin mission be say e go deliver compelling experiences give Wikipedia readers for emerging markets inside, wey go drive increased adoption den retention of Wikipedia for areas where internet use dey grow rapidly. === Why de name ''Inuka''? === ''Inuka'' be Kiswahili word wey dey mean "to rise". Wanna team hin mission be say we go raise de relevance of Wikipedia den oda Wikimedia project dema content, for readers for Emerging Markets inside wey no dey access am yet. We choose say we go use name wey comot language wey dem dey speak for part of emerging markets inside, for Africa inside, wey e be way wey go kai we for de audience we dey want reach plus wanna product choices. E be aspirational, den dey kai de team say everytin we dey build or implement, fit dey take we towards de goal of raising worldwide readership. == Mission == * Dem dey deliver compelling experiences for Wikipedia readers for emerging markets, dem dey drive increased adoption den retention for Wikipedia. == Team Principles == Below, be sum of wanna team principles, de tym wey we dey design den build products give people for Emerging Markets: * Build give mobile-first experiences * Explore fresh form factors * Short term * Multi-lingual * Global * Diverse * Emerging Markets centric * Content Enablers * Meet users wer dem dey == Inuka Team Projects == * [[Wikistories]] e dey make editors create short, visual den reliable knowledge wey comot Wikipedia for quick consumption den dem dey share am easy. E go fit generate content for visual format inside so say dem go capture den distribute encyclopedic knowledge wey be less suitable give long form articles. Dis fresh form of content contribution go take into account de constraints editors for emerging digital communities dey face when dem dey contribute content, den make am easier/more welcoming dem go contribute to knowledge successfully thru mobile phones. * [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. E be similar to page previews nanso give external sites. Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] * [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. == Design Research == * [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community * [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. * [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside == Meet the Team == <div><gallery heights="110" widths="220" perrow="7" mode="nolines"> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EMedina (WMF)|Eduardo Medina]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:HTan (WMF)|Huei Tan]]'''<br />Senior Software Engineer</small> File:Wikimedia Foundation office camera shy.png|<small>'''Mary Munyoki'''<br />Senior Technical Program Manager</small> File:Quinn, Neil April 2015.jpg|<small>'''[[m:User:Neil_Shah-Quinn_(WMF)|Neil Shah Quinn]]'''<br />Senior Data Scientist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:PWaigi-WMF|Purity Waigi]]'''<br />Lead Product Manager</small> File:Bhattacharjee, Runa Jan 2019.jpg|<small>'''[[foundation:User:Runab_WMF|Runa Bhattacharjee]]'''<br />Engineering Director</small> File:Stephane, Bisson January 2016.jpg|<small>'''[[metawiki:User:Sbisson_(WMF)|Stephane Bisson]]'''<br />Staff Software Engineer/Tech Lead</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:SGautam (WMF)|Sudhanshu Gautam]]'''<br />Senior UX Designer</small> File:Wikimedia Foundation hall blurred.jpg|<small>'''[[m:User:User:UOzurumba_(WMF)|Uzoma Ozurumba]]'''<br />Community Relationship Specialist</small> File:Wikimedia Foundation office camera shy.png|<small>'''[[User:EUdoh-WMF|Ezekiel Udoh]]'''<br />Test Engineer</small> </gallery> </div> == Follow wanna work == * Monthly/Quarterly status updates for project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]] top * [[phab:project/profile/4301/|What we dey do currently]] == Make you Get Involved == * == Contact us == * [[Category:Inuka Projects{{#translation:}}]] r1lmoliqvj43j8c2aggpezbvpeziwtw Translations:Reading/Web/Desktop Improvements/Updates/Talk to Web/31/es 1198 1606811 5387362 5385615 2022-07-28T22:11:31Z Zapipedia (WMF) 17560702 wikitext text/x-wiki '''Los estándar''' son para cualquier persona interesada en el proyecto. Se realizan en inglés. 10dudwi16kbxr3inhi5gbd1r50pnq6z Translations:Reading/Web/Desktop Improvements/Updates/Talk to Web/37/es 1198 1606817 5387129 5385617 2022-07-28T20:35:40Z SGrabarczuk (WMF) 9240933 wikitext text/x-wiki [$link Haz clic aquí para unirte] / [$dial marca por tu ubicación] / [$notes notes]. thtj57wfimpa3y3h27ul765ukglrbt0 Manual:Common errors and symptoms/PCRE/de 100 1607100 5386182 5386180 2022-07-28T11:59:14Z ThisCarthing 17456337 Created page with "== Ein neueres PHP-Paket auswählen ==" wikitext text/x-wiki <languages /> PCRE ist eine [https://php.net/pcre Perl Compatible Regular Expressions]-Bibliothek, die mit PHP mitgeliefert wird. <span lang="en" dir="ltr" class="mw-content-ltr">When you try to install or upgrade to MediaWiki 1.22 or later, you may receive the following error message:</span> <blockquote><!-- from message 'config-pcre-old' in includes/installer/Installer.i18n.php --> '''Fatal:''' PCRE <!-- $1 --><var>newer version</var> or later is required. Your PHP binary is linked with version <!-- $2 --><var>older version</var>. </blockquote> This issue may occur if you are using an older Linux distribution (one having an older version of PCRE than that bundled with PHP) and PHP is compiled with the <code>--with-pcre-regex=DIR</code> configure option. In particular, the <code>php53</code> packages from [[w:Red Hat Enterprise Linux|Red Hat Enterprise Linux]] 5 (and [[w:Red Hat Enterprise Linux derivatives|derivatives]] such as [[w:CentOS|CentOS]] and [[w:Scientific Linux|Scientific Linux]]) are broken in this regard. MediaWiki [https://gerrit.wikimedia.org/r/#/c/102081/ uses features introduced in the <var>newer version</var>] of [[w:PCRE|PCRE]] and no longer works with older versions of the library. Below are several methods to upgrade the PCRE library your PHP installation uses. == Ein neueres PHP-Paket auswählen == Some servers will allow you to select an alternative (later) version of PHP to use with one or more domains, that includes a later version of PCRE. For example, servers running Plesk 11.5+, let you select a domain, and change the hosting to use a fastCGI version of PHP (if none are available, your hosting company may install them). While the server default PHP 5.3.3 is packaged with PCRE 6.6, selecting fastCGI PHP 5.4.25 includes PCRE 8.1 <div lang="en" dir="ltr" class="mw-content-ltr"> ==Installing newer PHP packages== </div> For Red Hat Enterprise Linux 5 and its derivatives, there are several third-party package repositories that have newer versions of PHP compiled without the option in question. Here are some of them: * [http://iuscommunity.org/pages/GettingStarted.html IUS Community Project] * [http://blog.famillecollet.com/pages/Config-en Les RPMs de Remi] Note that these packages are not supported by Red Hat, by any other Linux vendor, or by the MediaWiki developers. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Recompiling PHP from source== </div> If you compiled PHP yourself using the source code from php.net, you should be able to recompile it to use the newer, bundled version of PCRE: * Run <code>./configure</code> again without the <code>--with-pcre-regex=DIR</code> option * Run <code>make</code> and/or <code>make install</code> again 3s12fv5e16ahcopprfgikk7pn8aog2v 5386184 5386182 2022-07-28T11:59:43Z ThisCarthing 17456337 Created page with "== Neuere PHP-Pakete installieren ==" wikitext text/x-wiki <languages /> PCRE ist eine [https://php.net/pcre Perl Compatible Regular Expressions]-Bibliothek, die mit PHP mitgeliefert wird. <span lang="en" dir="ltr" class="mw-content-ltr">When you try to install or upgrade to MediaWiki 1.22 or later, you may receive the following error message:</span> <blockquote><!-- from message 'config-pcre-old' in includes/installer/Installer.i18n.php --> '''Fatal:''' PCRE <!-- $1 --><var>newer version</var> or later is required. Your PHP binary is linked with version <!-- $2 --><var>older version</var>. </blockquote> This issue may occur if you are using an older Linux distribution (one having an older version of PCRE than that bundled with PHP) and PHP is compiled with the <code>--with-pcre-regex=DIR</code> configure option. In particular, the <code>php53</code> packages from [[w:Red Hat Enterprise Linux|Red Hat Enterprise Linux]] 5 (and [[w:Red Hat Enterprise Linux derivatives|derivatives]] such as [[w:CentOS|CentOS]] and [[w:Scientific Linux|Scientific Linux]]) are broken in this regard. MediaWiki [https://gerrit.wikimedia.org/r/#/c/102081/ uses features introduced in the <var>newer version</var>] of [[w:PCRE|PCRE]] and no longer works with older versions of the library. Below are several methods to upgrade the PCRE library your PHP installation uses. == Ein neueres PHP-Paket auswählen == Some servers will allow you to select an alternative (later) version of PHP to use with one or more domains, that includes a later version of PCRE. For example, servers running Plesk 11.5+, let you select a domain, and change the hosting to use a fastCGI version of PHP (if none are available, your hosting company may install them). While the server default PHP 5.3.3 is packaged with PCRE 6.6, selecting fastCGI PHP 5.4.25 includes PCRE 8.1 == Neuere PHP-Pakete installieren == For Red Hat Enterprise Linux 5 and its derivatives, there are several third-party package repositories that have newer versions of PHP compiled without the option in question. Here are some of them: * [http://iuscommunity.org/pages/GettingStarted.html IUS Community Project] * [http://blog.famillecollet.com/pages/Config-en Les RPMs de Remi] Note that these packages are not supported by Red Hat, by any other Linux vendor, or by the MediaWiki developers. <div lang="en" dir="ltr" class="mw-content-ltr"> ==Recompiling PHP from source== </div> If you compiled PHP yourself using the source code from php.net, you should be able to recompile it to use the newer, bundled version of PCRE: * Run <code>./configure</code> again without the <code>--with-pcre-regex=DIR</code> option * Run <code>make</code> and/or <code>make install</code> again bzrmzmtsd56fpgpkcuuxnasmy4jjzxq Translations:Manual:Common errors and symptoms/PCRE/3/de 1198 1607102 5386181 2022-07-28T11:59:13Z ThisCarthing 17456337 Created page with "== Ein neueres PHP-Paket auswählen ==" wikitext text/x-wiki == Ein neueres PHP-Paket auswählen == 1cibpwqdh9jnd9lchbgj8z4o7oe80oh Translations:Manual:Common errors and symptoms/PCRE/4/de 1198 1607103 5386183 2022-07-28T11:59:42Z ThisCarthing 17456337 Created page with "== Neuere PHP-Pakete installieren ==" wikitext text/x-wiki == Neuere PHP-Pakete installieren == 0p33ts0zga6djqzeln696ujy2hmzw5a Translations:Help:TemplateData/615/cs 1198 1607104 5386185 2022-07-28T12:00:25Z ENeRZet 17359278 Created page with "Hodnota $1 je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[$2|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně." wikitext text/x-wiki Hodnota $1 je určena pro datum ve formátu RRRR-MM-DD ([[:en:ISO 8601|ISO 8601]]). Například 2014-05-22. [[$2|Příručka TemplateData]] jej také označuje jako určený pro kombinace data a času ISO 8601, jako je "2014-05-22T16:01:12Z". Ale v praxi jej od února 2020 nepoužívá žádné velké editační rozhraní. Tímto způsobem a téměř všechny hlavní parametry šablony Wikimedie berou data a časy odděleně. lgbgc9a5zr4d4enbi2qzfbddczutr9j Translations:Help:TemplateData/616/cs 1198 1607105 5386187 2022-07-28T12:00:31Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki '''Výsledky''' lbfikrpepiaiktl72owcc4dal2k3q17 Translations:Help:TemplateData/617/cs 1198 1607106 5386189 2022-07-28T12:00:47Z ENeRZet 17359278 Created page with "* V aplikaci VisualEditor a editoru wikitext 2017 nemá $1 žádný viditelný efekt." wikitext text/x-wiki * V aplikaci VisualEditor a editoru wikitext 2017 nemá $1 žádný viditelný efekt. a46wpmj4nkf9aq5r6b7dllcfznpbdn9 Translations:Manual:CompareParsers.php/Page display title/de 1198 1607107 5386190 2022-07-28T12:00:49Z ThisCarthing 17456337 Created page with "Handbuch:compareParsers.php" wikitext text/x-wiki Handbuch:compareParsers.php eg6uphqqzyi6j3luj5d7kyimiylvby5 Translations:Manual:CompareParserCache.php/Page display title/de 1198 1607108 5386192 2022-07-28T12:01:01Z ThisCarthing 17456337 Created page with "Handbuch:compareParserCache.php" wikitext text/x-wiki Handbuch:compareParserCache.php mekc1jaqu2v4ck9lmtxzx866dsa6k8q Translations:Manual:CommonElements.css/Page display title/de 1198 1607109 5386193 2022-07-28T12:01:26Z ThisCarthing 17456337 Created page with "Handbuch:commonElements.css" wikitext text/x-wiki Handbuch:commonElements.css ptqjhfh4hi9egu4zfqql9qlt78l3koa Manual:CommonElements.css/de 100 1607110 5386194 2022-07-28T12:01:27Z ThisCarthing 17456337 Created page with "Handbuch:commonElements.css" wikitext text/x-wiki <languages/> {{DISPLAYTITLE:Manual:commonElements.css}} {{Removed|1.24}} {{MW file|commonElements.css|skins/common/}} <span lang="en" dir="ltr" class="mw-content-ltr">'''commonElements.css''' is the MediaWiki {{ll|Manual:CSS|style sheet}} for general styles on basic content elements.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It contains styles for basic elements such as links, lists, etc.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This style sheet is used by the {{ll|Skin:MonoBook|nsp=0}} and {{ll|Skin:Vector|nsp=0}} {{ll|Manual:skin|skins}}.</span> t1ugzdqym6nn1a1mmdru8tw3otjmd5f Translations:Help:TemplateData/618/cs 1198 1607111 5386195 2022-07-28T12:01:41Z ENeRZet 17359278 Created page with "* Ve wikitextovém editoru pro rok 2010 s TemplateWizard $1 zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic)." wikitext text/x-wiki * Ve wikitextovém editoru pro rok 2010 s TemplateWizard $1 zkracuje pole pro zadávání parametrů asi o třetinu a přidává rozbalovací kalendář, který umožňuje uživateli vybrat si datum. Zobrazí také šedý vzorový text ve vstupním poli "RRRR-MM-DD". Pokud vstup neodpovídá této normě, pole svítí červeně, ale editor vždy vypíše datum odpovídající normě (pokud jsou zadána čísla) nebo nic (pokud je zadán pouze text nebo nic). 43szubtn8xhiomf6gu8yi9xsw1505fp Translations:Help:TemplateData/619/cs 1198 1607112 5386197 2022-07-28T12:01:50Z ENeRZet 17359278 Created page with "'''S jinými parametry'''" wikitext text/x-wiki '''S jinými parametry''' te1bahwhruhz7rp2yhjxm2bp8pdeebt Translations:Help:TemplateData/620/cs 1198 1607113 5386199 2022-07-28T12:01:58Z ENeRZet 17359278 Created page with "* V editoru wikitext 2010 s TemplateWizard, $1 přepíše efekty $2. Hodnota $3 nebude automaticky vložena do vstupního pole, pokud je typ parametru $4." wikitext text/x-wiki * V editoru wikitext 2010 s TemplateWizard, $1 přepíše efekty $2. Hodnota $3 nebude automaticky vložena do vstupního pole, pokud je typ parametru $4. pc6fybhsu87s4rkum2ulcjynmqbu3h5 Translations:Help:TemplateData/621/cs 1198 1607114 5386201 2022-07-28T12:04:24Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki '''Výsledky''' lbfikrpepiaiktl72owcc4dal2k3q17 Translations:Help:TemplateData/622/cs 1198 1607115 5386207 2022-07-28T12:09:48Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki '''Výsledky''' lbfikrpepiaiktl72owcc4dal2k3q17 Translations:Help:TemplateData/623/cs 1198 1607116 5386218 2022-07-28T12:13:02Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki '''Výsledky''' lbfikrpepiaiktl72owcc4dal2k3q17 Translations:Help:TemplateData/740/cs 1198 1607117 5386222 2022-07-28T12:14:06Z ENeRZet 17359278 Created page with "Názvy souborů neobsahují předponu jmenného prostoru "$1"." wikitext text/x-wiki Názvy souborů neobsahují předponu jmenného prostoru "$1". t0nk665vzegiy0te5ij9fv3itqleo85 Translations:Help:TemplateData/624/cs 1198 1607118 5386226 2022-07-28T12:16:50Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki '''Výsledky''' lbfikrpepiaiktl72owcc4dal2k3q17 Translations:Help:TemplateData/625/cs 1198 1607119 5386232 2022-07-28T12:20:40Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki '''Výsledky''' lbfikrpepiaiktl72owcc4dal2k3q17 Translations:Help:TemplateData/626/cs 1198 1607120 5386236 2022-07-28T12:21:28Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki '''Výsledky''' lbfikrpepiaiktl72owcc4dal2k3q17 Translations:Help:TemplateData/627/cs 1198 1607121 5386242 2022-07-28T12:23:20Z ENeRZet 17359278 Created page with "'''Výsledky'''" wikitext text/x-wiki '''Výsledky''' lbfikrpepiaiktl72owcc4dal2k3q17 Translations:Help:TemplateData/741/cs 1198 1607122 5386269 2022-07-28T12:37:27Z ENeRZet 17359278 Created page with "Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat." wikitext text/x-wiki Tyto chyby může být obtížné odhalit a mají příliš mnoho forem, než aby je bylo možné vyjmenovat. ddgd3rzdsz42zbgg1bqcgv4xr5id7wa Translations:Help:TemplateData/680/cs 1198 1607123 5386271 2022-07-28T12:38:12Z ENeRZet 17359278 Created page with "Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například $1, který zvýrazní chyby a pomůže je opravit." wikitext text/x-wiki Nejlepší způsob, jak se jim vyhnout, je upravovat data šablony výhradně pomocí editoru TemplateData. Nejlepší způsob, jak je odhalit, jakmile k nim dojde, je použít externí validátor JSON, například $1, který zvýrazní chyby a pomůže je opravit. 6fcagvv4pbtdz23gd24yy0yem8dh4t1 Translations:Help:TemplateData/233/cs 1198 1607124 5386273 2022-07-28T12:38:40Z ENeRZet 17359278 Created page with "Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ($1)." wikitext text/x-wiki Editor wikitextu z roku 2010 nekontroluje neplatný JSON díky staré, neopravené chybě ($1). l2a4dm3s4255v1rtquwlrdve9y45w4n Translations:Help:TemplateData/742/cs 1198 1607125 5386275 2022-07-28T12:39:15Z ENeRZet 17359278 Created page with "Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "$1"." wikitext text/x-wiki Stránky, které obsahují neplatný JSON, mohou vyvolávat alarmující zprávy "$1". qqoxxyffp0w70uah0zmndgy35fw147m Translations:Help:TemplateData/743/cs 1198 1607126 5386277 2022-07-28T12:39:40Z ENeRZet 17359278 Created page with "Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše)." wikitext text/x-wiki Chcete-li tyto chyby opravit, nejlepším řešením je použít validátor JSON (viz výše). 8jpsgw1qr49uaoyckh717kgq7djazoz Translations:Help:TemplateData/744/cs 1198 1607127 5386283 2022-07-28T12:43:46Z ENeRZet 17359278 Created page with "Tento parametr není uveden v $1, ale měl by být." wikitext text/x-wiki Tento parametr není uveden v $1, ale měl by být. pn5hj656f2jik2y6jvdq1ubl4n0khel Translations:Help:TemplateData/745/cs 1198 1607128 5386285 2022-07-28T12:44:29Z ENeRZet 17359278 Created page with "Chyba: Požadovaná vlastnost "$1" nebyla nalezena." wikitext text/x-wiki Chyba: Požadovaná vlastnost "$1" nebyla nalezena. 53b7ra210kt0ikmd71jem779hz1i5r9 Topic:X05pidy5i54x4wdh 2600 1607129 5386286 2022-07-28T12:44:34Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x05pidy5i54x4wdh"} edxwy6egaddgw0zh8ajdbqi7qg704bm Translations:Help:TemplateData/746/cs 1198 1607130 5386294 2022-07-28T12:46:27Z ENeRZet 17359278 Created page with "Tento parametr není uveden v $1, ale měl by být." wikitext text/x-wiki Tento parametr není uveden v $1, ale měl by být. pn5hj656f2jik2y6jvdq1ubl4n0khel Translations:Help:TemplateData/747/cs 1198 1607131 5386296 2022-07-28T12:47:04Z ENeRZet 17359278 Created page with "Chyba: Neplatná hodnota vlastnosti "$1"." wikitext text/x-wiki Chyba: Neplatná hodnota vlastnosti "$1". ecf0y0twh73lh6ko2iula9y1547wvbu Translations:Help:TemplateData/748/cs 1198 1607132 5386302 2022-07-28T12:49:05Z ENeRZet 17359278 Created page with "Tyto uvozovky by zde neměly být." wikitext text/x-wiki Tyto uvozovky by zde neměly být. afvzq9g32p155s3bi3h8pycry97zxja Translations:Help:TemplateData/749/cs 1198 1607133 5386304 2022-07-28T12:50:19Z ENeRZet 17359278 Created page with "Chyba: Předpokládá se, že vlastnost "$1" bude "$2", "$3" nebo platný formátovací řetězec." wikitext text/x-wiki Chyba: Předpokládá se, že vlastnost "$1" bude "$2", "$3" nebo platný formátovací řetězec. ohw2i409391i6va1arfjc6vi5cvbwyn Translations:Help:TemplateData/628/cs 1198 1607134 5386310 2022-07-28T12:52:31Z ENeRZet 17359278 Created page with "K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje." wikitext text/x-wiki K této chybě dochází, pokud uvedete parametr, který v TemplateData neexistuje. 3snvvzdqp5t7m5jm1u17rmpdklnqspd Translations:Help:TemplateData/629/cs 1198 1607135 5386312 2022-07-28T12:52:56Z ENeRZet 17359278 Created page with "To je pravděpodobně způsobeno pravopisnými chybami." wikitext text/x-wiki To je pravděpodobně způsobeno pravopisnými chybami. 4921hsdmy35pqlec4yba5hu9nz96zsa Translations:Help:TemplateData/750/cs 1198 1607136 5386314 2022-07-28T12:53:19Z ENeRZet 17359278 Created page with "pravopisná chyba" wikitext text/x-wiki pravopisná chyba je0ogwr9ru6gtgsn95fod4qymhttwso Translations:Help:TemplateData/751/cs 1198 1607137 5386318 2022-07-28T12:54:43Z ENeRZet 17359278 Created page with "špatně umístěný parametr" wikitext text/x-wiki špatně umístěný parametr oc7pq7yz8c09sg4owyd90rv1sycia2g Translations:Help:TemplateData/630/cs 1198 1607138 5386322 2022-07-28T12:56:20Z ENeRZet 17359278 Created page with "Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují." wikitext text/x-wiki Kromě toho se ujistěte, že neuvádíte žádné parametry, které pro objekt TemplateData neexistují. hkg7qridychjkfsje8roo7om5vuxue6 Translations:Help:TemplateData/631/cs 1198 1607139 5386326 2022-07-28T12:57:17Z ENeRZet 17359278 Created page with "V sekci [[$1|Parametry TemplateData]] můžete zkontrolovat, které parametry pro objekt existují." wikitext text/x-wiki V sekci [[$1|Parametry TemplateData]] můžete zkontrolovat, které parametry pro objekt existují. 60hf35188umyz01bzjr867wn7jzmxtd Translations:Help:TemplateData/673/cs 1198 1607140 5386335 2022-07-28T13:18:14Z ENeRZet 17359278 Created page with "$1 a [[$2|Query Helper]]" wikitext text/x-wiki $1 a [[$2|Query Helper]] jve6hte6p0pcxdxdkja2h8uu0q7el2d Translations:Help:Templates/207/cs 1198 1607141 5386390 2022-07-28T13:40:55Z ENeRZet 17359278 Created page with "{{Thankyou|1=přidání "="|2=Tonda}}" wikitext text/x-wiki {{Thankyou|1=přidání "="|2=Tonda}} mqxkwlhbeg36yode0myywz2ls5xjpo5 Hosting services/pt 0 1607143 5386396 2022-07-28T13:45:58Z 201.47.225.82 Created page with "$url Categoria:WikiFarm] no WikiIndex." wikitext text/x-wiki <languages/> {{Warn|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Be warned''' that the Wikimedia Foundation does not guarantee the quality of or endorse any of the services on the list.</span>}} {{toc right}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want to run a MediaWiki wiki and don't want to maintain your own infrastructure, you might be interested in the [[Special:MyLanguage/Manual:Wiki family|wiki farms]] and hosting services listed below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In addition, most regular web hosting companies allow for installing MediaWiki without too much trouble, although maintaining and upgrading the code would still in most cases be up to you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * You can also install a pre-made [[Special:MyLanguage/software bundles|software bundle]] or software "appliance" on a [[w:Virtual private server|virtual private server]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Do not add hosting services to this list without directly linking to a page that ''explicitly'' states MediaWiki hosting. </div> <!-- Please keep the list in ALPHABETIC ORDER. Thank you! --> {| class="wikitable sortable" {{:Hosting services/Header}} |- !<br/> ! ! ! ! ! ! ! ! ! |- | [https://www.20i.com/mediawiki-hosting 20i] | USA, UK | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://www.a2hosting.com/mediawiki-hosting A2 Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://albatross.cloud/mediawiki-hosting Albatross Cloud] | USA | host | Managed Hosting and Cloud Services with exceptional support for Medium and Enterprise Clientele. | {{no}} | paid | Yes or subdomain | | 24/7 | |- | [https://www.arvixe.com/mediawiki_hosting Arvixe Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://biowikifarm.net/meta/Biowikifarm Biowikifarm] | Germany | farm | for non-commercial dissemination of biological open-content data | {{yes}} | free | | | | |- | [https://civihosting.com/mediawiki-hosting/ CiviHosting] | USA, Europe | host | Boutique-style hosting firm including account sizes for personal, business and enterprise-level wikis, including [[Extension:Semantic MediaWiki|Semantic MediaWiki]] and [[BlueSpice]] | {{no}} | paid | Yes, as well as domain registration service, or a subdomain is possible | SSH access | 24/7 support with 5 minute response time included with all accounts | [https://civihosting.com/shared-hosting/ Shared] and [https://civihosting.com/vps-hosting/ VPS hosting] available. Services include * Free installation and migration * Daily backups * 24/7 support with 5 minute response time * [https://civihosting.com/semantic-mediawiki-hosting/ Semantic MediaWiki] hosting * BlueSpice hosting * Turnkey solution for MediaWiki hosting |- | [https://www.cloudways.com/en/managed-mediawiki-cloud-hosting.php Cloudways.com] | Malta | host | | {{no}} | paid | You have to set it up independently | {{yes}} | | Quick setup, automatic backup, cloud-based (included in the cost). Support staff also in Dubai, Pakistan and Spain. |- | [https://help.dreamhost.com/hc/en-us/articles/217292577-MediaWiki-overview Dreamhost.com] | USA | host | | {{no}} | paid | | limited ssh access | 24/7 via tickets and email. | Also offers [https://help.dreamhost.com/hc/en-us/articles/215769478-Non-profit-discount free hosting service for non-profits.] |- |[https://community.fandom.com/wiki/Choosing_Fandom Fandom] | United States, France, Poland, Indonesia, Australia | farm | Entertainment, Lifestyle, Video Games and Anime | {{yes}} | free (with ads) | custom [[w:subdomain|subdomain]] only. | {{no}} | [https://fandom.zendesk.com/ Contact] and community forums | [https://www.fandom.com/community-creation-policy Wikis are not owned by their founders]. Fandom may take decisions affecting the community even if there's no consensus at all. They reserve the [https://community.fandom.com/wiki/Thread:1572365 right to change the wikis URL for SEO purposes]. In case the community wants to move to another host, the wiki and its content in most cases can't or won't be deleted from Fandom. There's only one skin available and it's proprietary. New Wikis Run MediaWiki 1.37.2 whilst older Wikis run MediaWiki 1.33. |- | [https://fastdot.com/hosting/cpanel-cloud-hosting/mediawiki-hosting/ Fastdot Hosting] | Australia, Asia Pacific, USA, UK | host | | {{no}} | paid | | | | 1-click installer |- | [https://hostdash.com/mediawiki-hosting/ HostDash] | USA | host | Blazing fast wiki hosting solutions, backed by 24/7 expert support & a 60 day money back guarantee. | {{no}} | paid | {{yes}} | | 24/7 | * 1-Click Setup * FREE Domain Name * 24/7 Expert Support * Proactive Malware Protection * cPanel Control Panel * 60 Day Money Back Guarantee |- | [https://www.hostgator.com/apps/wiki-hosting HostGator] | USA | host | | {{no}} | paid | {{yes}} | | | |- |[https://hostiso.com/mediawiki-hosting Hostiso] |USA, Canada, Germany, France, Singapore |host |Managed Hosting and Services with exceptional support for mediwiki clients! | {{no}} |paid |yes or subdomain | |24/7 |1-click setup, free backups, support, cPanel, cloud-based. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.hostknox.com/mediawiki-hosting HostKnox] | USA | host | | {{no}} | paid | {{yes}} | Chrooted (jailed) SSH | 24/7 via support tickets. 15-minute response time. | Free MediaWiki installation, transfer & upgrade. |- |[https://www.knownhost.com/media-wiki-hosting.html KnownHost] |USA, Europe |host | | {{no}} |paid | |SSH Access |24/7/365 Email and Ticket Support. |Free install support. Shared, VPS, Cloud and Dedicated Server lines. |- | [https://www.milesweb.com/mediawiki-hosting.php MilesWeb.com] | UK, US, India, Romania | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://miraheze.org Miraheze] | UK | farm | | {{yes}} | free (no ads) | {{optional}} | {{no}} | IRC, Email, Issue trackers, Wiki venues, Discord server | Community-driven, not-for-profit, quick wiki creation, HTTPS-only, public and private wikis. Infrastructure 100% [https://github.com/miraheze open source]. No hard limits on server resource usage and runs latest MediaWiki version. |- | [https://www.mywikis.com/ MyWikis] | USA We speak English / Nosotros hablamos español / On parle français / 我们讲中文 / हमें हिंदी आती है | host | Private wikis (public wikis are still available)<br />Different plans available, tailored for enterprise customers, personal wikis, and anywhere in between. | {{no}} | paid (no ads) | {{yes}} | FTP and SSH on request | Support system, email, phone, Zoom, Microsoft Teams, and Google Meet | * Wikis created automatically in under 5 minutes with 40+ extensions preinstalled. Hundreds of extensions available to install. * Self Service portal, where you can manage your wiki, add extensions to your wiki, reset passwords, and more. * Free migrations for most wikis; extensive experience in migrating from MediaWiki and other platforms. * 24/7 professional (not volunteer) personalized support from MediaWiki experts with 10+ years of experience; support response times guaranteed through SLAs. * 9 different privacy levels. Anti-spam built into every wiki. Wikis backed up daily. * Use a subdomain, buy a domain through MyWikis, or bring your own domain. |- | [https://neowiki.neoseeker.com/wiki/Alternative_To_Wikia Neoseeker] | | farm | game and entertainment-related wikis | {{yes}} | free | | | | |- |[https://OpenFox.io OpenFox.io] |Europe |Cloud based |Orgnaisational Wikis | {{no}} |Monthly and Annual |Company domain or Openfox.io subdomain. | {{no}} |Wiki set-up, consulting and implementation |Managed wiki Service with high security as well as set-up and organisational implementation support |- | [https://professional.wiki Professional.Wiki] | Europe | dedicated server | Professional services for companies of all sizes. Unmatched [[Semantic MediaWiki]] expertise. | {{no}} | paid | {{yes}} | {{yes}} | yes, with real experts | [https://professional.wiki/en/hosting Holistic services] including setup, management, support, training and custom development. Run by [https://professional.wiki/en/about MediaWiki veterans]. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.rosehosting.com/mediawiki-vps-hosting.html RoseHosting] | USA | host | | {{no}} | paid | | | | Linux VPS hosting. |- | [https://www.saasweb.net/auto/managed-hosting/mediawiki SaaS Web Internet Solutions] | Germany | host | Standard, BlueSpice Free/Pro, Semantic MediaWiki | {{no}} | paid | always | {{no}} | Phone at business hours, email 24x7 | Fully managed MediaWiki on several infrastructures (as needed): Shared Hosting, Dedicated - both either on OpenStack Public Cloud or VMware Private Cloud |- | [https://www.shoutwiki.com/ ShoutWiki] | | farm | | {{yes}} | free; ad-supported; paid | [https://www.shoutwiki.com/wiki/Set_up_custom_domain possible] | {{no}} | [https://www.shoutwiki.com/wiki/Special:Contact Contact] and [https://www.shoutwiki.com/wiki/Forum:Index Forum] at ShoutWiki Hub | From MediaWiki developers and others. Lacks HTTPS/SSL support. |- | [https://www.siteground.com/mediawiki-hosting.htm SiteGround] | USA, Netherlands, Singapore | host | | {{no}} | paid | {{yes}} | | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://wiki.gg/ wiki.gg] | USA | farm | | {{Yes}} | Free | {{No}} | | Email | Private wiki-farm, wikis are only created on request by staff, and they prefer wikis with developer/publisher support to either provide assets or information for the wiki or for the wiki to become Official. |- | [https://webarch.coop/mediawiki Webarchitects] | UK | farm | | {{no}} | paid | {{yes}} | Optional SSH access | IRC, email, phone | Multi-stakeholder cooperative with social responsibility focus, green power and green hardware, emphasis on free and open source software ([https://git.coop/webarch/mediawiki Ansible playbook published under GPLv3]). |- | [https://www.webhostuk.co.uk/wiki-hosting.html Webhost UK LTD] | UK, US | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- class="sortbottom" {{:Hosting services/Header}} |- | [https://wiki-valley.com Wiki Valley] (fr) [https://en.wiki-valley.com/Create_your_own_private_wiki_online_and_manage_knowledge Wiki Valley](en) | France | farm | Private wikis | {{no}} | [https://wiki-valley.com/wiki/Tarifs_de_l_hebergement_des_wikis by user/month and options] | {{yes}} | {{no}} | mail, chat, phone and wiki | [https://wiki-valley.com/wiki/Sp%C3%A9cial:Contact Création à la demande] (fr) [https://en.wiki-valley.com/Special:Contact Creation on demand] (en)<br/> |- | [https://www.wikibase.nl/Diensten/Managed_hosting Wikibase Solutions] | The Netherlands | host | Fully managed Wiki hosting in addition to a core business of developing Semantic MediaWiki solutions | {{no}} | paid | {{yes}} | at request | phone, Skype and email | Also provides support for Elasticsearch and other requested services. |- | [https://www.wikihoster.net/ WikiHoster.net] | Germany | farm | Semantic MediaWiki, updates and upgrades included in plans (serviced) | {{no}} | paid | possible | serviced (see specialism) | Phone and email at business hours | German site. Available for customers in the [[wikipedia:Single Euro Payments Area|SEPA-area]]. |- | [http://www.wiki-site.com/ Wiki-Site] | United States, Israel | farm | | {{yes}} | free (with ads) | | | | Available in 25 languages. Runs [[MediaWiki 1.11]]. Lacks HTTPS/SSL support. |- | [https://www.wikiteq.com/ WikiTeq] | USA | host | Professionally managed hosting on a private VPS | {{no}} | paid | {{yes}} | {{yes}} | On-call support team ready 24/7 | Enterprised-focused full-service MediaWiki development company providing fully supported and maintained wikis. |- | [https://meta.rdpstudio.top FutureWiki] | China | farm | | {{no}} | one time paid at creation, sometimes free by event | {{no}} | {{no}} | Email, wiki page | Quick wiki creation, HTTPS-only. Only for Chinese users. Currently in matainance. |} <div lang="en" dir="ltr" class="mw-content-ltr"> == External links == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[wikiapiary:Host:Hosts|Hosts]] listed at [[WikiApiary]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[wikiapiary:Farm:Farms|Farms]] listed at WikiApiary.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikibooks:Starting and Running a Wiki Website/Hosted Wikis]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[w:Comparison of wiki hosting services|Comparison of wiki hosting services]]</span> * [https://www.wikimatrix.org WikiMatrix] * <span lang="en" dir="ltr" class="mw-content-ltr">[https://curlie.org/Computers/Software/Groupware/Wiki/Wiki_Farms Wiki farms] at [[w:DMOZ|DMOZ]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikiindex.org/Category:WikiFarm Category:WikiFarm] at WikiIndex.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://github.com/WikiTeam/wikiteam/wiki/WikiFarms WikiFarms - wikiteam - tools for archiving wikis]. On [[w:GitHub|GitHub]].</span> [[Category:MediaWiki References{{#translation:}}]] toytt6ufkwchqf80kawqy9kf0jqykrb 5386398 5386396 2022-07-28T13:46:34Z 201.47.225.82 Created page with "Não agregue serviços de alojamento a esta lista sem um enlace directo a uma página que indique "explicitamente" o alojamento de MediaWiki." wikitext text/x-wiki <languages/> {{Warn|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Be warned''' that the Wikimedia Foundation does not guarantee the quality of or endorse any of the services on the list.</span>}} {{toc right}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want to run a MediaWiki wiki and don't want to maintain your own infrastructure, you might be interested in the [[Special:MyLanguage/Manual:Wiki family|wiki farms]] and hosting services listed below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In addition, most regular web hosting companies allow for installing MediaWiki without too much trouble, although maintaining and upgrading the code would still in most cases be up to you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * You can also install a pre-made [[Special:MyLanguage/software bundles|software bundle]] or software "appliance" on a [[w:Virtual private server|virtual private server]]. </div> Não agregue serviços de alojamento a esta lista sem um enlace directo a uma página que indique "explicitamente" o alojamento de MediaWiki. <!-- Please keep the list in ALPHABETIC ORDER. Thank you! --> {| class="wikitable sortable" {{:Hosting services/Header}} |- !<br/> ! ! ! ! ! ! ! ! ! |- | [https://www.20i.com/mediawiki-hosting 20i] | USA, UK | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://www.a2hosting.com/mediawiki-hosting A2 Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://albatross.cloud/mediawiki-hosting Albatross Cloud] | USA | host | Managed Hosting and Cloud Services with exceptional support for Medium and Enterprise Clientele. | {{no}} | paid | Yes or subdomain | | 24/7 | |- | [https://www.arvixe.com/mediawiki_hosting Arvixe Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://biowikifarm.net/meta/Biowikifarm Biowikifarm] | Germany | farm | for non-commercial dissemination of biological open-content data | {{yes}} | free | | | | |- | [https://civihosting.com/mediawiki-hosting/ CiviHosting] | USA, Europe | host | Boutique-style hosting firm including account sizes for personal, business and enterprise-level wikis, including [[Extension:Semantic MediaWiki|Semantic MediaWiki]] and [[BlueSpice]] | {{no}} | paid | Yes, as well as domain registration service, or a subdomain is possible | SSH access | 24/7 support with 5 minute response time included with all accounts | [https://civihosting.com/shared-hosting/ Shared] and [https://civihosting.com/vps-hosting/ VPS hosting] available. Services include * Free installation and migration * Daily backups * 24/7 support with 5 minute response time * [https://civihosting.com/semantic-mediawiki-hosting/ Semantic MediaWiki] hosting * BlueSpice hosting * Turnkey solution for MediaWiki hosting |- | [https://www.cloudways.com/en/managed-mediawiki-cloud-hosting.php Cloudways.com] | Malta | host | | {{no}} | paid | You have to set it up independently | {{yes}} | | Quick setup, automatic backup, cloud-based (included in the cost). Support staff also in Dubai, Pakistan and Spain. |- | [https://help.dreamhost.com/hc/en-us/articles/217292577-MediaWiki-overview Dreamhost.com] | USA | host | | {{no}} | paid | | limited ssh access | 24/7 via tickets and email. | Also offers [https://help.dreamhost.com/hc/en-us/articles/215769478-Non-profit-discount free hosting service for non-profits.] |- |[https://community.fandom.com/wiki/Choosing_Fandom Fandom] | United States, France, Poland, Indonesia, Australia | farm | Entertainment, Lifestyle, Video Games and Anime | {{yes}} | free (with ads) | custom [[w:subdomain|subdomain]] only. | {{no}} | [https://fandom.zendesk.com/ Contact] and community forums | [https://www.fandom.com/community-creation-policy Wikis are not owned by their founders]. Fandom may take decisions affecting the community even if there's no consensus at all. They reserve the [https://community.fandom.com/wiki/Thread:1572365 right to change the wikis URL for SEO purposes]. In case the community wants to move to another host, the wiki and its content in most cases can't or won't be deleted from Fandom. There's only one skin available and it's proprietary. New Wikis Run MediaWiki 1.37.2 whilst older Wikis run MediaWiki 1.33. |- | [https://fastdot.com/hosting/cpanel-cloud-hosting/mediawiki-hosting/ Fastdot Hosting] | Australia, Asia Pacific, USA, UK | host | | {{no}} | paid | | | | 1-click installer |- | [https://hostdash.com/mediawiki-hosting/ HostDash] | USA | host | Blazing fast wiki hosting solutions, backed by 24/7 expert support & a 60 day money back guarantee. | {{no}} | paid | {{yes}} | | 24/7 | * 1-Click Setup * FREE Domain Name * 24/7 Expert Support * Proactive Malware Protection * cPanel Control Panel * 60 Day Money Back Guarantee |- | [https://www.hostgator.com/apps/wiki-hosting HostGator] | USA | host | | {{no}} | paid | {{yes}} | | | |- |[https://hostiso.com/mediawiki-hosting Hostiso] |USA, Canada, Germany, France, Singapore |host |Managed Hosting and Services with exceptional support for mediwiki clients! | {{no}} |paid |yes or subdomain | |24/7 |1-click setup, free backups, support, cPanel, cloud-based. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.hostknox.com/mediawiki-hosting HostKnox] | USA | host | | {{no}} | paid | {{yes}} | Chrooted (jailed) SSH | 24/7 via support tickets. 15-minute response time. | Free MediaWiki installation, transfer & upgrade. |- |[https://www.knownhost.com/media-wiki-hosting.html KnownHost] |USA, Europe |host | | {{no}} |paid | |SSH Access |24/7/365 Email and Ticket Support. |Free install support. Shared, VPS, Cloud and Dedicated Server lines. |- | [https://www.milesweb.com/mediawiki-hosting.php MilesWeb.com] | UK, US, India, Romania | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://miraheze.org Miraheze] | UK | farm | | {{yes}} | free (no ads) | {{optional}} | {{no}} | IRC, Email, Issue trackers, Wiki venues, Discord server | Community-driven, not-for-profit, quick wiki creation, HTTPS-only, public and private wikis. Infrastructure 100% [https://github.com/miraheze open source]. No hard limits on server resource usage and runs latest MediaWiki version. |- | [https://www.mywikis.com/ MyWikis] | USA We speak English / Nosotros hablamos español / On parle français / 我们讲中文 / हमें हिंदी आती है | host | Private wikis (public wikis are still available)<br />Different plans available, tailored for enterprise customers, personal wikis, and anywhere in between. | {{no}} | paid (no ads) | {{yes}} | FTP and SSH on request | Support system, email, phone, Zoom, Microsoft Teams, and Google Meet | * Wikis created automatically in under 5 minutes with 40+ extensions preinstalled. Hundreds of extensions available to install. * Self Service portal, where you can manage your wiki, add extensions to your wiki, reset passwords, and more. * Free migrations for most wikis; extensive experience in migrating from MediaWiki and other platforms. * 24/7 professional (not volunteer) personalized support from MediaWiki experts with 10+ years of experience; support response times guaranteed through SLAs. * 9 different privacy levels. Anti-spam built into every wiki. Wikis backed up daily. * Use a subdomain, buy a domain through MyWikis, or bring your own domain. |- | [https://neowiki.neoseeker.com/wiki/Alternative_To_Wikia Neoseeker] | | farm | game and entertainment-related wikis | {{yes}} | free | | | | |- |[https://OpenFox.io OpenFox.io] |Europe |Cloud based |Orgnaisational Wikis | {{no}} |Monthly and Annual |Company domain or Openfox.io subdomain. | {{no}} |Wiki set-up, consulting and implementation |Managed wiki Service with high security as well as set-up and organisational implementation support |- | [https://professional.wiki Professional.Wiki] | Europe | dedicated server | Professional services for companies of all sizes. Unmatched [[Semantic MediaWiki]] expertise. | {{no}} | paid | {{yes}} | {{yes}} | yes, with real experts | [https://professional.wiki/en/hosting Holistic services] including setup, management, support, training and custom development. Run by [https://professional.wiki/en/about MediaWiki veterans]. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.rosehosting.com/mediawiki-vps-hosting.html RoseHosting] | USA | host | | {{no}} | paid | | | | Linux VPS hosting. |- | [https://www.saasweb.net/auto/managed-hosting/mediawiki SaaS Web Internet Solutions] | Germany | host | Standard, BlueSpice Free/Pro, Semantic MediaWiki | {{no}} | paid | always | {{no}} | Phone at business hours, email 24x7 | Fully managed MediaWiki on several infrastructures (as needed): Shared Hosting, Dedicated - both either on OpenStack Public Cloud or VMware Private Cloud |- | [https://www.shoutwiki.com/ ShoutWiki] | | farm | | {{yes}} | free; ad-supported; paid | [https://www.shoutwiki.com/wiki/Set_up_custom_domain possible] | {{no}} | [https://www.shoutwiki.com/wiki/Special:Contact Contact] and [https://www.shoutwiki.com/wiki/Forum:Index Forum] at ShoutWiki Hub | From MediaWiki developers and others. Lacks HTTPS/SSL support. |- | [https://www.siteground.com/mediawiki-hosting.htm SiteGround] | USA, Netherlands, Singapore | host | | {{no}} | paid | {{yes}} | | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://wiki.gg/ wiki.gg] | USA | farm | | {{Yes}} | Free | {{No}} | | Email | Private wiki-farm, wikis are only created on request by staff, and they prefer wikis with developer/publisher support to either provide assets or information for the wiki or for the wiki to become Official. |- | [https://webarch.coop/mediawiki Webarchitects] | UK | farm | | {{no}} | paid | {{yes}} | Optional SSH access | IRC, email, phone | Multi-stakeholder cooperative with social responsibility focus, green power and green hardware, emphasis on free and open source software ([https://git.coop/webarch/mediawiki Ansible playbook published under GPLv3]). |- | [https://www.webhostuk.co.uk/wiki-hosting.html Webhost UK LTD] | UK, US | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- class="sortbottom" {{:Hosting services/Header}} |- | [https://wiki-valley.com Wiki Valley] (fr) [https://en.wiki-valley.com/Create_your_own_private_wiki_online_and_manage_knowledge Wiki Valley](en) | France | farm | Private wikis | {{no}} | [https://wiki-valley.com/wiki/Tarifs_de_l_hebergement_des_wikis by user/month and options] | {{yes}} | {{no}} | mail, chat, phone and wiki | [https://wiki-valley.com/wiki/Sp%C3%A9cial:Contact Création à la demande] (fr) [https://en.wiki-valley.com/Special:Contact Creation on demand] (en)<br/> |- | [https://www.wikibase.nl/Diensten/Managed_hosting Wikibase Solutions] | The Netherlands | host | Fully managed Wiki hosting in addition to a core business of developing Semantic MediaWiki solutions | {{no}} | paid | {{yes}} | at request | phone, Skype and email | Also provides support for Elasticsearch and other requested services. |- | [https://www.wikihoster.net/ WikiHoster.net] | Germany | farm | Semantic MediaWiki, updates and upgrades included in plans (serviced) | {{no}} | paid | possible | serviced (see specialism) | Phone and email at business hours | German site. Available for customers in the [[wikipedia:Single Euro Payments Area|SEPA-area]]. |- | [http://www.wiki-site.com/ Wiki-Site] | United States, Israel | farm | | {{yes}} | free (with ads) | | | | Available in 25 languages. Runs [[MediaWiki 1.11]]. Lacks HTTPS/SSL support. |- | [https://www.wikiteq.com/ WikiTeq] | USA | host | Professionally managed hosting on a private VPS | {{no}} | paid | {{yes}} | {{yes}} | On-call support team ready 24/7 | Enterprised-focused full-service MediaWiki development company providing fully supported and maintained wikis. |- | [https://meta.rdpstudio.top FutureWiki] | China | farm | | {{no}} | one time paid at creation, sometimes free by event | {{no}} | {{no}} | Email, wiki page | Quick wiki creation, HTTPS-only. Only for Chinese users. Currently in matainance. |} <div lang="en" dir="ltr" class="mw-content-ltr"> == External links == </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[wikiapiary:Host:Hosts|Hosts]] listed at [[WikiApiary]].</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[wikiapiary:Farm:Farms|Farms]] listed at WikiApiary.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikibooks:Starting and Running a Wiki Website/Hosted Wikis]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[w:Comparison of wiki hosting services|Comparison of wiki hosting services]]</span> * [https://www.wikimatrix.org WikiMatrix] * <span lang="en" dir="ltr" class="mw-content-ltr">[https://curlie.org/Computers/Software/Groupware/Wiki/Wiki_Farms Wiki farms] at [[w:DMOZ|DMOZ]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikiindex.org/Category:WikiFarm Category:WikiFarm] at WikiIndex.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://github.com/WikiTeam/wikiteam/wiki/WikiFarms WikiFarms - wikiteam - tools for archiving wikis]. On [[w:GitHub|GitHub]].</span> [[Category:MediaWiki References{{#translation:}}]] 6645njv1wn9cfcohh3pwfyqw7nm5tk3 5386400 5386398 2022-07-28T13:46:50Z 201.47.225.82 Created page with "[[$1|Hosts]] listados em [[WikiApiary]]." wikitext text/x-wiki <languages/> {{Warn|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Be warned''' that the Wikimedia Foundation does not guarantee the quality of or endorse any of the services on the list.</span>}} {{toc right}} <div lang="en" dir="ltr" class="mw-content-ltr"> If you want to run a MediaWiki wiki and don't want to maintain your own infrastructure, you might be interested in the [[Special:MyLanguage/Manual:Wiki family|wiki farms]] and hosting services listed below. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * In addition, most regular web hosting companies allow for installing MediaWiki without too much trouble, although maintaining and upgrading the code would still in most cases be up to you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * You can also install a pre-made [[Special:MyLanguage/software bundles|software bundle]] or software "appliance" on a [[w:Virtual private server|virtual private server]]. </div> Não agregue serviços de alojamento a esta lista sem um enlace directo a uma página que indique "explicitamente" o alojamento de MediaWiki. <!-- Please keep the list in ALPHABETIC ORDER. Thank you! --> {| class="wikitable sortable" {{:Hosting services/Header}} |- !<br/> ! ! ! ! ! ! ! ! ! |- | [https://www.20i.com/mediawiki-hosting 20i] | USA, UK | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://www.a2hosting.com/mediawiki-hosting A2 Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://albatross.cloud/mediawiki-hosting Albatross Cloud] | USA | host | Managed Hosting and Cloud Services with exceptional support for Medium and Enterprise Clientele. | {{no}} | paid | Yes or subdomain | | 24/7 | |- | [https://www.arvixe.com/mediawiki_hosting Arvixe Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://biowikifarm.net/meta/Biowikifarm Biowikifarm] | Germany | farm | for non-commercial dissemination of biological open-content data | {{yes}} | free | | | | |- | [https://civihosting.com/mediawiki-hosting/ CiviHosting] | USA, Europe | host | Boutique-style hosting firm including account sizes for personal, business and enterprise-level wikis, including [[Extension:Semantic MediaWiki|Semantic MediaWiki]] and [[BlueSpice]] | {{no}} | paid | Yes, as well as domain registration service, or a subdomain is possible | SSH access | 24/7 support with 5 minute response time included with all accounts | [https://civihosting.com/shared-hosting/ Shared] and [https://civihosting.com/vps-hosting/ VPS hosting] available. Services include * Free installation and migration * Daily backups * 24/7 support with 5 minute response time * [https://civihosting.com/semantic-mediawiki-hosting/ Semantic MediaWiki] hosting * BlueSpice hosting * Turnkey solution for MediaWiki hosting |- | [https://www.cloudways.com/en/managed-mediawiki-cloud-hosting.php Cloudways.com] | Malta | host | | {{no}} | paid | You have to set it up independently | {{yes}} | | Quick setup, automatic backup, cloud-based (included in the cost). Support staff also in Dubai, Pakistan and Spain. |- | [https://help.dreamhost.com/hc/en-us/articles/217292577-MediaWiki-overview Dreamhost.com] | USA | host | | {{no}} | paid | | limited ssh access | 24/7 via tickets and email. | Also offers [https://help.dreamhost.com/hc/en-us/articles/215769478-Non-profit-discount free hosting service for non-profits.] |- |[https://community.fandom.com/wiki/Choosing_Fandom Fandom] | United States, France, Poland, Indonesia, Australia | farm | Entertainment, Lifestyle, Video Games and Anime | {{yes}} | free (with ads) | custom [[w:subdomain|subdomain]] only. | {{no}} | [https://fandom.zendesk.com/ Contact] and community forums | [https://www.fandom.com/community-creation-policy Wikis are not owned by their founders]. Fandom may take decisions affecting the community even if there's no consensus at all. They reserve the [https://community.fandom.com/wiki/Thread:1572365 right to change the wikis URL for SEO purposes]. In case the community wants to move to another host, the wiki and its content in most cases can't or won't be deleted from Fandom. There's only one skin available and it's proprietary. New Wikis Run MediaWiki 1.37.2 whilst older Wikis run MediaWiki 1.33. |- | [https://fastdot.com/hosting/cpanel-cloud-hosting/mediawiki-hosting/ Fastdot Hosting] | Australia, Asia Pacific, USA, UK | host | | {{no}} | paid | | | | 1-click installer |- | [https://hostdash.com/mediawiki-hosting/ HostDash] | USA | host | Blazing fast wiki hosting solutions, backed by 24/7 expert support & a 60 day money back guarantee. | {{no}} | paid | {{yes}} | | 24/7 | * 1-Click Setup * FREE Domain Name * 24/7 Expert Support * Proactive Malware Protection * cPanel Control Panel * 60 Day Money Back Guarantee |- | [https://www.hostgator.com/apps/wiki-hosting HostGator] | USA | host | | {{no}} | paid | {{yes}} | | | |- |[https://hostiso.com/mediawiki-hosting Hostiso] |USA, Canada, Germany, France, Singapore |host |Managed Hosting and Services with exceptional support for mediwiki clients! | {{no}} |paid |yes or subdomain | |24/7 |1-click setup, free backups, support, cPanel, cloud-based. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.hostknox.com/mediawiki-hosting HostKnox] | USA | host | | {{no}} | paid | {{yes}} | Chrooted (jailed) SSH | 24/7 via support tickets. 15-minute response time. | Free MediaWiki installation, transfer & upgrade. |- |[https://www.knownhost.com/media-wiki-hosting.html KnownHost] |USA, Europe |host | | {{no}} |paid | |SSH Access |24/7/365 Email and Ticket Support. |Free install support. Shared, VPS, Cloud and Dedicated Server lines. |- | [https://www.milesweb.com/mediawiki-hosting.php MilesWeb.com] | UK, US, India, Romania | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://miraheze.org Miraheze] | UK | farm | | {{yes}} | free (no ads) | {{optional}} | {{no}} | IRC, Email, Issue trackers, Wiki venues, Discord server | Community-driven, not-for-profit, quick wiki creation, HTTPS-only, public and private wikis. Infrastructure 100% [https://github.com/miraheze open source]. No hard limits on server resource usage and runs latest MediaWiki version. |- | [https://www.mywikis.com/ MyWikis] | USA We speak English / Nosotros hablamos español / On parle français / 我们讲中文 / हमें हिंदी आती है | host | Private wikis (public wikis are still available)<br />Different plans available, tailored for enterprise customers, personal wikis, and anywhere in between. | {{no}} | paid (no ads) | {{yes}} | FTP and SSH on request | Support system, email, phone, Zoom, Microsoft Teams, and Google Meet | * Wikis created automatically in under 5 minutes with 40+ extensions preinstalled. Hundreds of extensions available to install. * Self Service portal, where you can manage your wiki, add extensions to your wiki, reset passwords, and more. * Free migrations for most wikis; extensive experience in migrating from MediaWiki and other platforms. * 24/7 professional (not volunteer) personalized support from MediaWiki experts with 10+ years of experience; support response times guaranteed through SLAs. * 9 different privacy levels. Anti-spam built into every wiki. Wikis backed up daily. * Use a subdomain, buy a domain through MyWikis, or bring your own domain. |- | [https://neowiki.neoseeker.com/wiki/Alternative_To_Wikia Neoseeker] | | farm | game and entertainment-related wikis | {{yes}} | free | | | | |- |[https://OpenFox.io OpenFox.io] |Europe |Cloud based |Orgnaisational Wikis | {{no}} |Monthly and Annual |Company domain or Openfox.io subdomain. | {{no}} |Wiki set-up, consulting and implementation |Managed wiki Service with high security as well as set-up and organisational implementation support |- | [https://professional.wiki Professional.Wiki] | Europe | dedicated server | Professional services for companies of all sizes. Unmatched [[Semantic MediaWiki]] expertise. | {{no}} | paid | {{yes}} | {{yes}} | yes, with real experts | [https://professional.wiki/en/hosting Holistic services] including setup, management, support, training and custom development. Run by [https://professional.wiki/en/about MediaWiki veterans]. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.rosehosting.com/mediawiki-vps-hosting.html RoseHosting] | USA | host | | {{no}} | paid | | | | Linux VPS hosting. |- | [https://www.saasweb.net/auto/managed-hosting/mediawiki SaaS Web Internet Solutions] | Germany | host | Standard, BlueSpice Free/Pro, Semantic MediaWiki | {{no}} | paid | always | {{no}} | Phone at business hours, email 24x7 | Fully managed MediaWiki on several infrastructures (as needed): Shared Hosting, Dedicated - both either on OpenStack Public Cloud or VMware Private Cloud |- | [https://www.shoutwiki.com/ ShoutWiki] | | farm | | {{yes}} | free; ad-supported; paid | [https://www.shoutwiki.com/wiki/Set_up_custom_domain possible] | {{no}} | [https://www.shoutwiki.com/wiki/Special:Contact Contact] and [https://www.shoutwiki.com/wiki/Forum:Index Forum] at ShoutWiki Hub | From MediaWiki developers and others. Lacks HTTPS/SSL support. |- | [https://www.siteground.com/mediawiki-hosting.htm SiteGround] | USA, Netherlands, Singapore | host | | {{no}} | paid | {{yes}} | | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://wiki.gg/ wiki.gg] | USA | farm | | {{Yes}} | Free | {{No}} | | Email | Private wiki-farm, wikis are only created on request by staff, and they prefer wikis with developer/publisher support to either provide assets or information for the wiki or for the wiki to become Official. |- | [https://webarch.coop/mediawiki Webarchitects] | UK | farm | | {{no}} | paid | {{yes}} | Optional SSH access | IRC, email, phone | Multi-stakeholder cooperative with social responsibility focus, green power and green hardware, emphasis on free and open source software ([https://git.coop/webarch/mediawiki Ansible playbook published under GPLv3]). |- | [https://www.webhostuk.co.uk/wiki-hosting.html Webhost UK LTD] | UK, US | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- class="sortbottom" {{:Hosting services/Header}} |- | [https://wiki-valley.com Wiki Valley] (fr) [https://en.wiki-valley.com/Create_your_own_private_wiki_online_and_manage_knowledge Wiki Valley](en) | France | farm | Private wikis | {{no}} | [https://wiki-valley.com/wiki/Tarifs_de_l_hebergement_des_wikis by user/month and options] | {{yes}} | {{no}} | mail, chat, phone and wiki | [https://wiki-valley.com/wiki/Sp%C3%A9cial:Contact Création à la demande] (fr) [https://en.wiki-valley.com/Special:Contact Creation on demand] (en)<br/> |- | [https://www.wikibase.nl/Diensten/Managed_hosting Wikibase Solutions] | The Netherlands | host | Fully managed Wiki hosting in addition to a core business of developing Semantic MediaWiki solutions | {{no}} | paid | {{yes}} | at request | phone, Skype and email | Also provides support for Elasticsearch and other requested services. |- | [https://www.wikihoster.net/ WikiHoster.net] | Germany | farm | Semantic MediaWiki, updates and upgrades included in plans (serviced) | {{no}} | paid | possible | serviced (see specialism) | Phone and email at business hours | German site. Available for customers in the [[wikipedia:Single Euro Payments Area|SEPA-area]]. |- | [http://www.wiki-site.com/ Wiki-Site] | United States, Israel | farm | | {{yes}} | free (with ads) | | | | Available in 25 languages. Runs [[MediaWiki 1.11]]. Lacks HTTPS/SSL support. |- | [https://www.wikiteq.com/ WikiTeq] | USA | host | Professionally managed hosting on a private VPS | {{no}} | paid | {{yes}} | {{yes}} | On-call support team ready 24/7 | Enterprised-focused full-service MediaWiki development company providing fully supported and maintained wikis. |- | [https://meta.rdpstudio.top FutureWiki] | China | farm | | {{no}} | one time paid at creation, sometimes free by event | {{no}} | {{no}} | Email, wiki page | Quick wiki creation, HTTPS-only. Only for Chinese users. Currently in matainance. |} <div lang="en" dir="ltr" class="mw-content-ltr"> == External links == </div> * [[wikiapiary:Host:Hosts|Hosts]] listados em [[WikiApiary]]. * <span lang="en" dir="ltr" class="mw-content-ltr">[[wikiapiary:Farm:Farms|Farms]] listed at WikiApiary.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikibooks:Starting and Running a Wiki Website/Hosted Wikis]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[w:Comparison of wiki hosting services|Comparison of wiki hosting services]]</span> * [https://www.wikimatrix.org WikiMatrix] * <span lang="en" dir="ltr" class="mw-content-ltr">[https://curlie.org/Computers/Software/Groupware/Wiki/Wiki_Farms Wiki farms] at [[w:DMOZ|DMOZ]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikiindex.org/Category:WikiFarm Category:WikiFarm] at WikiIndex.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://github.com/WikiTeam/wikiteam/wiki/WikiFarms WikiFarms - wikiteam - tools for archiving wikis]. On [[w:GitHub|GitHub]].</span> [[Category:MediaWiki References{{#translation:}}]] 1so8zt0v5k0pmnq1svyi9ayozelp0x8 5386402 5386400 2022-07-28T13:47:20Z 201.47.225.82 Created page with "Se você deseja executar um wiki MediaWiki e não deseja manter sua própria infraestrutura, pode estar interessado nos ''[[$1|wiki farms]]'' e nos serviços de hospedagem listados abaixo." wikitext text/x-wiki <languages/> {{Warn|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Be warned''' that the Wikimedia Foundation does not guarantee the quality of or endorse any of the services on the list.</span>}} {{toc right}} Se você deseja executar um wiki MediaWiki e não deseja manter sua própria infraestrutura, pode estar interessado nos ''[[Special:MyLanguage/Manual:Wiki family|wiki farms]]'' e nos serviços de hospedagem listados abaixo. <div lang="en" dir="ltr" class="mw-content-ltr"> * In addition, most regular web hosting companies allow for installing MediaWiki without too much trouble, although maintaining and upgrading the code would still in most cases be up to you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * You can also install a pre-made [[Special:MyLanguage/software bundles|software bundle]] or software "appliance" on a [[w:Virtual private server|virtual private server]]. </div> Não agregue serviços de alojamento a esta lista sem um enlace directo a uma página que indique "explicitamente" o alojamento de MediaWiki. <!-- Please keep the list in ALPHABETIC ORDER. Thank you! --> {| class="wikitable sortable" {{:Hosting services/Header}} |- !<br/> ! ! ! ! ! ! ! ! ! |- | [https://www.20i.com/mediawiki-hosting 20i] | USA, UK | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://www.a2hosting.com/mediawiki-hosting A2 Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://albatross.cloud/mediawiki-hosting Albatross Cloud] | USA | host | Managed Hosting and Cloud Services with exceptional support for Medium and Enterprise Clientele. | {{no}} | paid | Yes or subdomain | | 24/7 | |- | [https://www.arvixe.com/mediawiki_hosting Arvixe Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://biowikifarm.net/meta/Biowikifarm Biowikifarm] | Germany | farm | for non-commercial dissemination of biological open-content data | {{yes}} | free | | | | |- | [https://civihosting.com/mediawiki-hosting/ CiviHosting] | USA, Europe | host | Boutique-style hosting firm including account sizes for personal, business and enterprise-level wikis, including [[Extension:Semantic MediaWiki|Semantic MediaWiki]] and [[BlueSpice]] | {{no}} | paid | Yes, as well as domain registration service, or a subdomain is possible | SSH access | 24/7 support with 5 minute response time included with all accounts | [https://civihosting.com/shared-hosting/ Shared] and [https://civihosting.com/vps-hosting/ VPS hosting] available. Services include * Free installation and migration * Daily backups * 24/7 support with 5 minute response time * [https://civihosting.com/semantic-mediawiki-hosting/ Semantic MediaWiki] hosting * BlueSpice hosting * Turnkey solution for MediaWiki hosting |- | [https://www.cloudways.com/en/managed-mediawiki-cloud-hosting.php Cloudways.com] | Malta | host | | {{no}} | paid | You have to set it up independently | {{yes}} | | Quick setup, automatic backup, cloud-based (included in the cost). Support staff also in Dubai, Pakistan and Spain. |- | [https://help.dreamhost.com/hc/en-us/articles/217292577-MediaWiki-overview Dreamhost.com] | USA | host | | {{no}} | paid | | limited ssh access | 24/7 via tickets and email. | Also offers [https://help.dreamhost.com/hc/en-us/articles/215769478-Non-profit-discount free hosting service for non-profits.] |- |[https://community.fandom.com/wiki/Choosing_Fandom Fandom] | United States, France, Poland, Indonesia, Australia | farm | Entertainment, Lifestyle, Video Games and Anime | {{yes}} | free (with ads) | custom [[w:subdomain|subdomain]] only. | {{no}} | [https://fandom.zendesk.com/ Contact] and community forums | [https://www.fandom.com/community-creation-policy Wikis are not owned by their founders]. Fandom may take decisions affecting the community even if there's no consensus at all. They reserve the [https://community.fandom.com/wiki/Thread:1572365 right to change the wikis URL for SEO purposes]. In case the community wants to move to another host, the wiki and its content in most cases can't or won't be deleted from Fandom. There's only one skin available and it's proprietary. New Wikis Run MediaWiki 1.37.2 whilst older Wikis run MediaWiki 1.33. |- | [https://fastdot.com/hosting/cpanel-cloud-hosting/mediawiki-hosting/ Fastdot Hosting] | Australia, Asia Pacific, USA, UK | host | | {{no}} | paid | | | | 1-click installer |- | [https://hostdash.com/mediawiki-hosting/ HostDash] | USA | host | Blazing fast wiki hosting solutions, backed by 24/7 expert support & a 60 day money back guarantee. | {{no}} | paid | {{yes}} | | 24/7 | * 1-Click Setup * FREE Domain Name * 24/7 Expert Support * Proactive Malware Protection * cPanel Control Panel * 60 Day Money Back Guarantee |- | [https://www.hostgator.com/apps/wiki-hosting HostGator] | USA | host | | {{no}} | paid | {{yes}} | | | |- |[https://hostiso.com/mediawiki-hosting Hostiso] |USA, Canada, Germany, France, Singapore |host |Managed Hosting and Services with exceptional support for mediwiki clients! | {{no}} |paid |yes or subdomain | |24/7 |1-click setup, free backups, support, cPanel, cloud-based. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.hostknox.com/mediawiki-hosting HostKnox] | USA | host | | {{no}} | paid | {{yes}} | Chrooted (jailed) SSH | 24/7 via support tickets. 15-minute response time. | Free MediaWiki installation, transfer & upgrade. |- |[https://www.knownhost.com/media-wiki-hosting.html KnownHost] |USA, Europe |host | | {{no}} |paid | |SSH Access |24/7/365 Email and Ticket Support. |Free install support. Shared, VPS, Cloud and Dedicated Server lines. |- | [https://www.milesweb.com/mediawiki-hosting.php MilesWeb.com] | UK, US, India, Romania | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://miraheze.org Miraheze] | UK | farm | | {{yes}} | free (no ads) | {{optional}} | {{no}} | IRC, Email, Issue trackers, Wiki venues, Discord server | Community-driven, not-for-profit, quick wiki creation, HTTPS-only, public and private wikis. Infrastructure 100% [https://github.com/miraheze open source]. No hard limits on server resource usage and runs latest MediaWiki version. |- | [https://www.mywikis.com/ MyWikis] | USA We speak English / Nosotros hablamos español / On parle français / 我们讲中文 / हमें हिंदी आती है | host | Private wikis (public wikis are still available)<br />Different plans available, tailored for enterprise customers, personal wikis, and anywhere in between. | {{no}} | paid (no ads) | {{yes}} | FTP and SSH on request | Support system, email, phone, Zoom, Microsoft Teams, and Google Meet | * Wikis created automatically in under 5 minutes with 40+ extensions preinstalled. Hundreds of extensions available to install. * Self Service portal, where you can manage your wiki, add extensions to your wiki, reset passwords, and more. * Free migrations for most wikis; extensive experience in migrating from MediaWiki and other platforms. * 24/7 professional (not volunteer) personalized support from MediaWiki experts with 10+ years of experience; support response times guaranteed through SLAs. * 9 different privacy levels. Anti-spam built into every wiki. Wikis backed up daily. * Use a subdomain, buy a domain through MyWikis, or bring your own domain. |- | [https://neowiki.neoseeker.com/wiki/Alternative_To_Wikia Neoseeker] | | farm | game and entertainment-related wikis | {{yes}} | free | | | | |- |[https://OpenFox.io OpenFox.io] |Europe |Cloud based |Orgnaisational Wikis | {{no}} |Monthly and Annual |Company domain or Openfox.io subdomain. | {{no}} |Wiki set-up, consulting and implementation |Managed wiki Service with high security as well as set-up and organisational implementation support |- | [https://professional.wiki Professional.Wiki] | Europe | dedicated server | Professional services for companies of all sizes. Unmatched [[Semantic MediaWiki]] expertise. | {{no}} | paid | {{yes}} | {{yes}} | yes, with real experts | [https://professional.wiki/en/hosting Holistic services] including setup, management, support, training and custom development. Run by [https://professional.wiki/en/about MediaWiki veterans]. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.rosehosting.com/mediawiki-vps-hosting.html RoseHosting] | USA | host | | {{no}} | paid | | | | Linux VPS hosting. |- | [https://www.saasweb.net/auto/managed-hosting/mediawiki SaaS Web Internet Solutions] | Germany | host | Standard, BlueSpice Free/Pro, Semantic MediaWiki | {{no}} | paid | always | {{no}} | Phone at business hours, email 24x7 | Fully managed MediaWiki on several infrastructures (as needed): Shared Hosting, Dedicated - both either on OpenStack Public Cloud or VMware Private Cloud |- | [https://www.shoutwiki.com/ ShoutWiki] | | farm | | {{yes}} | free; ad-supported; paid | [https://www.shoutwiki.com/wiki/Set_up_custom_domain possible] | {{no}} | [https://www.shoutwiki.com/wiki/Special:Contact Contact] and [https://www.shoutwiki.com/wiki/Forum:Index Forum] at ShoutWiki Hub | From MediaWiki developers and others. Lacks HTTPS/SSL support. |- | [https://www.siteground.com/mediawiki-hosting.htm SiteGround] | USA, Netherlands, Singapore | host | | {{no}} | paid | {{yes}} | | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://wiki.gg/ wiki.gg] | USA | farm | | {{Yes}} | Free | {{No}} | | Email | Private wiki-farm, wikis are only created on request by staff, and they prefer wikis with developer/publisher support to either provide assets or information for the wiki or for the wiki to become Official. |- | [https://webarch.coop/mediawiki Webarchitects] | UK | farm | | {{no}} | paid | {{yes}} | Optional SSH access | IRC, email, phone | Multi-stakeholder cooperative with social responsibility focus, green power and green hardware, emphasis on free and open source software ([https://git.coop/webarch/mediawiki Ansible playbook published under GPLv3]). |- | [https://www.webhostuk.co.uk/wiki-hosting.html Webhost UK LTD] | UK, US | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- class="sortbottom" {{:Hosting services/Header}} |- | [https://wiki-valley.com Wiki Valley] (fr) [https://en.wiki-valley.com/Create_your_own_private_wiki_online_and_manage_knowledge Wiki Valley](en) | France | farm | Private wikis | {{no}} | [https://wiki-valley.com/wiki/Tarifs_de_l_hebergement_des_wikis by user/month and options] | {{yes}} | {{no}} | mail, chat, phone and wiki | [https://wiki-valley.com/wiki/Sp%C3%A9cial:Contact Création à la demande] (fr) [https://en.wiki-valley.com/Special:Contact Creation on demand] (en)<br/> |- | [https://www.wikibase.nl/Diensten/Managed_hosting Wikibase Solutions] | The Netherlands | host | Fully managed Wiki hosting in addition to a core business of developing Semantic MediaWiki solutions | {{no}} | paid | {{yes}} | at request | phone, Skype and email | Also provides support for Elasticsearch and other requested services. |- | [https://www.wikihoster.net/ WikiHoster.net] | Germany | farm | Semantic MediaWiki, updates and upgrades included in plans (serviced) | {{no}} | paid | possible | serviced (see specialism) | Phone and email at business hours | German site. Available for customers in the [[wikipedia:Single Euro Payments Area|SEPA-area]]. |- | [http://www.wiki-site.com/ Wiki-Site] | United States, Israel | farm | | {{yes}} | free (with ads) | | | | Available in 25 languages. Runs [[MediaWiki 1.11]]. Lacks HTTPS/SSL support. |- | [https://www.wikiteq.com/ WikiTeq] | USA | host | Professionally managed hosting on a private VPS | {{no}} | paid | {{yes}} | {{yes}} | On-call support team ready 24/7 | Enterprised-focused full-service MediaWiki development company providing fully supported and maintained wikis. |- | [https://meta.rdpstudio.top FutureWiki] | China | farm | | {{no}} | one time paid at creation, sometimes free by event | {{no}} | {{no}} | Email, wiki page | Quick wiki creation, HTTPS-only. Only for Chinese users. Currently in matainance. |} <div lang="en" dir="ltr" class="mw-content-ltr"> == External links == </div> * [[wikiapiary:Host:Hosts|Hosts]] listados em [[WikiApiary]]. * <span lang="en" dir="ltr" class="mw-content-ltr">[[wikiapiary:Farm:Farms|Farms]] listed at WikiApiary.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikibooks:Starting and Running a Wiki Website/Hosted Wikis]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[w:Comparison of wiki hosting services|Comparison of wiki hosting services]]</span> * [https://www.wikimatrix.org WikiMatrix] * <span lang="en" dir="ltr" class="mw-content-ltr">[https://curlie.org/Computers/Software/Groupware/Wiki/Wiki_Farms Wiki farms] at [[w:DMOZ|DMOZ]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikiindex.org/Category:WikiFarm Category:WikiFarm] at WikiIndex.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://github.com/WikiTeam/wikiteam/wiki/WikiFarms WikiFarms - wikiteam - tools for archiving wikis]. On [[w:GitHub|GitHub]].</span> [[Category:MediaWiki References{{#translation:}}]] kgqg2037gqcjo1ypkztsd754v2zxubc 5386408 5386402 2022-07-28T13:48:37Z 201.47.225.82 Created page with "$url Categoria:WikiFarm] no WikiIndex." wikitext text/x-wiki <languages/> {{Warn|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Be warned''' that the Wikimedia Foundation does not guarantee the quality of or endorse any of the services on the list.</span>}} {{toc right}} Se você deseja executar um wiki MediaWiki e não deseja manter sua própria infraestrutura, pode estar interessado nos ''[[Special:MyLanguage/Manual:Wiki family|wiki farms]]'' e nos serviços de hospedagem listados abaixo. <div lang="en" dir="ltr" class="mw-content-ltr"> * In addition, most regular web hosting companies allow for installing MediaWiki without too much trouble, although maintaining and upgrading the code would still in most cases be up to you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * You can also install a pre-made [[Special:MyLanguage/software bundles|software bundle]] or software "appliance" on a [[w:Virtual private server|virtual private server]]. </div> Não agregue serviços de alojamento a esta lista sem um enlace directo a uma página que indique "explicitamente" o alojamento de MediaWiki. <!-- Please keep the list in ALPHABETIC ORDER. Thank you! --> {| class="wikitable sortable" {{:Hosting services/Header}} |- !<br/> ! ! ! ! ! ! ! ! ! |- | [https://www.20i.com/mediawiki-hosting 20i] | USA, UK | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://www.a2hosting.com/mediawiki-hosting A2 Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://albatross.cloud/mediawiki-hosting Albatross Cloud] | USA | host | Managed Hosting and Cloud Services with exceptional support for Medium and Enterprise Clientele. | {{no}} | paid | Yes or subdomain | | 24/7 | |- | [https://www.arvixe.com/mediawiki_hosting Arvixe Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://biowikifarm.net/meta/Biowikifarm Biowikifarm] | Germany | farm | for non-commercial dissemination of biological open-content data | {{yes}} | free | | | | |- | [https://civihosting.com/mediawiki-hosting/ CiviHosting] | USA, Europe | host | Boutique-style hosting firm including account sizes for personal, business and enterprise-level wikis, including [[Extension:Semantic MediaWiki|Semantic MediaWiki]] and [[BlueSpice]] | {{no}} | paid | Yes, as well as domain registration service, or a subdomain is possible | SSH access | 24/7 support with 5 minute response time included with all accounts | [https://civihosting.com/shared-hosting/ Shared] and [https://civihosting.com/vps-hosting/ VPS hosting] available. Services include * Free installation and migration * Daily backups * 24/7 support with 5 minute response time * [https://civihosting.com/semantic-mediawiki-hosting/ Semantic MediaWiki] hosting * BlueSpice hosting * Turnkey solution for MediaWiki hosting |- | [https://www.cloudways.com/en/managed-mediawiki-cloud-hosting.php Cloudways.com] | Malta | host | | {{no}} | paid | You have to set it up independently | {{yes}} | | Quick setup, automatic backup, cloud-based (included in the cost). Support staff also in Dubai, Pakistan and Spain. |- | [https://help.dreamhost.com/hc/en-us/articles/217292577-MediaWiki-overview Dreamhost.com] | USA | host | | {{no}} | paid | | limited ssh access | 24/7 via tickets and email. | Also offers [https://help.dreamhost.com/hc/en-us/articles/215769478-Non-profit-discount free hosting service for non-profits.] |- |[https://community.fandom.com/wiki/Choosing_Fandom Fandom] | United States, France, Poland, Indonesia, Australia | farm | Entertainment, Lifestyle, Video Games and Anime | {{yes}} | free (with ads) | custom [[w:subdomain|subdomain]] only. | {{no}} | [https://fandom.zendesk.com/ Contact] and community forums | [https://www.fandom.com/community-creation-policy Wikis are not owned by their founders]. Fandom may take decisions affecting the community even if there's no consensus at all. They reserve the [https://community.fandom.com/wiki/Thread:1572365 right to change the wikis URL for SEO purposes]. In case the community wants to move to another host, the wiki and its content in most cases can't or won't be deleted from Fandom. There's only one skin available and it's proprietary. New Wikis Run MediaWiki 1.37.2 whilst older Wikis run MediaWiki 1.33. |- | [https://fastdot.com/hosting/cpanel-cloud-hosting/mediawiki-hosting/ Fastdot Hosting] | Australia, Asia Pacific, USA, UK | host | | {{no}} | paid | | | | 1-click installer |- | [https://hostdash.com/mediawiki-hosting/ HostDash] | USA | host | Blazing fast wiki hosting solutions, backed by 24/7 expert support & a 60 day money back guarantee. | {{no}} | paid | {{yes}} | | 24/7 | * 1-Click Setup * FREE Domain Name * 24/7 Expert Support * Proactive Malware Protection * cPanel Control Panel * 60 Day Money Back Guarantee |- | [https://www.hostgator.com/apps/wiki-hosting HostGator] | USA | host | | {{no}} | paid | {{yes}} | | | |- |[https://hostiso.com/mediawiki-hosting Hostiso] |USA, Canada, Germany, France, Singapore |host |Managed Hosting and Services with exceptional support for mediwiki clients! | {{no}} |paid |yes or subdomain | |24/7 |1-click setup, free backups, support, cPanel, cloud-based. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.hostknox.com/mediawiki-hosting HostKnox] | USA | host | | {{no}} | paid | {{yes}} | Chrooted (jailed) SSH | 24/7 via support tickets. 15-minute response time. | Free MediaWiki installation, transfer & upgrade. |- |[https://www.knownhost.com/media-wiki-hosting.html KnownHost] |USA, Europe |host | | {{no}} |paid | |SSH Access |24/7/365 Email and Ticket Support. |Free install support. Shared, VPS, Cloud and Dedicated Server lines. |- | [https://www.milesweb.com/mediawiki-hosting.php MilesWeb.com] | UK, US, India, Romania | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://miraheze.org Miraheze] | UK | farm | | {{yes}} | free (no ads) | {{optional}} | {{no}} | IRC, Email, Issue trackers, Wiki venues, Discord server | Community-driven, not-for-profit, quick wiki creation, HTTPS-only, public and private wikis. Infrastructure 100% [https://github.com/miraheze open source]. No hard limits on server resource usage and runs latest MediaWiki version. |- | [https://www.mywikis.com/ MyWikis] | USA We speak English / Nosotros hablamos español / On parle français / 我们讲中文 / हमें हिंदी आती है | host | Private wikis (public wikis are still available)<br />Different plans available, tailored for enterprise customers, personal wikis, and anywhere in between. | {{no}} | paid (no ads) | {{yes}} | FTP and SSH on request | Support system, email, phone, Zoom, Microsoft Teams, and Google Meet | * Wikis created automatically in under 5 minutes with 40+ extensions preinstalled. Hundreds of extensions available to install. * Self Service portal, where you can manage your wiki, add extensions to your wiki, reset passwords, and more. * Free migrations for most wikis; extensive experience in migrating from MediaWiki and other platforms. * 24/7 professional (not volunteer) personalized support from MediaWiki experts with 10+ years of experience; support response times guaranteed through SLAs. * 9 different privacy levels. Anti-spam built into every wiki. Wikis backed up daily. * Use a subdomain, buy a domain through MyWikis, or bring your own domain. |- | [https://neowiki.neoseeker.com/wiki/Alternative_To_Wikia Neoseeker] | | farm | game and entertainment-related wikis | {{yes}} | free | | | | |- |[https://OpenFox.io OpenFox.io] |Europe |Cloud based |Orgnaisational Wikis | {{no}} |Monthly and Annual |Company domain or Openfox.io subdomain. | {{no}} |Wiki set-up, consulting and implementation |Managed wiki Service with high security as well as set-up and organisational implementation support |- | [https://professional.wiki Professional.Wiki] | Europe | dedicated server | Professional services for companies of all sizes. Unmatched [[Semantic MediaWiki]] expertise. | {{no}} | paid | {{yes}} | {{yes}} | yes, with real experts | [https://professional.wiki/en/hosting Holistic services] including setup, management, support, training and custom development. Run by [https://professional.wiki/en/about MediaWiki veterans]. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.rosehosting.com/mediawiki-vps-hosting.html RoseHosting] | USA | host | | {{no}} | paid | | | | Linux VPS hosting. |- | [https://www.saasweb.net/auto/managed-hosting/mediawiki SaaS Web Internet Solutions] | Germany | host | Standard, BlueSpice Free/Pro, Semantic MediaWiki | {{no}} | paid | always | {{no}} | Phone at business hours, email 24x7 | Fully managed MediaWiki on several infrastructures (as needed): Shared Hosting, Dedicated - both either on OpenStack Public Cloud or VMware Private Cloud |- | [https://www.shoutwiki.com/ ShoutWiki] | | farm | | {{yes}} | free; ad-supported; paid | [https://www.shoutwiki.com/wiki/Set_up_custom_domain possible] | {{no}} | [https://www.shoutwiki.com/wiki/Special:Contact Contact] and [https://www.shoutwiki.com/wiki/Forum:Index Forum] at ShoutWiki Hub | From MediaWiki developers and others. Lacks HTTPS/SSL support. |- | [https://www.siteground.com/mediawiki-hosting.htm SiteGround] | USA, Netherlands, Singapore | host | | {{no}} | paid | {{yes}} | | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://wiki.gg/ wiki.gg] | USA | farm | | {{Yes}} | Free | {{No}} | | Email | Private wiki-farm, wikis are only created on request by staff, and they prefer wikis with developer/publisher support to either provide assets or information for the wiki or for the wiki to become Official. |- | [https://webarch.coop/mediawiki Webarchitects] | UK | farm | | {{no}} | paid | {{yes}} | Optional SSH access | IRC, email, phone | Multi-stakeholder cooperative with social responsibility focus, green power and green hardware, emphasis on free and open source software ([https://git.coop/webarch/mediawiki Ansible playbook published under GPLv3]). |- | [https://www.webhostuk.co.uk/wiki-hosting.html Webhost UK LTD] | UK, US | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- class="sortbottom" {{:Hosting services/Header}} |- | [https://wiki-valley.com Wiki Valley] (fr) [https://en.wiki-valley.com/Create_your_own_private_wiki_online_and_manage_knowledge Wiki Valley](en) | France | farm | Private wikis | {{no}} | [https://wiki-valley.com/wiki/Tarifs_de_l_hebergement_des_wikis by user/month and options] | {{yes}} | {{no}} | mail, chat, phone and wiki | [https://wiki-valley.com/wiki/Sp%C3%A9cial:Contact Création à la demande] (fr) [https://en.wiki-valley.com/Special:Contact Creation on demand] (en)<br/> |- | [https://www.wikibase.nl/Diensten/Managed_hosting Wikibase Solutions] | The Netherlands | host | Fully managed Wiki hosting in addition to a core business of developing Semantic MediaWiki solutions | {{no}} | paid | {{yes}} | at request | phone, Skype and email | Also provides support for Elasticsearch and other requested services. |- | [https://www.wikihoster.net/ WikiHoster.net] | Germany | farm | Semantic MediaWiki, updates and upgrades included in plans (serviced) | {{no}} | paid | possible | serviced (see specialism) | Phone and email at business hours | German site. Available for customers in the [[wikipedia:Single Euro Payments Area|SEPA-area]]. |- | [http://www.wiki-site.com/ Wiki-Site] | United States, Israel | farm | | {{yes}} | free (with ads) | | | | Available in 25 languages. Runs [[MediaWiki 1.11]]. Lacks HTTPS/SSL support. |- | [https://www.wikiteq.com/ WikiTeq] | USA | host | Professionally managed hosting on a private VPS | {{no}} | paid | {{yes}} | {{yes}} | On-call support team ready 24/7 | Enterprised-focused full-service MediaWiki development company providing fully supported and maintained wikis. |- | [https://meta.rdpstudio.top FutureWiki] | China | farm | | {{no}} | one time paid at creation, sometimes free by event | {{no}} | {{no}} | Email, wiki page | Quick wiki creation, HTTPS-only. Only for Chinese users. Currently in matainance. |} <div lang="en" dir="ltr" class="mw-content-ltr"> == External links == </div> * [[wikiapiary:Host:Hosts|Hosts]] listados em [[WikiApiary]]. * <span lang="en" dir="ltr" class="mw-content-ltr">[[wikiapiary:Farm:Farms|Farms]] listed at WikiApiary.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikibooks:Starting and Running a Wiki Website/Hosted Wikis]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[w:Comparison of wiki hosting services|Comparison of wiki hosting services]]</span> * [https://www.wikimatrix.org WikiMatrix] * <span lang="en" dir="ltr" class="mw-content-ltr">[https://curlie.org/Computers/Software/Groupware/Wiki/Wiki_Farms Wiki farms] at [[w:DMOZ|DMOZ]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikiindex.org/Category:WikiFarm Category:WikiFarm] at WikiIndex.</span> * <span class="mw-translate-fuzzy">https://github.com/WikiTeam/wikiteam/wiki/WikiFarms Categoria:WikiFarm] no WikiIndex.</span> [[Category:MediaWiki References{{#translation:}}]] rgjfhbcynxykyabbgcalkf50g08w68e 5386411 5386408 2022-07-28T13:50:45Z Clump 81610 Not a translation wikitext text/x-wiki <languages/> {{Warn|1=<span lang="en" dir="ltr" class="mw-content-ltr">'''Be warned''' that the Wikimedia Foundation does not guarantee the quality of or endorse any of the services on the list.</span>}} {{toc right}} Se você deseja executar um wiki MediaWiki e não deseja manter sua própria infraestrutura, pode estar interessado nos ''[[Special:MyLanguage/Manual:Wiki family|wiki farms]]'' e nos serviços de hospedagem listados abaixo. <div lang="en" dir="ltr" class="mw-content-ltr"> * In addition, most regular web hosting companies allow for installing MediaWiki without too much trouble, although maintaining and upgrading the code would still in most cases be up to you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * You can also install a pre-made [[Special:MyLanguage/software bundles|software bundle]] or software "appliance" on a [[w:Virtual private server|virtual private server]]. </div> Não agregue serviços de alojamento a esta lista sem um enlace directo a uma página que indique "explicitamente" o alojamento de MediaWiki. <!-- Please keep the list in ALPHABETIC ORDER. Thank you! --> {| class="wikitable sortable" {{:Hosting services/Header}} |- !<br/> ! ! ! ! ! ! ! ! ! |- | [https://www.20i.com/mediawiki-hosting 20i] | USA, UK | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://www.a2hosting.com/mediawiki-hosting A2 Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://albatross.cloud/mediawiki-hosting Albatross Cloud] | USA | host | Managed Hosting and Cloud Services with exceptional support for Medium and Enterprise Clientele. | {{no}} | paid | Yes or subdomain | | 24/7 | |- | [https://www.arvixe.com/mediawiki_hosting Arvixe Hosting] | USA, Europe | host | | {{no}} | paid | | | 24/7 | 1-click setup |- | [https://biowikifarm.net/meta/Biowikifarm Biowikifarm] | Germany | farm | for non-commercial dissemination of biological open-content data | {{yes}} | free | | | | |- | [https://civihosting.com/mediawiki-hosting/ CiviHosting] | USA, Europe | host | Boutique-style hosting firm including account sizes for personal, business and enterprise-level wikis, including [[Extension:Semantic MediaWiki|Semantic MediaWiki]] and [[BlueSpice]] | {{no}} | paid | Yes, as well as domain registration service, or a subdomain is possible | SSH access | 24/7 support with 5 minute response time included with all accounts | [https://civihosting.com/shared-hosting/ Shared] and [https://civihosting.com/vps-hosting/ VPS hosting] available. Services include * Free installation and migration * Daily backups * 24/7 support with 5 minute response time * [https://civihosting.com/semantic-mediawiki-hosting/ Semantic MediaWiki] hosting * BlueSpice hosting * Turnkey solution for MediaWiki hosting |- | [https://www.cloudways.com/en/managed-mediawiki-cloud-hosting.php Cloudways.com] | Malta | host | | {{no}} | paid | You have to set it up independently | {{yes}} | | Quick setup, automatic backup, cloud-based (included in the cost). Support staff also in Dubai, Pakistan and Spain. |- | [https://help.dreamhost.com/hc/en-us/articles/217292577-MediaWiki-overview Dreamhost.com] | USA | host | | {{no}} | paid | | limited ssh access | 24/7 via tickets and email. | Also offers [https://help.dreamhost.com/hc/en-us/articles/215769478-Non-profit-discount free hosting service for non-profits.] |- |[https://community.fandom.com/wiki/Choosing_Fandom Fandom] | United States, France, Poland, Indonesia, Australia | farm | Entertainment, Lifestyle, Video Games and Anime | {{yes}} | free (with ads) | custom [[w:subdomain|subdomain]] only. | {{no}} | [https://fandom.zendesk.com/ Contact] and community forums | [https://www.fandom.com/community-creation-policy Wikis are not owned by their founders]. Fandom may take decisions affecting the community even if there's no consensus at all. They reserve the [https://community.fandom.com/wiki/Thread:1572365 right to change the wikis URL for SEO purposes]. In case the community wants to move to another host, the wiki and its content in most cases can't or won't be deleted from Fandom. There's only one skin available and it's proprietary. New Wikis Run MediaWiki 1.37.2 whilst older Wikis run MediaWiki 1.33. |- | [https://fastdot.com/hosting/cpanel-cloud-hosting/mediawiki-hosting/ Fastdot Hosting] | Australia, Asia Pacific, USA, UK | host | | {{no}} | paid | | | | 1-click installer |- | [https://hostdash.com/mediawiki-hosting/ HostDash] | USA | host | Blazing fast wiki hosting solutions, backed by 24/7 expert support & a 60 day money back guarantee. | {{no}} | paid | {{yes}} | | 24/7 | * 1-Click Setup * FREE Domain Name * 24/7 Expert Support * Proactive Malware Protection * cPanel Control Panel * 60 Day Money Back Guarantee |- | [https://www.hostgator.com/apps/wiki-hosting HostGator] | USA | host | | {{no}} | paid | {{yes}} | | | |- |[https://hostiso.com/mediawiki-hosting Hostiso] |USA, Canada, Germany, France, Singapore |host |Managed Hosting and Services with exceptional support for mediwiki clients! | {{no}} |paid |yes or subdomain | |24/7 |1-click setup, free backups, support, cPanel, cloud-based. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.hostknox.com/mediawiki-hosting HostKnox] | USA | host | | {{no}} | paid | {{yes}} | Chrooted (jailed) SSH | 24/7 via support tickets. 15-minute response time. | Free MediaWiki installation, transfer & upgrade. |- |[https://www.knownhost.com/media-wiki-hosting.html KnownHost] |USA, Europe |host | | {{no}} |paid | |SSH Access |24/7/365 Email and Ticket Support. |Free install support. Shared, VPS, Cloud and Dedicated Server lines. |- | [https://www.milesweb.com/mediawiki-hosting.php MilesWeb.com] | UK, US, India, Romania | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://miraheze.org Miraheze] | UK | farm | | {{yes}} | free (no ads) | {{optional}} | {{no}} | IRC, Email, Issue trackers, Wiki venues, Discord server | Community-driven, not-for-profit, quick wiki creation, HTTPS-only, public and private wikis. Infrastructure 100% [https://github.com/miraheze open source]. No hard limits on server resource usage and runs latest MediaWiki version. |- | [https://www.mywikis.com/ MyWikis] | USA We speak English / Nosotros hablamos español / On parle français / 我们讲中文 / हमें हिंदी आती है | host | Private wikis (public wikis are still available)<br />Different plans available, tailored for enterprise customers, personal wikis, and anywhere in between. | {{no}} | paid (no ads) | {{yes}} | FTP and SSH on request | Support system, email, phone, Zoom, Microsoft Teams, and Google Meet | * Wikis created automatically in under 5 minutes with 40+ extensions preinstalled. Hundreds of extensions available to install. * Self Service portal, where you can manage your wiki, add extensions to your wiki, reset passwords, and more. * Free migrations for most wikis; extensive experience in migrating from MediaWiki and other platforms. * 24/7 professional (not volunteer) personalized support from MediaWiki experts with 10+ years of experience; support response times guaranteed through SLAs. * 9 different privacy levels. Anti-spam built into every wiki. Wikis backed up daily. * Use a subdomain, buy a domain through MyWikis, or bring your own domain. |- | [https://neowiki.neoseeker.com/wiki/Alternative_To_Wikia Neoseeker] | | farm | game and entertainment-related wikis | {{yes}} | free | | | | |- |[https://OpenFox.io OpenFox.io] |Europe |Cloud based |Orgnaisational Wikis | {{no}} |Monthly and Annual |Company domain or Openfox.io subdomain. | {{no}} |Wiki set-up, consulting and implementation |Managed wiki Service with high security as well as set-up and organisational implementation support |- | [https://professional.wiki Professional.Wiki] | Europe | dedicated server | Professional services for companies of all sizes. Unmatched [[Semantic MediaWiki]] expertise. | {{no}} | paid | {{yes}} | {{yes}} | yes, with real experts | [https://professional.wiki/en/hosting Holistic services] including setup, management, support, training and custom development. Run by [https://professional.wiki/en/about MediaWiki veterans]. |- class="sortbottom" {{:Hosting services/Header}} |- | [https://www.rosehosting.com/mediawiki-vps-hosting.html RoseHosting] | USA | host | | {{no}} | paid | | | | Linux VPS hosting. |- | [https://www.saasweb.net/auto/managed-hosting/mediawiki SaaS Web Internet Solutions] | Germany | host | Standard, BlueSpice Free/Pro, Semantic MediaWiki | {{no}} | paid | always | {{no}} | Phone at business hours, email 24x7 | Fully managed MediaWiki on several infrastructures (as needed): Shared Hosting, Dedicated - both either on OpenStack Public Cloud or VMware Private Cloud |- | [https://www.shoutwiki.com/ ShoutWiki] | | farm | | {{yes}} | free; ad-supported; paid | [https://www.shoutwiki.com/wiki/Set_up_custom_domain possible] | {{no}} | [https://www.shoutwiki.com/wiki/Special:Contact Contact] and [https://www.shoutwiki.com/wiki/Forum:Index Forum] at ShoutWiki Hub | From MediaWiki developers and others. Lacks HTTPS/SSL support. |- | [https://www.siteground.com/mediawiki-hosting.htm SiteGround] | USA, Netherlands, Singapore | host | | {{no}} | paid | {{yes}} | | 24/7/365 support via live chat, email and phone | 1-click setup |- | [https://wiki.gg/ wiki.gg] | USA | farm | | {{Yes}} | Free | {{No}} | | Email | Private wiki-farm, wikis are only created on request by staff, and they prefer wikis with developer/publisher support to either provide assets or information for the wiki or for the wiki to become Official. |- | [https://webarch.coop/mediawiki Webarchitects] | UK | farm | | {{no}} | paid | {{yes}} | Optional SSH access | IRC, email, phone | Multi-stakeholder cooperative with social responsibility focus, green power and green hardware, emphasis on free and open source software ([https://git.coop/webarch/mediawiki Ansible playbook published under GPLv3]). |- | [https://www.webhostuk.co.uk/wiki-hosting.html Webhost UK LTD] | UK, US | host | | {{no}} | paid | {{yes}} | FTP & Jail Shell access | 24/7/365 support via live chat, email and phone | 1-click setup |- class="sortbottom" {{:Hosting services/Header}} |- | [https://wiki-valley.com Wiki Valley] (fr) [https://en.wiki-valley.com/Create_your_own_private_wiki_online_and_manage_knowledge Wiki Valley](en) | France | farm | Private wikis | {{no}} | [https://wiki-valley.com/wiki/Tarifs_de_l_hebergement_des_wikis by user/month and options] | {{yes}} | {{no}} | mail, chat, phone and wiki | [https://wiki-valley.com/wiki/Sp%C3%A9cial:Contact Création à la demande] (fr) [https://en.wiki-valley.com/Special:Contact Creation on demand] (en)<br/> |- | [https://www.wikibase.nl/Diensten/Managed_hosting Wikibase Solutions] | The Netherlands | host | Fully managed Wiki hosting in addition to a core business of developing Semantic MediaWiki solutions | {{no}} | paid | {{yes}} | at request | phone, Skype and email | Also provides support for Elasticsearch and other requested services. |- | [https://www.wikihoster.net/ WikiHoster.net] | Germany | farm | Semantic MediaWiki, updates and upgrades included in plans (serviced) | {{no}} | paid | possible | serviced (see specialism) | Phone and email at business hours | German site. Available for customers in the [[wikipedia:Single Euro Payments Area|SEPA-area]]. |- | [http://www.wiki-site.com/ Wiki-Site] | United States, Israel | farm | | {{yes}} | free (with ads) | | | | Available in 25 languages. Runs [[MediaWiki 1.11]]. Lacks HTTPS/SSL support. |- | [https://www.wikiteq.com/ WikiTeq] | USA | host | Professionally managed hosting on a private VPS | {{no}} | paid | {{yes}} | {{yes}} | On-call support team ready 24/7 | Enterprised-focused full-service MediaWiki development company providing fully supported and maintained wikis. |- | [https://meta.rdpstudio.top FutureWiki] | China | farm | | {{no}} | one time paid at creation, sometimes free by event | {{no}} | {{no}} | Email, wiki page | Quick wiki creation, HTTPS-only. Only for Chinese users. Currently in matainance. |} <div lang="en" dir="ltr" class="mw-content-ltr"> == External links == </div> * [[wikiapiary:Host:Hosts|Hosts]] listados em [[WikiApiary]]. * <span lang="en" dir="ltr" class="mw-content-ltr">[[wikiapiary:Farm:Farms|Farms]] listed at WikiApiary.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikibooks:Starting and Running a Wiki Website/Hosted Wikis]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[w:Comparison of wiki hosting services|Comparison of wiki hosting services]]</span> * [https://www.wikimatrix.org WikiMatrix] * <span lang="en" dir="ltr" class="mw-content-ltr">[https://curlie.org/Computers/Software/Groupware/Wiki/Wiki_Farms Wiki farms] at [[w:DMOZ|DMOZ]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://wikiindex.org/Category:WikiFarm Category:WikiFarm] at WikiIndex.</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[https://github.com/WikiTeam/wikiteam/wiki/WikiFarms WikiFarms - wikiteam - tools for archiving wikis]. On [[w:GitHub|GitHub]].</span> [[Category:MediaWiki References{{#translation:}}]] kgqg2037gqcjo1ypkztsd754v2zxubc Translations:Hosting services/5/pt 1198 1607144 5386397 2022-07-28T13:46:34Z 201.47.225.82 Created page with "Não agregue serviços de alojamento a esta lista sem um enlace directo a uma página que indique "explicitamente" o alojamento de MediaWiki." wikitext text/x-wiki Não agregue serviços de alojamento a esta lista sem um enlace directo a uma página que indique "explicitamente" o alojamento de MediaWiki. stl4o2sm73gklzmplp0ljhx7t05hprn Translations:Hosting services/51/pt 1198 1607145 5386399 2022-07-28T13:46:49Z 201.47.225.82 Created page with "[[$1|Hosts]] listados em [[WikiApiary]]." wikitext text/x-wiki [[$1|Hosts]] listados em [[WikiApiary]]. g5aechi1butvsbph3p6x4ysr5jlk06n Translations:Hosting services/2/pt 1198 1607146 5386401 2022-07-28T13:47:19Z 201.47.225.82 Created page with "Se você deseja executar um wiki MediaWiki e não deseja manter sua própria infraestrutura, pode estar interessado nos ''[[$1|wiki farms]]'' e nos serviços de hospedagem listados abaixo." wikitext text/x-wiki Se você deseja executar um wiki MediaWiki e não deseja manter sua própria infraestrutura, pode estar interessado nos ''[[$1|wiki farms]]'' e nos serviços de hospedagem listados abaixo. 8cmrzv8efmx1tov0ftlqb6beokk4zo0 Translations:Help:Templates/194/cs 1198 1607148 5386412 2022-07-28T13:51:34Z ENeRZet 17359278 Created page with "K určení alternativních názvů parametrů se často používají výchozí hodnoty." wikitext text/x-wiki K určení alternativních názvů parametrů se často používají výchozí hodnoty. laq4mctgw1q4td72mshlmfitxina0vn Translations:Help:Templates/195/cs 1198 1607149 5386414 2022-07-28T13:52:00Z ENeRZet 17359278 Created page with "Pokud máte například $1, šablona nejprve vyhledá parametr s názvem "$2"." wikitext text/x-wiki Pokud máte například $1, šablona nejprve vyhledá parametr s názvem "$2". 64vwr3ysbztrj7tgcza0q5yohakc78r Translations:Help:Templates/196/cs 1198 1607150 5386416 2022-07-28T13:52:25Z ENeRZet 17359278 Created page with "Pokud není nastaven, použije parametr s názvem "$1"." wikitext text/x-wiki Pokud není nastaven, použije parametr s názvem "$1". 74slsij15q7y9vo4sjqozd9qax27m6f Translations:Help:Templates/197/cs 1198 1607151 5386418 2022-07-28T13:53:00Z ENeRZet 17359278 Created page with "Pokud není nastaveno ani "$1" ani "$2", nevypíše se nic." wikitext text/x-wiki Pokud není nastaveno ani "$1" ani "$2", nevypíše se nic. mv12e3s1ejalemkzi2cfv6r77phw7up Translations:Help:Templates/198/cs 1198 1607152 5386420 2022-07-28T13:54:01Z ENeRZet 17359278 Created page with "=== Hodnocení ===" wikitext text/x-wiki === Hodnocení === ql2hztios546bmyehxubrqbntc03pum Translations:Help:Templates/199/cs 1198 1607153 5386422 2022-07-28T13:54:33Z ENeRZet 17359278 Created page with "Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete." wikitext text/x-wiki Toto je pokročilé téma, které můžete přeskočit, pokud jej nepotřebujete. 21lk4ge08b7lgeqtdr1cr84twjx86ge Translations:Help:Templates/200/cs 1198 1607154 5386424 2022-07-28T13:56:51Z ENeRZet 17359278 Created page with "Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou." wikitext text/x-wiki Obecně řečeno, parametry šablony jsou nahrazeny do šablony po tokenizaci (dělání symbolů), ale tak, jak jsou. 4l13nns91tvjbv0f992jtspkwnkmjd6 Translations:Help:Templates/201/cs 1198 1607155 5386426 2022-07-28T13:57:13Z ENeRZet 17359278 Created page with "Nejsou hodnoceny, dokud nejsou použity." wikitext text/x-wiki Nejsou hodnoceny, dokud nejsou použity. 4376trcbbmz97h5gln6tvr27tisorcg Translations:Help:Templates/202/cs 1198 1607156 5386428 2022-07-28T13:57:34Z ENeRZet 17359278 Created page with "To má několik důsledků." wikitext text/x-wiki To má několik důsledků. 1r8p5iipkuky04pcbn4a529uvfnzzgs Translations:Help:Templates/203/cs 1198 1607157 5386430 2022-07-28T13:58:04Z ENeRZet 17359278 Created page with "K ovládání názvu parametru nebo šablony můžete stále používat šablony, ale nemůžete rozdělit volání šablony mezi více šablon." wikitext text/x-wiki K ovládání názvu parametru nebo šablony můžete stále používat šablony, ale nemůžete rozdělit volání šablony mezi více šablon. 2npsy9brk3kssofwga6sbupz7c3s26t Translations:Help:Templates/204/cs 1198 1607158 5386432 2022-07-28T13:58:43Z ENeRZet 17359278 Created page with "Druhým důsledkem je odstranění mrtvého kódu." wikitext text/x-wiki Druhým důsledkem je odstranění mrtvého kódu. 6hcwt92gp7rsl39b17z9qb24jip3x3o Translations:Help:Templates/205/cs 1198 1607159 5386434 2022-07-28T13:59:33Z ENeRZet 17359278 Created page with "Mnoho, ale ne všechny funkce analyzátoru, značky analyzátoru a transkludované speciální stránky nejsou přímo zahrnuty jako šablony, ale místo toho jsou nahrazeny "strip marker"." wikitext text/x-wiki Mnoho, ale ne všechny funkce analyzátoru, značky analyzátoru a transkludované speciální stránky nejsou přímo zahrnuty jako šablony, ale místo toho jsou nahrazeny "strip marker". 91d33d8f4caky2ym27ea3057hdhr4ml 5386439 5386434 2022-07-28T14:03:20Z ENeRZet 17359278 wikitext text/x-wiki Mnoho, ale ne všechny funkce analyzátoru, značky analyzátoru a transkludované speciální stránky nejsou přímo zahrnuty jako šablony, ale místo toho jsou nahrazeny "značkou stripu". am72vvz6i8c9ydkr5y26hxhdhqilipz Topic:X05ttspe4a2pk23s 2600 1607160 5386436 2022-07-28T14:02:04Z Flow talk page manager 1946968 /* Tato stránka byla převedena na Strukturovanou diskusi */ flow-board application/json {"flow-workflow":"x05ttspe4a2pk23s"} 8m7oo47ktiigp9kucx4mkh9u8wj2nd1 Translations:Help:Templates/206/cs 1198 1607161 5386437 2022-07-28T14:03:00Z ENeRZet 17359278 Created page with "To znamená, že nemůžete manipulovat s výsledky pomocí funkcí analyzátoru, jako je $1 nebo podobných funkcí z rozšíření, protože místo výsledku funkce analyzátoru vidí značku stripu." wikitext text/x-wiki To znamená, že nemůžete manipulovat s výsledky pomocí funkcí analyzátoru, jako je $1 nebo podobných funkcí z rozšíření, protože místo výsledku funkce analyzátoru vidí značku stripu. qv3bms5av41u5q1pvb6q7wwp6eiop9b Translations:Manual:$wgMaxCredits/10/ja 1198 1607162 5386441 2022-07-28T14:05:28Z AdamMillerchip 17433733 Created page with "ユーザーが最終編集時間順に表示される。" wikitext text/x-wiki ユーザーが最終編集時間順に表示される。 jb0purinxlmy7k970nbz56vdbe1wv6j Translations:Manual:$wgMaxCredits/11/ja 1198 1607163 5386443 2022-07-28T14:05:40Z AdamMillerchip 17433733 Created page with "例:" wikitext text/x-wiki 例: dk8girww5t432a7z3w3yeuyvc7kwsu1 Translations:Download/54/cs 1198 1607164 5386450 2022-07-28T14:11:11Z ENeRZet 17359278 Created page with "Repozitáře některých [[w:Linux distribution|Linuxových distribucí]] také stále častěji nabízejí balíčky pro MediaWiki s různým stupněm pokrytí frekvence a rozšíření (např. Debian, Ubuntu, Fedora, Gentoo)." wikitext text/x-wiki Repozitáře některých [[w:Linux distribution|Linuxových distribucí]] také stále častěji nabízejí balíčky pro MediaWiki s různým stupněm pokrytí frekvence a rozšíření (např. Debian, Ubuntu, Fedora, Gentoo). 5drtzsj11jgzhxl2sduliozi397omdm Translations:Download/55/cs 1198 1607165 5386452 2022-07-28T14:11:25Z ENeRZet 17359278 Created page with "== Poznámky pod čarou ==" wikitext text/x-wiki == Poznámky pod čarou == 3rjnnoi7ht9yru9mqosxox1plktxiwg MediaWiki Language Extension Bundle/2022.07 0 1607166 5386455 2022-07-28T14:16:12Z APatro (WMF) 17087531 Start the release notes wikitext text/x-wiki We would like to announce the release of MediaWiki Language Extension Bundle 2022.07. This bundle is compatible with '''MediaWiki >= 1.37.2''' and requires '''PHP 7.3.19''' or above. Next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: * sha256sum: * Signature: Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.org/ * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ Release notes for each extension are below. == Highlights == * '''MLEB now requires MediaWiki >= 1.37.2 and PHP 7.3.19''' rmsdhyi966rngqln0p3r2ypha9k6e9f 5386558 5386455 2022-07-28T15:04:08Z APatro (WMF) 17087531 Add complete release notes wikitext text/x-wiki We would like to announce the release of MediaWiki Language Extension Bundle 2022.07. This bundle is compatible with '''MediaWiki >= 1.37.2''' and requires '''PHP 7.3.19''' or above. Next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: * sha256sum: * Signature: Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.org/ * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ Release notes for each extension are below. == Highlights == * '''MLEB now requires MediaWiki >= 1.37.2 and PHP 7.3.19''' == Babel, cldr, CleanChanges and LocalisationUpdate == * Localisation and maintenance updates. == Translate == * Support for MW 1.36 has been dropped * Localisation and maintenance updates. * Display previous edit summaries when translating content. ({{phab|T240364}}, {{gerrit|780684}}, {{gerrit|779829}}) * Avoid recreation of translation pages on bulk deletion of pages ({{phab|T291724}}, {{gerrit|799383}}) * Allow CSV export for message groups ({{phab|T309517}}, {{gerrit|802130}}) * Add a script to import translations from a CSV file ({{phab|T309517}}, {{gerrit|803294}}) * Fix "Impossible to mark pages for translation using the mobile site". ({{phab|T311631}}, {{gerrit|809970}}) * Allow filtering the translation review log by subtypes of actions. ({{phab|T216335}}, {{gerrit|810311}}) * Make it easy to go to source page and the translation page on Special:Translate. ({{phab|T270025}}, {{gerrit|807480}}) == UniversalLanguageSelector == * Support for MW 1.36 has been dropped * Localisation and maintenance updates. * Load OOUI widgets only when ULS is opened ({{phab|T309793}}, {{gerrit|803086}}) === Font updates === * No updates i0rssgho2d6yb9i657byriaiqi2g0n1 5386566 5386558 2022-07-28T15:29:20Z Nikerabbit 24 small review wikitext text/x-wiki We would like to announce the release of MediaWiki Language Extension Bundle 2022.07. This bundle is compatible with '''MediaWiki >= 1.37.2''' and requires '''PHP 7.3.19''' or above. Next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: * sha256sum: * Signature: Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.org/ * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ Release notes for each extension are below. == Highlights == * '''MLEB now requires MediaWiki 1.37.2 or later''' == Babel, cldr, CleanChanges and LocalisationUpdate == * Localisation and maintenance updates. == Translate == * Support for MediaWiki 1.36 has been dropped. * Localisation and maintenance updates. * Display previous edit summaries when translating content. ({{phab|T240364}}, {{gerrit|780684}}, {{gerrit|779829}}) * Avoid recreation of translation pages on bulk deletion of pages, for example when using the Nuke extension. ({{phab|T291724}}, {{gerrit|799383}}) * Allow CSV export for message groups. ({{phab|T309517}}, {{gerrit|802130}}) * Add a script to import translations from a CSV file. ({{phab|T309517}}, {{gerrit|803294}}) * Fix "Impossible to mark pages for translation using the mobile site". ({{phab|T311631}}, {{gerrit|809970}}) * Allow filtering the translation review log by sub-action. ({{phab|T216335}}, {{gerrit|810311}}) * Make it easy to go to source page and the translation page on Special:Translate. ({{phab|T270025}}, {{gerrit|807480}}) == UniversalLanguageSelector == * Support for MediaWiki 1.36 has been dropped. * Localisation and maintenance updates. * Performance optimization: Load OOUI widgets only when ULS is opened ({{phab|T309793}}, {{gerrit|803086}}) 5j0lm8zi1z0xl1bgtmwrt4rhyirt5gf 5386567 5386566 2022-07-28T15:29:39Z Nikerabbit 24 /* UniversalLanguageSelector */ wikitext text/x-wiki We would like to announce the release of MediaWiki Language Extension Bundle 2022.07. This bundle is compatible with '''MediaWiki >= 1.37.2''' and requires '''PHP 7.3.19''' or above. Next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: * sha256sum: * Signature: Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.org/ * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ Release notes for each extension are below. == Highlights == * '''MLEB now requires MediaWiki 1.37.2 or later''' == Babel, cldr, CleanChanges and LocalisationUpdate == * Localisation and maintenance updates. == Translate == * Support for MediaWiki 1.36 has been dropped. * Localisation and maintenance updates. * Display previous edit summaries when translating content. ({{phab|T240364}}, {{gerrit|780684}}, {{gerrit|779829}}) * Avoid recreation of translation pages on bulk deletion of pages, for example when using the Nuke extension. ({{phab|T291724}}, {{gerrit|799383}}) * Allow CSV export for message groups. ({{phab|T309517}}, {{gerrit|802130}}) * Add a script to import translations from a CSV file. ({{phab|T309517}}, {{gerrit|803294}}) * Fix "Impossible to mark pages for translation using the mobile site". ({{phab|T311631}}, {{gerrit|809970}}) * Allow filtering the translation review log by sub-action. ({{phab|T216335}}, {{gerrit|810311}}) * Make it easy to go to source page and the translation page on Special:Translate. ({{phab|T270025}}, {{gerrit|807480}}) == UniversalLanguageSelector == * Support for MediaWiki 1.36 has been dropped. * Localisation and maintenance updates. * Performance optimization: Load OOUI widgets only when ULS is opened. ({{phab|T309793}}, {{gerrit|803086}}) ipup52sv793zbo3vagn9jczt0v6naw6 5387692 5386567 2022-07-29T05:14:18Z APatro (WMF) 17087531 Remove LocalisationUpdate extension wikitext text/x-wiki We would like to announce the release of MediaWiki Language Extension Bundle 2022.07. This bundle is compatible with '''MediaWiki >= 1.37.2''' and requires '''PHP 7.3.19''' or above. Next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: * sha256sum: * Signature: Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.org/ * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ Release notes for each extension are below. == Highlights == * '''MLEB now requires MediaWiki 1.37.2 or later''' == Babel, cldr, and CleanChanges == * Localisation and maintenance updates. == Translate == * Support for MediaWiki 1.36 has been dropped. * Localisation and maintenance updates. * Display previous edit summaries when translating content. ({{phab|T240364}}, {{gerrit|780684}}, {{gerrit|779829}}) * Avoid recreation of translation pages on bulk deletion of pages, for example when using the Nuke extension. ({{phab|T291724}}, {{gerrit|799383}}) * Allow CSV export for message groups. ({{phab|T309517}}, {{gerrit|802130}}) * Add a script to import translations from a CSV file. ({{phab|T309517}}, {{gerrit|803294}}) * Fix "Impossible to mark pages for translation using the mobile site". ({{phab|T311631}}, {{gerrit|809970}}) * Allow filtering the translation review log by sub-action. ({{phab|T216335}}, {{gerrit|810311}}) * Make it easy to go to source page and the translation page on Special:Translate. ({{phab|T270025}}, {{gerrit|807480}}) == UniversalLanguageSelector == * Support for MediaWiki 1.36 has been dropped. * Localisation and maintenance updates. * Performance optimization: Load OOUI widgets only when ULS is opened. ({{phab|T309793}}, {{gerrit|803086}}) 3creat5wc48ut5vnqmaotj3960ksjce 5387698 5387692 2022-07-29T05:53:41Z KartikMistry 550774 Update links etc. wikitext text/x-wiki ​We would like to announce the release of MediaWiki Language Extension Bundle 2022.07. This bundle is compatible with '''MediaWiki >= 1.37.2''' and requires '''PHP 7.3.19''' or above. The next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.07.tar.bz2 * sha256sum: 3e8f48643403946fdb55f3ff086ed1e702c0367f3282c9dc78eb6785964c0809 * Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.07.tar.bz2.asc Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.org/ * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ Release notes for each extension are below. == Highlights == * '''MLEB now requires MediaWiki 1.37.2 or later''' == Babel, cldr, and CleanChanges == * Localisation and maintenance updates. == Translate == * Support for MediaWiki 1.36 has been dropped. * Localisation and maintenance updates. * Display previous edit summaries when translating content. ({{phab|T240364}}, {{gerrit|780684}}, {{gerrit|779829}}) * Avoid recreation of translation pages on the bulk deletion of pages, for example when using the Nuke extension. ({{phab|T291724}}, {{gerrit|799383}}) * Allow CSV export for message groups. ({{phab|T309517}}, {{gerrit|802130}}) * Add a script to import translations from a CSV file. ({{phab|T309517}}, {{gerrit|803294}}) * Fix "Impossible to mark pages for translation using the mobile site". ({{phab|T311631}}, {{gerrit|809970}}) * Allow filtering the translation review log by sub-action. ({{phab|T216335}}, {{gerrit|810311}}) * Make it easy to go to the source page and the translation page on Special:Translate. ({{phab|T270025}}, {{gerrit|807480}}) == UniversalLanguageSelector == * Support for MediaWiki 1.36 has been dropped.​​ * Localisation and maintenance updates. * Performance optimization: Load OOUI widgets only when ULS is opened. ({{phab|T309793}}, {{gerrit|803086}}) kh9eouevaxnnqhkak5oin8ismj7qv5a Topic:X05uwagmp7e1vwq4 2600 1607167 5386458 2022-07-28T14:21:16Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x05uwagmp7e1vwq4"} 9euoaa8i9yj6vivja6jzrph03lroq4t Translations:Inuka team/35/gpe 1198 1607168 5386459 2022-07-28T14:24:29Z DaSupremo 1532535 Created page with "[[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top." wikitext text/x-wiki [[Wikipedia Preview|Wikipedia]] Preview dey allow make Wikipedia content be available as contextual information for 3rd party websites top. esnne5yu8vto8wuetvc95r2dom4li8r Translations:Manual:Installation guide/117/cs 1198 1607169 5386463 2022-07-28T14:25:07Z ENeRZet 17359278 Created page with "Pokud máte pochybnosti, přečtěte si $1." wikitext text/x-wiki Pokud máte pochybnosti, přečtěte si $1. b09lctx9icokburrr34m6532547krn8 Translations:Manual:Installation guide/115/cs 1198 1607170 5386469 2022-07-28T14:27:08Z ENeRZet 17359278 Created page with "Pokročilá konfigurace" wikitext text/x-wiki Pokročilá konfigurace mmr3ik0bonko8r2igb2k3fmk337q6h4 Translations:Manual:Installation guide/116/cs 1198 1607171 5386471 2022-07-28T14:27:26Z ENeRZet 17359278 Created page with "Správa wiki" wikitext text/x-wiki Správa wiki qth38bt44732udjowgdbd0av6yj15xj Translations:Manual:Configuring MediaWiki/10/cs 1198 1607172 5386475 2022-07-28T14:31:27Z ENeRZet 17359278 Created page with "Tím se provede základní konfigurace potřebná pro zprovoznění wiki. Úplné podrobnosti o spuštění skriptu najdete v $config." wikitext text/x-wiki Tím se provede základní konfigurace potřebná pro zprovoznění wiki. Úplné podrobnosti o spuštění skriptu najdete v $config. 9zalxxljq7mg68dd0lybggepw3r74n3 5386477 5386475 2022-07-28T14:31:56Z ENeRZet 17359278 wikitext text/x-wiki Tím se provede základní konfigurace potřebná pro zprovoznění wiki. Úplné podrobnosti o spuštění skriptu najdete na stránce $config. rj80rqii4atmnx0mpimfazrmble1wgd Translations:Inuka team/55/gpe 1198 1607173 5386488 2022-07-28T14:39:04Z DaSupremo 1532535 Created page with "Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top." wikitext text/x-wiki Wikipedia Preview for partner websites top go allow dema readers gain context while dem dey read dema pages den help people make dem gain contextual knowledge wey comot Wikipedia without necessarily make dem click thru go Wikipedia den mo more for Wikipedia top plus de option make e be available to read more for Wikipedia top. gna8hf9zltkf7ijeiqjtzezn2crto8l Translations:Inuka team/56/gpe 1198 1607174 5386490 2022-07-28T14:39:49Z DaSupremo 1532535 Created page with "E be similar to page previews nanso give external sites." wikitext text/x-wiki E be similar to page previews nanso give external sites. 9edhm33yd21l1wxfgyuq7lz86udhim9 Translations:Inuka team/57/gpe 1198 1607175 5386492 2022-07-28T14:40:53Z DaSupremo 1532535 Created page with "Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]]" wikitext text/x-wiki Dem fi integrate de code for de site inside or if de external site dey use Wordpress then dem fi use de Wordpress plugin.<nowiki>https://wordpress.org/plugins/wikipedia-preview/</nowiki> Read more; [[Wikipedia Preview|https://www.mediawiki.org/wiki/Wikipedia_Preview]] rnpiik7c3v47za3vhpe9rwa1w8dd925 Translations:Inuka team/36/gpe 1198 1607176 5386494 2022-07-28T14:41:59Z DaSupremo 1532535 Created page with "[[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world." wikitext text/x-wiki [[Wikipedia for KaiOS|Wikipedia for KAIOS]] Wikipedia reading app give smart feature phones. Dem release am for 2 versions inside - 1) give India 2) give rest of de world. rkbiu4p44inbp5woq7o2sg2fycitor3 Translations:Inuka team/58/gpe 1198 1607177 5386496 2022-07-28T14:42:07Z DaSupremo 1532535 Created page with "[[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]." wikitext text/x-wiki [[:File:Introducing Wikipedia for KaiOS.webm|Short video of the app]]. ppfrblzmn6dm88mylac2phvqnortm6z Translations:Inuka team/37/gpe 1198 1607178 5386504 2022-07-28T14:44:46Z DaSupremo 1532535 Created page with "[[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community" wikitext text/x-wiki [[metawiki:Research:Wikistories_Indonesia_Concept_Testing|Wikistories Qualitative user research with clickable Wikistories]] prototypes for Indonesia inside plus contributors wey dey exist gather feedback from Indonesia editor communities for early concepts top den designs give Wikistories, wey dey focus for de experiences for potential Wikistories creators top wey dey comot from de editing community l2d3hbo745rp7p2ie1naz4qgebvj9oh Translations:Inuka team/38/gpe 1198 1607179 5386507 2022-07-28T14:47:07Z DaSupremo 1532535 Created page with "[[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia." wikitext text/x-wiki [[metawiki:Research:Wikistories_Africa_Research_(Nigeria,_Kenya,_South_Africa)|Qualitative user research with clickable Wikistories prototypes]] for Kenya, Nigeria den South Africa inside plus fresh/potential contributors investigate de behavior for content creators den consumers for three African countries inside plus distinct user behaviors den context especially wey dey relate to Wikimedia. su6aliz1y0n3ffxii87sl9mdvwt5ahh Translations:Manual:Installation requirements/106/cs 1198 1607180 5386509 2022-07-28T14:47:41Z ENeRZet 17359278 Created page with "Ke spuštění [[$1|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku." wikitext text/x-wiki Ke spuštění [[$1|údržbových skriptů MediaWiki]] budete potřebovat přístup z příkazového řádku. p8jjei67cth9wvsfzz6rrtc4p2010l2 Translations:Inuka team/39/gpe 1198 1607181 5386512 2022-07-28T14:49:18Z DaSupremo 1532535 Created page with "[[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones." wikitext text/x-wiki [[:File:Understanding KaiOS users in India - Report.pdf|Qualitative research in India]] so say dem go understand why den how dis users dey use dis phones. nxd4anscwu41n0733t17y3ywrwrvqj0 Translations:Inuka team/59/gpe 1198 1607182 5386517 2022-07-28T14:50:28Z DaSupremo 1532535 Created page with "We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do." wikitext text/x-wiki We mo say users choose say dem go purchase dis phones sake of dem be affordable den allow access to apps like smartphones dey do. ei5mt4rp0oi35zlnzwer3za8kpwyd20 Translations:Inuka team/60/gpe 1198 1607183 5386519 2022-07-28T14:51:40Z DaSupremo 1532535 Created page with "We sanso mo de challenge dem dey face" wikitext text/x-wiki We sanso mo de challenge dem dey face dt5eciqmvxwjafhakiaazqxpv61g4zu 5386525 5386519 2022-07-28T14:52:29Z DaSupremo 1532535 wikitext text/x-wiki We sanso mo de challenge dem dey face as dem dey try say dem go read Wikipedia for de native mobile browser inside. hkisll81po3kvf9eri9em49rgxzgw2k Translations:Manual:Installation requirements/104/cs 1198 1607184 5386523 2022-07-28T14:52:22Z ENeRZet 17359278 Created page with "MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP." wikitext text/x-wiki MediaWiki je široce kompatibilní se všemi hlavními webovými servery, které mohou vyvolat kompatibilní verzi PHP. 6tl0ispqhafwnuk5qjvumn2rigs1uwo Translations:Manual:Installation requirements/105/cs 1198 1607185 5386529 2022-07-28T14:53:29Z ENeRZet 17359278 Created page with "$1 ([příklad konfigurace $url]) je také dobrá volba." wikitext text/x-wiki $1 ([příklad konfigurace $url]) je také dobrá volba. eettiquzemyxmm7o6l6fenuwnjfa75z Translations:Manual:Installation requirements/99/cs 1198 1607186 5386531 2022-07-28T14:54:16Z ENeRZet 17359278 Created page with "(požadováno od verze 1.33)" wikitext text/x-wiki (požadováno od verze 1.33) fgyat9mavyuclh9nqvuyhftlob3d716 Translations:Inuka team/61/gpe 1198 1607187 5386533 2022-07-28T14:54:49Z DaSupremo 1532535 Created page with "Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside" wikitext text/x-wiki Challenges wey dem include be ability to scroll thru content, text size for de screen top, dem dey search give content den lack of awareness wey Wikipedia content be available for multiple languages inside imo3lqdondeujbbsr6xotgbbp7zcq6c Translations:Inuka team/40/gpe 1198 1607188 5386535 2022-07-28T14:55:03Z DaSupremo 1532535 Created page with "== Follow wanna work ==" wikitext text/x-wiki == Follow wanna work == g9kiy7m6j1lbhjkz3wiem40nghip86h Translations:Inuka team/41/gpe 1198 1607189 5386537 2022-07-28T14:55:25Z DaSupremo 1532535 Created page with "Monthly/Quarterly status updates for project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]] top" wikitext text/x-wiki Monthly/Quarterly status updates for project pages [[Wikistories]], [[Wikipedia Preview]] , [[Wikipedia for KaiOS|Wikipedia for KAIOS]] top hsuofx95lo4ejkhndykhg6rqni67vfj Translations:Inuka team/62/gpe 1198 1607190 5386541 2022-07-28T14:55:39Z DaSupremo 1532535 Created page with "What we dey do currently" wikitext text/x-wiki What we dey do currently r1psl3vhad5b6l5v0x3e582ggjrzoa8 Translations:Inuka team/42/gpe 1198 1607191 5386543 2022-07-28T14:55:59Z DaSupremo 1532535 Created page with "== Make you Get Involved ==" wikitext text/x-wiki == Make you Get Involved == 4dmwpfcboc1pgc88e9ucmx9nm9yhzva Translations:Inuka team/43/gpe 1198 1607192 5386545 2022-07-28T14:56:09Z DaSupremo 1532535 Created page with "== Contact us ==" wikitext text/x-wiki == Contact us == q3p227i4w4oxu7mbv0c2f7m4t0aefbg Translations:Inuka team/2/gpe 1198 1607193 5386549 2022-07-28T14:56:51Z DaSupremo 1532535 Created page with "== Introduction ==" wikitext text/x-wiki == Introduction == ra7zlxlb04d1bim5jvsevzinozkrnby Translations:Manual:Installation requirements/107/cs 1198 1607194 5386553 2022-07-28T14:59:26Z ENeRZet 17359278 Created page with "{{$1|Odesílání emailových upozornění}} přes samotný server vyžaduje [[w:Message transfer agent|agenta přenosu zpráv (MTA)]]." wikitext text/x-wiki {{$1|Odesílání emailových upozornění}} přes samotný server vyžaduje [[w:Message transfer agent|agenta přenosu zpráv (MTA)]]. b1avypm1ppiuaxf3hg7yyr2pgkpsrck Translations:Manual:Installation requirements/100/cs 1198 1607195 5386555 2022-07-28T15:00:16Z ENeRZet 17359278 Created page with "* '''{{$1|memcached}}''' lze použít pro ukládání objektů do mezipaměti." wikitext text/x-wiki * '''{{$1|memcached}}''' lze použít pro ukládání objektů do mezipaměti. nawoh4uczkmddi5nioowpvclbesbgxg Topic:X05x8ntlatejdruv 2600 1607196 5386557 2022-07-28T15:03:22Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x05x8ntlatejdruv"} gcrby4tzu4o6e4mj04nbuqh9nnnltu5 Talk:Greenhouse experiment 1 1607197 5386560 2022-07-28T15:06:56Z Matma Rex 36186 Matma Rex created the page [[Talk:Greenhouse experiment]] using a non-default content model "wikitext": per request wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 User talk:Viniciusftranslations 3 1607198 5386561 2022-07-28T15:13:18Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x05xslymotsxzi3h"} otsh48af6371n0u0dplo81kb9o0fasw Topic:X05xslymovrz3k2l 2600 1607199 5386562 2022-07-28T15:13:18Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x05xslymovrz3k2l"} 489d283nf5oay5qoxdw5x19c8mrmgew Topic:X05xvvuia73atjic 2600 1607200 5386563 2022-07-28T15:14:56Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x05xvvuia73atjic"} e6qu0qvbm6wdkmcswcaic3gbdg7zfnr Topic:X05y319rm0tfihu3 2600 1607201 5386564 2022-07-28T15:18:30Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x05y319rm0tfihu3"} dasg8ck07frpgoilkhkhg6d29b3i8v3 Topic:X05z0ilawkmlltgr 2600 1607202 5386569 2022-07-28T15:35:13Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x05z0ilawkmlltgr"} re4e6uc3b0akks23hsqqjhgmcadrwjo Translations:Structured Data Across Wikimedia/Newsletter/6/15/pt-br 1198 1607203 5386570 2022-07-28T15:39:01Z Eliazhar 17652978 Created page with "Esperamos ler e ver você em breve!" wikitext text/x-wiki Esperamos ler e ver você em breve! nnu8p4qik3v97l2r4i1vt6o7fvass3k Structured Data Across Wikimedia/Newsletter/6/pt-br 0 1607204 5386571 2022-07-28T15:39:02Z Eliazhar 17652978 Created page with "Esperamos ler e ver você em breve!" wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Deployment of Image suggestions</span> <span lang="en" dir="ltr" class="mw-content-ltr">On July 20, a first iteration of the [[:mw:Structured Data Across Wikimedia/Image Suggestions|Image suggestions tool]] was successfully deployed on Portuguese, Russian and Indonesian Wikipedia. The three Wikipedias have been identified in the last months as the first tester communities for this project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The goal of the tool is to embed a number of image suggestions in the user’s existing Wikipedia activities through weekly notifications, thus increasing the likelihood they will review such suggestions and add selected images as part of their current editing workflow. Currently, editors with 500+ edits on the identified projects add an average of 8 to 11 medias. We expect these rates to improve, thanks to our tool.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are currently collecting the first feedback from involved users, which will be used to identify potential bugs and improve the current experience. If you are interested in making your community involved in the following iterations of the tool, please let us know.</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">About the newsletter</span> <span lang="en" dir="ltr" class="mw-content-ltr">This newsletter will be released only when there are things to discuss or to be announced, and we plan on doing it in the least invasive way for your talk (i.e. through your notifications). If you want it delivered to your talk, let us know.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Let us also know your thoughts on the [[:mw:Talk:Structured Data Across Wikimedia|project's talk page]]. If you have direct inquiries, you can also refer to my [[mw:User talk:Sannita (WMF)|talk page]].</span> Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> slrltuthwu2tarf9ckkkre5qgwph5mc 5386573 5386571 2022-07-28T15:45:30Z Eliazhar 17652978 Created page with "Informe-nos também sobre suas ideias na [[$talk|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[$talksannita|página de discussão]]." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Deployment of Image suggestions</span> <span lang="en" dir="ltr" class="mw-content-ltr">On July 20, a first iteration of the [[:mw:Structured Data Across Wikimedia/Image Suggestions|Image suggestions tool]] was successfully deployed on Portuguese, Russian and Indonesian Wikipedia. The three Wikipedias have been identified in the last months as the first tester communities for this project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The goal of the tool is to embed a number of image suggestions in the user’s existing Wikipedia activities through weekly notifications, thus increasing the likelihood they will review such suggestions and add selected images as part of their current editing workflow. Currently, editors with 500+ edits on the identified projects add an average of 8 to 11 medias. We expect these rates to improve, thanks to our tool.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are currently collecting the first feedback from involved users, which will be used to identify potential bugs and improve the current experience. If you are interested in making your community involved in the following iterations of the tool, please let us know.</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">About the newsletter</span> <span lang="en" dir="ltr" class="mw-content-ltr">This newsletter will be released only when there are things to discuss or to be announced, and we plan on doing it in the least invasive way for your talk (i.e. through your notifications). If you want it delivered to your talk, let us know.</span> Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de discussão]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 2gre8dio7d1ap9z94oyhjlagq8evm0z 5386575 5386573 2022-07-28T15:46:42Z Eliazhar 17652978 wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Deployment of Image suggestions</span> <span lang="en" dir="ltr" class="mw-content-ltr">On July 20, a first iteration of the [[:mw:Structured Data Across Wikimedia/Image Suggestions|Image suggestions tool]] was successfully deployed on Portuguese, Russian and Indonesian Wikipedia. The three Wikipedias have been identified in the last months as the first tester communities for this project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The goal of the tool is to embed a number of image suggestions in the user’s existing Wikipedia activities through weekly notifications, thus increasing the likelihood they will review such suggestions and add selected images as part of their current editing workflow. Currently, editors with 500+ edits on the identified projects add an average of 8 to 11 medias. We expect these rates to improve, thanks to our tool.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are currently collecting the first feedback from involved users, which will be used to identify potential bugs and improve the current experience. If you are interested in making your community involved in the following iterations of the tool, please let us know.</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">About the newsletter</span> <span lang="en" dir="ltr" class="mw-content-ltr">This newsletter will be released only when there are things to discuss or to be announced, and we plan on doing it in the least invasive way for your talk (i.e. through your notifications). If you want it delivered to your talk, let us know.</span> Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 69sgpmdv8pfoujn77arcnoxend9npzz 5386577 5386575 2022-07-28T15:48:29Z Eliazhar 17652978 Created page with "Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Deployment of Image suggestions</span> <span lang="en" dir="ltr" class="mw-content-ltr">On July 20, a first iteration of the [[:mw:Structured Data Across Wikimedia/Image Suggestions|Image suggestions tool]] was successfully deployed on Portuguese, Russian and Indonesian Wikipedia. The three Wikipedias have been identified in the last months as the first tester communities for this project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The goal of the tool is to embed a number of image suggestions in the user’s existing Wikipedia activities through weekly notifications, thus increasing the likelihood they will review such suggestions and add selected images as part of their current editing workflow. Currently, editors with 500+ edits on the identified projects add an average of 8 to 11 medias. We expect these rates to improve, thanks to our tool.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are currently collecting the first feedback from involved users, which will be used to identify potential bugs and improve the current experience. If you are interested in making your community involved in the following iterations of the tool, please let us know.</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">About the newsletter</span> Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 9c9vsk5qk0g1fsrs9gn7xnp0ugeqr70 5386579 5386577 2022-07-28T15:49:09Z Eliazhar 17652978 Created page with "Sobre o boletim" wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Deployment of Image suggestions</span> <span lang="en" dir="ltr" class="mw-content-ltr">On July 20, a first iteration of the [[:mw:Structured Data Across Wikimedia/Image Suggestions|Image suggestions tool]] was successfully deployed on Portuguese, Russian and Indonesian Wikipedia. The three Wikipedias have been identified in the last months as the first tester communities for this project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The goal of the tool is to embed a number of image suggestions in the user’s existing Wikipedia activities through weekly notifications, thus increasing the likelihood they will review such suggestions and add selected images as part of their current editing workflow. Currently, editors with 500+ edits on the identified projects add an average of 8 to 11 medias. We expect these rates to improve, thanks to our tool.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We are currently collecting the first feedback from involved users, which will be used to identify potential bugs and improve the current experience. If you are interested in making your community involved in the following iterations of the tool, please let us know.</span> ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> ou9yit550slq46mlmptx4tyzjs9if20 5386585 5386579 2022-07-28T15:51:05Z Eliazhar 17652978 Created page with "Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Deployment of Image suggestions</span> <span lang="en" dir="ltr" class="mw-content-ltr">On July 20, a first iteration of the [[:mw:Structured Data Across Wikimedia/Image Suggestions|Image suggestions tool]] was successfully deployed on Portuguese, Russian and Indonesian Wikipedia. The three Wikipedias have been identified in the last months as the first tester communities for this project.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The goal of the tool is to embed a number of image suggestions in the user’s existing Wikipedia activities through weekly notifications, thus increasing the likelihood they will review such suggestions and add selected images as part of their current editing workflow. Currently, editors with 500+ edits on the identified projects add an average of 8 to 11 medias. We expect these rates to improve, thanks to our tool.</span> Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> rbg49jne99i6gvnr2sqixnmxz3bmt7m 5386590 5386585 2022-07-28T16:03:29Z Eliazhar 17652978 Created page with "O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, g..." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Deployment of Image suggestions</span> <span lang="en" dir="ltr" class="mw-content-ltr">On July 20, a first iteration of the [[:mw:Structured Data Across Wikimedia/Image Suggestions|Image suggestions tool]] was successfully deployed on Portuguese, Russian and Indonesian Wikipedia. The three Wikipedias have been identified in the last months as the first tester communities for this project.</span> O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> qqk7ytmem40d7yxweu2e49prjq17ikm 5386592 5386590 2022-07-28T16:05:06Z Eliazhar 17652978 Created page with "Em 20 de julho, uma primeira iteração da ferramenta [[$imgsugg|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Deployment of Image suggestions</span> Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> l4xg73w2ex0498ffrll2ba2587zs5xk 5386594 5386592 2022-07-28T16:05:49Z Eliazhar 17652978 Created page with "Implantação de sugestões de Imagem" wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">We will now concentrate on collecting feedback on [[:File:SDAW Search improv 05 quick view.png|Search Result Preview]]. Our main focus will be initially with Portuguese, Russian and Indonesian Wikipedia communities, as well as Mediawiki.org. You can always share your feedback on the [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Search improvements talk page]].</span> ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> jov7bgzalhpqsf7e5zapkeklnuosgq0 5386596 5386594 2022-07-28T16:12:34Z Eliazhar 17652978 Created page with "Agora nos concentremos em coletar feedback sobre a [[$improv5|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[$searchimprovtalk|Página de discussão sobre aprimoramentos de pesquisa]]." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">All other improvements received a general positive feedback in the consultation, and we have started implementing them in the last days. We thank all users who took the time to participate and share their opinions, who have been taken into consideration.</span> Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 1w9o1wp8yr6pawapf03hqxzucldm2ak 5386599 5386596 2022-07-28T16:13:37Z Eliazhar 17652978 Created page with "Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> <span lang="en" dir="ltr" class="mw-content-ltr">The consultation took place on 12 different Wikipedias and on Mediawiki.org, with a substantial participation from users. Based on the precious feedback collected, we decided to re-evaluate our [[:File:SDAW Search improv 02 Namespace tag.png|proposal on namespace tags]], and to tweak slightly [[:File:SDAW Search improv 01 thumbnail.png|article thumbnails]] in order to make it easier for users to hide them, if needed. We also decided not to proceed with [[:File:SDAW Search improv 04a Advanced search collapsed.png|collapsing the advanced search options]].</span> Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> t3ce34fuphodsl12oewj6wu3mm8pacg 5386602 5386599 2022-07-28T16:21:57Z Eliazhar 17652978 Created page with "A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[$improv2|proposta sobre tags de namespace]], e ajustar ligeiramente as [[$improv1|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[$improv4|remoção das opções de busca avançadas]]." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Most of the proposed changes were graphical improvements, aimed at providing better context and better layout for casual readers who want to use the Wikipedia search page, as well as promote awareness for Wikipedia’s sister projects by rearranging the “sister projects” search section.</span> A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> akvanpcahn49zyijt8tzlfmtucnv13o 5386604 5386602 2022-07-28T16:23:57Z Eliazhar 17652978 Created page with "A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos"." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> <span lang="en" dir="ltr" class="mw-content-ltr">From June 21 to July 10, we held a general consultation about a number of improvements to [[Special:Search|Special:Search]], as part of the general initiative about [[:mw:Structured Data Across Wikimedia/Search Improvements|Search Improvements]].</span> A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> tbsm62g8lypkdtfy79duuzgv5itvphn 5386607 5386604 2022-07-28T16:26:02Z Eliazhar 17652978 Created page with "De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[$search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[$searchimprov|Aprimoramentos de Pesquisa]]." wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;<span lang="en" dir="ltr" class="mw-content-ltr">Consultation about Search improvements</span> De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramentos de Pesquisa]]. A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> iafxj3fotfsy3xnaziide3ett2oynpk 5386609 5386607 2022-07-28T16:26:37Z Eliazhar 17652978 Created page with "Consulta sobre aprimoramentos de Pesquisa" wikitext text/x-wiki <languages /> <span lang="en" dir="ltr" class="mw-content-ltr">''Welcome to the newsletter for '''Structured Data Across Wikimedia (SDAW)'''! You can [[:mw:Newsletter:Structured Data Across Wikimedia|update your subscription to the newsletter]] at any time. If you have suggestions or questions, please [[:mw:Talk:Structured Data Across Wikimedia|let us know]]!''</span> ;Consulta sobre aprimoramentos de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramentos de Pesquisa]]. A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 1y0rf13pi1bo97i2taud6uhby6eokpm 5386613 5386609 2022-07-28T16:35:22Z Eliazhar 17652978 Created page with "''Bem-vindos ao boletim informativo de '''Dados Estruturados através da Wikimedia (SDAW)'''! Você pode [[$newsletter|atualizar sua assinatura do boletim informativo]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|nos informe]]!''" wikitext text/x-wiki <languages /> ''Bem-vindos ao boletim informativo de '''Dados Estruturados através da Wikimedia (SDAW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura do boletim informativo]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|nos informe]]!'' ;Consulta sobre aprimoramentos de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramentos de Pesquisa]]. A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> bslogqz0h078p1ejkoskb7xh0r484qx 5387306 5386613 2022-07-28T22:02:24Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre aprimoramentos de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramentos de Pesquisa]]. A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> ne8mi7u86mvrecxdapna3yjxi1prf0f 5387312 5387306 2022-07-28T22:02:36Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramentos de Pesquisa]]. A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> n6tfa2o1z7w4hcvklzooa6nm3xhh8nn 5387318 5387312 2022-07-28T22:02:53Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 2fqq5uakhr4yosd8vcwfgvp021thibo 5387326 5387318 2022-07-28T22:03:30Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 09ynye1vmi6ovzmnh0us9q3gll0k0l4 5387341 5387326 2022-07-28T22:07:42Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipédias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora nos concentremos em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre aprimoramentos de pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> c7gg8qz69hjwfdvue7v5lx1ssc75x0s 5387343 5387341 2022-07-28T22:08:23Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipédias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora iremos nos concentrar em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipédia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre Aprimoramento de Pesquisa]]. ;Implantação de sugestões de Imagem Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> kbclgi1urj0tqktwj511cf1kg8jxewf 5387345 5387343 2022-07-28T22:08:43Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipédias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora iremos nos concentrar em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipédia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre Aprimoramento de Pesquisa]]. ;Implantação da Sugestão de Imagens Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de palestras]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 46auvjdl23b5tzdef05ff6lz3bxh3c2 5387347 5387345 2022-07-28T22:09:37Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipédias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora iremos nos concentrar em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipédia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre Aprimoramento de Pesquisa]]. ;Implantação da Sugestão de Imagens Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre o boletim Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de discussão]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> g4kodhfe880g0u47rrpq60vgholts5j 5387349 5387347 2022-07-28T22:09:51Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipédias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora iremos nos concentrar em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipédia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre Aprimoramento de Pesquisa]]. ;Implantação da Sugestão de Imagens Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre a newsletter Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de discussão]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> pix4cx7lo05vbs5bbn1jyonl5zj68g4 5387351 5387349 2022-07-28T22:10:23Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipédias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora iremos nos concentrar em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipédia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre Aprimoramento de Pesquisa]]. ;Implantação da Sugestão de Imagens Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre a newsletter Essa newsletter será lançada somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua página de discussão, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de discussão]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> m4cgzbm3az47vvkt95f3k5zr6x0m40j 5387368 5387351 2022-07-28T22:11:36Z FDoria-WMF 17581223 wikitext text/x-wiki <languages /> ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[:mw:Newsletter:Structured Data Across Wikimedia|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] ;Consulta sobre Aprimoramento de Pesquisa De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[Special:Search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[:mw:Structured Data Across Wikimedia/Search Improvements|Aprimoramento de Pesquisa]]. A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". A consulta ocorreu em 12 Wikipédias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[:File:SDAW Search improv 02 Namespace tag.png|proposta sobre tags de namespace]], e ajustar ligeiramente as [[:File:SDAW Search improv 01 thumbnail.png|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[:File:SDAW Search improv 04a Advanced search collapsed.png|remoção das opções de busca avançadas]]. Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. Agora iremos nos concentrar em coletar feedback sobre a [[:File:SDAW Search improv 05 quick view.png|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipédia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[:mw:Talk:Structured Data Across Wikimedia/Search Improvements|Página de discussão sobre Aprimoramento de Pesquisa]]. ;Implantação da Sugestão de Imagens Em 20 de julho, uma primeira iteração da ferramenta [[:mw:Structured Data Across Wikimedia/Image Suggestions|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, as pessoas editoras com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. ;Sobre a newsletter Essa newsletter será lançada somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua página de discussão, nos informe. Informe-nos também sobre suas ideias na [[:mw:Talk:Structured Data Across Wikimedia|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[mw:User talk:Sannita (WMF)|página de discussão]]. Esperamos ler e ver você em breve! <noinclude> -- [[m:User:Sannita (WMF)|Sannita (WMF)]] ([[m:User talk:Sannita (WMF)|talk]]) [[Category:Structured Data Across Wikimedia| ]]</noinclude> 1zg646adf4zm2lepe022uwjz2ia164e Translations:Structured Data Across Wikimedia/Newsletter/6/14/pt-br 1198 1607205 5386572 2022-07-28T15:45:29Z Eliazhar 17652978 Created page with "Informe-nos também sobre suas ideias na [[$talk|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[$talksannita|página de discussão]]." wikitext text/x-wiki Informe-nos também sobre suas ideias na [[$talk|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[$talksannita|página de discussão]]. tfgckmhrvd4iffy2ieatdiq6c4miqp8 5386574 5386572 2022-07-28T15:46:41Z Eliazhar 17652978 wikitext text/x-wiki Informe-nos também sobre suas ideias na [[$talk|página de palestras do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[$talksannita|página de palestras]]. 27x2tx3z8abjp1z0nop7da4bgqb952o 5387346 5386574 2022-07-28T22:09:35Z FDoria-WMF 17581223 wikitext text/x-wiki Informe-nos também sobre suas ideias na [[$talk|página de discussão do projeto]]. Se você tiver perguntas diretas, pode também consultar minha [[$talksannita|página de discussão]]. tfgckmhrvd4iffy2ieatdiq6c4miqp8 Translations:Structured Data Across Wikimedia/Newsletter/6/13/pt-br 1198 1607206 5386576 2022-07-28T15:48:28Z Eliazhar 17652978 Created page with "Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe." wikitext text/x-wiki Este boletim será lançado somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua palestra, nos informe. p9nufx7vsvdp7ebiaap5bjmn1oak1hg 5387350 5386576 2022-07-28T22:10:21Z FDoria-WMF 17581223 wikitext text/x-wiki Essa newsletter será lançada somente quando houver coisas a serem discutidas ou anunciadas, e planejamos fazê-lo da maneira menos invasiva para sua palestra (ou seja, através de suas notificações). Se você quiser que ele seja entregue em sua página de discussão, nos informe. 4ncf6059r9zln72hvy6h27m9z31j1aa Translations:Structured Data Across Wikimedia/Newsletter/6/12/pt-br 1198 1607207 5386578 2022-07-28T15:49:08Z Eliazhar 17652978 Created page with "Sobre o boletim" wikitext text/x-wiki Sobre o boletim nyfqprra2h1nqlzgyv88cme5s4qc6qt 5387348 5386578 2022-07-28T22:09:49Z FDoria-WMF 17581223 wikitext text/x-wiki Sobre a newsletter hgc2ld4pg7cy6roeddmjhkqun29m2k1 Translations:Template:Reading/Web/Desktop Improvements/Talk page intro/1/he 1198 1607208 5386580 2022-07-28T15:49:44Z Omeritzics 17355017 Created page with "'''אפשר להגיב בכל שפה שהיא'''. מה שהכי מעניין כרגע אותנו זה:" wikitext text/x-wiki '''אפשר להגיב בכל שפה שהיא'''. מה שהכי מעניין כרגע אותנו זה: gi0rd97uczbhiuudjoup9wh1c35pq81 Template:Reading/Web/Desktop Improvements/Talk page intro/he 10 1607209 5386581 2022-07-28T15:49:45Z Omeritzics 17355017 Created page with "'''אפשר להגיב בכל שפה שהיא'''. מה שהכי מעניין כרגע אותנו זה:" wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = '''אפשר להגיב בכל שפה שהיא'''. מה שהכי מעניין כרגע אותנו זה: <div lang="en" dir="ltr" class="mw-content-ltr"> * Feedback on the functionalities we have already deployed, </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Ideas and mockups for future functionalities - How could they be further improved? What important considerations are not currently documented? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Identifying other focus areas we have not yet discovered, </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Expanding the list of existing gadgets and user scripts that are related to providing a better desktop experience. </div> {{int:Feedback-thanks-title}} <small><span class=plainlinks>([https://www.mediawiki.org/w/index.php?title=Special:Translate&group=page-Template%3AReading%2FWeb%2FDesktop+Improvements%2FTalk+page+intro {{int:translate-tag-translate-link-desc}}])</span></small> | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Reading/Web/Desktop Improvements/Talk page intro|noshift=1|uselang={{int:lang}}}} }} 7igm33obaiiwdczezkbfqqyshermrfi 5386583 5386581 2022-07-28T15:50:39Z Omeritzics 17355017 Created page with "*משוב על התכונות שכבר יש," wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = '''אפשר להגיב בכל שפה שהיא'''. מה שהכי מעניין כרגע אותנו זה: *משוב על התכונות שכבר יש, <div lang="en" dir="ltr" class="mw-content-ltr"> * Ideas and mockups for future functionalities - How could they be further improved? What important considerations are not currently documented? </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Identifying other focus areas we have not yet discovered, </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Expanding the list of existing gadgets and user scripts that are related to providing a better desktop experience. </div> {{int:Feedback-thanks-title}} <small><span class=plainlinks>([https://www.mediawiki.org/w/index.php?title=Special:Translate&group=page-Template%3AReading%2FWeb%2FDesktop+Improvements%2FTalk+page+intro {{int:translate-tag-translate-link-desc}}])</span></small> | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Reading/Web/Desktop Improvements/Talk page intro|noshift=1|uselang={{int:lang}}}} }} t4xlvj0w4l62xznrdxujyjqyis04wvi 5386587 5386583 2022-07-28T15:52:03Z Omeritzics 17355017 Created page with "*רעיונות והצעות לשיפור התכונות העתידיות - איך אפשר לשפר אותן? אילו שיקולים חשובים לא נלקחו בחשבון עד היום?" wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = '''אפשר להגיב בכל שפה שהיא'''. מה שהכי מעניין כרגע אותנו זה: *משוב על התכונות שכבר יש, *רעיונות והצעות לשיפור התכונות העתידיות - איך אפשר לשפר אותן? אילו שיקולים חשובים לא נלקחו בחשבון עד היום? <div lang="en" dir="ltr" class="mw-content-ltr"> * Identifying other focus areas we have not yet discovered, </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Expanding the list of existing gadgets and user scripts that are related to providing a better desktop experience. </div> {{int:Feedback-thanks-title}} <small><span class=plainlinks>([https://www.mediawiki.org/w/index.php?title=Special:Translate&group=page-Template%3AReading%2FWeb%2FDesktop+Improvements%2FTalk+page+intro {{int:translate-tag-translate-link-desc}}])</span></small> | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Reading/Web/Desktop Improvements/Talk page intro|noshift=1|uselang={{int:lang}}}} }} oc7hic24zyrwcx3vubq4qy24ho2j9kf Translations:Template:Reading/Web/Desktop Improvements/Talk page intro/2/he 1198 1607210 5386582 2022-07-28T15:50:38Z Omeritzics 17355017 Created page with "*משוב על התכונות שכבר יש," wikitext text/x-wiki *משוב על התכונות שכבר יש, na2uhdo2rgh54ae2dg8dzpz3cafh34y Translations:Structured Data Across Wikimedia/Newsletter/6/11/pt-br 1198 1607211 5386584 2022-07-28T15:51:04Z Eliazhar 17652978 Created page with "Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe." wikitext text/x-wiki Estamos atualmente coletando o primeiro feedback dos usuários envolvidos, que será usado para identificar potenciais bugs e melhorar a experiência atual. Se você estiver interessado em envolver sua comunidade nas seguintes iterações da ferramenta, por favor nos informe. 88gp2idnil5bush8d2ihziyzpcy15ce Translations:Template:Reading/Web/Desktop Improvements/Talk page intro/4/he 1198 1607212 5386586 2022-07-28T15:52:03Z Omeritzics 17355017 Created page with "*רעיונות והצעות לשיפור התכונות העתידיות - איך אפשר לשפר אותן? אילו שיקולים חשובים לא נלקחו בחשבון עד היום?" wikitext text/x-wiki *רעיונות והצעות לשיפור התכונות העתידיות - איך אפשר לשפר אותן? אילו שיקולים חשובים לא נלקחו בחשבון עד היום? 1hsikenkh18jk2582jlmee60qxyiebj Translations:Structured Data Across Wikimedia/Newsletter/6/10/pt-br 1198 1607213 5386589 2022-07-28T16:03:28Z Eliazhar 17652978 Created page with "O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, g..." wikitext text/x-wiki O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, os editores com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. jr9udqnnoes0w2z1znbh13h4mou7dg1 5387358 5386589 2022-07-28T22:11:29Z FDoria-WMF 17581223 wikitext text/x-wiki O objetivo da ferramenta é incorporar uma série de sugestões de imagens nas atividades existentes do usuário da Wikipédia através de notificações semanais, aumentando assim a probabilidade de que eles revisem tais sugestões e adicionem imagens selecionadas como parte de seu atual fluxo de trabalho de edição. Atualmente, as pessoas editoras com mais de 500 edições nos projetos identificados adicionam uma média de 8 a 11 mídias. Esperamos que estas taxas melhorem, graças à nossa ferramenta. 0b9pdj5qs7sl9sagy885x6w84r9q6g8 Translations:Structured Data Across Wikimedia/Newsletter/6/9/pt-br 1198 1607214 5386591 2022-07-28T16:05:05Z Eliazhar 17652978 Created page with "Em 20 de julho, uma primeira iteração da ferramenta [[$imgsugg|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto." wikitext text/x-wiki Em 20 de julho, uma primeira iteração da ferramenta [[$imgsugg|Ferramenta de sugestões de imagem]] foi implantada com sucesso na Wikipédia em português, russo e indonésio. As três Wikipédias foram identificadas nos últimos meses como as primeiras comunidades de testadores para este projeto. j8ynuzgmh4y6d8jj1w9tmujy4sq2jo8 Translations:Structured Data Across Wikimedia/Newsletter/6/8/pt-br 1198 1607215 5386593 2022-07-28T16:05:48Z Eliazhar 17652978 Created page with "Implantação de sugestões de Imagem" wikitext text/x-wiki Implantação de sugestões de Imagem 6dwfojrgbrcd9d0a3zdunw4fex3oncc 5387344 5386593 2022-07-28T22:08:42Z FDoria-WMF 17581223 wikitext text/x-wiki Implantação da Sugestão de Imagens b4c89r63yk4im962ruga6lxhd10xefw Translations:Structured Data Across Wikimedia/Newsletter/6/7/pt-br 1198 1607216 5386595 2022-07-28T16:12:33Z Eliazhar 17652978 Created page with "Agora nos concentremos em coletar feedback sobre a [[$improv5|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[$searchimprovtalk|Página de discussão sobre aprimoramentos de pesquisa]]." wikitext text/x-wiki Agora nos concentremos em coletar feedback sobre a [[$improv5|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipedia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[$searchimprovtalk|Página de discussão sobre aprimoramentos de pesquisa]]. f7rko3lw2auv6t7no5y7ymu2ji2uj4f 5387342 5386595 2022-07-28T22:08:22Z FDoria-WMF 17581223 wikitext text/x-wiki Agora iremos nos concentrar em coletar feedback sobre a [[$improv5|Prévia do Resultado das Pesquisas]]. Nosso foco principal será inicialmente com as comunidades portuguesa, russa e indonésia da Wikipédia, bem como Mediawiki.org. Você sempre poderá compartilhar seu feedback na [[$searchimprovtalk|Página de discussão sobre Aprimoramento de Pesquisa]]. do7il9rsgzyexo8f2210j2pwqphwfjk Translations:Structured Data Across Wikimedia/Newsletter/6/6/pt-br 1198 1607217 5386598 2022-07-28T16:13:36Z Eliazhar 17652978 Created page with "Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração." wikitext text/x-wiki Todas os outros melhoramentos receberam um feedback geral positivo na consulta, e começamos a implementá-los nos últimos dias. Agradecemos a todos os usuários que dedicaram tempo para participar e compartilhar suas opiniões, as quais foram levadas em consideração. rt43lk7iqleevuyplxfb81s0uog6oa8 Translations:Structured Data Across Wikimedia/Newsletter/6/5/pt-br 1198 1607218 5386601 2022-07-28T16:21:56Z Eliazhar 17652978 Created page with "A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[$improv2|proposta sobre tags de namespace]], e ajustar ligeiramente as [[$improv1|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[$improv4|remoção das opções de busca avançadas]]." wikitext text/x-wiki A consulta ocorreu em 12 Wikipedias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[$improv2|proposta sobre tags de namespace]], e ajustar ligeiramente as [[$improv1|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[$improv4|remoção das opções de busca avançadas]]. 9j7597a1y05wl5ml5e1mvokzx5ofhh3 5387340 5386601 2022-07-28T22:07:41Z FDoria-WMF 17581223 wikitext text/x-wiki A consulta ocorreu em 12 Wikipédias diferentes e no Mediawiki.org, com uma participação substancial dos usuários. Com base no precioso feedback coletado, decidimos reavaliar nossa [[$improv2|proposta sobre tags de namespace]], e ajustar ligeiramente as [[$improv1|thumbnails do artigos]] a fim de facilitar aos usuários escondê-las, se necessário. Decidimos também não prosseguir com a [[$improv4|remoção das opções de busca avançadas]]. a8yhwize0gfptbomjeu1u0aeazl5pgx Translations:Structured Data Across Wikimedia/Newsletter/6/4/pt-br 1198 1607219 5386603 2022-07-28T16:23:56Z Eliazhar 17652978 Created page with "A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos"." wikitext text/x-wiki A maioria das mudanças propostas foram melhorias gráficas, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". qxquxoft4wundtuflow7sbblladd5io 5387323 5386603 2022-07-28T22:03:29Z FDoria-WMF 17581223 wikitext text/x-wiki A maioria das mudanças propostas foram melhorias de design, visando proporcionar contexto e layout melhores para leitores casuais que desejam usar a página de busca da Wikipédia, bem como promover a conscientização para os projetos irmãos da Wikipédia, reorganizando a seção de busca "projetos irmãos". 8ropxyfcu9eay666q86j3oc4fs7in0b Translations:Structured Data Across Wikimedia/Newsletter/6/3/pt-br 1198 1607220 5386605 2022-07-28T16:26:00Z Eliazhar 17652978 Created page with "De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[$search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[$searchimprov|Aprimoramentos de Pesquisa]]." wikitext text/x-wiki De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[$search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[$searchimprov|Aprimoramentos de Pesquisa]]. nt4mj4ychnfj7izv3mqs6a09p9nnyy2 5387316 5386605 2022-07-28T22:02:52Z FDoria-WMF 17581223 wikitext text/x-wiki De 21 de junho a 10 de julho, realizamos uma consulta geral sobre uma série de melhorias para [[$search|Especial:Pesquisa]], como parte da iniciativa geral sobre [[$searchimprov|Aprimoramento de Pesquisa]]. 6jgweoo32cc2ks85poys7xeqdvywomq Translations:Structured Data Across Wikimedia/Newsletter/6/2/pt-br 1198 1607221 5386608 2022-07-28T16:26:36Z Eliazhar 17652978 Created page with "Consulta sobre aprimoramentos de Pesquisa" wikitext text/x-wiki Consulta sobre aprimoramentos de Pesquisa 8ejy26hvayna78nlx7e6jnovvl9m195 5387310 5386608 2022-07-28T22:02:35Z FDoria-WMF 17581223 wikitext text/x-wiki Consulta sobre Aprimoramento de Pesquisa 7i7mjkhmiu9pwvmxtvv2ifm3wsgqza7 Translations:Structured Data Across Wikimedia/Newsletter/6/1/pt-br 1198 1607222 5386612 2022-07-28T16:35:21Z Eliazhar 17652978 Created page with "''Bem-vindos ao boletim informativo de '''Dados Estruturados através da Wikimedia (SDAW)'''! Você pode [[$newsletter|atualizar sua assinatura do boletim informativo]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|nos informe]]!''" wikitext text/x-wiki ''Bem-vindos ao boletim informativo de '''Dados Estruturados através da Wikimedia (SDAW)'''! Você pode [[$newsletter|atualizar sua assinatura do boletim informativo]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|nos informe]]!'' ajtuezhr18joe6lmcela62rek35hubv 5387305 5386612 2022-07-28T22:02:23Z FDoria-WMF 17581223 wikitext text/x-wiki ''Bem-vindos ao newsletter do '''Dados Estruturados na Wikimedia (DEW)'''! Você pode [[$newsletter|atualizar sua assinatura da newsletter]] a qualquer momento. Se você tiver sugestões ou perguntas, por favor [[$falk|entre em contato]] jrqv4716ckac4it0038evlvn5oessmg Translations:Manual:Namespace/15/it 1198 1607223 5386615 2022-07-28T17:02:25Z GpieroMW 17587484 Created page with "L'elenco completo è mostrato nella tabella sotto." wikitext text/x-wiki L'elenco completo è mostrato nella tabella sotto. kyrg3ltdasqk8h5lulbs4lvxay9vjbq Translations:Manual:Namespace/20/it 1198 1607224 5386617 2022-07-28T17:04:35Z GpieroMW 17587484 Created page with "Modificare una pagina di discussione utente genera una notifica per l'utente." wikitext text/x-wiki Modificare una pagina di discussione utente genera una notifica per l'utente. g7tjbqw78i2v0at9z7fjjybv1eeknj8 Translations:Manual:Namespace/21/it 1198 1607225 5386619 2022-07-28T17:04:44Z GpieroMW 17587484 Created page with "Informazione sul wiki." wikitext text/x-wiki Informazione sul wiki. 5bhffuninb7yx3gm34cha9gkkxdp0o3 Translations:Manual:Namespace/29/it 1198 1607226 5386621 2022-07-28T17:05:16Z GpieroMW 17587484 Created page with "Contiene pagine speciali" wikitext text/x-wiki Contiene pagine speciali 5b4v58rcdb2lvuplqkanrayif8km3pd Translations:Manual:Namespace/28/it 1198 1607227 5386623 2022-07-28T17:05:32Z GpieroMW 17587484 Created page with "Pagine di descrizione di categorie" wikitext text/x-wiki Pagine di descrizione di categorie 2scgl3x7272a0ymlyibz0bcq77bcnrm Translations:Manual:Namespace/43/it 1198 1607228 5386625 2022-07-28T17:06:28Z GpieroMW 17587484 Created page with "* [[$confset-ns|Manual:Configuration settings#Namespaces]]" wikitext text/x-wiki * [[$confset-ns|Manual:Configuration settings#Namespaces]] b47u2xxno2ytpri0dzwm9j62jjegd6x Translations:Manual:Namespace/51/it 1198 1607229 5386627 2022-07-28T17:07:22Z GpieroMW 17587484 Created page with "I file possono essere spostati dagli utenti con il permesso "$1"." wikitext text/x-wiki I file possono essere spostati dagli utenti con il permesso "$1". bmaticwduh3x0kvxw7tjxydmvavg6qq Translations:Manual:Namespace/40/it 1198 1607230 5386629 2022-07-28T17:08:13Z GpieroMW 17587484 Created page with "Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in $h-manage e $h-cat." wikitext text/x-wiki Le pagine per file e categorie hanno delle funzionalità speciali, come descritto in $h-manage e $h-cat. dycrka2pfolt1poc1dg6xmly5342ve9 Translations:Manual:CommonSettings.php/Page display title/ru 1198 1607231 5386702 2022-07-28T17:44:35Z Артём 13327 17625157 Created page with "Руководство:CommonSettings.php" wikitext text/x-wiki Руководство:CommonSettings.php 7dbz05mgyy29zuzmhjieotloylr67pj Translations:Manual:Load.php/Page display title/ru 1198 1607232 5386703 2022-07-28T17:44:51Z Артём 13327 17625157 Created page with "Руководство:Load.php" wikitext text/x-wiki Руководство:Load.php 6cah7xd3ddv2k5tfdol5iflso9qmcy6 Translations:Manual:Orphans.php/Page display title/ru 1198 1607233 5386704 2022-07-28T17:46:25Z Артём 13327 17625157 Created page with "Руководство:Orphans.php" wikitext text/x-wiki Руководство:Orphans.php 7z98jky2p2xkpxi5es1yfpmv07ymgs7 Manual:Orphans.php/ru 100 1607234 5386705 2022-07-28T17:46:26Z Артём 13327 17625157 Created page with "Руководство:Orphans.php" wikitext text/x-wiki <languages/> {{Removed|1.38.0|newvarname=deleteOrphanedRevisions.php}} {{MW file|orphans.php|maintenance/|class1=Orphans}} <div lang="en" dir="ltr" class="mw-content-ltr"> '''orphans.php''' is a [[Manual:Maintenance scripts|MediaWiki maintenance script]] that looks for 'orphan' revisions (= revisions, which point to a non-existing page) and for 'childless' pages with no revisions (= pages, which point to a non-existing revision). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Options == </div> {| class=wikitable |- ! width="20%" | <span lang="en" dir="ltr" class="mw-content-ltr">Option/Parameter</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Description</span> |- | --fix || <span lang="en" dir="ltr" class="mw-content-ltr">Actually fix broken entries.</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> == Usage == </div> <syntaxhighlight lang="bash" style="overfow:auto;"> php maintenance/orphans.php [ --fix ] </syntaxhighlight> {{terminal|text= $ php maintenance/orphans.php Checking for orphan revision table entries... (this may take a while on a large wiki) No orphans! Yay! Checking for pages whose page_latest links are incorrect... (this may take a while on a large wiki) No pages with incorrect latest revision. Yay! }} {{Note|1=By default, the script finds but does not fix broken entries. <span lang="en" dir="ltr" class="mw-content-ltr">To actually fix broken entries, run the script with --fix parameter.</span>}} <div lang="en" dir="ltr" class="mw-content-ltr"> == See also == </div> * [[Manual:findOrphanedFiles.php]] * [[Manual:orphanStats.php]] [[Category:Maintenance scripts{{#translation:}}|Orphans.php]] [[Category:Content maintenance scripts{{#translation:}}]] 9oojlfcdnhy9zt5bykaw8i3oxn3bwmz 5386707 5386705 2022-07-28T17:46:39Z Артём 13327 17625157 Created page with "== См. также ==" wikitext text/x-wiki <languages/> {{Removed|1.38.0|newvarname=deleteOrphanedRevisions.php}} {{MW file|orphans.php|maintenance/|class1=Orphans}} <div lang="en" dir="ltr" class="mw-content-ltr"> '''orphans.php''' is a [[Manual:Maintenance scripts|MediaWiki maintenance script]] that looks for 'orphan' revisions (= revisions, which point to a non-existing page) and for 'childless' pages with no revisions (= pages, which point to a non-existing revision). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Options == </div> {| class=wikitable |- ! width="20%" | <span lang="en" dir="ltr" class="mw-content-ltr">Option/Parameter</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Description</span> |- | --fix || <span lang="en" dir="ltr" class="mw-content-ltr">Actually fix broken entries.</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> == Usage == </div> <syntaxhighlight lang="bash" style="overfow:auto;"> php maintenance/orphans.php [ --fix ] </syntaxhighlight> {{terminal|text= $ php maintenance/orphans.php Checking for orphan revision table entries... (this may take a while on a large wiki) No orphans! Yay! Checking for pages whose page_latest links are incorrect... (this may take a while on a large wiki) No pages with incorrect latest revision. Yay! }} {{Note|1=By default, the script finds but does not fix broken entries. <span lang="en" dir="ltr" class="mw-content-ltr">To actually fix broken entries, run the script with --fix parameter.</span>}} == См. также == * [[Manual:findOrphanedFiles.php]] * [[Manual:orphanStats.php]] [[Category:Maintenance scripts{{#translation:}}|Orphans.php]] [[Category:Content maintenance scripts{{#translation:}}]] pod7fzat2s95e5mekqun1vj8yiwhlho 5386709 5386707 2022-07-28T17:46:47Z Артём 13327 17625157 Created page with "Описание" wikitext text/x-wiki <languages/> {{Removed|1.38.0|newvarname=deleteOrphanedRevisions.php}} {{MW file|orphans.php|maintenance/|class1=Orphans}} <div lang="en" dir="ltr" class="mw-content-ltr"> '''orphans.php''' is a [[Manual:Maintenance scripts|MediaWiki maintenance script]] that looks for 'orphan' revisions (= revisions, which point to a non-existing page) and for 'childless' pages with no revisions (= pages, which point to a non-existing revision). </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Options == </div> {| class=wikitable |- ! width="20%" | <span lang="en" dir="ltr" class="mw-content-ltr">Option/Parameter</span> ! Описание |- | --fix || <span lang="en" dir="ltr" class="mw-content-ltr">Actually fix broken entries.</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> == Usage == </div> <syntaxhighlight lang="bash" style="overfow:auto;"> php maintenance/orphans.php [ --fix ] </syntaxhighlight> {{terminal|text= $ php maintenance/orphans.php Checking for orphan revision table entries... (this may take a while on a large wiki) No orphans! Yay! Checking for pages whose page_latest links are incorrect... (this may take a while on a large wiki) No pages with incorrect latest revision. Yay! }} {{Note|1=By default, the script finds but does not fix broken entries. <span lang="en" dir="ltr" class="mw-content-ltr">To actually fix broken entries, run the script with --fix parameter.</span>}} == См. также == * [[Manual:findOrphanedFiles.php]] * [[Manual:orphanStats.php]] [[Category:Maintenance scripts{{#translation:}}|Orphans.php]] [[Category:Content maintenance scripts{{#translation:}}]] ihksf1w018mwkt0skutytxdjhtth6o0 Translations:Manual:Orphans.php/14/ru 1198 1607235 5386706 2022-07-28T17:46:38Z Артём 13327 17625157 Created page with "== См. также ==" wikitext text/x-wiki == См. также == bi8ivbgs7b8bnnxddobnkm64gog2n6t Translations:Manual:Orphans.php/9/ru 1198 1607236 5386708 2022-07-28T17:46:46Z Артём 13327 17625157 Created page with "Описание" wikitext text/x-wiki Описание sne5uwauacf0fbubh1ygbthckefxvb4 Translations:Manual:Mwdocgen.php/10/ru 1198 1607237 5386710 2022-07-28T17:47:55Z Артём 13327 17625157 Created page with "Описание" wikitext text/x-wiki Описание sne5uwauacf0fbubh1ygbthckefxvb4 Translations:Manual:Mwdocgen.php/Page display title/ru 1198 1607238 5386712 2022-07-28T17:48:37Z Артём 13327 17625157 Created page with "Руководство:Mwdocgen.php" wikitext text/x-wiki Руководство:Mwdocgen.php av0rc8ara80nvzsp1a05xw4txzzo4qd Translations:Help:Extension:UniversalLanguageSelector/Input methods/kbp-tilde/7/de 1198 1607239 5386722 2022-07-28T18:48:25Z ThisCarthing 17456337 Created page with "Klicke "..." am Ende der Liste. Ein Menü wird erscheinen." wikitext text/x-wiki Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. th5jijk90e27imp9zu5frale6kl6kaa Translations:Help:Extension:UniversalLanguageSelector/Input methods/kbp-tilde/8/de 1198 1607240 5386724 2022-07-28T18:48:34Z ThisCarthing 17456337 Created page with "Finde "Kabɩyɛ" in dem Menü. Klicke es." wikitext text/x-wiki Finde "Kabɩyɛ" in dem Menü. Klicke es. mgsgkg1izt7fviq0eeyw78ih1fe9srl Translations:Help:Extension:UniversalLanguageSelector/Input methods/kbp-tilde/Page display title/de 1198 1607241 5386726 2022-07-28T18:48:41Z ThisCarthing 17456337 Created page with "Hilfe:Erweiterung:UniversalLanguageSelector/Eingabemethoden/kbp-tilde" wikitext text/x-wiki Hilfe:Erweiterung:UniversalLanguageSelector/Eingabemethoden/kbp-tilde 1rnbhy2cgo8qm9q7hsascuu4h68qhde Translations:Help:Extension:UniversalLanguageSelector/Input methods/kbp-tilde/1/de 1198 1607242 5386727 2022-07-28T18:49:03Z ThisCarthing 17456337 Created page with "Du kannst im Kabɩyɛ (Kabiye)-Alphabet mit allen Spezialbuchstaben tippen!" wikitext text/x-wiki Du kannst im Kabɩyɛ (Kabiye)-Alphabet mit allen Spezialbuchstaben tippen! 8nv1naebivw82s7lcayt3i2n7es6yrj Translations:Help:Extension:UniversalLanguageSelector/Input methods/nso-tilde/Page display title/de 1198 1607243 5386729 2022-07-28T18:49:18Z ThisCarthing 17456337 Created page with "Hilfe:Erweiterung:UniversalLanguageSelector/Eingabemethoden/nso-tilde" wikitext text/x-wiki Hilfe:Erweiterung:UniversalLanguageSelector/Eingabemethoden/nso-tilde 6vv0a399mxahhi3geduz36lh752s2iw Translations:Universal Language Selector/FAQ/96/de 1198 1607244 5386732 2022-07-28T18:50:27Z ThisCarthing 17456337 Created page with "Schriftart" wikitext text/x-wiki Schriftart bk716f8vta1eeej23s1wyeg59isi8if Translations:UploadWizard/71/de 1198 1607245 5386734 2022-07-28T18:51:36Z ThisCarthing 17456337 Created page with "Danke für deine Geduld und dein Verständnis :)" wikitext text/x-wiki Danke für deine Geduld und dein Verständnis :) mlc5gsbmfz2ivuxyk6q0vlltrko7onh Translations:UploadWizard/41/de 1198 1607246 5386736 2022-07-28T18:51:42Z ThisCarthing 17456337 Created page with "== Aufgaben ==" wikitext text/x-wiki == Aufgaben == 4qeu7mgsiicrriouoqo2l0e2tz7t10v Translations:Help:Extension:UniversalLanguageSelector/Input methods/vai-transliteration/35/de 1198 1607247 5386738 2022-07-28T18:52:19Z ThisCarthing 17456337 Created page with "Anmerkungen:" wikitext text/x-wiki Anmerkungen: iqmjq4v3cy597ym2xbzoa3axmwt8hwj Translations:Help:Extension:UniversalLanguageSelector/Input methods/vai-transliteration/36/de 1198 1607248 5386740 2022-07-28T18:52:34Z ThisCarthing 17456337 Created page with "ꘋ kann auch mit X getippt werden." wikitext text/x-wiki ꘋ kann auch mit X getippt werden. ptypvfi3dqgctwoe42w86hd04nfjwn2 Translations:Help:Extension:UniversalLanguageSelector/Input methods/vai-transliteration/10/de 1198 1607249 5386742 2022-07-28T18:52:50Z ThisCarthing 17456337 Created page with "Klicke "..." am Ende der Liste. Ein Menü wird erscheinen." wikitext text/x-wiki Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. th5jijk90e27imp9zu5frale6kl6kaa Translations:Help:Extension:UniversalLanguageSelector/Input methods/nqo-transliteration/Page display title/de 1198 1607250 5386744 2022-07-28T18:53:10Z ThisCarthing 17456337 Created page with "Hilfe:Erweiterung:UniversalLanguageSelector/Eingabemethoden/nqo-transliteration" wikitext text/x-wiki Hilfe:Erweiterung:UniversalLanguageSelector/Eingabemethoden/nqo-transliteration igrjcaor2tdrtnmxk2yflbjike5eeli Translations:Help:Extension:UniversalLanguageSelector/Input methods/nqo-transliteration/14/de 1198 1607251 5386745 2022-07-28T18:53:17Z ThisCarthing 17456337 Created page with "Lateinischer Buchstabe" wikitext text/x-wiki Lateinischer Buchstabe 0bkw1i44x88fxjctmjavk9qfnqxuwj4 Translations:Help:Extension:UniversalLanguageSelector/Input methods/nqo-transliteration/15/de 1198 1607252 5386747 2022-07-28T18:53:21Z ThisCarthing 17456337 Created page with "N'Ko-Buchstabe" wikitext text/x-wiki N'Ko-Buchstabe qs97rhk32y09cqtmoegonnicfdpgblu Translations:Help:Extension:UniversalLanguageSelector/Input methods/nqo-standard-qwerty/Page display title/de 1198 1607253 5386749 2022-07-28T18:53:39Z ThisCarthing 17456337 Created page with "Hilfe:Erweiterung:UniversalLanguaeSelector/Eingabemethoden/nqo-standard-qwerty" wikitext text/x-wiki Hilfe:Erweiterung:UniversalLanguaeSelector/Eingabemethoden/nqo-standard-qwerty s2cp3ntwlx682f4rrtwtyytsk3984eh Translations:Help:Extension:UniversalLanguageSelector/Input methods/nqo-standard-qwerty/9/de 1198 1607254 5386750 2022-07-28T18:53:46Z ThisCarthing 17456337 Created page with "Klicke "..." am Ende der Liste. Ein Menü wird erscheinen." wikitext text/x-wiki Klicke "..." am Ende der Liste. Ein Menü wird erscheinen. th5jijk90e27imp9zu5frale6kl6kaa Translations:Help:Extension:UniversalLanguageSelector/Input methods/nqo-standard-qwerty/14/de 1198 1607255 5386752 2022-07-28T18:53:52Z ThisCarthing 17456337 Created page with "Die volle Liste von Tasten und Zeichen:" wikitext text/x-wiki Die volle Liste von Tasten und Zeichen: hpbhcmrn7ue8j3pakf2eekmfg9g289n Translations:Wikidata Bridge/Development/25/de 1198 1607256 5386754 2022-07-28T18:54:43Z ThisCarthing 17456337 Created page with "Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen." wikitext text/x-wiki Wir warten nicht, bis ein "fertiges" Produkt für die Bereitstellung verfügbar ist: Wir werden schrittweise mit der Aktivierung der Funktionen beginnen, in den nächsten Monaten schrittweise Bestandteile bereitstellen und es nach dem Prinzip des trial & error mit den Autoren testen. bvlrxzvmyyxlt28k20popat3rc38jsu Translations:Wikidata Bridge/Development/24/de 1198 1607257 5386756 2022-07-28T18:55:01Z ThisCarthing 17456337 Created page with "Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren." wikitext text/x-wiki Wir beginnen nicht mit einer festen Vorstellung über das Werkzeug, das wir bereitstellen möchten, sondern bauen es zusammen mit den Communities auf, basierend auf Feedback-Schleifen, die wir regelmäßig organisieren. 55svomcbp4k3jg9s39nnnyi8dpee06p Translations:Wikidata Bridge/Development/23/de 1198 1607258 5386760 2022-07-28T18:55:21Z ThisCarthing 17456337 Created page with "Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden." wikitext text/x-wiki Um sicherzustellen, dass wir ein Tool entwickeln, das den Anforderungen der Autoren entspricht, verwenden wir in unserem Entwicklungsprozess flexible Methoden. ne52c86c4k2vu2p53xi01f5mbabvly8 Translations:Wikidata Bridge/Development/22/de 1198 1607259 5386762 2022-07-28T18:57:52Z ThisCarthing 17456337 start of splitting wikitext text/x-wiki ** Mehr Wikipedia-Autoren werden zukünftig Wikidata bearbeiten gdftlr0eqmd9nvkpwv0ecckdn436duk Translations:Wikidata Bridge/Development/21/de 1198 1607260 5386764 2022-07-28T18:58:04Z ThisCarthing 17456337 Created page with "** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt" wikitext text/x-wiki ** Ein Hinweis für Bearbeitungen aus Wikidata Bridge – der Verknüpfung mit Wikidata – wird hinzugefügt dsp09nqjsaab88ji1ff7ajpqm52dovm Translations:Wikidata Bridge/Development/20/de 1198 1607261 5386766 2022-07-28T18:58:15Z ThisCarthing 17456337 Created page with "* In Wikidata" wikitext text/x-wiki * In Wikidata 333995utweszba73oyn36qrrsyickpx Translations:Wikidata Bridge/Development/19/de 1198 1607262 5386768 2022-07-28T18:58:33Z ThisCarthing 17456337 Created page with "** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet" wikitext text/x-wiki ** In angepassten Infoboxen wird die Bearbeitungsoberfläche durch einen Link oder ein Symbol (z. B. "Wikidata-Daten bearbeiten") geöffnet 80iiultc4vf30hv6zh0zkvb9xta7etv Translations:Wikidata Bridge/Development/18/de 1198 1607263 5386770 2022-07-28T18:59:48Z ThisCarthing 17456337 Created page with "** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht" wikitext text/x-wiki ** Die Betreuer der Infoboxen müssen die [[Wikidata Bridge/Development/DocDrafts/How to Enable Wikidata Bridge for your Infobox/de|Vorlagen anpassen]], um die neue Funktion anwenden zu können. Wenn sie nicht angepasst werden, funktionieren die Infoboxen weiterhin wie bisher. Die Vorlagenersteller haben also die Wahl, ob sie die Bearbeitung der Wikidata-Daten aktivieren möchten oder nicht owngfpe0leliu84w91zrkxaweocvh1v Translations:Wikidata Bridge/Development/17/de 1198 1607264 5386772 2022-07-28T18:59:56Z ThisCarthing 17456337 Created page with "* In Infoboxen" wikitext text/x-wiki * In Infoboxen et2lfee01ghu5pb1ldt1i9ljot4qehq Translations:Wikidata Bridge/Development/16/de 1198 1607265 5386774 2022-07-28T19:00:05Z ThisCarthing 17456337 Created page with "** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert" wikitext text/x-wiki ** Eine neue Funktion der Wikibase-Client-Erweiterung wird aktiviert ectt2dbfiei9wfisufwbzkx54cysl4r Translations:Wikidata Bridge/Development/26/de 1198 1607267 5386792 2022-07-28T19:03:00Z ThisCarthing 17456337 Created page with "Die erste Version wird nicht unbedingt alle Funktionen haben, die du möchtest, aber es wird sich weiterentwickeln." wikitext text/x-wiki Die erste Version wird nicht unbedingt alle Funktionen haben, die du möchtest, aber es wird sich weiterentwickeln. fv4wqws0ek27jccpxfsfwqayrmklq58 Translations:Structured Data Across Wikimedia/3/de 1198 1607268 5386795 2022-07-28T19:07:43Z ThisCarthing 17456337 Created page with "Hintergrund" wikitext text/x-wiki Hintergrund cxa4dktq41m2jczou5g2gj8zcl2h7d0 Translations:Structured Data Across Wikimedia/72/de 1198 1607269 5386797 2022-07-28T19:07:55Z ThisCarthing 17456337 Created page with "Bildvorschlag" wikitext text/x-wiki Bildvorschlag o4srlyh7hfnzjt8s5c0x3obgqivcxi0 Translations:Structured Data Across Wikimedia/Search Improvements/3/de 1198 1607270 5386799 2022-07-28T19:08:19Z ThisCarthing 17456337 Created page with "Hintergrund" wikitext text/x-wiki Hintergrund cxa4dktq41m2jczou5g2gj8zcl2h7d0 Structured Data Across Wikimedia/Search Improvements/de 0 1607271 5386800 2022-07-28T19:08:20Z ThisCarthing 17456337 Created page with "Hintergrund" wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> The '''Search Improvements project''' will use structured content to give users a more inviting and more efficient way to search and find content on the Wikipedias. By improving [[Special:Search|Special:Search]], we want to enable users to find the information they are looking for, or that they may not have noticed, or previously come across through existing search. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We aim to identify and define incremental “special search” improvements that use structured content, to assist users in finding the content they are looking for, especially in those language wikis that have fewer articles. </div> == Hintergrund == <div lang="en" dir="ltr" class="mw-content-ltr"> Existing search functionalities mainly focus on article matches. This is a problem for Wikipedias in emerging languages, because there is a higher risk for readers to end up on the Special:Search page without finding relevant articles or content. Linguistic factors and inexperience in using Special:Search are also among the main obstacles in finding content. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Moreover, it is likely that the information that the user is seeking might be “hidden” somewhere on the projects – i.e., under sections of existing articles, or inside articles with a different name, or in sister projects and other sources in our ecosystem. </div> == <span lang="en" dir="ltr" class="mw-content-ltr">The project</span> == === <span lang="en" dir="ltr" class="mw-content-ltr">What we want to do</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Work in this area may include things like:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Stylistic UI improvements to the Special:Search page</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Creating a quick view panel for each result that:</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">shows key information about the result</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">displays interwiki links related to the result</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Current mockups</span> === <gallery widths="400px" heights="300px"> SDAW Search improv 01 thumbnail.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''1.''' Add article thumbnail to search results to allow for better scanning of the content, using the same thumbnails that appear in the Go bar.</span> SDAW Search improv 02 Namespace tag.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''2.''' Add namespace tags in front of the article to be able to better distinguish between various page types.</span> </gallery> <gallery widths="400px" heights="300px"> SDAW Search improv 03 sister search.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''3.''' Rearrange the sister search section and add a header for better context and awareness of these projects.</span> </gallery> <gallery widths="400px" heights="300px"> SDAW Search improv 04a Advanced search collapsed.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''4a.''' Collapse advance search so that there is more focus on the results itself.</span> SDAW Search improv 04b Advanced search expanded.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''4b.''' The advanced search can then be expanded if the user needs to use it.</span> </gallery> <gallery widths="300px" heights="400px"> SDAW Search improv 05 quick view.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''5.''' Introduce a quick-view panel for each result to discover relevant content and go directly to a desired section of the article.</span> </gallery> <gallery widths="400px" heights="300px"> SDAW Search improv 06a metadata.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''6a.''' Re-style metadata to put more focus on the content itself.</span> SDAW Search improv 07 no article message.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''7.''' New location for “create missing article” message to allow more focus on the search results and at the same time provide a clearer and consistent call to action to add an article.</span> </gallery> <gallery widths="400px" heights="300px"> SDAW Search improv 08 did you know message.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''8.''' Change the color of the “did you know” suggestion from red to blue as red is more appropriate for missing articles. (Message A: “did you mean” message)</span> SDAW Search improv 08b show results for message.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''8b.''' (Message B: “Show results for” message)</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Improving search experience through a tool/gadget</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, we would like to work with an interested contractor to ideate and develop a tool or gadget that experiments with using structured data/content to improve the search experience on one or more Wikipedias. Please [[Special:EmailUser/Sannita (WMF)|contact Sannita]] if you’re interested in learning more about this opportunity.</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Feedback</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Project feedback is and will always be welcome. We are especially interested in your ideas, and we are looking forward [[Talk:Structured Data Across Wikimedia/Search Improvements|to hearing from you on the talk page]] about what you think about the project, and especially about the following open questions:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">What do you think about the approaches outlined above?</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Do any of these changes affect the contribution flow in your opinion? If yes, how?</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Is the content in quick view helpful to you? If so, how would you use it?</span> [[Category:Structured Data Across Wikimedia]] ic036fyj7xru0ok6o4f68is18ugyool 5386802 5386800 2022-07-28T19:08:30Z ThisCarthing 17456337 Created page with "Das Projekt" wikitext text/x-wiki <languages /> <div lang="en" dir="ltr" class="mw-content-ltr"> The '''Search Improvements project''' will use structured content to give users a more inviting and more efficient way to search and find content on the Wikipedias. By improving [[Special:Search|Special:Search]], we want to enable users to find the information they are looking for, or that they may not have noticed, or previously come across through existing search. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> We aim to identify and define incremental “special search” improvements that use structured content, to assist users in finding the content they are looking for, especially in those language wikis that have fewer articles. </div> == Hintergrund == <div lang="en" dir="ltr" class="mw-content-ltr"> Existing search functionalities mainly focus on article matches. This is a problem for Wikipedias in emerging languages, because there is a higher risk for readers to end up on the Special:Search page without finding relevant articles or content. Linguistic factors and inexperience in using Special:Search are also among the main obstacles in finding content. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Moreover, it is likely that the information that the user is seeking might be “hidden” somewhere on the projects – i.e., under sections of existing articles, or inside articles with a different name, or in sister projects and other sources in our ecosystem. </div> == Das Projekt == === <span lang="en" dir="ltr" class="mw-content-ltr">What we want to do</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Work in this area may include things like:</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Stylistic UI improvements to the Special:Search page</span> * <span lang="en" dir="ltr" class="mw-content-ltr">Creating a quick view panel for each result that:</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">shows key information about the result</span> ** <span lang="en" dir="ltr" class="mw-content-ltr">displays interwiki links related to the result</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Current mockups</span> === <gallery widths="400px" heights="300px"> SDAW Search improv 01 thumbnail.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''1.''' Add article thumbnail to search results to allow for better scanning of the content, using the same thumbnails that appear in the Go bar.</span> SDAW Search improv 02 Namespace tag.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''2.''' Add namespace tags in front of the article to be able to better distinguish between various page types.</span> </gallery> <gallery widths="400px" heights="300px"> SDAW Search improv 03 sister search.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''3.''' Rearrange the sister search section and add a header for better context and awareness of these projects.</span> </gallery> <gallery widths="400px" heights="300px"> SDAW Search improv 04a Advanced search collapsed.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''4a.''' Collapse advance search so that there is more focus on the results itself.</span> SDAW Search improv 04b Advanced search expanded.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''4b.''' The advanced search can then be expanded if the user needs to use it.</span> </gallery> <gallery widths="300px" heights="400px"> SDAW Search improv 05 quick view.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''5.''' Introduce a quick-view panel for each result to discover relevant content and go directly to a desired section of the article.</span> </gallery> <gallery widths="400px" heights="300px"> SDAW Search improv 06a metadata.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''6a.''' Re-style metadata to put more focus on the content itself.</span> SDAW Search improv 07 no article message.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''7.''' New location for “create missing article” message to allow more focus on the search results and at the same time provide a clearer and consistent call to action to add an article.</span> </gallery> <gallery widths="400px" heights="300px"> SDAW Search improv 08 did you know message.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''8.''' Change the color of the “did you know” suggestion from red to blue as red is more appropriate for missing articles. (Message A: “did you mean” message)</span> SDAW Search improv 08b show results for message.png|<span lang="en" dir="ltr" class="mw-content-ltr">'''8b.''' (Message B: “Show results for” message)</span> </gallery> === <span lang="en" dir="ltr" class="mw-content-ltr">Improving search experience through a tool/gadget</span> === <span lang="en" dir="ltr" class="mw-content-ltr">Additionally, we would like to work with an interested contractor to ideate and develop a tool or gadget that experiments with using structured data/content to improve the search experience on one or more Wikipedias. Please [[Special:EmailUser/Sannita (WMF)|contact Sannita]] if you’re interested in learning more about this opportunity.</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Feedback</span> == <span lang="en" dir="ltr" class="mw-content-ltr">Project feedback is and will always be welcome. We are especially interested in your ideas, and we are looking forward [[Talk:Structured Data Across Wikimedia/Search Improvements|to hearing from you on the talk page]] about what you think about the project, and especially about the following open questions:</span> # <span lang="en" dir="ltr" class="mw-content-ltr">What do you think about the approaches outlined above?</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Do any of these changes affect the contribution flow in your opinion? If yes, how?</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Is the content in quick view helpful to you? If so, how would you use it?</span> [[Category:Structured Data Across Wikimedia]] ofv2gqfn825jf9iaedolg2zsl4831wb Translations:Structured Data Across Wikimedia/Search Improvements/6/de 1198 1607272 5386801 2022-07-28T19:08:28Z ThisCarthing 17456337 Created page with "Das Projekt" wikitext text/x-wiki Das Projekt dkc45z4ibt92shcbku0p7ec9ad666gy Translations:Category:APIQueryAfterExecute extensions/Page display title/cs 1198 1607273 5386803 2022-07-28T19:10:27Z ThisCarthing 17456337 Created page with "Kategorie:Rozšíření APIQueryAfterExecute" wikitext text/x-wiki Kategorie:Rozšíření APIQueryAfterExecute cq0rjs83irp93k39r78fh17wc2zfh6r Category:APIQueryAfterExecute extensions/cs 14 1607274 5386804 2022-07-28T19:10:28Z ThisCarthing 17456337 Created page with "Kategorie:Rozšíření APIQueryAfterExecute" wikitext text/x-wiki <languages/> <span lang="en" dir="ltr" class="mw-content-ltr"></span> {{HookUsage|APIQueryAfterExecute}} 4j0zck9bwinsb8mbo29k8z7xpcg71al Translations:Talk pages project/Replying/Prototype testing/12/de 1198 1607275 5386806 2022-07-28T19:12:06Z ThisCarthing 17456337 Created page with "Testziele" wikitext text/x-wiki Testziele ogf0f95wg9zk0s8dw5ijjcx6mp5gv6d Translations:Help:Extension:Translate/Components/18/de 1198 1607277 5386809 2022-07-28T19:15:11Z ThisCarthing 17456337 Created page with "=== Nachrichtengruppen ===" wikitext text/x-wiki === Nachrichtengruppen === lv5cdi2lh8dvhi03o420r429b3m0mer Translations:Help:Extension:Translate/Components/24/de 1198 1607278 5386811 2022-07-28T19:15:23Z ThisCarthing 17456337 Created page with "=== Nachricht ===" wikitext text/x-wiki === Nachricht === a22v8wbe99qftbj3u53jykwv0364h4y Translations:Help:Extension:Translate/Components/22/de 1198 1607279 5386813 2022-07-28T19:15:36Z ThisCarthing 17456337 Created page with "== Weitere Kernkomponenten ==" wikitext text/x-wiki == Weitere Kernkomponenten == a8b5jk8hjoe4wduamyflokgjndez7hf Translations:Tool status/Page display title/de 1198 1607280 5386815 2022-07-28T19:16:58Z ThisCarthing 17456337 Created page with "Werkzeugstatus" wikitext text/x-wiki Werkzeugstatus 513ky9lofbdgyx2wd0j2yi4s7v5vvz9 Tool status/de 0 1607281 5386816 2022-07-28T19:16:59Z ThisCarthing 17456337 Created page with "Werkzeugstatus" wikitext text/x-wiki <languages/> <div lang="en" dir="ltr" class="mw-content-ltr"> Tool status may be categorized as: </div> {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Release status</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Explanation</span> |-- | ''{{ll|Category:Stable tools|stable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable version</span> |-- | ''{{ll|Category:Beta status tools|beta}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable but not fully tested</span> |-- | ''{{ll|Category:Experimental tools|experimental}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">early stages of development, may change drastically.</span> |-- | ''{{ll|Category:Unstable tools|unstable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">broken - do not use this tool</span> |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} 9ptozyvt6i6wqdnski5dpd9t19vvyzn 5386818 5386816 2022-07-28T19:17:15Z ThisCarthing 17456337 Created page with "Der Status des Werkzeugs kann wie folgt kategorisiert werden:" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! <span lang="en" dir="ltr" class="mw-content-ltr">Release status</span> ! <span lang="en" dir="ltr" class="mw-content-ltr">Explanation</span> |-- | ''{{ll|Category:Stable tools|stable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable version</span> |-- | ''{{ll|Category:Beta status tools|beta}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable but not fully tested</span> |-- | ''{{ll|Category:Experimental tools|experimental}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">early stages of development, may change drastically.</span> |-- | ''{{ll|Category:Unstable tools|unstable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">broken - do not use this tool</span> |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} 8nc18za6wkwotf2hibjtb0lfynckcw6 5386820 5386818 2022-07-28T19:17:19Z ThisCarthing 17456337 Created page with "Erscheinungsstatus" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! <span lang="en" dir="ltr" class="mw-content-ltr">Explanation</span> |-- | ''{{ll|Category:Stable tools|stable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable version</span> |-- | ''{{ll|Category:Beta status tools|beta}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable but not fully tested</span> |-- | ''{{ll|Category:Experimental tools|experimental}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">early stages of development, may change drastically.</span> |-- | ''{{ll|Category:Unstable tools|unstable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">broken - do not use this tool</span> |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} 0n0nl9u0s8bpd0lwmo1ctze1f30oj1p 5386823 5386820 2022-07-28T19:17:20Z ThisCarthing 17456337 Created page with "Erklärung" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable version</span> |-- | ''{{ll|Category:Beta status tools|beta}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable but not fully tested</span> |-- | ''{{ll|Category:Experimental tools|experimental}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">early stages of development, may change drastically.</span> |-- | ''{{ll|Category:Unstable tools|unstable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">broken - do not use this tool</span> |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} jqbht7uwzrw4xwuggahzhgoqrayr0bm 5386824 5386823 2022-07-28T19:17:22Z ThisCarthing 17456337 Created page with "stabile Version" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">stable but not fully tested</span> |-- | ''{{ll|Category:Experimental tools|experimental}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">early stages of development, may change drastically.</span> |-- | ''{{ll|Category:Unstable tools|unstable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">broken - do not use this tool</span> |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} le6vk9w49eidonb81q8y6c4hfvunceo 5386826 5386824 2022-07-28T19:17:25Z ThisCarthing 17456337 Created page with "stabil, aber nicht vollständig getestet" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">early stages of development, may change drastically.</span> |-- | ''{{ll|Category:Unstable tools|unstable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">broken - do not use this tool</span> |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} cpp5zcysp589u7jh4dfsjtcqkqzxhp8 5386828 5386826 2022-07-28T19:17:27Z ThisCarthing 17456337 Created page with "im Frühstadium der Entwicklung, könnte sich erheblich ändern" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | im Frühstadium der Entwicklung, könnte sich erheblich ändern |-- | ''{{ll|Category:Unstable tools|unstable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">broken - do not use this tool</span> |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} g5h7a3n34cjdqpv9n32o2jlkzpbm67d 5386830 5386828 2022-07-28T19:17:31Z ThisCarthing 17456337 wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | im Frühstadium der Entwicklung, könnte sich erheblich ändern. |-- | ''{{ll|Category:Unstable tools|unstable}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">broken - do not use this tool</span> |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} iwztoigp7h0tlvrug6bzr4rtm1vlrst 5386832 5386830 2022-07-28T19:18:20Z ThisCarthing 17456337 Created page with "defekt - verwende dieses Werkzeug nicht" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | im Frühstadium der Entwicklung, könnte sich erheblich ändern. |-- | ''{{ll|Category:Unstable tools|unstable}}'' | defekt - verwende dieses Werkzeug nicht |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">default</span> |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} jel5nldq52nbsgbkodp841zsxbizun0 5386834 5386832 2022-07-28T19:18:23Z ThisCarthing 17456337 Created page with "Voreinstellung" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | im Frühstadium der Entwicklung, könnte sich erheblich ändern. |-- | ''{{ll|Category:Unstable tools|unstable}}'' | defekt - verwende dieses Werkzeug nicht |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | Voreinstellung |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | <span lang="en" dir="ltr" class="mw-content-ltr">previously claimed to be stable, now unmaintained</span> |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} b0x6hujv2u7sc9mkatr2ks3jorlkfx9 5386836 5386834 2022-07-28T19:18:25Z ThisCarthing 17456337 Created page with "galt zuvor als stabil, wird nicht mehr gewartet" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | im Frühstadium der Entwicklung, könnte sich erheblich ändern. |-- | ''{{ll|Category:Unstable tools|unstable}}'' | defekt - verwende dieses Werkzeug nicht |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | Voreinstellung |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | galt zuvor als stabil, wird nicht mehr gewartet |} <div lang="en" dir="ltr" class="mw-content-ltr"> More details are in the [[Special:MyLanguage/Template:Tool#status|Tool information box parameters]]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} lr9f4oa9p0fukq0ld3iyepyrlc619nv 5386838 5386836 2022-07-28T19:18:40Z ThisCarthing 17456337 Created page with "Weitere Einzelheiten sind in den [[$1|Werkzeugs-Informationsboxen-Parametern]] zu finden." wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | im Frühstadium der Entwicklung, könnte sich erheblich ändern. |-- | ''{{ll|Category:Unstable tools|unstable}}'' | defekt - verwende dieses Werkzeug nicht |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | Voreinstellung |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | galt zuvor als stabil, wird nicht mehr gewartet |} Weitere Einzelheiten sind in den [[Special:MyLanguage/Template:Tool#status|Werkzeugs-Informationsboxen-Parametern]] zu finden. <div lang="en" dir="ltr" class="mw-content-ltr"> == Tool release status colour schemes == </div> {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} q5fj9ctdjn7emghrebg1eniyjy8biae 5386840 5386838 2022-07-28T19:18:49Z ThisCarthing 17456337 Created page with "== Farbschemata des Freigabestatus der Werkzeuge ==" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | im Frühstadium der Entwicklung, könnte sich erheblich ändern. |-- | ''{{ll|Category:Unstable tools|unstable}}'' | defekt - verwende dieses Werkzeug nicht |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | Voreinstellung |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | galt zuvor als stabil, wird nicht mehr gewartet |} Weitere Einzelheiten sind in den [[Special:MyLanguage/Template:Tool#status|Werkzeugs-Informationsboxen-Parametern]] zu finden. == Farbschemata des Freigabestatus der Werkzeuge == {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=<span lang="en" dir="ltr" class="mw-content-ltr">layout test</span> }} 1vg6acdj0vzc9672hsxig23cyqx9swy 5386842 5386840 2022-07-28T19:18:51Z ThisCarthing 17456337 Created page with "Layout-Test" wikitext text/x-wiki <languages/> Der Status des Werkzeugs kann wie folgt kategorisiert werden: {| class="wikitable" ! Erscheinungsstatus ! Erklärung |-- | ''{{ll|Category:Stable tools|stable}}'' | stabile Version |-- | ''{{ll|Category:Beta status tools|beta}}'' | stabil, aber nicht vollständig getestet |-- | ''{{ll|Category:Experimental tools|experimental}}'' | im Frühstadium der Entwicklung, könnte sich erheblich ändern. |-- | ''{{ll|Category:Unstable tools|unstable}}'' | defekt - verwende dieses Werkzeug nicht |-- | ''{{ll|Category:Tools with unknown status|unknown}}'' | Voreinstellung |-- | ''{{ll|Category:Unmaintained tools|unmaintained}}'' | galt zuvor als stabil, wird nicht mehr gewartet |} Weitere Einzelheiten sind in den [[Special:MyLanguage/Template:Tool#status|Werkzeugs-Informationsboxen-Parametern]] zu finden. == Farbschemata des Freigabestatus der Werkzeuge == {{tmpl|0= <div style="display: flex; flex-wrap: wrap;"> {{Tool |templatemode=nocats |name = experimental |status = experimental |description = $1 }} {{Tool |templatemode=nocats |name = beta |status = beta |description = $1 }} {{Tool |templatemode=nocats |name = stable |status = stable |description = $1 }} {{Tool |templatemode=nocats |name = unknown |description = $1 }} {{Tool |templatemode=nocats |name = unstable |status = unstable |description = $1 }} {{Tool |templatemode=nocats |name = unmaintained |status = unmaintained |description = $1 }} </div> |1=Layout-Test }} rp6ptbill909vntowz4vp642omsw6ut Translations:Tool status/1/de 1198 1607282 5386817 2022-07-28T19:17:14Z ThisCarthing 17456337 Created page with "Der Status des Werkzeugs kann wie folgt kategorisiert werden:" wikitext text/x-wiki Der Status des Werkzeugs kann wie folgt kategorisiert werden: fxqfwviftk0kwnibgle1ppljjfzdzg9 Translations:Tool status/2/de 1198 1607283 5386819 2022-07-28T19:17:18Z ThisCarthing 17456337 Created page with "Erscheinungsstatus" wikitext text/x-wiki Erscheinungsstatus 7n46njvocgkpajonlf4jvtjpgtgzlnh Translations:Tool status/23/de 1198 1607284 5386821 2022-07-28T19:17:20Z ThisCarthing 17456337 Created page with "Erklärung" wikitext text/x-wiki Erklärung 7hemldiba3hejm1n07d4pzf3tn5ldmz Translations:Tool status/4/de 1198 1607285 5386822 2022-07-28T19:17:21Z ThisCarthing 17456337 Created page with "stabile Version" wikitext text/x-wiki stabile Version skbhfm5b69yvtyk68gsf0wd971ikmgq Translations:Tool status/6/de 1198 1607286 5386825 2022-07-28T19:17:24Z ThisCarthing 17456337 Created page with "stabil, aber nicht vollständig getestet" wikitext text/x-wiki stabil, aber nicht vollständig getestet 2zslduqvopaxinya2lamgrrcpjqdwkq Translations:Tool status/8/de 1198 1607287 5386827 2022-07-28T19:17:26Z ThisCarthing 17456337 Created page with "im Frühstadium der Entwicklung, könnte sich erheblich ändern" wikitext text/x-wiki im Frühstadium der Entwicklung, könnte sich erheblich ändern k39c8fes09igvko6o9eftl71e9l9pd9 5386829 5386827 2022-07-28T19:17:30Z ThisCarthing 17456337 wikitext text/x-wiki im Frühstadium der Entwicklung, könnte sich erheblich ändern. s5mw7crgerwgqgt6hzmk0atj3bwiqzf Translations:Tool status/10/de 1198 1607288 5386831 2022-07-28T19:18:19Z ThisCarthing 17456337 Created page with "defekt - verwende dieses Werkzeug nicht" wikitext text/x-wiki defekt - verwende dieses Werkzeug nicht iksd9204ipn2cd4pgibqboh0a76os1s Translations:Tool status/12/de 1198 1607289 5386833 2022-07-28T19:18:22Z ThisCarthing 17456337 Created page with "Voreinstellung" wikitext text/x-wiki Voreinstellung rwlnh7ccyf0q4rys33ird56jv3cr2sr Translations:Tool status/14/de 1198 1607290 5386835 2022-07-28T19:18:25Z ThisCarthing 17456337 Created page with "galt zuvor als stabil, wird nicht mehr gewartet" wikitext text/x-wiki galt zuvor als stabil, wird nicht mehr gewartet esancq0ohb60n0gvd240zsnzelfww1y Translations:Tool status/15/de 1198 1607291 5386837 2022-07-28T19:18:40Z ThisCarthing 17456337 Created page with "Weitere Einzelheiten sind in den [[$1|Werkzeugs-Informationsboxen-Parametern]] zu finden." wikitext text/x-wiki Weitere Einzelheiten sind in den [[$1|Werkzeugs-Informationsboxen-Parametern]] zu finden. qyw9s478rasae8je52f9nwr81n776yq Translations:Tool status/16/de 1198 1607292 5386839 2022-07-28T19:18:48Z ThisCarthing 17456337 Created page with "== Farbschemata des Freigabestatus der Werkzeuge ==" wikitext text/x-wiki == Farbschemata des Freigabestatus der Werkzeuge == 2va9upagx0fbaorrla8evby3uls9uyu Translations:Tool status/17/de 1198 1607293 5386841 2022-07-28T19:18:50Z ThisCarthing 17456337 Created page with "Layout-Test" wikitext text/x-wiki Layout-Test 6v742uzy5qr52mego7w7o2xvfnm6ddp Translations:Extension:GWToolset/22/de 1198 1607294 5386845 2022-07-28T19:22:10Z ThisCarthing 17456337 Created page with "Funktionsanfragen" wikitext text/x-wiki Funktionsanfragen 7vpds912gbymo0se8nlpduxaavfbv7q Translations:Extension:GWToolset/13/de 1198 1607295 5386846 2022-07-28T19:22:12Z ThisCarthing 17456337 Created page with "== Anmerkungen und Referenzen ==" wikitext text/x-wiki == Anmerkungen und Referenzen == 7nm9jxgopft0fy0mfbhhy73537qbchb Translations:Extension:NoTitle/12/de 1198 1607296 5386848 2022-07-28T19:22:37Z ThisCarthing 17456337 Created page with "$1 funktioniert für jede Seite." wikitext text/x-wiki $1 funktioniert für jede Seite. ggqdciro9uq48vqoxps23tb0yluwyoi Translations:Extension:TimedMediaHandler/5/de 1198 1607297 5386850 2022-07-28T19:23:26Z ThisCarthing 17456337 Created page with "== Funktionsübersicht ==" wikitext text/x-wiki == Funktionsübersicht == 0cck6eea5bp5giuwicp97hi9ztdb9zg Translations:Extension:TimedMediaHandler/104/de 1198 1607298 5386852 2022-07-28T19:23:56Z ThisCarthing 17456337 Created page with "Bitrate" wikitext text/x-wiki Bitrate og9jxgbkr1xsntzhiyh8dgdeylytvzi Translations:Extension:TimedMediaHandler/30/de 1198 1607299 5386854 2022-07-28T19:24:04Z ThisCarthing 17456337 Created page with "'''Bitrate'''" wikitext text/x-wiki '''Bitrate''' n93a9j8s7eyc3d39ro6qc7vdn1jtfme Translations:Help:Extension:Translate/30/lt 1198 1607300 5386856 2022-07-28T19:25:12Z Pavel1513 17650776 Created page with "Pakeitimų sekimas galimas ir išoriškai sekamiems failams, nes plėtinio viduje naudojama lokalizacijos failų išsaugotą išvestinę versiją, kur saugomi pirminis tekstas ir jo vertimai, vietoje to, kad panaudoti juos tiesiogiai originaliu formatu." wikitext text/x-wiki Pakeitimų sekimas galimas ir išoriškai sekamiems failams, nes plėtinio viduje naudojama lokalizacijos failų išsaugotą išvestinę versiją, kur saugomi pirminis tekstas ir jo vertimai, vietoje to, kad panaudoti juos tiesiogiai originaliu formatu. m54awwi2ua2gstzag2kww4cdgv9t4kw 5386858 5386856 2022-07-28T19:26:39Z Pavel1513 17650776 wikitext text/x-wiki Pakeitimų sekimas galimas ir išoriškai sekamiems failams, nes plėtinio viduje naudojama lokalizacijos failų išsaugotą išvestinę versiją, kur saugomi pirminis tekstas ir jo vertimai, vietoje jų tiesioginio naudojimo originaliu formatu. m7cmli99rn8wgs6l2lhpp1ms3p23asr Translations:Extension:LoginNotify/22/de 1198 1607301 5386860 2022-07-28T19:29:08Z ThisCarthing 17456337 Created page with "Ablauf des Cookies." wikitext text/x-wiki Ablauf des Cookies. 3t11jko5ioyfsmn4dwgfm9cyq90lii0 Translations:Extension:EasyTimeline/installation/5/de 1198 1607302 5386862 2022-07-28T19:31:19Z ThisCarthing 17456337 Created page with "== Ploticus herunterladen ==" wikitext text/x-wiki == Ploticus herunterladen == fh2hlatvz6974rgseuop7splhxuidyv Translations:Extension:EasyTimeline/installation/74/de 1198 1607303 5386864 2022-07-28T19:31:27Z ThisCarthing 17456337 Created page with "=== Schriftart ===" wikitext text/x-wiki === Schriftart === 8picxa7ib4zm81wtf4t8daxpujwh19r Translations:Extension:EasyTimeline/installation/43/de 1198 1607304 5386866 2022-07-28T19:32:29Z ThisCarthing 17456337 Created page with "== Bekannte Probleme ==" wikitext text/x-wiki == Bekannte Probleme == 2x094hu2zdsn581ylxt71dy03w78nqy Translations:Extension:Chartie/77/de 1198 1607305 5386869 2022-07-28T19:32:50Z ThisCarthing 17456337 Created page with "== Installieren ==" wikitext text/x-wiki == Installieren == 8rzozju2lk3uflzcosn4zme1db26r12 Translations:Extension:Chartie/90/de 1198 1607306 5386871 2022-07-28T19:33:02Z ThisCarthing 17456337 Created page with "Ändere den $1-Parameter:" wikitext text/x-wiki Ändere den $1-Parameter: 5zdnnrq8do47r1qzjmhrc1mk9ppz91r Translations:Extension:SupybotNotify/13/de 1198 1607307 5386873 2022-07-28T19:33:10Z ThisCarthing 17456337 Created page with "==Code==" wikitext text/x-wiki ==Code== l7jxcgaf2fzyzsw2i5affsp2jls1hgf Translations:Extension:ViewTable/5/de 1198 1607308 5386876 2022-07-28T19:33:48Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki Erweiterung herunterladen cjd1175xvnphdt3qrrot9edlq3tnmtu Translations:Extension:DebugMode/1/de 1198 1607309 5386878 2022-07-28T19:34:17Z ThisCarthing 17456337 Created page with "Setzt das Wiki im Debugmodus" wikitext text/x-wiki Setzt das Wiki im Debugmodus ou6m6bvu9onmlg2szl56681g0y3tj8v Translations:Extension:HtmlFromFile/9/de 1198 1607310 5386880 2022-07-28T19:34:24Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki Erweiterung herunterladen cjd1175xvnphdt3qrrot9edlq3tnmtu Translations:Extension:OfflineExtension/3/de 1198 1607311 5386882 2022-07-28T19:35:08Z ThisCarthing 17456337 Created page with "== Funktionen ==" wikitext text/x-wiki == Funktionen == 7eyd1ycfv7pqndvm4a8lnhu27e69gmx Translations:Extension:OfflineExtension/13/de 1198 1607312 5386884 2022-07-28T19:35:14Z ThisCarthing 17456337 Created page with "== Bekannte Probleme ==" wikitext text/x-wiki == Bekannte Probleme == 2x094hu2zdsn581ylxt71dy03w78nqy Translations:Extension:VectorUp/7/de 1198 1607313 5386886 2022-07-28T19:35:21Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki Erweiterung herunterladen cjd1175xvnphdt3qrrot9edlq3tnmtu Translations:Extension:VectorUp/10/de 1198 1607314 5386888 2022-07-28T19:37:12Z ThisCarthing 17456337 Created page with "Du bist bereits fertig! Genieße den Skin!" wikitext text/x-wiki Du bist bereits fertig! Genieße den Skin! otk8e0sovps7dbeoe061i9btishqwuw Translations:Extension:PoolCounter/12/de 1198 1607315 5386890 2022-07-28T19:37:52Z ThisCarthing 17456337 Created page with "Ein Array von Server-IP-Adressen." wikitext text/x-wiki Ein Array von Server-IP-Adressen. dp9qdowh9p36e1rib1iz1ki5e3daqqf Translations:Extension:Graph/Demo/11/de 1198 1607316 5386892 2022-07-28T19:39:09Z ThisCarthing 17456337 Created page with "== Mit der RESTBase-API ==" wikitext text/x-wiki == Mit der RESTBase-API == mlmqbku8das9hi1sb0tfehoijaojfth Translations:Extension:ManageWiki/34/de 1198 1607317 5386894 2022-07-28T19:40:15Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki Erweiterung herunterladen cjd1175xvnphdt3qrrot9edlq3tnmtu Translations:Extension:ManageWiki/35/de 1198 1607318 5386896 2022-07-28T19:40:39Z ThisCarthing 17456337 Created page with "Lade zuerst die separate $1-Erweiterung herunter und installiere sie." wikitext text/x-wiki Lade zuerst die separate $1-Erweiterung herunter und installiere sie. mr96thxpc8wyr8tgcdlkvnwfu213kix Translations:Extension:ManageWiki/23/de 1198 1607319 5386898 2022-07-28T19:41:30Z ThisCarthing 17456337 Created page with "ManageWikis Version von $wgAddGroups." wikitext text/x-wiki ManageWikis Version von $wgAddGroups. poipsy7kgf9s2miitqksg3pdd24ml0s Translations:Extension:ManageWiki/25/de 1198 1607320 5386900 2022-07-28T19:41:51Z ThisCarthing 17456337 Created page with "ManageWikis Version von $wgGroupPermissions." wikitext text/x-wiki ManageWikis Version von $wgGroupPermissions. sa1vd6jl1uflrragln7dz6xtz3a84xq Translations:Extension:ManageWiki/31/de 1198 1607321 5386902 2022-07-28T19:42:08Z ThisCarthing 17456337 Created page with "False deaktiviert diese Funktion." wikitext text/x-wiki False deaktiviert diese Funktion. eheak2uhdoil3iq1etrg511f2ututde Translations:Extension:ManageWiki/24/de 1198 1607322 5386904 2022-07-28T19:42:16Z ThisCarthing 17456337 Created page with "ManageWikis Version von $wgRemoveGroups." wikitext text/x-wiki ManageWikis Version von $wgRemoveGroups. d7tqd5p6djvqnj0qnupqsa7ye3g6f23 Translations:Extension:Parser function extensions/10/de 1198 1607323 5386906 2022-07-28T19:42:25Z ThisCarthing 17456337 Created page with "Erweiterung" wikitext text/x-wiki Erweiterung mfiydi0yb62jxe0hmkps7emryr9p3vg Translations:Extension:Parser function extensions/11/de 1198 1607324 5386908 2022-07-28T19:42:28Z ThisCarthing 17456337 Created page with "Funktion" wikitext text/x-wiki Funktion 8q8khvlp2atmeazfsck98qf7fracf1b Translations:Extension:Parser function extensions/15/de 1198 1607325 5386909 2022-07-28T19:42:31Z ThisCarthing 17456337 Created page with "MediaWiki-Version" wikitext text/x-wiki MediaWiki-Version n7hvm23bqouuser5duyioho7ip4yshq Translations:Extension:3DAlloy/58/de 1198 1607326 5386912 2022-07-28T19:42:42Z ThisCarthing 17456337 Created page with "Ändere den $1-Parameter:" wikitext text/x-wiki Ändere den $1-Parameter: 5zdnnrq8do47r1qzjmhrc1mk9ppz91r Translations:Extension:EasyTimeline/121/de 1198 1607327 5386914 2022-07-28T19:43:16Z ThisCarthing 17456337 Created page with "Siehe unten" wikitext text/x-wiki Siehe unten my0vxolnq46bk07mndt4pgjrg7xmy22 Translations:Extension:EasyTimeline/81/de 1198 1607328 5386916 2022-07-28T19:43:27Z ThisCarthing 17456337 Created page with "Tipps" wikitext text/x-wiki Tipps 7sf74ysabhyaz86bbpg9ql6kd1zklhz 5386918 5386916 2022-07-28T19:43:31Z ThisCarthing 17456337 wikitext text/x-wiki Tipps: pw8mcspqdcelhleb5ib6fmrz2uaugce Translations:Extension:EasyTimeline/87/de 1198 1607329 5386920 2022-07-28T19:43:44Z ThisCarthing 17456337 Created page with "Siehe [[$1|/installation]]" wikitext text/x-wiki Siehe [[$1|/installation]] s92wpvh0x7i4e3nu3526r1pug26q3n0 Translations:Extension:SendGrid/14/de 1198 1607330 5386922 2022-07-28T19:44:01Z ThisCarthing 17456337 Created page with "== Teste deine Einstellungen ==" wikitext text/x-wiki == Teste deine Einstellungen == ddzgxb8nthk68djpbv62k9la5w8ucb5 Translations:Extension:RottenLinks/26/de 1198 1607331 5386924 2022-07-28T19:44:18Z ThisCarthing 17456337 Created page with "Beispiel:" wikitext text/x-wiki Beispiel: 2icomidw13r503tgxp5h8heg0g1y47h Translations:Extension:Scribunto/133/de 1198 1607332 5386926 2022-07-28T19:44:56Z ThisCarthing 17456337 Created page with "Versuche, $1 zu $2 zu ändern" wikitext text/x-wiki Versuche, $1 zu $2 zu ändern cszo6gmuq6uueil55uiv6xw93j7v5c5 Translations:Extension:Scribunto/21/de 1198 1607333 5386927 2022-07-28T19:45:15Z ThisCarthing 17456337 Created page with "== Andere Seiten ==" wikitext text/x-wiki == Andere Seiten == chxoskkqu9l16d0klkuy9e20dycg2z6 Translations:Extension:SpamBlacklist/36/de 1198 1607334 5386929 2022-07-28T19:45:37Z ThisCarthing 17456337 Created page with "=== Leistung ===" wikitext text/x-wiki === Leistung === ga6mira61vrfs3hxqbulhk3n353xza6 Translations:Extension:RegexFunctions/2/de 1198 1607335 5386931 2022-07-28T19:45:47Z ThisCarthing 17456337 Created page with "Verwendung" wikitext text/x-wiki Verwendung 0luojxdvye0o4z8wj8bey6o6sv5yhgq Translations:Extension:RegexFunctions/7/de 1198 1607336 5386933 2022-07-28T19:45:53Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki Notwendig led6ypabr4c3z85pzbl7j5tos57b5kz Translations:Extension:RegexFunctions/9/de 1198 1607337 5386935 2022-07-28T19:45:57Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki Notwendig led6ypabr4c3z85pzbl7j5tos57b5kz Translations:Extension:RegexFunctions/18/de 1198 1607338 5386937 2022-07-28T19:46:02Z ThisCarthing 17456337 Created page with "optional" wikitext text/x-wiki optional 8hj2cm6kxgkn4ac7h6o4azdltflwm6p Translations:Extension:RegexFunctions/15/de 1198 1607339 5386939 2022-07-28T19:46:07Z ThisCarthing 17456337 Created page with "optional" wikitext text/x-wiki optional 8hj2cm6kxgkn4ac7h6o4azdltflwm6p Translations:Extension:RegexFunctions/21/de 1198 1607340 5386941 2022-07-28T19:46:12Z ThisCarthing 17456337 Created page with "notwendig" wikitext text/x-wiki notwendig loubw1u7l0c2r1l9b4lquxjobif08dp Translations:Extension:RegexFunctions/23/de 1198 1607341 5386943 2022-07-28T19:46:18Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki Notwendig led6ypabr4c3z85pzbl7j5tos57b5kz Translations:Extension:RegexFunctions/25/de 1198 1607342 5386945 2022-07-28T19:46:22Z ThisCarthing 17456337 Created page with "optional" wikitext text/x-wiki optional 8hj2cm6kxgkn4ac7h6o4azdltflwm6p Translations:Extension:RegexFunctions/27/de 1198 1607343 5386947 2022-07-28T19:46:30Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki Notwendig led6ypabr4c3z85pzbl7j5tos57b5kz Translations:Extension:RegexFunctions/29/de 1198 1607344 5386949 2022-07-28T19:46:34Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki Notwendig led6ypabr4c3z85pzbl7j5tos57b5kz Translations:Extension:RegexFunctions/31/de 1198 1607345 5386951 2022-07-28T19:46:38Z ThisCarthing 17456337 Created page with "Notwendig" wikitext text/x-wiki Notwendig led6ypabr4c3z85pzbl7j5tos57b5kz Translations:Extension:SocialProfile/30/de 1198 1607346 5386953 2022-07-28T19:46:56Z ThisCarthing 17456337 Created page with "Mit $1" wikitext text/x-wiki Mit $1 63zvr9gcqaaq7n21g0e609dzalcxw56 Translations:Extension:CLDR/17/de 1198 1607347 5386955 2022-07-28T19:47:15Z ThisCarthing 17456337 Created page with "=== Landesnamen ===" wikitext text/x-wiki === Landesnamen === p73d1o5ezb69vykzrj38ea3fifrrz9f Translations:Extension:PollNY/19/de 1198 1607348 5386957 2022-07-28T19:47:59Z ThisCarthing 17456337 Created page with "Benötigt die $1-Erweiterung." wikitext text/x-wiki Benötigt die $1-Erweiterung. 74vekoifzs6f3wch78ht882jnd1vpvo Translations:Extension:VoteNY/17/de 1198 1607349 5386959 2022-07-28T19:48:07Z ThisCarthing 17456337 Created page with "=== Spezialseite ===" wikitext text/x-wiki === Spezialseite === hge1rpwkr8vp46tlu90l8r54zqjnnyl Translations:Extension:Echo/77/de 1198 1607350 5386961 2022-07-28T19:48:38Z ThisCarthing 17456337 Created page with "koniguriere $1" wikitext text/x-wiki koniguriere $1 o77z0sz6dmoox5xtif4ayiy3uqby8om Translations:Extension:Echo/72/de 1198 1607351 5386963 2022-07-28T19:48:58Z ThisCarthing 17456337 Created page with "Setze auf $1, um zu deaktivieren." wikitext text/x-wiki Setze auf $1, um zu deaktivieren. kdwsoeyuge73obrg81w72ey1htxrpvg Translations:Extension:Echo/114/de 1198 1607352 5386965 2022-07-28T19:49:03Z ThisCarthing 17456337 Created page with "Setze auf $1, um zu deaktivieren." wikitext text/x-wiki Setze auf $1, um zu deaktivieren. kdwsoeyuge73obrg81w72ey1htxrpvg Translations:Extension:Echo/80/de 1198 1607353 5386967 2022-07-28T19:49:15Z ThisCarthing 17456337 Created page with "Für dies, verwende $1" wikitext text/x-wiki Für dies, verwende $1 spx05br4lel8aiz6mgy81kn40cgwjmv Translations:Extension:Echo/83/de 1198 1607354 5386969 2022-07-28T19:49:30Z ThisCarthing 17456337 Created page with "Alle Parameter sind optional:" wikitext text/x-wiki Alle Parameter sind optional: 28bwhm9ay7f5ba9rzs5c3l37v60vn63 Translations:Extension:TemplateData/31/de 1198 1607355 5386971 2022-07-28T19:49:41Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/32/de 1198 1607356 5386973 2022-07-28T19:49:44Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki Typ rryt6j2q6u744l6gb8q3cm2po3srisr Translations:Extension:TemplateData/33/de 1198 1607357 5386975 2022-07-28T19:49:46Z ThisCarthing 17456337 Created page with "Standard" wikitext text/x-wiki Standard 5dci1ri24gv1fapre2hrww7uvh9x7zq Translations:Extension:TemplateData/122/de 1198 1607358 5386977 2022-07-28T19:49:52Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki Zeichenkette c47tftmh0r31y0s78bzpnf8knbm9b71 Translations:Extension:TemplateData/125/de 1198 1607359 5386979 2022-07-28T19:49:57Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki Zeichenkette c47tftmh0r31y0s78bzpnf8knbm9b71 Translations:Extension:TemplateData/128/de 1198 1607360 5386981 2022-07-28T19:50:12Z ThisCarthing 17456337 Created page with "Art des Parameter" wikitext text/x-wiki Art des Parameter tbe8p4ucj74qea5am6um67gr900f8jf 5386983 5386981 2022-07-28T19:50:20Z ThisCarthing 17456337 wikitext text/x-wiki Art von Parameter i6w6tpryn3stnzbadg3tu6v15k66sds Translations:Extension:TemplateData/157/de 1198 1607361 5386985 2022-07-28T19:50:33Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/41/de 1198 1607362 5386987 2022-07-28T19:50:38Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/42/de 1198 1607363 5386989 2022-07-28T19:50:42Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki Typ rryt6j2q6u744l6gb8q3cm2po3srisr Translations:Extension:TemplateData/43/de 1198 1607364 5386991 2022-07-28T19:50:46Z ThisCarthing 17456337 Created page with "Standard" wikitext text/x-wiki Standard 5dci1ri24gv1fapre2hrww7uvh9x7zq Translations:Extension:TemplateData/80/de 1198 1607365 5386993 2022-07-28T19:50:53Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/81/de 1198 1607366 5386995 2022-07-28T19:50:57Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki Typ rryt6j2q6u744l6gb8q3cm2po3srisr Translations:Extension:TemplateData/84/de 1198 1607367 5386997 2022-07-28T19:51:01Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki Zeichenkette c47tftmh0r31y0s78bzpnf8knbm9b71 Translations:Extension:TemplateData/87/de 1198 1607368 5386999 2022-07-28T19:51:06Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/88/de 1198 1607369 5387001 2022-07-28T19:51:09Z ThisCarthing 17456337 Created page with "Wert" wikitext text/x-wiki Wert id9h31nlb1vygjjjmgeumx8s93n5tgj Translations:Extension:TemplateData/187/de 1198 1607370 5387003 2022-07-28T19:51:28Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/188/de 1198 1607371 5387005 2022-07-28T19:51:32Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki Typ rryt6j2q6u744l6gb8q3cm2po3srisr Translations:Extension:TemplateData/194/de 1198 1607372 5387007 2022-07-28T19:51:39Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/195/de 1198 1607373 5387008 2022-07-28T19:51:42Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki Typ rryt6j2q6u744l6gb8q3cm2po3srisr Translations:Extension:TemplateData/203/de 1198 1607374 5387010 2022-07-28T19:51:48Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/204/de 1198 1607375 5387012 2022-07-28T19:51:52Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki Typ rryt6j2q6u744l6gb8q3cm2po3srisr Translations:Extension:TemplateData/207/de 1198 1607376 5387013 2022-07-28T19:51:55Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki Zeichenkette c47tftmh0r31y0s78bzpnf8knbm9b71 Translations:Extension:TemplateData/221/de 1198 1607377 5387015 2022-07-28T19:52:01Z ThisCarthing 17456337 Created page with "Schlüssel" wikitext text/x-wiki Schlüssel 34mgfv6lbrl7iu20dvttfikg5vu0ibq Translations:Extension:TemplateData/222/de 1198 1607378 5387017 2022-07-28T19:52:04Z ThisCarthing 17456337 Created page with "Typ" wikitext text/x-wiki Typ rryt6j2q6u744l6gb8q3cm2po3srisr Translations:Extension:TemplateData/227/de 1198 1607379 5387019 2022-07-28T19:52:09Z ThisCarthing 17456337 Created page with "oder" wikitext text/x-wiki oder 8tt9ia9vyn0318y9ovaeq6438k2s4hs Translations:Extension:TemplateData/234/de 1198 1607380 5387021 2022-07-28T19:52:15Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki Zeichenkette c47tftmh0r31y0s78bzpnf8knbm9b71 Translations:Extension:TemplateData/236/de 1198 1607381 5387023 2022-07-28T19:52:19Z ThisCarthing 17456337 Created page with "Zeichenkette" wikitext text/x-wiki Zeichenkette c47tftmh0r31y0s78bzpnf8knbm9b71 Translations:Extension:TemplateData/21/de 1198 1607382 5387025 2022-07-28T19:52:25Z ThisCarthing 17456337 Created page with "Variable" wikitext text/x-wiki Variable 30s7g709s5nrg5etugkyqe36rb4kbbw Translations:Extension:TemplateData/22/de 1198 1607383 5387027 2022-07-28T19:52:28Z ThisCarthing 17456337 Created page with "Standard" wikitext text/x-wiki Standard 5dci1ri24gv1fapre2hrww7uvh9x7zq Translations:Extension:Tab Override/Page display title/de 1198 1607384 5387035 2022-07-28T19:56:03Z ThisCarthing 17456337 Created page with "Erweiterung:Tab Override" wikitext text/x-wiki Erweiterung:Tab Override iexngyjlkgdk3q8ljypsemcm6zj0bk9 Translations:Extension:Tab Override/2/de 1198 1607385 5387036 2022-07-28T19:56:34Z ThisCarthing 17456337 Created page with "Erweiterung herunterladen" wikitext text/x-wiki Erweiterung herunterladen cjd1175xvnphdt3qrrot9edlq3tnmtu Translations:Extension:Tab Override/3/de 1198 1607386 5387038 2022-07-28T19:56:39Z ThisCarthing 17456337 Created page with "== Was kann diese Erweiterung machen? ==" wikitext text/x-wiki == Was kann diese Erweiterung machen? == cp9kdc1upl3bbnimf1cc1d4vll9sy2w Translations:Extension:Tab Override/8/de 1198 1607387 5387040 2022-07-28T19:57:07Z ThisCarthing 17456337 Created page with "Keine Konfiguration notwendig." wikitext text/x-wiki Keine Konfiguration notwendig. 0ixshugji11cyncbxzuuh3qkvo0bljj Translations:Extension:UnicodeConverter/1/de 1198 1607388 5387042 2022-07-28T20:00:34Z ThisCarthing 17456337 Created page with "Beispielspezialseite" wikitext text/x-wiki Beispielspezialseite 9z5q8lxlz1pt2mzk777b75alvozvpaf Translations:Extension:UnicodeConverter/2/de 1198 1607389 5387044 2022-07-28T20:00:55Z ThisCarthing 17456337 Created page with "Dies war die erste Spezialseitenerweiterung." wikitext text/x-wiki Dies war die erste Spezialseitenerweiterung. m435b0ck95at5pqt11qojck0pr4mfy1 Translations:Manual:Special pages/283/de 1198 1607390 5387046 2022-07-28T20:01:35Z ThisCarthing 17456337 Created page with "* Lokalisierungsdatei" wikitext text/x-wiki * Lokalisierungsdatei ps36vzjxm2cz9hflhiq6z4jp35fkpdo Translations:Manual:Special pages/181/de 1198 1607391 5387048 2022-07-28T20:01:58Z ThisCarthing 17456337 Created page with "Ein Beispiel:" wikitext text/x-wiki Ein Beispiel: lwlufiffz2nadtp20jf600ln2pm8kyk Topic:X06dzw1ghys3dge4 2600 1607394 5387052 2022-07-28T20:04:15Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x06dzw1ghys3dge4"} es4d5az9ah6xummc6s1qic40666hshb Translations:Manual:Special pages/256/de 1198 1607395 5387053 2022-07-28T20:04:23Z ThisCarthing 17456337 Created page with "Siehe $1 für die Vorgehensweise." wikitext text/x-wiki Siehe $1 für die Vorgehensweise. gmetnsbqh0l1mf7umvpiln9hted9ae0 Translations:Extension:UserFunctions/45/de 1198 1607396 5387056 2022-07-28T20:07:16Z ThisCarthing 17456337 Created page with "Algorithmus" wikitext text/x-wiki Algorithmus 26z69em4qb55cmsdsm1xthtd0gamq97 Translations:Extension:UserExport/4/de 1198 1607397 5387058 2022-07-28T20:07:31Z ThisCarthing 17456337 Created page with "Benutzerrecht" wikitext text/x-wiki Benutzerrecht 4cphxnt7iiigll40rph55xhjqrlxyo0 Translations:Extension:UserManager/2/de 1198 1607398 5387060 2022-07-28T20:08:24Z ThisCarthing 17456337 Created page with "== Verwendung / Funktionen ==" wikitext text/x-wiki == Verwendung / Funktionen == fyt4x9szogmpwxugl1ro2zzla0iruac Translations:Extension:UserThrottle/2/de 1198 1607399 5387062 2022-07-28T20:09:16Z ThisCarthing 17456337 Created page with "== Was diese Erweiterung macht ==" wikitext text/x-wiki == Was diese Erweiterung macht == k2zypk5rku0jcchd5ahz11tto8p9der Translations:Extension:UserThrottle/11/de 1198 1607400 5387064 2022-07-28T20:09:42Z ThisCarthing 17456337 Created page with "10 Registrierungen in fünf Minuten" wikitext text/x-wiki 10 Registrierungen in fünf Minuten 8oshio2as1qdowyiwdr0lkihtu29233 Translations:Extension:UserThrottle/6/de 1198 1607401 5387066 2022-07-28T20:09:56Z ThisCarthing 17456337 Created page with "Um diese Erweiterung zu installieren, füge folgendes zu $LocalSettings hinzu:" wikitext text/x-wiki Um diese Erweiterung zu installieren, füge folgendes zu $LocalSettings hinzu: eenzk7zehd1gd9ccxaifwn3qnkp5oj2 Translations:Extension:UserWelcome/1/de 1198 1607402 5387068 2022-07-28T20:10:18Z ThisCarthing 17456337 Created page with "Was auch immer SocialProfile benötigt" wikitext text/x-wiki Was auch immer SocialProfile benötigt ami5koamknvzncaex2f0qk0uk6m6fqn Translations:Extension:UserWelcome/2/de 1198 1607403 5387070 2022-07-28T20:10:26Z ThisCarthing 17456337 Created page with "Verfügbar als Teil von $1" wikitext text/x-wiki Verfügbar als Teil von $1 9q3s7wzfwb4xztlf9t71l5vp8qjw8v3 Translations:Extension:Wikibase Client/Lua/1/de 1198 1607404 5387072 2022-07-28T20:12:15Z ThisCarthing 17456337 Created page with "== Weiterführende Lektüre ==" wikitext text/x-wiki == Weiterführende Lektüre == n6ewbcpk9vfdqqgouuoqi8o83uc09k9 Extension:Wikibase Client/Lua/de 102 1607405 5387073 2022-07-28T20:12:16Z ThisCarthing 17456337 Created page with "== Weiterführende Lektüre ==" wikitext text/x-wiki <languages/> {{Ambox | type = content | text = Documentation can now be found at [https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_lua.html doc.wikimedia.org], automatically generated from <code>docs/topics/lua.md</code> in [[Wikibase]]. }} {{Notice|1=<nowiki/> ; Notes * [[d:Special:MyLanguage/Wikidata:Lexicographical data|Lexeme (WD LGD)]] is now supported. See [https://doc.wikimedia.org/WikibaseLexeme/master/php/md_docs_topics_lua.html doc.wikimedia.org] and [[phab:T235901]].<!-- Need [[Extension:WikibaseLexeme/Lua]] --> * [[c:Special:MyLanguage/Commons:Structured data|MediaInfo (SDC)]] is now supported. See [[Extension:WikibaseMediaInfo/Lua]] and [[c:Commons:Structured data/Lua|Commons:Structured data/Lua]]. }} == Weiterführende Lektüre == * {{ll|Manual:Coding conventions/Lua}} * {{ll|Extension:Scribunto/Lua reference manual}} * {{ll|Wikibase/DataModel/JSON}} * Wikimedia Gerrit mediawiki-extensions-Wikibase (master) source code ** [[git:mediawiki/extensions/Wikibase/+/master/docs/topics/lua.md|/docs/topics/lua.md]] ** [[git:mediawiki/extensions/Wikibase/+/master/client/includes/DataAccess/Scribunto/mw.wikibase.lua|/client/includes/DataAccess/Scribunto/mw.wikibase.lua]] ** [[git:mediawiki/extensions/Wikibase/+/master/client/includes/DataAccess/Scribunto/mw.wikibase.entity.lua|/client/includes/DataAccess/Scribunto/mw.wikibase.entity.lua]] * Wikimedia Phabricator Diffusion extension-Wikibase (master) source code mirror ** [[phab:diffusion/EWBA/browse/master/docs/topics/lua.md|/docs/topics/lua.md]] ** [[phab:diffusion/EWBA/browse/master/client/includes/DataAccess/Scribunto/mw.wikibase.lua|/client/includes/DataAccess/Scribunto/mw.wikibase.lua]] ** [[phab:diffusion/EWBA/browse/master/client/includes/DataAccess/Scribunto/mw.wikibase.entity.lua|/client/includes/DataAccess/Scribunto/mw.wikibase.entity.lua]] * Wikimedia GitHub mediawiki-extensions-Wikibase (master) source code mirror ** [https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/docs/topics/lua.md /docs/topics/lua.md] ** [https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/client/includes/DataAccess/Scribunto/mw.wikibase.lua /client/includes/DataAccess/Scribunto/mw.wikibase.lua] ** [https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/client/includes/DataAccess/Scribunto/mw.wikibase.entity.lua /client/includes/DataAccess/Scribunto/mw.wikibase.entity.lua] [[Category:Wikibase{{#translation:}}]] [[Category:Lua{{#translation:}}]] i0lk95pbj4agvuqsqgedzf82jnmvvms Translations:Extension:Wikibase Client/Lua/Page display title/de 1198 1607406 5387074 2022-07-28T20:12:23Z ThisCarthing 17456337 Created page with "Erweiterung:Wikibase Client/Lua" wikitext text/x-wiki Erweiterung:Wikibase Client/Lua pxg18ua3xpugb5jcy0m7a09g2af0hq4 Translations:Extension:WikiHiero/28/de 1198 1607407 5387075 2022-07-28T20:13:55Z ThisCarthing 17456337 Created page with "WikiHieros Syntax" wikitext text/x-wiki WikiHieros Syntax 2grunvkmikgsajvee3cr9m5572tdmzf Translations:Extension:Wikispeech/Speechoid on Cloud VPS/Page display title/de 1198 1607408 5387077 2022-07-28T20:17:01Z ThisCarthing 17456337 Created page with "Erweiterung:Wikispeech/Speechoid auf Cloud VPS" wikitext text/x-wiki Erweiterung:Wikispeech/Speechoid auf Cloud VPS lu48i1qld2ujfckih41bdn97zgaycfn Extension:Wikispeech/Speechoid on Cloud VPS/de 102 1607409 5387078 2022-07-28T20:17:01Z ThisCarthing 17456337 Created page with "Erweiterung:Wikispeech/Speechoid auf Cloud VPS" wikitext text/x-wiki <languages/> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is a brief guide to install Speechoid on [[wikitech:Cloud VPS|Cloud VPS]]. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Follow instructions for [[wikitech:Help:Instances#Creating an instance|creating an instance]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Minimum recommended image is ''m1.medium''; Speechoid requires 15 GB of disk space and 4 GB RAM.</span><ref>http://stts-se.github.io/wikispeech/</ref> # <span lang="en" dir="ltr" class="mw-content-ltr">Add a Security Group and add a rule to it with port 10000 (the rest of the parameters can be left as default).</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Create a proxy for the instance, for port 10000.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">In your {{ll|MediaWiki}} installation, set the [[Special:MyLanguage/Manual:Configuration settings|config variable]] <code>WikispeechSpeechoidUrl</code> to the URL given to the proxy in 3 (e.g. in {{ll|Manual:LocalSettings.php|LocalSettings.php}}).</span> <div lang="en" dir="ltr" class="mw-content-ltr"> == References == </div> [[Category:Wikispeech{{#translation:}}]] 6yhk2wr5p1dlwkmpkem701gw0lg70w8 5387080 5387078 2022-07-28T20:17:10Z ThisCarthing 17456337 Created page with "== Einzelnachweise ==" wikitext text/x-wiki <languages/> <div lang="en" dir="ltr" class="mw-content-ltr"> Here is a brief guide to install Speechoid on [[wikitech:Cloud VPS|Cloud VPS]]. </div> # <span lang="en" dir="ltr" class="mw-content-ltr">Follow instructions for [[wikitech:Help:Instances#Creating an instance|creating an instance]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">Minimum recommended image is ''m1.medium''; Speechoid requires 15 GB of disk space and 4 GB RAM.</span><ref>http://stts-se.github.io/wikispeech/</ref> # <span lang="en" dir="ltr" class="mw-content-ltr">Add a Security Group and add a rule to it with port 10000 (the rest of the parameters can be left as default).</span> # <span lang="en" dir="ltr" class="mw-content-ltr">Create a proxy for the instance, for port 10000.</span> # <span lang="en" dir="ltr" class="mw-content-ltr">In your {{ll|MediaWiki}} installation, set the [[Special:MyLanguage/Manual:Configuration settings|config variable]] <code>WikispeechSpeechoidUrl</code> to the URL given to the proxy in 3 (e.g. in {{ll|Manual:LocalSettings.php|LocalSettings.php}}).</span> == Einzelnachweise == [[Category:Wikispeech{{#translation:}}]] m7vvwmewzfjiwblqiov0sdaagzrsev7 Translations:Extension:Wikispeech/Speechoid on Cloud VPS/7/de 1198 1607410 5387079 2022-07-28T20:17:09Z ThisCarthing 17456337 Created page with "== Einzelnachweise ==" wikitext text/x-wiki == Einzelnachweise == ch2237thj6o2twshf20djhp86t15qrv Translations:Documentation/Style guide/170/de 1198 1607411 5387081 2022-07-28T20:21:19Z ThisCarthing 17456337 Created page with "Freundlich" wikitext text/x-wiki Freundlich 8ecqcw9yqenelmb1aksymwrzmmsimha Translations:Documentation/Style guide/180/de 1198 1607412 5387083 2022-07-28T20:21:26Z ThisCarthing 17456337 Created page with "Positiv" wikitext text/x-wiki Positiv fs2xyl46q17m95etwipgrhqd8d40yvn Translations:Interwiki cache/Page display title/de 1198 1607413 5387088 2022-07-28T20:23:35Z ThisCarthing 17456337 Created page with "Interwiki-Cache" wikitext text/x-wiki Interwiki-Cache j011cp01kxmnhlyiqdmvxguq0qyyb1f Interwiki cache/de 0 1607414 5387089 2022-07-28T20:23:36Z ThisCarthing 17456337 Created page with "Interwiki-Cache" wikitext text/x-wiki <languages/> <span lang="en" dir="ltr" class="mw-content-ltr">MediaWiki has a database table ({{ll|Manual:Interwiki table|interwiki}} table) for [[Special:MyLanguage/Help:Links#Interwiki_links|interwiki prefixes]].</span> <span lang="en" dir="ltr" class="mw-content-ltr">This is by default used directly, but two types of [[Special:MyLanguage/Manual:Performance tuning|caching]] can be used for better performance.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> "Interwiki cache" can thus refer to two types of caching, but in Wikimedia context it usually refers to CDB caching. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Database and memcached == </div> When '''[[memcached]]''' is enabled, the interwiki prefixes of the database table will be cached too. This can be controlled using the {{ll|Manual:$wgInterwikiExpiry|$wgInterwikiExpiry}} setting. This cache can be cleared using the {{ll|Manual:clearInterwikiCache.php|clearInterwikiCache.php}} script. It removes the caching based on the prefixes found in the database table. <div lang="en" dir="ltr" class="mw-content-ltr"> == Interwiki cache == </div> The {{ll|Manual:$wgInterwikiCache|$wgInterwikiCache}} variable can be set to a custom cache that will be used ''instead,'' as a replacement for the database table. Until 2015, Wikimedia used it to configure the path to a '''[[CDB]]''' file that is loaded from disk when needed. Since 2016, it is also supported to set {{ll|Manual:$wgInterwikiCache|$wgInterwikiCache}} directly to an array. This is typically done by storing the array in a PHP file containing <syntaxhighlight lang=php inline><?php return array( .. );</syntaxhighlight> and loading it in the variable assignment with <code>require</code>. MediaWiki does not contain a script to build or update such a cache file ([[bugzilla:33395|bug 33395]]), however [[Extension:WikimediaMaintenance|WikimediaMaintenance]] contains {{ll|Manual:dumpInterwiki.php|dumpInterwiki.php}} which is a custom Wikimedia-specific scripts used for generating the Interwiki cache file for Wikimedia wikis. The {{ll|Manual:$wgInterwikiScopes|$wgInterwikiScopes}} and {{ll|Manual:$wgInterwikiFallbackSite|$wgInterwikiFallbackSite}} settings are used when reading this cache. <div lang="en" dir="ltr" class="mw-content-ltr"> === Setting this up on your own wiki === </div> See [[Interwiki cache/Setup for your own wiki]] for cheap(er) ways to do it, assuming you want interwiki links on your wiki to take readers to the Wikimedia projects, and also for a bunch on info about the interwiki cdb file innards. For the more painful but more correct approach, see below. *You will need a copy of [[phab:diffusion/EWMA|extension/WikimediaMaintenance]]; place this in the extensions directory in the root of your MediaWiki installation. *Retrieve the files [[phab:source/mediawiki-config/browse/master/dblists/all.dblist|all.dblist]], [[phab:source/mediawiki-config/browse/master/dblists/special.dblist|special.dblist]], and [[phab:source/mediawiki-config/browse/master/langlist|langlist]] and put them someplace (e.g. in a subdir in the base of your MediaWiki installation) for convenience. *Edit extension/WikimediaMaintenance/dumpInterwikis.php and change the path <code>/srv/mediawiki</code> for those three files to the path to the directory where you just put them. *From the base of your MediaWiki installation, do *:<code>echo 'print wfWikiID();' | php maintenance/eval.php</code> :Add this value to all.dblist, assuming it's not already in there. If it does not start with a known language code (e.g. it is, say, 'wikitech-mw_ instead of something nice like frwiktionary), add it also to special.dblist. You can check the language codes in the langlist file you copied over. *From the base of your MediaWiki installation, do *:<code>php extensions/WikimediaMaintenance/dumpInterwiki.php > cache/new-interwikis.php</code> *From the base of your MediaWiki installation, make a copy of any existing cache/interwiki.db file you may have and then do *:<code>cp cache/new-interwikis.php cache/interwiki.php</code> *Edit LocalSettings.php and add *:<code>$wgInterwikiCache = require "$IP/cache/interwiki.php";</code> Now shortcuts and all other iw links should work for your project. Note that if you added it to 'special.dblist', it will behave as though it is a 'wikipedia' with en as the default language. <div lang="en" dir="ltr" class="mw-content-ltr"> == Retrieving interwikis == </div> To view the interwiki prefixes, you can use the [[API]] (action=query&meta=siteinfo&siprop=interwikimap) or install the [[Extension:Interwiki|Interwiki]] extension. These return the prefixes in the database table, and since MW 1.19 these will also work correctly for CDB cached interwiki prefixes. When using memcached, they will return prefixes directly from the database. This could cause a slight difference because the database may have been modified since the last cache version, but since {{r|114912}} deleted entries are removed from the memcached cache too. [[Category:Interwiki{{#translation:}}]] amq7dho6a8g2xqwjgt8v3n83av4mmjc 5387092 5387089 2022-07-28T20:24:17Z ThisCarthing 17456337 Created page with "MediaWiki hat eine Datenbanktabelle ($1-Tabelle) für [[$2|Interwiki-Präfixe]]." wikitext text/x-wiki <languages/> MediaWiki hat eine Datenbanktabelle ({{ll|Manual:Interwiki table|interwiki}}-Tabelle) für [[Special:MyLanguage/Help:Links#Interwiki_links|Interwiki-Präfixe]]. <span lang="en" dir="ltr" class="mw-content-ltr">This is by default used directly, but two types of [[Special:MyLanguage/Manual:Performance tuning|caching]] can be used for better performance.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> "Interwiki cache" can thus refer to two types of caching, but in Wikimedia context it usually refers to CDB caching. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Database and memcached == </div> When '''[[memcached]]''' is enabled, the interwiki prefixes of the database table will be cached too. This can be controlled using the {{ll|Manual:$wgInterwikiExpiry|$wgInterwikiExpiry}} setting. This cache can be cleared using the {{ll|Manual:clearInterwikiCache.php|clearInterwikiCache.php}} script. It removes the caching based on the prefixes found in the database table. <div lang="en" dir="ltr" class="mw-content-ltr"> == Interwiki cache == </div> The {{ll|Manual:$wgInterwikiCache|$wgInterwikiCache}} variable can be set to a custom cache that will be used ''instead,'' as a replacement for the database table. Until 2015, Wikimedia used it to configure the path to a '''[[CDB]]''' file that is loaded from disk when needed. Since 2016, it is also supported to set {{ll|Manual:$wgInterwikiCache|$wgInterwikiCache}} directly to an array. This is typically done by storing the array in a PHP file containing <syntaxhighlight lang=php inline><?php return array( .. );</syntaxhighlight> and loading it in the variable assignment with <code>require</code>. MediaWiki does not contain a script to build or update such a cache file ([[bugzilla:33395|bug 33395]]), however [[Extension:WikimediaMaintenance|WikimediaMaintenance]] contains {{ll|Manual:dumpInterwiki.php|dumpInterwiki.php}} which is a custom Wikimedia-specific scripts used for generating the Interwiki cache file for Wikimedia wikis. The {{ll|Manual:$wgInterwikiScopes|$wgInterwikiScopes}} and {{ll|Manual:$wgInterwikiFallbackSite|$wgInterwikiFallbackSite}} settings are used when reading this cache. <div lang="en" dir="ltr" class="mw-content-ltr"> === Setting this up on your own wiki === </div> See [[Interwiki cache/Setup for your own wiki]] for cheap(er) ways to do it, assuming you want interwiki links on your wiki to take readers to the Wikimedia projects, and also for a bunch on info about the interwiki cdb file innards. For the more painful but more correct approach, see below. *You will need a copy of [[phab:diffusion/EWMA|extension/WikimediaMaintenance]]; place this in the extensions directory in the root of your MediaWiki installation. *Retrieve the files [[phab:source/mediawiki-config/browse/master/dblists/all.dblist|all.dblist]], [[phab:source/mediawiki-config/browse/master/dblists/special.dblist|special.dblist]], and [[phab:source/mediawiki-config/browse/master/langlist|langlist]] and put them someplace (e.g. in a subdir in the base of your MediaWiki installation) for convenience. *Edit extension/WikimediaMaintenance/dumpInterwikis.php and change the path <code>/srv/mediawiki</code> for those three files to the path to the directory where you just put them. *From the base of your MediaWiki installation, do *:<code>echo 'print wfWikiID();' | php maintenance/eval.php</code> :Add this value to all.dblist, assuming it's not already in there. If it does not start with a known language code (e.g. it is, say, 'wikitech-mw_ instead of something nice like frwiktionary), add it also to special.dblist. You can check the language codes in the langlist file you copied over. *From the base of your MediaWiki installation, do *:<code>php extensions/WikimediaMaintenance/dumpInterwiki.php > cache/new-interwikis.php</code> *From the base of your MediaWiki installation, make a copy of any existing cache/interwiki.db file you may have and then do *:<code>cp cache/new-interwikis.php cache/interwiki.php</code> *Edit LocalSettings.php and add *:<code>$wgInterwikiCache = require "$IP/cache/interwiki.php";</code> Now shortcuts and all other iw links should work for your project. Note that if you added it to 'special.dblist', it will behave as though it is a 'wikipedia' with en as the default language. <div lang="en" dir="ltr" class="mw-content-ltr"> == Retrieving interwikis == </div> To view the interwiki prefixes, you can use the [[API]] (action=query&meta=siteinfo&siprop=interwikimap) or install the [[Extension:Interwiki|Interwiki]] extension. These return the prefixes in the database table, and since MW 1.19 these will also work correctly for CDB cached interwiki prefixes. When using memcached, they will return prefixes directly from the database. This could cause a slight difference because the database may have been modified since the last cache version, but since {{r|114912}} deleted entries are removed from the memcached cache too. [[Category:Interwiki{{#translation:}}]] qxi7z21jracviytlvwv7lrljyvcxzkk 5387094 5387092 2022-07-28T20:24:28Z ThisCarthing 17456337 Created page with "== Interwiki-Cache ==" wikitext text/x-wiki <languages/> MediaWiki hat eine Datenbanktabelle ({{ll|Manual:Interwiki table|interwiki}}-Tabelle) für [[Special:MyLanguage/Help:Links#Interwiki_links|Interwiki-Präfixe]]. <span lang="en" dir="ltr" class="mw-content-ltr">This is by default used directly, but two types of [[Special:MyLanguage/Manual:Performance tuning|caching]] can be used for better performance.</span> <div lang="en" dir="ltr" class="mw-content-ltr"> "Interwiki cache" can thus refer to two types of caching, but in Wikimedia context it usually refers to CDB caching. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> == Database and memcached == </div> When '''[[memcached]]''' is enabled, the interwiki prefixes of the database table will be cached too. This can be controlled using the {{ll|Manual:$wgInterwikiExpiry|$wgInterwikiExpiry}} setting. This cache can be cleared using the {{ll|Manual:clearInterwikiCache.php|clearInterwikiCache.php}} script. It removes the caching based on the prefixes found in the database table. == Interwiki-Cache == The {{ll|Manual:$wgInterwikiCache|$wgInterwikiCache}} variable can be set to a custom cache that will be used ''instead,'' as a replacement for the database table. Until 2015, Wikimedia used it to configure the path to a '''[[CDB]]''' file that is loaded from disk when needed. Since 2016, it is also supported to set {{ll|Manual:$wgInterwikiCache|$wgInterwikiCache}} directly to an array. This is typically done by storing the array in a PHP file containing <syntaxhighlight lang=php inline><?php return array( .. );</syntaxhighlight> and loading it in the variable assignment with <code>require</code>. MediaWiki does not contain a script to build or update such a cache file ([[bugzilla:33395|bug 33395]]), however [[Extension:WikimediaMaintenance|WikimediaMaintenance]] contains {{ll|Manual:dumpInterwiki.php|dumpInterwiki.php}} which is a custom Wikimedia-specific scripts used for generating the Interwiki cache file for Wikimedia wikis. The {{ll|Manual:$wgInterwikiScopes|$wgInterwikiScopes}} and {{ll|Manual:$wgInterwikiFallbackSite|$wgInterwikiFallbackSite}} settings are used when reading this cache. <div lang="en" dir="ltr" class="mw-content-ltr"> === Setting this up on your own wiki === </div> See [[Interwiki cache/Setup for your own wiki]] for cheap(er) ways to do it, assuming you want interwiki links on your wiki to take readers to the Wikimedia projects, and also for a bunch on info about the interwiki cdb file innards. For the more painful but more correct approach, see below. *You will need a copy of [[phab:diffusion/EWMA|extension/WikimediaMaintenance]]; place this in the extensions directory in the root of your MediaWiki installation. *Retrieve the files [[phab:source/mediawiki-config/browse/master/dblists/all.dblist|all.dblist]], [[phab:source/mediawiki-config/browse/master/dblists/special.dblist|special.dblist]], and [[phab:source/mediawiki-config/browse/master/langlist|langlist]] and put them someplace (e.g. in a subdir in the base of your MediaWiki installation) for convenience. *Edit extension/WikimediaMaintenance/dumpInterwikis.php and change the path <code>/srv/mediawiki</code> for those three files to the path to the directory where you just put them. *From the base of your MediaWiki installation, do *:<code>echo 'print wfWikiID();' | php maintenance/eval.php</code> :Add this value to all.dblist, assuming it's not already in there. If it does not start with a known language code (e.g. it is, say, 'wikitech-mw_ instead of something nice like frwiktionary), add it also to special.dblist. You can check the language codes in the langlist file you copied over. *From the base of your MediaWiki installation, do *:<code>php extensions/WikimediaMaintenance/dumpInterwiki.php > cache/new-interwikis.php</code> *From the base of your MediaWiki installation, make a copy of any existing cache/interwiki.db file you may have and then do *:<code>cp cache/new-interwikis.php cache/interwiki.php</code> *Edit LocalSettings.php and add *:<code>$wgInterwikiCache = require "$IP/cache/interwiki.php";</code> Now shortcuts and all other iw links should work for your project. Note that if you added it to 'special.dblist', it will behave as though it is a 'wikipedia' with en as the default language. <div lang="en" dir="ltr" class="mw-content-ltr"> == Retrieving interwikis == </div> To view the interwiki prefixes, you can use the [[API]] (action=query&meta=siteinfo&siprop=interwikimap) or install the [[Extension:Interwiki|Interwiki]] extension. These return the prefixes in the database table, and since MW 1.19 these will also work correctly for CDB cached interwiki prefixes. When using memcached, they will return prefixes directly from the database. This could cause a slight difference because the database may have been modified since the last cache version, but since {{r|114912}} deleted entries are removed from the memcached cache too. [[Category:Interwiki{{#translation:}}]] 8p7kf5ripw5qa1h4qixxoltdtz04gme Translations:Interwiki cache/1/de 1198 1607415 5387091 2022-07-28T20:24:17Z ThisCarthing 17456337 Created page with "MediaWiki hat eine Datenbanktabelle ($1-Tabelle) für [[$2|Interwiki-Präfixe]]." wikitext text/x-wiki MediaWiki hat eine Datenbanktabelle ($1-Tabelle) für [[$2|Interwiki-Präfixe]]. cbxz6j8cahyguzphlqqfxjz5t8f7cuu Translations:Interwiki cache/5/de 1198 1607416 5387093 2022-07-28T20:24:27Z ThisCarthing 17456337 Created page with "== Interwiki-Cache ==" wikitext text/x-wiki == Interwiki-Cache == e9ewwtv06ddf0g2eg3a2s604j1y1cr6 Translations:Extension:EventLogging/64/en 1198 1607418 5387143 2022-07-28T21:07:40Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki When adding the parameter $1 to the URL, the console in the browser's devtools will show the event logging being triggered. f627fennka9uhd6hzh6ms8fpg4f7u7y Translations:Template:InstallationNav/11/ja 1198 1607419 5387167 2022-07-28T21:14:40Z Shirayuki 472859 Created page with "MediaWiki のインストール" wikitext text/x-wiki MediaWiki のインストール fex9jo62takw09dqxre09c0wbaqyex5 Translations:Template:InstallationNav/12/ja 1198 1607420 5387169 2022-07-28T21:14:45Z Shirayuki 472859 Created page with "要件" wikitext text/x-wiki 要件 c95sv1wydok91d0bd8cn1lw6yjrhf3r Translations:Template:InstallationNav/14/ja 1198 1607421 5387171 2022-07-28T21:15:37Z Shirayuki 472859 Created page with "アップロード" wikitext text/x-wiki アップロード k8nooyqyne8qc7khcxh1qbzurihpo31 Translations:Template:InstallationNav/15/ja 1198 1607422 5387173 2022-07-28T21:15:46Z Shirayuki 472859 Created page with "データベースをセットアップする" wikitext text/x-wiki データベースをセットアップする sndud96gcyrvw0uwct22yls4amdnn3o Translations:Template:InstallationNav/16/ja 1198 1607423 5387175 2022-07-28T21:15:49Z Shirayuki 472859 Created page with "インストール" wikitext text/x-wiki インストール axqesxbrlx7lpln1ggobf2xavuk5hel Translations:Template:InstallationNav/17/ja 1198 1607425 5387178 2022-07-28T21:15:56Z Shirayuki 472859 Created page with "環境設定" wikitext text/x-wiki 環境設定 nbic1r83n08ygzp7wz3sy242yzdsjmm Translations:Template:InstallationNav/18/ja 1198 1607426 5387180 2022-07-28T21:16:18Z Shirayuki 472859 Created page with "よくある質問" wikitext text/x-wiki よくある質問 0oxehpvdmxv4vil8x1ie4rxuinxfe7a Translations:Template:InstallationNav/20/en 1198 1607427 5387184 2022-07-28T21:17:24Z FuzzyBot 451990 Importing a new version from external source wikitext text/x-wiki Get help and support 52nuibm0ihzpr0zsa4ids7wp8a4568j Translations:Template:InstallationNav/20/ja 1198 1607428 5387215 2022-07-28T21:17:53Z Shirayuki 472859 Created page with "ヘルプ/サポート" wikitext text/x-wiki ヘルプ/サポート obz6qwdwpxuw7q5mecj795h9q84kspx User:Texniths/common.js 2 1607429 5387228 2022-07-28T21:27:28Z Texniths 5432743 Created page with "mw.loader.load( 'https://en.wikipedia.org/w/index.php?title=User:Volker_E._(WMF)/dark-mode.js&action=raw&ctype=text/javascript' );" javascript text/javascript mw.loader.load( 'https://en.wikipedia.org/w/index.php?title=User:Volker_E._(WMF)/dark-mode.js&action=raw&ctype=text/javascript' ); cl1skxtjfjdsomvhg1dy7fmkij1o4gk Translations:Manual:Installing MediaWiki/157/ja 1198 1607430 5387247 2022-07-28T21:33:08Z Shirayuki 472859 Created page with "== 付録 ==" wikitext text/x-wiki == 付録 == c0fmkoceheyvv7nl5jthypr3w9vjiqk Translations:Manual:Installing MediaWiki/162/ja 1198 1607431 5387251 2022-07-28T21:34:00Z Shirayuki 472859 Created page with "=== システム固有の手順 ===" wikitext text/x-wiki === システム固有の手順 === 0e2duivblr4szgs2w4ve0m7lkuvqh76 User:SPatel (WMF)/Greenhouse 2 1607432 5387254 2022-07-28T21:34:48Z SPatel (WMF) 17546935 Created page with "[[File:Greenhouse and Flower Beds by Kuroda Seiki (Kuroda Kinenkan).jpg|center|thumb|500x500px|Here we collect, water, and grow ideas.]]" wikitext text/x-wiki [[File:Greenhouse and Flower Beds by Kuroda Seiki (Kuroda Kinenkan).jpg|center|thumb|500x500px|Here we collect, water, and grow ideas.]] 8tz4btxkp41832hhieodmxv012j9mw4 5387264 5387254 2022-07-28T21:39:19Z SPatel (WMF) 17546935 Image change wikitext text/x-wiki [[File:Cluj-Napoca Botanical Garden-9964.jpg|center|thumb|500x500px|Here we collect, water, and grow ideas.]] b5yatg1477dq6wjcbxo2kfciz920plv 5387283 5387264 2022-07-28T21:55:43Z SPatel (WMF) 17546935 wikitext text/x-wiki [[File:Cluj-Napoca Botanical Garden-9964.jpg|center|thumb|500x500px|Here we collect, water, and grow ideas.]] == Seedlings == ''Ideas that are incubating'' == Sprouts == ''Ideas that are easier to imagine'' * Page preview for blue links have made navigating wiki rabbit holes a lot more effective by providing effective context switching. Could red-links benefit from a page preview too? Almost like an empty state for page preview that tells a bit about why it's red and how to contribute or add missing content? == Blooms == ''Ideas that have been imagined'' 393qd6klladlhm6x0gmumkgkfhlgnf6 Translations:Manual:$wgUpdateRowsPerJob/2/de 1198 1607433 5387265 2022-07-28T21:51:26Z Piet2609 17478837 Created page with "Zu aktualisierende Reihenanzahl pro Job" wikitext text/x-wiki Zu aktualisierende Reihenanzahl pro Job 8hy814khbbko03nwm3f7n3b4on7jwfc Translations:Manual:$wgUpdateRowsPerJob/4/de 1198 1607434 5387267 2022-07-28T21:51:40Z Piet2609 17478837 Created page with "Zu aktualisierende Reihenanzahl pro Job." wikitext text/x-wiki Zu aktualisierende Reihenanzahl pro Job. fx6t6pbh9ilpcet1gmg3ymtzbyoby0r Translations:Manual:System administration/81/tr 1198 1607435 5387270 2022-07-28T21:52:40Z Baris6161TURK 17188421 Created page with "=== E-posta bildirimleri gönderme ===" wikitext text/x-wiki === E-posta bildirimleri gönderme === 0ir78fktalrr4rs6n72bs2s1s0huuvr Translations:Manual:System administration/82/tr 1198 1607436 5387271 2022-07-28T21:52:42Z Baris6161TURK 17188421 Created page with "$1 sayfasına bakın" wikitext text/x-wiki $1 sayfasına bakın 530py4dntsws2ecm7svd212t431jdnf Translations:Manual:Installing MediaWiki/146/tr 1198 1607437 5387301 2022-07-28T22:02:03Z Baris6161TURK 17188421 Created page with "Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar." wikitext text/x-wiki Bu sayfa, MediaWiki'yi manuel olarak kurmak ve yapılandırmak için tüm adımları kapsar. c7vx504no8vptz0fb4j5ejhosfyydce Translations:Manual:Installing MediaWiki/147/tr 1198 1607438 5387307 2022-07-28T22:02:28Z Baris6161TURK 17188421 Created page with "Aşağıdaki [[$1|Ekler]] bölümü [[$2|el kuruluma daha kolay alternatifler]] sunar." wikitext text/x-wiki Aşağıdaki [[$1|Ekler]] bölümü [[$2|el kuruluma daha kolay alternatifler]] sunar. q0zswn2hvnlf6f5iyss6qzyf7nns372 Translations:Manual:Installing MediaWiki/148/tr 1198 1607439 5387309 2022-07-28T22:02:35Z Baris6161TURK 17188421 Created page with "Aşağıdaki [[$1|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar." wikitext text/x-wiki Aşağıdaki [[$1|Ekler]] bölümü ayrıca belirli sistem yapılandırmaları için kurulum notları sağlar. pj96poyevg4fqoer1mm69qy2kergy3g Translations:Manual:Installing MediaWiki/149/tr 1198 1607440 5387313 2022-07-28T22:02:46Z Baris6161TURK 17188421 Created page with "MediaWiki'yi zaten çalıştırıyorsanız, [[$1|Yükseltme kılavuzuna]] bakın." wikitext text/x-wiki MediaWiki'yi zaten çalıştırıyorsanız, [[$1|Yükseltme kılavuzuna]] bakın. fi1xowwl1wc3bxfqe07i2j43e7jzn8i Translations:Manual:Installing MediaWiki/150/tr 1198 1607441 5387315 2022-07-28T22:02:51Z Baris6161TURK 17188421 Created page with "== Kurulum gereksinimlerini kontrol edin ==" wikitext text/x-wiki == Kurulum gereksinimlerini kontrol edin == 7nyc5f6yqsmt7mqs84m23f4df305bty Translations:Manual:Installing MediaWiki/151/tr 1198 1607442 5387319 2022-07-28T22:02:58Z Baris6161TURK 17188421 Created page with "Sisteminizin [[$1|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin." wikitext text/x-wiki Sisteminizin [[$1|kurulum gereksinimlerini]] karşılayıp karşılamadığını kontrol edin. lw4qxd0crc8wakn37w2chzyf99fqy6d Translations:Manual:Installing MediaWiki/152/tr 1198 1607443 5387321 2022-07-28T22:03:21Z Baris6161TURK 17188421 Created page with "Yüklemeyi planladığınız MediaWiki sürümünün $1 sayfasını da kontrol ettiğinizden emin olun." wikitext text/x-wiki Yüklemeyi planladığınız MediaWiki sürümünün $1 sayfasını da kontrol ettiğinizden emin olun. 27gd8zpwkvchju5pmovax1y6nwn0xt7 Translations:Manual:Installing MediaWiki/6/tr 1198 1607444 5387324 2022-07-28T22:03:29Z Baris6161TURK 17188421 Created page with "== MediaWiki yazılımını indirin ==" wikitext text/x-wiki == MediaWiki yazılımını indirin == bbls3ptvhbr0pxbau62ym7s36d9w1vj Translations:Manual:Installing MediaWiki/121/tr 1198 1607445 5387327 2022-07-28T22:03:37Z Baris6161TURK 17188421 Created page with "MediaWiki tar dosyasını [[$1|resmi indirme sayfasından]] indirin." wikitext text/x-wiki MediaWiki tar dosyasını [[$1|resmi indirme sayfasından]] indirin. 77pp99xx7uybdl5ws3kw6iffsj10gji Translations:Manual:Installing MediaWiki/122/tr 1198 1607446 5387329 2022-07-28T22:03:48Z Baris6161TURK 17188421 Created page with "Genel olarak, bir üretim ortamı kullanıyorsanız, $1 olan en son kararlı sürümü çalıştırmak istersiniz." wikitext text/x-wiki Genel olarak, bir üretim ortamı kullanıyorsanız, $1 olan en son kararlı sürümü çalıştırmak istersiniz. cigmgl8e0rqjqbgrhjzvqedkfl4i0tc Translations:Manual:Installing MediaWiki/136/tr 1198 1607447 5387331 2022-07-28T22:03:54Z Baris6161TURK 17188421 Created page with "== MediaWiki yazılımını çıkarın ==" wikitext text/x-wiki == MediaWiki yazılımını çıkarın == jdi9x5axjhtmn9fbw1u6sk2bjlh2k6z Translations:Manual:Installing MediaWiki/10/tr 1198 1607448 5387333 2022-07-28T22:04:01Z Baris6161TURK 17188421 Created page with "İndirilen dosya $2 veya $1 dosya biçimindedir." wikitext text/x-wiki İndirilen dosya $2 veya $1 dosya biçimindedir. 5d02byymvbgl4d9punm7bmuqs38bmlf Translations:Manual:Installing MediaWiki/137/tr 1198 1607449 5387335 2022-07-28T22:04:08Z Baris6161TURK 17188421 Created page with "Kullanmadan önce bu arşiv dosyasını açmanız gerekir." wikitext text/x-wiki Kullanmadan önce bu arşiv dosyasını açmanız gerekir. 9cia8c7hfyumibo086wxci1ub20hplw Translations:Manual:Installing MediaWiki/11/tr 1198 1607450 5387337 2022-07-28T22:04:16Z Baris6161TURK 17188421 Created page with "Dosyayı yerel olarak açabilir (ve ardından FTP yoluyla sunucuya yükleyebilirsiniz) veya doğrudan sunucunuzdan açabilirsiniz." wikitext text/x-wiki Dosyayı yerel olarak açabilir (ve ardından FTP yoluyla sunucuya yükleyebilirsiniz) veya doğrudan sunucunuzdan açabilirsiniz. layvetqp1g0lhuhvxkjmyaivyl7ab2u Translations:Reading/Web/Desktop Improvements/Updates/232/es 1198 1607451 5387387 2022-07-28T22:14:18Z Zapipedia (WMF) 17560702 Created page with "==== $1: Título de la página/cambio de pestañas ====" wikitext text/x-wiki ==== $1: Título de la página/cambio de pestañas ==== g08a9b6fzkxxfy9kxe3lhueg0ysw3de Translations:Reading/Web/Desktop Improvements/Updates/233/es 1198 1607452 5387389 2022-07-28T22:14:31Z Zapipedia (WMF) 17560702 Created page with "Estamos implementando una de nuestras últimas actualizaciones." wikitext text/x-wiki Estamos implementando una de nuestras últimas actualizaciones. crbmshw6s7pa4ckixfujk02y1mh8g5s Translations:Reading/Web/Desktop Improvements/Updates/234/es 1198 1607453 5387392 2022-07-28T22:14:39Z Zapipedia (WMF) 17560702 Created page with "El título de la página se mostrará encima de las pestañas como $1, $2, $3, $4 o $5." wikitext text/x-wiki El título de la página se mostrará encima de las pestañas como $1, $2, $3, $4 o $5. 38kdwptw551507xrys7kzn4zl1znar1 Translations:Reading/Web/Desktop Improvements/Updates/235/es 1198 1607454 5387395 2022-07-28T22:14:47Z Zapipedia (WMF) 17560702 Created page with "Con este cambio, mejoramos dos cosas." wikitext text/x-wiki Con este cambio, mejoramos dos cosas. lzfrd3y28600gm053h85p5k7v95u1jp Translations:Reading/Web/Desktop Improvements/Updates/236/es 1198 1607455 5387399 2022-07-28T22:14:58Z Zapipedia (WMF) 17560702 Created page with "En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está viendo." wikitext text/x-wiki En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está viendo. 137tjup7rhneidyw06vy5fqceyg2isf 5387403 5387399 2022-07-28T22:15:03Z Zapipedia (WMF) 17560702 wikitext text/x-wiki En primer lugar, estamos dejando claro que los elementos de las pestañas están relacionados con la página que se está visualizando. eam0ignn2g8rr884wzkye3pdz6go1v3 Translations:Reading/Web/Desktop Improvements/Updates/237/es 1198 1607456 5387407 2022-07-28T22:15:15Z Zapipedia (WMF) 17560702 Created page with "Se hace evidente cuando ponemos el título de la página en primer lugar." wikitext text/x-wiki Se hace evidente cuando ponemos el título de la página en primer lugar. mezd4iywqfhjqu19ljn5iba1nu1wbn6 Translations:Reading/Web/Desktop Improvements/Updates/238/es 1198 1607457 5387409 2022-07-28T22:15:23Z Zapipedia (WMF) 17560702 Created page with "Este cambio también facilita el [[$1|cambio de idioma]]." wikitext text/x-wiki Este cambio también facilita el [[$1|cambio de idioma]]. rit3z09fq3m0j6sihdeg9x12kjft7x7 Translations:Reading/Web/Desktop Improvements/Updates/239/es 1198 1607458 5387414 2022-07-28T22:15:33Z Zapipedia (WMF) 17560702 Created page with "Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página." wikitext text/x-wiki Ha desplazado el botón de idiomas a una posición aún más destacada en la parte superior de la página. bkdjgjwdxg3o1me14beob0rn52sdokf Translations:Reading/Web/Desktop Improvements/Updates/247/es 1198 1607459 5387418 2022-07-28T22:15:42Z Zapipedia (WMF) 17560702 Created page with "[[$1|Descubre más en Phabricator]]." wikitext text/x-wiki [[$1|Descubre más en Phabricator]]. mfx69rgpvoxkfjx8sn9zc29r5c31566 Translations:Reading/Web/Desktop Improvements/Updates/240/es 1198 1607460 5387421 2022-07-28T22:15:51Z Zapipedia (WMF) 17560702 Created page with "Hemos ido introduciendo este cambio en pequeños pasos." wikitext text/x-wiki Hemos ido introduciendo este cambio en pequeños pasos. 6it8d6uej88k45lmyuep76cypgtp395 Translations:Reading/Web/Desktop Improvements/Updates/241/es 1198 1607461 5387423 2022-07-28T22:16:28Z Zapipedia (WMF) 17560702 Created page with "Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[$1|wikis early adopter]]." wikitext text/x-wiki Desde los últimos días de junio, está disponible para todos los usuarios que hayan optado por el skin Vector 2022, y para algunas [[$1|wikis early adopter]]. pavop251a05vgn578ahj5ir7zvr6bo4 Translations:Reading/Web/Desktop Improvements/Updates/242/es 1198 1607462 5387425 2022-07-28T22:16:38Z Zapipedia (WMF) 17560702 Created page with "Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios." wikitext text/x-wiki Durante la semana del 4 de julio, el cambio será visible en todas las wikis de los primeros usuarios. isl41cyq19ro61q08mg7m19tml2dn1j Translations:Reading/Web/Desktop Improvements/Updates/243/es 1198 1607463 5387427 2022-07-28T22:16:47Z Zapipedia (WMF) 17560702 Created page with "Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio." wikitext text/x-wiki Además, nuestro próximo horario de oficina será el 26 de julio en lugar del 12 de julio. f3oop9zocro3attkqqi4l1kf6sjf3ut Translations:Reading/Web/Desktop Improvements/Updates/244/es 1198 1607464 5387429 2022-07-28T22:17:06Z Zapipedia (WMF) 17560702 Created page with "Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis." wikitext text/x-wiki Esto nos permitirá preparar la comunicación para que Vector 2022 sea el skin predeterminado en más wikis. 35fq06hmhgknb17m7jvdk5b581uahvm Translations:Reading/Web/Desktop Improvements/Updates/245/es 1198 1607465 5387431 2022-07-28T22:17:30Z Zapipedia (WMF) 17560702 Created page with "También estamos trabajando para mejorar el apoyo lingüístico en los encuentros virtuales (horas de oficina) en el futuro." wikitext text/x-wiki También estamos trabajando para mejorar el apoyo lingüístico en los encuentros virtuales (horas de oficina) en el futuro. bs7cd2lyc74rt09dxptep8vnppjblm5 Translations:Reading/Web/Desktop Improvements/Updates/246/es 1198 1607466 5387433 2022-07-28T22:17:41Z Zapipedia (WMF) 17560702 Created page with "¡Muy pronto te contaremos más!" wikitext text/x-wiki ¡Muy pronto te contaremos más! g84izz366drjhm6pjqfaqvxgzt9jsmq Translations:Reading/Web/Desktop Improvements/Updates/196/es 1198 1607467 5387435 2022-07-28T22:17:54Z Zapipedia (WMF) 17560702 Created page with "Esperamos implantar el nuevo índice en nuestras wikis piloto en la primera quincena de abril." wikitext text/x-wiki Esperamos implantar el nuevo índice en nuestras wikis piloto en la primera quincena de abril. jyfsa7xr6jaj9fr06xynop77ki5ofck Translations:Reading/Web/Desktop Improvements/Updates/209/es 1198 1607468 5387437 2022-07-28T22:18:03Z Zapipedia (WMF) 17560702 Created page with "Esperamos que pronto, al menos un Wikisource se añada a esa lista." wikitext text/x-wiki Esperamos que pronto, al menos un Wikisource se añada a esa lista. 32ciynkpkotgg9zos7k70dwgsqq2xaf Topic:X06odmn1wwvqm8ie 2600 1607469 5387510 2022-07-28T23:10:39Z Flow talk page manager 1946968 /* 已将此页面转换为结构式讨论板块 */ flow-board application/json {"flow-workflow":"x06odmn1wwvqm8ie"} i3i4n0pmmxxb43xjoustdk580o37vft $wgCargoLegacyNullLuaFieldsAsEmptyString 0 1607472 5387518 2022-07-29T00:52:54Z Crystal-bot 5243179 Bot: Create redirect for extension parameter to corresponding extension page wikitext text/x-wiki #REDIRECT [[Extension:Cargo]] d83n3lvavggf9574umm16d5ldkeja3y Topic:X06vod5ouyxqrulm 2600 1607473 5387519 2022-07-29T01:21:43Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x06vod5ouyxqrulm"} 6qpp6d40tkyoefw6nohxkdnesfhiw6z Translations:Wikibase/72/id 1198 1607474 5387520 2022-07-29T02:22:38Z Harditaher 2685976 Created page with "Selamat datang di halaman utama '''Wikibase'''" wikitext text/x-wiki Selamat datang di halaman utama '''Wikibase''' 3ch3cyta89ge5rwehmlhzv8vyiuhssz Translations:Wikibase/83/id 1198 1607475 5387522 2022-07-29T02:24:05Z Harditaher 2685976 Created page with "Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh $1 yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut." wikitext text/x-wiki Di sini Anda dapat menemukan dokumentasi dan sumber daya untuk perangkat lunak terbuka yang dibuat oleh $1 yang dapat Anda gunakan untuk membuat basis pengetahuan kolaboratif -- dan membuka pintu ke web Data Terbuka Tertaut. kodaaok65y17eeff5j4ma8y0unjsu3q Translations:Wikibase/84/id 1198 1607476 5387524 2022-07-29T02:24:32Z Harditaher 2685976 Created page with "Memulai" wikitext text/x-wiki Memulai dp3v34a59g96xi5pec4su2o26a78jmo Translations:Wikibase/85/id 1198 1607477 5387526 2022-07-29T02:24:40Z Harditaher 2685976 Created page with "== Menggunakan Wikibase ==" wikitext text/x-wiki == Menggunakan Wikibase == 52l15us8g1i0h7605gzpg3x1oshr42h 5387556 5387526 2022-07-29T02:29:57Z Harditaher 2685976 wikitext text/x-wiki Menggunakan Wikibase gr5lfz3ri3nahiocm87o8glbv1wydom Translations:Wikibase/86/id 1198 1607478 5387528 2022-07-29T02:24:43Z Harditaher 2685976 Created page with "Referensi" wikitext text/x-wiki Referensi 5rqd93eu5q7dwbh2xgt3nooqph0lsbk Translations:Wikibase/73/id 1198 1607479 5387530 2022-07-29T02:24:54Z Harditaher 2685976 Created page with "Apa itu Wikibase?" wikitext text/x-wiki Apa itu Wikibase? sqomn7wnx6q3zos5km0j2zdaln9wc6n Translations:Wikibase/74/id 1198 1607480 5387532 2022-07-29T02:25:24Z Harditaher 2685976 Created page with "Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur." wikitext text/x-wiki Pengantar singkat tentang perangkat lunak canggih ini untuk mengelola data terstruktur. r5cwmxighuicq3004upzhujrkmjk8we Translations:Wikibase/75/id 1198 1607481 5387534 2022-07-29T02:25:38Z Harditaher 2685976 Created page with "Haruskan saya menggunakan Wikibase?" wikitext text/x-wiki Haruskan saya menggunakan Wikibase? 5d7f0vj9ib1kp2vz3fkgcjvscuc6qah 5387536 5387534 2022-07-29T02:26:22Z Harditaher 2685976 wikitext text/x-wiki Haruskah saya menggunakan Wikibase? jeakahg1humxyzcf5795qp6sqybr302 Translations:Wikibase/76/id 1198 1607482 5387538 2022-07-29T02:26:35Z Harditaher 2685976 Created page with "Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris." wikitext text/x-wiki Menjawab pertanyaan "Haruskah saya menggunakan Wikibase?" menggunakan kata dan tanda baca dalam bahasa Inggris. qdvgg1oiunqftdx3ou6rocpvgz1j1im Translations:Wikibase/77/id 1198 1607483 5387540 2022-07-29T02:26:41Z Harditaher 2685976 Created page with "Studi Kasus:" wikitext text/x-wiki Studi Kasus: thidqjp3jvdb4gpsheux1kkds681t4t Translations:Wikibase/78/id 1198 1607484 5387542 2022-07-29T02:27:03Z Harditaher 2685976 Created page with "Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya." wikitext text/x-wiki Beberapa contoh berguna tentang siapa yang saat ini menggunakan Wikibase dan bagaimana caranya. hnjhcy3qqzhou61i5uqv1725pguv7cx Translations:Wikibase/79/id 1198 1607485 5387544 2022-07-29T02:27:32Z Harditaher 2685976 Created page with "Memulai cepat" wikitext text/x-wiki Memulai cepat g6qx8l6a4b423wulpcyapsrczgrsjzp Translations:Wikibase/80/id 1198 1607486 5387546 2022-07-29T02:27:57Z Harditaher 2685976 Created page with "Jelajahi Wikibase dalam waktu singkat!" wikitext text/x-wiki Jelajahi Wikibase dalam waktu singkat! ch3qxy1v5ub4v5677d49w965w2mjiuh Translations:Wikibase/58/id 1198 1607487 5387548 2022-07-29T02:28:00Z Harditaher 2685976 Created page with "Pertanyaan umum" wikitext text/x-wiki Pertanyaan umum p7h57eep2t076ncjm4ngt6431mcm6e4 Translations:Wikibase/81/id 1198 1607488 5387550 2022-07-29T02:28:14Z Harditaher 2685976 Created page with "'''Pertanyaan yang sering diajukan (FAQ)''' tentang penggunaan Wikibase." wikitext text/x-wiki '''Pertanyaan yang sering diajukan (FAQ)''' tentang penggunaan Wikibase. 7yru4tlfrh83j3hfx1dd1o4ljpktk9b Translations:Wikibase/56/id 1198 1607489 5387552 2022-07-29T02:28:22Z Harditaher 2685976 Created page with "Instal" wikitext text/x-wiki Instal 1lq8e7pzselunqtx5bgrf76qk2iy5pz Translations:Wikibase/82/id 1198 1607490 5387554 2022-07-29T02:28:54Z Harditaher 2685976 Created page with "Menyiapkan Wikibase di sistem Anda." wikitext text/x-wiki Menyiapkan Wikibase di sistem Anda. rijbzcv81bbpo7sauco3nyj5cpwek7b Topic:X070oc21armkc5o6 2600 1607491 5387559 2022-07-29T02:51:28Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x070oc21armkc5o6"} asjeayulmn0iodoye0nae7prupefolp Translations:Manual:Pywikibot/Compat/articlenos.py/1/zh 1198 1607492 5387560 2022-07-29T03:01:47Z GuGuMur 17451226 Created page with "文件<code>'''articlenos.py'''</code>是一个用于展示在[[特殊:最近更改]]页面中正在创建的新文章的序号的脚本" wikitext text/x-wiki 文件<code>'''articlenos.py'''</code>是一个用于展示在[[特殊:最近更改]]页面中正在创建的新文章的序号的脚本 d8763jr41b53lqvkebqen7nlsc13prk 5387562 5387560 2022-07-29T03:02:19Z GuGuMur 17451226 wikitext text/x-wiki 文件<code>'''articlenos.py'''</code>是一个用于展示在[[特殊:最近更改]]页面中正在创建的新文章的序号的脚本。 dcbdhjdxwna04fpao0w7rfzsdjser46 Translations:Manual:Pywikibot/Compat/articlenos.py/2/zh 1198 1607493 5387564 2022-07-29T03:02:55Z GuGuMur 17451226 Created page with "使用这个脚本不需要进行任何编辑行为,亦不需要任何[[Project:Bots|bot账户]]。" wikitext text/x-wiki 使用这个脚本不需要进行任何编辑行为,亦不需要任何[[Project:Bots|bot账户]]。 rlm3cd85lip7ggumd0o6z0flpvhkqg2 Translations:Manual:Pywikibot/Compat/articlenos.py/3/zh 1198 1607494 5387566 2022-07-29T03:03:31Z GuGuMur 17451226 Created page with "该脚本需要 Python IRC 库 $url" wikitext text/x-wiki 该脚本需要 Python IRC 库 $url 29jdi2bymo77s30p3huedt4k1m16opi User:Ilovemydoodle2/styles.css 2 1607498 5387642 2022-07-29T03:57:23Z Ilovemydoodle2 17636692 Created page with "span { opacity: 0; z-index: 0; height: 0px; user-select: none; }" css text/css span { opacity: 0; z-index: 0; height: 0px; user-select: none; } 2ocdz39gczfj4g8dn75k1k6sbrtvhtv Translations:Reading/Web/Desktop Improvements/248/zh 1198 1607499 5387656 2022-07-29T04:23:24Z Chubit 17346826 Created page with "第四组Wiki(在上面的时间轴上标记为$1):" wikitext text/x-wiki 第四组Wiki(在上面的时间轴上标记为$1): tkapkelkd7vwc6hwn8w7d7tv0m0atds Translations:Reading/Web/Desktop Improvements/Updates/232/zh 1198 1607500 5387658 2022-07-29T04:24:09Z Chubit 17346826 Created page with "==== $1:页面标题/标签切换 ====" wikitext text/x-wiki ==== $1:页面标题/标签切换 ==== 5g2xbj76tb366i0sxk5cc3hkgrw5zjc Translations:Reading/Web/Desktop Improvements/Updates/233/zh 1198 1607501 5387660 2022-07-29T04:24:26Z Chubit 17346826 Created page with "我们正在部署我们的最新更新之一。" wikitext text/x-wiki 我们正在部署我们的最新更新之一。 fjrepz7c6wgf97eten2ub3oqbeevgxf Translations:Reading/Web/Desktop Improvements/Updates/234/zh 1198 1607502 5387662 2022-07-29T04:24:35Z Chubit 17346826 Created page with "页面标题将显示在选项卡上方,例如$1、$2、$3、$4或$5。" wikitext text/x-wiki 页面标题将显示在选项卡上方,例如$1、$2、$3、$4或$5。 rreyoa5uctj71ks7vwxm4dxs1hu3vyh Translations:Reading/Web/Desktop Improvements/Updates/235/zh 1198 1607503 5387664 2022-07-29T04:24:52Z Chubit 17346826 Created page with "通过这一变化,我们正在改进两件事。" wikitext text/x-wiki 通过这一变化,我们正在改进两件事。 eyo3q2nvcg6dxku1zp9bsrrczuc7bkz Translations:Reading/Web/Desktop Improvements/Updates/236/zh 1198 1607504 5387666 2022-07-29T04:24:58Z Chubit 17346826 Created page with "首先,我们要明确标签中的项目与正在查看的页面相关。" wikitext text/x-wiki 首先,我们要明确标签中的项目与正在查看的页面相关。 9vkvls10c1q9u2fnwsldqp6lipbn9mt Translations:Reading/Web/Desktop Improvements/Updates/237/zh 1198 1607505 5387668 2022-07-29T04:25:04Z Chubit 17346826 Created page with "当我们将页面标题放在首位时,这一点变得很明显。" wikitext text/x-wiki 当我们将页面标题放在首位时,这一点变得很明显。 l8dj3eqkavda8jpfeaeyy8dp3rcrjuh Translations:Reading/Web/Desktop Improvements/Updates/238/zh 1198 1607506 5387670 2022-07-29T04:25:24Z Chubit 17346826 Created page with "此更改还使[[$1|切换语言]]更容易。" wikitext text/x-wiki 此更改还使[[$1|切换语言]]更容易。 1gx5lmhdwia4v9t32njo1x16q7ezpg3 Translations:Reading/Web/Desktop Improvements/Updates/239/zh 1198 1607507 5387672 2022-07-29T04:25:31Z Chubit 17346826 Created page with "它将语言按钮移到页面顶部更显眼的位置。" wikitext text/x-wiki 它将语言按钮移到页面顶部更显眼的位置。 huoywryk7mn7qhjy8apvvbrtx8hs1js Translations:Reading/Web/Desktop Improvements/Updates/247/zh 1198 1607508 5387674 2022-07-29T04:25:39Z Chubit 17346826 Created page with "[[$1|了解有关Phabricator的更多信息]]。" wikitext text/x-wiki [[$1|了解有关Phabricator的更多信息]]。 pysx4qwsx8uqgo2umm0gwhqarniy1to Translations:Reading/Web/Desktop Improvements/Updates/240/zh 1198 1607509 5387676 2022-07-29T04:25:45Z Chubit 17346826 Created page with "我们一直在逐步引入这种变化。" wikitext text/x-wiki 我们一直在逐步引入这种变化。 0glhrs0pvljfgfbnhh2iz5coqvn32sg Translations:Reading/Web/Desktop Improvements/Updates/241/zh 1198 1607510 5387678 2022-07-29T04:26:02Z Chubit 17346826 Created page with "自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[$1|早期采用者wiki]]都可以使用它。" wikitext text/x-wiki 自6月的最后几天以来,所有选择加入Vector 2022皮肤的用户和一些[[$1|早期采用者wiki]]都可以使用它。 mpqwu2kwi5b3qzlbz9z6l6m6zdmjaim Translations:Reading/Web/Desktop Improvements/Updates/242/zh 1198 1607511 5387680 2022-07-29T04:26:13Z Chubit 17346826 Created page with "在7月4日这一周,所有早期采用者wiki上都将显示更改。" wikitext text/x-wiki 在7月4日这一周,所有早期采用者wiki上都将显示更改。 nzyo8pdaghj1rxt6y0nu0jmwgqx31ax Translations:Reading/Web/Desktop Improvements/Updates/243/zh 1198 1607512 5387682 2022-07-29T04:26:36Z Chubit 17346826 Created page with "除此之外,我们的下一个办公时间将是7月26日而不是7月12日。" wikitext text/x-wiki 除此之外,我们的下一个办公时间将是7月26日而不是7月12日。 dc13dftx129wu2yg199r182ucpwmie3 Translations:Reading/Web/Desktop Improvements/Updates/244/zh 1198 1607513 5387684 2022-07-29T04:26:48Z Chubit 17346826 Created page with "这将使我们能够准备有关使Vector 2022成为更多wiki的默认设置的沟通。" wikitext text/x-wiki 这将使我们能够准备有关使Vector 2022成为更多wiki的默认设置的沟通。 8hyyeuobv8wozglpip3swktd1nq5w2e Translations:Reading/Web/Desktop Improvements/Updates/245/zh 1198 1607514 5387686 2022-07-29T04:26:54Z Chubit 17346826 Created page with "我们还在努力为未来的办公时间提供更好的语言支持。" wikitext text/x-wiki 我们还在努力为未来的办公时间提供更好的语言支持。 cfushkxuhlz4esk2e8stsvwsr4exr8q Translations:Reading/Web/Desktop Improvements/Updates/246/zh 1198 1607515 5387688 2022-07-29T04:27:08Z Chubit 17346826 Created page with "更多信息即将推出!" wikitext text/x-wiki 更多信息即将推出! 6t81n1f47ts1ggkolspunpteo88vpvj Topic:X0767m8lp1qyto3r 2600 1607516 5387690 2022-07-29T04:30:52Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x0767m8lp1qyto3r"} 0b0ghrobuwcpcs7hi1udvcz2eyzp2jo Topic:X079b4d5guxmjxaf 2600 1607517 5387693 2022-07-29T05:26:29Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x079b4d5guxmjxaf"} qxmr1pjzcime3aixk1qyiodbeitx57h Topic:X07bs049vlimq6br 2600 1607520 5387708 2022-07-29T06:10:49Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x07bs049vlimq6br"} o3qx030ty27e1x6377hh3mqk8u4qvi0 Translations:Manual:Namespace/59/it 1198 1607521 5387709 2022-07-29T06:14:51Z GpieroMW 17587484 Created page with "* 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti." wikitext text/x-wiki * 2 nomespace "virtuali" (uno per le pagine speciali generate dinamicamente e uno che serve come alias per i collegamenti diretti ai file), rispettivamente numerati -1 e -2. Poiché questi namespace non corrispondono a pagine memorizzate nel database, non è possibile creare o cancellare pagine in questi namespace e non esistono namespace di discussione corrispondenti. ozruqwa3o00i8rcw16sfnqiuuoabnt1 Translations:Manual:Namespace/24/it 1198 1607522 5387711 2022-07-29T06:15:13Z GpieroMW 17587484 Created page with "Personalizzazione dell'interfaccia del sito" wikitext text/x-wiki Personalizzazione dell'interfaccia del sito jy8s7zccqp073fuesbwab6o0h7zx7u7 Translations:Manual:Namespace/25/it 1198 1607523 5387713 2022-07-29T06:15:42Z GpieroMW 17587484 Created page with "Modificabile solo dall'utente con permessi '[[$edit-if|editinterface]]'." wikitext text/x-wiki Modificabile solo dall'utente con permessi '[[$edit-if|editinterface]]'. dyancvgbcakoomu4cqz93xsqcmku4c1 Translations:Manual:Namespace/26/it 1198 1607524 5387715 2022-07-29T06:16:02Z GpieroMW 17587484 Created page with "Pagine template" wikitext text/x-wiki Pagine template 4nfh0bg8sxauq0jq56wkih7nlygn3u5 Translations:Manual:Namespace/32/it 1198 1607525 5387717 2022-07-29T06:16:17Z GpieroMW 17587484 Created page with "=== Namespace personalizzati ===" wikitext text/x-wiki === Namespace personalizzati === fiti2ft2tclcedb1c6yqk9zka47jtop Translations:Manual:Namespace/33/it 1198 1607526 5387719 2022-07-29T06:17:10Z GpieroMW 17587484 Created page with "Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine." wikitext text/x-wiki Le estensioni e gli amministratori del sito possono definire namespace per raggruppare altre classi di pagine. 8rcbrghmjpiee8afnj0vqcgxa187c46 Translations:Manual:Namespace/19/it 1198 1607527 5387723 2022-07-29T06:18:51Z GpieroMW 17587484 Created page with "Il namespace soggetto non ha prefisso." wikitext text/x-wiki Il namespace soggetto non ha prefisso. 0gk55f0q2gjiw03qqg3l7ugh042ks2t Translations:Manual:Namespace/47/it 1198 1607528 5387725 2022-07-29T06:19:08Z GpieroMW 17587484 Created page with "{{$1|Pagine utente}}." wikitext text/x-wiki {{$1|Pagine utente}}. 3shrw5q3vcfx213i9175ckrcyi30ey9 Translations:Manual:Namespace/22/it 1198 1607529 5387727 2022-07-29T06:20:06Z GpieroMW 17587484 Created page with "Definito da $1, e se non impostato manualmente in modo diverso, ha come valore predefinito $2." wikitext text/x-wiki Definito da $1, e se non impostato manualmente in modo diverso, ha come valore predefinito $2. 9esvlfrvitx13qq0saujtjeq0e0uozt Translations:Manual:Namespace/11/it 1198 1607530 5387729 2022-07-29T06:20:28Z GpieroMW 17587484 Created page with "=== Namespace soggetti e discussioni ===" wikitext text/x-wiki === Namespace soggetti e discussioni === r6olac34lnmwsvb1cqkcvoveyu6z9wy Translations:Manual:Namespace/49/it 1198 1607531 5387731 2022-07-29T06:20:42Z GpieroMW 17587484 Created page with "Discussione" wikitext text/x-wiki Discussione ox7zs9prlssqj8kux5q5m1fr0goj9co Translations:Manual:Namespace/45/it 1198 1607532 5387733 2022-07-29T06:21:37Z GpieroMW 17587484 Created page with "Per una panoramica approfondita, vedere $1." wikitext text/x-wiki Per una panoramica approfondita, vedere $1. a80aaojke6h68deh7xiqeislagstnro Translations:Manual:Namespace/36/it 1198 1607533 5387735 2022-07-29T06:23:10Z GpieroMW 17587484 Created page with "Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main." wikitext text/x-wiki Alcuni namespace, come Project e Help, esistono solo per comodità e non hanno alcuna funzionalità aggiuntiva rispetto al namespace Main. ht5wijarwbzqcw4uwzk75szxc5j3zmn Translations:Manual:Namespace/37/it 1198 1607534 5387737 2022-07-29T06:24:17Z GpieroMW 17587484 Created page with "Le pagine del namespace dei template possono essere [[$transclusion|transcluded]] senza il prefisso del namespace." wikitext text/x-wiki Le pagine del namespace dei template possono essere [[$transclusion|transcluded]] senza il prefisso del namespace. 7vfhyhblghbfugjushfaoyfmrd0gtas Translations:Manual:Namespace/38/it 1198 1607535 5387739 2022-07-29T06:25:19Z GpieroMW 17587484 Created page with "Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[$user-talkpg|pagine di discussione degli utenti]] generano un messaggio di notifica automatico." wikitext text/x-wiki Le pagine del namespace degli utenti sono associate agli account utente o agli indirizzi IP. Le modifiche a [[$user-talkpg|pagine di discussione degli utenti]] generano un messaggio di notifica automatico. e96z7i9i07nz6rct25zsoukofzvem7j Translations:Manual:Namespace/52/it 1198 1607536 5387741 2022-07-29T06:26:03Z GpieroMW 17587484 Created page with "Le pagine Categorie possono essere spostate dagli utenti con permesso "$1"." wikitext text/x-wiki Le pagine Categorie possono essere spostate dagli utenti con permesso "$1". 1b7haz7nd87gd78rydnk3tvo2xr9tc6 Translations:Manual:Namespace/13/it 1198 1607537 5387747 2022-07-29T08:13:37Z GpieroMW 17587484 Created page with "==Namespaces incorporati==" wikitext text/x-wiki ==Namespaces incorporati== rfcjfx8in3akdc0yqzr6zy31zgge0py Translations:Manual:Namespace/39/it 1198 1607538 5387749 2022-07-29T08:15:18Z GpieroMW 17587484 Created page with "Le pagine nel namespace [[$sysmsg|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[$locale|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[$edit-if|editinterface]]." wikitext text/x-wiki Le pagine nel namespace [[$sysmsg|"MediaWiki"]] sono usate per sovrascrivere i messaggi predefiniti in [[$locale|file di lingua]] e possono essere modificate solo dagli amministratori o da altri utenti con il permesso [[$edit-if|editinterface]]. 2k0ytinlj9he2ciw9y2ff8p8xumgoay Translations:Manual:Namespace/31/it 1198 1607539 5387751 2022-07-29T08:16:11Z GpieroMW 17587484 Created page with "Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in $1." wikitext text/x-wiki Ogni namespace ha anche una costante derivata dal suo nome, con tutte le lettere in maiuscolo, gli spazi sostituiti da trattini bassi e il prefisso "NS_". Ad esempio, la costante per lo spazio dei nomi "User talk" è NS_USER_TALK. Un elenco completo si trova in $1. 13hmrqkxefz1w6pbpfdd0qel18n4c6y Translations:Manual:Namespace/30/it 1198 1607540 5387754 2022-07-29T08:23:51Z GpieroMW 17587484 Created page with "Alias per collegamenti diretti a file audio video" wikitext text/x-wiki Alias per collegamenti diretti a file audio video 91zt3obxhb8zwnxkrycftmnfq1daaf6 Translations:Manual:Namespace/50/it 1198 1607541 5387757 2022-07-29T08:27:49Z GpieroMW 17587484 Created page with "Solo [[$1|alcunew pagine]] in questo namespace richiedono i permessi $2 e $3, oltre a questo." wikitext text/x-wiki Solo [[$1|alcunew pagine]] in questo namespace richiedono i permessi $2 e $3, oltre a questo. 50vanuxq2dnoedgusek27lpwxphkyi0 5387759 5387757 2022-07-29T08:28:04Z GpieroMW 17587484 typo wikitext text/x-wiki Solo [[$1|alcune pagine]] in questo namespace richiedono i permessi $2 e $3, oltre a questo. pucjnup1tb9nbaeyvwa8jlnmr6v5dl7 Translations:Manual:Namespace/23/it 1198 1607542 5387761 2022-07-29T08:28:41Z GpieroMW 17587484 Created page with "Pagine di descrizione di multimedia" wikitext text/x-wiki Pagine di descrizione di multimedia 33rhc8j1w1drrjprg0u55p2d5jm0ad3 Translations:Manual:Namespace/46/it 1198 1607543 5387763 2022-07-29T08:30:09Z GpieroMW 17587484 Created page with "{{$1|Articoli di contenuto "reale"}}." wikitext text/x-wiki {{$1|Articoli di contenuto "reale"}}. r1u59u4fr7ydkvajyix3qdyass1qcxb Topic:X07jtwlt0wqyuroq 2600 1607544 5387765 2022-07-29T08:35:25Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x07jtwlt0wqyuroq"} 0ifrfuw4n8bo7xo9t7s27z2aga36a1k Translations:Help:Transclusion/3/it 1198 1607545 5387766 2022-07-29T08:36:08Z GpieroMW 17587484 Created page with "=== Uso di base ===" wikitext text/x-wiki === Uso di base === 06xdyfyi3fl25c73du7e2087jrxv17e Translations:Help:Transclusion/2/it 1198 1607546 5387768 2022-07-29T08:36:53Z GpieroMW 17587484 Created page with "==Sintassi della pagina di destinazione==" wikitext text/x-wiki ==Sintassi della pagina di destinazione== 7s357ihs1sy0xmz33fg9z4qns4sr0ek Topic:X07k5d7dww5etn6l 2600 1607548 5387771 2022-07-29T08:41:09Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x07k5d7dww5etn6l"} s1bg7aepddz5k1h9315xmx6egmigc8a Topic:X07kx8fpxr3ugu8x 2600 1607550 5387773 2022-07-29T08:55:03Z Flow talk page manager 1946968 /* This page has been converted into a Structured Discussions board */ flow-board application/json {"flow-workflow":"x07kx8fpxr3ugu8x"} 4al6gyqk5tuwpusklq25vnw0xddic66 Translations:Template:Empty section/2/pt-br 1198 1607551 5387904 2022-07-29T11:29:10Z Eliazhar 17652978 Created page with "Você pode ajudar o MediaWiki.org expandindo-o." wikitext text/x-wiki Você pode ajudar o MediaWiki.org expandindo-o. 1dcxv6u3sq38sp33vrii3jt6r8momqk Template:Empty section/pt-br 10 1607552 5387905 2022-07-29T11:29:12Z Eliazhar 17652978 Created page with "Você pode ajudar o MediaWiki.org expandindo-o." wikitext text/x-wiki <noinclude> <languages/> </noinclude>{{#switch: | = {{notice|1=<span lang="en" dir="ltr" class="mw-content-ltr">This section is empty.</span> Você pode ajudar o MediaWiki.org expandindo-o.}} | #default= {{#invoke:Template translation|renderTranslatedTemplate|template=Template:Empty section|noshift=1|uselang={{int:lang}}}} }}<noinclude> {{documentation}} </noinclude> 1gez8vhurwa7bgh2ca77vgefhg378ed Translations:Manual:Pywikibot/category redirect.py/5/pt-br 1198 1607553 5387907 2022-07-29T11:38:46Z Eliazhar 17652978 Created page with "Circula somente sobre [[$1|Category:categorias não-vazias e sutilmente redirecionadas da Wikipedia]] e move todas as imagens, páginas e categorias em categorias de redirecionamento para a categoria alvo" wikitext text/x-wiki Circula somente sobre [[$1|Category:categorias não-vazias e sutilmente redirecionadas da Wikipedia]] e move todas as imagens, páginas e categorias em categorias de redirecionamento para a categoria alvo m12lvm2dphwld337kfr9qdhlzeuy8rc Manual:Pywikibot/category redirect.py/pt-br 100 1607554 5387908 2022-07-29T11:38:47Z Eliazhar 17652978 Created page with "Circula somente sobre [[$1|Category:categorias não-vazias e sutilmente redirecionadas da Wikipedia]] e move todas as imagens, páginas e categorias em categorias de redirecionamento para a categoria alvo" wikitext text/x-wiki <languages/> {{Git/pywikibot}} {{Pywikibot|scripts}} <div lang="en" dir="ltr" class="mw-content-ltr"> '''category_redirect.py''' is a {{ll|Manual:Pywikibot|Pywikibot}} script used to move pages out of redirected categories. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The bot will look for categories that are marked with a category redirect template, take the first parameter of the template as the target of the redirect, and move all pages and subcategories of the category there. It also changes hard redirects into soft redirects, and fixes double redirects. A log is written under &lt;userpage>/category_redirect_log. Only category pages that haven't been edited for a certain cooldown period (7 days by default) are taken into account. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The following parameters are supported: </div> {{Pywikibot command table beginning}} {{option|delay:#|2=<span lang="en" dir="ltr" class="mw-content-ltr">Set an amount of days. If the category is edited more recenty than given days, ignore it. Default is 7</span>}} {{option|tiny|2=Circula somente sobre [[:d:Q8099903|Category:categorias não-vazias e sutilmente redirecionadas da Wikipedia]] e move todas as imagens, páginas e categorias em categorias de redirecionamento para a categoria alvo}} {{Pywikibot command table end}} <div lang="en" dir="ltr" class="mw-content-ltr"> == Usage == </div> <syntaxhighlight lang=shell-session> $ python pwb.py category_redirect [options] </syntaxhighlight> {{Manual:Pywikibot/Global Options}} [[Category:Pywikibot scripts{{#translation:}}|category_redirect]] 8adilb1sux8kvoj0h440a3nb77j4kfj